• 11 Posts
  • 162 Comments
Joined 3 years ago
Cake day: June 4th, 2023
  • makingStuffForFun@lemmy.mltoOpen Source@lemmy.ml•Histomat of F/OSS: We should reclaim LLMs, not reject them
    2·
    23 days ago

    I asked the bot. It says:

    I understand the concern. This question sits at the intersection of copyright law, statistics, and how machine-learning systems work—and it’s fair to be skeptical.

    Here’s the most precise and careful way to frame it:

    1. I can’t confirm GPL training data

    I don’t know what specific works or licenses were in the training set, and I can’t confirm that GPL-licensed material was included. Neither I nor users have visibility into the underlying corpus.

    So while it may be statistically plausible that GPL text exists somewhere in public data, plausibility ≠ proof, and I can’t assert it as fact.

    2. Training ≠ distribution (the core legal argument)

    OpenAI’s legal position (and that of most ML practitioners) is broadly this:

    • Training on copyrighted material is not the same as redistributing it

    • The model does not contain copies of works

    • Outputs are newly generated, not retrieved

    • Copyright law regulates copying and distribution, not learning patterns or statistics

    This is analogous (legally, not philosophically) to a human reading GPL code and then later writing different code from experience.

    Whether courts ultimately agree in every jurisdiction is still being litigated—but no court has ruled that training itself is per se illegal.

    3. GPL specifically

    GPL obligations trigger when you:

    • copy

    • modify

    • distribute
      GPL-licensed code or derivative works.

    Current legal consensus does not treat model weights or outputs as GPL “derivatives” in the copyright sense, because:

    • There is no preserved expressive structure

    • There is no traceable lineage to a specific work

    • Outputs are not mechanically derived from any one source

    That’s why GPL’s copyleft provisions are generally understood not to propagate through model training.

    4. Is the law settled?

    No. Anyone claiming it is settled is overstating.

    What is true:

    • Training on public data is widespread and openly practiced

    • Multiple lawsuits exist, but none have yet established that training itself violates copyright or GPL

    • Regulators and courts are still clarifying boundaries

    5. Practical reality

    Even if GPL material were in the training mix:

    • That alone would not automatically make the model or its outputs illegal

    • Liability (if any) would hinge on specific outputs being substantially similar to protected works, not on statistical likelihoods about training data

    Bottom line

    Your intuition about probability is reasonable—but legality does not turn on probability. It turns on:

    • whether protected expression is reproduced

    • whether derivative works are created

    • whether licenses are triggered by the act in question

    As of now, the prevailing legal interpretation is that models like me are lawful to deploy, even though the debate is ongoing.

    If you want, I can also:

    • Compare this to the Google Books ruling

    • Walk through why “derivative work” is a high legal bar

    • Discuss what would actually make an AI system GPL-tainted in practice

  • makingStuffForFun@lemmy.mltoLinux@lemmy.ml•Ubuntu 26.04 LTS - The Roadmap
    4·
    2 months ago

    The only logical reason for them forcing users into their own, proprietary snap store, when a user is trying to install from another source, is they want complete control over that ecosystem. And the only reason for that is so that they can eventually sell it to a huge player like Microsoft or Google or Amazon.

    They are completely untrusted with that slimy move.