Thread with 25 posts
jump to expanded postmaintaining an open-source game emulator has really perverse incentives. users do not care whether your code is good or clean or properly tested. if a horrible hack gets a popular game running, they will plagiarise your WIP patch, make their own build of it, and distribute both…
…at which point it becomes very tempting to just move to a completely closed development model, where we only publish code that is complete enough to land on trunk. and already we are like half of the way there with touchHLE, but it's tempting to go all in. perverse incentives!
by the way, did you know that US copyright law does not recognise moral rights (i.e. the right of attribution)? it's purely about copying. plagiarising open-source code is generally (IANAL) legal unless the license prohibits it. :(
@hikari uh. what?
@hikari I think I'm not clear on what you mean by "plagiarizing", since usually that would imply copying?
@hikari the distinction between "copyright", "moral rights", and "author's rights" are largely philosophical; the actual practical distinctions are fairly nuanced, and tend to come down to limitations on what rights can be transferred or sublicensed
@hikari you could maybe consider relicensing to GPLv3 (as explicitly allowed by the MPL 2.0) and exercising the GPLv3 clause that allows "Prohibiting misrepresentation of the origin of that material, or requiring that modified versions of such material be marked in reasonable ways as different from the original version"?
@saagar yes but that doesn't give me DMCA takedown powers
@saagar depends who wields them and for what purpose
@saagar fruit company?
@saagar …which
@saagar i thought that was the other mysterious online fruit whisperer's thing
@hikari Lucky for me, Darling is far from a state where I would have to worry about that happening.
But it's something I do worry about when Darling becomes usable/popular enough... I probably wouldn't keep development closed though if this does become an issue for Darling.
@curioustommy oooh, you work on darling? it's a cool project. i do wonder what would have happened if i'd chosen to fork darling way back when, rather than writing touchHLE from scratch.
@hikari I really don’t get it, how do hacky forks with no contributors impact you? If it’s open source how is this plagiarism? Are they using your branding and name? You’re allowed to protect those independent of the source.
@penny there's fairly little i can do to protect the name, and these builds already create confusion, though i've taken some measures already to try to do something about it.
aside from a branding problem, what's frustrating is that this kind of thing can lead to people attributing your own work to someone else, and that isn't great from a motivational standpoint
@hikari would that be why gstreamer had "good" "bad" and "ugly" branches ?
@PypeBros i don't know, but that sounds interesting!
@dcnick3 that would make much sense, given the field.