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

A couple of years back, a bunch of projects started switching to proprietary Source Available licenses like #SSPL. I predicted that they would soon regret it, as they started to be replaced with forks of their own software. Feeling pretty smug reading this ...

"Redis bets big on an open source return

The company is hopeful that changing its license will allow it to better compete with the Valkey fork."

#MattAsay, May 2025

https://www.infoworld.com/article/3975620/redis-bets-big-on-an-open-source-return.html

(1/2)

#SourceAvailable #Redis #Valkey

I missed this news a couple of days ago: #Redis is officially FOSS again, as it has backtracked from #SSPL and moved to AGPL (which IMHO is what they should have adopted all along).

This closes the cycle of my prediction:

1. That Redis had made a terrible mistake by switching to SSPL
2. That the switch to SSPL would have just resulted in a fork fever that would have critically eroded their user base and reputation
3. That those forks would have been eventually included in standard Linux distros instead of Redis itself because of their OSI-compatible licenses, and adopted as alternatives to Redis by the cloud providers (hence invalidating the whole point of SSPL)
4. That Redis would have eventually backtracked and switched back to AGPL

There’s a 5th point in my prediction that hasn’t materialized yet though: that the damage is already done and it will be hard to revert.

Fedora, Arch and Alpine have all replaced Redis with Valkey in their repos already, and Debian has opted to temporarily provide both.

Many Docker configurations, cloud and on-prem deployments, Terraform templates, home servers etc. have already all migrated to Valkey.

Not only, but the seismic fork allowed Valkey to implement features that have been requested in Redis for a while but not implemented because of the most complex governance of the project (like RDMA). Plus, while Valkey guarantees parity of features as of Redis 7.2.4, the mismatch of features is only supposed to increase as the hard fork diverges. This makes it even more unlikely that an enterprise software that has already migrated to Valkey takes the risk of migrating back to Redis later.

Redis’ decision leaves MongoDB as the only major SSPL-licensed project out there. And that is also coming with its costs. For example, the Linux Foundation has just opened its arms to Microsoft’s DocumentDB rather than MongoDB because the former is released under an OSI-compatible MIT license rather than Mongo’s SSPL.

The other project that still partly uses SSPL is Elastic. And even in that case the decision has backfired. It opened the way to AWS to release OpenSearch under an Apache license, and grab a lot of FOSS developers to power its proprietary cloud efforts for free instead.

I missed this news a couple of days ago: #Redis is officially FOSS again, as it has backtracked from #SSPL and moved to AGPL (which IMHO is what they should have adopted all along).

This closes the cycle of my prediction:

1. That Redis had made a terrible mistake by switching to SSPL
2. That the switch to SSPL would have just resulted in a fork fever that would have critically eroded their user base and reputation
3. That those forks would have been eventually included in standard Linux distros instead of Redis itself because of their OSI-compatible licenses, and adopted as alternatives to Redis by the cloud providers (hence invalidating the whole point of SSPL)
4. That Redis would have eventually backtracked and switched back to AGPL

There’s a 5th point in my prediction that hasn’t materialized yet though: that the damage is already done and it will be hard to revert.

Fedora, Arch and Alpine have all replaced Redis with Valkey in their repos already, and Debian has opted to temporarily provide both.

Many Docker configurations, cloud and on-prem deployments, Terraform templates, home servers etc. have already all migrated to Valkey.

Not only, but the seismic fork allowed Valkey to implement features that have been requested in Redis for a while but not implemented because of the most complex governance of the project (like RDMA). Plus, while Valkey guarantees parity of features as of Redis 7.2.4, the mismatch of features is only supposed to increase as the hard fork diverges. This makes it even more unlikely that an enterprise software that has already migrated to Valkey takes the risk of migrating back to Redis later.

Redis’ decision leaves MongoDB as the only major SSPL-licensed project out there. And that is also coming with its costs. For example, the Linux Foundation has just opened its arms to Microsoft’s DocumentDB rather than MongoDB because the former is released under an OSI-compatible MIT license rather than Mongo’s SSPL.

The other project that still partly uses SSPL is Elastic. And even in that case the decision has backfired. It opened the way to AWS to release OpenSearch under an Apache license, and grab a lot of FOSS developers to power its proprietary cloud efforts for free instead.