Reddit's r/opensource bans AI projects — and non-English posts, sparking a revolt and a rival subreddit
r/opensource banned any project that uses, is made by, or is intended for AI on Oct 24, 2026, and non-English posts too — users spun up a rival subreddit.
r/opensource — one of Reddit’s main venues where independent developers announce their projects — has banned AI outright. A pinned rule post titled “Your tokens aren’t valuable: No more AI.”, published by moderator u/Wolvereness on October 24, 2026, draws the line without much ceremony: “if your project uses AI, is made by AI, or is intended for AI, it’s not welcome on r/opensource. AI, as it exists today, is incongruent to this Open Source community.” Non-English posts are banned alongside them, on the stated grounds that moderators “cannot distinguish between AI-written and AI-translated.” The comment section revolted within hours, and readers have already founded a rival subreddit, r/TrueOpenSource.
Key points
- The ban is a triple test: a project fails if it uses, is made by, or is intended for AI. MCP servers, AI-built tools and AI-assisted code are all caught by the same sentence.
- The entry bar now demands a one-year-old, actively maintained project with three or more contributors and an existing community; posters need year-old accounts, and violations mean permanent bans. Registered nonprofits can ask for an exemption through modmail.
- The moderator concedes “There’s no ‘objective’ way to implement this policy”; the top comment questioning the rule collected roughly eight times more upvotes than the post itself, and r/TrueOpenSource got a public shout-out in a post edit.
Background
For years r/opensource worked as a default launchpad: post your repo, pick up early users, find contributors. The new rules shut that door to solo maintainers, projects under a year old and every non-English speaker at once. Reddit communities have swept AI before: r/programming, the site’s largest programming subreddit, temporarily banned all AI and LLM content in April 2026, as Tom’s Hardware reported on April 3. We have tracked the same squeeze inside open source itself: QGIS banned AI contributions outright and then moved to extend the ban to all repository text, while Google froze its open source bug bounty because “the vast majority” of automated submissions were invalid. Commenters in the thread add a compounding problem: the Linux kernel already contains AI-generated code, so under a literal reading the largest open source project would not qualify here either. And the moderator driving the policy is not a neutral figure — Wolvereness is Wesley Wolfe, who filed the September 2014 DMCA takedown that froze CraftBukkit on GitHub and pushed the Bukkit community toward Spigot.
The rules
The post lists hard entry criteria (see the table) and adds a pointed footnote: “If it’s obvious you’re using AI in your project, we don’t want it. Tokens are cheap, and we don’t care how many you spent to make your amazing project.” Wolvereness estimates about 20 modmail messages a day from “people expecting their slop projects and burner accounts to get an exception,” so the post warns up front: petition for an account-age exemption and “you will be permanently banned and muted.”
| Requirement | New rule |
|---|---|
| Project age | One year old, and actively maintained — not just registered |
| Contributors | Multiple; the moderator’s stated bar is three or more |
| Project type | No capstone/school projects (note apps, PDF viewers, CLI music players), nothing “intended for AI” such as MCPs |
| Community | Must already have a community; requests for maintainers or contributors are no longer accepted |
| License | OSI license, as always |
| Account | One year old, with meaningful Reddit activity |
| Penalty | Permanent ban for posting LLM output; temporary bans for one-off lapses |
| Exemption | 501(c)/(d)/(e)/(f)/(k) or 521(a) organizations, or local equivalents, with modmail pre-approval as “approved users” — the post notes it is deliberately not limited to 501(c)(3) |
The non-English ban lands in three sentences: “If you don’t speak English, you need to find a different community. We cannot distinguish between AI-written and AI-translated. Since you don’t speak English, you can’t even verify yourself if it translated correctly.” Penalties are tiered — a temporary lapse earns a temporary ban, but posting “the result of your LLM output tokens” means “you will never be welcome back.” The Verge spotted one carve-out: in the comments, Wolvereness said software “that incidentally has accessibility features that use AI,” such as automatic captioning, remains welcome. That is goodwill — and also a license for selective enforcement.
What others say
The subreddit’s own comment section pushed back first. “Linus uses AI for kernel development now. This is a ridiculous stance,” wrote TuringTestTwister in a comment chain that drew 86 replies; AlexanderDoak observed that “the top comment calling this out as ridiculous has 8x more upvotes than the post itself.” bikes-n-math said his nine-year-old, 300-star project, maintained alone, was now unwelcome overnight. dwkeith, a retired engineer with 30 years across Apple and Google who has spent 14 months building an open source project with Claude, called the blanket ban a way to make the sub “far less interesting.”
The loudest reaction came on X. Lunduke Journal summarized the policy as banning “anything using AI. In any way,” with violators “permanently banned” — heavier than the primary post, which ties permanent bans to posting violations rather than to using AI. Epic Games CEO Tim Sweeney retweeted the argument that “By their own rule, that means the biggest open source project of all time, Linux, is now banned too.” Developer theo scoffed at “the most unemployed possible take on AI.” Digg’s aggregation counted 439 sentiment-bearing replies from 376 accounts across five conversations, 77.7% of them negative — Digg’s own methodology. A minority dissents: benjamincrozat argued small open source libraries have “almost lost all their value” now that nobody hand-writes them, so the ban costs him nothing. One test cuts against the rule itself: amarao_san had GPT 6 translate a text, and the detector Pangram scored the result “100% human written.” If detection tools cannot tell, the moderator’s eye is doing all the work.
Our take
For indie developers this is a real distribution squeeze. r/opensource was a low-friction place to launch, find a first wave of users and recruit contributors; solo maintainers, young projects and non-English speakers are now all out, and contributor-wanted posts are gone entirely. The deeper problem is predictability: the moderator admits there is no objective standard and enforcement runs on an “eye test” — the same rule that spares an automatic-captioning feature today can delete your project tomorrow. That is not necessarily malice. When verification cost from AI submissions overwhelms a volunteer community — QGIS’s labeling experiment did not hold, Google’s bounty pipeline drowned — the options genuinely narrow, and a blanket ban is the last one left. As for r/TrueOpenSource, the escape hatch is a day old and unproven. Two things to watch: whether r/programming’s April ban quietly expires, and whether r/opensource holds this line or walks it back under the backlash.