Why I'm leaving GitHub for Forgejo

This wasn’t just one developer quietly packing up and leaving GitHub. In the comments, it turned into a full-blown custody battle over the future of coding. The writer says the real issue isn’t a few bad outages, but the bigger fear that Microsoft now owns the house, the locks, and maybe even the spare key to your code. That argument got extra fuel when the Dutch government launched its own self-run Forgejo site, basically saying: if even a government wants to own its own stuff, maybe that’s the mood now.

But the crowd was far from united. One side was practically waving "I told you so" signs. Some commenters argued that code was never supposed to live in one giant corporate mall anyway, and that people forgot the original dream: keep things spread out, keep mirrors, don’t let one platform become the whole internet. Others were much more practical, chiming in with rave reviews that self-hosting Forgejo is "impressively easy" and worth trying.

Then came the eye-roll brigade. One especially spicy commenter called out the article’s whole premise: if you say it’s not about outages, then why spend so much time talking about outages? Ouch. Meanwhile, another person cut straight to the real-world question everyone was thinking: okay, but does the built-in automation actually work? And in a very internet twist, someone even popped in with a solution for the dreaded lost "social graph" drama, saying tools like GitSocial can carry your followers and teamwork history across sites. In other words: part ideology, part practical migration tips, part comment-section therapy session.