Developer migrates personal repos to self-hosted Forgejo v15 LTS on a NUC, citing digital sovereignty, US jurisdiction risk, and GitHub’s Copilot training-data default flip.
Key Takeaways
GitHub logged 257 incidents and 48 major outages from May 2025 to April 2026, including a silent commit-revert bug affecting 658 repos and 2,092 pull requests.
In August 2025 GitHub lost its independent CEO; it now reports into Microsoft’s CoreAI division, the same group building Copilot.
From April 24, 2026, Copilot Free/Pro/Pro+ interaction data defaults to opt-in for AI training with no repository-level opt-out for maintainers.
FISA Section 702 and the CLOUD Act follow corporate control, not data geography; EU data residency does not remove US legal exposure.
The Dutch Ministry of the Interior chose Forgejo over GitLab for code.overheid.nl specifically because Forgejo is fully open source with no open-core split, governed by Codeberg e.V.
Hacker News Comment Review
The dominant thread argues self-hosting solves ownership but sacrifices the decentralized spirit of Git itself; commenters pushed mirrors and federation as the real fix rather than swapping one central host for another.
Federation support for Forgejo and fully decentralized alternatives like Radicle and AT Protocol-based Tangled drew significant interest as longer-term solutions, though network effects keep teams locked to Git-compatible forges.
A practical counterpoint: several commenters run Gitea or Forgejo on cheap used NUCs air-gapped to LAN with zero public exposure, treating AI-scraper risk as a reason to avoid a public HTTP frontend entirely.
Notable Comments
@xvilka: Frames completed Forgejo federation as the real unlock and calls out Radicle as a fully decentralized alternative worth watching.
@merb: Argues the unsolved problem is not hosting but review tooling: semantic diffs and sane merge-request workflows still lag on every forge.
