I think I found the issue.
An update on GitHub availability
41–50 of 266 posts
Re: An update on GitHub availability
#42GitHub instability has started way before that. I understand it’s too much to ask of a trillion-dollar corporation to consider the impact of their own actions, but perhaps they should’ve thought of that before forcing LLM development down everyone’s throats.
Re: An update on GitHub availability
#43> The main driver is a rapid change in how software is being built. Since the second half of December 2025, agentic development workflows have accelerated sharply. GitHub instability has started way before that. I understand it’s too much to ask of a trillion-dollar corporation to consider the impact of their own actions, but perhaps they should’ve thought of that before forcing LLM development down everyone’s throat…
Re: An update on GitHub availability
#44I'm biased (founder of tangled.org), but the future really should be federated forges. Host repositories on sovereign infra with global identity + federated "metadata" (issues, pulls, etc.). Global indices for this should be trivial to spin up so availability is never a concern (we're working towards this!).
But, there are? I can host a repo on GitHub, Codeberg and self host it too. Then I need to watch over main to keep it consistent between those. After that's established, I can do updates from wherever. Link'em in the README.
Re: An update on GitHub availability
#45I'm biased (founder of tangled.org), but the future really should be federated forges. Host repositories on sovereign infra with global identity + federated "metadata" (issues, pulls, etc.). Global indices for this should be trivial to spin up so availability is never a concern (we're working towards this!).
What is "sovereign infra" exactly?
Re: An update on GitHub availability
#46> The main driver is a rapid change in how software is being built. Since the second half of December 2025, agentic development workflows have accelerated sharply. GitHub instability has started way before that. I understand it’s too much to ask of a trillion-dollar corporation to consider the impact of their own actions, but perhaps they should’ve thought of that before forcing LLM development down everyone’s throat…
While they contributed, they were still following the market trend anyway. If they weren't letting folks use it directly, other companies would have (and are).
They started the trend with Copilot.
> If they weren't letting folks use it directly
There is a chasm of difference between “letting you use it” and “forcing it down your throat”. Microsoft is doing the latter, not the former. Copilot is annoyingly present by default at every step on GitHub.
Re: An update on GitHub availability
#47Earlier quoted context omitted.
What is "sovereign infra" exactly?
No less than self hosted, imo. If youre on some cloud it doesnt really matter that you pay them absurd amounts of money, you arent sovereign.
Re: An update on GitHub availability
#48Re: An update on GitHub availability
#49I wonder if they’ll end the free lunch we’ve been having since the MS takeover. There’s been a deluge of spam and crapware projects due to the LLM wave which is visible in that graph. Can’t see them sustaining being a public dustbin for low value projects forever.
I feel like this would have negative impacts (lots of interesting historical archives on Github) but maybe if a project hasn't been touched, or cloned, in some time, it just gets deleted with some notice.
Re: An update on GitHub availability
#50Earlier quoted context omitted.
Seems pretty sensible to not rely on a single provider for their large complex system?
This isn't a mom and pop shop. They have locations all over the world: https://datacenters.microsoft.com/ There's no intrinsic reason they should be vulnerable to themselves.
But Github don't have that rationale.