conv.

All stories
TechQuiet 76d · day 77

Developer abandons GitHub over stability, AI training concerns; SourceHut ban on LLM projects complicates migration options

A developer's public exit from GitHub and SourceHut's new LLM restrictions reignite debate over platform lock-in and self-hosting versus centralized collaboration.

What to know

  • A developer published a high-profile account of abandoning GitHub for self-hosted Forgejo, citing years of platform instability and concerns about code being used to train AI models.
  • SourceHut's recent ban on LLM-using projects has prompted developers to reconsider migration options, but alternative platforms face their own restrictions and fragmentation challenges.
  • Most developers remain on GitHub despite dissatisfaction because switching is prohibitively expensive due to integrations and automation dependencies; alternatives lack GitHub's collaboration network effects.
  • The conversation reveals a fundamental tension: centralized platforms risk vendor lock-in and enshittification, while fragmented self-hosted options sacrifice the ecosystem benefits that make open-source collaboration possible.

The dispute Whether restrictions on LLM use by alternative platforms are justified (protecting against AI training) or misguided (fragmenting the ecosystem and driving users back to GitHub). · positions read across 15 posts and comments

most voices

GitHub is problematic but inescapable; network effects and switching costs keep developers hostage.

  • “GitHub is going the wrong way, but there really is nothing workable for open-source projects except GitHub. I don't want to register on all these random GitHub killers just to open an issue or PR.”

    vladkens · Hacker News
many voices

Self-hosting (Forgejo) is worth the tradeoff for control and reliability; fragmentation is a price worth paying.

  • “What finally pushed me over the edge was a hour long Actions outage that prevented me from pushing a hot fix…For work that a business depends on, I can't recommend GitHub Actions…So far I'm loving Forgejo and have no regrets!”

    JLO64 · Hacker News
some voices

Alternative platforms' restrictions (SourceHut's LLM ban, Codeberg's terms) are counterproductive and will drive users back to GitHub.

  • “It ridiculous, Codeberg did the same. I get why, really, I do, but it's creating a severe damage that will be abused by a third evil actor…Outcome? Everyone on their own self-hosted git servers, zero collaboration.”

    oscarcp · Hacker News

“I agreed with the sentiment of the post, and Github deserves every bit of it. Tried codeberg (which uses forgejo) and I am very happy with it personally.”

dabedee, Developer · Hacker News

iozguradem Developer/bloggerGitHub (Microsoft) Centralized Git hosting platformSourceHut Alternative Git hosting platformCodeberg/Forgejo community Self-hosted Git platform and alternative hosts

The record 2 articles and posts · last 30 days

  1. Bye, Bye GitHub press · HN Frontpage · iozguradem · 77d ago
  2. Bye, Bye GitHub L: https:// log.ozgur.works/bye-bye-github .html C: https:// news.ycombinator.com/item?id=4 9483020… post · Mastodon · hkrn@mstdn.social · 77d ago

What people are saying 14 voices from 2 sites · best of 15 · verbatim

Still unanswered
  • Will Forgejo and other self-hosted platforms implement federation to enable collaboration across instances without centralizing on GitHub?
  • How sustainable is the fragmentation across GitHub, SourceHut, Codeberg, and self-hosted solutions for long-term open-source development?