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>

Bradley M. KuhnToday, <a href="https://mastodon.social/@richardfontana" class="u-url mention" rel="nofollow noopener" target="_blank">@richardfontana</a> & I restarted, relaunched, & revitalized copyleft-next.All versions & variants of <a href="https://floss.social/tags/GPL" class="mention hashtag" rel="nofollow noopener" target="_blank">#GPL</a> are great licenses. But, today, <a href="https://floss.social/tags/GPLv3" class="mention hashtag" rel="nofollow noopener" target="_blank">#GPLv3</a> turned 18 years old & <a href="https://floss.social/tags/GPLv2" class="mention hashtag" rel="nofollow noopener" target="_blank">#GPLv2</a> turned 34 years old.At least once in a generation, <a href="https://floss.social/tags/FOSS" class="mention hashtag" rel="nofollow noopener" target="_blank">#FOSS</a> needs a new approach to strong <a href="https://floss.social/tags/copyleft" class="mention hashtag" rel="nofollow noopener" target="_blank">#copyleft</a>.These posts have details: <a href="https://lists.copyleft.org/pipermail/next/2025q2/000000.html" rel="nofollow noopener" translate="no" target="_blank">https://lists.copyleft.org/pipermail/next/2025q2/000000.html</a> & <a href="https://fedi.copyleft.org/@next/114769761806288554" rel="nofollow noopener" translate="no" target="_blank">https://fedi.copyleft.org/@next/114769761806288554</a>I ask you to follow <a href="https://fedi.copyleft.org/@next" class="u-url mention" rel="nofollow noopener" target="_blank">@next</a> & check out our website at <a href="https://next.copyleft.org/" rel="nofollow noopener" translate="no" target="_blank">https://next.copyleft.org/</a>. FYI: I'll migrate this account to @bkuhn@copyleft.org later this week.

copyleft-nextToday, we (<a href="https://floss.social/@bkuhn" class="u-url mention" rel="nofollow noopener" target="_blank">@bkuhn</a> & <a href="https://mastodon.social/@richardfontana" class="u-url mention" rel="nofollow noopener" target="_blank">@richardfontana</a>) excitedly announce that we have restarted, revitalized, and relaunched copyleft-next!Today, <a href="https://fedi.copyleft.org/tags/GPLv3" class="mention hashtag" rel="nofollow noopener" target="_blank">#GPLv3</a> turns exactly 18 years old. This month, <a href="https://fedi.copyleft.org/tags/GPLv2" class="mention hashtag" rel="nofollow noopener" target="_blank">#GPLv2</a> turned 34 years old. These are both great licenses and we love them. Nevertheless, at least once in a generation, <a href="https://fedi.copyleft.org/tags/FOSS" class="mention hashtag" rel="nofollow noopener" target="_blank">#FOSS</a> needs a new approach to strong <a href="https://fedi.copyleft.org/tags/copyleft" class="mention hashtag" rel="nofollow noopener" target="_blank">#copyleft</a>.Read more in this thread about the relaunch of the copyleft-next project … ( or read more on the post here: <a href="https://lists.copyleft.org/pipermail/next/2025q2/000000.html" rel="nofollow noopener" translate="no" target="_blank">https://lists.copyleft.org/pipermail/next/2025q2/000000.html</a> )

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>!

Europe Says<a href="https://www.europesays.com/2114818/" rel="nofollow noopener" translate="no" target="_blank">https://www.europesays.com/2114818/</a> Garanti BBVA Romania offers real-time RON transfers with Allevo <a href="https://pubeurope.com/tags/Allevo" class="mention hashtag" rel="nofollow noopener" target="_blank">#Allevo</a> <a href="https://pubeurope.com/tags/Europe" class="mention hashtag" rel="nofollow noopener" target="_blank">#Europe</a> <a href="https://pubeurope.com/tags/FinTechNewsEurope" class="mention hashtag" rel="nofollow noopener" target="_blank">#FinTechNewsEurope</a> <a href="https://pubeurope.com/tags/FinTPInstant" class="mention hashtag" rel="nofollow noopener" target="_blank">#FinTPInstant</a> <a href="https://pubeurope.com/tags/GarantiBBVARomania" class="mention hashtag" rel="nofollow noopener" target="_blank">#GarantiBBVARomania</a> <a href="https://pubeurope.com/tags/GPLv3" class="mention hashtag" rel="nofollow noopener" target="_blank">#GPLv3</a> <a href="https://pubeurope.com/tags/InstantPayments" class="mention hashtag" rel="nofollow noopener" target="_blank">#InstantPayments</a> <a href="https://pubeurope.com/tags/PaymentProcessing" class="mention hashtag" rel="nofollow noopener" target="_blank">#PaymentProcessing</a> <a href="https://pubeurope.com/tags/RealTimeDigitalPayments" class="mention hashtag" rel="nofollow noopener" target="_blank">#RealTimeDigitalPayments</a> <a href="https://pubeurope.com/tags/romania" class="mention hashtag" rel="nofollow noopener" target="_blank">#romania</a> <a href="https://pubeurope.com/tags/stiri" class="mention hashtag" rel="nofollow noopener" target="_blank">#stiri</a> <a href="https://pubeurope.com/tags/stp" class="mention hashtag" rel="nofollow noopener" target="_blank">#stp</a> <a href="https://pubeurope.com/tags/Swift" class="mention hashtag" rel="nofollow noopener" target="_blank">#Swift</a> <a href="https://pubeurope.com/tags/TransFonD" class="mention hashtag" rel="nofollow noopener" target="_blank">#TransFonD</a>

Davide BucciI decided to release the source code of my award-winning text adventure game for vintage computers, Silk Dust: <a href="https://github.com/DarwinNE/Silk-Dust" rel="nofollow noopener" target="_blank">https://github.com/DarwinNE/Silk-Dust</a> <a href="https://mastodon.sdf.org/tags/opensource" class="mention hashtag" rel="nofollow noopener" target="_blank">#opensource</a> <a href="https://mastodon.sdf.org/tags/retrocomputing" class="mention hashtag" rel="nofollow noopener" target="_blank">#retrocomputing</a> <a href="https://mastodon.sdf.org/tags/TextAdventure" class="mention hashtag" rel="nofollow noopener" target="_blank">#TextAdventure</a> <a href="https://mastodon.sdf.org/tags/InteractiveFiction" class="mention hashtag" rel="nofollow noopener" target="_blank">#InteractiveFiction</a> <a href="https://mastodon.sdf.org/tags/GPLv3" class="mention hashtag" rel="nofollow noopener" target="_blank">#GPLv3</a>

aaronGrapheneOS: Where Licenses Matter More Than PeopleI chose to write this. Link removed <a href="https://dragonscave.space/tags/GrapheneOS" class="mention hashtag" rel="nofollow noopener" target="_blank">#GrapheneOS</a> <a href="https://dragonscave.space/tags/Accessibility" class="mention hashtag" rel="nofollow noopener" target="_blank">#Accessibility</a> <a href="https://dragonscave.space/tags/FOSS" class="mention hashtag" rel="nofollow noopener" target="_blank">#FOSS</a> <a href="https://dragonscave.space/tags/Blind" class="mention hashtag" rel="nofollow noopener" target="_blank">#Blind</a> <a href="https://dragonscave.space/tags/DisabilityTech" class="mention hashtag" rel="nofollow noopener" target="_blank">#DisabilityTech</a> <a href="https://dragonscave.space/tags/Inclusion" class="mention hashtag" rel="nofollow noopener" target="_blank">#Inclusion</a> <a href="https://dragonscave.space/tags/GPLv3" class="mention hashtag" rel="nofollow noopener" target="_blank">#GPLv3</a> <a href="https://dragonscave.space/tags/espeak" class="mention hashtag" rel="nofollow noopener" target="_blank">#espeak</a> <a href="https://dragonscave.space/tags/a11y" class="mention hashtag" rel="nofollow noopener" target="_blank">#a11y</a> <a href="https://dragonscave.space/tags/Security" class="mention hashtag" rel="nofollow noopener" target="_blank">#Security</a> <a href="https://dragonscave.space/tags/FreeSoftware" class="mention hashtag" rel="nofollow noopener" target="_blank">#FreeSoftware</a> <a href="https://dragonscave.space/tags/DisabilityRights" class="mention hashtag" rel="nofollow noopener" target="_blank">#DisabilityRights</a> <a href="https://dragonscave.space/tags/Android" class="mention hashtag" rel="nofollow noopener" target="_blank">#Android</a> <a href="https://dragonscave.space/tags/Rant" class="mention hashtag" rel="nofollow noopener" target="_blank">#Rant</a> <a href="https://dragonscave.space/tags/TechShame" class="mention hashtag" rel="nofollow noopener" target="_blank">#TechShame</a>**update**: If you are using this post as some kind of call-to-action to harass and attack the GOS developers, please don't.That damages everyone. You, them, and myself. It's not helpful.**Update two**. I have made the decision to pull this post. It is not a good starting-point for a discussion, and just encourages defensiveness on both sides – when there really aren't sides here at all.As a FOSS contributor, I am deeply ashamed at the way I approached this out of frustration.

Kevin Karhan :verified:<a href="https://hsnl.social/@eloy" class="u-url mention" rel="nofollow noopener" target="_blank">@eloy</a> <a href="https://infosec.space/tags/GPL" class="mention hashtag" rel="nofollow noopener" target="_blank">#GPL</a> wors poorly for <a href="https://infosec.space/tags/art" class="mention hashtag" rel="nofollow noopener" target="_blank">#art</a>, thus I recommend using <a href="https://mastodon.social/@creativecommons" class="u-url mention" rel="nofollow noopener" target="_blank">@creativecommons</a> instead.<ul><li>I.e. <a href="https://infosec.space/tags/CCBYSA" class="mention hashtag" rel="nofollow noopener" target="_blank">#CCBYSA</a> would be roughly <a href="https://infosec.space/tags/GPLv3" class="mention hashtag" rel="nofollow noopener" target="_blank">#GPLv3</a>-alike.</li></ul><a href="https://infosec.space/tags/NotLegalAdvice" class="mention hashtag" rel="nofollow noopener" target="_blank">#NotLegalAdvice</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>

GigaquadEach month we'll be making a financial donation to an <a href="https://fosstodon.org/tags/opensource" class="mention hashtag" rel="nofollow noopener" target="_blank">#opensource</a> project we highly value or depend upon. This month our featured project is <a href="https://fosstodon.org/tags/FairEmail" class="mention hashtag" rel="nofollow noopener" target="_blank">#FairEmail</a>, a superb Android email client licence under <a href="https://fosstodon.org/tags/gplv3" class="mention hashtag" rel="nofollow noopener" target="_blank">#gplv3</a>. We use it ourselves and would recommend it to our customers.Find more information here: <a href="https://email.faircode.eu/" rel="nofollow noopener" translate="no" target="_blank">https://email.faircode.eu/</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://chaos.social/@frumble" class="u-url mention" rel="nofollow noopener" target="_blank">@frumble</a> <a href="https://exquisite.social/@thomholwerda" class="u-url mention" rel="nofollow noopener" target="_blank">@thomholwerda</a> ja, <a href="https://infosec.space/tags/GPLv3" class="mention hashtag" rel="nofollow noopener" target="_blank">#GPLv3</a> hat auch wieder Probleme.<ul><li>Ideal wäre <a href="https://infosec.space/tags/BSD" class="mention hashtag" rel="nofollow noopener" target="_blank">#BSD</a> (wenn nicht sogar <a href="https://infosec.space/tags/0BSD" class="mention hashtag" rel="nofollow noopener" target="_blank">#0BSD</a>) weil GPLv3 ist mit <a href="https://infosec.space/tags/CCSS" class="mention hashtag" rel="nofollow noopener" target="_blank">#CCSS</a> inkompatibel und daher für alles was nicht ebenfalls <a href="https://infosec.space/tags/GPLv3" class="mention hashtag" rel="nofollow noopener" target="_blank">#GPLv3</a> oder <a href="https://infosec.space/tags/AGPLv3" class="mention hashtag" rel="nofollow noopener" target="_blank">#AGPLv3</a> ist inkompatibel!</li></ul>

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>

Thorsten Leemhuis (acct. 1/4)TIL: <a href="https://linuxrocks.online/@tuxedocomputers" class="u-url mention" rel="nofollow noopener" target="_blank">@tuxedocomputers</a> released <a href="https://fosstodon.org/tags/Linux" class="mention hashtag" rel="nofollow noopener" target="_blank">#Linux</a> <a href="https://fosstodon.org/tags/kernel" class="mention hashtag" rel="nofollow noopener" target="_blank">#kernel</a> drivers for their machines under the <a href="https://fosstodon.org/tags/GPLv3" class="mention hashtag" rel="nofollow noopener" target="_blank">#GPLv3</a>, which makes it impossible for competitors and distros to ship them pre-compiled, as that license is incompatible with the <a href="https://fosstodon.org/tags/LinuxKernel" class="mention hashtag" rel="nofollow noopener" target="_blank">#LinuxKernel</a>'s <a href="https://fosstodon.org/tags/GPLv2" class="mention hashtag" rel="nofollow noopener" target="_blank">#GPLv2</a> only license. They did this purposely, allegedly to "keep control of the upstream pacing" – and want to re-license the code while upstreaming.<a href="https://github.com/tuxedocomputers/tuxedo-keyboard/issues/61" rel="nofollow noopener" translate="no" target="_blank">https://github.com/tuxedocomputers/tuxedo-keyboard/issues/61</a><a href="https://gitlab.com/tuxedocomputers/development/packages/tuxedo-drivers/-/issues/137" rel="nofollow noopener" translate="no" target="_blank">https://gitlab.com/tuxedocomputers/development/packages/tuxedo-drivers/-/issues/137</a> <a href="https://gitlab.com/tuxedocomputers/development/packages/tuxedo-drivers/-/issues/138" rel="nofollow noopener" translate="no" target="_blank">https://gitlab.com/tuxedocomputers/development/packages/tuxedo-drivers/-/issues/138</a><a href="https://gitlab.com/tuxedocomputers/development/packages/tuxedo-drivers#regarding-upstreaming-of-tuxedo-drivers" rel="nofollow noopener" translate="no" target="_blank">https://gitlab.com/tuxedocomputers/development/packages/tuxedo-drivers#regarding-upstreaming-of-tuxedo-drivers</a>

Kevin Karhan :verified:<a href="https://babka.social/@serge" class="u-url mention" rel="nofollow noopener" target="_blank">@serge</a> yeah, <a href="https://infosec.space/tags/RMS" class="mention hashtag" rel="nofollow noopener" target="_blank">#RMS</a> is a cringy "FLOSS extremist" in the worst sense of it, because he started hating <a href="https://infosec.space/tags/OLPC" class="mention hashtag" rel="nofollow noopener" target="_blank">#OLPC</a> for merely making it possible to put <a href="https://infosec.space/tags/Windows" class="mention hashtag" rel="nofollow noopener" target="_blank">#Windows</a> on the <a href="https://infosec.space/tags/XO1" class="mention hashtag" rel="nofollow noopener" target="_blank">#XO1</a>.<ul><li>Not delivering it with it even as a BTO option, but merely offering <a href="https://infosec.space/tags/drivers" class="mention hashtag" rel="nofollow noopener" target="_blank">#drivers</a>.</li></ul>And for him everythng that isn't <a href="https://infosec.space/tags/GPLv3" class="mention hashtag" rel="nofollow noopener" target="_blank">#GPLv3</a> or <a href="https://infosec.space/tags/AGPLv3" class="mention hashtag" rel="nofollow noopener" target="_blank">#AGPLv3</a> isn't <a href="https://infosec.space/tags/FLOSS" class="mention hashtag" rel="nofollow noopener" target="_blank">#FLOSS</a> to him, with his fanboys getting caught harrassing projects to "switch to GPLv3" for no reason.

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

Kevin Karhan :verified:Rant re: CCSS vs FLOSS licensing, wishful thinking

Kevin Karhan :verified:re: Off-topic related tangent on GPL relicensing

Kevin Karhan :verified:<a href="https://mas.to/@libreleah" class="u-url mention" rel="nofollow noopener" target="_blank">@libreleah</a> thanks.Personally, I think maintainers should choose their license wisely beforehand:<ul><li>There are reasons why I chose to put some projects <a href="https://github.com/greyhat-academy/lists.d" rel="nofollow noopener" target="_blank">under</a> <a href="https://infosec.space/tags/CCBYNCSA" class="mention hashtag" rel="nofollow noopener" target="_blank">#CCBYNCSA</a>, <a href="https://github.com/kbtechnologies/nucbook" rel="nofollow noopener" target="_blank">some</a> <a href="https://infosec.space/tags/GPLv3" class="mention hashtag" rel="nofollow noopener" target="_blank">#GPLv3</a> and <a href="https://github.com/OS-1337/OS1337" rel="nofollow noopener" target="_blank">some</a> <a href="https://infosec.space/tags/0BSD" class="mention hashtag" rel="nofollow noopener" target="_blank">#0BSD</a>.</li><li>In some cases I did fork stuff under <a href="https://infosec.space/tags/MIT" class="mention hashtag" rel="nofollow noopener" target="_blank">#MIT</a> which I'd not change the license of - even if it would be compatible - because I <a href="https://github.com/OS-1337/mlb" rel="nofollow noopener" target="_blank">literally changed nothing in terms of code</a> and also didn't see any advantage in doing so to begin with.</li></ul>Espechally in the case of <a href="https://infosec.space/tags/DuckStation" class="mention hashtag" rel="nofollow noopener" target="_blank">#DuckStation</a> this is bad because we ain't talking about the whole <a href="https://infosec.space/tags/GPLv2" class="mention hashtag" rel="nofollow noopener" target="_blank">#GPLv2</a>-only vs. GPLv3+ drama or <a href="https://infosec.space/tags/grsecurity" class="mention hashtag" rel="nofollow noopener" target="_blank">#grsecurity</a> <a href="https://infosec.space/tags/paywalling" class="mention hashtag" rel="nofollow noopener" target="_blank">#paywalling</a> (which is <a href="https://www.youtube.com/watch?v=cXLFXV6zIyk" rel="nofollow noopener" target="_blank">an asshole move but legal</a> )...<ul><li>Maybe the dev(s) - <a href="https://www.youtube.com/watch?v=Oj9Vl-Bteq8" rel="nofollow noopener" target="_blank">unlike</a> <a href="https://infosec.space/tags/Capcom" class="mention hashtag" rel="nofollow noopener" target="_blank">#Capcom</a> - weren't fully aware of this issue, but even big Companies (i.e. <a href="https://infosec.space/tags/AVM" class="mention hashtag" rel="nofollow noopener" target="_blank">#AVM</a>) got forced into compliance...</li></ul>Lets just hope a friendly (!!!) reminder makes them realize, apologize and undo the change...

Recent searches

Search options

Administered by:

Server stats:

#gplv3