I regret migrating to Codeberg

Original Article ↗ Hacker News Discussion ↗

Codeberg, a German non-profit Git forge positioned as a FOSS- and community-focused alternative to GitHub, has updated its terms to ban projects that are mostly LLM-generated and all cryptocurrency-related code. Supporters say the policy is a legitimate way to conserve limited resources, resist AI “slop,” and stay aligned with free-software values, while critics see it as vague, hard to enforce, ideologically driven gatekeeping that undermines neutrality and chills solo and hobbyist projects. The change is prompting some users to leave for self-hosted Forgejo/Gitea or other hosts, and has reignited broader questions about governance, censorship vs. freedom of association, and whether code forges should curate content or remain maximally open.

Codeberg’s new rules and existing constraints

  • Commenters recap that Codeberg:
    • Requires public repos to be under FLOSS / free‑culture licenses; NC/ND Creative Commons are disallowed.
    • Allows private repos only when directly supporting public FLOSS work or for “small personal stuff,” not general personal hosting.
    • Newly forbids projects that “mostly consist” of generative‑AI‑written code and bans cryptocurrency/blockchain projects.
  • Some note this is consistent with a long‑standing “FOSS‑only, community‑benefit” mission; others say it was marketed de facto as a general GitHub alternative, creating mismatched expectations.

Motivations: resource limits vs ideology

  • Supporters emphasize:
    • Non‑profit, donation‑funded infra can’t subsidize massive CI/storage use from one‑shot, low‑quality “vibe‑coded” projects.
    • AI/bot scraping and LLM‑driven repos strain infrastructure.
    • Ethical concerns: training on FOSS without consent, environmental cost, and “slop” drowning human work.
  • Critics counter:
    • If the issue is resources, quotas, rate limits, or paid tiers would be more direct and neutral.
    • Wording about “reputation” and “no community” suggests values policing more than capacity management.

Impact on solo devs and project “legitimacy”

  • Many solo FOSS authors feel targeted:
    • They read the blog’s “development team of none” rhetoric as dismissive of one‑person projects, despite most FOSS starting that way.
    • Some freeze or migrate their small, human‑written projects out of fear of arbitrary deletion.
  • Others argue Codeberg only wants to avoid high‑resource “ghost projects,” not normal small repos.

Enforcement ambiguity and fairness

  • Multiple comments call the “mostly AI‑generated” standard unenforceable:
    • No reliable way to detect or quantify AI‑written code; invites vibe‑based, arbitrary takedowns.
    • Edge cases (heavy AI assistance with human review, AI‑generated tests, occasional use) are unclear.
  • Concern that retroactive rule changes and vague thresholds make Codeberg an unreliable long‑term host.

Governance, politics, and “freedom”

  • Governance:
    • Rules were passed via a member vote in the German non‑profit association; non‑member users had no formal say.
    • Some members felt the process was perfunctory, with limited debate and later discussion shunted to chat rooms.
  • Politics:
    • Supporters say free‑software hosting is inherently political and a host can choose to exclude AI and crypto to protect commons.
    • Critics see this as non‑neutral “censorship‑adjacent” behavior at odds with a broad “freedom” brand, especially when projects are removed after people invested in migrating.

LLMs as tools: quality, ethics, and future

  • Pro‑LLM voices:
    • Use AI assistants to be more productive, especially solo; see many AI‑assisted projects as well‑engineered, not slop.
    • Argue that “human‑written” is not a reliable proxy for code quality; average human code can be worse than carefully supervised AI code.
  • Anti‑LLM or cautious voices:
    • Emphasize environmental damage, dependence on big vendors, copyright murkiness, and long‑term skill atrophy.
    • Want curated human‑only spaces as a “seal of quality” and cultural choice, even if imperfectly enforced.

Alternatives and responses

  • Reactions range from:
    • “Good, this makes me more likely to use/donate to Codeberg”
    • To “I’m moving back to GitHub / to self‑hosted Forgejo, Gitea, or other forges; I no longer trust Codeberg.”
  • Alternatives mentioned: GitHub, GitLab, SourceHut, Forgejo/Gitea self‑hosting, Radicle, Tangled/ATProto‑based forges, and pure git+CGI setups.
  • Some argue the deeper lesson is to treat any third‑party forge as a mirror and keep primary control via self‑hosting.

Miscellaneous thread themes

  • Debate over whether this is “censorship” in the legal vs colloquial sense; German law and non‑profit/tax status come up.
  • Comparisons to Mastodon vs Bluesky: centralization of power, data/control separation, and portability.
  • Side discussion about the article’s anti‑JavaScript prank UI and nostalgia for JS‑minimal sites.