I only made this yesterday, yet it’s already mostly relevant again. Replace “bombs” with “kills,” and yeah…
I only made this yesterday, yet it’s already mostly relevant again. Replace “bombs” with “kills,” and yeah…
I believe it’s spelled “extortion”
The creator of that fork closed it down within a day.
Thank you. I need to bookmark this glorious man’s Wikipedia page.
There’s no way they would state that directly, or they would be labeled a vexatious litigant. They might have emphasized their desire to refuse future settlement offers if the first one wasn’t taken, if you catch my drift.
I also found this one for Yuzu, which captured the deleted submodules as well. There’s another one for Citra, but the submodules point to the mirrored repos under the uploader’s personal account and is missing dynarmic
.
Combining the two should bring both Citra and Yuzu back to being compile-able.
git clone https://..../yuzu.git
cd yuzu
git submodule update --init --recursive
tar -cvzf ../yuzu.tar.gz yuzu
And store that on a couple of flash drives.
That fork seems like a cash grab considering it already has a Patreon. The person who uploaded it wiped the commit history and missed the entire submodule graph, including the ones deleted by the Yuzu/Citra team. On the bright side, the Windows build provided appears to be clean.
I’m not sure about voluntary deletions, but a DMCA request will take every known fork down with it.
I can’t quite remember the name, but there is actually at least one U.S. judge that takes the time and effort to learn about the technology in depth before making a ruling.
I don’t think that applies in this case since DeCSS was unambiguously and primarily designed to strip DRM (with interoperability as a consequence), while Yuzu was primarily designed to emulate a system (with DRM “circumvention” as a consequence).
Nintendo isn’t arguing against emulation itself, they’re challenging Yuzu on the anti-circumvention part of the DMCA. There isn’t precedent for going against emulators using that yet AFAICT; Sony v. Bleem is entirely unrelated.
Wikipedia has an entire list of anti-circumvention exceptions under the page for the DMCA. I have no idea how those exceptions came to be or how much money and time was involved to make it happen, but it does seem to be changing in our benefit over time.
Do you think it’s possible that Nintendo is having the devs agree to that statement is a way for them to prevent others from forking Yuzu and continuing development? If someone stripped out the ROM decryption code, it would be harder to claim the fork falls under 17 U.S.C. 1201 as a circumvention tool. By having the original creators state it is, would it open up derivative works to being classified as one in future lawsuits regardless of whether it still contains the questionable code?
Nintendo’s angle is more along the lines of:
It’s a massive reach, but it’s a plausible argument—or even a good one if the judge is a technologically illiterate luddite. Beyond that, Nintendo is the kind of litigant that will drag out a lawsuit until the other party is forced to settle.
They also have a Patreon. Since Nintendo got away with killing Yuzu, Ryujinx is probably next.
Nintendo went after them for using (not distributing) prod.keys
to decrypt game titles and system firmware under 17 U.S.C. 1201 (2), which sidesteps having to challenge the legality of emulation directly. I guess Yuzu doesn’t have the funds to fight them in court on that.
In a professional capacity, it was React with TypeScript for front-end, Node for backend with Nginx to serve static assets. At the end of the day, it wasn’t really for me. I enjoy web dev for hobby projects, but working with it day after day ruined my intrinsic desire to keep doing it.
As a former web dev, I know it’s normal industry standard stuff, but it’s really hard to give Reddit the benefit of the doubt here.
Their tracking is completely ingrained in the webcomponent-based SPA itself, beyond what’s reasonable for anonymized analytics. Disabling cookies even broke loading content, despite being logged out.
FTFY.
He also 110% deserves to have his darling little piggy bank IPO ruined after the bullshit, lack of communication, and steamrolling pulled with the API fiasco.