A new twist in the "AI license laundering of chardet" story https://github.com/chardet/chardet/issues/327
-
A new twist in the "AI license laundering of chardet" story https://github.com/chardet/chardet/issues/327
@cwebber Reading through all the comments there left me wondering if anyone has (yet) hooked up an LLM to be a project maintainer. Interactions via issues and just let it loose. People would be utterly mad to ever include it in their supply chain, and yet people do do mad things.
-
A new twist in the "AI license laundering of chardet" story https://github.com/chardet/chardet/issues/327
@cwebber Isn’t this what forks are for?
-
@cwebber
> Their claim that it is a "complete rewrite" is irrelevant, since they had ample exposure to the originally licensed code (i.e. this is not a "clean room" implementation). Adding a fancy code generator into the mix does not somehow grant them any additional rights.
The human didn't write the code, the LLM did. "They" which had "ample exposure to the originally licensed code" does not exist; "they" are ephemeral.
1. Start a fresh session / clean context, make it meticulously document the architecture, APIs, etc
2. keep those documents, throw away the code, start a new session with an LLM that has clean context and tell it to build off those documents.
That's clean room. If the original code was not in the LLM's context, it's not violating the license.
This is how you can do this. Proving beyond a reasonable doubt he didn't do it this way is going to require a lot of evidence nobody will have. -
-
@vv @cwebber proving the original was trained by the model or is in the model is quite difficult to do and is questionable whether or not it really matters anyway.
Chris Lattner was "trained on" GCC when he wrote LLVM. He studied it a lot. GCC compiles code C/C++ successfully, LLVM compiles C/C++ code successfully.
Both produce completely working bytecode and generally you don't *need* one compiler over the other to get an end result that is acceptable.
Should LLVM be allowed to have an Apache license because of this?
These are tough questions. -
omg I am just seeing now that the dude who did the "AI relicensing" fucking replied with an obvious slop response, of all the fucking disrespectful things to do, holy fucking shit https://github.com/chardet/chardet/issues/327#issuecomment-4005195078
@cwebber I felt my brain getting smoother as I read that
-
Winning option 1: yes, you can vibe code proprietary codebases into the public domain, allowing us to bootstrap proprietary codebases quickly
Winning option 2: stopping laundering of copyleft codebases
Either of these are interesting outcomes!
@cwebber Microslop committed to picking up the legal bill for anyone concerned about copyright issues with AI outputs from copilot so one could hypothetically use their tools to "clean room" implement Photoshop and then have Satya fight Adobe for your right to do so. Sounds fun to me!
https://blogs.microsoft.com/on-the-issues/2023/09/07/copilot-copyright-commitment-ai-legal-concerns/ -
@cwebber Microslop committed to picking up the legal bill for anyone concerned about copyright issues with AI outputs from copilot so one could hypothetically use their tools to "clean room" implement Photoshop and then have Satya fight Adobe for your right to do so. Sounds fun to me!
https://blogs.microsoft.com/on-the-issues/2023/09/07/copilot-copyright-commitment-ai-legal-concerns/ -
@cwebber Microslop committed to picking up the legal bill for anyone concerned about copyright issues with AI outputs from copilot so one could hypothetically use their tools to "clean room" implement Photoshop and then have Satya fight Adobe for your right to do so. Sounds fun to me!
https://blogs.microsoft.com/on-the-issues/2023/09/07/copilot-copyright-commitment-ai-legal-concerns/ -
@cwebber I'm not sure that's slop, but I won't discount the possibility...
But this part is funny in the dark humor sort of way:"...explicitly instructed Claude not to base anything on LGPL/GPL-licensed code."
So, you see, no problem...

Claude after being explicitly instructed not to base anything on LGPL/GPL-licensed code

-
R relay@relay.infosec.exchange shared this topic