StrypeyApr 29

"After I joined the company, and a year of evaluating alternatives, in March 2024, we decided to move Redis to the SSPL license. This achieved our goal—AWS and Google now maintain their own fork ..."

#RowanTrollope, 2025

https://redis.io/blog/agplv3/

Huh. No wonder warning them that a relicense to SPPL would only result in a fork had no impact. It never occurred to me that getting corporate re-users to fork was the *goal*! But that kind of makes sense.

#Redis #SSPL #SourceAvailable #AGPL

Redis is now available under the AGPLv3 open source license | Redis

Developers love Redis. Unlock the full potential of the Redis database with Redis Enterprise and start building blazing fast apps.

Redis
Show threadGiacomo TesioApr 1
#OSI literally maintain a list of "approved" #opensource licenses.

They are very corporate friendly. More precisely, #BigTech friendly.
In fact, they refused #SSPL when #Amazon was among their top sponsors and adopted the much more subversive #CAL when #HoloChain was among their top sponsors.

Furthermore, I partecipated to the discussions around the #OSAID some years ago and I've never met such a corrupt environment before. They used absurd tricks to please #Google and #Meta and not include "training data" among the requirements, so that they could easily break free of #AIAct.

So, they are not just gatekeepers, but basically unregistered BigTech lobbyists.

CC: @[email protected]
Show threadGiacomo TesioMar 3
@[email protected]
non-FOSS source-available licenses, and who uses them and why
You seems only interested in licenses designed to protect corporate interests. They exist to... protect some corporate interests.

Of those you listed, #SSPL was rejected by #OSI for a single reasons: #Amazon money as a premium sponsor, but was otherwise just a slightly tweaked #AGPLv3.

Anyway, if you only care about #opensource (thus commercial) stuff, you basically listed all relevan ones.

Yet not all "non #FOSS" licenses exist to please corporate greed.

Many other licenses don't give a shit about business or "susteinability" but try a better balance between #freedom and other political values.

A well known example is #HESSLA
https://web.archive.org/web/20120204033625/http://www.hacktivismo.com/about/hessla.php

Another less known example of a license used by #hacktivists is the #HackingLicense: https://monitora-pa.it/LICENSE.txt

I use this license in all my side projects: feel free to ask me anything.

@[email protected]
OSI Corporate Sponsors & Support | Open Source Initiative

Show threadGiacomo TesioFeb 5
@[email protected]

First it's important to note that over years I realized that #OSI is just a corporate (and US-led) gatekeeper organization that serve the very interests their sponsors.
You can easily see this reading their license review mailing while keeping a tab opened on the sponsors page of the day through the #WaybackMachine.
Just as a couple of example, they rejected #MongoDB's #SSPL while #Amazon was their major sponsor and adopted CAL that was way more contentious.

The last damage that OSI did to our communities has been the #Meta dictated #OSAID (OpenSource #AI Definition) better known as #OpenWashing Definition, that superseed the #OSD and does not require training data sharing, voiding the freedom to study and welcoming toxic candies within "open source" just to avoid the #AIAct requirements.

So I don't care about OSI opinion about the #HackingLicense (or about anything else).

Having said that, you are right that its first condition forbid any use of the covered work that would limit third party access or use of it.

So basically you can't use your freedom to limit the freedom of others.

Is it still a free license?
Never asked to #RMS or #FSF, but I guess that such formal constraint makes it "not free" to their eyes.

What they miss, imho, is that freedom without communion is always going to be exploited by the strongers (under #capitalism, the rich) to oppress the weakest (everybody else, the workers, the customers, the environment...) as #LLM are showing these days.

In fact the latest version of the #HackingLicense was written in response ti #GitHub #Copilot (aka #CopyALot), after it distributed #GPLv3 code from #Quake with a wrong attribution and a permissive license.

The Hacking License is a dependency inversion: if you use data or code covered by it, anything that come out can be used under such license.
The License-review Archives

Reddit Tech VN BotDec 9

SSPL yêu cầu các tích hợp bên ngoài phải công khai khi chạy dự án. Nhiều doanh nghiệp dùng dual-licensing để ngăn lớn dùng mà không đóng góp. Bạn có ủng hộ dùng SSPL độc quyền (chỉ SSPL) để thúc đẩy hợp tác mở? Biết project nào dùng SSPL độc quyền? #SSPL #AGPL #OpenSource #NguồnMở #MởMã #Licensing #BảnQuyền #ThảoLuậnMỞnguồn

https://www.reddit.com/r/opensource/comments/1pikr0l/anyone_using_the_sspl_license_exclusively/

HoldMyTypeNov 26

in 2018, #Redis Ltd., the company managing Redis development, licensed some modules under a modified Apache 2.0 with a Commons Clause.[26][27]

In 2024, the Redis company switched the licensing for the Redis core code repository from the BSD license to dual #SSPL and proprietary licensing.
Valkey is a drop-in replacement for Redis, so the existing #NixOS Nextcloud module's Redis configuration options can be leveraged
#foss #valkey
You may hate #nixos , you may like it, but you can't ignore it

StrypeySep 22, 2025

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

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.

InfoWorld
Reddit Tech VN BotSep 21, 2025

LibreChat không thể tự host cho mục đích thương mại do giấy phép SSPL của MongoDB. Giấy phép này yêu cầu bạn phải công khai mã nguồn toàn bộ hệ thống nếu cung cấp dịch vụ dựa trên MongoDB, kể cả dùng nội bộ. Đây là hạn chế lớn cho doanh nghiệp muốn sử dụng LibreChat. #LibreChat #MongoDB #SSPL #OpenSource #SelfHosting

https://www.reddit.com/r/LocalLLaMA/comments/1nn449p/librechat_cant_be_selfhosted_in_any_commercial/

michabbbAug 25, 2025

The Story of #Valkey 🚀 🧑‍🏫

Back in early 2024, a popular #opensource project, #Redis, made a bold change: it shifted its licensing from #BSD to a more restrictive #SSPL license...

https://devdojo.com/post/tnylea/the-story-of-valkey

#devops

Show threadDominic 🇪🇺 🏳️‍🌈 🇺🇦May 8, 2025
@sogrady I don't entirely agree with the take that Redis relicensing to #AGPL means the #SSPL has lost; to me, it's more of a question of timing of Redis' move, as opposed to MongoDB's original move to the SSPL. More here: https://findthethread.blog/Licentious-Licensing/
Licentious Licensing

The riveting topic of open-source licensing is back in the news once again, this time because Salvatore Sanfilippo (aka Antirez) has rejoined Redis and pushed to re-open-source it under the AGPL license, reversing its recent move to the SSPL:

Find The Thread