Codeberg is a community-run German nonprofit that hosts free and open source software projects. A member vote approved a terms change that allows it to ban projects seen as harming Codeberg’s reputation, with cryptocurrency projects named as an example. That landed right after a separate Codeberg policy against projects that mostly consist of code written by generative AI tools. For people who only knew Codeberg as a friendlier GitHub alternative, this was a rude reminder that it sees itself less as neutral infrastructure and more as a curated commons with explicit values.
The strongest throughline was not “crypto good” so much as “this makes Codeberg feel unreliable as a long-term host.” Even many people who dislike crypto said the policy is sloppy because it bans a category instead of targeting fraud, scams, resource abuse, or malware directly. The recent AI rule made that concern sharper, because its wording around “mostly” AI-generated code and “tolerated in practice” reads vague enough to invite case-by-case judgment. That pushed the conversation from the substance of crypto into trust, predictability, and whether a forge can be serious infrastructure if users cannot clearly tell what might be unwelcome next.
The defense of Codeberg was straightforward and often blunt. It is not GitHub. It is not trying to be neutral, universal, or growth-maximizing. It is a nonprofit association whose paying members vote on policy, and anyone unhappy with that can use GitHub, GitLab, self-hosted
Forgejo, Gitea, or more decentralized options. Several commenters argued this is exactly the point of free software infrastructure: many smaller hosts with different norms, not one giant default. Others added that every platform is political anyway, including GitHub through takedowns, product choices, and Microsoft’s priorities. From that angle, Codeberg is just being more honest about it.
Where the comments really sharpened the story was on governance and scope. The vote was real, but it came from active association members, not the full user base, which left some regular users surprised that “community-led” effectively means dues-paying members of a German registered association. That structure looked healthy to supporters and like thin legitimacy to critics. A more technical subthread also picked apart the environmental rationale. People noted that the stated case leans heavily on proof-of-work harms and sloppy Bitcoin energy comparisons, while modern proof-of-stake systems like Ethereum have radically lower energy use. That did not persuade supporters much, because many of them were plainly arguing from Codeberg’s desired community boundaries, not from a carefully drawn technical line between blockchain designs.
The practical conclusion was harsh but clear. If you want a host whose mission includes deciding what kinds of software belong, Codeberg is becoming more legible. If you want your code host to behave like boring infrastructure, this episode was a warning to keep your code, issues, and project identity portable because
git alone is easy to move, but the surrounding collaboration metadata is not.
codeberg.org