#sspl

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

Not that I like the status-quo, but we'd rather see businesses steer clear of anything GPLv2+ or GPLv3 or worse.

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

I think #Linux being #GPLv2only is a good compromise and my personal gripes with #FSF & #GNUtils as well as #GlibC are something different...

@Nicholasr_ITSulu @nixCraft nodds in agreement and since there are so many stakeholders with opposing interests and a #copyleft license, #GAFAMs can't #enshittify or #tivolize it!

And due to #GPLv2only eben a move to #AssholeLicensing like #AGPLv3 or #SSPL is not possible!

@GossiTheDog consider putting all your content under #AGPLv3, #SSPL or even better #CCBYNCND?

@xerxespersrex nodds in agreement...

Shit like #SSPL & #RSAL is IMHO even worse than #SourceAvailable as it's literally "#AssholeLicensing"...

At least most source available products like #Tarsnap are honest that they are not #OpenSource!

@anderseknert Everyone who uses #AssholeLicensing like #SSPL or tries to infringe upon users' #FLOSS #Rights like #grsecurity & #RedHad do should be banned from any professional developments and supply chains as part of the #RiskAssessment and #RiskAvoidance in #DueDiligence.

Anything else in criminal neglect at this point...

One can really see this is an older video, as it misses not only #0BSD between #PublicDomain and #MIT but also #SSPL right of #AGPLv3 in a tab that's right of it called "#AssetDenial" or "#Monopolistic" or just "#AssholeLicensing" and a tab right of that for "#SourceAvailable" licensing, but I get ahead of myself...

#Sarcasm #OpenSource #Licensing #Copyleft #Cipyright #Copywrong #rant #vent #venting

@marcan @fuchsiii Either way, like @landley I did the #copyleft experiment and those projects didn't see even remotely as much resonance or contribution as when I embraced #0BSD as a #PermissiveLicense (cuz #PublicDomain legally doesn't exist in #Germany: One cannot renounce #Authorship for legal reasons, otherwise #HateSpeech would be unprosecute-able, so only #Copyright lapses 70 years post-mortem of the Authors)...

I think "#AssholeLicensing" like #SSPL is inherently unfree and #AGPLv3 is just an act of committing #AssetDenial which doesn't work.

TBH, the only way to preven #GAFAMs like Amazon from leeching #FLOSS is to either make #CCSS or offer the superior [#SaaS] solution by ticking boxes #aws can't (i.e. due to #CloudAct, like #GDPR compliance) or inherently won't hecause it's antithetical to their business (i
e. [airgapped] #SelfHosting & Support/Management Options for self-hosted systems)...

I.e. #healthcare IT in the #EU pay Companies like #Telekom to host their medical data because unlike #Amazon they can and will evidently enshure their U.S. division can't leak that data to U.S. govt. agencies.

"Last Thursday... Redis announced that it had changed the license covering its software from the open-source 3-Clause BSD License to the Redis Source Available License and the Server Side Public License, both source-available proprietary licenses..."

#ChristineHall, 2024

https://fossforce.com/2024/03/redis-goes-from-open-source-to-fauxpen-and-the-forks-have-already-started/

#Redis #Redict #SourceAvailable #SSPL #Redis

Как компании зарабатывают на опенсорсе, а потом выкидывают его

Финансирование разработки Kubernetes крупнейшими спонсорами на GitHub за последние десять лет, источник Эти компании сначала при помощи сообщества разрабатывают опенсорсный софт или берут готовый, строят на нём прибыльный бизнес, зарабатывают миллионы. А потом меняют лицензию, оставляя контрибуторов, пользователей и партнёров в недоумении, что им делать. Такова бизнес-модель некоторых современных компаний вроде Redis Labs . Но ещё хуже поступают крупные облачные провайдеры. Они просто используют готовые решения, вообще не занимаясь разработкой и убивая бизнес «паразитов», описанных выше. Здесь вообще паразиты в квадрате. И весь этот террариум кормится опенсорсом.

https://habr.com/ru/companies/ruvds/articles/811679/

#ruvds_статьи #Amazon #Redis #ElasticSearch #OpenSearch #Redis_Enterprise_Cloud #Apache 20 #Server_Side_Public_License #SSPL #Berkeley_Software_Distribution #BSD #HashiCorp #Terraform #Mozilla_Public_License #MPL #Business_Source_License #BSL #Redict #KeyDB #Valkey #OpenTofu #OpenTF

Honestly, this is not bad. Wonder if someone can put together an open source license album with an SSPL bonus track just to upset the purists. https://arstechnica.com/?p=2015379

#AIgenerated #opensource #sspl

Having had a front-row seat for #MongoDB's travails in adopting the #SSPL, I have some thoughts on #Redis' recent relicensing. Bottom line, I don't think the #OSI is doing itself or the open-source community any favors by opposing these reasonable defensive moves by vendors. The SSPL is much closer to the spirit of open-source than some of what goes on in the #cloud world, even if that respects the letter of the definition. https://findthethread.blog/redis/mongodb/database/open-source/enterprise/2024/04/04/Defensive-Moves.html #foss #opensource

[Перевод] В погоне за заменой Redis

21 марта Redis Ltd. объявила, что, начиная с Redis 7.4, ее «in-memory data store» будет выпускаться под несвободными лицензиями с доступным (source-available) исходным кодом. Новость малоприятная, но вполне ожидаемая. Необычно в этой ситуации обилие альтернатив для тех, кто хочет остаться со свободным ПО: есть как минимум четыре варианта замены, включая уже существующий форк под названием KeyDB и недавно анонсированный проект Valkey от Linux Foundation. Вопрос теперь в том, что предпочтут пользователи, провайдеры и создатели дистрибутивов Linux.

https://habr.com/ru/companies/flant/articles/804969/

#субд #redis #keydb #valkey #open_source #лицензии #bsl #sspl #bsd #garnet

в продолжении драмы c Mongo и в свете перехода Redis на лучшую открытую лицензию SSPL, лицемерные SAAS-пидарасы накатали целый сайт — ssplisbad.com
Они продолжают настаивать, что им должны давать код бесплатно и несут хуйню про "убийство опенсорса", как это всегда делают лицемерные пидарасы. Ну да, опенсорс для лицемерных пидарасов будет убит, для этого и придумана эта лицензия, бинго! #ssplisgood #sspl

@drewdevault@fosstodon.org

To be honest, I can't see any compliance issue.

You can use #MongoDB under the #SSPL, but in practice you cannot have an edge over your competitors by doing so, as they will benefit of any innovation you create to make the service more useful, easy to manage or integrate and so on.

Probably this means that you cannot drive profit from such a business, but it's not technically impossible to use it this way, just anti-economic for a cloud company.

But "anti-economic for a cloud company" is quite different from "impossible".

@varx @glacials

Btw I’m wondering how this license may impact use-cases where the component A released under #SSPL is not used directly by software B, but software B uses C (or it forks C), which in turn uses A (i.e. if the license is transitive).

An example: in #Platypush I use #Redis quite heavily - as an in-memory cache, as a pub/sub framework for inter-process communication, and as a memory queue.

Platypush is already FOSS, but it’s released under a relatively permissive MIT license. (I’ve pondered a lot over the pros/cons of MIT vs. *GPL when licensing a product like Platypush, in the future I may also considering switching to AGPL, but for now MIT is a good trade-off).

This means that people are free to copy the code of a Platypush plugin into their projects. Or use its plugins as libraries for their own integrations. Or extend it with their own plugins. Or make a fork and expose it as a service on their cloud. And the MIT license doesn’t require anybody to redistribute the full source.

But Platypush also uses Redis, which is now under SSPL.

What should company X, which has made their closed fork of Platypush with a bunch of proprietary integrations, and maybe distribute it as a service, do now? They are basically exposing a closed service that uses Redis under the hood, which violates SSPL. But the service itself is a fork of an open service released under MIT, so there’s no violation from that point of view.

In other words, does SSPL override other more permissive licenses every time a product is exposed as a service?

#Redis abandons Open Core and moves to Open Nothing.

Redis Labs 2019:

"This change has zero effect on the Redis core license, which is and will always be licensed under the 3-Clause-BSD."

redis.com/blog/redis-labs-modu…

Redis (just Redis[0]) 2024:

"Beginning today, all future versions of Redis will be released with source-available licenses. Starting with Redis 7.4, Redis will be dual-licensed under the Redis Source Available License (RSALv2) and Server Side Public License (SSPLv1). Consequently, Redis will no longer be distributed under the three-clause Berkeley Software Distribution (BSD)."

redis.com/blog/redis-adopts-du…

[0] redis.com/press/redis-labs-bec…

#RedisSharedSource #RedisSourceAvailable #RedisProprietary #RedisCore
#RedisSSPL #RedisRSAL #SSPL #RSAL

My Apologies and thanks are due to the OP of the rabbit hole that led me here, their username got lost in a fog of FUD and Corporate apologia.

but this was the escape hatch I was looking for, thanks.

Toward Copyleft Equality for All
by Bradley M. Kuhn

#FOSS #AGPL #SSPL #AfferoGPL #CopyLeft

https://sfconservancy.org/blog/2020/jan/06/copyleft-equality/

Redis 改變授權，變成非開源軟體

Redis 宣佈拿掉開源授權：「Redis Adopts Dual Source-Available Licensing」，對應的 git commit 在「Change license from BSD-3 to dual RSALv2+SSPLv1 (#13157)」這邊可以看到。

Starting with Redis 7.4,

https://blog.gslin.org/archives/2024/03/22/11710/redis-%e6%94%b9%e8%ae%8a%e6%8e%88%e6%ac%8a%ef%bc%8c%e8%ae%8a%e6%88%90%e9%9d%9e%e9%96%8b%e6%ba%90%e8%bb%9f%e9%ab%94/

#Computer #Murmuring #Network #Service #Software #cache #daemon #layer #license #open #redis #source #sspl