2 ms·
The remedy for unintentional infringement is generally to remove the infringing code and cease distribution. That used to be a serious issue when rewriting the
by timschmidt 3mo ago
The remedy for unintentional infringement is generally to remove the infringing code and cease distribution. That used to be a serious issue when rewriting the offending code might take years. But these days? Rewriting any offending code is a matter of specifying the interfaces and setting Claude / Codex to work. Risk of incorporating derived code might go up with accepting LLM submissions, but cost of recovering from them seems to have dropped accordingly, at least on the technical side.
- m4rtink 3mo agoReplace one set of LLM tainted code by a different bunch of LLM tainted code - perfect a and totally solid from any legal perspective! (The paragraph above is a sarcasm.)
- 15155 3mo agoIs this concept of "LLM tainted" enumerated in a statute or potentially borne out of actual case law somewhere?
- timschmidt 3mo agoPerhaps you've never maintained any serious open source software. A line-by-line source code audit for license compliance including some ripping-out and re-writing of non-compliant code was the first thing I did when taking over maintainership of Repsnapper nearly 20 years ago. Was required to get it into Fedora. I don't see how the presence of LLM generated code changes that kind of work at all.