I have been using Linux for over 8 months now, and my primary distribution of choice was Debian.

Debian recently conducted a community vote on allowing AI contributions, and it ended up allowing responsible AI contributions.

What is this responsible? How can AI commits be responsible? There are thousands of reasons to not use AI, and the primary reason is AI is a thief.

How did you react to Debian’s decision? Did you switch distros? Which one was your option, and why?

Also, when the Linux kernel itself allows AI commits, is there any practicality in a Linux distribution strictly limiting or restricting AI commits?

I have no serious usability issue with Debian now but am concerned about the use of AI even in my Linux distribution. Should I keep going with Debian or consider any other distribution, as I only have 8+ months of experience as a daily Linux user? I tried almost all Linux distros and am comfortable with everything except Void Linux and highly complex ones like Gentoo.

  • cmnybo ( cmnybo@discuss.tchncs.de ) 
    link
    fedilink
    English
    arrow-up
    47
    ·
    1 month ago

    There will never be an AI free Linux distro again since it’s allowed in the kernel. I would certainly prefer to use a distro that doesn’t allow vibe coded programs though. That junk is unmaintainable and will be abandoned when the creator can no longer afford the tokens.

  • Arthur Besse ( cypherpunks@lemmy.ml ) 
    link
    fedilink
    English
    arrow-up
    17
    ·
    edit-2
    1 month ago

    Are Anti-AI Linux distributions practical?

    It’s not possible to have a 100% no-LLM-coding-involved Linux distro anymore now that the kernel itself is welcoming LLM-assisted contributions, but it’s still possible to say that everything which the distro produces itself will not use AI.

    How can AI commits be responsible?

    What Debian means is: by reading what it produces and not just blindly accepting it but having humans review it carefully. The quality of LLM-assisted software is highly variable. Experienced people like Debian and Linux kernel developers are much less likely to publish very bad slop than inexperienced developers who are newly able to make a thing work well enough to ship it.

    I am concerned about the extent of Debian’s embrace of LLMs but I still have a lot more confidence in them than most other distros (especially small hardcore-anti-AI distro projects lacking sufficient developer capacity to even keep up with security updates).

    I expect we’ll be seeing lots more things like this non-upstreamable-because-AI hardware enablement and distros like Nura (formerly postmarketOS) will either either adopt more nuanced LLM policies or be forked.

    I am doubtful about if there will be any serious distros with hard LLM bans in a few years from now. But also, perhaps the bubble will have burst by then, so hosted inference won’t be so cheap and the use of LLMs will probably be quite different.

    the primary reason is AI is a thief

    This is not the primary reason for most people, I don’t think. I think the fact that it increases complexity while reducing human understanding is the biggest problem; it’s possible (easy even) now to produce mountains of good-enough-by-many-metrics source code which the person doing the prompting has very little comprehension of. The fact that it is also a plagiarism machine is far less of a problem than this. (There are a litany of other problems too of course, several others of which I would also rate as worse than the plagiarism aspect.)

    • Yeah the Debian Project’s position makes a lot of sense to me. They’re basically saying that they won’t be wasting a bunch of resources trying to seek out LLM generated code and purge it and will instead just focus on making sure ALL the code is up to their quality standards. This will likely mean they spend a lot of time sifting out slop anyway, and will allow them to keep just focusing on making the project do what it’s always done. Ship a stable, usable, and free distro.

  • dusk ( dusk@piefed.social ) 
    link
    fedilink
    English
    arrow-up
    16
    ·
    1 month ago

    “How did you react to Debian’s decision?”

    I deleted it, debian was thankfully not my main, just a backup/something of interest.

    The ‘vote’ itself seemed dodgy, every option was going to ai in some form, or another.

  • hendrik ( hendrik@palaver.p3x.de ) 
    link
    fedilink
    English
    arrow-up
    15
    ·
    1 month ago

    I’ve been using Debian for a long time and honestly, I’m not going to worry about this too much as of today. We got that decision, yes. But I don’t think I’ve seen any consequences, yet. And I always try to judge people by what they actually do. Less so by what they say.

    I say that the last word hasn’t been said yet. On this whole AI thing. We still got many Linux people who don’t really appreciate AI. The entire community isn’t really fond of it. We got people who say there isn’t a way to make use of it responsibly. I have a hunch there’s more to this story. But only time will tell. Until then I’m going to continue using Debian, just like I have for the past 10-15 years. I trust the community distributions, they faced other challenges before. And usually they’re not half bad at facing challenges and ultimately doing the right thing.

    Doesn’t have to be easy. Sometimes we’re headed the wrong direction for a while. But what matters IMO is the result. And I’m positive they’ll find some way to deal with this. I don’t think AI fits Debian’s identity at all. Would be a big surprise to me if they don’t realize it as well.

  • Mordikan ( Mordikan@kbin.earth ) 
    link
    fedilink
    arrow-up
    15
    ·
    1 month ago

    What is this responsible? How can AI commits be responsible? There are thousands of reasons to not use AI, and the primary reason is AI is a thief.

    I feel like you aren’t actually asking a legitimate question and are just trying to soapbox, but this is covered by Debian here: https://lists.debian.org/debian-devel-announce/2026/08/msg00005.html

    As far as what the consequences of failing to follow that policy is, it would be covered under the Debian code of conduct: https://www.debian.org/code_of_conduct_interpretation.html

    NOTE: I am not a Debian user. I just performed a basic search to find the answer to that question.

  • No. It’s not practical.

    No matter how you feel about ai or how you think it is wrong, the increased tempo of bug fixes and security patches necessitates either manpower beyond what is feasible for volunteer projects or the use of ai tools.

    It’s an arms race and you can’t opt out without just missing the patch schedule.

    • rumba ( rumba@lemmy.zip ) 
      link
      fedilink
      English
      arrow-up
      1
      ·
      1 month ago

      Yeah, all the FOSS communities have been starving for labor since they started. Likely the best we could hope for is that the true experts at the top are maintaining a critical eye on what makes it in.

        • rumba ( rumba@lemmy.zip ) 
          link
          fedilink
          English
          arrow-up
          1
          ·
          1 month ago

          It’s a mix right?

          In some cases, you have absolute neophyte coders trying to shove unvetted vibe code in. There needs to be some bars on entry for what is submitted. I’d like to see at least mid level code in the same style and verbosity and not something that’s on the fringe of the vibe where it failed 15 times and ended up shoving some great atrocity in for a lack of context. As long as the person asking for a PR isn’t trying to insert horrors, inspecting the input using tools isn’t the worst thing either.

  • Unless you literally programmed every component yourself, you can’t get away from some level of LLM involvement, even if the distro itself bans it. There is no 100% certain way to check code for LLM use. So if a developer doesn’t disclose it, and the maintainers accept the code, it’s in the official codebase now.

    There’s a deeper problem though, which is a problem of demarcation. What counts as an “AI contribution” to you? Obviously vibe-coding is. But what about more subtle uses?

    What if a developer uses an LLM to read the code and suggest a way to make a certain contribution, but it never actually generates any code, the developer implements the LLM’s suggestion completely by hand. Does that count?

    What about if a developer hand writes 95% of the code themselves, but that last 5% they aren’t as confident in, so they have the LLM generate it. Does that count?

    What if an extremely experienced developer uses an LLM to generate 100% of the code, but spends hours going over ever single line making sure it is correct and making little tweaks before submitting the code?

    What if a developer writes the initial code 100% by hand, and only uses an LLM to go through and optimize the formatting and performance before submitting it?

    What if a developer writes 100% of the code by hand, but uses an LLM to generate a bunch of unit tests and documentation?

    These are just some of the ways that LLMs can be involved in the process of software development, and most of these wouldn’t have any real chance of being caught by a maintainer doing some sort of scan to detect LLM usage.

    I’m not saying these uses are or aren’t justifiable/acceptable, but my point is it’s often not clear what people consider to be “over the line”. Almost no experienced devs in the FOSS world are advocating for the 100% vibe-code/token-maxing approach. But lots of them are comfortable with using LLMs in similar ways to what I listed earlier.

    The tough truth is that you’re almost certainly already using software that has LLM involvement at some level. Short of going full Amish mode, or using completely pre-LLM software in some kind of air gapped setup, you’re not going to be able to avoid it.

    • Man, my friend said he made a web app. He asked me if it would be secure to deploy. I check the front end and immediately check if his formatting was readable.

      Two javascript blocks embedded: one was beautified, normal, tabbed out.

      The other block was debeautified, which JS developers do so people can’t steal their code (as if that works these days).

      I said, “You didn’t make this.”

      “Yeah I did!”

      “You used AI.”

      “But I wrote the prompts!”

      "To prompt a computer to steal two separate snippets of javascript from actual developers to achieve the goal.

      "Man, this is fine for prototyping, just to demo an idea. But I wouldn’t release this to the public, because if I saw that, I am going to use the tools I already have, and my LLM to speed up the actions, and I will show you how hackable the app actually is.

      “You didn’t make a steak. You ordered a steak and got a McRib with carrots.”

      He responds, “Does it look ok?”

      “Yeah, we can use the css, and we can adjust that as needed, but if your frontend is this sloppy, I wouldn’t release the backend and take customer data. Hell no.”

    • technocrit ( technocrit@lemmy.dbzer0.com ) 
      link
      fedilink
      arrow-up
      1
      ·
      edit-2
      1 month ago

      What if someone does a copy/paste of a code snippet from a google search and then modified it for their own purposes?

      According to the grifters, this is “AI” but it’s not and nobody cares. There is no boundary for something that doesn’t exist (“AI”). That’s fundamental to the grift.

  • AI is a tool. You already trust the developers to build an operating system with the tools available.

    From the Debian announcement

    The Debian Project nevertheless expects that all contributions submitted to Debian, regardless of how and with which tools they were produced, satisfy the same standards of quality, correctness, maintainability, and legal compliance. The use of a generative AI tool does not diminish the contributor’s responsibility for the work they submit. Contributors are expected to understand, review, test, and, where appropriate, modify AI-assisted output before incorporating it into Debian. Blindly accepting or uploading AI-generated material without appropriate human review is inconsistent with Debian’s established development practices.

    It’s quite clear they don’t allow vibe coding. As you say, the kernal itself allows AI contributions in a similar way.

    If you’re worried about the ethical aspects of AI then you’ll probably have to move to NetBSD. If you’re only worried about quality this is a non issue.

  • cerement ( cerement@slrpnk.net ) 
    link
    fedilink
    arrow-up
    6
    ·
    1 month ago

    Most of it comes down to personally mitigating the damages:

    • start with ElementaryOS and Pantheon/Gnome, then decide which path you want to follow
    • if you’re hardcore, go for NetBSD or MirBSD or 9front/Plan9 instead of Linux
    • on the Linux side: ElementaryOS, Gentoo, Chimera Linux, AerynOS, and Nura/PostmarketOS all have strong LLM policies
      • along those lines: Gnome and Cosmic haven’t gone soft on AI the way KDE has
    • Starlight Network No-AI List is one jumping off point, but there are several other lists including repo-slopscore and Weird Little Guys
    • dusk ( dusk@piefed.social ) 
      link
      fedilink
      English
      arrow-up
      6
      ·
      1 month ago

      Weird little guys is an interesting read, I was surprised to find Jeff Geerling there, I always thought he was just a really crappy youtuber, with really stupid fans. I was half expecting to find Linus SebastiDouche on the list afterwards.

      • I liked him a lot. I first learned about Jellyfin from his video just a few years ago. I would’ve bet money that Linus TT would be on such a list before Jeff Geerling. I don’t have a parasocial relationship or idolize YouTubers, but I’m definitely still disappointed. (Maybe I was a stupid fan, but now I’m just stupid 💀)

        • dusk ( dusk@piefed.social ) 
          link
          fedilink
          English
          arrow-up
          2
          ·
          1 month ago

          Jeff never made sense to me, his videos seemed dodgy, the first one I saw he was jumping on the linus screwdriver silly hype train, but his fans just adored him, to the point I assumed some of them were drooling. I didn’t see much more of him over the years, so my view is definitely limited.

        • Alex ( stsquad@lemmy.ml ) 
          link
          fedilink
          arrow-up
          1
          ·
          1 month ago

          I do like Jeff’s videos, he comes across as a true engineering nerd. I find his SBC reviews to be pretty thorough and some of his other videos make for an interesting side quest on stuff he’s interested in.

          I certainly don’t view DeVaults purity list as the authority on if I should watch someone’s videos or not.

  • Are Anti-AI Linux distributions practical?

    No, because there’s no such thing as “AI”. It’s irrational to try to remove something that doesn’t exist. People will continue using computers to compute regardless.

    On the other hand I don’t think developers should accept slop. I guess that’s what “responsible” means.