• notSys ( notSys@lemmy.cafe ) 
          link
          fedilink
          English
          arrow-up
          3
          ·
          2 months ago

          So you agree with me, that AI is not fascist, but at the same time you say that one of goals of fascism is for people to think that AI is not fascist.

          Am I reading it right?

          • You are, in fact, not reading that right.

            Let me spell it for you because you apparently fell victim to the previously mentioned attack on education: AI is a tool. Like any tool it is not inherently evil, but the fascists love to take potentially useful tools and turn them around to cause as much suffering as possible. In this case, AI (more specifically LLMs) is used to make people reliant on it by getting them addicted to outsourcing all their problem solving skills while also reducing the value of art and artists of all types so they can take the money that artists would have made and also control ‘art’ (can’t have any pesky artists drawing pictures of people beating the nazis up) all the while sucking up every single data point about you.

            If that’s all too complicated for you to understand, I guess you could over simplify it as “fascism is when AI”

            • notSys ( notSys@lemmy.cafe ) 
              link
              fedilink
              English
              arrow-up
              3
              ·
              2 months ago

              Does that mean internet is fascist? Search engines? Calculators? Writing?

              All of those things outsource your congnitive skills.

              Almost nobody is saying that AI art generation is a complete subsitute for conventional art.

              Even if all of that were true, it wouldn’t make AI fascist, but totalitarian.

  • The point isn’t so much the quality of the code itself.

    The point is that AI is an inefficient power-wasting piece of trash, and the data centres that power it have significant negative impacts on people and the environment, all for the sake of devs being lazy idiots. And you’d have to be an idiot to let AI take away your skills.

  • jobbies ( jobbies@lemmy.zip ) 
    link
    fedilink
    arrow-up
    26
    ·
    2 months ago

    I’m not an AI evangelist but I am open-minded. I think Debian’s decision is balanced, and more importantly realistic.

    There’s a difference between vibe coding and using AI to improve productivity. I’m a dev and pretty much everyone I know is using AI in some way. Yes they’ll lose contributors initially but Debian would lose more in the long run if they’d outright banned it.

    For all those who are saying ‘AI supports fascists’ - the most popular models right now are Chinese. Very oppressive and paranoid government but definitely not fascist.

    For all those that say ‘AI causes global warming’ - you’re correct, but unless you’ve got your own solar panels, so does your non-AI gaming rig. And your gas-driven car.

    • I think it’s helpful to separate the problems of the technology itself from all the BS that big tech companies engage in when developing and pushing it.

      Say you only use small, open-weight models that are hosted locally in a data center that is conscientious, environmentally clean, has strict data privacy policies and doesn’t pull the bullshit big-tech do.

      You use them minimally and responsibly, you don’t over-rely on them. Is there a problem in that case?

      • jobbies ( jobbies@lemmy.zip ) 
        link
        fedilink
        arrow-up
        3
        ·
        2 months ago

        You use them minimally and responsibly, you don’t over-rely on them. Is there a problem in that case?

        Responsibly is the key word there. I.e. vibe-coding an entire project full of security risks without understanding the architecture or languages used. Vs. using LLMs to error check code, brainstorm a project, write code you feel confident you can review yourself.

        Also, like you say, hosting locally. Or using a provider like Mistral that is European, not evil, uses France’s abundant nuclear power…

          • jobbies ( jobbies@lemmy.zip ) 
            link
            fedilink
            arrow-up
            6
            ·
            2 months ago

            I sort-of agree, but what are you disclosing?

            If a project on github was 100% vibe coded with no (initial) human review - I’d want to know that.

            If a project was 60% hand coded, 40% vibes but reviewed by a human … yeah in the interests of openness it doesn’t hurt to disclose that.

            If a project was 100% hand cranked but checked by an LLM? If its open source I’m not sure I need to know that.

            If a project was 100% hand cranked and human-reviewed, is open source but the dev used an LLM to keep a to do list of tasks… no I don’t need to know that.

            And like someone else pointed out - how exactly do you verify that AI was not used at all for any part of a project?

            Also, you know Microsoft will be vibe-coding its products. Would that stop you using Windows, Xbox, M365 etc?

    • dubs ( dubs@lemmy.dbzer0.com ) 
      link
      fedilink
      arrow-up
      6
      ·
      2 months ago

      Agreed. I think they should have pushed for stronger disclosure requirements, but I also realise that isn’t actually enforceable.

      I also find it very telling that people will talk about the negative parts of AI, but not acknowledge other automation tools that perpetuate the same problems. My experience is that most people’s complaints have a real basis, but they are just mis-diagnosed.

      The problems seem to be our economic and societal structures, and AI is the new fancy tool that exacerbates those problems. But I’ve not heard a good reason why AI itself is that problem.

    • Auli ( Auli@lemmy.ca ) 
      link
      fedilink
      English
      arrow-up
      1
      ·
      2 months ago

      Oh I’m not perfect so everything bad is OK argument. Like we need at this time to be burning more fossil fuels.

  • chris ( chris@l.roofo.cc ) 
    link
    fedilink
    arrow-up
    14
    ·
    edit-2
    2 months ago

    Well what would the disclosure requirement improve? It’s unenforceable and it just gets in the way of evaluating the code based on quality. Every code should have high standards. Bad llm code is just as bad as bad human code.

    If a project allows llm contributions then disclosing it will only make people wary of the wrong things. Putting a badge on it is not helpful anymore if it’s allowed. I have seen good llm code and bad human code.

    • kibiz0r ( kibiz0r@midwest.social ) 
      link
      fedilink
      English
      arrow-up
      40
      ·
      2 months ago

      Code is a liability. The only thing that balances it out is people who understand the code. The people are the asset.

      If you contribute LLM-generated code but not your understanding, you’ve essentially taken out a loan in the maintainers’ names.

      • chris ( chris@l.roofo.cc ) 
        link
        fedilink
        arrow-up
        1
        ·
        edit-2
        2 months ago

        Not only the contributor has to understand code. There have always been flyby contributers that just add their code and that’s it. So if a PR adds code that cannot be maintained by others it can’t be added. That is part of the review process. That is part of evaluating based on quality. It’s unimportant if a human or an llm wrote something unmaintainable.

    • ProdigalFrog ( ProdigalFrog@slrpnk.net ) OP
      link
      fedilink
      English
      arrow-up
      7
      ·
      2 months ago

      The Free Software Foundation of Europe recently published an article detailing why it’s legally quite important for developers to disclose and carefully catalog which code was created by LLMs.

      https://fsfe.org/news/2026/news-20260825-01.html

      Recommendations for AI usage in Free Software contributions

      With these issues in mind, the recently published Recommendations When Using LLM-Backed Generative AI Systems for FOSS Contributions by the SFC outlines some of the legal difficulties for copyright and licensing that generative systems have created for software developers who wish to write, maintain, or contribute to Free Software projects.

      Notably for the purposes of this article, the SFC recommends the full recording and disclosure of how and when an AI tool was used to assist in the creation of a contribution. As stated by the SFC:

      “FOSS project leaders cannot make good decisions about LLM-gen-AI policy if they cannot survey which contributions were assisted, and how much they are assisted. Part of the contribution process should (at least) include a disclosure of what LLM-gen-AI system was used, its version (as these system change over time), and a brief description of how the system assisted the contributor. This information should be included in a machine-readable format in commit logs."

      Indeed, such disclosure can be an important foundational step to allow for the accurate assessment of the copyrightability of code that has been assisted or generated by AI tools, in order to assess their licensability into Free Software. Open and clear disclosure is a helpful step for the Free Software community to maintain a healthy licensing ecosystem, which is currently threatened by the legal uncertainties that come with the advent of generative AI.

      Additionally, it is worthwhile for developers to document in some capacity the extent of human work that they have done in their software projects, whether it be the writing of code, the selection and arrangement of components within the project, or the extent of human modification of machine generated content.

      • chris ( chris@l.roofo.cc ) 
        link
        fedilink
        arrow-up
        3
        ·
        2 months ago

        IANAL but from my naive perspective it might make more sense to not disclose this because no one can prove that something was written by AI if no one discloses it. That means for me that any claims that a certain part cannot be copyrighted are hard or even impossible to make.

  • adarza ( adarza@lemmy.ca ) 
    link
    fedilink
    English
    arrow-up
    12
    ·
    2 months ago

    and the death blow is when more like-minded developers do the same… there won’t be enough left that would vote to change policy to try to lure some back.

  • AceFuzzLord ( AceFuzzLord@lemmy.zip ) 
    link
    fedilink
    arrow-up
    11
    ·
    2 months ago

    Looks like I better start learning OpenBSD ASAP. I really like my distro of choice, but if the distro it’s based off of is shooting itself in the foot, I have to switch over massive ethical concerns!

    Second I find out I can put a second drive in my desktop, I plan on using it to learn to make something a lot less hostile to the actual people helping develop the OS. And OpenBSD sounds like a fun choice for now… at least until I find they have started betraying the actual people.