@alina were it so easy…

• To me #AGPLv3 is a non-starter and only beaten by source-available #OpenWashing of the #SSPL kind when it comes to "#AssholeLicensing".
• It only exists as contagious #AssetDenial licensing. But that's the maintainers choice.

Either way, a .noai file is a good indicator.

@ainmosni mine are:

No-Gos:

• Operated and/or maintained by known bad actors (i.e. DHH)
• Allowing "#AI" / #AIslop in their codebase / repo / contributions /...
• A malicious "#CoC" that enables and shields abusers and harassers or the E.S. Raymond kind ("Right to be Rude")
• Financed or supported by #GAFAMs / military/intelligence contractors.
• Using #ClownFlare / #CloudFlare or other #RogueISP|s / value removing middlemen.
• Being only source-available, open-core or otherwise doing #OpenWashing or #AssholeLicensing with ie. #SSPL!
• Absurdly wasteful tech stack (i.e. only works on #Memenetes (#Kubernetes) or #WinShit (#Windows11)…
• Extremely long list of issues with no activities.
  • #StaleBot / #StarBit and other bullshit!
  • #Paywalled access to code.

Green flags:

• Operated and/or maintained by trans*, nonbinary and/or furries.
• Clearly banning AI & AIslop if not outright sabotaging /tarpitting / hacking any AI bullshit.
• #Accessibility and #FrugalComputing are part of the goals.
• Active development
  • Active issue tracker
• Regular releases

Yellow Flags (that need context):

• Low/no activity
  • archived repo
• few releases

@bkuhn @eruwero @maybeanerd Okay, this derailment of yours it taking more than 11.000 characters that I can put in this post to cleanup whilst going anywhere and so I'd stick with @InnuendoStudios 's advice and not entertain a fruitless discussion that is a waste of time, traffic, storage and mental energy.

• Or as people in Bavaria would say: "Get lost!"

Feel free to come back once you got something productive to bring to the table, except ticking the box for "cringe Stallman-esque GPLnazi" cuz your arguments make you sound like the kind of toxic folks that make it really hard to convince someone to ever do FLOSS at all.

• The kind of people that harrass folks on GitHub for not putting their code under #GPLv3 instead of being happy that someone decided to share their code, free of charge with no expectation of monetary compensation in return!

If you want to make ends meet writing code then I'm sorry to pop that bubble but aside from #CCSS there's hardly any chance that happens.

• Projects like #Linux are the exception,from the norm and even there it's just key players/donors telling their #employees to make things work (i.e. write drivers so people can run Linux as Guest on Hyper-V)

So yeah, if you want to get paid then #AGPLv3 won't do that either!

• All #SSPL and other #AssholeLicensing did was get big corporations to hire folks to make drop-in replacements to replace stuff like #Redis with better alternatives!

As for me: I'm busy beyond #WageWork, and the reasons are literally NONE OF YOUR BUSINESS!

#thxbye #next #EOD

@maybeanerd this is nothing new.

#Google also doesn't allow #GPL in #Android (except #Linux Kernel) to the point that they explicitly ban anyone from calling it "Android" if they did so.

• On the flipside developers like @landley evidenced with #BusyBox that enforcing license terms doesn't do much than burnout IP lawyers and scare away [corporate] contributors.

That being said, if you want to monopolize your #FLOSS and make shure none of the #GAFAMs want to even look at it (but instread invest millions into building a binary-compatible, drop-in replacement) then "#AssholeLicensing" with #AGPLv3 or even #SSPL is possible and OFC you can license your work under your terms…

#NotLegalAdvice #Licensing #OpenSource #GAFAM

@innocence well, they switched to an #AssholeLicensing model, maing the reference implementation now a worse decision and put the Matrix Protocol in danger.

• Whereas @delta / #deltaChat uses #PGP/MIME as an open, #MultiVendor & #MultiProvider standard. Ditto for @monocles / #MonoclesChat & @gajim / #gajim (#XMPP+#OMEMO)…

And yes #AGPLv3 is an asshole license as it is inherently incompatible with a shitton of #IP laws and thus (oftentimes) cannot.be complied with.

• Choosing it or #SSPL is meant to #monopolize the market for commercial hosting providers that offer #ManagedHosting of #MatrixChat.

#Matrix #Chat

@jacob yes, and #OpenWashing is a real issue not just with #AssholeLicensing as seen with #Redis & others using #SSPL as a literal #AssholeLicense which are just "#SourceAvailable" instead of #OpenSource, but actual #donations.and #contributions.

• Try to convince any C-level decisionmakers to donate even 1% of the equivalent of licensing the #CCSS equivalents of the #FLOSS deployed will get one laughed at, and suggesting 10% threatened woth getting fired.

#AskMeHowIKnow…

@kotaro gramted, all of tuhe #Forks that are #BSD-licensed had way more #effort put into them.

• I just think that #AssholeLicensing is as bad as #Tivolization in terms of #OpenSource and #useability.

#SSPL is still worse than #AGPLv3, but #AGPL & #GPLv3 are just completely disregarding the legal reality of #IP and #Licensing.

• If they don't want to accept #competition, they could've chosen @creativecommons #CCBYNCSA instead, but they did not!

Needless to say if I were a #developer of it and had contributed under #BSD license I'd expect to either get my code removed entirely or the license to be kept the same.

• And now you know why I'll refuse to sign any "#ContributorLicenseAgreement" (#CLA) UNLESS I get a paid, non - term-limited position as an enployee in return…

@Nicholasr_ITSulu @nixCraft nodds in agreement and since there are so many stakeholders with opposing interests and a #copyleft license, #GAFAMs can't #enshittify or #tivolize it!

• And due to #GPLv2only eben a move to #AssholeLicensing like #AGPLv3 or #SSPL is not possible!