yoasif

@ yoasif @fedia.io

Posts

12
Comments

8
Joined

3 yr. ago

Technology @piefed.social
yoasif @fedia.io
3d ago

Wikipedia Turned on its Volunteers. Now it’s Coming for its Workers.

www.quippd.com /writing/2026/08/04/wikipedia-turned-on-its-volunteers-now-its-coming-for-its-workers.html

0
4d ago

Wikipedia Turned on its Volunteers. Now it’s Coming for its Workers.
Jump
4

yoasif @fedia.io 4d ago
They did, but that was for contributions. They still sold access to the encyclopedia to big tech so they could train on it to create slop (in violation of the licenses that Wikipedia is licensed under).

4d ago

Wikipedia Turned on its Volunteers. Now it’s Coming for its Workers.

OSM doesn't require you to open derivative works, though - they just require attribution. Kind of a different situation.

Free and Open Source Software @beehaw.org

yoasif @fedia.io

4d ago

Wikipedia Turned on its Volunteers. Now it’s Coming for its Workers.

www.quippd.com /writing/2026/08/04/wikipedia-turned-on-its-volunteers-now-its-coming-for-its-workers.html

4mo ago

AI Code is Hollowing Out Open Source, and Maintainers are Looking the Other Way

Jump

yoasif @fedia.io 4mo ago

I know what copyleft licenses are about, that was covered in the post - if you read it. If you are saying that you are making long comments without reading the post, great I guess, but not super interesting (to me).

I'm not really interested in getting into an argument around license choice because I wasn't advocating for any particular license (like you seem to be).

4mo ago

AI Code is Hollowing Out Open Source, and Maintainers are Looking the Other Way

Jump

yoasif @fedia.io 4mo ago

I said I was focusing on copyleft, cool that you ignored the entire post though. 😑

4mo ago

AI Code is Hollowing Out Open Source, and Maintainers are Looking the Other Way

Jump

yoasif @fedia.io 4mo ago

I think the reimplementation stuff is a separate question because the argument for it working looks a lot stronger, and because it doesn't have anything to do with the source material having LLM output in it. Also if this method holds as legally valid, it's going to be easier to just do that than justify copying code directly (which would probably have to only be copies of the explicitly generated parts of the code, requiring figuring out how to replace the rest), which means it won't matter whether some portion of it was generated.

Is it a separate question, though?

Both works are copyrighted, one is just copyrighted as "all rights reserved" (our leaked commercial code) and the rest is licensed as LGPL. We're putting both pieces of code inside the LLM and then asking the LLM to make a new version.

What makes the action of leaking different from the act of putting it on the web? Rights are reserved in either case.

If they aren't entirely generated, you can't make a full fork, and why would a partial fork be useful?

Well, people are contributing to copyleft codebases expecting that when people build on their work, that work (the derivative works) are also licensed in the same way. You don't need to fork for the value to be lost. People expected virality to be part of their contribution, and clearly the new derivative works are partially non-copyleft.

Beyond that, as more of the codebase is LLM produced, the less of it is protected by the copyleft license, until we have a ship of Theseus situation where the codebase is available, but no longer copyleft. That is clearly not what was intended by e.g. the GPL. Just look at the Stallman quote in post.

4mo ago

AI Code is Hollowing Out Open Source, and Maintainers are Looking the Other Way

Jump

yoasif @fedia.io 4mo ago

ianal but does it even work like that? Is there any specific reason to think it does? I don't believe you really get credit for purity and fairness vibes in the legal system. Same goes for the idea that code where it is ambiguous whether it is AI output could be considered public domain, seems kind of implausible, is there actually any reason to think the law works that way? If it did, then any copyrighted work not accompanied by proof of human authorship would be at risk, uncharacteristic for a system focused on giving big copyright holders what they want without trouble.

I'm mostly just playing along with your thought experiment. As I said, we know that projects are already accepting LLM code into projects that are nominally copyleft.

There is no way, leaks happen, big tech companies have massive influence, a situation where their code falls into the public domain as soon as the public gets their hands on it just isn't realistic.

If that is the case, is chardet 7.0.0 a derivative work of chardet, or is it a public domain LLM work? The whole LLM project is fraught with questions like these, but it seems that the vendors at least are counting on not copying leaked software and instead copying open source code that is publicly hosted.

Why is it okay to strip copyright from open source works but not from leaked closed source works?

We know that Disney is suing to protect its works - if it is true that LLM outputs are transformative, they should lose, as should any vendor whose leaked code was "transformed" by an LLM.

4mo ago

AI Code is Hollowing Out Open Source, and Maintainers are Looking the Other Way

Jump

yoasif @fedia.io 4mo ago

Making use of the non-copyrightability of AI output to copy code in otherwise unauthorized ways does not seem like a straightforward or legally safe thing to do. That's especially the case because high profile proprietary software projects also make heavy use of AI, it doesn't seem likely the courts will support a legal precedent that strips those projects of copyright and allow anyone to use them for whatever.

I think what may happen in practice could be worse - basically if we can't tell whether some code is the work of a human, but the project accepts AI code, if there we forego the analysis of whether something was produced by a human, the entire project may be deemed public domain -- perhaps after a certain date (when LLM contributions were welcomed).

Beyond that, by integrating LLM code into those projects, the projects are signifying assent to their works to be consumed by LLMs for infringement of the whole work - not just the LLM produced portions - it is hard to be doctrinaire about adherence to the open source license when the maintainers themselves are violating it.

We may see a future where copyrights for works become more like trademarks - if you don't make any attempt to protect your work from piracy, you may simply lose the right to contest its theft.

Obviously, it is as you say - today the courts may smile upon a GPL project where a commercial vendor copied and released as their own without sharing alike - but if they instead say that they copied the work into their LLM and produced a copy without protections (as chardet has done), the courts might be less willing to afford the project copyright protections if the project itself was making use of the same copyright stripping technology to strip others' work to claim protections over copied work.

Besides which, "authored by Claude" seems like a pretty easy way to find public domain code, and as Malus presents, the only code that may ultimately be protected is closed source code - you can't copy it if you don't have the source.

The diversion of "people may try to pass of LLM code as their own" is a nice diversion, but ancillary to the existing situation where projects are incorporating public domain code as licensed. We can start there before we start worrying about fraud.

4mo ago

AI Code is Hollowing Out Open Source, and Maintainers are Looking the Other Way

Jump

yoasif @fedia.io 4mo ago

I don't really think we need to go down the copyfraud path to see that AI code damages copyleft projects no matter what - we know that some projects are already accepting AI generated code, and they don't ask you to hide it - it is all in the open.