@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

@landley @eruwero @maybeanerd but if your goal is to "commit asset-denial" against GAFAMs then shure, #AGPLv3 is a shure-fire method to have neither corporate users nor -sponsors…

• If you expect to be paid to maintain #FLOSS you need to find a company willing to do that, and they certainly won't do AGPL but either #openwashing with "#SourceAvailable" shit like #SSPL or choose #0BSD up to #GPLv2.

@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

@santi @mos_8502 @Wintermute_BBS well, as for #GPLv2 and license enforcement, using #copyleft as a bat to club corporations with isn't effective.

@landley still feels remorse for having started that with #BusyBox.

Not to mention #GPLv3 & #AGPLv3 really is bad unless one wants to commit "asset denial" aka. be an anticompetitive dickhead and at that point it's close to "asshole licensing" of #SSPL & #RSAL!