GitHub | load more | comedy gold
Only two.
#GitHub #UX #interject #hidden #history #OSS #legal #LGPL #GPL #licence #licencing #fork #revert
#LGPL
You're speculating on the reasons #SCOTUS denied cert. There is nothing in their denial that supports your argument.
The big picture stakes are high (of course). Focusing on a year-old case as if it actually tells us something new merely because SCOTUS denied cert is just a mechanism for spreading FUD.
Here's a full analysis of the entire DC Circuit Ruling:
https://sfconservancy.org/blog/2026/mar/04/scotus-deny-cert-dc-circuit-thaler-appeal-llm-ai/
Cc: @downey
@soller I'm relying primarily on hard-work, regular research, and constant vigilance, not luck and not FUD.
It is not time to panic.
I urge folks to read what #SFC has published on #LLM's & #AI
The biggest problem we have is the funding gap between those of us trying to save #copyleft & those who are creating the problem.
We'll need less luck and be able to more easily apply the other skills I mentioned if folks support #SoftwareFreedom Conservancy.
OP (see uphtread) has misunderstood this (year old) Court ruling quite a bit.
It's ok—we all make mistakes. The important task now is to correct the mistake.
I encourage boosting of this reply to address & draw attention boost to the prior error.
I assure you #copyleft (& software itself) *are not* seriously impacted by this ruling, and #SFC remains constantly vigilant on these matters.
https://sfconservancy.org/blog/2026/mar/04/scotus-deny-cert-dc-circuit-thaler-appeal-llm-ai/
IANAL but AFAIK @soller isn't either.
Cc: @downey
#LLM #AI #legal #Court #GPL #LGPL
Salvatore Sanfilippo (@antirez) and Armin Ronacher (@mitsuhiko) both argue that #AI reimplementation of #copyleft libraries is fine. Their legal reasoning might be correct. That's not the point.
Legal and legitimate are different things—and both pieces quietly assume otherwise.
https://writings.hongminhee.org/2026/03/legal-vs-legitimate/
¹ At #SCaLE2026, #SFC is again the Network Sponsor. For the 2nd year, the entire #SCaLE network is operating on #OpenWrt One's — the only wireless router hardware in history to comply with #GPL & #LGPL from Day 0 *&* have no proprietary software² for its operating system & UI.
Want One? Visit #SoftwareFeedom Conservancy's booth (on left entering expo hall) to buy One (while supplies last).
Not at #SCaLE? https://sfconservancy.org/activities/openwrt-one.html
²It does have binary blobs on some components.
#Chardet : quand une #IA réécrit un logiciel #opensource #foss en cinq jours et change sa #licence , sans vergogne de #LGPL à #MIT ...
Vide #juridique total...
korben.info/chardet-quan...
Chardet : quand une IA réécrit...
#Chardet : quand une #IA réécrit un logiciel #opensource #foss en cinq jours et change sa #licence , sans vergogne de #LGPL à #MIT ...
Vide #juridique total...
An interesting #licence war is happening in the #Python world.
The popular `chardet` package has apparently been re-written (by assistance of the Claude #LLM). Undergoing this *version* change to v 7.0.0 the current maintainer has shifted the licence away from the #LGPL to the more permissive MIT licence.
I'm not a lawyer, and I don't know about the deeper backgrounds. While a complete clean slate implementation may justify a different licence, I don't think that anyone who's been maintaining a package for years can claim complete lack of influence on the existing code base. So a licence change from one version to another without consent of the (original) contributors seems wildly inadmissible.
Additionally, if the author claims a complete re-write using Claude, in many jurisdictions (including the US) AI generated content cannot be IP protected. So in that case he'd have had to remove the #copyright (c) claim to his name as well to be at least consistent with the narrative.
This is completely independent of the authenticity of the supposed statement by Mark Pilgrim (original author) of `chardet`.
I'm interested to hear what others think ...
https://www.theregister.com/2026/03/06/ai_kills_software_licensing/
@simon Obviously! The source code is: that code required to produce the binary. That code was LGPL. It doesn't matter how many algorithms, nor the nature of the algorithms, it goes through to become those 1s and 0s.
#law #lawfare #computerScience #intellectualProperty #licensing #FOSS #GNU #LGPL #MIT #code #softwareEngineering #LLM #codeWashing
"AI" LLM-based licensewashing of LGPL code ... by the project maintainer.
What the hell is wrong with these folks? Token go in, brain fall out.
Getting a program to "rewrite" your code doesn't nullify the copyright ownership or license terms of everything that went before it. You need a clean-room reimplementation from a bare spec for that, and LLMs *by definition* can't do that.
https://github.com/chardet/chardet/releases/tag/7.0.0
#FFS.
#AI #LLM #OpenSource #FreeSoftware #license #licensing #LGPL #GPL #CleanRoom #reimplementation
The article about the issue in this subthread is now published: https://sfconservancy.org/blog/2026/mar/04/scotus-deny-cert-dc-circuit-thaler-appeal-llm-ai/
To @maxine's larger point in the OP, #SFC is putting serious work in the next few months into issues related to #LLM-backed #AI agents and their impact and implications for #FOSS. Nothing beyond that to report at this very moment, as it's a work in progress, but please watch #SoftwareFreedom Conservancy's website for announcements in coming months.
I wonder what the best #OpenSource license for some unimportant hobby project libraries is? I want to allow it to be used in projects of any kind of license, but want to require any changes on the library itself to be published under the same license. There is #MPL (2), #CDDL (1.1), #EPL (2), #LGPL (2 or 3). LGPL doesn't allow static linking, and I want to allow that. Though when the library is a dynamic scripting language that isn't really relevant, I suppose.
🌐 Có ai biết giấy phép nào nằm giữa LGPL và MPL2 không? MPL cho phép fork đóng nguồn nếu thay đổi trong file mới; LGPL có quy tắc liên kết phức tạp; ngoại lệ classpath với GPL có thể hoạt động nhưng GitHub không phát hiện. Bạn có đề xuất nào? #OpenSource #License #LGPL #MPL2 #GNU #PhầnMềmMãNguồn #GiấyPhép
Des retours d'expériences sur vos projets en MIT, LGPL3 ou GPL3. Des regrets d'avoir choisi l'un plus que l'autre ? #opensource #licence #mit #gpl #lgpl
Do you like Ruby? Do you like Terminal User Interfaces (TUIs)? Then you might LOVE this!
https://man.sr.ht/~kerrick/ratatui_ruby/
#TUI #Ruby #Rust #Ratatui #Software #Architecture #Design #Roadmap #OpenSource #LGPL
FFmpeg reicht DMCA-Takedown gegen Rockchip ein
https://linuxnews.de/ffmpeg-reicht-dmca-takedown-gegen-rockchip-ein/ #ffmpeg #dmca #rockchip #lgpl #linux #linuxnews
@skyfaller, to add to what @ossguy said, I think a #copyleft-@next should clearly state that the 3ʳᵈ party beneficiary right to users is intended. While it was clearly intended by #GPL & #LGPL, we've had to spend 5 years & substantial resources in #SFC's case against #Vizio to adjudicate 3PB under copyleft.
Decades of copyleft litigation has taught me that you really do need to say explicitly in the license text what is obvious to everyone, as bad actors love to be disingenuous.
#LGPL permits combos w/ source-available licenses (source provided:no right to modify (beyond building),no commercial redistribution,etc) for proprietary #Rust code but users can modify LGPL'd portions & rebuild/relink/install.
Clearly Rust folks decided —as a *technical* matter— everyone should have source at build time.
Now, if the real goal of Rust is to forbid users from having source for anything…then #FOSS & Rust are less compatible than I imagined anyway.
Client Info
Server: https://mastodon.social
Version: 2025.07
Repository: https://github.com/cyevgeniy/lmst