Apparently chardet got Claude to rewrite the entire codebase from LGPL to MIT?

[leonardof@bertha.social]

@Foxboron If it's in the US, I'm under the impression that code written by an LLM is public domain. That is, supposing it's not illegal as it should be

[skyr@chaos.social]

@Foxboron @scy chances are high that LLM bros suspect it is, that's why they are cutting deals with Big Music. Unfortunately, there's no global-encompassing multi-billion dollar corporation protecting open-source...

[lindsey@recurse.social]

@jn @Foxboron That's exactly the sense that I read it in, and it took me a minute to realize that's not what they meant

[rootwyrm@weird.autos]

@Bubu @Foxboron oh, and I forgot to mention, it's also guaranteed to have numerous instances of code copied verbatim from other projects. Meaning it is also both infringing and subject to other licenses which are likely to include LGPL, GPLv3, and so on.

[froge@social.glitched.systems]

@Foxboron@chaos.social the most hilarious part is that it's not even really MIT licensed, most of this is AI output with no way to distinguish it from human output, in a lot of nations this is machine produced text and just isn't legally valid for anything

he literally doesn't have the authority to relicense this as MIT no matter how much he wants to, because he's not the copyright holder of the code, a machine created most of it

[paul@oldfriends.live]

@thomasjwebb Right now, that is how SCOTUS is leaning regarding AI generated output. They refused to interfere with a patent application and "artist" copyright, leaving it up to the copyright and patent offices to decide, which they said no. Some guy used AI to create a beverage holder and light beacon using AI. When the patent was denied, he tried to copyright the AI created "artist" renditions to get around the patent.

@Foxboron @scy

reuters.com

(www.reuters.com)

https://www.supremecourt.gov/docket/docketfiles/html/public/25-449.html

[bob_zim@infosec.exchange]

@scy @Foxboron It is absolutely a violation for the company which built the model to build a model which emits license-restricted code without following the terms of the license. The model doesn’t commit the violation any more than a photocopier does, of course.

The emitted code cannot be copyrighted at all, but if it emitted the code in a way which meets the terms of the license, the code would be covered by the original license.

[douginamug@mastodon.xyz]

@Foxboron the presenters have a live demo: https://malus.sh/

[gooba42@mastodon.social]

@Foxboron Except the output can't be copyrighted and so the result is public domain. It can't even be licensed anymore.

[blogdiva@mastodon.social]

YUP

copyright is for humans, not automata ―hard or soft.

so, ironically, the prompts are copyrightable but not the output.

so anything you want to copyright should not be prompted into a corporate regurgitation machine, including so-called grammar checkers.

@thomasjwebb @Foxboron @scy

[gooba42@mastodon.social]

@Foxboron Went ahead and added an issue since you can't apply an MIT license to public domain LLM output.

[zkat@toot.cat]

@Foxboron that's... not copyrightable, therefore not licensable?

[glyph@mastodon.social]

@Foxboron @joshbressers @scy verbatim isn’t the question here, the question is infringement. is the output here substantially derivative of previous versions of chardet to the point that it could be considered infringing? US copyright precedent is a muddled mess and I think this could implicate at least one unresolved circuit split. I don’t know what the answer will be but I know I wouldn’t want to be standing in the blast radius of that decision

[slightlyoff@toot.cafe]

@Foxboron If you can't copyright it, you can't license the copyright. Interesting times.

[xgranade@wandering.shop]

@Foxboron It looks like this was the PR?

chardet 7.0: ground-up MIT-licensed rewrite by dan-blanchard · Pull Request #322 · chardet/chardet

Python character encoding detector. Contribute to chardet/chardet development by creating an account on GitHub.

GitHub (github.com)

Even aside from the ethical and moral issues with LLMs, it doesn't seem optimal that a 15k line PR affecting almost a million dependent repos (if GitHub's count is to be believed) was up for three days before getting merged in.

[xgranade@wandering.shop]

@aud It's at least not systems code, so there's not a lot of potential for buffer overflow and other memory unsafety exploits, but yeah. No. chardet is not a small surface area.

[wordshaper@weatherishappening.network]

@thomasjwebb @Foxboron @scy In the US, at least, human authorship is required for copyright, and if you try to copyright something that's a mix of AI and human generated then generally only the human generated part is copyrightable.

https://www.congress.gov/crs-product/LSB10922#:~:text=Granting%20that%20human%20authors%20may,applying%20to%20register%20their%20copyright.

This is separate from the LLMs emitting text other people have written, so at *best* this code can't be licensed because it's not copyrightable, and at worst its license laundering and there's precedent (IIRC) for stomping on that hard.

[aud@fire.asta.lgbt]

@xgranade@wandering.shop There's just no way that's a good idea. I'm pretty sure a human who tried to push a 15K rewrite into most libraries would be yelled at forever and the PR rejected, or asked to be broken into smaller PRs, because it's just such a large change in one go and no one can possibly fit that entire thing into their head.

It doesn't magically become a good idea just because claude shat it out.

[jens@social.finkhaeuser.de]

@scy @Foxboron It's a bit complicated, actually. IANAL, but this is what I understand:

- The music notation is copyrightable, individual notes are not. A sequence of notes is debatable, and it depends highly on recognizability AFAIK.

- A music recording is copyrightable. Playing that music in a distinctly different arrangement, less of an issue.

- Arguably, a change in digital format is either still the same recording, or sufficiently indistinguishable from it.

- Copyright has an ancient...

[jens@social.finkhaeuser.de]

@scy @Foxboron ... naming and goes back to a time where making copies and distributing them was the hard part.

This is a non-problem in the digital age, which is why it's fine to create backup copies of copyrighted works, so long as the people accessing them are always the people having purchased/licensed an original copy.

So LLMs training on GPL is not itself a copyright violation, and them reproducing similar code isn't either, but then publishing such sufficiently similar code is.