I believe it is a narrow view of the situation. If we take a look into the history, into the reasons for inventing GPL, we'll see that it was an attempt to fight copyrights with copyrights. The very name 'copyleft' is trying to convey the idea. What AI are eroding is copyright. You can re-implement not just a GPL program, but to reverse engineer and re-implement a closed source program too, people have demonstrated i…
> LLM as the main weapon LLM's - to date - seem to require massive capital expenditures to have the highest quality ones, which is a monumental shift in power towards mega corporations and away from the world of open source where you could do innovative work on your own computer running Linux or FreeBSD or some other open OS. I don't think that's an exciting idea for the Free Software Foundation. Perhaps with time we…
Is legal the same as legitimate: AI reimplementation and the erosion of copyleft
191–200 of 623 posts
Re: Is legal the same as legitimate: AI reimplementation and the erosion of copyleft
#192Re: Is legal the same as legitimate: AI reimplementation and the erosion of copyleft
#193Earlier quoted context omitted.
What does derivative mean here? Because IMO it means that the existing work was used as input. So if you used a LLM and it was trained on the existing work, that's a derivative work. If you rot13 encode something as input, so you can't personally read it, and then a device decides to rot13 on it again and output it, that's a derivative work.
LLMs do not encode nor encrypt their training data. The fact they can recite training data is a defect not a default. You can understand this more simply by calculating the model size as an inverse of a fantasy compression algorithm that is 50% better than SOTA. You'll find you'd still be missing 80-90% of the training data even if it were as much of a stochastic parrot as you may be implying. The outputs of AI are n…
Re: Is legal the same as legitimate: AI reimplementation and the erosion of copyleft
#194I downloaded both 6.0 and 7.0 and based on only a light comparison of a few key files, nothing would suggest to me that 7.0 was copied from 6.0, especially for a 41x faster implementation. It is a lot more organized and readable in my armature opinion, and the code is about 1/10th the size.
Re: Is legal the same as legitimate: AI reimplementation and the erosion of copyleft
#195I believe it is a narrow view of the situation. If we take a look into the history, into the reasons for inventing GPL, we'll see that it was an attempt to fight copyrights with copyrights. The very name 'copyleft' is trying to convey the idea. What AI are eroding is copyright. You can re-implement not just a GPL program, but to reverse engineer and re-implement a closed source program too, people have demonstrated i…
> LLM as the main weapon LLM's - to date - seem to require massive capital expenditures to have the highest quality ones, which is a monumental shift in power towards mega corporations and away from the world of open source where you could do innovative work on your own computer running Linux or FreeBSD or some other open OS. I don't think that's an exciting idea for the Free Software Foundation. Perhaps with time we…
When the FSF and GPL were created, I don't think this was really a consideration. They were perfectly happy with requiring Big Iron Unix or an esoteric Lisp Machine to use the software - they just wanted to have the ability to customize and distribute fixes and enhancements to it.
Re: Is legal the same as legitimate: AI reimplementation and the erosion of copyleft
#196shall we now have to think about the tradeoffs in adopting - proprietary - free - slop-licensed software?
Re: Is legal the same as legitimate: AI reimplementation and the erosion of copyleft
#197Re: Is legal the same as legitimate: AI reimplementation and the erosion of copyleft
#198From the article: > He fed only the API and the test suite to Claude and asked it to reimplement the library from scratch. From GPL2: > The source code for a work means the preferred form of the work for making modifications to it. For an executable work, complete source code means all the source code for all modules it contains, plus any associated interface definition files, plus the scripts used to control compila…
Google v. Oracle ruled that use of APIs are fair game and could be argued that test cases are strictly a use of APIs and not implementation.
Regarding chardet, I'm not sure "I wanted to circumvent the license" is a good way to argue fair use.
Re: Is legal the same as legitimate: AI reimplementation and the erosion of copyleft
#199I think the missing thing here is that the license violation already happened. Most of the big models trained on data in a manner that violated terms of service. We'll need a court case but I think it's extremely reasonable to consider any model trained on GPL code to be infected with open licensing requirements.
I agree there has to be a court case about it. I think the current argument, however, is that it is transformative, and therefore falls under fair use.
Re: Is legal the same as legitimate: AI reimplementation and the erosion of copyleft
#200Earlier quoted context omitted.
> LLM as the main weapon LLM's - to date - seem to require massive capital expenditures to have the highest quality ones, which is a monumental shift in power towards mega corporations and away from the world of open source where you could do innovative work on your own computer running Linux or FreeBSD or some other open OS. I don't think that's an exciting idea for the Free Software Foundation. Perhaps with time we…
> LLM's - to date - seem to require massive capital expenditures to have the highest quality ones There are near-SOTA LLM's available under permissive licenses. Even running them doesn't require prohibitive expenses on hardware unless you insist on realtime use.
What async tasks could a local LLM accomplish on Intel 11th gen CPU with 32GB RAM?