cross-posted from: https://lemmy.ml/post/44059967
for those not familiar with Mark Pilgrim, he is/was a prolific author, blogger, and hacker who abruptly disappeared from the internet in 2011.
cross-posted from: https://lemmy.bestiver.se/post/968527
One of the commentors in there claims that Claude will straight give you struct sk_buffer. I dont have access to Claude but I vomited and went to chatgpt and it said it was copyrighted and couldnt give it to me. I know we hate AI, but ir changes so fast make sure your info is right. We cant take them down with falsehoods, even if they are freshly made false. If anyone has Claude and can test let me know.
You can ask the LLM the same question a hundred times and it might not give you the same answer it gave someone else. The way it responds is a combination of random chance and the language used to ask the question.
I used whatever free tokens I had asking and every time it said it was a copyright violation in different ways. Make of that what you will but dont underestimate these oligarchs. They’re weaving past, present, and future into the biggest ball of shit ever created and it rolls in their favor.
Isn’t the LGPL supposed to be relicensable as opposed to GPL’s share-alike?
No, LGPL just allows linking to differently-licensed software.
Basically linking copies some code from the library into the program that uses it, making any linked software a derivative work.
Sellers of proprietary software libraries give permission for this specific type of linking in their license. LGPL gives the same permission to people who are otherwise following the GPL. LGPL used to be called the “library-GPL” because it is the GPL plus permission to use the library linking mechanism.
Nope. The LGPL simply makes an exception for programs that link with it through an API (aka when an LGPL program is used as a library).
nope, here *GPL acts like cancer, once it touches something, it remains *GPL until the last bit of it is still there.
Cancer is a bad analogy. It’s more like antibodies against non-free bactetia :)
I have a completely different view of what free means. xGPL are restrictive and sticky.
The freedom to deny others the same freedom?
Ok, maybe explain the restrictions that offend you so much?
GPL licenses are straight-up cancer, they force every derivative or linked project to adopt their viral copyleft rules, nuking proprietary reuse or easy mixing with other codebases, while a weird GPL cult preaches it as the one true path to “openness” and “freedom”. As someone who codes purely for fun, I like the dead-simple clarity of MIT and BSD: just keep the notice and license text, then do whatever the hell you want. No GPL bullshit or compliance headaches for me, permissive licenses like these keep my sanity intact.
Licenses like the MIT are built to support grifters that just want to take and not contribute back, so…
That’s… The point of the GPL licenses, to preserve copyleft. I also prefer the simplicity of the MIT license for my own works, but I respect the copyleft ideals.
If it’s all your own work then a license is purely for others to follow. MIT and GPL license can be just as simple as including a textfile of that license in the project.
Ideally one includes a header in each code file so ensure people just looking at that file without project context know the license.
GPL is especially popular with people who don’t want their labor of love to become a source of free labor for corporations who will tweak it, close the source, directly profit off it, and never donate or contribute patches. For them, it’s an antiparasitic license.
I’ve heard that “corporate parasite” argument way too often, but it’s massively overrated. Open Source allows selling anyway, MIT, BSD and GPL all do. If someone makes smart changes and lives off it, that’s awesome, not reprehensible!
GPL only forces source disclosure when distributing binaries, not for every damn thing – imagine you land a juicy company contract: you tweak a GPL work, deliver the binaries, and only have to hand the modified source TO THAT COMPANY, NOT the whole world! That’s why AGPL fanatics had to invent their SaaS trap. For me as a hobby coder, GPLs are just pointless headaches instead of real freedom.
Well, I do not get his point, the code has been completely rewritten. Not to mention that the new license is much better than the old one.
One of the more “interesting” additional aspects is that courts have decided that works of generative models are not copyrightable… so one can’t license them either.
If the llm they used was trained on the original code, the result was not legally rewritten. To change licensing without buy in from all original authors, the new code must be fully original from spec. Ignoring the legal definitions for convenience opens the door for corporations to steal open source and copyleft materials and strip away the licensing requirements.
That’s a wild claim you’re making. So far, it looks like the code is completely new, and for this case, it doesn’t really matter where it comes from. New code - new license.
If you write new code looking at the old code in another editor window, that’s likely derivative work. If you’ve never seen the original code and are looking only at the API, that’s likely not derivative work. Determining whether the code is ‘new’ is insufficient.
If the LLM training data is based on / has used GPL code, this might set an interesting legal precedent.
okay, you have to be able to prove the LLM didn’t learn off of the original source material. Because if it is, its dertivitve work, making it subject to LGPL.
LLM is not the copyright owner, it’s a developer of the LGPL package… IMHO, it’s an obvious violation of the original developer rights.
Well, I do not have to, the burden of proof lies on the person making the claim.
That’s valid in a debate, but not quite how courts work?
I’m not a lawyer, just someone petty enough to read laws.
The discovery requests in the law suit will require yo turn over all training data. From there, it will be up to the AI makers to prove that it wasn’t used, if it was fed into training data. Which if it was open source, almost certainly was.
That as side.
Your making an equal claim that it wasn’t. With an equal amount of proof. So what your sating bears as much weight as the other person.
I have not made any claims, and I am not affiliated with this project in any way. I don’t know how this could be dealt with in court, or whether anyone will even bother with it.
You claim
https://vger.to/lemmy.ml/comment/24346212
That its completlt rewritten, with the implication that its not using the project as input.
So yes, you do should back that up
This is a vast downgrade; stripping the GPL is an obvious attempt at nuking open source by bad faith actors. See what’s happening with AOSP, which would be impossible under GPL.
The day GPL stops being used is the day every major tech company will start slowly but surely closing their code down until open source is completely dead
Yeah, personally I don’t really like the GPL* (for stuff that isn’t actively of interest to companies), but this kind of stripping the GPL from an existing project is just, gross. Definitely seems like an active attempt to nuke it and take it over.
(*because I like it when other open source people can use a given piece of code e.g. I wrote, and I’m not particularly picky about whether they agree with me on what specific form of open source is best; wanna use my MIT or public domain code in a GPL project? go for it!)
(s/open source/free software/g if you’re one of the “open source isn’t REAL FREE SOFTWARE!!!” people; I use the terms interchangeably, bite me)
(also I get using the GPL for stuff that companies would actively want to take over. Like, apparently, this project.)
– Frost
What is happening with AOSP has nothing to do with the license. This project is not being developed by the community, but by Google for Google’s money, and Google can do whatever it wants with it. It’s silly to be offended by this. Anyone who is dissatisfied can fork the project and do whatever they want with it, if they can manage *(well, no, without Google’s resources, this is of course unrealistic).
So no one is going to say what chardet is, huh.
It’s a library for detecting which character encoding a string is encoded with.
Here are the docs for the vibe-coded rewrite, and here is the version before it.
The new vibe-coded version also adds language detection; it isn’t clear to me why the current version of the readme shows it classifying the string
"It’s a lovely day — let’s grab coffee."as Spanish with 99% confidence, without any comment in the docs about that being a misclassification, but I guess that if the LLM-authored program says it is then that must be one of those phrases that looks the same in Spanish as in English 👀
