shakedown.social is one of the many independent Mastodon servers you can use to participate in the fediverse.
A community for live music fans with roots in the jam scene. Shakedown Social is run by a team of volunteers (led by @clifff and @sethadam1) and funded by donations.

Administered by:

Server stats:

254
active users

#assholelicensing

0 posts0 participants0 posts today
Kevin Karhan :verified:<p><span class="h-card" translate="no"><a href="https://social.veraciousnetwork.com/@cdp1337" class="u-url mention" rel="nofollow noopener" target="_blank">@<span>cdp1337</span></a></span> there's a reason it got forked before they switched to <em>"<a href="https://infosec.space/tags/AssholeLicensing" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>AssholeLicensing</span></a>"</em></p>
Kevin Karhan :verified:<p><span class="h-card" translate="no"><a href="https://social.jacobian.org/@jacob" class="u-url mention" rel="nofollow noopener" target="_blank">@<span>jacob</span></a></span> <em>yes</em>, and <em><a href="https://infosec.space/tags/OpenWashing" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>OpenWashing</span></a></em> is a real issue not just with <a href="https://infosec.space/tags/AssholeLicensing" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>AssholeLicensing</span></a> as seen with <a href="https://infosec.space/tags/Redis" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>Redis</span></a> &amp; others using <a href="https://infosec.space/tags/SSPL" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>SSPL</span></a> as a literal <a href="https://infosec.space/tags/AssholeLicense" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>AssholeLicense</span></a> which are just <em>"<a href="https://infosec.space/tags/SourceAvailable" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>SourceAvailable</span></a>"</em> instead of <a href="https://infosec.space/tags/OpenSource" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>OpenSource</span></a>, but actual <a href="https://infosec.space/tags/donations" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>donations</span></a>.and <a href="https://infosec.space/tags/contributions" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>contributions</span></a>.</p><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">#<span>CCSS</span></a> equivalents of the <a href="https://infosec.space/tags/FLOSS" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>FLOSS</span></a> deployed will get one laughed at, and suggesting 10% threatened woth getting fired.</li></ul><p><a href="https://infosec.space/tags/AskMeHowIKnow" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>AskMeHowIKnow</span></a>…</p>
Kevin Karhan :verified:<p><span class="h-card" translate="no"><a href="https://kotaro.me/@kotaro" class="u-url mention" rel="nofollow noopener" target="_blank">@<span>kotaro</span></a></span> gramted, all of tuhe <a href="https://infosec.space/tags/Forks" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>Forks</span></a> that are <a href="https://infosec.space/tags/BSD" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>BSD</span></a>-licensed had way more <a href="https://infosec.space/tags/effort" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>effort</span></a> put into them.</p><ul><li>I just think that <a href="https://infosec.space/tags/AssholeLicensing" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>AssholeLicensing</span></a> is as bad as <a href="https://infosec.space/tags/Tivolization" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>Tivolization</span></a> in terms of <a href="https://infosec.space/tags/OpenSource" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>OpenSource</span></a> and <a href="https://infosec.space/tags/useability" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>useability</span></a>.</li></ul><p><a href="https://infosec.space/tags/SSPL" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>SSPL</span></a> is still worse than <a href="https://infosec.space/tags/AGPLv3" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>AGPLv3</span></a>, but <a href="https://infosec.space/tags/AGPL" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>AGPL</span></a> &amp; <a href="https://infosec.space/tags/GPLv3" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>GPLv3</span></a> are just completely disregarding the legal reality of <a href="https://infosec.space/tags/IP" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>IP</span></a> and <a href="https://infosec.space/tags/Licensing" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>Licensing</span></a>.</p><ul><li>If they don't want to accept <a href="https://infosec.space/tags/competition" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>competition</span></a>, they could've chosen <span class="h-card" translate="no"><a href="https://mastodon.social/@creativecommons" class="u-url mention" rel="nofollow noopener" target="_blank">@<span>creativecommons</span></a></span> <a href="https://infosec.space/tags/CCBYNCSA" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>CCBYNCSA</span></a> instead, but they did not! </li></ul><p>Needless to say if I were a <a href="https://infosec.space/tags/developer" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>developer</span></a> of it and had contributed under <a href="https://infosec.space/tags/BSD" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>BSD</span></a> license I'd expect to either get my code removed entirely or the license to be kept the same.</p><ul><li>And now you know why I'll refuse to sign any <em>"<a href="https://infosec.space/tags/ContributorLicenseAgreement" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>ContributorLicenseAgreement</span></a>"</em> (<a href="https://infosec.space/tags/CLA" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>CLA</span></a>) <em>UNLESS</em> I get a paid, non - term-limited position as an enployee in return…</li></ul>
Kevin Karhan :verified:<p><span class="h-card" translate="no"><a href="https://mastos.online/@Nicholasr_ITSulu" class="u-url mention" rel="nofollow noopener" target="_blank">@<span>Nicholasr_ITSulu</span></a></span> <span class="h-card" translate="no"><a href="https://mastodon.social/@nixCraft" class="u-url mention" rel="nofollow noopener" target="_blank">@<span>nixCraft</span></a></span> <em>nodds in agreement</em> and since there are so many stakeholders with opposing interests <em>and</em> a <a href="https://infosec.space/tags/copyleft" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>copyleft</span></a> license, <a href="https://infosec.space/tags/GAFAMs" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>GAFAMs</span></a> can't <a href="https://infosec.space/tags/enshittify" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>enshittify</span></a> or <a href="https://infosec.space/tags/tivolize" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>tivolize</span></a> it!</p><ul><li>And due to <a href="https://infosec.space/tags/GPLv2only" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>GPLv2only</span></a> eben a move to <a href="https://infosec.space/tags/AssholeLicensing" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>AssholeLicensing</span></a> like <a href="https://infosec.space/tags/AGPLv3" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>AGPLv3</span></a> or <a href="https://infosec.space/tags/SSPL" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>SSPL</span></a> is not possible!</li></ul>
Kevin Karhan :verified:<p><span class="h-card" translate="no"><a href="https://mastodon.social/@xerxespersrex" class="u-url mention" rel="nofollow noopener" target="_blank">@<span>xerxespersrex</span></a></span> <em>nodds in agreement</em>...</p><ul><li>Shit like <a href="https://infosec.space/tags/SSPL" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>SSPL</span></a> &amp; <a href="https://infosec.space/tags/RSAL" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>RSAL</span></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">#<span>SourceAvailable</span></a> as it's literally <em>"<a href="https://infosec.space/tags/AssholeLicensing" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>AssholeLicensing</span></a>"</em>...</li></ul><p>At least most <em>source available</em> products like <a href="https://infosec.space/tags/Tarsnap" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>Tarsnap</span></a> are <a href="https://www.tarsnap.com/open-source.html" rel="nofollow noopener" target="_blank">honest</a> that they <em>are not <a href="https://infosec.space/tags/OpenSource" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>OpenSource</span></a></em>!</p>
Kevin Karhan :verified:<p><span class="h-card" translate="no"><a href="https://hachyderm.io/@anderseknert" class="u-url mention" rel="nofollow noopener" target="_blank">@<span>anderseknert</span></a></span> Everyone who uses <a href="https://infosec.space/tags/AssholeLicensing" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>AssholeLicensing</span></a> like <a href="https://infosec.space/tags/SSPL" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>SSPL</span></a> or tries to infringe upon users' <a href="https://infosec.space/tags/FLOSS" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>FLOSS</span></a> <a href="https://infosec.space/tags/Rights" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>Rights</span></a> like <a href="https://infosec.space/tags/grsecurity" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>grsecurity</span></a> &amp; <a href="https://infosec.space/tags/RedHad" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>RedHad</span></a> do should be banned from any professional developments and supply chains as part of the <em><a href="https://infosec.space/tags/RiskAssessment" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>RiskAssessment</span></a> and <a href="https://infosec.space/tags/RiskAvoidance" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>RiskAvoidance</span></a></em> in <a href="https://infosec.space/tags/DueDiligence" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>DueDiligence</span></a>.</p><ul><li>Anything else in criminal neglect at this point...</li></ul>
Kevin Karhan :verified:<p>One can really see <a href="https://www.youtube.com/watch?v=4hZxo96x48A&amp;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">#<span>0BSD</span></a> between <a href="https://infosec.space/tags/PublicDomain" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>PublicDomain</span></a> and <a href="https://infosec.space/tags/MIT" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>MIT</span></a> but also <a href="https://infosec.space/tags/SSPL" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>SSPL</span></a> right of <a href="https://infosec.space/tags/AGPLv3" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>AGPLv3</span></a> in a tab that's right of it called <em>"<a href="https://infosec.space/tags/AssetDenial" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>AssetDenial</span></a>"</em> or <em>"<a href="https://infosec.space/tags/Monopolistic" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>Monopolistic</span></a>"</em> or just <em>"<a href="https://infosec.space/tags/AssholeLicensing" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>AssholeLicensing</span></a>"</em> and a tab right of that for <em>"<a href="https://infosec.space/tags/SourceAvailable" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>SourceAvailable</span></a>"</em> licensing, but I get ahead of myself...</p><p><a href="https://infosec.space/tags/Sarcasm" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>Sarcasm</span></a> <a href="https://infosec.space/tags/OpenSource" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>OpenSource</span></a> <a href="https://infosec.space/tags/Licensing" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>Licensing</span></a> <a href="https://infosec.space/tags/Copyleft" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>Copyleft</span></a> <a href="https://infosec.space/tags/Cipyright" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>Cipyright</span></a> <a href="https://infosec.space/tags/Copywrong" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>Copywrong</span></a> <a href="https://infosec.space/tags/rant" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>rant</span></a> <a href="https://infosec.space/tags/vent" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>vent</span></a> <a href="https://infosec.space/tags/venting" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>venting</span></a></p>
Kevin Karhan :verified:<p><span class="h-card" translate="no"><a href="https://fosstodon.org/@carlwgeorge" class="u-url mention" rel="nofollow noopener" target="_blank">@<span>carlwgeorge</span></a></span> <span class="h-card" translate="no"><a href="https://mastodon.bsd.cafe/@vermaden" class="u-url mention" rel="nofollow noopener" target="_blank">@<span>vermaden</span></a></span> <span class="h-card" translate="no"><a href="https://fosstodon.org/@samurro" class="u-url mention" rel="nofollow noopener" target="_blank">@<span>samurro</span></a></span> <span class="h-card" translate="no"><a href="https://mastodon.bsd.cafe/@tara" class="u-url mention" rel="nofollow noopener" target="_blank">@<span>tara</span></a></span> <span class="h-card" translate="no"><a href="https://linuxmom.net/@vkc" class="u-url mention" rel="nofollow noopener" target="_blank">@<span>vkc</span></a></span> <span class="h-card" translate="no"><a href="https://mstdn.social/@BrodieOnLinux" class="u-url mention" rel="nofollow noopener" target="_blank">@<span>BrodieOnLinux</span></a></span> TBH, being just marginally better than <a href="https://infosec.space/tags/Oracle" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>Oracle</span></a> and <a href="https://infosec.space/tags/Microsoft" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>Microsoft</span></a> is the only reason I'd use <a href="https://infosec.space/tags/RHEL" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>RHEL</span></a> over <a href="https://infosec.space/tags/Solaris" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>Solaris</span></a> or god forbid <a href="https://infosec.space/tags/Windows" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>Windows</span></a>, tho I'm glad <a href="https://infosec.space/tags/Linux" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>Linux</span></a> isn't controlled entirely by <a href="https://infosec.space/tags/RedHat" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>RedHat</span></a> and that I can use <a href="https://infosec.space/tags/OpenSUSE" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>OpenSUSE</span></a> and <a href="https://infosec.space/tags/UbuntuLTS" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>UbuntuLTS</span></a> and their parent companies didn't gave me or my (fmr.) clients/employers the finger... </p><p>But hey, go keep <a href="https://fosstodon.org/@carlwgeorge/113066753513420985" rel="nofollow noopener" target="_blank">lying to yourself</a> with the <em>corporate propaganda</em> of <a href="https://fosstodon.org/@carlwgeorge/113066740483764069" rel="nofollow noopener" target="_blank">open source sustainability</a> because if you think that <a href="https://infosec.space/tags/FLOSS" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>FLOSS</span></a> needs to be <a href="https://infosec.space/tags/profitable" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>profitable</span></a> you haven't understood why people choose <a href="https://infosec.space/tags/Copyleft" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>Copyleft</span></a> licenses like the <a href="https://infosec.space/tags/GPLv2" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>GPLv2</span></a> and espechally <a href="https://infosec.space/tags/GPLv3" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>GPLv3</span></a> and how Red Hat is providing arguments to push for <em>"<a href="https://infosec.space/tags/AssholeLicensing" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>AssholeLicensing</span></a>"</em> a la <a href="https://infosec.space/tags/AGPLv3" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>AGPLv3</span></a>.</p><p>Your <a href="https://fosstodon.org/@carlwgeorge/113066777245682297" rel="nofollow noopener" target="_blank">dismissals</a> of criticism are childish and your way to flood my notifications with bs replies just to then flee the discussion like a coward is a really bad way to <a href="https://fosstodon.org/@carlwgeorge/113066796196131707" rel="nofollow noopener" target="_blank">pull rank</a>.</p><ul><li>This behaviour reminds me of <em>"channers"</em> that refexively reply <em>"You have an anime pfp, your opinion doesn't matter!"</em> as if that's a way to engage with potential clients!</li></ul><p>Just because I'm not a CxO doesn't mean I know how to (dis-)recommend suppliers and underpin that with past experiences, as clients/employers trust in my judgement.</p>
Kevin Karhan :verified:<p><span class="h-card" translate="no"><a href="https://social.treehouse.systems/@marcan" class="u-url mention" rel="nofollow noopener" target="_blank">@<span>marcan</span></a></span> <span class="h-card" translate="no"><a href="https://oxytodon.com/@fuchsiii" class="u-url mention" rel="nofollow noopener" target="_blank">@<span>fuchsiii</span></a></span> Either way, like <span class="h-card" translate="no"><a href="https://mstdn.jp/@landley" class="u-url mention" rel="nofollow noopener" target="_blank">@<span>landley</span></a></span> I did the <a href="https://infosec.space/tags/copyleft" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>copyleft</span></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">#<span>0BSD</span></a> as a <a href="https://infosec.space/tags/PermissiveLicense" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>PermissiveLicense</span></a> (cuz <a href="https://infosec.space/tags/PublicDomain" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>PublicDomain</span></a> legally doesn't exist in <a href="https://infosec.space/tags/Germany" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>Germany</span></a>: One cannot renounce <a href="https://infosec.space/tags/Authorship" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>Authorship</span></a> for legal reasons, otherwise <a href="https://infosec.space/tags/HateSpeech" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>HateSpeech</span></a> would be unprosecute-able, so only <a href="https://infosec.space/tags/Copyright" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>Copyright</span></a> lapses 70 years post-mortem of the Authors)...</p><ul><li>I think <em>"<a href="https://infosec.space/tags/AssholeLicensing" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>AssholeLicensing</span></a>"</em> like <a href="https://infosec.space/tags/SSPL" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>SSPL</span></a> is inherently unfree and <a href="https://infosec.space/tags/AGPLv3" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>AGPLv3</span></a> is just an act of <em>committing <a href="https://infosec.space/tags/AssetDenial" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>AssetDenial</span></a></em> which doesn't work.</li></ul><p>TBH, the only way to preven <a href="https://infosec.space/tags/GAFAMs" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>GAFAMs</span></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">#<span>FLOSS</span></a> is to either make <a href="https://infosec.space/tags/CCSS" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>CCSS</span></a> or offer the <em>superior [<a href="https://infosec.space/tags/SaaS" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>SaaS</span></a>] solution</em> by ticking boxes <a href="https://infosec.space/tags/aws" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>aws</span></a> can't ( i.e. due to <a href="https://infosec.space/tags/CloudAct" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>CloudAct</span></a>, like <a href="https://infosec.space/tags/GDPR" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>GDPR</span></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">#<span>SelfHosting</span></a> &amp; Support/Management Options for self-hosted systems)...</p><ul><li> <a href="https://infosec.space/tags/healthcare" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>healthcare</span></a>-IT based startups in the <a href="https://infosec.space/tags/EU" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>EU</span></a> pay Companies like <a href="https://infosec.space/tags/Telekom" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>Telekom</span></a> to host their medical data because unlike <a href="https://infosec.space/tags/Amazon" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>Amazon</span></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:<p><span class="h-card" translate="no"><a href="https://groupe-tazor.com/@Yuki" class="u-url mention" rel="nofollow noopener" target="_blank">@<span>Yuki</span></a></span> I sincerely hope everyone's gonna fork <a href="https://infosec.space/tags/Redis" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>Redis</span></a> before they changed to <a href="https://infosec.space/tags/AssholeLicensing" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>AssholeLicensing</span></a> with the <a href="https://infosec.space/tags/SSPL" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>SSPL</span></a> which is a <a href="https://infosec.space/tags/NonFree" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>NonFree</span></a> <a href="https://infosec.space/tags/AssholeLicense" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>AssholeLicense</span></a>. </p><p>This is worse than <a href="https://infosec.space/tags/Copyleft" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>Copyleft</span></a> but just blatant <em>Asset Denial</em> because *"We WaNt AmAzOn To PaY uS!" kinda bs...</p><p>If you want to make money with <a href="https://infosec.space/tags/FLOSS" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>FLOSS</span></a>, provide some good product and make it attractive to <a href="https://infosec.space/tags/donate" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>donate</span></a> and/or <a href="https://infosec.space/tags/buy" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>buy</span></a> some support.</p><p>As a matter of fact, <span class="h-card" translate="no"><a href="https://mstdn.jp/@landley" class="u-url mention" rel="nofollow noopener" target="_blank">@<span>landley</span></a></span> did try to <em>crowbar</em> <a href="https://infosec.space/tags/GPLv2" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>GPLv2</span></a> [or rather started it]¹ with <a href="https://infosec.space/tags/BusyBox" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>BusyBox</span></a> and that failed miserably, because now everyone knows BusyBox as the litigatious² folks that one should just not use code from.</p><p>There's a reason I chose <a href="https://infosec.space/tags/0BSD" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>0BSD</span></a> ³ for <span class="h-card" translate="no"><a href="https://infosec.space/@OS1337" class="u-url mention" rel="nofollow noopener" target="_blank">@<span>OS1337</span></a></span> and it's because I most of the work I do is build and repackage <a href="https://infosec.space/tags/toybox" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>toybox</span></a> + <a href="https://infosec.space/tags/musl" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>musl</span></a> / <a href="https://infosec.space/tags/Linux" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>Linux</span></a> and I want people to use it as a <em>friendly licensed</em> foundation for their <em><a href="https://infosec.space/tags/IoT" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>IoT</span></a></em> and <em><a href="https://infosec.space/tags/embedded" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>embedded</span></a></em> projects down the line.</p><p>And that means that I'll also accept contributions on the same license and not expect devs to sign away code under worse terms so I can turn it into <a href="https://infosec.space/tags/UnfreeSoftware" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>UnfreeSoftware</span></a> the way Redis and others did...</p><p>¹ <a href="https://www.youtube.com/watch?v=MkJkyMuBm3g&amp;t=1607s" rel="nofollow noopener" translate="no" target="_blank"><span class="invisible">https://www.</span><span class="ellipsis">youtube.com/watch?v=MkJkyMuBm3</span><span class="invisible">g&amp;t=1607s</span></a><br>² <a href="https://www.busybox.net/license.html" rel="nofollow noopener" translate="no" target="_blank"><span class="invisible">https://www.</span><span class="">busybox.net/license.html</span><span class="invisible"></span></a><br>³ <a href="https://en.wikipedia.org/wiki/BSD_licenses#0-clause_license_(%22BSD_Zero_Clause_License%22)" rel="nofollow noopener" translate="no" target="_blank"><span class="invisible">https://</span><span class="ellipsis">en.wikipedia.org/wiki/BSD_lice</span><span class="invisible">nses#0-clause_license_(%22BSD_Zero_Clause_License%22)</span></a><br>⁴ <a href="https://github.com/OS-1337/OS1337/blob/main/LICENSE.md" rel="nofollow noopener" translate="no" target="_blank"><span class="invisible">https://</span><span class="ellipsis">github.com/OS-1337/OS1337/blob</span><span class="invisible">/main/LICENSE.md</span></a></p>