Kevin Karhan :verified:<p><span class="h-card" translate="no"><a href="https://social.treehouse.systems/@marcan" class="u-url mention" rel="nofollow noopener noreferrer" 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 noreferrer" 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 noreferrer" target="_blank">@<span>landley</span></a></span> I did the <a href="https://infosec.space/tags/copyleft" class="mention hashtag" rel="nofollow noopener noreferrer" 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 noreferrer" target="_blank">#<span>0BSD</span></a> as a <a href="https://infosec.space/tags/PermissiveLicense" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>PermissiveLicense</span></a> (cuz <a href="https://infosec.space/tags/PublicDomain" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>PublicDomain</span></a> legally doesn't exist in <a href="https://infosec.space/tags/Germany" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>Germany</span></a>: One cannot renounce <a href="https://infosec.space/tags/Authorship" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>Authorship</span></a> for legal reasons, otherwise <a href="https://infosec.space/tags/HateSpeech" class="mention hashtag" rel="nofollow noopener noreferrer" 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 noreferrer" 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 noreferrer" target="_blank">#<span>AssholeLicensing</span></a>"</em> like <a href="https://infosec.space/tags/SSPL" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>SSPL</span></a> is inherently unfree and <a href="https://infosec.space/tags/AGPLv3" class="mention hashtag" rel="nofollow noopener noreferrer" 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 noreferrer" 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 noreferrer" target="_blank">#<span>GAFAMs</span></a> <a href="https://youtu.be/ZzI9JE0i6Lc" rel="nofollow noopener noreferrer" target="_blank">like Amazon</a> from leeching <a href="https://infosec.space/tags/FLOSS" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>FLOSS</span></a> is to either make <a href="https://infosec.space/tags/CCSS" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>CCSS</span></a> or offer the <em>superior [<a href="https://infosec.space/tags/SaaS" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>SaaS</span></a>] solution</em> by ticking boxes <a href="https://infosec.space/tags/aws" class="mention hashtag" rel="nofollow noopener noreferrer" 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 noreferrer" target="_blank">#<span>CloudAct</span></a>, like <a href="https://infosec.space/tags/GDPR" class="mention hashtag" rel="nofollow noopener noreferrer" 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 noreferrer" target="_blank">#<span>SelfHosting</span></a> & Support/Management Options for self-hosted systems)...</p><ul><li> <a href="https://infosec.space/tags/healthcare" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>healthcare</span></a>-IT based startups in the <a href="https://infosec.space/tags/EU" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>EU</span></a> pay Companies like <a href="https://infosec.space/tags/Telekom" class="mention hashtag" rel="nofollow noopener noreferrer" 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 noreferrer" 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>