MastodonTech.de

Kevin Karhan :verified:<a href="https://owo.cafe/@stage7" class="u-url mention" rel="nofollow noopener" target="_blank">@stage7</a> personally I do wish for <a href="https://infosec.space/tags/FLOSS" class="mention hashtag" rel="nofollow noopener" target="_blank">#FLOSS</a> to have more teeth…<ul><li>I mean, <a href="https://infosec.space/tags/GPLv2" class="mention hashtag" rel="nofollow noopener" target="_blank">#GPLv2</a> got confirmed as valid in Germany and the <a href="https://infosec.space/tags/license" class="mention hashtag" rel="nofollow noopener" target="_blank">#license</a> terms successfully enforced.</li></ul>The only restrictions I'm aware of are "[legal and/or business] deals that have unexpectably bad terms and conditions" (aimed at exploiting "someones lack of expefience, ability to make informed decisions or socioeconomic situation [of distress]") which mostly aims at criminalizing <a href="https://infosec.space/tags/PaydayLoans" class="mention hashtag" rel="nofollow noopener" target="_blank">#PaydayLoans</a> at extortive APRs, rentseeking, discrimination and other tactics preying on <a href="https://infosec.space/tags/consumers" class="mention hashtag" rel="nofollow noopener" target="_blank">#consumers</a>.<ul><li>It's more of a <a href="https://infosec.space/tags/ConsumerProtection" class="mention hashtag" rel="nofollow noopener" target="_blank">#ConsumerProtection</a> thing and almost certainly doesn't apply to <a href="https://infosec.space/tags/Businesses" class="mention hashtag" rel="nofollow noopener" target="_blank">#Businesses</a> which are exempt from consumer protection (cuz <a href="https://infosec.space/tags/B2B" class="mention hashtag" rel="nofollow noopener" target="_blank">#B2B</a> aind <a href="https://infosec.space/tags/B2C" class="mention hashtag" rel="nofollow noopener" target="_blank">#B2C</a>!)</li></ul>Plus <a href="https://infosec.space/tags/FLOSS" class="mention hashtag" rel="nofollow noopener" target="_blank">#FLOSS</a> licenses ain't the norm (and I'm pretty shure that we rather see <a href="https://infosec.space/tags/CCSS" class="mention hashtag" rel="nofollow noopener" target="_blank">#CCSS</a> banned than <a href="https://infosec.space/tags/AntifascistLicense" class="mention hashtag" rel="nofollow noopener" target="_blank">#AntifascistLicense</a>|s being struck down!)…<ul><li>OFC this is <a href="https://infosec.space/tags/NotLegalAdvice" class="mention hashtag" rel="nofollow noopener" target="_blank">#NotLegalAdvice</a> and <a href="https://infosec.space/tags/speculation" class="mention hashtag" rel="nofollow noopener" target="_blank">#speculation</a>, tho OFC one has the freedom to decline business based off objective and/or terms/justifications, like throwing a Neonazi out of a bar.</li></ul><a href="https://infosec.space/tags/AntifascistLicenses" class="mention hashtag" rel="nofollow noopener" target="_blank">#AntifascistLicenses</a> <a href="https://infosec.space/tags/Antifascism" class="mention hashtag" rel="nofollow noopener" target="_blank">#Antifascism</a> <a href="https://infosec.space/tags/Licensing" class="mention hashtag" rel="nofollow noopener" target="_blank">#Licensing</a> <a href="https://infosec.space/tags/FOSS" class="mention hashtag" rel="nofollow noopener" target="_blank">#FOSS</a> <a href="https://infosec.space/tags/OpenSource" class="mention hashtag" rel="nofollow noopener" target="_blank">#OpenSource</a>

Kevin Karhan :verified:<a href="https://weird.autos/@rootwyrm" class="u-url mention" rel="nofollow noopener" target="_blank">@rootwyrm</a> <a href="https://infosec.exchange/@david_chisnall" class="u-url mention" rel="nofollow noopener" target="_blank">@david_chisnall</a> <a href="https://circumstances.run/@davidgerard" class="u-url mention" rel="nofollow noopener" target="_blank">@davidgerard</a> <a href="https://infosec.exchange/@0xabad1dea" class="u-url mention" rel="nofollow noopener" target="_blank">@0xabad1dea</a> <a href="https://mastodon.xyz/@dougwade" class="u-url mention" rel="nofollow noopener" target="_blank">@dougwade</a> <a href="https://corteximplant.com/@zeyus" class="u-url mention" rel="nofollow noopener" target="_blank">@zeyus</a> yeah, and the gew cases of litigation in terms of enforcement backfired hard as well...<ul><li>Don't even get <a href="https://mstdn.jp/@landley" class="u-url mention" rel="nofollow noopener" target="_blank">@landley</a> started on the <a href="https://infosec.space/tags/BusyBox" class="mention hashtag" rel="nofollow noopener" target="_blank">#BusyBox</a> <a href="https://infosec.space/tags/GPLv2" class="mention hashtag" rel="nofollow noopener" target="_blank">#GPLv2</a> enforcement...</li></ul>That being said in <a href="https://infosec.space/tags/Germany" class="mention hashtag" rel="nofollow noopener" target="_blank">#Germany</a> said <a href="https://infosec.space/tags/GPL" class="mention hashtag" rel="nofollow noopener" target="_blank">#GPL</a> licenses get enforced by courts - as <a href="https://infosec.space/tags/Fritz" class="mention hashtag" rel="nofollow noopener" target="_blank">#Fritz</a>! (nee <a href="https://infosec.space/tags/AVM" class="mention hashtag" rel="nofollow noopener" target="_blank">#AVM</a>) found out the hard way.

Kevin Karhan :verified:<a href="https://hachyderm.io/@edboythinks" class="u-url mention" rel="nofollow noopener" target="_blank">@edboythinks</a> personally I'm in the process of.migrating from <a href="https://infosec.space/tags/Ubuntu" class="mention hashtag" rel="nofollow noopener" target="_blank">#Ubuntu</a> fonts to <a href="https://infosec.space/tags/B612" class="mention hashtag" rel="nofollow noopener" target="_blank">#B612</a> because they are superior yet more permissively licensed.<ul><li>Sadly I've not found an elegant way to force <a href="https://infosec.space/tags/SunGalatDemi" class="mention hashtag" rel="nofollow noopener" target="_blank">#SunGalatDemi</a> into the <a href="https://infosec.space/tags/Linux" class="mention hashtag" rel="nofollow noopener" target="_blank">#Linux</a> <a href="https://infosec.space/tags/kernel" class="mention hashtag" rel="nofollow noopener" target="_blank">#kernel</a> as <a href="https://infosec.space/tags/Console" class="mention hashtag" rel="nofollow noopener" target="_blank">#Console</a> <a href="https://infosec.space/tags/Font" class="mention hashtag" rel="nofollow noopener" target="_blank">#Font</a> and <a href="https://infosec.space/tags/license" class="mention hashtag" rel="nofollow noopener" target="_blank">#license</a>-wise that would not work (<a href="https://infosec.space/tags/CDDL" class="mention hashtag" rel="nofollow noopener" target="_blank">#CDDL</a> is incompatible with <a href="https://infosec.space/tags/GPLv2" class="mention hashtag" rel="nofollow noopener" target="_blank">#GPLv2</a>) nor would it make sense as any machine that I can't <a href="https://infosec.space/tags/SSH" class="mention hashtag" rel="nofollow noopener" target="_blank">#SSH</a> into runs in <a href="https://infosec.space/tags/MDA" class="mention hashtag" rel="nofollow noopener" target="_blank">#MDA</a> mode thus only has the hardware fonts of that mode anyway...</li></ul>

Kevin Karhan :verified:<a href="https://mastodon.social/@katyswain" class="u-url mention" rel="nofollow noopener" target="_blank">@katyswain</a> I think <a href="https://infosec.space/tags/GPLv3" class="mention hashtag" rel="nofollow noopener" target="_blank">#GPLv3</a> did more harm than good due to being a later version of the <a href="https://infosec.space/tags/GPL" class="mention hashtag" rel="nofollow noopener" target="_blank">#GPL</a> and thus causing <a href="https://infosec.space/tags/LicensingConflicts" class="mention hashtag" rel="nofollow noopener" target="_blank">#LicensingConflicts</a>.<ul><li>Worse even: many parts of it are inherently incompatible with how <a href="https://infosec.space/tags/IP" class="mention hashtag" rel="nofollow noopener" target="_blank">#IP</a>, <a href="https://infosec.space/tags/Patents" class="mention hashtag" rel="nofollow noopener" target="_blank">#Patents</a> and <a href="https://infosec.space/tags/Licensing" class="mention hashtag" rel="nofollow noopener" target="_blank">#Licensing</a> works that if caused problems for <a href="https://infosec.space/tags/GPLv2" class="mention hashtag" rel="nofollow noopener" target="_blank">#GPLv2</a> as well.</li></ul>There's a reason why I've chosen <a href="https://infosec.space/tags/0BSD" class="mention hashtag" rel="nofollow noopener" target="_blank">#0BSD</a> over GPLv3 in many newer projects and even consider changing said license on those that I am the sole contributor of...

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

Kevin Karhan :verified:<a href="https://gaysex.cloud/@sodiboo" class="u-url mention" rel="nofollow noopener" target="_blank">@sodiboo</a> <a href="https://possum.city/@tauon" class="u-url mention" rel="nofollow noopener" target="_blank">@tauon</a> <a href="https://transfem.social/@puppygirlhornypost2" class="u-url mention" rel="nofollow noopener" target="_blank">@puppygirlhornypost2</a> <a href="https://possum.city/@silly" class="u-url mention" rel="nofollow noopener" target="_blank">@silly</a> I don't think it's much of a "<a href="https://infosec.space/tags/freedom" class="mention hashtag" rel="nofollow noopener" target="_blank">#freedom</a>" on <a href="https://infosec.space/tags/iOS" class="mention hashtag" rel="nofollow noopener" target="_blank">#iOS</a> but rather that the few devices and OS versions in circulation, alongside everyone from <a href="https://infosec.space/tags/jailbreaker" class="mention hashtag" rel="nofollow noopener" target="_blank">#jailbreaker</a> to <a href="https://infosec.space/tags/malware" class="mention hashtag" rel="nofollow noopener" target="_blank">#malware</a> (espechally <a href="https://infosec.space/tags/govware" class="mention hashtag" rel="nofollow noopener" target="_blank">#govware</a> <a href="https://infosec.space/tags/developers" class="mention hashtag" rel="nofollow noopener" target="_blank">#developers</a>) want to crack it open result in way more personnel and money behind it.<ul><li>OFC the fact that the <a href="https://infosec.space/tags/Android" class="mention hashtag" rel="nofollow noopener" target="_blank">#Android</a> experience is worse from that POV is the lack of <a href="https://infosec.space/tags/regulation" class="mention hashtag" rel="nofollow noopener" target="_blank">#regulation</a> re: <a href="https://infosec.space/tags/repairability" class="mention hashtag" rel="nofollow noopener" target="_blank">#repairability</a> and <a href="https://infosec.space/tags/openness" class="mention hashtag" rel="nofollow noopener" target="_blank">#openness</a> that would make shit work. Most cheap <a href="https://infosec.space/tags/phones" class="mention hashtag" rel="nofollow noopener" target="_blank">#phones</a> are done with even cheaper <a href="https://infosec.space/tags/SoC" class="mention hashtag" rel="nofollow noopener" target="_blank">#SoC</a>'s by manufacturers who can't be assed (or frankly don't give a shit at all!) when it comes to <a href="https://infosec.space/tags/Linux" class="mention hashtag" rel="nofollow noopener" target="_blank">#Linux</a> <a href="https://infosec.space/tags/mainline" class="mention hashtag" rel="nofollow noopener" target="_blank">#mainline</a> support. (I mean, you've seen the video where <a href="https://mastodon.social/@SexyCyborg" class="u-url mention" rel="nofollow noopener" target="_blank">@SexyCyborg</a> demanded a vendor to give her the sourcecode as per <a href="https://infosec.space/tags/GPLv2" class="mention hashtag" rel="nofollow noopener" target="_blank">#GPLv2</a> for her device?)</li></ul>Granted <a href="https://grapheneos.social/@GrapheneOS" class="u-url mention" rel="nofollow noopener" target="_blank">@GrapheneOS</a> does limit their support to devices that can comply with their <a href="https://infosec.space/tags/security" class="mention hashtag" rel="nofollow noopener" target="_blank">#security</a> standards.<ul><li>The issues are mostly caused by hostile app developers that specifically decided to knee-jerk their users / customers for no good reason.</li></ul>I do wish for both vendors like <a href="https://infosec.space/tags/Fairphone" class="mention hashtag" rel="nofollow noopener" target="_blank">#Fairphone</a> to up their game and regulators like <a href="https://ec.social-network.europa.eu/@EUCommission" class="u-url mention" rel="nofollow noopener" target="_blank">@EUCommission</a> to actually push for more <a href="https://infosec.space/tags/transparency" class="mention hashtag" rel="nofollow noopener" target="_blank">#transparency</a>, <a href="https://infosec.space/tags/openness" class="mention hashtag" rel="nofollow noopener" target="_blank">#openness</a> and <a href="https://infosec.space/tags/LongTermSupport" class="mention hashtag" rel="nofollow noopener" target="_blank">#LongTermSupport</a> of <a href="https://infosec.space/tags/Smartphones" class="mention hashtag" rel="nofollow noopener" target="_blank">#Smartphones</a>, because <a href="https://infosec.space/tags/ManufacturedEwaste" class="mention hashtag" rel="nofollow noopener" target="_blank">#ManufacturedEwaste</a> like <a href="https://infosec.space/tags/SOYES" class="mention hashtag" rel="nofollow noopener" target="_blank">#SOYES</a>, <a href="https://infosec.space/tags/WiKo" class="mention hashtag" rel="nofollow noopener" target="_blank">#WiKo</a>, <a href="https://infosec.space/tags/Unihertz" class="mention hashtag" rel="nofollow noopener" target="_blank">#Unihertz</a> and others that ship <a href="https://infosec.space/tags/outdated" class="mention hashtag" rel="nofollow noopener" target="_blank">#outdated</a> <a href="https://infosec.space/tags/AndroidDevices" class="mention hashtag" rel="nofollow noopener" target="_blank">#AndroidDevices</a> and never even a single update are a major problem!<ul><li>I don't blame projects like <a href="https://fosstodon.org/@LineageOS" class="u-url mention" rel="nofollow noopener" target="_blank">@LineageOS</a> that they can't cover every device & SoC even tho they propably have the widest compatibility, I just think that there needs to be pressure that manufacturers don't just vomit stuff on the market and let customers frustratingly figure out the rest.</li></ul>I do have to give <a href="https://infosec.space/tags/Apple" class="mention hashtag" rel="nofollow noopener" target="_blank">#Apple</a> credit where it is due, and that is that <a href="https://infosec.space/tags/iOS" class="mention hashtag" rel="nofollow noopener" target="_blank">#iOS</a> does have consistency and accessibility nailed down very well. Something that they obviously are able being the "<a href="https://infosec.space/tags/BenevolentDictator" class="mention hashtag" rel="nofollow noopener" target="_blank">#BenevolentDictator</a>" of a <a href="https://infosec.space/tags/SingleVendor" class="mention hashtag" rel="nofollow noopener" target="_blank">#SingleVendor</a> & <a href="https://infosec.space/tags/SingleProvider" class="mention hashtag" rel="nofollow noopener" target="_blank">#SingleProvider</a> - platform. <ul><li>Obviously since they are the <a href="https://infosec.space/tags/vendor" class="mention hashtag" rel="nofollow noopener" target="_blank">#vendor</a> for <a href="https://infosec.space/tags/hardware" class="mention hashtag" rel="nofollow noopener" target="_blank">#hardware</a> and the sole ["legitimate" / official] <a href="https://infosec.space/tags/distributor" class="mention hashtag" rel="nofollow noopener" target="_blank">#distributor</a> for any <a href="https://infosec.space/tags/Apps" class="mention hashtag" rel="nofollow noopener" target="_blank">#Apps</a> they do OFC cross-finance their relatively long <a href="https://infosec.space/tags/support" class="mention hashtag" rel="nofollow noopener" target="_blank">#support</a> with their 15-30% cut from <a href="https://infosec.space/tags/App" class="mention hashtag" rel="nofollow noopener" target="_blank">#App</a> <a href="https://infosec.space/tags/sales" class="mention hashtag" rel="nofollow noopener" target="_blank">#sales</a> & <a href="https://infosec.space/tags/InAppPurchase" class="mention hashtag" rel="nofollow noopener" target="_blank">#InAppPurchase</a>|s they charge, which is why <a href="https://infosec.space/tags/AndroidPhones" class="mention hashtag" rel="nofollow noopener" target="_blank">#AndroidPhones</a> suffer the "<a href="https://infosec.space/tags/3DO" class="mention hashtag" rel="nofollow noopener" target="_blank">#3DO</a> syndrome": Needing to charge more since they only get to make money once with hardware sales and not after that, so there's no incentive for them to give a shit beyond "brand value" to care. <a href="https://infosec.space/tags/Google" class="mention hashtag" rel="nofollow noopener" target="_blank">#Google</a>, <a href="https://infosec.space/tags/Samsing" class="mention hashtag" rel="nofollow noopener" target="_blank">#Samsing</a>, <a href="https://infosec.space/tags/Fairphone" class="mention hashtag" rel="nofollow noopener" target="_blank">#Fairphone</a> and very few others do, but most don't as they close the books on the product once launched and sold out (angrily stares at Unihertz)...</li></ul>Maybe one day the folks at <a href="https://fosstodon.org/@frameworkcomputer" class="u-url mention" rel="nofollow noopener" target="_blank">@frameworkcomputer</a> acquire Fairphone and decide to bring the same modularity to <a href="https://infosec.space/tags/Smartphones" class="mention hashtag" rel="nofollow noopener" target="_blank">#Smartphones</a> and get something done that makes it easy to maintain long-term and that even <a href="https://infosec.space/tags/GrapheneOS" class="mention hashtag" rel="nofollow noopener" target="_blank">#GrapheneOS</a> are willing to support.<ul><li>Until then the <a href="https://infosec.space/tags/Enshittification" class="mention hashtag" rel="nofollow noopener" target="_blank">#Enshittification</a> is ruining everything as usual...</li></ul>

Gea-Suan Lin真的有人寄信要 GPL 授權的 copy...Hacker News 上看到 2022 年的文章：「I wrote to the address in the GPLv2 license notice (2022) (mendhak.com)」，原文在「I wrote to the address in the GPLv2 license notice and received the GPLv3 license」。作者在 GPLv2 看到這段： You should have received a copy of the GNU General Public License along with this program; if not, write to the Free Software Foundation, Inc., 5…<a href="https://blog.gslin.org/archives/2025/04/25/12366/%e7%9c%9f%e7%9a%84%e6%9c%89%e4%ba%ba%e5%af%84%e4%bf%a1%e8%a6%81-gpl-%e6%8e%88%e6%ac%8a%e7%9a%84-copy/" rel="nofollow noopener" translate="no" target="_blank">https://blog.gslin.org/archives/2025/04/25/12366/%e7%9c%9f%e7%9a%84%e6%9c%89%e4%ba%ba%e5%af%84%e4%bf%a1%e8%a6%81-gpl-%e6%8e%88%e6%ac%8a%e7%9a%84-copy/</a><a href="https://abpe.org/tags/copy" class="mention hashtag" rel="nofollow noopener" target="_blank">#copy</a> <a href="https://abpe.org/tags/fsf" class="mention hashtag" rel="nofollow noopener" target="_blank">#fsf</a> <a href="https://abpe.org/tags/gnu" class="mention hashtag" rel="nofollow noopener" target="_blank">#gnu</a> <a href="https://abpe.org/tags/gpl" class="mention hashtag" rel="nofollow noopener" target="_blank">#gpl</a> <a href="https://abpe.org/tags/gplv2" class="mention hashtag" rel="nofollow noopener" target="_blank">#gplv2</a> <a href="https://abpe.org/tags/gplv3" class="mention hashtag" rel="nofollow noopener" target="_blank">#gplv3</a> <a href="https://abpe.org/tags/hard" class="mention hashtag" rel="nofollow noopener" target="_blank">#hard</a> <a href="https://abpe.org/tags/license" class="mention hashtag" rel="nofollow noopener" target="_blank">#license</a> <a href="https://abpe.org/tags/mail" class="mention hashtag" rel="nofollow noopener" target="_blank">#mail</a> <a href="https://abpe.org/tags/public" class="mention hashtag" rel="nofollow noopener" target="_blank">#public</a>

Hacker NewsI wrote to the address in the GPLv2 license notice<a href="https://code.mendhak.com/gpl-v2-address-letter/" rel="nofollow noopener" translate="no" target="_blank">https://code.mendhak.com/gpl-v2-address-letter/</a><a href="https://mastodon.social/tags/HackerNews" class="mention hashtag" rel="nofollow noopener" target="_blank">#HackerNews</a> <a href="https://mastodon.social/tags/GPLv2" class="mention hashtag" rel="nofollow noopener" target="_blank">#GPLv2</a> <a href="https://mastodon.social/tags/OpenSource" class="mention hashtag" rel="nofollow noopener" target="_blank">#OpenSource</a> <a href="https://mastodon.social/tags/SoftwareLicensing" class="mention hashtag" rel="nofollow noopener" target="_blank">#SoftwareLicensing</a> <a href="https://mastodon.social/tags/HackerNews" class="mention hashtag" rel="nofollow noopener" target="_blank">#HackerNews</a> <a href="https://mastodon.social/tags/TechCommunity" class="mention hashtag" rel="nofollow noopener" target="_blank">#TechCommunity</a> <a href="https://mastodon.social/tags/GPL" class="mention hashtag" rel="nofollow noopener" target="_blank">#GPL</a>

Kevin Karhan :verified:<a href="https://diaspodon.fr/@AugierLe42e" class="u-url mention" rel="nofollow noopener" target="_blank">@AugierLe42e</a> I assume that port is fixed to a specific USB Hub / Controller / Port and the button is similarly linked to some GPIO / I²C / PS/2 port...<ul><li>What you can do is check <code>lsusb</code> for <a href="https://infosec.space/tags/USB" class="mention hashtag" rel="nofollow noopener" target="_blank">#USB</a> devices and see if the specific port in question has a USB mass storage device or SATA bridge chip attached to it when said button is pressed.</li></ul>If <a href="https://infosec.space/tags/QNAP" class="mention hashtag" rel="nofollow noopener" target="_blank">#QNAP</a> used <a href="https://infosec.space/tags/Linux" class="mention hashtag" rel="nofollow noopener" target="_blank">#Linux</a> they should've provided those drivers / scripts as part of their <a href="https://infosec.space/tags/GPLv2" class="mention hashtag" rel="nofollow noopener" target="_blank">#GPLv2</a> obligations to buyers/owners of said <a href="https://infosec.space/tags/NAS" class="mention hashtag" rel="nofollow noopener" target="_blank">#NAS</a> boxes.<ul><li>Just don't expect any of that code to be useable, as <a href="https://mstdn.jp/@landley" class="u-url mention" rel="nofollow noopener" target="_blank">@landley</a> can attest from the <a href="https://infosec.space/tags/BusyBox" class="mention hashtag" rel="nofollow noopener" target="_blank">#BusyBox</a> license enforcement…</li></ul>Either way if you can reliably identify the port & detect the button presses that should be sufficient to build like a <a href="https://infosec.space/tags/bash" class="mention hashtag" rel="nofollow noopener" target="_blank">#bash</a> or <a href="https://infosec.space/tags/python" class="mention hashtag" rel="nofollow noopener" target="_blank">#python</a> script to basically detect the drive, mount it and <code>cp -r /dev/$DRIVE/ /home/copied_drives/$LABEL/</code> <ul><li>It may need some fiddling and will most likely only work reliably on unencrypted drives with ext2-ext4, btrfs, ntfs, fat32, exfat filesystems...</li></ul>Pretty shure you'll have to tweak a bit unless you want to use <code>/dev/by-uuid/$UUID</code> and the UUIDs of the partitions as name...

Mark Gardner<a href="https://mastodon.social/@nixCraft" class="u-url mention" rel="nofollow noopener" target="_blank">@nixCraft</a> Those <a href="https://fosstodon.org/@homebrew" class="u-url mention" rel="nofollow noopener" target="_blank">@homebrew</a> instructions for <a href="https://social.sdf.org/tags/macOS" class="mention hashtag" rel="nofollow noopener" target="_blank">#macOS</a> on your web page will not help the circa-2006 <a href="https://social.sdf.org/tags/rsync" class="mention hashtag" rel="nofollow noopener" target="_blank">#rsync</a> 2.6.9 <a href="https://social.sdf.org/tags/Apple" class="mention hashtag" rel="nofollow noopener" target="_blank">#Apple</a> pre-installs at `/usr/bin/rsync`They probably stopped with that version because it was the last one to be <a href="https://social.sdf.org/tags/GPLv2" class="mention hashtag" rel="nofollow noopener" target="_blank">#GPLv2</a> licensed: <a href="https://rsync.samba.org/GPL2.html" rel="nofollow noopener" translate="no" target="_blank">https://rsync.samba.org/GPL2.html</a>Thanks <a href="https://hostux.social/@fsf" class="u-url mention" rel="nofollow noopener" target="_blank">@fsf</a>!

jbz🍏 macOS No Longer Ships with Emacs — Bozhidar Batsov｢ The answer to the first question turned out to be Apple being opposed to using anything licensed under GPL v3, and so it happens that Emacs 22.1 was the last Emacs version licensed under GPL v2 ｣<a href="https://batsov.com/articles/2025/01/12/macos-no-longer-ships-with-emacs/" rel="nofollow noopener" translate="no" target="_blank">https://batsov.com/articles/2025/01/12/macos-no-longer-ships-with-emacs/</a><a href="https://indieweb.social/tags/emacs" class="mention hashtag" rel="nofollow noopener" target="_blank">#emacs</a> <a href="https://indieweb.social/tags/macos" class="mention hashtag" rel="nofollow noopener" target="_blank">#macos</a> <a href="https://indieweb.social/tags/gplv2" class="mention hashtag" rel="nofollow noopener" target="_blank">#gplv2</a>

LibreQoSYou can find us on <a href="https://fosstodon.org/tags/GitHub" class="mention hashtag" rel="nofollow noopener" target="_blank">#GitHub</a> obviously, as well:<a href="https://github.com/LibreQoE/LibreQoS" rel="nofollow noopener" translate="no" target="_blank">https://github.com/LibreQoE/LibreQoS</a>Oh, and <a href="https://fosstodon.org/tags/LibreQoS" class="mention hashtag" rel="nofollow noopener" target="_blank">#LibreQoS</a> is <a href="https://fosstodon.org/tags/GPLv2" class="mention hashtag" rel="nofollow noopener" target="_blank">#GPLv2</a>.<a href="https://fosstodon.org/tags/QualityOfExperience" class="mention hashtag" rel="nofollow noopener" target="_blank">#QualityOfExperience</a> <a href="https://fosstodon.org/tags/OpenSource" class="mention hashtag" rel="nofollow noopener" target="_blank">#OpenSource</a> <a href="https://fosstodon.org/tags/QoE" class="mention hashtag" rel="nofollow noopener" target="_blank">#QoE</a> <a href="https://fosstodon.org/tags/FLOSS" class="mention hashtag" rel="nofollow noopener" target="_blank">#FLOSS</a> <a href="https://fosstodon.org/tags/bufferbloat" class="mention hashtag" rel="nofollow noopener" target="_blank">#bufferbloat</a> <a href="https://fosstodon.org/tags/latency" class="mention hashtag" rel="nofollow noopener" target="_blank">#latency</a> <a href="https://fosstodon.org/tags/jitter" class="mention hashtag" rel="nofollow noopener" target="_blank">#jitter</a> <a href="https://fosstodon.org/tags/ISP" class="mention hashtag" rel="nofollow noopener" target="_blank">#ISP</a> <a href="https://fosstodon.org/tags/WISP" class="mention hashtag" rel="nofollow noopener" target="_blank">#WISP</a> <a href="https://fosstodon.org/tags/FISP" class="mention hashtag" rel="nofollow noopener" target="_blank">#FISP</a> <a href="https://fosstodon.org/tags/QoS" class="mention hashtag" rel="nofollow noopener" target="_blank">#QoS</a> <a href="https://fosstodon.org/tags/broadband" class="mention hashtag" rel="nofollow noopener" target="_blank">#broadband</a> <a href="https://fosstodon.org/tags/QualityOfService" class="mention hashtag" rel="nofollow noopener" target="_blank">#QualityOfService</a> <a href="https://fosstodon.org/tags/FWA" class="mention hashtag" rel="nofollow noopener" target="_blank">#FWA</a> <a href="https://fosstodon.org/tags/InternetServiceProvider" class="mention hashtag" rel="nofollow noopener" target="_blank">#InternetServiceProvider</a> <a href="https://fosstodon.org/tags/fiber" class="mention hashtag" rel="nofollow noopener" target="_blank">#fiber</a> RFC8290 <a href="https://fosstodon.org/tags/FQ_CoDel" class="mention hashtag" rel="nofollow noopener" target="_blank">#FQ_CoDel</a> <a href="https://fosstodon.org/tags/sch_CAKE" class="mention hashtag" rel="nofollow noopener" target="_blank">#sch_CAKE</a> <a href="https://fosstodon.org/tags/FQCoDel" class="mention hashtag" rel="nofollow noopener" target="_blank">#FQCoDel</a> <a href="https://fosstodon.org/tags/schCAKE" class="mention hashtag" rel="nofollow noopener" target="_blank">#schCAKE</a> <a href="https://fosstodon.org/tags/WiFi" class="mention hashtag" rel="nofollow noopener" target="_blank">#WiFi</a> <a href="https://fosstodon.org/tags/speedtest" class="mention hashtag" rel="nofollow noopener" target="_blank">#speedtest</a>

Kevin Karhan :verified:<a href="https://infosec.exchange/@FritzAdalis" class="u-url mention" rel="nofollow noopener" target="_blank">@FritzAdalis</a> <a href="https://defcon.social/@fl0und3r" class="u-url mention" rel="nofollow noopener" target="_blank">@fl0und3r</a> <a href="https://xyzzy.link/users/fence" class="u-url mention" rel="nofollow noopener" target="_blank">@fence</a> Granted, <a href="https://infosec.space/tags/OpenBSD" class="mention hashtag" rel="nofollow noopener" target="_blank">#OpenBSD</a> usually removes <a href="https://infosec.space/tags/complexity" class="mention hashtag" rel="nofollow noopener" target="_blank">#complexity</a> and stuff that can't be <a href="https://infosec.space/tags/secured" class="mention hashtag" rel="nofollow noopener" target="_blank">#secured</a> to their standards, and I do applaud them for that.<ul><li>Even tho it comes at the cost of a system that isn't easy to get started with, since one's experience and intuition from <a href="https://infosec.space/tags/Linux" class="mention hashtag" rel="nofollow noopener" target="_blank">#Linux</a> won't help one here...</li></ul>That being said even tho I despise <a href="https://infosec.space/tags/Netflix" class="mention hashtag" rel="nofollow noopener" target="_blank">#Netflix</a>, they moved to <a href="https://infosec.space/tags/FreeBSD" class="mention hashtag" rel="nofollow noopener" target="_blank">#FreeBSD</a> as that cuts down on their specific hardware needs, which is ne net and gross positive for the world and <a href="https://infosec.space/tags/BSD" class="mention hashtag" rel="nofollow noopener" target="_blank">#BSD</a>'s as they'll need less hardware, datacenter floorspace, cooling, power and thus reduce the impact of their business.<ul><li>Tho it's not because Netflix is envoirmentally concious or some other <a href="https://infosec.space/tags/greenwashing" class="mention hashtag" rel="nofollow noopener" target="_blank">#greenwashing</a> reason, but because their infrastructure is more expensive than personnel and cutting down 5% cost at that is saving them millions even if they pay their BSD engineers 10x to their Linux counterparts.</li></ul>OFC for <a href="https://infosec.space/tags/commercial" class="mention hashtag" rel="nofollow noopener" target="_blank">#commercial</a> users, BSDs are always more preferable as <a href="https://infosec.space/tags/GPLv2" class="mention hashtag" rel="nofollow noopener" target="_blank">#GPLv2</a> of <a href="https://infosec.space/tags/Linux" class="mention hashtag" rel="nofollow noopener" target="_blank">#Linux</a> would basically make it hard to do the "security by obscurity" part of <a href="https://infosec.space/tags/DRM" class="mention hashtag" rel="nofollow noopener" target="_blank">#DRM</a> & <a href="https://infosec.space/tags/CopyProtection" class="mention hashtag" rel="nofollow noopener" target="_blank">#CopyProtection</a> they want on stuff like <a href="https://infosec.space/tags/GameConsoles" class="mention hashtag" rel="nofollow noopener" target="_blank">#GameConsoles</a>. <ul><li>BSD is way more permissive and I do like that.</li></ul>Sadly for many, Linux won for most "mainstream" applications to the point that outside nieche cases, it's a rounding error in statistics.<ul><li>That being said many innovations do get adopted where possible, like <a href="https://infosec.space/tags/OpenZFS" class="mention hashtag" rel="nofollow noopener" target="_blank">#OpenZFS</a> support (tho AFAIK OpenBSD lacks that for the aforementioned complexity reasons)...</li></ul>

Kevin Karhan :verified:<a href="https://mastodon.social/@prem_k" class="u-url mention" rel="nofollow noopener" target="_blank">@prem_k</a> <a href="https://mastodon.social/@silentexception" class="u-url mention" rel="nofollow noopener" target="_blank">@silentexception</a> Well, <a href="https://infosec.space/tags/FLOSS" class="mention hashtag" rel="nofollow noopener" target="_blank">#FLOSS</a> does not require that they need to make it simple for one to do so.Both <a href="https://infosec.space/tags/grsecurity" class="mention hashtag" rel="nofollow noopener" target="_blank">#grsecurity</a> & <a href="https://infosec.space/tags/RedHad" class="mention hashtag" rel="nofollow noopener" target="_blank">#RedHad</a> comply to <a href="https://infosec.space/tags/GPLv2" class="mention hashtag" rel="nofollow noopener" target="_blank">#GPLv2</a> by merely providing <a href="https://infosec.space/tags/paywalled" class="mention hashtag" rel="nofollow noopener" target="_blank">#paywalled</a> access to their repos.They don't need to provide instructions to make reproduceable builds nor documentation nor resources to do so!

lukwoodyI also love the argument of controlling the upstreaming pace because in other words "the drivers aren't ready yet" ... <a href="https://linuxrocks.online/@tuxedocomputers" class="u-url mention" rel="nofollow noopener" target="_blank">@tuxedocomputers</a> why do you sell it to customers if the drivers aren't ready enough for upstreaming... <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://chaos.social/tags/tuxedo" class="mention hashtag" rel="nofollow noopener" target="_blank">#tuxedo</a> <a href="https://chaos.social/tags/gplv2" class="mention hashtag" rel="nofollow noopener" target="_blank">#gplv2</a> <a href="https://chaos.social/tags/linux" class="mention hashtag" rel="nofollow noopener" target="_blank">#linux</a>

Fabián Rodríguez 🛡💾 🇨🇴 🌴FreeCAD Version 1.0 Released - <a href="https://mastodon.social/tags/FreeCAD" class="mention hashtag" rel="nofollow noopener" target="_blank">#FreeCAD</a> is an open-source parametric 3D <a href="https://mastodon.social/tags/CAD" class="mention hashtag" rel="nofollow noopener" target="_blank">#CAD</a> (Computer-Aided Design) modeling tool. It's primarily used for designing and engineering products in various fields such as mechanical engineering, product design, and architecture. This release marks FreeCAD's readiness for extensive real-world applications, reflecting the dedicated efforts of its community.<a href="https://blog.freecad.org/2024/11/19/freecad-version-1-0-released/" rel="nofollow noopener" translate="no" target="_blank">https://blog.freecad.org/2024/11/19/freecad-version-1-0-released/</a><a href="https://mastodon.social/tags/freesoftware" class="mention hashtag" rel="nofollow noopener" target="_blank">#freesoftware</a> <a href="https://mastodon.social/tags/autocad" class="mention hashtag" rel="nofollow noopener" target="_blank">#autocad</a> <a href="https://mastodon.social/tags/opensource" class="mention hashtag" rel="nofollow noopener" target="_blank">#opensource</a> <a href="https://mastodon.social/tags/GPLv2" class="mention hashtag" rel="nofollow noopener" target="_blank">#GPLv2</a>

Thorsten Leemhuis (acct. 1/4)7/ To follow up once more, likely for the last time: Werner Sembach relicensed the last of the formerly GPL3+ed <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 from <a href="https://linuxrocks.online/@tuxedocomputers" class="u-url mention" rel="nofollow noopener" target="_blank">@tuxedocomputers</a> to <a href="https://fosstodon.org/tags/GPLv2" class="mention hashtag" rel="nofollow noopener" target="_blank">#GPLv2</a> about an hour ago after all external contributors have agreed to that move. 👏 <a href="https://gitlab.com/tuxedocomputers/development/packages/tuxedo-drivers/-/commits/main" rel="nofollow noopener" translate="no" target="_blank">https://gitlab.com/tuxedocomputers/development/packages/tuxedo-drivers/-/commits/main</a>Cc: <a href="https://chaos.social/@waldi" class="u-url mention" rel="nofollow noopener" target="_blank">@waldi</a> <a href="https://fosstodon.org/tags/LinuxKernel" class="mention hashtag" rel="nofollow noopener" target="_blank">#LinuxKernel</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>

Frühere Suchanfragen

Suchoptionen

Verwaltet von:

Serverstatistik:

#gplv2