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/
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
@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.
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.
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.
So yeah, if you want to get paid then #AGPLv3 won't do that either!
As for me: I'm busy beyond #WageWork, and the reasons are literally NONE OF YOUR BUSINESS!
@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…
@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.
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…
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)
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/
@innocence well, they switched to an #AssholeLicensing model, maing the reference implementation now a worse decision and put the Matrix Protocol in danger.
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.
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...
@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!
@jacob yes, and #OpenWashing is a real issue not just with #AssholeLicensing as seen with #Redis & others using #SSPL as a literal #AssholeLicense which are just "#SourceAvailable" instead of #OpenSource, but actual #donations.and #contributions.
@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/
What I learned during the license switch —Creator of Redis
What I learned during the license switch —Creator of Redis #redis #opensource #sspl #fauxpen #valkeyHot 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.
@kotaro gramted, all of tuhe #Forks that are #BSD-licensed had way more #effort put into them.
#SSPL is still worse than #AGPLv3, but #AGPL & #GPLv3 are just completely disregarding the legal reality of #IP and #Licensing.
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.
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.
@brouhaha #OpenSearch has continued to grow and do well even after #Elasticsearch relicensed. In some steep heavy irony, #Graylog had moved to #OpenSearch from #Elastic, which should have been an obvious example to everyone else that SSPL is absolutely terrible for your dev community and business. (Ditto for BuSL).
Shot:
https://graylog.org/post/graylog-v4-0-licensing-sspl/
Chaser:
https://go2docs.graylog.org/1380099/planning_your_deployment/planning_your_upgrade_to_opensearch.htm
@landley @burnoutqueen Yeah...
#GPLv3 is a desaster as it's 99% ideology and 1% license text and alongside #AGPLv3 completely ignores the reality of how #licensing and #patents and #IP works.
And on the flipside we basically get "source available" stuff like #SSPL which only serves as a means to commit #AssetDenial and monopolize commercial offerings...
