Shakedown Social

Kevin Karhan :verified:<a href="https://mastodon.social/@katyswain" class="u-url mention" rel="nofollow noopener" target="_blank">@katyswain</a> I din't think that <a href="https://infosec.space/tags/CCSS" class="mention hashtag" rel="nofollow noopener" target="_blank">#CCSS</a> is good either, but the demands of <a href="https://infosec.space/tags/GPLv3" class="mention hashtag" rel="nofollow noopener" target="_blank">#GPLv3</a> are not compatible with the (adnitteldy shitty) reality of how <a href="https://infosec.space/tags/IP" class="mention hashtag" rel="nofollow noopener" target="_blank">#IP</a>, <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> work and thus it kneecaps a lot of things.<ul><li>GPLv3 caused <a href="https://infosec.space/tags/Apple" class="mention hashtag" rel="nofollow noopener" target="_blank">#Apple</a> to freeze their <a href="https://infosec.space/tags/bash" class="mention hashtag" rel="nofollow noopener" target="_blank">#bash</a> version and divest into <a href="https://infosec.space/tags/LLVM" class="mention hashtag" rel="nofollow noopener" target="_blank">#LLVM</a> and adopt <a href="https://infosec.space/tags/zsh" class="mention hashtag" rel="nofollow noopener" target="_blank">#zsh</a>.</li><li>As <a href="https://mstdn.jp/@landley" class="u-url mention" rel="nofollow noopener" target="_blank">@landley</a> showed, enforcing the <a href="https://infosec.space/tags/GPL" class="mention hashtag" rel="nofollow noopener" target="_blank">#GPL</a>(v2) resulted in exactly 0 code being committed to <a href="https://infosec.space/tags/BusyBox" class="mention hashtag" rel="nofollow noopener" target="_blank">#BusyBox</a> and it only made said project look toxic and litigatious. </li><li>Also i've yet to see anything happen re: <a href="https://infosec.space/tags/paywalled" class="mention hashtag" rel="nofollow noopener" target="_blank">#paywalled</a> <a href="https://infosec.space/tags/SourceCodeAccess" class="mention hashtag" rel="nofollow noopener" target="_blank">#SourceCodeAccess</a> for <a href="https://infosec.space/tags/grsec" class="mention hashtag" rel="nofollow noopener" target="_blank">#grsec</a> & <a href="https://infosec.space/tags/RedHat" class="mention hashtag" rel="nofollow noopener" target="_blank">#RedHat</a> <a href="https://infosec.space/tags/Linux" class="mention hashtag" rel="nofollow noopener" target="_blank">#Linux</a>. Maybe <a href="https://infosec.space/tags/GPLv4" class="mention hashtag" rel="nofollow noopener" target="_blank">#GPLv4</a> will ban <a href="https://infosec.space/tags/paxwalling" class="mention hashtag" rel="nofollow noopener" target="_blank">#paxwalling</a> and force violators to work on <a href="https://infosec.space/tags/GNU" class="mention hashtag" rel="nofollow noopener" target="_blank">#GNU</a> / <a href="https://infosec.space/tags/HURD" class="mention hashtag" rel="nofollow noopener" target="_blank">#HURD</a>?</li></ul>I chose <a href="https://infosec.space/tags/0BSD" class="mention hashtag" rel="nofollow noopener" target="_blank">#0BSD</a> for _OS/1337 because as with any "intellectual labour", one cannot force others to collaborate and I'd rather have people join in out of the goodness of their hearts instead of just dumping some random git commit that is useless.<a href="https://infosec.space/tags/OS1337" class="mention hashtag" rel="nofollow noopener" target="_blank">#OS1337</a>

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> kinda gives me <a href="https://infosec.space/tags/grsecurity" class="mention hashtag" rel="nofollow noopener" target="_blank">#grsecurity</a> & <a href="https://infosec.space/tags/RHEL" class="mention hashtag" rel="nofollow noopener" target="_blank">#RHEL</a> - flashbacks: cuz <a href="https://infosec.space/tags/paywalling" class="mention hashtag" rel="nofollow noopener" target="_blank">#paywalling</a> <a href="https://infosec.space/tags/SourcecodeAccess" class="mention hashtag" rel="nofollow noopener" target="_blank">#SourcecodeAccess</a> to paying <a href="https://infosec.space/tags/subscribers" class="mention hashtag" rel="nofollow noopener" target="_blank">#subscribers</a> and penalizing them aka. firing them as clients for exercising their right to share/modify/redistribute the <a href="https://infosec.space/tags/SourceCode" class="mention hashtag" rel="nofollow noopener" target="_blank">#SourceCode</a> is inherently an asshole move but apparently legal.<ul><li>Since <a href="https://infosec.space/tags/BrucePerens" class="mention hashtag" rel="nofollow noopener" target="_blank">#BrucePerens</a> failed to sue <a href="https://infosec.space/tags/grsec" class="mention hashtag" rel="nofollow noopener" target="_blank">#grsec</a> into not doing that and <a href="https://infosec.space/tags/IBM" class="mention hashtag" rel="nofollow noopener" target="_blank">#IBM</a> took notice when they bought <a href="https://infosec.space/tags/RedHat" class="mention hashtag" rel="nofollow noopener" target="_blank">#RedHat</a>.</li></ul> Not shure if a <a href="https://infosec.space/tags/license" class="mention hashtag" rel="nofollow noopener" target="_blank">#license</a> that governs things beyond the useage rights of a <a href="https://infosec.space/tags/Software" class="mention hashtag" rel="nofollow noopener" target="_blank">#Software</a> is even legally enforceable in Germany amd many other juristictions... <ul><li>I'd certainly rather blow €€€€ on a lawyer instead of playing "<a href="https://infosec.space/tags/FuckAroundAndFindOit" class="mention hashtag" rel="nofollow noopener" target="_blank">#FuckAroundAndFindOit</a>" and facing insolvency-inducing "cease and decist letters" from competitiors by having flatout-illegal terms...</li></ul><a href="https://infosec.space/tags/WhatYouAllowIsWhatWillContinue" class="mention hashtag" rel="nofollow noopener" target="_blank">#WhatYouAllowIsWhatWillContinue</a>

Recent searches

Search options

Administered by:

Server stats:

#sourcecodeaccess