whizzter
Joined 11 years ago
Joined 11 years ago
I think you misjudged my intent with that initial comment, it was mostly that I'd be feeling easier about AI usage if I knew the models WEREN'T trained on GPL'ed code, people producing GPL'ed software has historically been quite profilic in certain areas and the odds of copyrightable parts of GPL'ed code not showing up in AI code managing certain fileformats is definetly nonzero.
Ie, I'd be happier using Claude Code-nogpl, I'd be fine with adding BSD,etc copyright notices if given provenance information from the model, being in the GPL minefield because they don't really seem to track inputs is another.
From the page, https://openjdk.org/legal/ai
--------------------------
What are the intellectual-property risks of using generative AI tools?
The Oracle Contributor Agreement (OCA) requires that a contributor own the intellectual property rights in each contribution and be able to grant those rights to Oracle, without restriction. Most generative AI tools, however, are trained on copyrighted and licensed content, and their output can include content that infringes those copyrights and licenses, so contributing such content would violate the OCA. Whether a user of a generative AI tool has IP rights in content generated by the tool is the subject of active litigation.
--------------------------
But they're just Oracle lawyers so it's baloney right?
The thing they're doing correctly right now imho, is that AI mode is mostly toggled for things that passes a quick questions filter (probably low probability of a purchase, like "global illumination methods" giving a decent overview of the field) while if you just type green shoes it'll put out an assortment of online and local shopping options.
Now if as someone said in the sibling comments, Google is gouging their customers with the new auction model that's another problem, but if I was a shareholder I'd be less worried about an exodus of end users to OpenAI,etc than I was a year ago.
"Mbed TLS - Medium, CVSS 5.9 - A buffer-length typo reduces a 2048-bit DH modulus to one byte. TLS 1.2 DHE_RSA sessions are decryptable when the client accepts the broken parameters. GOAHEAD-SA-2026-0005."
Not familiar with those implementation details but was this the root cause?
I know there was some cases in the past where people swapped licences and changed variablenames,etc but the essential code clearly remained.
So far it seems more cases that have been decided in lower instances or has been settled or gone in the direction of the party with most money for lawyers, still even in those cases there seems to be a slight tilt towards rightsholders.
I'm not saying anything categorically, but if some cases go all the way and towards rightsholders, it could become a real shitshow in the software industry since we've adopted AI so heavily and the non-significatng portion of public GPL licenced code could bite people in the ass.
Or maybe the FSF is just waiting for everyone using AI code to become hooked and then subpoena every Antrophic/OAI/Codex customer and force the most massive source release in history (If Adobe/MS would file lawsuits vs the Craft apps and with their resources create legal precedent it could create chaos, maybe the only part stopping them right now from filing lawsuits is them realizing it could backfire since they're heavy AI users themselves).
Companies copying things to make profit for themselves not being held accountable.
Progress is one thing, injustice is another.