Reddit’s r/opensource AI Ban Targets the Wrong Problem

Open source has an AI problem. But it’s not the one Reddit’s largest open source forum just tried to solve.

The subreddit’s October 24 post, titled “Your tokens aren’t valuable: No more AI,” lays out four main rules: projects must be at least a year old, have multiple contributors, be posted by someone who speaks English, and cannot be made by or intended for AI. Tools built for AI are out too, and MCP servers are named as an example.

The fine print goes further. Projects need an OSI license, an existing community, and “subjectively 3+” contributors. The poster needs a Reddit account at least a year old with significant activity. Anyone who messages the moderators asking for an exception after trying to post gets a permanent ban, a rule tied to an estimate of 20 such messages a day.

And the language rule drew the loudest reaction. Non-English speakers are told to find a different community, because moderators say they can’t tell AI-written text from AI-translated text. Even the moderation team is split. Moderator ssddanbrown said they disagreed with the rule and learned about the changes through mod-review notifications.

The Linux Problem

The timing is awkward. The rules landed a few days after Linux kernel maintainers dropped the requirement to disclose AI use in kernel work. A consensus to deprecate the “Assisted-by” tag reportedly formed at the Linux Maintainers Summit in Prague, and Linus Torvalds’ message to developers was simple: understand your code, whatever tools you use.

So critics asked the obvious question. The Linux kernel now contains some AI-generated code, so projects that use it could get caught by the ban. One widely shared post listed Linux, Firefox, Python, Docker, VS Code, and Git as projects that would no longer qualify under a strict reading.

The moderators admit the policy is subjective. Moderator Wolvereness said there’s no “objective” way to implement it and that moderators need discretion to remove unwanted AI-generated material. He also said there’s room for selective enforcement, such as software with AI-powered accessibility features like automatic captioning.

That’s the core issue. A rule you can’t apply consistently isn’t really a rule. It’s a mood.

“Judging code by how it was written won’t hold, because AI is already built into the editors, translators, and coding tools many developers use,” said Mitch Ashley, vice president and practice lead for CIO & Technology Buyers and Software Lifecycle Engineering at The Futurum Group. “Producing a contribution now costs almost nothing, while reviewing one still costs a maintainer’s time.”

The Frustration Is Real

It’s easy to mock the ban. But the moderators didn’t invent the problem.

Maintainers have spent the past year buried in low-effort AI output. Ghostty adopted a zero-tolerance policy that only allows AI-generated pull requests for accepted issues, and tldraw began auto-closing all external pull requests in January. GitHub itself has looked at turning off pull requests entirely, limiting them to trusted collaborators, and adding AI triage tools and attribution.

The kernel has felt it too. Torvalds said earlier this year that the Linux security mailing list had become almost unmanageable because AI-generated duplicate bug reports flooded it.

So a volunteer moderation team facing a flood of AI-written project announcements has a real workload problem. A blunt filter is a predictable response. But predictable isn’t right.

Tools vs. Accountability

The kernel and r/opensource looked at the same pressure and landed in opposite places.

The kernel’s answer is accountability. Dropping the disclosure tag doesn’t make AI-generated patches trusted by default. Contributors still remain responsible for the code they submit. Torvalds has been clear about Linux’s position. He said Linux “is not one of those anti-AI projects.”

The subreddit’s answer is exclusion. It judges the tool, not the work. And it sweeps in people who never touched an LLM: solo maintainers, new projects, and developers who write in a second language.

That last group matters. Open source has always been global. Plenty of strong engineers run their English through a translator before they post. Treating that as a red flag shuts out exactly the contributors open source should want.

Ashley sees a better path. “The workable fix shifts that cost back to the submitter, with a named person answering for every change and automated checks rejecting broken work before a reviewer sees it,” he said. “Watch whether GitHub builds that triage into the platform.”

What DevOps Teams Should Take From This

Most engineering organizations aren’t moderating a subreddit. But they are writing policies for AI-assisted code right now, both for internal repos and the open-source projects they depend on. A few lessons apply.

Hold people accountable, not tools. The person who submits the code owns it. That standard works whether a human or an agent wrote the first draft. It’s also enforceable, because you can review the work and the person behind it.

Push the cost back to the submitter. Slop is a review-capacity issue. Contribution templates, issue-first workflows, and CI gates that reject broken submissions early all reduce load without banning anyone.

Be careful with rules you can’t measure. If a policy depends on guessing whether text “feels” AI-written, it will be applied unevenly. That erodes trust faster than the problem it was meant to fix.

Watch your upstream. If key dependencies tighten contribution rules, your team’s ability to report bugs or push fixes upstream can change. Know the policies of the projects you rely on.

The Bottom Line

The r/opensource moderators are right that low-quality AI output is wearing people down. They’re wrong that banning AI, new projects, and non-English speakers fixes it.

The Linux kernel offers a better model. Use whatever tools you want. Understand the code. Own what you ship.

That’s a standard that scales. A ban on a technology that’s already inside nearly every major open-source project doesn’t.