Just saw a CC No Derivatives licensed artwork fly through my timeline. I have opinions on -ND:
https://rys.io/en/101.html
Short version:
ND doesn't stop bad things (say, appropriation) from being done, while stopping good things (say, translation) from being done.
On a broader level it makes promoting and building libre-culture together harder.
ShareAlike is as effective at stopping some bad things (say, corporations using stuff in ads) from happening, while explicitly allowing the good.
I dive deeper into my reasoning in the blogpost (inb4 "like and subscribe").
Sorry about the subtoot (kinda-sorta), but didn't want to jump into the artist's thread and do a reply-guy thing.
Obviously everyone has the right to choose whatever license they like and feel suits them best!
But I feel there is a lot of mythos around what No Derivatives can and cannot do, and I believe it is harmful to the broader libre culture movement.
Semi-related, there is a batch of new "anti-capitalist" software licenses that is getting traction. I have similar problems with them as I have with NC and ND. I guess I should write them up, too.
But tl;dr would be: fragmenting the FLOSS codebase by using incompatible and legally unclear software licenses like that is shooting ourselves in the foot; AGPL achieves the same (big corporate capitalist entities stay the fsck away), without causing that much legal incompatibility/fragmentation.
@penny now go ahead to Pleroma's git repository, check all the dependencies, and imagine they all use incompatible licenses.
And then try to write a complicated piece of software and release it for free onto the world, without risking somebody who might disagree with you on something sues you for it.
Licensing compatibility is the *superpower* of FLOSS. Undermining it is exactly what corporate drones would *love*. They don't care that much about your code, as long as nobody uses it for anything serious.
@penny well if you don't care about licenses, why are you debating stuff about licenses?
Thing is, nobody cares about licenses, until they do. Until it turns out that their little project has grown to a point where it suddenly matters, but now they're stuck.
I'm probably not going to convince you. That's cool. I hope you never bump into this issue in any of your personal projects.
You might want to not make public statements about your potential intent to infringe on software licenses, though. Stay safe!