Using Leaked Nintendo Source Code Poses Serious Legal Risk to Emulators [link]
Re: Using Leaked Nintendo Source Code Poses Serious Legal Risk to Emulators [link]
Seems like the emulator devs have their bases covered by publicly saying they would never touch the leaked files. wink wink
https://twitter.com/bitinkstudios <- Follow me on twitter! Thanks!
https://www.patreon.com/bitinkstudios <- Support me on Patreon!
https://www.patreon.com/bitinkstudios <- Support me on Patreon!
Re: Using Leaked Nintendo Source Code Poses Serious Legal Risk to Emulators [link]
The content of the linked article actually says the exact oposite of this thread's title.
Tom Dietrich, a Copyright Attorney at The McArthur Law Firm in Los Angeles, told Motherboard in an email that Nintendo would need direct evidence of the leaked code appearing in an emulator to have a strong infringement case. Looking at the leak and using it isn’t enough because reverse engineering code is legal in the U.S.
Re: Using Leaked Nintendo Source Code Poses Serious Legal Risk to Emulators [link]
This also doesn't invalidate the copyrights of existing emulator code. Don't forget that we've had N64, Gamecube, and Wii emulators before the leak too, for several years.
Re: Using Leaked Nintendo Source Code Poses Serious Legal Risk to Emulators [link]
It doesn't even matter if Nintendo has a case or not - they can shut down any emulator project with the proverbial snap. Sony's case against Bleem! was dismissed, but not before shutting that company down (that said, Bleem! was selling their emulator).
The Dolphin devs are right - they don't want to test the line between copying and merely using the code.
The Dolphin devs are right - they don't want to test the line between copying and merely using the code.
-
- Posts: 1510
- Joined: Thu May 19, 2005 11:30 am
Re: Using Leaked Nintendo Source Code Poses Serious Legal Risk to Emulators [link]
Doubtful that they can do that effectively in the case of an open-source project from a pseudonymous author.strat wrote:they can shut down any emulator project with the proverbial snap
Re: Using Leaked Nintendo Source Code Poses Serious Legal Risk to Emulators [link]
Github or other hosting will bow to a court order.
-
- Posts: 1510
- Joined: Thu May 19, 2005 11:30 am
Re: Using Leaked Nintendo Source Code Poses Serious Legal Risk to Emulators [link]
Plenty of non-U.S. hosting options that don't honor American court orders available. And getting a court order in a foreign country on something that is not as trivial as hosting pirated motion pictures, although entirely possible, is at least not easy as a "snap".
But yes, if one insists on using GitHub, it's easier to shut down one's project.
But yes, if one insists on using GitHub, it's easier to shut down one's project.
- NovaSquirrel
- Posts: 483
- Joined: Fri Feb 27, 2009 2:35 pm
- Location: Fort Wayne, Indiana
- Contact:
Re: Using Leaked Nintendo Source Code Poses Serious Legal Risk to Emulators [link]
According to Hector Martin the leaks aren't even useful to emulation anyway
Re: Using Leaked Nintendo Source Code Poses Serious Legal Risk to Emulators [link]
He's talking about a Wii POV; for N64 emulation, the verilog being there should be more useful. In the last tweet he says
Remember there is no good N64 emulator in existence. They all suck in various ways.Now if the leak *really* contained full Verilog for the GPU, for example, that could help resolve long tail emulation mysteries... But no sane emulator developer is going to want to taint their project like that. But it doesn't, so this is a moot point.
Re: Using Leaked Nintendo Source Code Poses Serious Legal Risk to Emulators [link]
Even if the leak doesn't provide much new knowledge, he clearly says that it does give some insight, so it's hard to argue that the leak isn't any useful, despite that he's trying to say otherwise. Information is information.
It's understandable that a big project like Dolphin doesn't want to associate themselves with a leak of confidential information though.
Regarding using code, emulators like Dolphin usually requires the user to provide themselves things dumped from a real system anyway, so I don't see why that would be a problem. I guess something similar could be done with Verilog code if it was about that.
It's understandable that a big project like Dolphin doesn't want to associate themselves with a leak of confidential information though.
Regarding using code, emulators like Dolphin usually requires the user to provide themselves things dumped from a real system anyway, so I don't see why that would be a problem. I guess something similar could be done with Verilog code if it was about that.
Re: Using Leaked Nintendo Source Code Poses Serious Legal Risk to Emulators [link]
No, verilog is turned into hw, it can't be dumped via software. "Dumping" hw is decapping and manual transcription.
Re: Using Leaked Nintendo Source Code Poses Serious Legal Risk to Emulators [link]
I was talking about dumping software like GC/Wii DSP ROMs or the NAND memory in the Wii which Dolphin uses, not Verilog.
That about Verilog was the Verilog for the GPU (which the leak didn't contain) for a hypothetical hardware clone that needs it. An emulator wouldn't even be written in Verilog in the first place, so I don't see the problem there either.
That about Verilog was the Verilog for the GPU (which the leak didn't contain) for a hypothetical hardware clone that needs it. An emulator wouldn't even be written in Verilog in the first place, so I don't see the problem there either.