You’re mixing up cranks and bigots. Bigots tend to get banned because they’re harmful. Cranks tend to exclude themselves on principle.
The term “crank” is usually used as a pejorative, but cranks can sometimes be beneficial. Richard Stallman is the prototypical example of a Free Software crank. Definitely annoying, but also definitely a net benefit to all of us.
That’d be covered by #4:
The license may require derived works to carry a different name or version number from the original software.
There is a clause about redistribution (1), and it expressly specifies that it applies to “aggregate software distribution containing programs from several different sources”, not single, standalone works.
That is a weird way of wording it. In practice I doubt there are any OSI-approved licenses that prohibit standalone commercial distribution. If there were, you could trivially comply by just including a “hello world” program to make it an aggregate distribution.
From the RFC, it sounds like the system proposed here is more robust than what kbin has. Tags on kbin are just freeform user-defined hashtags.
The goal of the copyleft movement (which overlaps heavily with the free software movement) is to carve out an intellectual commons that can’t be re-enclosed. This commons is important for a number of reasons, including that it tends to be better for end-users of software in the sense that anti-features can’t really gain a foothold. It does not automatically solve UX issues, nor does it stop people from using the knowledge of the commons to do bad things.
Much of the strength of the intellectual commons is that it builds on itself, instead of having to re-invent the same things in a dozen or more different proprietary endeavors. If we were to start a “peace software” movement, it would be incompatible with the commons, due to the restrictions it imposes. Peace software can’t build on copyleft software, and none of the commons can build on peace software. These sorts of things were considered, and compatibility was deemed more important than pushing more specific values. This isn’t a matter of the FSF or OSI standing in the way, it’s just that “peace software” would have to go it alone.
Due to this dynamic, those that want to build “anticapitalist software” would be better served by using the GNU AGPL, rather than a license that restricts commercial use. The AGPL fixes the loophole that the GPL leaves open for network services, and should allow us to carve out a new noncommercial online ecosystem. It should even be used for non-network code, as that code may be repurposed or built upon by network services. I’m glad to see lemmy, kbin, and mastodon using it.
Sympathy lost for this attention seeker.
She was an attention seeker back on reddit
So you never had any sympathy to begin with, because aTtEnShUn SeEkEr, which is the lamest cop-out ever. Just say you hate women and get it over with.
Sounds like you’re just proving her point.
I won’t claim it’s as easy as Python, but that’s the rough area that Nim is aiming for. Going from dynamically typed to statically typed is always going to be kind of painful, but I’ve liked the language overall.
Also, we have a Nim community here, if anyone is interested: https://programming.dev/c/nim
You wouldn’t shitpost in the policeman’s helmet
Adding this one to the list of specialized instances
This meme is stealing.
Y’all have it rough. When this happens to me, it’s pretty much always:
You’re posting to /c/foss, not /c/freeofchargeandthecodeisavailableforinspection.