r/opensource banned AI projects. It can't tell which ones
The moderators of r/opensource posted new submission rules on Saturday evening, and the first line of the post does most of the work: "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," the rules post reads, as quoted by The Verge.
The reaction was immediate and hostile enough to spawn a rival subreddit, r/trueopensource, within a day. Moderator Wolvereness then stepped into the comments to explain that the rule has room for selective enforcement — software that "incidentally has accessibility features that use AI," automatic captioning being the example. You can read that two ways. It is either a rule with sensible carve-outs, or it is an admission that the ban is applied by judgment, case by case, by whoever is on duty.
The rest of the rules are the story
The AI ban is what travelled, but the same post adds three restrictions that are, in engineering terms, more interesting. Submitted projects must be at least a year old, actively maintained, and have more than one contributor. The mods also wrote that "we can no longer field requests asking for maintainers or people to contribute."
Read those together and you get an accurate description of the problem: a showcase subreddit drowning in brand-new projects whose only user is their author. A minimum age plus a contributor count is a proxy for "someone other than the author has kept this alive," which is exactly the signal a volunteer moderator cannot get from reading a README. That part of the policy is measurable. It is also the part nobody is arguing about, because it is not about AI at all.
Then there is the language rule. "If you don't speak English, you need to find a different community," the post says. "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."
The sentence that gives the game away
That is the most honest sentence in the entire policy, and it is a confession. The mods are telling you that their enforcement instrument does not work, so they have narrowed the population until the instrument appears to work — and the population they cut is the one where these tools fail hardest.
This is not a hypothetical weakness. The best-documented failure mode in AI-text detection is exactly second-language writing: a Stanford team ran seven widely used detectors over 91 TOEFL essays by non-native English speakers and 88 essays by US eighth-graders, and the tools flagged more than half of the non-native essays as machine-written — a 61.22% average false-positive rate — the authors reported in Patterns. Predictable prose is what the detectors punish, and a writer working in their second language produces predictable prose. We went through the mechanics of this yesterday in AI 101 — What is an AI detector?: a detector scores perplexity and calls it a verdict, and the same text flips from "100 percent AI" to "mostly human" when someone moves the threshold.
So r/opensource has not solved the detection problem. It has moved it onto people. Every non-native speaker is now excluded not because their text was measured as machine-written, but because measuring it would be unreliable — and the cost of that unreliability lands entirely on them rather than on the moderators.
What the formal processes decided
It is worth remembering that the biggest open-source bodies have now run this exact argument to a conclusion, with procedures instead of vibes.
Debian spent July and August on a General Resolution with eight competing proposals, and voted between August 15 and August 28. The winner was "Responsible Use of Generative AI," and the resulting policy is deliberately unremarkable: Debian's developers may use AI tools for development, maintenance and documentation, and "generative AI is neither exempt from nor subject to special rules beyond the standards already expected of Debian," per the resolution. The blanket ban was on the ballot, argued for at length, and lost. We made the case for that outcome in August — The Take — Debian's LLM ban would punish honesty, not bad code — and the vote landed where the argument did: the thing Debian can actually check is the code and the human who signs for it, not the provenance of the keystrokes.
The Linux kernel arrived at the same place by a different route: its policy permits AI-assisted patches and puts the liability on the human submitter. System76 went furthest in the prohibition direction and still ended up building an enforcement mechanism — a checkbox in the pull-request template and a bot that closes PRs without it — because a rule with no mechanism is a wish. That version is at least auditable: the declaration is on the record, and lying on it is a bannable act with a paper trail. r/opensource shipped a rule with no mechanism at all and a moderator promising selective enforcement.
Who this actually costs
Three groups pay for the new policy, and only one of them is the one the mods are angry at.
Solo developers launching something new lose their cheapest venue for finding the first users and the first contributors. The subreddit's whole function for that cohort — "here is a thing I made, does it work" — is now out of scope by rule.
Non-English-speaking developers lose access to an English-language community on the grounds of their passport, which is the part of this policy that will not survive contact with anyone outside the subreddit.
And the subreddit itself loses the category. "Intended for AI" excludes the agent frameworks, inference servers, eval harnesses and MCP tooling that a large share of new open-source work now consists of. A general open-source forum that excludes the fastest-growing part of open source is making a statement about its own future, not about AI's.
The enforcement asymmetry is the practical worry. Rules applied by judgment select for confidence, not compliance: a project with a polished README and a familiarity with the community's norms gets the benefit of the doubt, and an unfamiliar project from an unfamiliar account gets removed. That is how a rule meant to keep out slop ends up keeping out strangers.
What to watch
Whether the ban survives a month in any recognisable form. Selective enforcement is a one-way ratchet toward "whatever the mods dislike this week," and the first high-profile false positive — a long-maintained project removed because a dependency now ships AI-generated code, which commenters have already raised about the Linux kernel — will force either a rewrite or a fight.
Whether r/trueopensource becomes a venue rather than a protest. Splinter subs usually die in a fortnight; the ones that last do it by being better at the thing the original was for.
And whether other subreddits copy the halves separately. The age-and-contributors filter is good moderation dressed as an AI rule, and it will spread. The language rule is the opposite, and it should not.
If a community can't verify which code was machine-written, should it exclude the people it suspects — or drop the pretence of verification? Write to us via our contact page.
