- cross-posted to:
- emulation@lemmy.ml
- piracy@lemmy.dbzer0.com
- cross-posted to:
- emulation@lemmy.ml
- piracy@lemmy.dbzer0.com
You must log in or # to comment.
Forking a repo is not the same as developing it. Any idiot can rehost the existing source code, but all the developers with knowledge of the code base and project just got axed by Nintendo.
Why throw away the commit history?
Also made communities, setup a patron and donation mails.
This just seems like a dude wanting to scam money out of it and/or taking credit for continued development, disregarding any effort made before the fork.
One of the problems with Yuzu (to nintendo) was that it contained the encryption keys pulled off nintendo switches. By removing commit history you actually can permanently remove this part of the code. There might be a more clever way to do this. Thats my best guess.
Although a good guess, this looks more like the work of someone who’s in way over their head and barely knows how to use git. Probably just downloaded the repo as a zip instead of cloning it through git. At least that’s the vibe I get from their commit history and other repos.
So basically, this person did the right thing on accident.
I downloaded and set up Yuza the day before all this went down, and it did not include encryption keys. And trust me, I looked.
Even if there were keys, you could scrub the history instead of deleting it outright
Except, if someone had the repo cloned before the purge, they would retain all of the information, wouldn’t they?
What is different about this project? How will they reign in Nintendo’s legal team?
Like 10 minutes ago the project was nuked by the owner
