A new twist in the "AI license laundering of chardet" story https://github.com/chardet/chardet/issues/327
Timeline
Post
Remote status
Context
1
@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.
> 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.
Replies
0Fetching replies…