The moderators of r/opensource, one of Reddit's best-known forums for open-source software, have banned projects that use AI, solo and new projects, and non-English posts, and the community is in open revolt. The Verge reported on Sunday, October 25, 2026 that the new submission rules, posted Saturday evening, open with: "If your project uses AI, is made by AI, or is intended for AI, it's not welcome on r/opensource." Within hours the comments filled with objections, and a rival community, r/trueopensource, appeared.
This is a news story about a forum, not about a law or a license. It still matters to builders, because it shows how open-source communities are reacting to a flood of AI-assisted projects, and because the rules, as written, are much broader than a ban on low-quality "slop."
TL;DR: what the rules say and what is disputed
| Question | Answer |
|---|---|
| What was announced? | New submission rules from the r/opensource moderators, posted October 24, 2026 |
| Is AI banned? | Per the post quoted by The Verge: any project that uses AI, is made by AI, or is intended for AI is unwelcome |
| Which projects can still be posted? | Per The Verge: at least one year old, actively maintained, with multiple contributors |
| Can I ask for contributors? | No. The mods say they "can no longer field requests asking for maintainers or people to contribute" |
| Non-English posts? | The post says non-English speakers should find a different community, because AI-written and AI-translated text cannot be told apart |
| Is enforcement strict? | Unclear. Moderator Wolvereness said there is nuance and room for selective enforcement, such as accessibility features like captioning |
| What was the reaction? | A "firestorm" in the comments and a rival subreddit, r/trueopensource, per The Verge |
What exactly did the moderators announce?
The Verge's weekend editor Terrence O'Brien summarizes the post. The headline rule is the AI ban, justified with the line that "AI, as it exists today, is incongruent to this Open Source community." The wording matters: it is not limited to AI-generated code, it also covers projects "intended for AI," which would seem to include tools such as local model runners, agent frameworks and MCP servers, all of which are open source.
Alongside it come three other restrictions. Submitted projects must be at least one year old, actively maintained, and have multiple contributors, which rules out a solo developer showing a new project. The mods will stop handling requests for maintainers or contributors. And the English-only rule, which the moderators justify by saying they "cannot distinguish between AI-written and AI-translated" text.
We could not load the original Reddit post in our automated fetch, so the quotes above come from The Verge's reporting. Read the rules on the r/opensource subreddit itself, since moderators can edit or retract them at any time.
Open-source contributors gathered around an open box, illustrating the r/opensource community the new rules govern
Why did the community push back so hard?
The objections fall into four groups, and most of them are practical rather than ideological.
The rules would exclude major projects. The Verge notes that many commenters pointed out that the Linux kernel now contains some AI-generated code, so projects using it could technically be banned. On Hacker News, fishgoesblub argued that requiring several contributors would have kept the XZ project off the sub, and another commenter noted that all of D. J. Bernstein's software would fail the multiple-contributor test.
The English-only rule is seen as exclusionary. Reddit has a large global developer base. A rule that tells non-English speakers to leave is a harder line than the AI ban itself, and the "we cannot tell translation from AI" logic would block ordinary translation tools too.
Some think the diagnosis is right and the cure is wrong. Several Hacker News commenters sympathized with the underlying problem. Jonathanstrange wrote that moderators were probably overwhelmed with LLM-generated project announcements. Augment_me said they agreed on community grounds, having watched human interaction fall in communities flooded with AI-generated pull requests and projects. Dw_arthur predicted that gatekeeping will return in a world where AI can produce unlimited software. These are individual commenters' views, not measured data.
Others see it as a power trip that will not last. Paxy called r/opensource "not a particularly large or important community," and 2Gkashmiri predicted the rules would be reverted because they would ban the Linux kernel. The Hacker News thread, at 62 points and 78 comments when we read it, is split. Satvikpendem pointed out that r/rust, r/programming and others already restrict AI posts or code dumps and are, in that commenter's view, more pleasant to read. Meanwhile pdp argued that frontier models no longer produce slop at all, a claim that is contested in the same thread.
Is this part of a bigger pattern?
Yes, though the earlier cases were narrower. In August 2026, OpenJDK published an interim policy rejecting any contribution with LLM-generated code, which we covered in OpenJDK bans AI-generated code. That policy governs a code repository where maintainers carry legal and review liability. A discussion subreddit has a different problem: attention. When anyone can generate a plausible-looking project and README in an hour, volunteer moderators drown.
That is the same dynamic behind the wider AI slop problem, and it connects to the cost of checking AI output that we described in the AI verification tax. When producing is nearly free and verifying is expensive, communities raise the price of entry. Our explainer on what AI slop is covers how to tell low-effort output from real work.
A maintainer figure with a lantern guiding small shapes, illustrating moderators filtering a flood of project submissions
The tension is real. Open source and AI are deeply entangled: open-weight models, inference runtimes and agent tools are open-source projects, and many maintainers use AI assistants daily. A rule that treats all of that as foreign to open source draws a line most of the working ecosystem does not recognize. For another example of community friction over AI, see the backlash to anti-AI fonts on Hacker News.
Why age and contributor count are poor proxies for quality
The moderators appear to use project age and contributor count as a cheap filter for "real" projects. The filter is easy to apply, which is its appeal for volunteers, but it fails in both directions. Plenty of excellent tools are written and maintained by one person for years, and the commenters above name several. At the same time, a determined spammer can fake a year of history and a second contributor with little effort, especially now that agents can open commits and issues on a schedule.
A filter that checks behavior would work better: does the project have tests, tagged releases, responses to issues, a license file and a changelog? Those signals are harder to fake and say more about maintenance than a calendar date. Whether the moderators move that way is an open question, and it is the most likely compromise if the rules are softened.
There is also a discovery cost. Newcomers and solo builders lose the one place that used to surface their work, while established projects, which already have audiences, lose little. That asymmetry is why even commenters who liked the anti-slop goal criticized the multi-contributor requirement.
What is confirmed and what is not
- Confirmed by The Verge: the existence of the new rules, their main provisions, the moderator's comment on selective enforcement, and the creation of r/trueopensource.
- Reported by commenters, not verified: that the kernel or specific projects would be banned in practice. That depends on enforcement, which the moderators described as nuanced.
- Not known: whether the moderators will revise the rules, how many members left, or whether Reddit administrators will intervene. We will update this post if that changes.
What should open-source developers do?
If you build with AI and want to share a project, the practical steps are small.
- Read the sub's current rules before posting. They may change, and the sub's moderators decide enforcement.
- Post where your audience is. Hacker News Show HN, X, GitHub Discussions and topic-specific communities are all open to AI-assisted work, each with its own norms. A commenter on Hacker News said X has become their best source of interesting open-source projects.
- Disclose how AI was used. Many maintainers' objections are about undisclosed machine-written code and unreviewed pull requests, not about tools themselves.
- Show human ownership. A clear README, tests, a changelog and answers to issues signal a maintained project, which is the very thing the new rules try to measure, crudely, through age and contributor count.
- Do not rely on one platform. A single moderation decision can reshape a community overnight, as this weekend shows.
If you maintain a project yourself, the lesson is to write your own AI policy early. Agent plugins and skills are making it easy to generate pull requests at scale, and a short contributing-guide section on AI use saves arguments later.
Bottom line
The r/opensource rules are an early, blunt answer to a real problem: communities cannot keep up with the volume of AI-generated projects. They are also so broad that they contradict the way much of open source now works. Expect either a quick rewrite or a split, and expect other volunteer-run communities to face the same choice.
Details reflect reporting as of October 25, 2026. Moderators may change the rules; check the subreddit for the current version.