Earlier quoted context omitted.
We should be removing IP law entirely, not strengthening it to cover entire classes of problem even when implemented entirely differently. Same for anyone trying to claim "colorful monster creatures" as innately Pokemon IP. Just because someone climbed a mountain first doesn't mean they own it forever. Nobody should be honouring any of these claims. Nor should we be treating AI models themselves as respected IP. They…
Good news! LLM output cannot be copyrighted. Everything that an LLM produces is automatically, irrevocably, in the public domain.
Is legal the same as legitimate: AI reimplementation and the erosion of copyleft
511–520 of 623 posts
Re: Is legal the same as legitimate: AI reimplementation and the erosion of copyleft
#512Earlier quoted context omitted.
We should be removing IP law entirely, not strengthening it to cover entire classes of problem even when implemented entirely differently. Same for anyone trying to claim "colorful monster creatures" as innately Pokemon IP. Just because someone climbed a mountain first doesn't mean they own it forever. Nobody should be honouring any of these claims. Nor should we be treating AI models themselves as respected IP. They…
Good news! LLM output cannot be copyrighted. Everything that an LLM produces is automatically, irrevocably, in the public domain.
Re: Is legal the same as legitimate: AI reimplementation and the erosion of copyleft
#513Oracle v Google concluded that APIs could not be protected by either copyright or copyleft. It seemed to me at the time that most here supported that decision. Has anything changed?
Re: Is legal the same as legitimate: AI reimplementation and the erosion of copyleft
#514> If source code can now be generated from a specification, the specification is where the essential intellectual content of a GPL project resides. Our foreparents fought for the right to implement works-a-like to corporate software packages, even if the so-called owners did not like it. We're ready to throw it all away, and let intellectual property owners get so much more control. The implications will not end up b…
Re: Is legal the same as legitimate: AI reimplementation and the erosion of copyleft
#515> If source code can now be generated from a specification, the specification is where the essential intellectual content of a GPL project resides. Our foreparents fought for the right to implement works-a-like to corporate software packages, even if the so-called owners did not like it. We're ready to throw it all away, and let intellectual property owners get so much more control. The implications will not end up b…
Re: Is legal the same as legitimate: AI reimplementation and the erosion of copyleft
#516Earlier quoted context omitted.
> I feel as though, from an information-theoretic standpoint, it can't be possible that an LLM (which is almost certainly It doesn't need to for my argument to make sense. It's a problem if it reproduces a single copyrighted work (near)-verbatim. Which we have plenty of examples of.
Do we? Even when people attempt to jail break most models with 1000s of prompts they are only able to get a paragraph or two of well known copyrighted works and some blocks of paraphrased text, and that's with giving it a substantially leading question.
Re: Is legal the same as legitimate: AI reimplementation and the erosion of copyleft
#517Earlier quoted context omitted.
Not quite in my opinion. The output of an LLM from a simple prompt falls into the public domain, but if you also give a copyrighted work as input, the mechanistic transformation performed will not alter the original license (same as encoding a video does not change its license).
Are training data counted as input? It would be interesting to see a court ruling that the output of LLMs trained on copyleft code are licensed under the GPL ... and all other viral licenses simultaneously
It is quantum legality, to use copyright input is legal or illegal depending on the observer.
Re: Is legal the same as legitimate: AI reimplementation and the erosion of copyleft
#518Earlier quoted context omitted.
Yeah, I really don't think we want APIs to be protected by IP. But in this case it isn't just the API, there were also tests involved. I think you could make a pretty strong argument that if you used a test suite to get an agent to implement some code, the code is a derivative product of the test code.
[dead]
What is the difference between an "agent" and a "compiler"?
For that matter, what is the difference between "I got an agent to provide a high level description" and a decompiler?
What is the difference between ["decompiling" a binary, editing the resulting source, recompiling, and redistributing] and [analyzing the behavior of a binary, feeding that description into an LLM, generating source code that replicates that behavior, editing that, recompiling and redistributing]?
Takeaway: we are now in a world where software tools can climb up and down the abstraction stack willy nilly and independently of human effort. Legal tools that attempt to track the "provenance" of "source code" were already shaky but are now crumbling entirely.
Re: Is legal the same as legitimate: AI reimplementation and the erosion of copyleft
#519If you are 50 years old or more, the computing you were born with (you own the computer, you own the programs) will be gone. Copyleft only makes sense if you own the computer.
That makes me sad.
Re: Is legal the same as legitimate: AI reimplementation and the erosion of copyleft
#520Earlier quoted context omitted.
Not quite in my opinion. The output of an LLM from a simple prompt falls into the public domain, but if you also give a copyrighted work as input, the mechanistic transformation performed will not alter the original license (same as encoding a video does not change its license).
Are training data counted as input? It would be interesting to see a court ruling that the output of LLMs trained on copyleft code are licensed under the GPL ... and all other viral licenses simultaneously