Earlier quoted context omitted.
> If you had a hermetically sealed code base that just happened to coincide line for line with the codebase for GCC, it would still be a copy. That's not what the law says [1]. If two people happen to independently create the same thing they each have their own copyright. If it's highly improbable that two works are independent (eg. the gcc code base), the first author would probably go to court claiming copying, but…
It is true that if two people happen to independently create the same thing, they each have their own copyright. It is also true that in all the cases that I know about where that has occurred the courts have taken a very, very, very close look at the situation and taken extensive evidence to convince the court that there really wasn't any copying. It was anything but a "get out of jail free" card; it in fact was dif…
Relicensing with AI-Assisted Rewrite
251–260 of 408 posts
Re: Relicensing with AI-Assisted Rewrite
#252Earlier quoted context omitted.
So what? Is reading code the same as copying code or modifying existing code?
If you want to prove you did not make a derivative work, yes it helps if you never read the source code. Hence so call "clean room" implementations.
Re: Relicensing with AI-Assisted Rewrite
#253> Accepting AI-rewriting as relicensing could spell the end of Copyleft The more restrictive licences perhaps, though only if the rewriter convinces everyone that they can properly maintain the result. For ancient projects that aren't actively maintained anyway (because they are essentially done at this point) this might make little difference, but for active projects any new features and fixes might result in either…
Re: Relicensing with AI-Assisted Rewrite
#254> Accepting AI-rewriting as relicensing could spell the end of Copyleft The more restrictive licences perhaps, though only if the rewriter convinces everyone that they can properly maintain the result. For ancient projects that aren't actively maintained anyway (because they are essentially done at this point) this might make little difference, but for active projects any new features and fixes might result in either…
Re: Relicensing with AI-Assisted Rewrite
#255Earlier quoted context omitted.
If you want to prove you did not make a derivative work, yes it helps if you never read the source code. Hence so call "clean room" implementations.
Why should I prove that? Let those who claim the violation prove that.
You can't just dismiss it then say the claimant has to provide proof.
Re: Relicensing with AI-Assisted Rewrite
#256Generative AI changed the equation so much that our existing copyright laws are simply out of date. Even copyright laws with provisions for machine learning were written when that meant tangential things like ranking algorithms or training of task-specific models that couldn't directly compete with all of their source material. For code it also completely changes where the human-provided value is. Copyright protects…
Honestly, good. Copyright and IP law in general have been so twisted by corporations that only they benefit now, see Mickey Mouse laws by Disney for example, or patenting obvious things like Nintendo or even just patent trolling in general.
Re: Relicensing with AI-Assisted Rewrite
#257Earlier quoted context omitted.
Are you referring to this? https://osyuksel.github.io/blog/reconstructing-moby-dick-llm... I see a test where one model managed to 85% reproduce a paragraph given 3 input paragraphs under 50% of the time. So it can't even produce 1 paragraph given 3 as input, and it can't even get close half the time. "Contains Moby Dick" would be something like you give it the first paragraph and it produces the rest of the book. Wh…
I'm no longer certain what point you're trying to make. Getting close less than half the time given three paragraphs as input still sounds like red-handed copyright infringement to me. If I sample a copyrighted song in my new track, clip it, slow it down, and decimate the bit rate, a court would not let me off the hook. It doesn't matter how much context you push into these things. If I feed them 50% of Moby Dick and…
> If I feed them 50% of Moby Dick and they produce the next word and I can repeatedly do that to produce the entire book... then we can prove the statistical model encodes the book.
It can't because it doesn't. That's what it means to say it diverges.
The "number of attempts" is you cheating. You're giving it the book when you let it try again word by word until it gets the correct answer, and then claiming it produced the book. That's exactly the residual that I said characterizes the extent to which it doesn't know the book. Trivially, no matter how bad the model is, if you give it the residual, it can losslessly compress anything at all.
If you had a simple model that just predicts next word given current word (trained on word pair frequency across all English text, or even all text excluding Moby Dick), and then give it retries until it gets the current word right, it will also quickly produce the book. Because it was your retry policy that encoded the book, not the model. Without that policy, it will get it wrong within a few words, just like these models do.
Re: Relicensing with AI-Assisted Rewrite
#258Generative AI changed the equation so much that our existing copyright laws are simply out of date. Even copyright laws with provisions for machine learning were written when that meant tangential things like ranking algorithms or training of task-specific models that couldn't directly compete with all of their source material. For code it also completely changes where the human-provided value is. Copyright protects…
It's not a problem. If you give a work to an AI and say "rewrite this", you created a derivative work. If you don't give a work to an AI and say "write a program that does (whatever the original code does)" then you didn't. During discovery the original author will get to see the rewriter's Claude logs and see which one it is. If the rewriter deleted their Claude logs during the lawsuit they go to jail. If the rewrit…
Re: Relicensing with AI-Assisted Rewrite
#259Why would anyone waste their time reading what they wrote then?
Re: Relicensing with AI-Assisted Rewrite
#260The second part here is problematic, but fascinating: "I then started in an empty repository with no access to the old source tree, and explicitly instructed Claude not to base anything on LGPL/GPL-licensed code." Problem - Claude almost certainly was trained on the LGPL/GPL original code. It knows that is how to solve the problem. It's dubious whether Claude can ignore whatever imprints that original code made on its weights. If it COULD do that, that would be a pretty cool innovation in explainable AI. But AFAIK LLMs can't even reliably trace what data influenced the output for a query, see https://iftenney.github.io/projects/tda/, or even fully unlearn a piece of training data.
Is anyone working on this? I'd be very interested to discuss.
Some background - I'm a developer & IP lawyer - my undergrad thesis was "Copyright in the Digital Age" and discussed copyleft & FOSS. Been litigating in federal court since 2010 and training AI models since 2019, and am working on an AI for litigation platform. These are evolving issues in US courts.
BTW if you're on enterprise or a paid API plan, Anthropic indemnifies you if its outputs violate copyright. But if you're on free/pro/max, the terms state that YOU agree to indemnify THEM for copyright violation claims.[0]
[0] https://www.anthropic.com/legal/consumer-terms - see para. 11 ("YOU AGREE TO INDEMNIFY AND HOLD HARMLESS THE ANTHROPIC PARTIES FROM AND AGAINST ANY AND ALL LIABILITIES, CLAIMS, DAMAGES, EXPENSES (INCLUDING REASONABLE ATTORNEYS’ FEES AND COSTS), AND OTHER LOSSES ARISING OUT OF … YOUR ACCESS TO, USE OF, OR ALLEGED USE OF THE SERVICES ….")