This assumes front-end development.

From a (dev)ops perspective, if I had a vendor hand me a tarball instead of proper documentation, I’d look very far away from their company. It isn’t a matter of if shit goes wrong, but when. And when that shit goes wrong, having comprehensive documentation about the architecture and configuration is going to be a lot more useful than having to piece it together yourself in the middle of an outage.

For your sake, I hope your employment was agile as well. Those jobs sound like they were dumpster fires waiting to happen.

This seems like common sense, no? Return 403 or better yet reject TCP connections on port 80 entirely.

That initial HTTP request header and body is sent in clear text, and that’s more than enough to leak credentials or other sensitive data.

The emulator itself doesn’t necessarily have to exist only to run retail games. It could be used to develop or debug homebrew and marketed as such. They wouldn’t even need to have decrypted the operating system to understand it, as Atmosphère is a complete reimplementation untainted by Nintendo code.

If it ran retail games as a consequence of being accurate to real hardware, that would just be a happy accident. And as long as the developers don’t acknowledge running retail games and don’t directly assist in fixing them, they have plausible deniability.

This raises the following question: if Nintendo does not respect in the slightest our property rights by pulling such stunts, why should we as end users respect their intellectual property rights?

I’m a big fan of the “buy a game and crack it right after” philosophy. Respect property rights until something is in one’s legitimate possession, and then remove any encumbrances preventing it from being used in the way the purchaser wanted.

They sued under the DMCA, though?

Mind sharing the links?

I know Ryujinx stopped accepting people into their Discord, but that’s all I’m aware of at the moment.

You, sir/madam, are amazing.

They’re NAND chips containing encrypted games soldered to a PCB and connected to the console through a proprietary data transfer interface. A cartridge is a glorified SD card, and you don’t need to agree to any ToS to buy one second-hand.

Decrypting the ROM ahead of time and requiring that to be used would be the safe alternative.

It would require a separate tool to do that first, but decoupling the steps would prevent Nintendo from going after the much-harder-to-develop emulator using the argument they used here. If they kill the decryption tool, another one pops up.

The point is that the hypothetical user never used the console’s ToS-encumbered software. Fusee bypasses the bootloader and jumps straight into a user-provided payload, which doesn’t have any terms attached to it. Those payloads are capable of dumping prod.keys and the data off the cartridges to an SD card.

Ouch. Hopefully, someone has it installed and can share the APK. Or better yet, if somebody archived the entire org instead of just the yuzu repo.

Nintendo’s ToS doesn’t mean anything to people who never agreed to it. Someone can buy a fusee-vulnerable Switch and use tools to dump the prod.keys and legally-purchased cartridges without ever agreeing to a single thing.

Yuzu absolutely went into a gray area with not exclusively using pre-decrypted ROMs. That’s where they opened themselves up to Nintendo’s argument in the lawsuit.

Edit the computer hosts file to resolve yuzu-emu.org to 0.0.0.0 or 127.0.0.1? That will stop it from connecting, at least.

A lawyer on the !technology@lemmy.world thread mentioned that a settlement doesn’t set a precedent, so they’re safe from that at least.

Nintendo’s argument also doesn’t apply to emulators that only work with pre-decrypted ROMs. Anything older than a PS3 doesn’t have encryption at all.

I wouldn’t call it a clear violation of 17 U.S.C. 1201, but it was a plausible one. I do agree that they would have been blasted for legal fees trying to figure that part out, however.

Nintendo had a leg to stand on, but it was highly dependent on whether the judge would find an emulator’s primary purpose to be DRM prevention. A good judge that does research into the subject likely wouldn’t find it to be the case, since the primary purpose is emulation and decrypting game titles is only a small part of that. Ending up with a luddite or corporate shill judge is always a huge risk, though.

I’m not sure. Worst case, you can compile it manually from one of the archive forks?

You can’t officially download it anymore. If you’re familiar with compiling things, there are backup forks everywhere, though. A lovely Lemming posted an archive.org link to download the last builds in other comments here.

In even more unrelated news, does anybody know of some good spots to bury random flash drives containing a lot of C++ code?

Apkmirror has the APKs still

https://lemmy.zip/comment/7971207

This guy made a public archive.