Community to talk about emulation & roms.
RULES:
1.) No bigotry
LINKS:
Emulation Wiki - Your source for everything emulation :)
[WIP] Emulation Links Wiki - My personal wiki for emulation links, please help contribute!
r/Roms Megathread - Megathread of Roms
RetroArch - RetroArch is the popular front-end to libretro which is a simple API that allows for the creation of games and emulators.
Specifically the emulation part. I wonder could this be used to take down a future emulator emulating the game. I know Nintendo claimed DMCA for the yuzu stuff. Not sure about EULA if there would be grounds to do so. Either way I'm sure we can expect more of this crap as time goes on.
like the rest of you I never read and ignore them , but on a whim I skimmed this one and this stood out.
So if some company added to their software a short EULA, with no frivolous provisions, that you could ctrl+f in, and access after you've accepted and installed the program, that you can reasonably read before making a purchase, that you can copy to the clipboard or print, and that otherwise didn't have any glaring things indicating it's in bad faith, would you be down with EULAs?
Let's say the whole text is something like:
Or let's say it was that text plus a plainly-stated contractually-binding prohibition against cheats and mods. Or a prohibition on streaming the game. Or a prohibition on playing any game by Ass Pucker LLC ever again.
You're asking for a blanket statement from me but giving specific examples.
Regarding what you said before the quote block, yes. My generic objection to EULAs would be lifted in this case.
Regarding the obviously objectionable example clauses in the block and after it, I am opposed to those but they are a reason to reject the particular EULAs which contain them, just like any contract which contains similar dispositions (imagine having to agree never to eat at Burger King when you buy a Big Mac).
My previous comment was about things that are generally wrong with the practice of EULAs because they have become a de facto standard, and was not meant to imply that those are the only things that can possibly be wrong with any EULA ever.
Well at least I'd know where the boundaries are. I don't want to have to distill a 10pg eula to it's core tenets, is rather plain language for most of it, with technical legal language only where it's critical, and not as an addendum or post script.
If people actually understand what the limits are, the creators can get useful feedback on what the community likes or doesn't about the terms.