Petit rappel libriste que l'AGPL et les licences libres et open source sont inefficaces contre les états ne respectant pas le droit international comme Israël ni contre l'usage de votre code pour organiser le mouvement nazi comme Trump.

TM SGNL, the obscure unofficial Signal app Mike Waltz uses to text with Trump officials https://micahflee.com/tm-sgnl-the-obscure-unofficial-signal-app-mike-waltz-uses-to-text-with-trump-officials/

Mastodon’s Founder Says Trump’s New Social Network Is Just Mastodon https://www.vice.com/en/article/truth-social-is-mastodon-trump/

#foss #technologie #agpl #mastodon #signal #libre

Unpopular opinion: If you do not perform all the obligations of a license like the AGPLv3 yourself, and would gladly and fearlessly use software produced by someone else exclusively available under that license as part of your software service, you shouln’t offer your software under that license.

#FOSS #OSS #FreeSoftware #OpenSource #SoftwareFreedom #AGPL #AGPLv3 #SaaS

So #Redis changed its license again and returned to #FOSS by adopting #AGPL. I'm curious to see how it will go against #valkey. Is it too late to regain credibility in the community? Maybe a possible future for other projects that share the same destiny. There was once upon a time Hashicorp...

Hot Take: The misinformation about the SSPL needs to stop.

If you disagree with the SSPL, that's fine.

But if you argue against what you think what the SSPL is, rather than what it actually is, you are actively harming the FOSS community.

The SSPL is based on the AGPL (Edit: It's actually based on the GPLv3). MongoDB (the company) has a nice little difference PDF that you can read. https://webassets.mongodb.com/_com_assets/legal/SSPL-compared-to-AGPL.pdf

The OSI says the SSPL is not Open Source. I understand their reasoning, and that's their prerogative. But I think this call was more harmful than it was beneficial.

The FSF said they'd look into the SSPL and make a comment, it's been a long while and they've been silent on the matter. Claims that the SSPL is not a Free Software license are false. Note that I'm also not making a claim that the SSPL is a Free Software license, because that equally lacks evidence.

I appreciate that people *really* do not like the requirements for Section 13. That's fine, if that's your beef with the SSPL, then say that instead of spreading falsities. I *really* don't like it when software fails to provide Freedom 3. I prefer copyleft licenses over permissive licenses. Some people prefer licenses that allow people to close the source later, I disagree with that.

Can we please just argue against realities, instead of fantasies? Thank you.

#FOSS #OpenSource #FreeSoftware #GPL #AGPL #SSPL

Redis, which last year ceased licensing its code with the open source BSD-3 licence in favour of "source available" SSPL licences, which are not recognised by the Open Source Institute (OSI), has returned to the fold.

https://www.computing.co.uk/news/2025/open-source/redis-returns-to-the-open-source-fold

#opensource #redis #agpl #technews #database #nosql

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

Interesting to see that Redis is open source again, AGPL. Much better fit for the project.

#redis #agpl #opensource

Redis 8正式リリース、AGPLのもと再びオープンソースとして利用可能に
https://gihyo.jp/article/2025/05/redis-8?utm_source=feed

#gihyo #技術評論社 #gihyo_jp #Redis #KVS #AGPL #NoSQL

https://blog.gslin.org/archives/2025/05/02/12380/redis-%e5%ae%a3%e4%bd%88%e5%b0%87%e4%bd%bf%e7%94%a8-agplv3-ssplv1-rsalv2/

Redis 宣佈將使用 AGPLv3/SSPLv1/RSALv2

#agpl #agplv3 #cache #license #open #redis #rsal #rsalv2 #software #source #sspl #ssplv1 #valkey

Last year, #Redis changed its license to the #SSPL, which is neither an #OpenSource nor a #FreeSoftware license. This led to #Valkey, a fork and drop-in replacement.

Now Redis has decided to go back to a real Free Software license, the #GNU #AGPL. This is a great decision, although it remains to be seen if they reverted their decision in time, or if it is too late and the community will continue with Valkey and not look back.

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

#Redis 8 is now #AGPL.

https://antirez.com/news/151

This is good news, but I don't know what the implications are for Valkey et al.

You know, I literally was just going back and forth between redis and valkey the other day and settled on Redis. I don't think the SSPL preserves software freedom, but it seemed better than Amazon and Google's BSD-licensed stuff, which would be a walled-off, "take what you get or fork off" sort of environment. I genuinely had the thought "I wonder why the don't just go with the AGPL, that would be toxic enough to the likes of Amazon and Google".

...whaddayaknow.

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

I probably had this mental conversation with myself at the same time as these people were working on the final draft of this blog post.

wild.

Edit: also, releasing on #MayDay? 🔥

RE: https://fosstodon.org/@atoponce/114433970981720210

#redis #openSource #freeSoftware #agpl

And if you were hoping that the #copyleft from #AGPL would somehow prevent #Redis from relicensing back to SSPL or worse, you might want to read their #CLA, while remembering what #Hashicorp did:

https://github.com/redis/redis/blob/unstable/CONTRIBUTING.md

#redis

I should note that although #AGPL is #opensource, it is a different license than the #BSD it had used before, and that means that #Redis can use #Valkey code but Valkey cannot use the new Redis code (under the current licensing). The move seems to be clearly about trying to undermine Valkey, which just speaks to how much ground they have lost to make such a move.

#Redis is #FreeSoftware again; specifically #AGPL !

https://redis.io/blog/agplv3/
https://antirez.com/news/151

Unclear what this means for the forks Valkey (BSD-3-Clause) and Redict (LGPL).

#copyleft

https://antirez.com/news/151

#Redis #AGPL #FOSS

Redis returns to open source under AGPLv3, moving away from SSPL. Redis 8 is now GA with new features and performance boosts.

https://antirez.com/news/151

#Redis #OpenSource #AGPL #DevOps

#Redis moves back to #AGPL

🤡

https://www.theregister.com/2025/05/01/redis_returns_to_open_source/

Redis 8 has been released, and it’s open source again under the AGPL v3 license.

https://antirez.com/news/151

https://redis.io/blog/redis-8-ga/

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

#redis #agpl #agplv3 #opensource

🎉BREAKING: #Redis is #open #source again! 🎉 After a lengthy and thrilling #debate (with all the #drama of a soap opera), they ditched the SSPL like a bad habit. 🚮 Thank goodness for those who believed in the power of #AGPL, because who doesn't love a #license debate with their morning coffee? ☕🙄
https://antirez.com/news/151 #Coffee #HackerNews #ngated