Developer abandons GitHub for self-hosted Forgejo citing instability and trust issues

This event reflects a broader tension between convenience and control in developer tooling. GitHub’s centralized model offers ease of use and collaboration, but recent instability and corporate policies, particularly around AI training on public code, have eroded trust. The author’s decision to self-host underscores a desire for autonomy, though it comes with significant trade-offs. Self-hosted solutions like Forgejo require infrastructure management, backups, and security updates, which may not be feasible for all developers or teams. The move also isolates code from the broader open-source ecosystem, limiting visibility and contributions unless additional measures are taken to expose the homelab to the public internet.

The critique of GitHub’s reliability is notable given the platform’s scale and resources. While the author frames this as a personal failing of the industry, it raises questions about whether centralized services can ever meet the expectations of users who demand both stability and ethical data practices. The comparison to pre-internet software distribution, where products were shipped as-is, ignores the complexity of modern cloud services, but it does highlight a nostalgia for simpler, more predictable systems. For engineers, this serves as a reminder that no platform is immune to outages or policy shifts, and that contingency plans (e.g., backups, alternative hosting) are increasingly necessary.

The author’s distrust extends beyond GitHub to the legal and political frameworks governing data usage. The skepticism toward court rulings on fair use reflects a growing unease about how tech giants leverage user-generated content for profit, often with minimal transparency. This sentiment is likely shared by others in the developer community, particularly those who contribute to open-source projects. However, the practicality of self-hosting as a solution is limited. Most developers lack the time, expertise, or resources to maintain their own infrastructure, and even those who do may struggle with scalability or security. The post ultimately serves as a call to action for greater awareness of platform risks, but it also illustrates the challenges of opting out entirely.