Shakedown Social

Simon Brooke<a href="https://f.duriansoftware.com/@joe" class="u-url mention" rel="nofollow noopener" target="_blank">@joe</a> related, it seems to me that, as Microsoft's <a href="https://mastodon.scot/tags/copilot" class="mention hashtag" rel="nofollow noopener" target="_blank">#copilot</a> has been trained on <a href="https://mastodon.scot/tags/GPL" class="mention hashtag" rel="nofollow noopener" target="_blank">#GPL</a> licensed code, it must be assumed that any code generated with assistance from copilot contains GPL code and is therefore itself automatically subject to the GPL (either 2 0 or, at your option, any subsequent version).

YogthosThe context of companies wanting to rip out copyleft from Linux makes the push for Rust rewrites make a lot more sense. <a href="https://techrights.org/n/2025/03/19/Sami_Tikkanen_Explains_on_Rust_Language_and_Its_Goals.shtml" rel="nofollow noopener" translate="no" target="_blank">https://techrights.org/n/2025/03/19/Sami_Tikkanen_Explains_on_Rust_Language_and_Its_Goals.shtml</a><a href="https://social.marxist.network/tags/gpl" class="mention hashtag" rel="nofollow noopener" target="_blank">#gpl</a> <a href="https://social.marxist.network/tags/linux" class="mention hashtag" rel="nofollow noopener" target="_blank">#linux</a>

Bradley M. Kuhn<a href="https://mastodon.social/@blogdiva" class="u-url mention" rel="nofollow noopener" target="_blank">@blogdiva</a>This is a job for <a href="https://fedi.copyleft.org/tags/GPL" class="mention hashtag" rel="nofollow noopener" target="_blank">#GPL</a> enforcement. Are you familiar with the Vizio case? <a href="https://sfc.ngo/vizio" rel="nofollow noopener" translate="no" target="_blank">https://sfc.ngo/vizio</a>The <a href="https://fedi.copyleft.org/tags/Vizio" class="mention hashtag" rel="nofollow noopener" target="_blank">#Vizio</a> case is impact litigation on these very issues you raise.We would love the <a href="https://mastodon.social/@eff" class="u-url mention" rel="nofollow noopener" target="_blank">@eff</a> 's help of course if they were perhaps interested.Cc: <a href="https://mastodon.km6g.us/@kevin" class="u-url mention" rel="nofollow noopener" target="_blank">@kevin</a>

Digital Mark λ ☕️ 🕹 🙄<a href="https://fe.disroot.org/users/ramin_hal9001" class="u-url mention" rel="nofollow noopener" target="_blank">@ramin_hal9001</a> Corpos already steal copyrighted text & code with LLMs, they don't care about the license at all.BSD isn't to protect my code from ever being used by a corpo, which I know can't be stopped. It's to make it convenient for other people to use. I care about the teams of ONE or TWO who want something.I can't use GPL shit, unless I make everything GPL. Or AGPL. Or v2 or v3. Or LGPL. Can I link to the proprietary library I need? NOPE. <a href="https://appdot.net/tags/bsdlicense" class="mention hashtag" rel="nofollow noopener" target="_blank">#bsdlicense</a> <a href="https://appdot.net/tags/bsd" class="mention hashtag" rel="nofollow noopener" target="_blank">#bsd</a> <a href="https://appdot.net/tags/mit" class="mention hashtag" rel="nofollow noopener" target="_blank">#mit</a> <a href="https://appdot.net/tags/mitlicense" class="mention hashtag" rel="nofollow noopener" target="_blank">#mitlicense</a> <a href="https://appdot.net/tags/gpl" class="mention hashtag" rel="nofollow noopener" target="_blank">#gpl</a>

Ramin Honary<a href="https://grell.dev/blog/ai_rejection" rel="nofollow noopener" target="_blank">Another reason to use the GPL software license, over MIT or BSD</a> In short, GPL uses copyright law to protect you, as an author of software, from exploitation better than MIT or BSD software licenses do. Here we have a case of the Anthropic corporation using MIT-licensed code in one of their software products, which is of course a for-profit product. The original author of that code received no compensation, as it is not required by the license. So the author applied for a job at Anthropic, and ironically, Anthropic responded with an AI-generated rejection letter. Corporations like Anthropic seem to have an allergy to GPL-licensed code however, due to the nature of how the GPL license grants much more specific rights and restrictions, both to the authors of the code, and the companies who use it.Of course, nowadays LLMs can ingest GPL and MIT/BSD licensed code and spit it back out in altered form, essentially letting the makers of the LLM profit from your work without compensating you, so the GPL is probably due for an “upgrade” to prevent use for AI training. Unfortunately thanks to regulatory capture, and not-so-impartial courts of law mostly ignoring copyright law nowadays, it might not even be possible to use GPL or copyright to protect authors of software anymore. Probably a whole new legal framework is required first, and I don’t think this will be happening any time soon.<a class="hashtag" href="https://fe.disroot.org/tag/tech" rel="nofollow noopener" target="_blank">#tech</a> <a class="hashtag" href="https://fe.disroot.org/tag/software" rel="nofollow noopener" target="_blank">#software</a> <a class="hashtag" href="https://fe.disroot.org/tag/ai" rel="nofollow noopener" target="_blank">#AI</a> <a class="hashtag" href="https://fe.disroot.org/tag/gpl" rel="nofollow noopener" target="_blank">#GPL</a> <a class="hashtag" href="https://fe.disroot.org/tag/mitlicense" rel="nofollow noopener" target="_blank">#MITLicense</a> <a class="hashtag" href="https://fe.disroot.org/tag/bsdlicense" rel="nofollow noopener" target="_blank">#BSDLicense</a> <a class="hashtag" href="https://fe.disroot.org/tag/gpllicense" rel="nofollow noopener" target="_blank">#GPLLicense</a> <a class="hashtag" href="https://fe.disroot.org/tag/freesoftware" rel="nofollow noopener" target="_blank">#FreeSoftware</a> <a class="hashtag" href="https://fe.disroot.org/tag/foss" rel="nofollow noopener" target="_blank">#FOSS</a> <a class="hashtag" href="https://fe.disroot.org/tag/floss" rel="nofollow noopener" target="_blank">#FLOSS</a>

Simon Brooke<a href="https://mastodon.social/@lolaodelola" class="u-url mention" rel="nofollow noopener" target="_blank">@lolaodelola</a> <a href="https://mastodon.scot/tags/OpenSource" class="mention hashtag" rel="nofollow noopener" target="_blank">#OpenSource</a> and <a href="https://mastodon.scot/tags/FreeSoftware" class="mention hashtag" rel="nofollow noopener" target="_blank">#FreeSoftware</a> maintainers deserve (and need) to be paid, if free software is to be reliably maintained as corporate users demand that it should be.Dual licensing is one mechanism to do that.I prefer the use of the <a href="https://mastodon.scot/tags/GPL" class="mention hashtag" rel="nofollow noopener" target="_blank">#GPL</a>, however, even if it deters corporate use, precisely because of its virality. Yes, corporates MAY use my work -- provided that they share theirs.

David<a href="https://mastodon.social/@glynmoody" class="u-url mention" rel="nofollow noopener" target="_blank">@glynmoody</a> <a href="https://infosec.exchange/tags/Microsoft" class="mention hashtag" rel="nofollow noopener" target="_blank">#Microsoft</a> does have one viable solution, and it would require relinquishing some control. It would work like this: <ol><li>Pay a European law firm to create an independent (i.e., non-subsidiary—not owned or controlled by Microsoft or any of its officers) <a href="https://infosec.exchange/tags/EU" class="mention hashtag" rel="nofollow noopener" target="_blank">#EU</a> corporation; call it something like "Microsoft Europe." That corporation must have solely EU-resident EU citizens constituting its officers (board, directors, and voting shareholders). </li><li>Irrevocably license all Microsoft [US] IP involved in software or services used by EU principals to Microsoft Europe, as part of a contractual agreement requiring Microsoft Europe to follow Microsoft [US] direction except as contraindicated by EU or member-state law. Agree to allow Microsoft Europe to relicense under EU, rather than US, law, whenever providing products or services to EU customers, then have Microsoft Europe do so. </li><li>Include with the license all complete and corresponding source code (by the <a href="https://infosec.exchange/tags/GPL" class="mention hashtag" rel="nofollow noopener" target="_blank">#GPL</a> definition), and include in the contract an NDA prohibiting any reuse or redistribution of all but the open-source parts of that source code except as strictly necessary (by the <a href="https://infosec.exchange/tags/GDPR" class="mention hashtag" rel="nofollow noopener" target="_blank">#GDPR</a> definition) to fulfil license or contractual obligations to EU customers or to comply with EU or member state law. </li><li>Charge licensing feeds to Microsoft Europe equal to everything in excess of their operating costs (just enough personnel to fulfil licenses and contracts to EU suppliers and customers, plus EU-based insurance and legal services). Then Microsoft [US] is out no more revenue than necessary to run an office. </li><li>As the foregoing isolate Microsoft Europe legally and through disjoint org charts, isolate digital systems through cryptography. Make it mathematically impossible for Microsoft [US] to violate EU or member state law regarding EU data, as only Microsoft Europe would be able to access the cryptographic keys controlling confidentiality, availability, or integrity of EU data. </li></ol>The net effect: for the cost of perhaps a few to several million Euros, is that Microsoft [US] could maintain status quo the EU, except insofar as becoming unable to violate EU or member state law at the behest of the US government. The same model can be replicated in other jurisdictions, such as <a href="https://infosec.exchange/tags/Canada" class="mention hashtag" rel="nofollow noopener" target="_blank">#Canada</a>, and by other multinational digital services providers, such as <a href="https://infosec.exchange/tags/Alphabet" class="mention hashtag" rel="nofollow noopener" target="_blank">#Alphabet</a> (Google). To make this happen, EU (and other) governments can require it as a condition of continuing to do business with Microsoft (and other multinationals). Maintaining a monolithic multinational corporation is the legal equivalent of maintaining a flat network. Internationally federating a multinational corporation is the legal equivalent of maintaining a well segmented network. In the coming years, US-based Big Tech companies will need to firewall their non-US operations off from themselves, as outline above. And non-US governments will need to mandate that. The sanctioning of the <a href="https://infosec.exchange/tags/ICC" class="mention hashtag" rel="nofollow noopener" target="_blank">#ICC</a> was already proof of that necessity.

dorotaCThanks to all the awesome answers, this is what I figured out:<a href="https://copyleft.org/guide/" rel="nofollow noopener" translate="no" target="_blank">https://copyleft.org/guide/</a> existsIf the ISP sells me something, they must provide the sources. They can't just pass along the source offer and say it's not their problem.If I buy from a private person, they theoretically pass along the source offer and I can bug the seller.If I buy it from a modder, the modder must give me their mod's sources.Time to go shopping and contact <a href="https://fosstodon.org/tags/telekom" class="mention hashtag" rel="nofollow noopener" target="_blank">#telekom</a> I guess :) <a href="https://fosstodon.org/tags/gpl" class="mention hashtag" rel="nofollow noopener" target="_blank">#gpl</a> <a href="https://fosstodon.org/tags/copyright" class="mention hashtag" rel="nofollow noopener" target="_blank">#copyright</a> <a href="https://fosstodon.org/tags/freesoftware" class="mention hashtag" rel="nofollow noopener" target="_blank">#freesoftware</a>

dorotaCMaybe actually reading the <a href="https://fosstodon.org/tags/GPL" class="mention hashtag" rel="nofollow noopener" target="_blank">#GPL</a> helps:> 3. You may copy and distribute the Program [...] in object code or executable form [...] provided that you also do one of the following: > a) Accompany it with the complete corresponding machine-readable source codeWhen I sell my laptop, there's no "copy", just "distrbute". But if I install Linux on it first, then I "copy and distribute", so sources needed. Does that mean the last person flashing the router is responsible for sources?<a href="https://mastodon.social/@fsfe" class="u-url mention" rel="nofollow noopener" target="_blank">@fsfe</a>

dorotaCAbout <a href="https://fosstodon.org/tags/GPL" class="mention hashtag" rel="nofollow noopener" target="_blank">#GPL</a> .If I buy a second-hand device with <a href="https://fosstodon.org/tags/Linux" class="mention hashtag" rel="nofollow noopener" target="_blank">#Linux</a> on it, who's responsible for giving me the sources?It seems logical to me that the person I bought it from. But good luck getting sources from a private rando ( <a href="https://fosstodon.org/tags/sustainability" class="mention hashtag" rel="nofollow noopener" target="_blank">#sustainability</a> <a href="https://fosstodon.org/tags/reuse" class="mention hashtag" rel="nofollow noopener" target="_blank">#reuse</a> ). On the other hand, my <a href="https://fosstodon.org/tags/ISP" class="mention hashtag" rel="nofollow noopener" target="_blank">#ISP</a> sells me, say a <a href="https://fosstodon.org/tags/Huawei" class="mention hashtag" rel="nofollow noopener" target="_blank">#Huawei</a> device. Is the ISP obliged to give me sources or can they say "it's not our problem" and send me to the manufacturer?<a href="https://fosstodon.org/tags/askfedi" class="mention hashtag" rel="nofollow noopener" target="_blank">#askfedi</a> <a href="https://fosstodon.org/tags/law" class="mention hashtag" rel="nofollow noopener" target="_blank">#law</a> <a href="https://fosstodon.org/tags/copyleft" class="mention hashtag" rel="nofollow noopener" target="_blank">#copyleft</a> <a href="https://fosstodon.org/tags/copyright" class="mention hashtag" rel="nofollow noopener" target="_blank">#copyright</a> <a href="https://fosstodon.org/tags/opensource" class="mention hashtag" rel="nofollow noopener" target="_blank">#opensource</a> <a href="https://fosstodon.org/tags/freesoftware" class="mention hashtag" rel="nofollow noopener" target="_blank">#freesoftware</a>

Hacker NewsIn the long run, GPL code becomes irrelevant (2015)<a href="https://josephg.com/blog/in-the-long-run-gpl-code-becomes-irrelevant/" rel="nofollow noopener" translate="no" target="_blank">https://josephg.com/blog/in-the-long-run-gpl-code-becomes-irrelevant/</a><a href="https://mastodon.social/tags/HackerNews" class="mention hashtag" rel="nofollow noopener" target="_blank">#HackerNews</a> <a href="https://mastodon.social/tags/GPL" class="mention hashtag" rel="nofollow noopener" target="_blank">#GPL</a> <a href="https://mastodon.social/tags/Irrelevance" class="mention hashtag" rel="nofollow noopener" target="_blank">#Irrelevance</a> <a href="https://mastodon.social/tags/OpenSource" class="mention hashtag" rel="nofollow noopener" target="_blank">#OpenSource</a> <a href="https://mastodon.social/tags/Code" class="mention hashtag" rel="nofollow noopener" target="_blank">#Code</a> <a href="https://mastodon.social/tags/LongTerm" class="mention hashtag" rel="nofollow noopener" target="_blank">#LongTerm</a> <a href="https://mastodon.social/tags/SoftwareDevelopment" class="mention hashtag" rel="nofollow noopener" target="_blank">#SoftwareDevelopment</a> <a href="https://mastodon.social/tags/HackerNews" class="mention hashtag" rel="nofollow noopener" target="_blank">#HackerNews</a>

Bradley M. Kuhn<a href="https://mas.to/@carnage4life" class="u-url mention" rel="nofollow noopener" target="_blank">@carnage4life</a> Good point & 🙄 re: Brad Smith. His name is in the top five reasons why I stopped accepting "Brad" as my name circa 2001…I did not wanna share a name with the (then) General Counsel of $MSFT.I think many don't realize that there is a *lawyer* (not a technologist) who has been President of Microsoft for years.Brad Smith is also believed to be (we can't prove it — Microsoft state secrets) the mastermind behind the anti-<a href="https://fedi.copyleft.org/tags/copyleft" class="mention hashtag" rel="nofollow noopener" target="_blank">#copyleft</a> / anti-<a href="https://fedi.copyleft.org/tags/GPL" class="mention hashtag" rel="nofollow noopener" target="_blank">#GPL</a> campaign of the early 2000s.Cc: <a href="https://toot.liw.fi/@liw" class="u-url mention" rel="nofollow noopener" target="_blank">@liw</a>

Dendrobatus Azureus<a href="https://polymaths.social/@rl_dane" class="u-url mention" rel="nofollow noopener" target="_blank">@rl_dane</a> <a href="https://mastodon.bsd.cafe/@Dendrobatus_Azureus" class="u-url mention" rel="nofollow noopener" target="_blank">@Dendrobatus_Azureus</a>Have you made use of the bug report feature to report this to the programmers of KDEconnect?<a href="https://polymaths.social/tags/kdeconnect" class="mention hashtag" rel="nofollow noopener" target="_blank">#KDEConnect</a> <a href="https://polymaths.social/tags/networking" class="mention hashtag" rel="nofollow noopener" target="_blank">#networking</a> <a href="https://polymaths.social/tags/linux" class="mention hashtag" rel="nofollow noopener" target="_blank">#Linux</a> <a href="https://polymaths.social/tags/gnu" class="mention hashtag" rel="nofollow noopener" target="_blank">#GNU</a> <a href="https://polymaths.social/tags/gpl" class="mention hashtag" rel="nofollow noopener" target="_blank">#GPL</a> <a href="https://polymaths.social/tags/posix" class="mention hashtag" rel="nofollow noopener" target="_blank">#POSIX</a> <a href="https://polymaths.social/tags/antennapod" class="mention hashtag" rel="nofollow noopener" target="_blank">#AntennaPod</a> <a href="https://polymaths.social/tags/stories" class="mention hashtag" rel="nofollow noopener" target="_blank">#Stories</a> <a href="https://polymaths.social/tags/mahabharata" class="mention hashtag" rel="nofollow noopener" target="_blank">#Mahabharata</a> <a href="https://polymaths.social/tags/ramayana" class="mention hashtag" rel="nofollow noopener" target="_blank">#Ramayana</a>

Marco BrescianiI've decided to move all my <a href="https://fosstodon.org/tags/FOSS" class="mention hashtag" rel="nofollow noopener" target="_blank">#FOSS</a> projects from <a href="https://fosstodon.org/tags/GPL" class="mention hashtag" rel="nofollow noopener" target="_blank">#GPL</a> to <a href="https://fosstodon.org/tags/EUPL" class="mention hashtag" rel="nofollow noopener" target="_blank">#EUPL</a> .The transition for my digital garden (see profile) on <a href="https://social.anoxinon.de/@Codeberg" class="u-url mention" rel="nofollow noopener" target="_blank">@Codeberg</a> Pages is almost done. Then I'll start with the software things.Any thoughts?

Glyn MoodyCopyleft-Next Project - <a href="https://next.copyleft.org/" rel="nofollow noopener" translate="no" target="_blank">https://next.copyleft.org/</a> "A new, post-post-modern, non-weak copyleft license inspired by, though different from, the GNU <a href="https://mastodon.social/tags/GPL" class="mention hashtag" rel="nofollow noopener" target="_blank">#GPL</a>." <a href="https://mastodon.social/tags/licensing" class="mention hashtag" rel="nofollow noopener" target="_blank">#licensing</a> <a href="https://mastodon.social/tags/freesoftware" class="mention hashtag" rel="nofollow noopener" target="_blank">#freesoftware</a> <a href="https://mastodon.social/tags/opensource" class="mention hashtag" rel="nofollow noopener" target="_blank">#opensource</a>

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.

Jens Finkhäuser<a href="https://infosec.exchange/@mainframed767" class="u-url mention" rel="nofollow noopener" target="_blank">@mainframed767</a> The point being, this isn't a <a href="https://social.finkhaeuser.de/tags/GPL" class="mention hashtag" rel="nofollow noopener" target="_blank">#GPL</a> problem, nor is it an <a href="https://social.finkhaeuser.de/tags/AI" class="mention hashtag" rel="nofollow noopener" target="_blank">#AI</a> issue, it's a way more fundamental issue; the various license flavours matter only in the degree of damage done.The <a href="https://social.finkhaeuser.de/tags/commons" class="mention hashtag" rel="nofollow noopener" target="_blank">#commons</a> doesn't exist to be plundered by <a href="https://social.finkhaeuser.de/tags/RobberBarons" class="mention hashtag" rel="nofollow noopener" target="_blank">#RobberBarons</a>.It's not even there for all of us equally, that is a common mistake (pun intended without apologies). It exists to improve *everybody's* life.Those last two points may seem to say the same thing, but there's a subtle yet important difference.

Soldier of FORTRAN :ReBoot:All the code I write is open source. I do that because I don't want others to have to sweat through the same challenges. I want them to learn from it, change it, make it better. Be part of the community, and hoping that those that use my code give back.I think we need a new GPL license that says "if this code is used by AI to generate new code then that code must also be GPL4"Yes, the gpl should already be doing this, but maybe something more explicit is due.<a href="https://infosec.exchange/tags/foss" class="mention hashtag" rel="nofollow noopener" target="_blank">#foss</a> <a href="https://infosec.exchange/tags/opensource" class="mention hashtag" rel="nofollow noopener" target="_blank">#opensource</a> <a href="https://infosec.exchange/tags/gpl" class="mention hashtag" rel="nofollow noopener" target="_blank">#gpl</a> <a href="https://infosec.exchange/tags/llm" class="mention hashtag" rel="nofollow noopener" target="_blank">#llm</a> <a href="https://infosec.exchange/tags/ai" class="mention hashtag" rel="nofollow noopener" target="_blank">#ai</a>

Recent searches

Search options

Administered by:

Server stats:

#gpl