Thanks those who shared this satire:
https://www.mcsweeneys.net/articles/i-work-for-an-evil-company-but-outside-work-im-actually-a-really-good-person

IMO, only paragraph missing was:

> “3 hours/week, my company lets me upstream code to their favorite MIT-licensed #FOSS project! That counts. Of course, in exchange, I have to post on y-combinator how bad #copyleft is & file a #GitHub ticket telling some #AGPLv3'd project to change licenses. Oh, & all the best patches with new features stay on our internal branch…but *I* fixed all typos & misspellings upstream!”

Cc: @aral @brunobord

Thanks those who shared this satire:
https://www.mcsweeneys.net/articles/i-work-for-an-evil-company-but-outside-work-im-actually-a-really-good-person

IMO, only paragraph missing was:

> “3 hours/week, my company lets me upstream code to their favorite MIT-licensed #FOSS project! That counts. Of course, in exchange, I have to post on y-combinator how bad #copyleft is & file a #GitHub ticket telling some #AGPLv3'd project to change licenses. Oh, & all the best patches with new features stay on our internal branch…but *I* fixed all typos & misspellings upstream!”

Cc: @aral @brunobord

@amszmidt@mastodon.social

The way #LLM are voiding classic #copyleft has been experimentally demonstrated years ago, when #GitHub #Copilot was caught distributing well known #AGPLv3 code with a permissive license and wrong author attribution.

Also, technically that incident demonstrated how Copilot's model itself is a derivative work of copylefted works: if a lossy compression of copyrighted material is still subject to authors' #copyright, encoding such compression as arrays of floats that can be executed by virtual processors with a dedicated architecture (so called "inference" engines) does't change its nature of derivative work. Similarly violating copyrights of millions of authors at once doesn't free you of such rights.
That's basically why #OpenAI and friends are so scared by current lack of sustainable business models for their #LLM: they need money to keep Judges away.
But anyway I still have to find a single person that debate with technical competence and in good faith the derivative nature of LLMs from the text corpora compressed in their models.

As for the Hacking License not being a Free Software license, it's debatable after a careful read since the only thing you cannot do with the software is to prevent others from enjoining the same freedom it grants you.

Yet I've never claimed it is Free Software because, sadly, I'm forced to move beyond Free Software by its own limit.

OTOH I'm proud that it's not an #OpenSource license as I'll never submit it to #OSI corrupted #gatekeepers.¹

As for #FLOSS, it's a term designed to confuse free software values with corporate propaganda while marginalizing hackers: its a leaking abstraction designed to fool developers and exploit their naive groupthinking. Having been fooled myself. Never again. 😉

____

¹ The way OSI tried to #openwash the #OSAID, with an over complicated process that doubled #Meta's lobbyists' votes to exclude training data from the requirements confirmed my opinion about them.

@doctormo@floss.social

@amszmidt@mastodon.social

The way #LLM are voiding classic #copyleft has been experimentally demonstrated years ago, when #GitHub #Copilot was caught distributing well known #AGPLv3 code with a permissive license and wrong author attribution.

Also, technically that incident demonstrated how Copilot's model itself is a derivative work of copylefted works: if a lossy compression of copyrighted material is still subject to authors' #copyright, encoding such compression as arrays of floats that can be executed by virtual processors with a dedicated architecture (so called "inference" engines) does't change its nature of derivative work. Similarly violating copyrights of millions of authors at once doesn't free you of such rights.
That's basically why #OpenAI and friends are so scared by current lack of sustainable business models for their #LLM: they need money to keep Judges away.
But anyway I still have to find a single person that debate with technical competence and in good faith the derivative nature of LLMs from the text corpora compressed in their models.

As for the Hacking License not being a Free Software license, it's debatable after a careful read since the only thing you cannot do with the software is to prevent others from enjoining the same freedom it grants you.

Yet I've never claimed it is Free Software because, sadly, I'm forced to move beyond Free Software by its own limit.

OTOH I'm proud that it's not an #OpenSource license as I'll never submit it to #OSI corrupted #gatekeepers.¹

As for #FLOSS, it's a term designed to confuse free software values with corporate propaganda while marginalizing hackers: its a leaking abstraction designed to fool developers and exploit their naive groupthinking. Having been fooled myself. Never again. 😉

____

¹ The way OSI tried to #openwash the #OSAID, with an over complicated process that doubled #Meta's lobbyists' votes to exclude training data from the requirements confirmed my opinion about them.

@doctormo@floss.social

Generally speaking, #copyleft codebases interact best with small-to-medium business ventures rather than advancing the interests of megacorps.

#Mastodon is an obvious example — which has a growing ecosystem of small businesses (like @mastohost) & nonprofit entities working in collaboration.

We see similar in the #GPL'd #Drupal community.

When megacorps get involved with copylefted projects, it's usually to exploit rather than engage — hence the widespread #GPLv2 violations on #Linux.
#AGPLv3

Generally speaking, #copyleft codebases interact best with small-to-medium business ventures rather than advancing the interests of megacorps.

#Mastodon is an obvious example — which has a growing ecosystem of small businesses (like @mastohost) & nonprofit entities working in collaboration.

We see similar in the #GPL'd #Drupal community.

When megacorps get involved with copylefted projects, it's usually to exploit rather than engage — hence the widespread #GPLv2 violations on #Linux.
#AGPLv3

@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

@bkuhn @mastohost @eruwero @maybeanerd well, I merely refer to the fact that most.companies I've had to deal with won't touch #AGPLv3 because it's provisions are incompatible with #IP laws and #patents as well as #licensing.

• #GPLv3 and it's issues and the general enforcement problems got covered my @landley ....

🤔…Fascinating that @kkarhan claims sponsors & corporate contributors will “never get involved” with an #AGPLv3 codebase by *using* an AGPLv3 codebase — namely #Mastodon — to make these false claims.

Plenty of people getting sponsored & are starting businesses around Mastodon (including @mastohost, which I use), & Donald Trump himself — Truth Social is a (now) AGPLv3 compliant fork of Mastodon.

Perhaps Google+ would be a replacement for Mastodon you'd prefer?

Cc: @eruwero @maybeanerd

@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.