I have a déjà vu! 
(20 chars)
14 Likes
I assume we all would appreciate new good supported apps, but it is not so cool just to fork because your mail ist not answered within few days. And if you still use old code, you should at least have all conributers mentioned in your project.
Maybe it’s better first to clarify approach befor start with code and release it. Maybe just start one discussion here to ask people about what and how?
I am sure, if you would ask hiw to contribute, nobody will say noway 
1 Like
That’s also how people with less scruples walk all over you (or the things you hold dear).
I was also going to comment on the commit history of the repo; but since it is gone, i guess i don’t need to.
1 Like
Lack of culture/knowledge. Not harmful means, I’m afraid.
Firm response may be necessary, perhaps, but more useful with educational ingredients, I’d say.
This leads me to this.
3 Likes
There are ways that people can comment constructively about something they don’t agree with without being rude and sarcastic, and without making personal attacks.
That’s just common courtesy.
Negativity just enflames the situation and creates conflict where none is necessary.
It also loses the poster respect and credibility.
5 Likes
You’re absolutely right, and in fact I spoke with Werkwolf a little while ago.
I think we had the same thing happen a few weeks or months ago, when somebody copied Whisperfish and tried to impersonate @rubdos, so that may explain the harsh reaction here after it happened again.
I think that also shows that AI can only steal and remix things humans have already created, but is not capable of original thought. Although it does seem to have at least tried to obfuscate this by removing the original contributors from the README. 
Please do not forget that you will likely encounter proportionally more negative reactions than positive ones to whatever you create, simply because giving praise somehow seems to be less common than criticism nowadays. If you let yourself get discouraged by that, you will never achieve success.
I do hope you will not try to take the lazy route again, though.
4 Likes
Actually, I wrote the README myself, and I thought that adding the link to Fern’s GitHub page would be enough as credit — clearly it wasn’t, and I’ve already apologized for that. As for the AI “remixing”, I also have something to say about that, because I was the one who took Fern’s open code, fed it to the AI, and told it to start from that project. So it’s normal that certain names remained.
These are all things I’ve already discussed extensively with WerkWolf in the Telegram chat.
But in any case, if this app ends up being available on Storeman again, I’ll definitely have it go through WerkWolf’s review first.
4 Likes
Just FYI, I didn’t want to attack you or undermine your project. My concern generally is that there is quite a lot fragmentation already inside Sailfish ecosystem, which would be improved by people working together. I, as a end user would benefit from that so I might be a little bit selfish here. But of course I understand as every community dev is working during their freetime it might be easier route to do things solo. I’m just happy that there are devs working on Sailfish, even if they do apps only for themselves.
2 Likes
I mean, generally speaking, if it is an open-source license and you comply with its requirements (which, depending on the license, may also include crediting the original contributors), you can fork it to your heart’s content without needing approval from the original author. But it is certainly nice if you ask anyway.
Even if a bit late, I did it and I’m doing it.
3 Likes
I like RooTelegram and it makes me sad, that you closed the Repo. I would ask to keep it open until your development will be pushed to Fernschreiber. I really like the features you developed…
3 Likes
This here.
Also, I am not attacking @RootGPT. They do what they do responsibly, even if I would not use LLM-produced code to get there.
2 Likes
Thank you so much for your onestly feedback.
2 Likes
My 15 cents: While i am Fernschreiber and Yottagram user from day one, thanks @WerkWolf and @Mister_Magister ! i love @RootGPT features like Sharing and Daemon which are missed in Fernschreiber and also Voice and Video calls which are in the development! If RooTelegram is heavily based on Fernschreiber, merging the missing feature together would be the best outcome for the community. And if Sebastian has no time atm. to develop new features, the new features added by @RootGPT should find the way to the app asap. I think we use Telegram lot. Its a must-have application for many SailfishOS users, so many ppl (including me) are very thankful for the SailfishOS Telegram Client developers, @WerkWolf @Mister_Magister and @RootGPT now! Thank you guys! The most satisfaction for the developer is - when people use your software. Thank for your work and contributions!
9 Likes
Do you want to hear something funny? The credits for all contributors were there from the very beginning — you just had to look at the app’s About page, as shown in the image I had already uploaded at the start of the thread. I only needed to add the link in the README.md on the GitHub page…
7 Likes
I see many abandoned (or lets say old) apps coming again under the original name (Fork). From the other side i understand you, you took Fernschreiber code, updated it heavily (The original App doesn’t saw updates since 12.2023) and released under another name. I am not very strong in GPL3 Terms, but since the link to the original project and original developers is under the about page - personally - i see no problem at all. And when Sebastian would have time again, he can review your code and take it for updating Fernschreiber (If he will want it) So for my users perspective - it doesn’t matter how the app is calling, for me is functionality important. But from the Open Source / GPL view it might be important. Anyway: you did a good job, and it would be very bad, when your app (or your code) would not be used by the community.
9 Likes
Since the project is up again - i guess i will comment.
The project uses summary commits - as if there is another master repo, or no real version control at all.
The comments and commit messages are in native language instead of English.
I.e. the author is thus actively working against anyone wanting to inspect, contribute to, or learn from the project - doing the bare minimum that the original license requires. A real dick move. How is this not being overly protective of “your” work, which is precisely what the original author was criticized for?
6 Likes
what you said, plus this quote from the store description / readme:
It is specified that any negative comment regarding this circumstance will not only be ignored but will result in the immediate blocking of the user.
in other words: “I forbid you to criticize me! If you do it anyway, I threaten to delete your comments!” (on OpenRepos, an app owner can delete any comment on their app page; there’s no such thing as “blocking”)
I personally would not touch an app developed like that with a ten foot pole, let alone trust it with my private chats or financial data. It’s an open invitation for bad guys to sneak in like it regularly happens - the last incident with Arch Linux’s AUR. I’m not accusing the author of being a bad guy themself but this kind of irresponsible development process with little to no accountability/reviewability means that anything can happen and no one will ever notice. Especially with a chat/finance app, this is a big red flag. Others may see that differently of course.
6 Likes
I can see some valid criticism overall, but when it comes to the comments, I would probably do exactly the same.
The internet is full of trolls and people who only know how to tear things down and are incapable of building anything themselves. As a developer, you have to stay on top of that constantly, or they’ll slowly drain your motivation and try to drag you down to their level. After dealing with that for several decades, I’ve learned that “delete, ban, don’t engage” works best.
1 Like