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>

find you on :butterfedy1: fediverseUpgrade to <a class="hashtag" href="https://wizard.casa/collections/tags/gplv4" rel="nofollow noopener" target="_blank">#GPLv4</a>?Nothing wrong with <a class="hashtag" href="https://wizard.casa/collections/tags/gplv3" rel="nofollow noopener" target="_blank">#GPLv3</a>, but I feel it does need to be updated to specifically make it unlawful to put the code on any repository owned or operated by an entity that is engaging in software theft (eg. Micros(ha)ft servers). That means no code on git-hub(dot) com.... includes forks and mirrors obviously.Microsoft supports <a class="hashtag" href="https://wizard.casa/collections/tags/softwaretheft" rel="nofollow noopener" target="_blank">#softwareTheft</a> via their so-called "ai".(NOTE: The new license wouldn't need to add anything about "AI" because the existing license is clear, but it probably should explicitly name micros(ha)ft as barred for the sake of clarity.)<a class="u-url mention" href="https://mastodon.xyz/@rms" rel="nofollow noopener" target="_blank">@rms</a> <a class="u-url mention" href="https://hostux.social/@fsf" rel="nofollow noopener" target="_blank">@fsf</a> <a class="u-url mention" href="https://shitposter.world/users/jeffcliff" rel="nofollow noopener" target="_blank">@jeffcliff</a> <a class="u-url mention" href="https://mitra.social/users/silverpill" rel="nofollow noopener" target="_blank">@silverpill</a> <a class="u-url mention" href="https://freesoftwareextremist.com/users/r" rel="nofollow noopener" target="_blank">@r</a>

Recent searches

Search options

Administered by:

Server stats:

#gplv4