this post was submitted on 12 Sep 2026
122 points (97.7% liked)

Linux

19180 readers
390 users here now

Welcome to c/linux!

Welcome to our thriving Linux community! Whether you're a seasoned Linux enthusiast or just starting your journey, we're excited to have you here. Explore, learn, and collaborate with like-minded individuals who share a passion for open-source software and the endless possibilities it offers. Together, let's dive into the world of Linux and embrace the power of freedom, customization, and innovation. Enjoy your stay and feel free to join the vibrant discussions that await you!

Rules:

  1. Stay on topic: Posts and discussions should be related to Linux, open source software, and related technologies.

  2. Be respectful: Treat fellow community members with respect and courtesy.

  3. Quality over quantity: Share informative and thought-provoking content.

  4. No spam or self-promotion: Avoid excessive self-promotion or spamming.

  5. No NSFW adult content

  6. Follow general lemmy guidelines.

founded 3 years ago
MODERATORS
top 50 comments
sorted by: hot top controversial new old
[–] A_norny_mousse@piefed.zip 59 points 1 week ago* (last edited 1 week ago) (5 children)

A maintainer. Apparently went into a hissy fit because people pointed out to him that he broke the rules. That said, the critics probably weren't very nice to him either.

Ah, Linux drama.

BTW, the rules sound sensible to me:

"In this section, "AI" refers to generative artificial intelligence tools, including Large Language Models and similar technologies.

All contributions are expected to be made by humans. AI tools may be used for research and learning, but all content in contributions must originate from and be understood by the contributor. This includes code, documentation, issues, security reports, pull request descriptions, and comments in all Void Linux community spaces.

ALL usage of AI tools MUST be disclosed.

Do not bring AI review tools into pull requests.

Usage of AI-powered human-language translation tools is acceptable to facilitate contributions across language barriers."

Esp. this part: "contributions must (...) be understood by the contributor."

I'm in a smaller community that sees a lot of AI-supported app development recently and while the outcome can occasionally be good, I'm not sure it's worth taking those few good apples with the flood of vibe coded projects, and their "developers" that tend to get very defensive when simply asked about things.

Not saying this is the case here though.

[–] HaraldvonBlauzahn@feddit.org 9 points 1 week ago* (last edited 1 week ago) (1 children)

On the rules, citing hperrin:

It sounds like their policy is basically the same as Human Contribution Policy 2-TR. That’s awesome.

[–] A_norny_mousse@piefed.zip 5 points 1 week ago (1 children)

Great that people are working on that. And adopting it.

[–] HaraldvonBlauzahn@feddit.org 3 points 1 week ago* (last edited 1 week ago)

I think establishing new rules and boundaries in a new territory will never happen entirely without conflict. Nice if people still behave like gentlemen.

load more comments (4 replies)
[–] Sanctus@anarchist.nexus 23 points 1 week ago (1 children)

I think the thing I hate most about AI is what it has done to all of our psyche. Look at this.

[–] A_norny_mousse@piefed.zip 5 points 1 week ago* (last edited 1 week ago)

Yeah it really fucks with your psyche.

That, at first glance, you cannot distinguish any digital work from being real work, or the result of telling an AI to do it. And the result isn't anybody's work. Except of those the AI stole from.

But I have seen meltdowns like this long before any sort of LLM-based fakery.

As I wrote before: "Linux drama"

[–] Endymion_Mallorn@kbin.melroy.org 10 points 1 week ago (1 children)

Cool. Let the slop users go join the fascist DHH in Omacom. Then again, I'm giving a much closer look at Haiku & BSD again since a slop generator was used in the Linux kernel.

[–] HaraldvonBlauzahn@feddit.org 0 points 1 week ago (4 children)

Then again, I’m giving a much closer look at Haiku & BSD again since a slop generator was used in the Linux kernel.

As far as I understand, the Linux kernel uses LLMs in practice for code review, not for code generation. And they do not replace human review with it, but use it in addition.

[–] sem@piefed.blahaj.zone 1 points 5 days ago (1 children)

Seeking to understand: this type of code review LLM usage is disallowed in the Void project, correct?

You cannot make code reviews or security audits which originated from an LLM?

[–] HaraldvonBlauzahn@feddit.org 2 points 5 days ago

The rules are cited above. As I read it, you can make code reviews using LLMs.

But:

  • You have to disclose this usage
  • You have to describe the results in your own words
  • You need to make a fix yourself.
[–] AceFuzzLord@lemmy.zip 9 points 1 week ago

I don't know about the other guy, but I personally see that as a very slippery slope. You start with human reviewed code. Then the people who know how to code properly disappear after being bogged down with genAI code until they snap, regardless of whether it's 3rd party submitted or code you see being generated to try and help you. Then in comes all sorts of code that looks good because nobody can read and/or understand it.

That's part of my Programmer Replacement Theory. You replace the competent programmers with sloperators and you can waltz in to easily take control over something like open source in general. Triple EEE has never ended and this is just another extension of it, IMO.

[–] racketlauncher831@lemmy.ml 2 points 1 week ago

Not replacing human reviewers how? If you allow LLM to review it, human reviewers are "freed" to do something else. Soon there will be no new blood in the reviewer's bracket, and the old reviewers will get rusty on their reviewing skill too.

And this does not stop at reviewing. I bet you $50.

It doesn't matter. It was allowed at all. Linux is now as complicit with the slopiverse as X, Meta, Alphabet, Nvidia, and the rest of the bastards.

There are just two stances on this, and Linux has picked one. Either you're in or you're out. There are no more gray areas when the harm is proven and the damage is actively being done. There's the moral choice where you denounce the evil, and there's being evil.

[–] EnsignWashout@startrek.website 7 points 1 week ago* (last edited 1 week ago) (3 children)

I'm so tired of "Ai big number" headlines. 100+ packages - but how many good ones? (Genuinely, I don't know, as I don't the recognize those listed.)

We need projects that diligently keep the slop out. We don't need every protect to do so, but it is critical that some do.

We have Meta and Microsoft to provide quick-to-market low quality shit.

The version of Linux that matters is the slow thoughtful good software.

I'm not mad at slop slingers, aa long as they don't secretly inject slop risk where not welcome.

Edit: Thanks for responses.

For anyone who has read this far, I encourage seeing responses below for informative and nuanced thoughts on this.

[–] HaraldvonBlauzahn@feddit.org 12 points 1 week ago* (last edited 1 week ago)

I’m so tired of “Ai big number” headlines. 100+ packages - but how many good ones? (Genuinely, I don’t know, as I don’t the recognize those listed.)

There might be a bit confusion. A package maintainer does not (necessarily) author the packages (the source code of the projects they contain), but typically maintains build scripts and security patches for upstream packages maintained by their authors. This is necessary because build systems and scripts are complex and packages from one distro would usually not fit into another one.

In other words, most code he/she produces are build scripts, and testing and adapting updates. And yes, this is still a lot of work.

[–] Dran_Arcana@lemmy.world 6 points 1 week ago

A lot of those packages are pretty core to deployments, the docker ones in particular are probably on every developer/homelabber using void (so everyone probably?)

The docker runtimes handle a lot of the container sandboxing and security configuration, and are a huge source of container escape vulnerability.

[–] HaraldvonBlauzahn@feddit.org 4 points 1 week ago (1 children)

It is a small and comperatively frugal distro. Which pretty much makes sense for an AI-free distro.

The now orphaned packages include Adapta, Autodia, SFML, abootimg, alacritty, arpwatch, asus-kbd-backlight, backblaze-b2, bash-preexec, beep, binfmt-support, bitlbee-facebook, bitlbee-steam, cdm, clementine, crane, csound, daemonize, darkhttpd, dep, diff-pdf, docker-cli, docker-gc, docker-gen, dtc, embree, entr, etcd, fcron, flannel, flint, font-fontin, forego, freeplane, fscrypt, gede, gettext-stub, git-cola, gkill, glock, go-bindata, go-jira, hans, hivex, hopper, hostaliases, hugo, iio-sensor-proxy, indicator-doom-cpu, interbench, ispc, jbigkit, kaitai-struct-compiler, kubernetes, kvirc, libguestfs, libnfc, libpodofo0.9.7, logstalgia, massren, mbox, mfoc, mkinitcpio-nfs-utils, mksh, moby, motion, openresolv, packer, pd, perl-Template-Toolkit, pinktrace, podofo, python3-Arrow, python3-b2sdk, python3-pdm-backend, python3-xattr, racket, rakarrack, rancher-compose, rmlint, rng-tools, rocker, runit-swap, sassc, scanmem, schroot, sift, splix, sublime-text3, subtle, supermin, sydbox, tag, tbb, terraform, terragrunt, texmaker, thermald, trollock, ttf-ubuntu-font-family, urbanterror-data, urbanterror, usbredir, vagrant, vba-m, virt-manager, virtme, webcat, websocketd, wpa_actiond, xboxdrv, xcompmgr, and yoshimi.

I am using a few of them, for example virt-manager and racket.

[–] canaryWart@programming.dev 0 points 1 week ago

The handful that've crossed paths with are mostly dependencies of things i actually use. The rest happen to the worst packages i've ever used for those programmes, or just inferior products when compared to the alternatives

[–] devfuuu@lemmy.world 4 points 1 week ago
[–] racketlauncher831@lemmy.ml 2 points 1 week ago

Here is the link to the PR: https://github.com/void-linux/void-packages/pull/62482

Please stop citing from a third-party news site!

load more comments
view more: next ›