[embedding-shape]

I've used MIT almost exclusively for anything I've published, under multiple identities, and seems to work fine too. What benefit would AGPL3 give me over MIT, in terms of avoiding burnout? So far, saying "No" or not working for free for companies, been working fine as an approach so far, but always open to hearing even better approaches.

[hilariously]

It prevents the No from ever materializing because almost no one wants to use your code to build on top of.

[embedding-shape]

How am I supposed to practice saying "No" in low-stakes situations then? :|

[hilariously]

I would tell you but I am practicing right now.

[greenavocado]

There's also the MIT+NIRREG (misspelling intentional) license

plusnirreg.com (misspelling intentional) is the home page of the license

It's also AGPL compatible!

> Why?

By including the word "NXXXXXX" in a LICENSE file that must be distributed with the software you will ensure:

The software will not be used or hosted by western corporations that promote censorship

The software will not be used or hosted by compromised individuals that promote censorship

Users of the software will be immune to attacks that would result in censorship of others