this post was submitted on 12 Apr 2026
649 points (95.1% liked)

Technology

83753 readers
2698 users here now

This is a most excellent place for technology news and articles.


Our Rules


  1. Follow the lemmy.world rules.
  2. Only tech related news or articles.
  3. Be excellent to each other!
  4. Mod approved content bots can post up to 10 articles per day.
  5. Threads asking for personal tech support may be deleted.
  6. Politics threads may be removed.
  7. No memes allowed as posts, OK to post as comments.
  8. Only approved bots from the list below, this includes using AI responses and summaries. To ask if your bot can be added please contact a mod.
  9. Check for duplicates before posting, duplicates may be removed
  10. Accounts 7 days and younger will have their posts automatically removed.

Approved Bots


founded 2 years ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
[–] marlowe221@lemmy.world 77 points 1 day ago* (last edited 1 day ago) (2 children)

Yeah, that’s also my question. Partially because I am a former-lawyer-turned-software-developer… but, yeah. How are the kernel maintainers supposed to evaluate whether a particular PR contains non-GPL code?

Granted, this was potentially an issue before LLMs too, but nowhere near the scale it will be now.

(In the interests of full disclosure, my legal career had nothing to do with IP law or software licensing - I did public interest law).

[–] stsquad@lemmy.ml 45 points 1 day ago (1 children)

They don't, just like they don't with human submitted stuff. The point of the Signed-off-by is the author attests they have the rights to submit the code.

[–] ell1e@leminal.space 2 points 19 hours ago* (last edited 19 hours ago) (1 children)

Which I'm guessing they cannot attest, if LLMs truly have the 2-10% plagiarism rate that multiple studies seem to claim. It's an absurd rule, if you ask me. (Not that I would know, I'm not a lawyer.)

[–] stsquad@lemmy.ml 3 points 14 hours ago (1 children)

Where are you seeing the 2-10% figure?

In my experience code generation is most affected by the local context (i.e. the codebase you are working on). On top of that a lot of code is purely mechanical - code generally has to have a degree of novelty to be protected by copyright.

[–] Danquebec@sh.itjust.works 1 points 9 hours ago (1 children)

Imagine how broken it would be otherwise. The first person to write a while loop in any given language would be the owner of it. Anyone else using the same concept would have to write an increasingly convoluted while loop with extra steps.

[–] sloppy_diffuser@sh.itjust.works 1 points 5 hours ago

Anyone else using the same concept would have to write an increasingly convoluted while loop with extra steps.

Sounds like an origin story for recursion.

[–] wonderingwanderer@sopuli.xyz 13 points 1 day ago (1 children)

If it's flagged as "assisted by " then it's easy to identify where that code came from. If a commercial LLM is trained on proprietary code, that's on the AI company, not on the developer who used the LLM to write code. Unless they can somehow prove that the developer had access to said proprietary code and was able to personally exploit it.

If AI companies are claiming "fair use," and it holds up in court, then there's no way in hell open-source developers should be held accountable when closed-source snippets magically appear in AI-assisted code.

Granted, I am not a lawyer, and this is not legal advice. I think it's better to avoid using AI-written code in general. At most use it to generate boilerplate, and maybe add a layer to security audits (not as a replacement for what's already being done).

But if an LLM regurgitates closed-source code from its training data, I just can't see any way how that would be the developer's fault...

[–] sem@piefed.blahaj.zone 6 points 1 day ago (1 children)

Pretty convenient.

This is how copyleft code gets laundered into closed source programs.

All part of the plan.

[–] wonderingwanderer@sopuli.xyz 1 points 20 hours ago (3 children)

How would they launder it? Just declare it their own property because a few lines of code look similar? When there's no established connection between the developers and anyone who has access to the closed-source code?

That makes no sense. Please tell me that wouldn't hold up in court.

[–] ricecake@sh.itjust.works 1 points 6 hours ago

I believe what they're referring to is the training of models on open source code, which is then used to generate closed source code.
The break in connection you mention makes it not legally infringement, but now code derived from open source is closed source.

Because of the untested nature of the situation, it's unclear how it would unfold, likely hinging on how the request was formed.

We have similar precedent with reverse engineering, but the non sentient tool doing it makes it complicated.

[–] lagoon8622@sh.itjust.works 2 points 13 hours ago (1 children)

Please tell me that wouldn't hold up in court.

First tell us how much money you have. Then we'll be able to predict whether the courts will find in your favor or not

[–] wonderingwanderer@sopuli.xyz 1 points 7 hours ago

Sad but true...

[–] sem@piefed.blahaj.zone 2 points 14 hours ago (1 children)

First of all, who is going to discover the closed source use of gpl code and create a lawsuit anyway?

Second, the llm ingests the code, and then spits it back out, with maybe a few changes. That is how it benefits from copyleft code while stripping the license.

Maybe a human could do the same thing, but it would take much longer.

[–] wonderingwanderer@sopuli.xyz 1 points 7 hours ago

Wait, did you just move the goalposts? I thought the issue we were talking about was open-source developers who use LLM-generated code and unwittingly commit changes that contain allegedly closed-source snippets from the LLM's training data.

Now you want to talk about LLM training data that uses open-source code, and then closed-source developers commit changes that contain snippets of GPL code? That's fine. It's a change of topic, but we can talk about that too.

Just don't expect what I said before about the previous topic of discussion to apply to the new topic. If we're talking about something different now, I get to say different things. That's how it works.