- cross-posted to:
- foss
- piracy@lemmy.dbzer0.com
- cross-posted to:
- foss
- piracy@lemmy.dbzer0.com
You must log in or # to comment.
“We are trying to get the builds working.” And begging for contributors on discord. This isn’t a real project, just a reupload of yuzu’s source code with some overly optimistic aspirations.
No Android builds :(
Building a community around Discord ain’t it
I hope the former Yuzu developers can coalesce into one or two projects and continue their work on a completely different project like Suyu, with other repos syncing to it in case it gets taken down later.
Calling Suyu a “completely different project” is a bit misleading. :D Because it’s just Yuzu with a rebranding or renaming. I don’t think the former Yuzu developers will work on any fork of Yuzu, which is probably part of the settlement.
Yes, I jest, only in hopes that the other projects are “completely different” for the purposes of the lawsuit and settlement.
Unfortunately as part of the settlement, the Yuzu team is prohibited from ever working on an emulator for any Nintendo console again. This is why Citra was shut down as well.
suyu, prounced “sue-you”
😂 You can never beat FOSS, I guess.
Nintendo:
We look forward to fucking up some more open source developers
This time without incorporated companies to hide behind! They can take our money directly!
– A wild Codeberg appeared. –
Codeberg is a collaboration platform providing Git hosting and services for free and open source software, content and projects.
The organization selected the European Union for their headquarters and computer infrastructure, due to members’ concerns that a software project repository hosted in the United States could be removed if a malicious actor made bad faith copyright claims under the Digital Millennium Copyright Act.
In June 2022 the Software Freedom Conservancy’s “Give Up Github” campaign (in response to the GitHub Copilot licensing controversy) promoted Codeberg as an alternative to GitHub.
So is this stock Yuzu without any changes? IIRC the legal issue was something about circumventing copy protection, so would this project be subject to the same issues?
Also, how do I verify that this fork isn’t malware wrapped in emulator code?
Also, how do I verify that this fork isn’t malware wrapped in emulator code?
The code is open source, you read it all, ensure that you download exactly the code you read, and you compile it yourself. That’s the only way, in general, to accomplish this.
