Reddit's r/opensource bans AI projects, solo devs and non English speakers

One of the largest open source communities on Reddit has decided that AI does not belong there. On Saturday evening, October 24, the lead moderator of r/opensource posted new submission rules under the title "Your tokens aren't valuable: No more AI." The core sentence was blunt: if your project uses AI, is made by AI, or is intended for AI, it is not welcome. "AI, as it exists today, is incongruent to this Open Source community," wrote moderator Wolvereness.

Within a day the post had turned into one of the loudest open source arguments of the year. The Verge called it a revolt, Gizmodo and Kotaku picked it up, and on Monday The Register summed it up as a ban on "AI slop, and quite a few humans for good measure". A rival community, r/TrueOpenSource, was created the same weekend. A second moderator publicly disagreed and then stepped down. By Monday the lead moderator had edited the post to say "Adjustments will be made."

It is easy to dismiss this as forum drama. I think it is more useful than that, because it shows in a very compressed way the tension that every open source project is now dealing with: AI made it cheap to produce code, but it did not make it cheap to review, maintain or trust that code.

What the new rules say

The AI ban got the headlines, but the post actually contains a whole package of restrictions. Some of them have nothing to do with AI at all.

For a project to be advertised on the subreddit, it now has to meet all of these conditions:

• It must be at least one year old, and not just old but actively maintained.
• It must have multiple contributors, which the moderator describes as "subjectively 3+".
• It must not be a common capstone project, such as the note taking apps, PDF viewers and command line music players that students tend to build.
• It must not be intended for AI. MCP servers are named as an example.
• It must already have an existing community. Requests for new maintainers or contributors are no longer allowed.
• It still needs an OSI approved license, as before.

On top of that, posters need an account that is at least one year old with "significant Reddit contributions". Anyone who posts, gets removed and then asks the moderators for an exception risks a permanent ban. The moderator wrote that he estimates around 20 such messages a day from people who expect their "slop projects and burner accounts" to get special treatment.

Then comes the line that drew the most anger: "If you don't speak English, you need to find a different community." The reasoning given is that the moderators cannot tell AI written text from AI translated text, and that someone who does not speak English cannot verify whether a translation is correct.

There is one exemption. Registered nonprofit organizations, such as 501(c) groups in the United States or their equivalents elsewhere, can skip the project and account minimums if they ask the moderators for approval before their first post.

Why a moderator would go this far

Before judging the rules, it helps to understand the problem they try to solve. AI coding tools have made it possible to produce a working looking app in an afternoon. A lot of those apps end up being posted to communities like r/opensource as "I built this", often by brand new accounts and often with an AI written description. For the people who moderate these forums, that means a flood of near identical submissions that push real news, discussion and long running projects out of view.

BookStack creator Dan Brown, who was the second most active moderator of the subreddit, described exactly that in a blog post about the rule change. He wrote that the influx of vibe coded projects has been a real problem "due to their sheer quantity flooding the sub". He also pointed out that Wolvereness was the one doing almost all of the moderation work, and that without him the subreddit "would be full of spam, low effort posts, and outright crap marketing". His reading of the situation: one person who had simply had enough, and responded with blunt rules.

That matches what many maintainers outside Reddit report. The cost of AI generated contributions does not land on the person who generates them. It lands on whoever has to review them.

Why the rules backfired

The problem is that the rules hit far more than low effort AI projects.

The age and contributor rules exclude many projects that never touched an AI tool. One user told The Register that their nine year old project, with more than 300 GitHub stars and dozens of resolved issues, would no longer qualify because they are its only contributor. Most open source projects start with one person. A community that bans calls for contributors also removes one of the main ways a solo project could ever reach three contributors.

The language rule is the clearest example of collateral damage. Open source has always been global, and a large share of maintainers do not speak English as their first language. Dan Brown called the wording "frankly terrible, to the point of being offensive" and said he would have preferred asking people to post their original text or use simple translation tools.

And the AI rule itself is close to impossible to apply consistently. Critics quickly pointed out that the Linux kernel now contains AI assisted code, which would technically put the most famous open source project of all outside the rules. When asked about that, Wolvereness said Linux would probably still be allowed, and admitted that "there's no 'objective' way to implement this policy". In practice, the rule means AI is forbidden unless the moderators decide it is fine.

Developers use AI more and trust it less

The fight on r/opensource did not come out of nowhere. It reflects a split that already shows up in survey data.

In the 2025 Stack Overflow Developer Survey, 84% of respondents said they use or plan to use AI tools in their development work, up from 76% a year earlier. 51% of professional developers used them every day. At the same time, 46% said they actively distrust the accuracy of AI output, up from 31%, while only 33% trusted it and just 3% trusted it highly.

That is the gap in a nutshell. Most developers use these tools, and many of them do not trust what comes out. A subreddit full of experienced open source people is exactly the place where that distrust is strongest, and where the volume of AI generated submissions is felt most directly.

Linux went the other way

What makes the timing interesting is that the most important open source project made the opposite decision only a few weeks earlier.

The Linux kernel had asked contributors to add an "Assisted-by" tag to patches written with help from a language model. In a patch posted on October 9, kernel developer Sasha Levin proposed removing that requirement after it came up at the 2026 Maintainers Summit. His argument was based on numbers: roughly 10% of the 18,533 non merge commits in Linux 7.3 up to the seventh release candidate carried the tag, while actual AI use was far more widespread. Some contributors did not know about the rule, others left the tag off on purpose, and few maintainers asked about it. A tag that most AI assisted patches do not carry tells you nothing.

The change was merged as a documentation update for Linux 7.4 by October 21. Two rules stay in place, according to the kernel documentation on AI coding assistants: AI tools must never add a Signed-off-by line, because only a human can certify the Developer Certificate of Origin, and the human submitter must review the code, check the license and take full responsibility for it.

Linus Torvalds was characteristically direct about tool rules. Replying to a developer who wanted to keep some form of required disclosure, he joked that by the same logic you should also ban compilers and editors, and wrote that he expects people "to understand what they are doing", which "has very little to do with what tools they use", as quoted by The Register.

Three ways open source handles AI right now

If you put r/opensource and the kernel side by side, you can see the three main positions that open source communities are taking.

The first is a ban. Gentoo and NetBSD were early here and do not accept AI generated code. According to The Register, System76 recently banned AI generated code and other content from its COSMIC desktop project, and parts of GNOME have introduced similar restrictions. r/opensource now joins that camp, at least for what it allows people to promote.

The second is disclosure with limits. Dan Brown points to r/selfhosted as a better model: posts need an AI disclaimer, and new projects must be at least three months old unless they go into a shared megathread. That slows the flood without declaring every AI assisted project unwelcome.

The third is the kernel model. Use whatever tools you like, but a human signs off, a human is responsible, and maintainers can reject anything the submitter cannot explain.

None of these is free. Bans are hard to enforce and push away honest contributors who use AI carefully. Disclosure only works if people disclose, and the kernel data shows they mostly do not. The responsibility model depends on maintainers having enough time to judge each patch, which is the very resource AI generated volume is eating up.

What happened next

By Monday, October 26, the situation was already moving. Wolvereness added a note to the original post saying "Adjustments will be made", followed by a separate post. In it he wrote that Linux "is not, nor could conceivably ever be banned", that a pet project "pumped out in two claude code session limits" will still not be welcome, and that the line lies somewhere between those two and will likely move over time. He also promised that no rule will ever target or favor any ethnicity.

Dan Brown removed himself as a moderator, writing that the topic had turned into an AI versus anti AI culture war with heavy brigading, and that a subreddit is not worth that much stress. Meanwhile, r/TrueOpenSource and r/OpenSourceAIAllowed have become the places for people who feel pushed out, and the original post itself gave both of them a shout out.

My take

I understand the moderator. Anyone who has looked at the new posts on a popular developer forum in 2026 knows how many of them are thin, AI generated projects that nobody will maintain next month. Volunteers cannot review all of that, and someone has to draw a line.

But "no AI" is the wrong line. It describes a tool, not the thing people actually care about, which is whether a project is maintained, understood and worth someone else's time. A long running project whose maintainer uses an assistant for tests or documentation is not the problem. A weekend clone with a generated README and no plan to maintain it is a problem whether or not AI wrote it.

The kernel's answer is the more honest one: judge the work, hold a human responsible, and stop pretending you can reliably detect how code was written. For communities, the practical version of that looks like the r/selfhosted approach plus quality filters that apply to everyone, such as minimum project age, a clear description written by the author, and a way for maintainers to say what they used.

For anyone who publishes open source projects, the lesson is simple. Be open about your tools, make it clear that you understand and maintain your code, and do not rely on a single forum to find users. As Dan Brown put it, one strength of open source is that anyone can fork. That now applies to communities as much as to code.

Sources

• r/opensource, moderator announcement "Your tokens aren't valuable: No more AI." and follow up "Adjustments will be made.", October 24 and 26, 2026
• The Verge, r/opensource just banned AI, non-English speakers, and more, October 25, 2026
• Gizmodo, 'Tokens Are Cheap': Open Source Subreddit Bans AI, October 25, 2026
• The Register, Reddit's r/opensource bans AI slop, and quite a few humans for good measure, October 26, 2026
• Dan Brown, The /r/opensource Rule Changes, October 25, 2026
• Sasha Levin, docs: remove Assisted-by references, Linux kernel mailing list
• The Linux Kernel documentation, AI Coding Assistants
• The Register, Linux kernel devs drop obligatory confession of AI tool usage, October 14, 2026
• Stack Overflow, 2025 Developer Survey, AI section