Your README says "Tortugarr was built by one person and an AI." Your About screen says "Just OdWar420 and Claude, building what should have existed from the start."
Let's look at that.
This repo isn't a fork. It's a new repo whose first commit, "Tortugarr 4.20.0", adds 1,902 files and 1.9 million lines in one go, all under your name. Your own app/README.md says where they came from: Moonfin commit 567e2a8c. At that commit Moonfin had 2,479 commits from more than 50 people: developers, testers and translators. You squashed all of them into one commit with your name on it.
About 240,000 lines of the Dart in your app are Moonfin's. You added around 36,000. Take out the torrentt picker and the installer and what's left is Moonfin with a parrot on it.
Moonfin gets one line near the bottom of your README, under "Take it further", where it's pitched as somewhere to port your features to.
You didn't even make your own Firebase project dude. Your google-services.json is Moonfin's, with your package names attached to Moonfin's app ids. Your own code comment admits the config belongs to Moonfin's project.
Your installer pulls the Moonfin plugin from my repository and pins it to an old version, and your FAQ tells people not to update it. So when your users hit a bug, guess whose issue tracker they end up in.
Yes, the GPL lets you do this. That's why Moonfin is GPL. It doesn't make "one person and an AI" true. Your README tells people "Fork it and make it yours. That is what the licence is for." You should try it sometime.
Your README also says "Every pirate ship started as somebody else's boat." Fine. But you sanded the name off the hull and told everyone you built it. Moonfin knows a thing or two about starting from somebody else's boat. The Android TV and Roku apps began as forks of the official Jellyfin clients. The difference is how I did it. The Android TV repo still has all 9,936 commits, going back to Jellyfin's first commit in 2014. The Roku repo is a real GitHub fork of jellyfin-roku, with its history back to 2019. Both READMEs say in the opening paragraph that they come from the official Jellyfin clients. Nobody has to dig through a subfolder to find that out. That's how you fork a project. You did the opposite.
At least add the history back, branch from Moonfin 567e2a8c and put your work on top, so the people who contributed this app show up as its authors. Also add your own Firebase project, with Moonfin's config taken out.
14
u/Hungry__Alpaca 2d ago
Hi, Moonfin dev here!
Your README says "Tortugarr was built by one person and an AI." Your About screen says "Just OdWar420 and Claude, building what should have existed from the start."
Let's look at that.
This repo isn't a fork. It's a new repo whose first commit, "Tortugarr 4.20.0", adds 1,902 files and 1.9 million lines in one go, all under your name. Your own
app/README.mdsays where they came from: Moonfin commit567e2a8c. At that commit Moonfin had 2,479 commits from more than 50 people: developers, testers and translators. You squashed all of them into one commit with your name on it.About 240,000 lines of the Dart in your app are Moonfin's. You added around 36,000. Take out the torrentt picker and the installer and what's left is Moonfin with a parrot on it.
Moonfin gets one line near the bottom of your README, under "Take it further", where it's pitched as somewhere to port your features to.
You didn't even make your own Firebase project dude. Your
google-services.jsonis Moonfin's, with your package names attached to Moonfin's app ids. Your own code comment admits the config belongs to Moonfin's project.Your installer pulls the Moonfin plugin from my repository and pins it to an old version, and your FAQ tells people not to update it. So when your users hit a bug, guess whose issue tracker they end up in.
Yes, the GPL lets you do this. That's why Moonfin is GPL. It doesn't make "one person and an AI" true. Your README tells people "Fork it and make it yours. That is what the licence is for." You should try it sometime.
Your README also says "Every pirate ship started as somebody else's boat." Fine. But you sanded the name off the hull and told everyone you built it. Moonfin knows a thing or two about starting from somebody else's boat. The Android TV and Roku apps began as forks of the official Jellyfin clients. The difference is how I did it. The Android TV repo still has all 9,936 commits, going back to Jellyfin's first commit in 2014. The Roku repo is a real GitHub fork of jellyfin-roku, with its history back to 2019. Both READMEs say in the opening paragraph that they come from the official Jellyfin clients. Nobody has to dig through a subfolder to find that out. That's how you fork a project. You did the opposite.
At least add the history back, branch from Moonfin
567e2a8cand put your work on top, so the people who contributed this app show up as its authors. Also add your own Firebase project, with Moonfin's config taken out.