Codeberg's ban on crypto projects merged the same week it banned AI-generated code

The clause, and who wrote it

Codeberg — the nonprofit, community-run alternative to GitHub built on Forgejo — merged a pull request at its 2026 community assembly amending the platform's terms of use to prohibit "content that harms the reputation of Codeberg, such as — but not limited to — cryptocurrency related projects." The change was proposed by a contributor going by Gusted and merged July 22, 2026. The stated justification, drawn from the surrounding discussion, links cryptocurrency projects generically to "fraudulent activities and high-risk investments" — the ban isn't targeting a specific bad actor or incident, it's a category-wide exclusion.

The timing matters: the same week, Codeberg separately banned "vibe coded" projects — repositories built primarily by AI code generation without meaningful human review. Two content-category bans, merged days apart, both drafted without a precise definition of what they're banning.

"Running a coffee hosting service" and imposing morality

The most-upvoted pushback came from a Google Android SRE: "Banning abuse is fine, and disliking Cryptocurrency projects at a moral level is fine, but running a [git] hosting service and putting your moral judgements on projects like this just seems chilling." Their objection isn't that crypto scams don't exist — it's that Codeberg is a neutral hosting utility, and using that position to enforce a values-based exclusion on an entire technology category sets a precedent other hosts, and other categories, could follow next.

A second commenter zeroed in on the definitional gap: "cryptocurrency related" is undefined, and taken literally could sweep in cryptography libraries, consensus-algorithm implementations, or privacy-preserving payment research that has nothing to do with speculation or fraud — work that shares vocabulary with crypto but not its business model. Without a narrower definition, enforcement becomes a judgment call made project by project, by moderators, after the fact.

Some in the thread supported the ban outright on ethical grounds — "crypto is a hive of scams," as one reply put it, framing the policy as a reasonable safeguard between Codeberg's name and bad actors who'd otherwise use it as free infrastructure. But the visible ratio in the thread ran heavily critical, and a third angle complicated the ethics further: one commenter noted crypto is genuinely load-bearing infrastructure for people in sanctioned countries or under authoritarian regimes — including LGBTQ+ individuals — using it for financial autonomy that traditional banking rails deny them. A blanket ban doesn't distinguish between a rug-pull token and a censorship-resistant payment tool; it excludes both under the same clause.

Not the first time, and probably not the last

One reply noted this wasn't Codeberg's first pass at the policy — a similar ban surfaced "early this month" in an earlier, less formal round, and July's PR appears to be the codified version. Several commenters used the moment to talk about exit options — Radicle's decentralized, self-hostable model and Tor-mirrored alternatives came up repeatedly as ways to avoid depending on any single platform's evolving content policy, moral or otherwise. The underlying tension Codeberg's own volunteers are wrestling with in public: a community-run alternative to Big Tech hosting was supposed to mean fewer arbitrary rules, not a different set of them.