A new twist in the "AI license laundering of chardet" story https://github.com/chardet/chardet/issues/327
-
But really, relicensing a GPL codebase to MIT is uninteresting.
Let's do the interesting one, which is: vibe code a "clean room" reimplementation of an entire proprietary codebase! After all, Microsoft released a "shared source" proprietary version of Windows. Now try seeing what happens if you run THAT through the "turn it into public domain" machine
Win-win outcome, no matter how it goes
@cwebber it's just gonna launder wine code lol -
I left a comment to that effect here https://github.com/chardet/chardet/issues/327#issuecomment-4005721071
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
-
But really, relicensing a GPL codebase to MIT is uninteresting.
Let's do the interesting one, which is: vibe code a "clean room" reimplementation of an entire proprietary codebase! After all, Microsoft released a "shared source" proprietary version of Windows. Now try seeing what happens if you run THAT through the "turn it into public domain" machine
Win-win outcome, no matter how it goes
@cwebber I have been saying this since the first copilot iteration!
If Microsoft wants to show us how to launder copyright, by all means, let them.
-
I left a comment to that effect here https://github.com/chardet/chardet/issues/327#issuecomment-4005721071
@cwebber that's exactly where my mind went to. Any time I've rewritten something that was in copyleft because I needed it copycenter or even with such inspiration, I wouldn't let myself even look at the original code. But it would be a net boon to OSS if the same rules apply to proprietary stuff. The bad situation would be if corporate lawyers effectively made it so that only their code is protected from such reimplementation.
-
I left a comment to that effect here https://github.com/chardet/chardet/issues/327#issuecomment-4005721071
@cwebber good times!

It's going to be fun to see how the boundaries of "human produced work" are defined over time, but I expect it will work out in whatever way benefits the big money players in software and media.
Does this only apply to "AI"? What does that mean? If I have a machine generated background crowd or vapour in some frames of my $300M blockbuster movie, can I still copyright it?
-
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 happy to see Mark Pilgrim still exists, he sorta disappeared from public life and I hadn't seen him active in public-facing software at all
-
But really, relicensing a GPL codebase to MIT is uninteresting.
Let's do the interesting one, which is: vibe code a "clean room" reimplementation of an entire proprietary codebase! After all, Microsoft released a "shared source" proprietary version of Windows. Now try seeing what happens if you run THAT through the "turn it into public domain" machine
Win-win outcome, no matter how it goes
@cwebber Microsoft can still sue for patent violations. But Windows 7 is over 15 years old.
Also, trademark violations should be carefully avoided.
-
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 The ReactOS people take such careful steps to avoid any even potentially compromising contact with Windows source. I'm not a fan of copyright in general, but as long as it exists, people need to be mindful of what they're doing and the history it touches on.
It's a whole project of its own to get contributors to relicense their code and rewrite what can't be relicensed, and most projects that do it take a bunch of flak even if they have good reasons. (like GPL->AGPL)
And this dude just vibed his way through it
-
A new twist in the "AI license laundering of chardet" story https://github.com/chardet/chardet/issues/327
@cwebber I would very much like someone with a legal mind explain how software licenses interact with yesterday's ruling that AI gen work is not copyrightable. What exactly is the basis of the copyright here? I hope we get to see someone dive into this.
-
@cwebber I would very much like someone with a legal mind explain how software licenses interact with yesterday's ruling that AI gen work is not copyrightable. What exactly is the basis of the copyright here? I hope we get to see someone dive into this.
@etoani @cwebber It was a decline to rule. The case they declined to rule on stood, and it focused narrowly on someone trying to get his pet AI recognized as sentient to qualify for authorship under copyright law.
Where the line is on how much authorship flips "authored parts are copyrightable" to "the whole thing is copyrighted" is still contested and evolving in courts.
edit: The SCOTUS likes to let lawyers duke it out in district courts and wait for enough rulings, especially with serious cross-district conflicts, at that level to pick from to hear.
-
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 that whole relicensing and this slop reply are vomit inducing.
-
@cwebber that whole relicensing and this slop reply are vomit inducing.
-
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 love the sentence "If you are indeed the Mark Pilgrim..." So steeped in bad faith that you assume others are too.
-
R relay@relay.an.exchange shared this topic
-
But really, relicensing a GPL codebase to MIT is uninteresting.
Let's do the interesting one, which is: vibe code a "clean room" reimplementation of an entire proprietary codebase! After all, Microsoft released a "shared source" proprietary version of Windows. Now try seeing what happens if you run THAT through the "turn it into public domain" machine
Win-win outcome, no matter how it goes
@cwebber Well, the maintainer's point was that this is "clean room", by which they mean Claude was not given the existing codebase as input. The counter argument is that the existing codebase almost certainly forms part of Claude's training data, so the claim of it being genuinely clean room is bogus. So to make your idea work, you'd have to use the proprietary codebase as training data, rather than prompt input.
-
@cwebber Well, the maintainer's point was that this is "clean room", by which they mean Claude was not given the existing codebase as input. The counter argument is that the existing codebase almost certainly forms part of Claude's training data, so the claim of it being genuinely clean room is bogus. So to make your idea work, you'd have to use the proprietary codebase as training data, rather than prompt input.
@cwebber and I suspect that if you made an LLM based on the specific code as training data, a court would probably rule differently to how they have ruled about LLM generated code in other cases. maybe.
-
@cwebber Well, the maintainer's point was that this is "clean room", by which they mean Claude was not given the existing codebase as input. The counter argument is that the existing codebase almost certainly forms part of Claude's training data, so the claim of it being genuinely clean room is bogus. So to make your idea work, you'd have to use the proprietary codebase as training data, rather than prompt input.
-
But really, relicensing a GPL codebase to MIT is uninteresting.
Let's do the interesting one, which is: vibe code a "clean room" reimplementation of an entire proprietary codebase! After all, Microsoft released a "shared source" proprietary version of Windows. Now try seeing what happens if you run THAT through the "turn it into public domain" machine
Win-win outcome, no matter how it goes
@cwebber I cynically fear that the likely outcome is that proprietary copyright holders with lots of lawyers and money could succeed in preventing re-licensing as open source, while copyleft advocates with few resources couldn't actually prevent re-licensing to closed.
-
But really, relicensing a GPL codebase to MIT is uninteresting.
Let's do the interesting one, which is: vibe code a "clean room" reimplementation of an entire proprietary codebase! After all, Microsoft released a "shared source" proprietary version of Windows. Now try seeing what happens if you run THAT through the "turn it into public domain" machine
Win-win outcome, no matter how it goes
@cwebber I think you're going to need one hell of a kickstarter to fund that one.
-
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'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...

-
@cwebber that whole relicensing and this slop reply are vomit inducing.