alyaza [they/she]@beehaw.orgM to Gaming@beehaw.orgEnglish · 3 days ago"I didn’t fully appreciate the scope of it": a year on from taking over, Nexus Mods owners reflect on the challenges of their push to minimise modding hasslewww.rockpapershotgun.comexternal-linkmessage-square8linkfedilinkarrow-up122arrow-down11
arrow-up121arrow-down1external-link"I didn’t fully appreciate the scope of it": a year on from taking over, Nexus Mods owners reflect on the challenges of their push to minimise modding hasslewww.rockpapershotgun.comalyaza [they/she]@beehaw.orgM to Gaming@beehaw.orgEnglish · 3 days agomessage-square8linkfedilink
minus-squareMorgikan@fedia.iolinkfedilinkarrow-up6·2 days agoThat’s not quite the same thing. Yes, someone can fork your project, but you maintain control over your own repository. Nobody gets to say “I need this, so you can’t remove it or previous commits related to it from your repo”. You can totally filter and scrub your own repos.
minus-squareFarceOfWill@infosec.publinkfedilinkarrow-up9·2 days agoYou control your own disk but by putting it on nexus you’ve put it into their repo and said others can depend on it.
That’s not quite the same thing.
Yes, someone can fork your project, but you maintain control over your own repository. Nobody gets to say “I need this, so you can’t remove it or previous commits related to it from your repo”. You can totally filter and scrub your own repos.
You control your own disk but by putting it on nexus you’ve put it into their repo and said others can depend on it.