Kevin Karhan :verified:<p><span class="h-card" translate="no"><a href="https://hachyderm.io/@edboythinks" class="u-url mention" rel="nofollow noopener" target="_blank">@<span>edboythinks</span></a></span> personally I'm in the process of.migrating from <a href="https://infosec.space/tags/Ubuntu" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>Ubuntu</span></a> fonts to <a href="https://infosec.space/tags/B612" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>B612</span></a> because they are superior yet more permissively licensed.</p><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">#<span>SunGalatDemi</span></a> into the <a href="https://infosec.space/tags/Linux" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>Linux</span></a> <a href="https://infosec.space/tags/kernel" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>kernel</span></a> as <a href="https://infosec.space/tags/Console" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>Console</span></a> <a href="https://infosec.space/tags/Font" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>Font</span></a> and <a href="https://infosec.space/tags/license" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>license</span></a>-wise that would not work (<a href="https://infosec.space/tags/CDDL" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>CDDL</span></a> is incompatible with <a href="https://infosec.space/tags/GPLv2" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>GPLv2</span></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">#<span>SSH</span></a> into runs in <a href="https://infosec.space/tags/MDA" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>MDA</span></a> mode thus only has the hardware fonts of that mode anyway...</li></ul>
veganism.social is one of the many independent Mastodon servers you can use to participate in the fediverse.
Veganism Social is a welcoming space on the internet for vegans to connect and engage with the broader decentralized social media community.
Administered by:
Server stats:
292active users
veganism.social: About · Status · Profiles directory · Privacy policy
Mastodon: About · Get the app · Keyboard shortcuts · View source code · v4.4.0-alpha.5
#GPLv2
0 posts · 0 participants · 0 posts today
Kevin Karhan :verified:<p><span class="h-card" translate="no"><a href="https://mastodon.social/@katyswain" class="u-url mention" rel="nofollow noopener" target="_blank">@<span>katyswain</span></a></span> I think <a href="https://infosec.space/tags/GPLv3" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>GPLv3</span></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">#<span>GPL</span></a> and thus causing <a href="https://infosec.space/tags/LicensingConflicts" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>LicensingConflicts</span></a>.</p><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">#<span>IP</span></a>, <a href="https://infosec.space/tags/Patents" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>Patents</span></a> and <a href="https://infosec.space/tags/Licensing" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>Licensing</span></a> works that if caused problems for <a href="https://infosec.space/tags/GPLv2" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>GPLv2</span></a> as well.</li></ul><p>There's a reason why I've chosen <a href="https://infosec.space/tags/0BSD" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>0BSD</span></a> over GPLv3 in many newer projects and even consider changing said license on those that I am the sole contributor of...</p>
Bradley M. Kuhn<p>Today, <span class="h-card" translate="no"><a href="https://mastodon.social/@richardfontana" class="u-url mention" rel="nofollow noopener" target="_blank">@<span>richardfontana</span></a></span> & I restarted, relaunched, & revitalized copyleft-next.</p><p>All versions & variants of <a href="https://floss.social/tags/GPL" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>GPL</span></a> are great licenses. But, today, <a href="https://floss.social/tags/GPLv3" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>GPLv3</span></a> turned 18 years old & <a href="https://floss.social/tags/GPLv2" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>GPLv2</span></a> turned 34 years old.</p><p>At least once in a generation, <a href="https://floss.social/tags/FOSS" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>FOSS</span></a> needs a new approach to strong <a href="https://floss.social/tags/copyleft" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>copyleft</span></a>.</p><p>These posts have details: <a href="https://lists.copyleft.org/pipermail/next/2025q2/000000.html" rel="nofollow noopener" translate="no" target="_blank"><span class="invisible">https://</span><span class="ellipsis">lists.copyleft.org/pipermail/n</span><span class="invisible">ext/2025q2/000000.html</span></a> & <a href="https://fedi.copyleft.org/@next/114769761806288554" rel="nofollow noopener" translate="no" target="_blank"><span class="invisible">https://</span><span class="ellipsis">fedi.copyleft.org/@next/114769</span><span class="invisible">761806288554</span></a></p><p>I ask you to follow <span class="h-card" translate="no"><a href="https://fedi.copyleft.org/@next" class="u-url mention" rel="nofollow noopener" target="_blank">@<span>next</span></a></span> & check out our website at <a href="https://next.copyleft.org/" rel="nofollow noopener" translate="no" target="_blank"><span class="invisible">https://</span><span class="">next.copyleft.org/</span><span class="invisible"></span></a>. </p><p>FYI: I'll migrate this account to @bkuhn@copyleft.org later this week.</p>
copyleft-next<p>Today, we (<span class="h-card" translate="no"><a href="https://floss.social/@bkuhn" class="u-url mention" rel="nofollow noopener" target="_blank">@<span>bkuhn</span></a></span> & <span class="h-card" translate="no"><a href="https://mastodon.social/@richardfontana" class="u-url mention" rel="nofollow noopener" target="_blank">@<span>richardfontana</span></a></span>) excitedly announce that we have restarted, revitalized, and relaunched copyleft-next!</p><p>Today, <a href="https://fedi.copyleft.org/tags/GPLv3" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>GPLv3</span></a> turns exactly 18 years old. This month, <a href="https://fedi.copyleft.org/tags/GPLv2" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>GPLv2</span></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">#<span>FOSS</span></a> needs a new approach to strong <a href="https://fedi.copyleft.org/tags/copyleft" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>copyleft</span></a>.</p><p>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"><span class="invisible">https://</span><span class="ellipsis">lists.copyleft.org/pipermail/n</span><span class="invisible">ext/2025q2/000000.html</span></a> )</p>
100%/0% TAX ✅ ✅<p>This song is released under the GPL-2.0 license as part of the Battle for Wesnoth game and the music is located at </p><p><a href="https://github.com/wesnoth/wesnoth/tree/master/data/core/music" rel="nofollow noopener" translate="no" target="_blank"><span class="invisible">https://</span><span class="ellipsis">github.com/wesnoth/wesnoth/tre</span><span class="invisible">e/master/data/core/music</span></a></p><p>Also described at:</p><p><a href="https://wiki.wesnoth.org/Available_Music" rel="nofollow noopener" translate="no" target="_blank"><span class="invisible">https://</span><span class="ellipsis">wiki.wesnoth.org/Available_Mus</span><span class="invisible">ic</span></a></p><p>Title:<br>Battle Epic</p><p>Author:<br>Doug Kaufman</p><p>official filename:<br>battle-epic.ogg</p><p>If you like this song maybe you want to follow <span class="h-card" translate="no"><a href="https://fosstodon.org/@wesnoth" class="u-url mention" rel="nofollow noopener" target="_blank">@<span>wesnoth</span></a></span></p><p><a href="https://mastodon.social/tags/wesnoth" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>wesnoth</span></a> <a href="https://mastodon.social/tags/WesnothMusic" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>WesnothMusic</span></a> <a href="https://mastodon.social/tags/GameMusic" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>GameMusic</span></a> <a href="https://mastodon.social/tags/music" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>music</span></a> <a href="https://mastodon.social/tags/GPLv2" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>GPLv2</span></a> <a href="https://mastodon.social/tags/soundtrack" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>soundtrack</span></a> <a href="https://mastodon.social/tags/WesnothSoundtrack" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>WesnothSoundtrack</span></a> <a href="https://mastodon.social/tags/FediMusic" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>FediMusic</span></a> <a href="https://mastodon.social/tags/DougKaufman" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>DougKaufman</span></a> <a href="https://mastodon.social/tags/BattleEpic" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>BattleEpic</span></a></p>
Kevin Karhan :verified:<p><span class="h-card" translate="no"><a href="https://go.lema.org/santi" class="u-url mention" rel="nofollow noopener" target="_blank">@<span>santi</span></a></span> <span class="h-card" translate="no"><a href="https://studio8502.ca/@mos_8502" class="u-url mention" rel="nofollow noopener" target="_blank">@<span>mos_8502</span></a></span> <span class="h-card" translate="no"><a href="https://oldbytes.space/@Wintermute_BBS" class="u-url mention" rel="nofollow noopener" target="_blank">@<span>Wintermute_BBS</span></a></span> well, as for <a href="https://infosec.space/tags/GPLv2" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>GPLv2</span></a> and <em>license enforcement</em>, using <a href="https://infosec.space/tags/copyleft" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>copyleft</span></a> as a bat to club corporations with isn't effective.</p><p><span class="h-card" translate="no"><a href="https://mstdn.jp/@landley" class="u-url mention" rel="nofollow noopener" target="_blank">@<span>landley</span></a></span> still feels remorse for having started that with <a href="https://infosec.space/tags/BusyBox" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>BusyBox</span></a>. </p><p>Not to mention <a href="https://infosec.space/tags/GPLv3" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>GPLv3</span></a> & <a href="https://infosec.space/tags/AGPLv3" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>AGPLv3</span></a> really is bad unless one wants to commit <em>"asset denial"</em> aka. be an anticompetitive dickhead and at that point it's close to <em>"asshole licensing"</em> of <a href="https://infosec.space/tags/SSPL" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>SSPL</span></a> & <a href="https://infosec.space/tags/RSAL" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>RSAL</span></a>!</p>
Kevin Karhan :verified:<p><span class="h-card" translate="no"><a href="https://gaysex.cloud/@sodiboo" class="u-url mention" rel="nofollow noopener" target="_blank">@<span>sodiboo</span></a></span> <span class="h-card" translate="no"><a href="https://possum.city/@tauon" class="u-url mention" rel="nofollow noopener" target="_blank">@<span>tauon</span></a></span> <span class="h-card" translate="no"><a href="https://transfem.social/@puppygirlhornypost2" class="u-url mention" rel="nofollow noopener" target="_blank">@<span>puppygirlhornypost2</span></a></span> <span class="h-card" translate="no"><a href="https://possum.city/@silly" class="u-url mention" rel="nofollow noopener" target="_blank">@<span>silly</span></a></span> I don't think it's much of a <em>"<a href="https://infosec.space/tags/freedom" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>freedom</span></a>"</em> on <a href="https://infosec.space/tags/iOS" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>iOS</span></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">#<span>jailbreaker</span></a> to <a href="https://infosec.space/tags/malware" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>malware</span></a> (espechally <a href="https://infosec.space/tags/govware" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>govware</span></a> <a href="https://infosec.space/tags/developers" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>developers</span></a>) want to crack it open result in way more personnel <em>and</em> money behind it.</p><ul><li>OFC the fact that the <a href="https://infosec.space/tags/Android" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>Android</span></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">#<span>regulation</span></a> re: <a href="https://infosec.space/tags/repairability" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>repairability</span></a> and <a href="https://infosec.space/tags/openness" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>openness</span></a> that would make shit work. Most cheap <a href="https://infosec.space/tags/phones" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>phones</span></a> are done with even cheaper <a href="https://infosec.space/tags/SoC" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>SoC</span></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">#<span>Linux</span></a> <a href="https://infosec.space/tags/mainline" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>mainline</span></a> support. (I mean, you've seen the video where <span class="h-card" translate="no"><a href="https://mastodon.social/@SexyCyborg" class="u-url mention" rel="nofollow noopener" target="_blank">@<span>SexyCyborg</span></a></span> 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">#<span>GPLv2</span></a> for her device?)</li></ul><p>Granted <span class="h-card" translate="no"><a href="https://grapheneos.social/@GrapheneOS" class="u-url mention" rel="nofollow noopener" target="_blank">@<span>GrapheneOS</span></a></span> 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">#<span>security</span></a> standards.</p><ul><li>The issues are mostly caused by <em>hostile app developers</em> that specifically decided to <em>knee-jerk</em> their users / customers for no good reason.</li></ul><p>I do wish for both vendors like <a href="https://infosec.space/tags/Fairphone" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>Fairphone</span></a> to up their game <em>and</em> regulators like <span class="h-card" translate="no"><a href="https://ec.social-network.europa.eu/@EUCommission" class="u-url mention" rel="nofollow noopener" target="_blank">@<span>EUCommission</span></a></span> to actually push for more <a href="https://infosec.space/tags/transparency" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>transparency</span></a>, <a href="https://infosec.space/tags/openness" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>openness</span></a> and <a href="https://infosec.space/tags/LongTermSupport" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>LongTermSupport</span></a> of <a href="https://infosec.space/tags/Smartphones" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>Smartphones</span></a>, because <a href="https://infosec.space/tags/ManufacturedEwaste" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>ManufacturedEwaste</span></a> like <a href="https://infosec.space/tags/SOYES" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>SOYES</span></a>, <a href="https://infosec.space/tags/WiKo" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>WiKo</span></a>, <a href="https://infosec.space/tags/Unihertz" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>Unihertz</span></a> and others that ship <a href="https://infosec.space/tags/outdated" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>outdated</span></a> <a href="https://infosec.space/tags/AndroidDevices" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>AndroidDevices</span></a> <em>and</em> never even a <em>single update</em> are a major problem!</p><ul><li>I don't blame projects like <span class="h-card" translate="no"><a href="https://fosstodon.org/@LineageOS" class="u-url mention" rel="nofollow noopener" target="_blank">@<span>LineageOS</span></a></span> that they can't cover <em>every device & SoC</em> even tho they propably have the widest compatibility, I just think that there needs to be <em>pressure</em> that manufacturers don't just vomit stuff on the market and let customers frustratingly figure out the rest.</li></ul><p>I do have to give <a href="https://infosec.space/tags/Apple" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>Apple</span></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">#<span>iOS</span></a> does have consistency and accessibility nailed down very well. Something that they obviously are able being the <em>"<a href="https://infosec.space/tags/BenevolentDictator" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>BenevolentDictator</span></a>"</em> of a <a href="https://infosec.space/tags/SingleVendor" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>SingleVendor</span></a> & <a href="https://infosec.space/tags/SingleProvider" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>SingleProvider</span></a> - platform. </p><ul><li>Obviously since they are the <a href="https://infosec.space/tags/vendor" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>vendor</span></a> for <a href="https://infosec.space/tags/hardware" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>hardware</span></a> and the sole [<em>"legitimate"</em> / <em>official</em>] <a href="https://infosec.space/tags/distributor" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>distributor</span></a> for any <a href="https://infosec.space/tags/Apps" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>Apps</span></a> they do OFC cross-finance their relatively long <a href="https://infosec.space/tags/support" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>support</span></a> with their 15-30% cut from <a href="https://infosec.space/tags/App" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>App</span></a> <a href="https://infosec.space/tags/sales" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>sales</span></a> & <a href="https://infosec.space/tags/InAppPurchase" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>InAppPurchase</span></a>|s they charge, which is why <a href="https://infosec.space/tags/AndroidPhones" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>AndroidPhones</span></a> suffer the <em>"<a href="https://infosec.space/tags/3DO" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>3DO</span></a> syndrome"</em>: 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 <em>"brand value"</em> to care. <a href="https://infosec.space/tags/Google" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>Google</span></a>, <a href="https://infosec.space/tags/Samsing" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>Samsing</span></a>, <a href="https://infosec.space/tags/Fairphone" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>Fairphone</span></a> and very few others do, but most don't as they close the books on the product once launched and sold out (<em>angrily stares at Unihertz</em>)...</li></ul><p>Maybe one day the folks at <span class="h-card" translate="no"><a href="https://fosstodon.org/@frameworkcomputer" class="u-url mention" rel="nofollow noopener" target="_blank">@<span>frameworkcomputer</span></a></span> 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">#<span>Smartphones</span></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">#<span>GrapheneOS</span></a> are willing to support.</p><ul><li>Until then the <a href="https://infosec.space/tags/Enshittification" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>Enshittification</span></a> is ruining everything as usual...</li></ul>
Kevin Karhan :verified:<p><span class="h-card" translate="no"><a href="https://diaspodon.fr/@AugierLe42e" class="u-url mention" rel="nofollow noopener" target="_blank">@<span>AugierLe42e</span></a></span> 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...</p><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">#<span>USB</span></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><p>If <a href="https://infosec.space/tags/QNAP" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>QNAP</span></a> used <a href="https://infosec.space/tags/Linux" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>Linux</span></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">#<span>GPLv2</span></a> obligations to buyers/owners of said <a href="https://infosec.space/tags/NAS" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>NAS</span></a> boxes.</p><ul><li>Just don't expect any of that code to be useable, as <span class="h-card" translate="no"><a href="https://mstdn.jp/@landley" class="u-url mention" rel="nofollow noopener" target="_blank">@<span>landley</span></a></span> can attest from the <a href="https://infosec.space/tags/BusyBox" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>BusyBox</span></a> license enforcement…</li></ul><p>Either way if you can reliably identify the port & detect the button presses that <em>should</em> be sufficient to build like a <a href="https://infosec.space/tags/bash" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>bash</span></a> or <a href="https://infosec.space/tags/python" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>python</span></a> script to basically detect the drive, mount it and <code>cp -r /dev/$DRIVE/ /home/copied_drives/$LABEL/</code> </p><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><p>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...</p>
OS/1337<p>Interestingly, all the people that say "<a href="https://infosec.space/tags/Copilot" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>Copilot</span></a> is violating my <a href="https://infosec.space/tags/Copyright" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>Copyright</span></a>!" and fanboy <a href="https://infosec.space/tags/BusyBox" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>BusyBox</span></a>'s hamfisted approach to <a href="https://infosec.space/tags/GPLv2" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>GPLv2</span></a> enforcement are really quiet when it comes to enforcing <a href="https://infosec.space/tags/GPLv2" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>GPLv2</span></a> against <a href="https://infosec.space/tags/RedHat" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>RedHat</span></a> or <a href="https://infosec.space/tags/grsecurity" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>grsecurity</span></a>... </p><p><a href="https://infosec.space/tags/NotLegalAdvice" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>NotLegalAdvice</span></a> but maybe it's because only those that bought the final product are entitled to the source and <a href="https://infosec.space/tags/learning" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>learning</span></a> isn't <a href="https://infosec.space/tags/CopyrightInfringement" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>CopyrightInfringement</span></a> because otherwise we'd all be lifelong <a href="https://infosec.space/tags/DebtPeons" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>DebtPeons</span></a> to <a href="https://infosec.space/tags/Schoolbook" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>Schoolbook</span></a>- & <a href="https://infosec.space/tags/Textbook" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>Textbook</span></a> <a href="https://infosec.space/tags/authors" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>authors</span></a> or rather their Copyright-holding <a href="https://infosec.space/tags/publishers" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>publishers</span></a>! </p><p><a href="https://felixreda.eu/2021/07/github-copilot-is-not-infringing-your-copyright/" rel="nofollow noopener" translate="no" target="_blank"><span class="invisible">https://</span><span class="ellipsis">felixreda.eu/2021/07/github-co</span><span class="invisible">pilot-is-not-infringing-your-copyright/</span></a></p>
Leafy Greens<p>This is wildly ambitious of me, but who wants to join me in creating a <a href="https://meow.social/tags/FOSS" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>FOSS</span></a> alternative to discord? I believe that we can break the cycle of enshittification by being <a href="https://meow.social/tags/OpenSource" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>OpenSource</span></a> . This is a massive undertaking, though, and I can't do it alone.</p><p>Please boost to spread the word, and reply if you're interested in joining.</p><p><a href="https://meow.social/tags/software" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>software</span></a> <a href="https://meow.social/tags/development" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>development</span></a> <a href="https://meow.social/tags/GPL" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>GPL</span></a> <a href="https://meow.social/tags/GPLv2" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>GPLv2</span></a> <a href="https://meow.social/tags/GPLv3" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>GPLv3</span></a></p>
VegansExploreLive feeds
Mastodon is the best way to keep up with what's happening.
Follow anyone across the fediverse and see it all in chronological order. No algorithms, ads, or clickbait in sight.
Create accountLoginDrag & drop to upload