• onlinepersona@programming.dev
    link
    fedilink
    arrow-up
    2
    ·
    5 minutes ago

    A nice gesture, but let’s be honest, the system is corrupt and won’t care. The real way to fight is to use AI to opensource all proprietary software out there and watch them squeal.

  • chunes@lemmy.world
    link
    fedilink
    arrow-up
    3
    ·
    1 hour ago

    I’ve hated the prevalence of too-permissive licenses in the past 15 years. People need to go fucking brush up on their Stallman writings

    • apotheotic (she/her)@beehaw.org
      link
      fedilink
      English
      arrow-up
      7
      arrow-down
      3
      ·
      3 hours ago

      Permissive licenses are what everyone should strive toward. A world where we can share advancements and technologies freely with one another and innovate based on the prior work of others is a world where a shit load of cool stuff gets done. The issue arises when bad faith actors take advantage of it and act against the spirit of collaboration. The problem isn’t caused by the permissive license, but by the bad actor, and the latter is what should be addressed

      • SwooshBakery624 [they/them]@programming.dev
        link
        fedilink
        English
        arrow-up
        5
        ·
        2 hours ago

        A world where we can share advancements and technologies freely with one another and innovate based on the prior work of others is a world where a shit load of cool stuff gets done.

        And how does a copyleft license get in the way of that? On the contrary, with the GPL, I can be sure that the technology and code will be freely shared. Freely as in freedom, that’s the whole point.

        • apotheotic (she/her)@beehaw.org
          link
          fedilink
          English
          arrow-up
          2
          ·
          2 hours ago

          I misunderstood your initial point, I thought you were speaking against permissive/copyleft licenses generally. We agree with one another. Except in the “I can be sure that the technology and code will be freely shared” because just as bad actors can abuse a permissive license, bad actors (see: companies with enough money to just squash the legal case) can simply ignore a copyleft license. I think we 99% agree though and I love copyleft.

          • boonhet@lemmy.zip
            link
            fedilink
            arrow-up
            1
            ·
            50 minutes ago

            Permissive is the opposite of copyleft. Permissive is “here’s my code, do whatever the fuck you want”, copyleft is “here’s my code, you may use it but if your derivative work is available to other people then I dictate how it must be licensed”

          • SwooshBakery624 [they/them]@programming.dev
            link
            fedilink
            English
            arrow-up
            2
            ·
            2 hours ago

            because just as bad actors can abuse a permissive license, bad actors

            You are right, but with copyleft you at least have legal mechanisms to force the company to comply with the license. With MIT or BSD there aren’t any, because permissive licences don’t enforce any such restrictions.

            I think we 99% agree though and I love copyleft.

            Yup. And I love copyleft too.

  • Jay🚩@lemmy.ml
    link
    fedilink
    arrow-up
    5
    arrow-down
    1
    ·
    4 hours ago

    This won’t work. If they want to protect from AIs they need new license which probably won’t fit definition of open source by OSI. Also GPLv3 even won’t protect them.

  • anticurrent@sh.itjust.works
    link
    fedilink
    arrow-up
    19
    arrow-down
    3
    ·
    6 hours ago

    Isn’t AI and already rendering those licenses moot? AI data sets don’t care what type of license the code it scraped caries. and probably most AI code being generated for private companies is based on non-permissive licenses. yet nothing can be done about it.

    • im_fine_sandy@nord.pub
      link
      fedilink
      English
      arrow-up
      12
      ·
      4 hours ago

      I think the answer is “yes”.

      This feels like a token response to a systemic unsolvable problem.

      The article says itself talks about having models launder code so it can’t be considered a copy of the source.

    • lime!@feddit.nu
      link
      fedilink
      arrow-up
      7
      arrow-down
      3
      ·
      5 hours ago

      to look at it another way: since anything an llm spits out is public domain, whoever commanded it do so is automatically in breach of the gpl unless they can show evidence that there is no copyleft material in the training data at all.

      • rollerbang@lemmy.world
        link
        fedilink
        arrow-up
        4
        arrow-down
        1
        ·
        4 hours ago

        Afaik that’s not exactly so. I recall articles saying that significant input/prompt may influence that. Whether this is true or not I can’t say.

        • entwine@programming.dev
          link
          fedilink
          arrow-up
          2
          arrow-down
          1
          ·
          1 hour ago

          I recall articles saying that significant input/prompt may influence that. Whether this is true or not I can’t say.

          That’s not true. Until these issues have run through the courts, we won’t know what is or isn’t legal. The biggest court case I’m familiar with atm is the New York Times’ case that has yet to be resolved, and even then the ruling there will probably be too narrow to decide anything for code licensing. Hell, OpenAI/Microsoft might even settle to avoid a bad ruling, leaving all those questions unanswered.

          So the Tl;Dr is that anyone using LLMs to code (in any capacity) is taking a risk, since the legality of it is still uncertain. It’s not outside the realm of possibility that some court will rule that LLMs trained on stolen data are illegal, and the outputs of those models are infringing.

        • lime!@feddit.nu
          link
          fedilink
          arrow-up
          6
          arrow-down
          2
          ·
          4 hours ago

          can’t be. if there is gpled code in the training data, all code must be gpl since the model is one work. and since it can’t, that’s a breach.

            • entwine@programming.dev
              link
              fedilink
              arrow-up
              1
              arrow-down
              1
              ·
              1 hour ago

              I hate seeing this kind of doomerism around AI discussions. A future where we have no rights is not inevitable.

              We know for a fact that OpenAI, Anthropic, Google etc trained on GPL code. They haven’t claimed otherwise, and this isn’t something they’re trying to hide.

              We also know what the various open source models were trained on, since they’re open source.

              We can pass laws that require LLM providers to disclose their data set in some way, eg through independent audits. Trump is the one who didn’t want AI regulation, and he basically just lost all ability to make that a reality. The final six weeks of the pedophile congress isn’t likely to accomplish anything on that front, and even if they do, the incoming congress can reverse it.

              This is the time to energize people, not complain on the internet.

    • Kissaki@programming.dev
      link
      fedilink
      English
      arrow-up
      5
      ·
      6 hours ago

      If you can compare the code and it matches you probably have a good case if the AI user can’t demonstrate it’s not coming from you.

      There’s different kinds of datasets. Some respect, select and disclose licenses, others do not.

      Some model trainers use any data they can, others are selective on what they train on.

      It can also be a decision on principle rather than current or future enforcability. If you say “don’t copy this” and someone blatantly does, the morality is clearer than if you didn’t specifically say that.

      There’s also a question of how court rulings and law may change the situation of enforcability and usage/ignorance risk.

      MIT requires attribution too. GPL is, at the very least, a stronger statement of intention and demand. It can also be seen as protest or indication of a broader move of corporate AI exploitation leading to damage to the whole FOSS ecosystem, with additional restrictions being applied. Corps that would use AI now can’t use the MIT product anymore like before.

      • anticurrent@sh.itjust.works
        link
        fedilink
        arrow-up
        6
        ·
        6 hours ago

        First, you can’t even compare the code if you don’t have access to it, you don’t have access to google’s or facebook’s code.

        Second who can even legally challenge entities with pockets as deep as the ocean.

        Third courts will probably classify AI generated code based of non-permissive licenses as fair use, so It’s a lost cause anyway.

  • Kissaki@programming.dev
    link
    fedilink
    English
    arrow-up
    7
    ·
    6 hours ago

    It would be interesting to see whether the BSD community finds a way to keep working with Asahi under the new terms.

    They could go GPL too. :)

    Asahi dual-licensing would be difficult, because then it’d be out there as MIT or BSD, which they don’t want. The BSD using custom-licensed parts - the BSD projects probably don’t want that.

    • misk@piefed.socialOP
      link
      fedilink
      English
      arrow-up
      24
      arrow-down
      1
      ·
      8 hours ago

      AI bubble has shown that if you don’t have billions of dollars for lawyers, your IP will be copied and compressed into an LLM and you won’t be able to do anything about it, regardless of license. But at least Apple won’t be able to profit from Asahi team work and BSDs won’t be able to use drivers from Asahi. So much winning.

      • Axolotl.cpp@lemmy.dbzer0.com
        link
        fedilink
        arrow-up
        2
        ·
        2 hours ago

        Apple is an asshole company, if they wanted community contribution for their drivers, they could’ve made their stuff open, now they can go fuck off, full stop

  • Kissaki@programming.dev
    link
    fedilink
    English
    arrow-up
    6
    ·
    6 hours ago

    “Sad to see Asahi out there burning bridges for no reason… relicensing m1n1 and drivers under GPL2-or-later, seemingly without the consent of all prior contributors, under the guise of “defending against AI bad actors”, seems entirely disingenuous and misguided.”

    “no reason” but there’s reasons anyway and those are “entirely disingenuous and misguided”

    Too bad [their] twitter posts don’t go into actual arguments. Why is it supposedly disingenuous? Why misguided? Are there better alternatives? Probably not.

  • AliOski@feddit.nl
    link
    fedilink
    arrow-up
    5
    arrow-down
    1
    ·
    7 hours ago

    I am not entirely sure why the GPLv2 license wouldn’t work for the BSDs, but either way I doubt that the problem was so big that it really required a license change. Everything in life is a trade-off, and I think the trade-off of not supporting the BSDs to prevent potential bad faith actors from “stealing the code without attribution” is a really bad trade-off.

    • Kissaki@programming.dev
      link
      fedilink
      English
      arrow-up
      4
      ·
      6 hours ago

      I am not entirely sure why the GPLv2 license wouldn’t work for the BSDs,

      The GPL is a copyleft license. Derivative and combined works must be published under the same license.

      You can use BSD with GPL and then publish as GPL, but you can not publish as BSD.

      • AliOski@feddit.nl
        link
        fedilink
        arrow-up
        1
        ·
        6 hours ago

        I understand that the licenses are different. What I dont understand is why the BSD operating systems cannot make use of Asahi if it is GPL licensed instead of MIT licensed.

        • AnyOldName3@lemmy.world
          link
          fedilink
          arrow-up
          3
          ·
          4 hours ago

          Because, as the comment you’re replying to says, if they include any GPL code, the whole combined work has to be licensed as GPL, and the BSD operating systems don’t want to be GPL.

    • pulsewidth@lemmy.world
      link
      fedilink
      arrow-up
      11
      ·
      8 hours ago

      If you read the article, you’d see…

      What the GPL changes is the commercial benefit. Under MIT, someone can take Asahi’s code, close it up, and sell a product, and that’s perfectly legal as long as the notice stays in.

      Under the GPL, anyone who distributes a modified version has to release the source under the same license. You can’t legally build a closed, paid Apple Silicon distro on top of GPL code. And if a product’s source has to be public, the copying is easier to spot.

      The article explains that the GPL license will enable legal action against future use along those lines - and that WINE did the same thing back in the 90s, and its worked for them.

      • lime!@feddit.nu
        link
        fedilink
        arrow-up
        2
        ·
        5 hours ago

        it’s weird that they just phrase it as “has to release the source code”, it skips over the most important part. they have to release the source to any user who asks for it. if they want to be assholes about it they can request proof of purchase. unless the product is free, but then the question becomes “so what’s the problem again?”.

      • illusionist@lemmy.zip
        link
        fedilink
        arrow-up
        1
        arrow-down
        6
        ·
        8 hours ago

        I deleted my comment a minute later because I didn’t want to discuss it any further.

        But since you already replied: with ai rewriting, I don’t think that the switch to gpl changes anything. Even if the bad actors now publish their code, how would it change what they do?

        • ApeNo1@lemmy.world
          link
          fedilink
          arrow-up
          5
          ·
          7 hours ago

          Because it includes the modified code from the GPL licensed code and any derivative works, which in many cases may mean the source code to their entire application including what they may consider sensitive IP has to be provided or readily made available to customers who have paid for the software. Further to this any paying customer who receives this source code can make it all publicly available for free which can effectivelly kill the paid software.