r/opensource Banned AI Projects It Cannot Detect. Read the Proxies Instead of the Ban

The new rule on r/opensource is written about as plainly as a rule can be: if your project uses AI, was made with AI, or is meant for AI, it is not welcome there. A moderator's announcement, titled "Your tokens aren't valuable," argues that AI as it exists today does not fit that community.

That is a blunt line, and the interesting part is not the line. It is what the moderators had to build to enforce it.

Nobody can look at a repository and see whether a model wrote parts of it. They can look at the commit history, the contributors, the README's fluency, the age of the project, and the account that posted it. So the announcement converts an unverifiable question into a list of stand-ins: a project must be at least a year old and actively maintained, several people must have contributed, and the poster needs substantial history on Reddit. The gates are mechanical on purpose: the moderators say they already field roughly twenty exemption requests a day. The German report from heise quotes the moderators' reasoning that tokens are cheap and that they do not care how much anyone spent on their project.

Read that list again and notice what it measures. Not provenance. Team size, project age, and how long someone has been posting in a specific forum.

The proxies select for the wrong thing

The most obvious casualty is the solo maintainer who has never touched AI. Someone who has quietly shipped one project alone for six years, with no contributors because there was nobody else, now fails the "several people contributed" test. The rule cannot distinguish that person from a generated repository, so it treats them the same and calls it policy.

The second casualty is anyone who does not write English natively. The new terms are effectively English-only, and the stated reason is that the moderators cannot tell machine-written text from a translation. That is an honest admission and a bad instrument. Reddit is a global platform; translated posts were never a crisis before the tools that make them easy existed. The rule now charges non-native speakers for the moderators' inability to measure what they actually care about.

More than two thousand comments had piled up on the announcement when heise covered it, and this is what they are mostly about: not whether AI belongs in open source, but whether the enforcement mechanism punishes people who did nothing wrong. That is what a proxy rule always produces, because a proxy is chosen for being observable, not for being fair.

The same week, the opposite conclusion

A few weeks earlier the Linux kernel decided that patches no longer need to declare whether AI was involved, reversing a disclosure rule that had existed for less than a year. Linus Torvalds has been openly dismissive of rules about AI tools, calling rules that ban specific tools stupid, and he uses LLMs himself.

Heise reads the outcome the same way: under the new terms, posts about Linux would probably no longer be allowed, which is the kind of result that makes a rule look less like a principle and more like a hydraulic press. There are alternatives, r/linux among them, so nobody is silenced. But the comparison is worth sitting with: the same uncertainty about AI authorship produced opposite policies in two adjacent communities in the same month.

The difference is verification capacity. A kernel patch arrives with a review process, tests, maintainers, and a paper trail; whether a tool helped write it matters less because the code has to survive people reading it. A subreddit has none of that machinery. It has a submit button and a mod queue, so when it wants to exclude something it cannot see, it has to exclude a shadow of it instead.

What this means if you publish creative work

The same pattern shows up wherever creative work is posted publicly, and it is worth recognizing before it lands on you.

Any community that cannot verify provenance will gate on something it can see. Sometimes that is tool disclosure. More often it is account age, follower counts, portfolio depth, a client list, the presence of process files, or how well someone writes in the community's language. None of those are the thing being policed. All of them are correlated enough to feel like a signal to whoever is doing the moderating.

Which means arguing about detection is a losing game. Watermarks and content credentials are real and worth keeping where they survive (we covered how visible watermarks work in Gemini's image output and why detection tooling reads them), but a pipeline is where they come apart. A crop, a re-encode, a screenshot, a paste into a slide deck: any of those can decouple the manifest from the file, and tools that do not understand credentials may strip or rewrite the metadata outright. The loss is not automatic. A soft binding can still match an asset after a different resolution or encoding, and a credential-aware tool may record the edit in a new manifest instead of discarding it. Survival depends on every tool in the chain, which is not a property you control. Any policy that depends on a marker making it through a creative pipeline is a policy that will be applied inconsistently, and inconsistently applied rules always cost the least powerful person in the room the most.

What survives is not a forensic marker. It is the work's own paper trail: layered files, version history with timestamps, the seed and the workflow, the unedited capture, the note that says which part the model made and which part you made. That evidence is boring, it is local, and nobody can strip it without discarding the work itself.

The practical version, for anyone publishing AI-assisted work right now:

• Keep the process artifact next to the deliverable, in the same folder, named the same thing.
• Say what the tool did and what you did. One sentence, in the post itself, not in a reply to a critic.
• Do not lead with "AI-assisted" as a defense. Lead with the work, and have the receipts ready when someone asks.
• Assume any marker in the file may not survive the next tool in the chain, and keep the original plus your own record of how the work was made.

The part where the ban is not wrong

It would be easy and dishonest to write this as a story about a community being unreasonable. The flood is real. Low-effort generated repositories and generated promotional posts do consume moderation capacity, and the announcement's frustration is the frustration of people who have watched their forum's signal degrade for two years. A community is allowed to set terms for its own space, including terms that are crude.

The problem is that a proxy rule does not stop at the thing you wanted to stop. It runs until it hits someone the proxy was never meant to describe, and then it keeps running, because the tool has no way to notice. r/opensource has traded one kind of noise for a different kind of exclusion, and the exclusion falls on the people least able to absorb it: the solo builder, the non-native writer, the newcomer with no posting history.

If your work lives in public, the lesson is not to argue about whether it looks generated. It is to make the honest version of your process visible before anyone has to guess, because the guess will be made with whatever instrument is lying around.