🌈 Social 📸 Photography 🌈

Kevin Karhan :verified:<a href="https://fosstodon.org/@innocence" class="u-url mention" rel="nofollow noopener" target="_blank">@innocence</a> well, they <a href="https://element.io/blog/sustainable-licensing-at-element-with-agpl/" rel="nofollow noopener" target="_blank">switched</a> to an <a href="https://infosec.space/tags/AssholeLicensing" class="mention hashtag" rel="nofollow noopener" target="_blank">#AssholeLicensing</a> model, maing the <a href="https://robots.net/news/new-matrix-licensing-shift-makes-building-on-the-protocol-less-appealing/" rel="nofollow noopener" target="_blank">reference implementation</a> now a <a href="https://techcrunch.com/2023/11/06/decentralized-communication-protocol-matrix-shifts-to-less-permissive-agpl-open-source-license/" rel="nofollow noopener" target="_blank">worse decision</a> and put the Matrix Protocol <a href="https://blakes.dev/posts/2023-11-06-element-closing-matrix/" rel="nofollow noopener" target="_blank">in danger</a>.<ul><li>Whereas <a href="https://chaos.social/@delta" class="u-url mention" rel="nofollow noopener" target="_blank">@delta</a> / <a href="https://infosec.space/tags/deltaChat" class="mention hashtag" rel="nofollow noopener" target="_blank">#deltaChat</a> uses <a href="https://infosec.space/tags/PGP" class="mention hashtag" rel="nofollow noopener" target="_blank">#PGP</a>/MIME as an open, <a href="https://infosec.space/tags/MultiVendor" class="mention hashtag" rel="nofollow noopener" target="_blank">#MultiVendor</a> & <a href="https://infosec.space/tags/MultiProvider" class="mention hashtag" rel="nofollow noopener" target="_blank">#MultiProvider</a> standard. Ditto for <a href="https://monocles.social/@monocles" class="u-url mention" rel="nofollow noopener" target="_blank">@monocles</a> / <a href="https://infosec.space/tags/MonoclesChat" class="mention hashtag" rel="nofollow noopener" target="_blank">#MonoclesChat</a> & <a href="https://fosstodon.org/@gajim" class="u-url mention" rel="nofollow noopener" target="_blank">@gajim</a> / <a href="https://infosec.space/tags/gajim" class="mention hashtag" rel="nofollow noopener" target="_blank">#gajim</a> (<a href="https://infosec.space/tags/XMPP" class="mention hashtag" rel="nofollow noopener" target="_blank">#XMPP</a>+<a href="https://infosec.space/tags/OMEMO" class="mention hashtag" rel="nofollow noopener" target="_blank">#OMEMO</a>)…</li></ul>And yes <a href="https://infosec.space/tags/AGPLv3" class="mention hashtag" rel="nofollow noopener" target="_blank">#AGPLv3</a> is an <a href="https://element.io/blog/tag/licensing/" rel="nofollow noopener" target="_blank">asshole license</a> as <a href="https://element.io/blog/element-to-adopt-agplv3/" rel="nofollow noopener" target="_blank">it</a> is inherently incompatible with a shitton of <a href="https://infosec.space/tags/IP" class="mention hashtag" rel="nofollow noopener" target="_blank">#IP</a> laws and thus (oftentimes) cannot.be complied with.<ul><li>Choosing it or <a href="https://infosec.space/tags/SSPL" class="mention hashtag" rel="nofollow noopener" target="_blank">#SSPL</a> is meant to <a href="https://infosec.space/tags/monopolize" class="mention hashtag" rel="nofollow noopener" target="_blank">#monopolize</a> the market for commercial hosting providers that offer <a href="https://infosec.space/tags/ManagedHosting" class="mention hashtag" rel="nofollow noopener" target="_blank">#ManagedHosting</a> of <a href="https://infosec.space/tags/MatrixChat" class="mention hashtag" rel="nofollow noopener" target="_blank">#MatrixChat</a>.</li></ul><a href="https://infosec.space/tags/Matrix" class="mention hashtag" rel="nofollow noopener" target="_blank">#Matrix</a> <a href="https://infosec.space/tags/Chat" class="mention hashtag" rel="nofollow noopener" target="_blank">#Chat</a>

Fabio ManganielloI missed <a href="https://www.theregister.com/2025/08/14/redis_redux/" rel="nofollow noopener" target="_blank">this news</a> a couple of days ago: <a class="hashtag" href="https://manganiello.social/tag/redis" rel="nofollow noopener" target="_blank">#Redis</a> is officially FOSS again, as it has backtracked from <a class="hashtag" href="https://manganiello.social/tag/sspl" rel="nofollow noopener" target="_blank">#SSPL</a> and moved to AGPL (which IMHO is what they should have adopted all along).This closes the cycle of my prediction:<ol><li>That Redis had made a terrible mistake by switching to SSPL</li><li>That the switch to SSPL would have just resulted in a fork fever that would have critically eroded their user base and reputation</li><li>That those forks would have been eventually included in standard Linux distros instead of Redis itself because of their OSI-compatible licenses, and adopted as alternatives to Redis by the cloud providers (hence invalidating the whole point of SSPL)</li><li>That Redis would have eventually backtracked and switched back to AGPL</li></ol>There’s a 5th point in my prediction that hasn’t materialized yet though: that the damage is already done and it will be hard to revert.<a href="https://www.phoronix.com/news/Fedora-Replacing-Redis-Valkey" rel="nofollow noopener" target="_blank">Fedora</a>, <a href="https://www.phoronix.com/news/Arch-Linux-Going-Valkey" rel="nofollow noopener" target="_blank">Arch</a> and <a href="https://www.theregister.com/2024/05/29/alpine_linux_320_released" rel="nofollow noopener" target="_blank">Alpine</a> have all replaced Redis with Valkey in their repos already, and Debian has opted to temporarily provide both.Many Docker configurations, cloud and on-prem deployments, Terraform templates, home servers etc. have already all migrated to Valkey.Not only, but the seismic fork allowed Valkey to implement features that have been requested in Redis for a while but not implemented because of the most complex governance of the project (like <a href="https://valkey.io/topics/RDMA/" rel="nofollow noopener" target="_blank">RDMA</a>). Plus, while Valkey guarantees parity of features <a href="https://redis.io/blog/what-is-valkey/" rel="nofollow noopener" target="_blank">as of Redis 7.2.4</a>, the mismatch of features is only supposed to increase as the hard fork diverges. This makes it even more unlikely that an enterprise software that has already migrated to Valkey takes the risk of migrating back to Redis later.Redis’ decision <a href="https://www.mongodb.com/legal/licensing/server-side-public-license" rel="nofollow noopener" target="_blank">leaves MongoDB as the only major SSPL-licensed project out there</a>. And that is also coming with its costs. For example, the Linux Foundation has just <a href="https://www.theregister.com/2025/08/25/linux_foundation_says_yes_to/" rel="nofollow noopener" target="_blank">opened its arms to Microsoft’s DocumentDB</a> rather than MongoDB because the former is released under an OSI-compatible MIT license rather than Mongo’s SSPL.The other project that still partly uses SSPL is <a href="https://www.elastic.co/blog/elastic-license-v2" rel="nofollow noopener" target="_blank">Elastic</a>. And even in that case the decision has backfired. It opened the way to AWS to <a href="https://github.com/opensearch-project/OpenSearch?tab=Apache-2.0-1-ov-file#readme" rel="nofollow noopener" target="_blank">release OpenSearch under an Apache license</a>, and grab a lot of FOSS developers to power its proprietary cloud efforts for free instead.

Kevin Karhan :verified:<a href="https://go.lema.org/santi" class="u-url mention" rel="nofollow noopener" target="_blank">@santi</a> <a href="https://studio8502.ca/@mos_8502" class="u-url mention" rel="nofollow noopener" target="_blank">@mos_8502</a> <a href="https://oldbytes.space/@Wintermute_BBS" class="u-url mention" rel="nofollow noopener" target="_blank">@Wintermute_BBS</a> well, as for <a href="https://infosec.space/tags/GPLv2" class="mention hashtag" rel="nofollow noopener" target="_blank">#GPLv2</a> and license enforcement, using <a href="https://infosec.space/tags/copyleft" class="mention hashtag" rel="nofollow noopener" target="_blank">#copyleft</a> as a bat to club corporations with isn't effective.<a href="https://mstdn.jp/@landley" class="u-url mention" rel="nofollow noopener" target="_blank">@landley</a> still feels remorse for having started that with <a href="https://infosec.space/tags/BusyBox" class="mention hashtag" rel="nofollow noopener" target="_blank">#BusyBox</a>. Not to mention <a href="https://infosec.space/tags/GPLv3" class="mention hashtag" rel="nofollow noopener" target="_blank">#GPLv3</a> & <a href="https://infosec.space/tags/AGPLv3" class="mention hashtag" rel="nofollow noopener" target="_blank">#AGPLv3</a> 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 <a href="https://infosec.space/tags/SSPL" class="mention hashtag" rel="nofollow noopener" target="_blank">#SSPL</a> & <a href="https://infosec.space/tags/RSAL" class="mention hashtag" rel="nofollow noopener" target="_blank">#RSAL</a>!

Kevin Karhan :verified:<a href="https://social.jacobian.org/@jacob" class="u-url mention" rel="nofollow noopener" target="_blank">@jacob</a> yes, and <a href="https://infosec.space/tags/OpenWashing" class="mention hashtag" rel="nofollow noopener" target="_blank">#OpenWashing</a> is a real issue not just with <a href="https://infosec.space/tags/AssholeLicensing" class="mention hashtag" rel="nofollow noopener" target="_blank">#AssholeLicensing</a> as seen with <a href="https://infosec.space/tags/Redis" class="mention hashtag" rel="nofollow noopener" target="_blank">#Redis</a> & others using <a href="https://infosec.space/tags/SSPL" class="mention hashtag" rel="nofollow noopener" target="_blank">#SSPL</a> as a literal <a href="https://infosec.space/tags/AssholeLicense" class="mention hashtag" rel="nofollow noopener" target="_blank">#AssholeLicense</a> which are just "<a href="https://infosec.space/tags/SourceAvailable" class="mention hashtag" rel="nofollow noopener" target="_blank">#SourceAvailable</a>" instead of <a href="https://infosec.space/tags/OpenSource" class="mention hashtag" rel="nofollow noopener" target="_blank">#OpenSource</a>, but actual <a href="https://infosec.space/tags/donations" class="mention hashtag" rel="nofollow noopener" target="_blank">#donations</a>.and <a href="https://infosec.space/tags/contributions" class="mention hashtag" rel="nofollow noopener" target="_blank">#contributions</a>.<ul><li>Try to convince any C-level decisionmakers to donate even 1% of the equivalent of licensing the <a href="https://infosec.space/tags/CCSS" class="mention hashtag" rel="nofollow noopener" target="_blank">#CCSS</a> equivalents of the <a href="https://infosec.space/tags/FLOSS" class="mention hashtag" rel="nofollow noopener" target="_blank">#FLOSS</a> deployed will get one laughed at, and suggesting 10% threatened woth getting fired.</li></ul><a href="https://infosec.space/tags/AskMeHowIKnow" class="mention hashtag" rel="nofollow noopener" target="_blank">#AskMeHowIKnow</a>…

Kevin Karhan :verified:<a href="https://kotaro.me/@kotaro" class="u-url mention" rel="nofollow noopener" target="_blank">@kotaro</a> gramted, all of tuhe <a href="https://infosec.space/tags/Forks" class="mention hashtag" rel="nofollow noopener" target="_blank">#Forks</a> that are <a href="https://infosec.space/tags/BSD" class="mention hashtag" rel="nofollow noopener" target="_blank">#BSD</a>-licensed had way more <a href="https://infosec.space/tags/effort" class="mention hashtag" rel="nofollow noopener" target="_blank">#effort</a> put into them.<ul><li>I just think that <a href="https://infosec.space/tags/AssholeLicensing" class="mention hashtag" rel="nofollow noopener" target="_blank">#AssholeLicensing</a> is as bad as <a href="https://infosec.space/tags/Tivolization" class="mention hashtag" rel="nofollow noopener" target="_blank">#Tivolization</a> in terms of <a href="https://infosec.space/tags/OpenSource" class="mention hashtag" rel="nofollow noopener" target="_blank">#OpenSource</a> and <a href="https://infosec.space/tags/useability" class="mention hashtag" rel="nofollow noopener" target="_blank">#useability</a>.</li></ul><a href="https://infosec.space/tags/SSPL" class="mention hashtag" rel="nofollow noopener" target="_blank">#SSPL</a> is still worse than <a href="https://infosec.space/tags/AGPLv3" class="mention hashtag" rel="nofollow noopener" target="_blank">#AGPLv3</a>, but <a href="https://infosec.space/tags/AGPL" class="mention hashtag" rel="nofollow noopener" target="_blank">#AGPL</a> & <a href="https://infosec.space/tags/GPLv3" class="mention hashtag" rel="nofollow noopener" target="_blank">#GPLv3</a> are just completely disregarding the legal reality of <a href="https://infosec.space/tags/IP" class="mention hashtag" rel="nofollow noopener" target="_blank">#IP</a> and <a href="https://infosec.space/tags/Licensing" class="mention hashtag" rel="nofollow noopener" target="_blank">#Licensing</a>.<ul><li>If they don't want to accept <a href="https://infosec.space/tags/competition" class="mention hashtag" rel="nofollow noopener" target="_blank">#competition</a>, they could've chosen <a href="https://mastodon.social/@creativecommons" class="u-url mention" rel="nofollow noopener" target="_blank">@creativecommons</a> <a href="https://infosec.space/tags/CCBYNCSA" class="mention hashtag" rel="nofollow noopener" target="_blank">#CCBYNCSA</a> instead, but they did not! </li></ul>Needless to say if I were a <a href="https://infosec.space/tags/developer" class="mention hashtag" rel="nofollow noopener" target="_blank">#developer</a> of it and had contributed under <a href="https://infosec.space/tags/BSD" class="mention hashtag" rel="nofollow noopener" target="_blank">#BSD</a> license I'd expect to either get my code removed entirely or the license to be kept the same.<ul><li>And now you know why I'll refuse to sign any "<a href="https://infosec.space/tags/ContributorLicenseAgreement" class="mention hashtag" rel="nofollow noopener" target="_blank">#ContributorLicenseAgreement</a>" (<a href="https://infosec.space/tags/CLA" class="mention hashtag" rel="nofollow noopener" target="_blank">#CLA</a>) UNLESS I get a paid, non - term-limited position as an enployee in return…</li></ul>

Björn Schießle :europa:Last year, <a href="https://social.schiessle.eu/tags/Redis" class="mention hashtag" rel="nofollow noopener" target="_blank">#Redis</a> changed its license to the <a href="https://social.schiessle.eu/tags/SSPL" class="mention hashtag" rel="nofollow noopener" target="_blank">#SSPL</a>, which is neither an <a href="https://social.schiessle.eu/tags/OpenSource" class="mention hashtag" rel="nofollow noopener" target="_blank">#OpenSource</a> nor a <a href="https://social.schiessle.eu/tags/FreeSoftware" class="mention hashtag" rel="nofollow noopener" target="_blank">#FreeSoftware</a> license. This led to <a href="https://social.schiessle.eu/tags/Valkey" class="mention hashtag" rel="nofollow noopener" target="_blank">#Valkey</a>, a fork and drop-in replacement.Now Redis has decided to go back to a real Free Software license, the <a href="https://social.schiessle.eu/tags/GNU" class="mention hashtag" rel="nofollow noopener" target="_blank">#GNU</a> <a href="https://social.schiessle.eu/tags/AGPL" class="mention hashtag" rel="nofollow noopener" target="_blank">#AGPL</a>. 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.<a href="https://redis.io/blog/agplv3/" rel="nofollow noopener" translate="no" target="_blank">https://redis.io/blog/agplv3/</a>

Kevin Karhan :verified:<a href="https://mstdn.jp/@landley" class="u-url mention" rel="nofollow noopener" target="_blank">@landley</a> <a href="https://todon.nl/@burnoutqueen" class="u-url mention" rel="nofollow noopener" target="_blank">@burnoutqueen</a> Yeah...<a href="https://infosec.space/tags/GPLv3" class="mention hashtag" rel="nofollow noopener" target="_blank">#GPLv3</a> is a desaster as it's 99% ideology and 1% license text and alongside <a href="https://infosec.space/tags/AGPLv3" class="mention hashtag" rel="nofollow noopener" target="_blank">#AGPLv3</a> completely ignores the reality of how <a href="https://infosec.space/tags/licensing" class="mention hashtag" rel="nofollow noopener" target="_blank">#licensing</a> and <a href="https://infosec.space/tags/patents" class="mention hashtag" rel="nofollow noopener" target="_blank">#patents</a> and <a href="https://infosec.space/tags/IP" class="mention hashtag" rel="nofollow noopener" target="_blank">#IP</a> works.<ul><li>Not that I like the status-quo, but we'd rather see businesses steer clear of anything GPLv2+ or GPLv3 or worse.</li></ul>And on the flipside we basically get "source available" stuff like <a href="https://infosec.space/tags/SSPL" class="mention hashtag" rel="nofollow noopener" target="_blank">#SSPL</a> which only serves as a means to commit <a href="https://infosec.space/tags/AssetDenial" class="mention hashtag" rel="nofollow noopener" target="_blank">#AssetDenial</a> and monopolize commercial offerings...<ul><li>I think <a href="https://infosec.space/tags/Linux" class="mention hashtag" rel="nofollow noopener" target="_blank">#Linux</a> being <a href="https://infosec.space/tags/GPLv2only" class="mention hashtag" rel="nofollow noopener" target="_blank">#GPLv2only</a> is a good compromise and my personal gripes with <a href="https://infosec.space/tags/FSF" class="mention hashtag" rel="nofollow noopener" target="_blank">#FSF</a> & <a href="https://infosec.space/tags/GNUtils" class="mention hashtag" rel="nofollow noopener" target="_blank">#GNUtils</a> as well as <a href="https://infosec.space/tags/GlibC" class="mention hashtag" rel="nofollow noopener" target="_blank">#GlibC</a> are something different...</li></ul>

Kevin Karhan :verified:<a href="https://mastos.online/@Nicholasr_ITSulu" class="u-url mention" rel="nofollow noopener" target="_blank">@Nicholasr_ITSulu</a> <a href="https://mastodon.social/@nixCraft" class="u-url mention" rel="nofollow noopener" target="_blank">@nixCraft</a> nodds in agreement and since there are so many stakeholders with opposing interests and a <a href="https://infosec.space/tags/copyleft" class="mention hashtag" rel="nofollow noopener" target="_blank">#copyleft</a> license, <a href="https://infosec.space/tags/GAFAMs" class="mention hashtag" rel="nofollow noopener" target="_blank">#GAFAMs</a> can't <a href="https://infosec.space/tags/enshittify" class="mention hashtag" rel="nofollow noopener" target="_blank">#enshittify</a> or <a href="https://infosec.space/tags/tivolize" class="mention hashtag" rel="nofollow noopener" target="_blank">#tivolize</a> it!<ul><li>And due to <a href="https://infosec.space/tags/GPLv2only" class="mention hashtag" rel="nofollow noopener" target="_blank">#GPLv2only</a> eben a move to <a href="https://infosec.space/tags/AssholeLicensing" class="mention hashtag" rel="nofollow noopener" target="_blank">#AssholeLicensing</a> like <a href="https://infosec.space/tags/AGPLv3" class="mention hashtag" rel="nofollow noopener" target="_blank">#AGPLv3</a> or <a href="https://infosec.space/tags/SSPL" class="mention hashtag" rel="nofollow noopener" target="_blank">#SSPL</a> is not possible!</li></ul>

Kevin Karhan :verified:<a href="https://cyberplace.social/@GossiTheDog" class="u-url mention" rel="nofollow noopener" target="_blank">@GossiTheDog</a> consider putting all your content under <a href="https://infosec.space/tags/AGPLv3" class="mention hashtag" rel="nofollow noopener" target="_blank">#AGPLv3</a>, <a href="https://infosec.space/tags/SSPL" class="mention hashtag" rel="nofollow noopener" target="_blank">#SSPL</a> or even better <a href="https://infosec.space/tags/CCBYNCND" class="mention hashtag" rel="nofollow noopener" target="_blank">#CCBYNCND</a>?

Kevin Karhan :verified:<a href="https://mastodon.social/@xerxespersrex" class="u-url mention" rel="nofollow noopener" target="_blank">@xerxespersrex</a> nodds in agreement...<ul><li>Shit like <a href="https://infosec.space/tags/SSPL" class="mention hashtag" rel="nofollow noopener" target="_blank">#SSPL</a> & <a href="https://infosec.space/tags/RSAL" class="mention hashtag" rel="nofollow noopener" target="_blank">#RSAL</a> is IMHO even <a href="https://www.youtube.com/watch?v=5v72pNaincM" rel="nofollow noopener" target="_blank">worse</a> than <a href="https://infosec.space/tags/SourceAvailable" class="mention hashtag" rel="nofollow noopener" target="_blank">#SourceAvailable</a> as it's literally "<a href="https://infosec.space/tags/AssholeLicensing" class="mention hashtag" rel="nofollow noopener" target="_blank">#AssholeLicensing</a>"...</li></ul>At least most source available products like <a href="https://infosec.space/tags/Tarsnap" class="mention hashtag" rel="nofollow noopener" target="_blank">#Tarsnap</a> are <a href="https://www.tarsnap.com/open-source.html" rel="nofollow noopener" target="_blank">honest</a> that they are not <a href="https://infosec.space/tags/OpenSource" class="mention hashtag" rel="nofollow noopener" target="_blank">#OpenSource</a>!

Kevin Karhan :verified:<a href="https://hachyderm.io/@anderseknert" class="u-url mention" rel="nofollow noopener" target="_blank">@anderseknert</a> Everyone who uses <a href="https://infosec.space/tags/AssholeLicensing" class="mention hashtag" rel="nofollow noopener" target="_blank">#AssholeLicensing</a> like <a href="https://infosec.space/tags/SSPL" class="mention hashtag" rel="nofollow noopener" target="_blank">#SSPL</a> or tries to infringe upon users' <a href="https://infosec.space/tags/FLOSS" class="mention hashtag" rel="nofollow noopener" target="_blank">#FLOSS</a> <a href="https://infosec.space/tags/Rights" class="mention hashtag" rel="nofollow noopener" target="_blank">#Rights</a> like <a href="https://infosec.space/tags/grsecurity" class="mention hashtag" rel="nofollow noopener" target="_blank">#grsecurity</a> & <a href="https://infosec.space/tags/RedHad" class="mention hashtag" rel="nofollow noopener" target="_blank">#RedHad</a> do should be banned from any professional developments and supply chains as part of the <a href="https://infosec.space/tags/RiskAssessment" class="mention hashtag" rel="nofollow noopener" target="_blank">#RiskAssessment</a> and <a href="https://infosec.space/tags/RiskAvoidance" class="mention hashtag" rel="nofollow noopener" target="_blank">#RiskAvoidance</a> in <a href="https://infosec.space/tags/DueDiligence" class="mention hashtag" rel="nofollow noopener" target="_blank">#DueDiligence</a>.<ul><li>Anything else in criminal neglect at this point...</li></ul>

Kevin Karhan :verified:One can really see <a href="https://www.youtube.com/watch?v=4hZxo96x48A&t=4m15s" rel="nofollow noopener" target="_blank">this</a> is an older video, as it misses not only <a href="https://infosec.space/tags/0BSD" class="mention hashtag" rel="nofollow noopener" target="_blank">#0BSD</a> between <a href="https://infosec.space/tags/PublicDomain" class="mention hashtag" rel="nofollow noopener" target="_blank">#PublicDomain</a> and <a href="https://infosec.space/tags/MIT" class="mention hashtag" rel="nofollow noopener" target="_blank">#MIT</a> but also <a href="https://infosec.space/tags/SSPL" class="mention hashtag" rel="nofollow noopener" target="_blank">#SSPL</a> right of <a href="https://infosec.space/tags/AGPLv3" class="mention hashtag" rel="nofollow noopener" target="_blank">#AGPLv3</a> in a tab that's right of it called "<a href="https://infosec.space/tags/AssetDenial" class="mention hashtag" rel="nofollow noopener" target="_blank">#AssetDenial</a>" or "<a href="https://infosec.space/tags/Monopolistic" class="mention hashtag" rel="nofollow noopener" target="_blank">#Monopolistic</a>" or just "<a href="https://infosec.space/tags/AssholeLicensing" class="mention hashtag" rel="nofollow noopener" target="_blank">#AssholeLicensing</a>" and a tab right of that for "<a href="https://infosec.space/tags/SourceAvailable" class="mention hashtag" rel="nofollow noopener" target="_blank">#SourceAvailable</a>" licensing, but I get ahead of myself...<a href="https://infosec.space/tags/Sarcasm" class="mention hashtag" rel="nofollow noopener" target="_blank">#Sarcasm</a> <a href="https://infosec.space/tags/OpenSource" class="mention hashtag" rel="nofollow noopener" target="_blank">#OpenSource</a> <a href="https://infosec.space/tags/Licensing" class="mention hashtag" rel="nofollow noopener" target="_blank">#Licensing</a> <a href="https://infosec.space/tags/Copyleft" class="mention hashtag" rel="nofollow noopener" target="_blank">#Copyleft</a> <a href="https://infosec.space/tags/Cipyright" class="mention hashtag" rel="nofollow noopener" target="_blank">#Cipyright</a> <a href="https://infosec.space/tags/Copywrong" class="mention hashtag" rel="nofollow noopener" target="_blank">#Copywrong</a> <a href="https://infosec.space/tags/rant" class="mention hashtag" rel="nofollow noopener" target="_blank">#rant</a> <a href="https://infosec.space/tags/vent" class="mention hashtag" rel="nofollow noopener" target="_blank">#vent</a> <a href="https://infosec.space/tags/venting" class="mention hashtag" rel="nofollow noopener" target="_blank">#venting</a>

Kevin Karhan :verified:rant, "open" "source", swearing, subtoot-ish

Kevin Karhan :verified:<a href="https://social.treehouse.systems/@marcan" class="u-url mention" rel="nofollow noopener" target="_blank">@marcan</a> <a href="https://oxytodon.com/@fuchsiii" class="u-url mention" rel="nofollow noopener" target="_blank">@fuchsiii</a> Either way, like <a href="https://mstdn.jp/@landley" class="u-url mention" rel="nofollow noopener" target="_blank">@landley</a> I did the <a href="https://infosec.space/tags/copyleft" class="mention hashtag" rel="nofollow noopener" target="_blank">#copyleft</a> experiment and those projects didn't see even remotely as much resonance or contribution as when I embraced <a href="https://infosec.space/tags/0BSD" class="mention hashtag" rel="nofollow noopener" target="_blank">#0BSD</a> as a <a href="https://infosec.space/tags/PermissiveLicense" class="mention hashtag" rel="nofollow noopener" target="_blank">#PermissiveLicense</a> (cuz <a href="https://infosec.space/tags/PublicDomain" class="mention hashtag" rel="nofollow noopener" target="_blank">#PublicDomain</a> legally doesn't exist in <a href="https://infosec.space/tags/Germany" class="mention hashtag" rel="nofollow noopener" target="_blank">#Germany</a>: One cannot renounce <a href="https://infosec.space/tags/Authorship" class="mention hashtag" rel="nofollow noopener" target="_blank">#Authorship</a> for legal reasons, otherwise <a href="https://infosec.space/tags/HateSpeech" class="mention hashtag" rel="nofollow noopener" target="_blank">#HateSpeech</a> would be unprosecute-able, so only <a href="https://infosec.space/tags/Copyright" class="mention hashtag" rel="nofollow noopener" target="_blank">#Copyright</a> lapses 70 years post-mortem of the Authors)...<ul><li>I think "<a href="https://infosec.space/tags/AssholeLicensing" class="mention hashtag" rel="nofollow noopener" target="_blank">#AssholeLicensing</a>" like <a href="https://infosec.space/tags/SSPL" class="mention hashtag" rel="nofollow noopener" target="_blank">#SSPL</a> is inherently unfree and <a href="https://infosec.space/tags/AGPLv3" class="mention hashtag" rel="nofollow noopener" target="_blank">#AGPLv3</a> is just an act of committing <a href="https://infosec.space/tags/AssetDenial" class="mention hashtag" rel="nofollow noopener" target="_blank">#AssetDenial</a> which doesn't work.</li></ul>TBH, the only way to preven <a href="https://infosec.space/tags/GAFAMs" class="mention hashtag" rel="nofollow noopener" target="_blank">#GAFAMs</a> <a href="https://youtu.be/ZzI9JE0i6Lc" rel="nofollow noopener" target="_blank">like Amazon</a> from leeching <a href="https://infosec.space/tags/FLOSS" class="mention hashtag" rel="nofollow noopener" target="_blank">#FLOSS</a> is to either make <a href="https://infosec.space/tags/CCSS" class="mention hashtag" rel="nofollow noopener" target="_blank">#CCSS</a> or offer the superior [<a href="https://infosec.space/tags/SaaS" class="mention hashtag" rel="nofollow noopener" target="_blank">#SaaS</a>] solution by ticking boxes <a href="https://infosec.space/tags/aws" class="mention hashtag" rel="nofollow noopener" target="_blank">#aws</a> can't ( i.e. due to <a href="https://infosec.space/tags/CloudAct" class="mention hashtag" rel="nofollow noopener" target="_blank">#CloudAct</a>, like <a href="https://infosec.space/tags/GDPR" class="mention hashtag" rel="nofollow noopener" target="_blank">#GDPR</a> compliance) or inherently won't hecause it's antithetical to their business ( i.e. [airgapped] <a href="https://infosec.space/tags/SelfHosting" class="mention hashtag" rel="nofollow noopener" target="_blank">#SelfHosting</a> & Support/Management Options for self-hosted systems)...<ul><li> <a href="https://infosec.space/tags/healthcare" class="mention hashtag" rel="nofollow noopener" target="_blank">#healthcare</a>-IT based startups in the <a href="https://infosec.space/tags/EU" class="mention hashtag" rel="nofollow noopener" target="_blank">#EU</a> pay Companies like <a href="https://infosec.space/tags/Telekom" class="mention hashtag" rel="nofollow noopener" target="_blank">#Telekom</a> to host their medical data because unlike <a href="https://infosec.space/tags/Amazon" class="mention hashtag" rel="nofollow noopener" target="_blank">#Amazon</a> they can and will evidently enshure their U.S. division can't leak that data to U.S. govt. agencies and if one butters them with enough money, they'll likely sign the hardest NDAs one can throw at them...</li></ul>

Kevin Karhan :verified:<a href="https://wetdry.world/@ohanamatsumae" class="u-url mention" rel="nofollow noopener" target="_blank">@ohanamatsumae</a> ain't <a href="https://infosec.space/tags/MongoDB" class="mention hashtag" rel="nofollow noopener" target="_blank">#MongoDB</a> those <a href="https://infosec.space/tags/SaaS" class="mention hashtag" rel="nofollow noopener" target="_blank">#SaaS</a>-only guys that basically use <a href="https://infosec.space/tags/AssholeLicensing" class="mention hashtag" rel="nofollow noopener" target="_blank">#AssholeLicensing</a> as per <a href="https://infosec.space/tags/SSPL" class="mention hashtag" rel="nofollow noopener" target="_blank">#SSPL</a>? <a href="https://en.wikipedia.org/wiki/MongoDB" rel="nofollow noopener" translate="no" target="_blank">https://en.wikipedia.org/wiki/MongoDB</a> <a href="https://en.wikipedia.org/wiki/Server_Side_Public_License#Licensed_software" rel="nofollow noopener" translate="no" target="_blank">https://en.wikipedia.org/wiki/Server_Side_Public_License#Licensed_software</a>To me that disqualifies them for any serious useage!

Kevin Karhan :verified:<a href="https://mastodon.social/@Elucidating" class="u-url mention" rel="nofollow noopener" target="_blank">@Elucidating</a> A license used to <a href="https://infosec.space/tags/monopolize" class="mention hashtag" rel="nofollow noopener" target="_blank">#monopolize</a> the commercial offering of a <a href="https://infosec.space/tags/Software" class="mention hashtag" rel="nofollow noopener" target="_blank">#Software</a> (<a href="https://infosec.space/tags/AsAService" class="mention hashtag" rel="nofollow noopener" target="_blank">#AsAService</a>) whilst claiming it's <a href="https://infosec.space/tags/OpenSource" class="mention hashtag" rel="nofollow noopener" target="_blank">#OpenSource</a>...Kinda like <a href="https://infosec.space/tags/SSPL" class="mention hashtag" rel="nofollow noopener" target="_blank">#SSPL</a> does and also how <a href="https://infosec.space/tags/RedHat" class="mention hashtag" rel="nofollow noopener" target="_blank">#RedHat</a> and <a href="https://infosec.space/tags/grsecurity" class="mention hashtag" rel="nofollow noopener" target="_blank">#grsecurity</a> act by basically restricting access to <a href="https://infosec.space/tags/OpenSource" class="mention hashtag" rel="nofollow noopener" target="_blank">#OpenSource</a>...

Kevin Karhan :verified:<a href="https://mastodon.social/@xeraa" class="u-url mention" rel="nofollow noopener" target="_blank">@xeraa</a> <a href="https://oxytodon.com/@fuchsiii" class="u-url mention" rel="nofollow noopener" target="_blank">@fuchsiii</a> <a href="https://mk.absturztau.be/@puniko" class="u-url mention" rel="nofollow noopener" target="_blank">@puniko</a> <a href="https://fosstodon.org/@linux_mclinuxface" class="u-url mention" rel="nofollow noopener" target="_blank">@linux_mclinuxface</a> Case in point, <a href="https://infosec.space/tags/SSPL" class="mention hashtag" rel="nofollow noopener" target="_blank">#SSPL</a> is an <a href="https://infosec.space/tags/AssholeLicense" class="mention hashtag" rel="nofollow noopener" target="_blank">#AssholeLicense</a> even more than <a href="https://infosec.space/tags/AGPLv3" class="mention hashtag" rel="nofollow noopener" target="_blank">#AGPLv3</a> because it's sole purpose is to commit <a href="https://infosec.space/tags/AssetDenial" class="mention hashtag" rel="nofollow noopener" target="_blank">#AssetDenial</a> against <a href="https://infosec.space/tags/commercial" class="mention hashtag" rel="nofollow noopener" target="_blank">#commercial</a> users & <a href="https://infosec.space/tags/hosters" class="mention hashtag" rel="nofollow noopener" target="_blank">#hosters</a>.It's worse than <a href="https://infosec.space/tags/GPLv3" class="mention hashtag" rel="nofollow noopener" target="_blank">#GPLv3</a> because that one is lunacy in terms of <a href="https://infosec.space/tags/IP" class="mention hashtag" rel="nofollow noopener" target="_blank">#IP</a> and espechally <a href="https://infosec.space/tags/Patents" class="mention hashtag" rel="nofollow noopener" target="_blank">#Patents</a> because it's solely ideologically motivated, but yeah...IMHO everything under <a href="https://en.wikipedia.org/wiki/Server_Side_Public_License" rel="nofollow noopener" target="_blank">SSPL</a> is <a href="https://infosec.space/tags/UnfreeSoftware" class="mention hashtag" rel="nofollow noopener" target="_blank">#UnfreeSoftware</a> in that it's <a href="https://infosec.space/tags/license" class="mention hashtag" rel="nofollow noopener" target="_blank">#license</a> terms are worse than a <a href="https://infosec.space/tags/SourceAvailable" class="mention hashtag" rel="nofollow noopener" target="_blank">#SourceAvailable</a> license as used by <a href="https://infosec.space/tags/Tarsnap" class="mention hashtag" rel="nofollow noopener" target="_blank">#Tarsnap</a> because they are at least honest about the why...I really hope not just <a href="https://infosec.space/tags/GAFAMs" class="mention hashtag" rel="nofollow noopener" target="_blank">#GAFAMs</a> like <a href="https://infosec.space/tags/Amazon" class="mention hashtag" rel="nofollow noopener" target="_blank">#Amazon</a> with <a href="https://infosec.space/tags/aws" class="mention hashtag" rel="nofollow noopener" target="_blank">#aws</a> forked the pre-<a href="https://infosec.space/tags/Enshittification" class="mention hashtag" rel="nofollow noopener" target="_blank">#Enshittification</a> versions under <a href="https://infosec.space/tags/BSD" class="mention hashtag" rel="nofollow noopener" target="_blank">#BSD</a> and start publishing and maintaining these.<a href="https://infosec.space/tags/Redis" class="mention hashtag" rel="nofollow noopener" target="_blank">#Redis</a>, like <a href="https://infosec.space/tags/Elastic" class="mention hashtag" rel="nofollow noopener" target="_blank">#Elastic</a> and <a href="https://infosec.space/tags/MongoDB" class="mention hashtag" rel="nofollow noopener" target="_blank">#MongoDB</a> have chosen to kick everyone in the groin out of pettyness against commercial hosters, and I hope <a href="https://mastodon.social/@Mastodon" class="u-url mention" rel="nofollow noopener" target="_blank">@Mastodon</a> & <a href="https://mastodon.social/@MastodonEngineering" class="u-url mention" rel="nofollow noopener" target="_blank">@MastodonEngineering</a> as well as <a href="https://mastodon.social/@Gargron" class="u-url mention" rel="nofollow noopener" target="_blank">@Gargron</a> work hard to replace Redis with a real <a href="https://infosec.space/tags/FLOSS" class="mention hashtag" rel="nofollow noopener" target="_blank">#FLOSS</a> alternative like <a href="https://infosec.space/tags/RabbitMQ" class="mention hashtag" rel="nofollow noopener" target="_blank">#RabbitMQ</a> or even hetter, allow disabling a caching-DB in lieu of helping setup a <a href="https://infosec.space/tags/Ramdisk" class="mention hashtag" rel="nofollow noopener" target="_blank">#Ramdisk</a> with a <a href="https://infosec.space/tags/PostgreSQL" class="mention hashtag" rel="nofollow noopener" target="_blank">#PostgreSQL</a> cache-DB on it.

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" 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" target="_blank">#Platypush</a> I use <a class="hashtag" href="https://manganiello.social/tag/redis" rel="nofollow noopener" 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?

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

Recent searches

Search options

Administered by:

Server stats:

#sspl