Fosstodon

0 posts0 participants0 posts today

Giacomo Tesio<a href="https://mastodon.online/users/larsmb" class="u-url mention" rel="nofollow noopener noreferrer" target="_blank">@larsmb@mastodon.online</a> You see, when <a href="https://snac.tesio.it?t=osi" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#OSI</a> people talk about "license proliferation" they means "<a href="https://snac.tesio.it?t=copyleft" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#copyleft</a> proliferation" that is, in fact, the proliferation of licenses that protect the work from appropriation. In fact, OSI approved over 100 mostly equivalent permissive licenses, among which some masterpiece like the <a href="https://snac.tesio.it?t=fairlicense" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#FairLicense</a> <a href="https://opensource.org/license/fair" rel="nofollow noopener noreferrer" target="_blank">https://opensource.org/license/fair</a> just because they were backed by the right corporation. They cry about license proliferation only when a <a href="https://snac.tesio.it?t=copyleft" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#copyleft</a> license conflict with the interests of their largest sponsors. Indeed the <a href="https://snac.tesio.it?t=mongodb" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#MongoDB</a> <a href="https://snac.tesio.it?t=sspl" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#SSPL</a> was not approved while <a href="https://snac.tesio.it?t=amazon" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Amazon</a> was one of the biggest OSI donor, while <a href="https://snac.tesio.it?t=cal" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#CAL</a> (that was even more "dangerous" as a copyleft according to the same arguments that got SSPL refused) was approved, because no <a href="https://snac.tesio.it?t=bigtech" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#BigTech</a> ever gave a shit about blockchain stuff (for obvious reasons). The OSI behaviour over the years shows that they cry about license proliferation only to justify their refusals. So if they don't care, you shouldn't either. Sure, conflicts among licenses exists (for example, you cannot mix code under the <a href="https://snac.tesio.it?t=hackinglicense" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#HackingLicense</a> and code under <a href="https://snac.tesio.it?t=gpl" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#GPL</a>), but right now we need first and foremost to widen the overton windows that OSI gatekeepers try desperately to keep closed. We have urgent need of new licenses that can protect the commons that we create without restricting their spread and evolution. Code is Speech. <a href="https://social.vivaldi.net/users/lproven" class="u-url mention" rel="nofollow noopener noreferrer" target="_blank">@lproven@vivaldi.net</a> <a href="https://tldr.nettime.org/users/tante" class="u-url mention" rel="nofollow noopener noreferrer" target="_blank">@tante@tldr.nettime.org</a>

kgoetzI'm disappointed that despite <a href="https://aus.social/tags/elasticsearch" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#elasticsearch</a> being <a href="https://aus.social/tags/opensource" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#opensource</a> again it seems there is no release under the open licence - only the <a href="https://aus.social/tags/SSPL" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#SSPL</a> 😢

tizmicHad a look into <a href="https://mastodon.social/tags/Serverpod" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Serverpod</a> for <a href="https://mastodon.social/tags/Flutter" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Flutter</a> <a href="https://mastodon.social/tags/Backend" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Backend</a> and thought I could build full-stack with <a href="https://mastodon.social/tags/Dart" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Dart</a> . It claims to be <a href="https://mastodon.social/tags/opensource" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#opensource</a> then looking further into its GitHub repo¹ discovering most is <a href="https://mastodon.social/tags/BSD" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#BSD</a>-3 though its main serverpod package is <a href="https://mastodon.social/tags/SSPL" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#SSPL</a>.Such things are so frustrating and exhaustive... :BlobhajShock:[1]: <a href="https://github.com/serverpod/serverpod" rel="nofollow noopener noreferrer" translate="no" target="_blank">https://github.com/serverpod/serverpod</a>

defnullI'll start: <a href="https://chaos.social/tags/Graylog" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Graylog</a> is <a href="https://chaos.social/tags/SSPL" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#SSPL</a> licensed (which is NOT a <a href="https://chaos.social/tags/FOSS" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#FOSS</a> license) and does not accept any contributions without giving up your copyright completely. They also removed a really essential feature (user groups) from the free version, but continue to offer the exact same feature with a different name behind their ridiculously expensive "Enterprise License" paywall.Graylog was <a href="https://chaos.social/tags/GPL" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#GPL</a> licensed up until 4.0 (2021).

ADMIN magazineElastic announces open source license option for <a href="https://hachyderm.io/tags/Elasticsearch" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Elasticsearch</a> <a href="https://www.admin-magazine.com/News/Open-Source-AGPL-Added-as-License-Option-for-Elasticsearch" rel="nofollow noopener noreferrer" translate="no" target="_blank">https://www.admin-magazine.com/News/Open-Source-AGPL-Added-as-License-Option-for-Elasticsearch</a> <a href="https://hachyderm.io/tags/AGPL" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#AGPL</a> <a href="https://hachyderm.io/tags/OpenSource" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#OpenSource</a> <a href="https://hachyderm.io/tags/ELv2" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#ELv2</a> <a href="https://hachyderm.io/tags/SSPL" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#SSPL</a> <a href="https://hachyderm.io/tags/OSI" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#OSI</a> <a href="https://hachyderm.io/tags/license" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#license</a> <a href="https://hachyderm.io/tags/Elastic" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Elastic</a>

Gea-Suan LinElasticsearch 打算要回來提供 AGPL 授權在「Elasticsearch is open source, again (elastic.co)」這邊看到的，Elasticsearch 目前是自家的 ELv2 以及 SSPL 授權，現在打算要提供 AGPL 授權了：「Elasticsearch is Open Source, Again」。不過應該也<a href="https://blog.gslin.org/archives/2024/08/30/11956/elasticsearch-%e6%89%93%e7%ae%97%e8%a6%81%e5%9b%9e%e4%be%86%e6%8f%90%e4%be%9b-agpl-%e6%8e%88%e6%ac%8a/" rel="nofollow noopener noreferrer" translate="no" target="_blank">https://blog.gslin.org/archives/2024/08/30/11956/elasticsearch-%e6%89%93%e7%ae%97%e8%a6%81%e5%9b%9e%e4%be%86%e6%8f%90%e4%be%9b-agpl-%e6%8e%88%e6%ac%8a/</a><a href="https://abpe.org/tags/Computer" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Computer</a> <a href="https://abpe.org/tags/Murmuring" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Murmuring</a> <a href="https://abpe.org/tags/SearchEngine" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#SearchEngine</a> <a href="https://abpe.org/tags/Software" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Software</a> <a href="https://abpe.org/tags/amazon" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#amazon</a> <a href="https://abpe.org/tags/aws" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#aws</a> <a href="https://abpe.org/tags/elastic" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#elastic</a> <a href="https://abpe.org/tags/elasticseach" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#elasticseach</a> <a href="https://abpe.org/tags/elv2" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#elv2</a> <a href="https://abpe.org/tags/license" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#license</a> <a href="https://abpe.org/tags/open" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#open</a> <a href="https://abpe.org/tags/opensearch" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#opensearch</a> <a href="https://abpe.org/tags/source" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#source</a> <a href="https://abpe.org/tags/sspl" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#sspl</a>

Strypey"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..."<a href="https://mastodon.nzoss.nz/tags/ChristineHall" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#ChristineHall</a>, 2024<a href="https://fossforce.com/2024/03/redis-goes-from-open-source-to-fauxpen-and-the-forks-have-already-started/" rel="nofollow noopener noreferrer" translate="no" target="_blank">https://fossforce.com/2024/03/redis-goes-from-open-source-to-fauxpen-and-the-forks-have-already-started/</a><a href="https://mastodon.nzoss.nz/tags/Redis" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Redis</a> <a href="https://mastodon.nzoss.nz/tags/Redict" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Redict</a> <a href="https://mastodon.nzoss.nz/tags/SourceAvailable" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#SourceAvailable</a> <a href="https://mastodon.nzoss.nz/tags/SSPL" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#SSPL</a> <a href="https://mastodon.nzoss.nz/tags/Redis" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Redis</a>

HabrКак компании зарабатывают на опенсорсе, а потом выкидывают егоФинансирование разработки Kubernetes крупнейшими спонсорами на GitHub за последние десять лет, источник Эти компании сначала при помощи сообщества разрабатывают опенсорсный софт или берут готовый, строят на нём прибыльный бизнес, зарабатывают миллионы. А потом меняют лицензию, оставляя контрибуторов, пользователей и партнёров в недоумении, что им делать. Такова бизнес-модель некоторых современных компаний вроде Redis Labs . Но ещё хуже поступают крупные облачные провайдеры. Они просто используют готовые решения, вообще не занимаясь разработкой и убивая бизнес «паразитов», описанных выше. Здесь вообще паразиты в квадрате. И весь этот террариум кормится опенсорсом.<a href="https://habr.com/ru/companies/ruvds/articles/811679/" rel="nofollow noopener noreferrer" translate="no" target="_blank">https://habr.com/ru/companies/ruvds/articles/811679/</a><a href="https://zhub.link/tags/ruvds_%D1%81%D1%82%D0%B0%D1%82%D1%8C%D0%B8" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#ruvds_статьи</a> <a href="https://zhub.link/tags/Amazon" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Amazon</a> <a href="https://zhub.link/tags/Redis" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Redis</a> <a href="https://zhub.link/tags/ElasticSearch" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#ElasticSearch</a> <a href="https://zhub.link/tags/OpenSearch" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#OpenSearch</a> <a href="https://zhub.link/tags/Redis_Enterprise_Cloud" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Redis_Enterprise_Cloud</a> <a href="https://zhub.link/tags/Apache" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Apache</a> 20 <a href="https://zhub.link/tags/Server_Side_Public_License" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Server_Side_Public_License</a> <a href="https://zhub.link/tags/SSPL" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#SSPL</a> <a href="https://zhub.link/tags/Berkeley_Software_Distribution" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Berkeley_Software_Distribution</a> <a href="https://zhub.link/tags/BSD" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#BSD</a> <a href="https://zhub.link/tags/HashiCorp" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#HashiCorp</a> <a href="https://zhub.link/tags/Terraform" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Terraform</a> <a href="https://zhub.link/tags/Mozilla_Public_License" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Mozilla_Public_License</a> <a href="https://zhub.link/tags/MPL" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#MPL</a> <a href="https://zhub.link/tags/Business_Source_License" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Business_Source_License</a> <a href="https://zhub.link/tags/BSL" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#BSL</a> <a href="https://zhub.link/tags/Redict" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Redict</a> <a href="https://zhub.link/tags/KeyDB" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#KeyDB</a> <a href="https://zhub.link/tags/Valkey" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Valkey</a> <a href="https://zhub.link/tags/OpenTofu" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#OpenTofu</a> <a href="https://zhub.link/tags/OpenTF" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#OpenTF</a>

ocdtrekkieHonestly, 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. <a href="https://arstechnica.com/?p=2015379" rel="nofollow noopener noreferrer" translate="no" target="_blank">https://arstechnica.com/?p=2015379</a><a href="https://mastodon.social/tags/AIgenerated" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#AIgenerated</a> <a href="https://mastodon.social/tags/opensource" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#opensource</a> <a href="https://mastodon.social/tags/sspl" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#sspl</a>

Dominic 🇪🇺 🏳️‍🌈 🇺🇦Having had a front-row seat for <a href="https://mastodon.social/tags/MongoDB" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#MongoDB</a>'s travails in adopting the <a href="https://mastodon.social/tags/SSPL" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#SSPL</a>, I have some thoughts on <a href="https://mastodon.social/tags/Redis" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Redis</a>' recent relicensing. Bottom line, I don't think the <a href="https://mastodon.social/tags/OSI" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#OSI</a> 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 <a href="https://mastodon.social/tags/cloud" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#cloud</a> world, even if that respects the letter of the definition. <a href="https://findthethread.blog/redis/mongodb/database/open-source/enterprise/2024/04/04/Defensive-Moves.html" rel="nofollow noopener noreferrer" translate="no" target="_blank">https://findthethread.blog/redis/mongodb/database/open-source/enterprise/2024/04/04/Defensive-Moves.html</a> <a href="https://mastodon.social/tags/foss" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#foss</a> <a href="https://mastodon.social/tags/opensource" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#opensource</a>

Habr[Перевод] В погоне за заменой Redis21 марта Redis Ltd. объявила, что, начиная с Redis 7.4, ее «in-memory data store» будет выпускаться под несвободными лицензиями с доступным (source-available) исходным кодом. Новость малоприятная, но вполне ожидаемая. Необычно в этой ситуации обилие альтернатив для тех, кто хочет остаться со свободным ПО: есть как минимум четыре варианта замены, включая уже существующий форк под названием KeyDB и недавно анонсированный проект Valkey от Linux Foundation. Вопрос теперь в том, что предпочтут пользователи, провайдеры и создатели дистрибутивов Linux.<a href="https://habr.com/ru/companies/flant/articles/804969/" rel="nofollow noopener noreferrer" translate="no" target="_blank">https://habr.com/ru/companies/flant/articles/804969/</a><a href="https://zhub.link/tags/%D1%81%D1%83%D0%B1%D0%B4" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#субд</a> <a href="https://zhub.link/tags/redis" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#redis</a> <a href="https://zhub.link/tags/keydb" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#keydb</a> <a href="https://zhub.link/tags/valkey" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#valkey</a> <a href="https://zhub.link/tags/open_source" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#open_source</a> <a href="https://zhub.link/tags/%D0%BB%D0%B8%D1%86%D0%B5%D0%BD%D0%B7%D0%B8%D0%B8" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#лицензии</a> <a href="https://zhub.link/tags/bsl" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#bsl</a> <a href="https://zhub.link/tags/sspl" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#sspl</a> <a href="https://zhub.link/tags/bsd" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#bsd</a> <a href="https://zhub.link/tags/garnet" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#garnet</a>

DocRekdNot only they managed to actually make big cloud pay for <a href="https://hachyderm.io/tags/redis" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#redis</a> development, they also shows us how: just make yourself so popular that everybody and their grandma uses it, then make yourself so hated that nobody want to work with you, like by re-releasing it under the <a href="https://hachyderm.io/tags/sspl" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#sspl</a>

Shamar<a href="https://fosstodon.org/@drewdevault" class="u-url mention" rel="nofollow noopener noreferrer" target="_blank">@drewdevault</a>To be honest, I can't see any compliance issue.You can use <a href="https://qoto.org/tags/MongoDB" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#MongoDB</a> under the <a href="https://qoto.org/tags/SSPL" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#SSPL</a>, 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".<a href="https://infosec.exchange/@varx" class="u-url mention" rel="nofollow noopener noreferrer" target="_blank">@varx</a> <a href="https://hachyderm.io/@glacials" class="u-url mention" rel="nofollow noopener noreferrer" target="_blank">@glacials</a>

Fabio ManganielloBtw I’m wondering how this license may impact use-cases where the component A released under <a class="hashtag" href="https://manganiello.social/tag/sspl" rel="nofollow noopener noreferrer" target="_blank">#SSPL</a> 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 <a class="hashtag" href="https://manganiello.social/tag/platypush" rel="nofollow noopener noreferrer" target="_blank">#Platypush</a> I use <a class="hashtag" href="https://manganiello.social/tag/redis" rel="nofollow noopener noreferrer" target="_blank">#Redis</a> 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?

tallship<a class="u-url mention" href="https://gleasonator.com/users/alex" rel="nofollow noopener noreferrer" target="_blank">@alex</a> <a class="u-url mention" href="https://fosstodon.org/@linux_mclinuxface" rel="nofollow noopener noreferrer" target="_blank">@linux_mclinuxface</a>From my PoV, it's certainly a license that's preferable to that of BSD or MIT. There's a solid reasoning behind this <a href="https://lukesmith.xyz/articles/why-i-use-the-gpl-and-not-cuck-licenses/" rel="nofollow noopener noreferrer" target="_blank">HERE</a>.After all, even Tanenbaum himself was surprised to discover that MINIX is the most ubiquitous of all operating systems:> "I guess that makes MINIX the most widely used computer operating system in the world, even more than Windows, Linux, or MacOS."The SSPL being akin to that of the AGPL avoids that sort of dreadful situation, ensuring protections for the end users that not even the GPL affords them where <a class="hashtag" href="https://public.mitra.social/collections/tags/saas" rel="nofollow noopener noreferrer" target="_blank">#SaaS</a> is concerned ;)<a class="hashtag" href="https://public.mitra.social/collections/tags/tallship" rel="nofollow noopener noreferrer" target="_blank">#tallship</a> <a class="hashtag" href="https://public.mitra.social/collections/tags/foss" rel="nofollow noopener noreferrer" target="_blank">#FOSS</a> <a class="hashtag" href="https://public.mitra.social/collections/tags/sspl" rel="nofollow noopener noreferrer" target="_blank">#SSPL</a> <a class="hashtag" href="https://public.mitra.social/collections/tags/agpl" rel="nofollow noopener noreferrer" target="_blank">#AGPL</a>⛵.

clacke: exhausted pixie dream boy 🇸🇪🇭🇰💙💛<a href="https://libranet.de/search?tag=Redis" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Redis</a> 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."<a href="https://redis.com/blog/redis-labs-modules-license-changes/" rel="nofollow noopener noreferrer" target="_blank">redis.com/blog/redis-labs-modu…</a>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)."<a href="https://redis.com/blog/redis-adopts-dual-source-available-licensing/" rel="nofollow noopener noreferrer" target="_blank">redis.com/blog/redis-adopts-du…</a>[0] <a href="https://redis.com/press/redis-labs-becomes-simply-redis/" rel="nofollow noopener noreferrer" target="_blank">redis.com/press/redis-labs-bec…</a><a href="https://libranet.de/search?tag=RedisSharedSource" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#RedisSharedSource</a> <a href="https://libranet.de/search?tag=RedisSourceAvailable" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#RedisSourceAvailable</a> <a href="https://libranet.de/search?tag=RedisProprietary" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#RedisProprietary</a> <a href="https://libranet.de/search?tag=RedisCore" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#RedisCore</a> <a href="https://libranet.de/search?tag=RedisSSPL" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#RedisSSPL</a> <a href="https://libranet.de/search?tag=RedisRSAL" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#RedisRSAL</a> <a href="https://libranet.de/search?tag=SSPL" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#SSPL</a> <a href="https://libranet.de/search?tag=RSAL" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#RSAL</a>

immibisInteresting: The <a class="hashtag" href="https://social.immibis.com/tag/osi" rel="nofollow noopener noreferrer" target="_blank">#OSI</a> disapproves <a class="hashtag" href="https://social.immibis.com/tag/sspl" rel="nofollow noopener noreferrer" target="_blank">#SSPL</a> as a license for being discriminatory against a field of endeavour. SSPL is to AGPL what AGPL is to <a class="hashtag" href="https://social.immibis.com/tag/gpl" rel="nofollow noopener noreferrer" target="_blank">#GPL</a>. The OSI is a consortium of Amazon, Google, Meta, Microsoft, etc. Those companies stand to lose a lot from SSPL software because it would require them to open-source more, exactly identical to the reason Microsoft doesn't put GPL software in Windows. Seems they have successfully embraced, extended, extinguished the meaning of "open source".

MrCopilotMy 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<a href="https://mstdn.social/tags/FOSS" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#FOSS</a> <a href="https://mstdn.social/tags/AGPL" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#AGPL</a> <a href="https://mstdn.social/tags/SSPL" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#SSPL</a> <a href="https://mstdn.social/tags/AfferoGPL" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#AfferoGPL</a> <a href="https://mstdn.social/tags/CopyLeft" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#CopyLeft</a><a href="https://sfconservancy.org/blog/2020/jan/06/copyleft-equality/" rel="nofollow noopener noreferrer" translate="no" target="_blank">https://sfconservancy.org/blog/2020/jan/06/copyleft-equality/</a>

Risotto Bias<a href="https://tech.lgbt/tags/AGPL" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#AGPL</a> vs <a href="https://tech.lgbt/tags/SSPL" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#SSPL</a>AGPL, add the requirement to include mgmt/monitoring/backup/storage/APIs/UIs such that you could run the service (e.g., other internal APIs or dashboards don't leak through in how AGPL is defined - only that library's API)or, SSPL, but get rid of the "you aren't allowed to run a competing business" requirement (e.g., SSPL isn't truly open)AGPL but more SSPL but less

Gea-Suan LinRedis 改變授權，變成非開源軟體Redis 宣佈拿掉開源授權：「Redis Adopts Dual Source-Available Licensing」，對應的 git commit 在「Change license from BSD-3 to dual RSALv2+SSPLv1 (#13157)」這邊可以看到。Starting with Redis 7.4,<a href="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/" rel="nofollow noopener noreferrer" translate="no" target="_blank">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/</a><a href="https://abpe.org/tags/Computer" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Computer</a> <a href="https://abpe.org/tags/Murmuring" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Murmuring</a> <a href="https://abpe.org/tags/Network" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Network</a> <a href="https://abpe.org/tags/Service" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Service</a> <a href="https://abpe.org/tags/Software" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Software</a> <a href="https://abpe.org/tags/cache" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#cache</a> <a href="https://abpe.org/tags/daemon" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#daemon</a> <a href="https://abpe.org/tags/layer" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#layer</a> <a href="https://abpe.org/tags/license" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#license</a> <a href="https://abpe.org/tags/open" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#open</a> <a href="https://abpe.org/tags/redis" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#redis</a> <a href="https://abpe.org/tags/source" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#source</a> <a href="https://abpe.org/tags/sspl" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#sspl</a>

Recent searches

Search options

Administered by:

Server stats:

#sspl