Post #1787316
2026-04-29 11:33 UTC
Replies (23)
-
@yosh@toot.yosh.is 2026-04-29 11:43
On the same topic - I'm also really annoyed by the “real GitHub Uptime tracker" that's regularly posted. Evan Hahn did a good job breaking down why it's bad: https://evanhahn.com/in-defense-of-githubs-poor-uptime/ The last paragraph in that post is titled: “There are better reasons to dislike GitHub”. And like, yeah - definitely.
-
@woe2you@beige.party 2026-04-29 11:44
@yosh Does anyone have a spare Planck length-sized violin? They used to have nines before they went all in on slop.
-
@djmitche@fosstodon.org 2026-04-29 11:45
@yosh they built the machine creating that traffic and have been BEGGING us to use it for years now. Interesting that they are right now increasing the price of that very machine! https://github.blog/news-insights/company-news/github-copilot-is-moving-to-usage-based-billing/
-
@samir@mastodon.functional.computer 2026-04-29 11:52
@yosh If your service cannot handle the load, you can push back, stop accepting more load. You don’t have to degrade the experience for all customers; that is a choice.
-
@unchartedworlds@scicomm.xyz 2026-04-29 12:02
@yosh Interesting, thanks. I wonder what percentage of the increased load is LLM-generated? I imagine the recent pressures and incentives to use LLMs could account for a significant multiplication of traffic. #GitHub
-
@benjamineskola@hachyderm.io 2026-04-29 12:17
@yosh @baldur I’m not incredibly sympathetic. For one thing they’ve been rewriting the frontend in ways that make it significantly more fragile (React); but also, they’re the same company that’s pushing all the LLM/‘agentic’ nonsense that’s causing most of that excess traffic. The leopard is eating its own face.
-
@viraptor@cyberplace.social 2026-04-29 13:01
@yosh It's a nice cover story, but they were failing for so much longer: https://damrnelson.github.io/github-historical-uptime/ The reason seems pretty clear from that picture and they have an almost perfectly horizontally scalable system with lots of immutable data - two different forks will never join, so they can shard however they want. There's no good reason for actions to mess with that part at all. Somehow buildkite successfully exists entirely outside GitHub and does the same kinds of things.
-
@aiono@mastodon.social 2026-04-29 13:13
@yosh this would be plausible if the outages started happening last year, which is not the case
-
@dln@mastodon.social 2026-04-29 15:13
@yosh So it doesn't scale? And they're incapable of handling ~450RPS at SLO, globally?
-
@thomasfuchs@hachyderm.io 2026-04-29 15:37
@yosh @Migueldeicaza “stability issues” is one thing, days on end of constant outages and breakages from a trillion dollar company specializing in [checks notes] server hosting seems like it well deserves to be criticized
-
@kdekooter@mastodon.social 2026-04-29 16:33
@yosh a whole new meaning to "eating your own dogfood" - eating your own copilot sh*t
-
@scottytrees@mastodon.social 2026-04-29 16:40
@yosh explain like i'm 5 what this means to the average linux user if anything?
-
@thejacenallen@mastodon.social 2026-04-29 18:31
@yosh you believe their claims lmao idiot
-
@jcolag@mastodon.social 2026-04-29 21:40
@yosh Didn't they "prioritize moving to Azure" over features and utility specifically for this eventuality? That was...October, looks like. https://thenewstack.io/github-will-prioritize-migrating-to-azure-over-feature-development/ It's almost impressive that they're already shrugging their shoulders, in its way...
-
@poliorcetics@social.treehouse.systems 2026-04-29 22:42
@yosh what a disappointing take and defense those toots are. If you’re not paid by MicroSlop for these, double shame.
-
@OmegaPolice@hachyderm.io 2026-04-29 23:10
@yosh Nothing is safe from the slopmachines 😞
-
@donaldball@triangletoot.party 2026-04-29 23:53
@yosh @mayintoronto They should have thought about this before they broke everyone’s licenses compile Copilot.
-
@emma@orbital.horse 2026-04-29 23:59
@yosh yeah all that order of magnitude of raw sewage and child porn.
-
@StarkRG@myside-yourside.net 2026-04-30 05:57
@yosh I wonder how much of that increase is directly due to AI garbage.
-
@stark@mastodon.mit.edu 2026-04-30 09:54
@yosh I don't see why going from 1B commits to 14B commits on 14x separate repos would cause any additional complexity. What does seem like it would cause issues is if they went to 14B commits on the same number of repos. If each commit is getting larger and part of a more complex repo.
-
@leeloo@c.im 2026-04-30 10:01
@yosh Considering that everyone seems to be leaving Github these days, those commits must be AI commits. Soon Github will be an AI echo chamber that everyone else avoids.
-
@ghalldev@mastodon.social 2026-04-30 15:24
@yosh I’ve heard, from an ex-GitHub engineer I spoke to recently, that the main issue is their allocation of resources towards AI/Copilot. Based on that, their issues handling a surge in activity would seem to be a symptom and not necessarily the root cause…
-
@zbrown@floss.social 2026-04-30 18:28
@yosh oh no, the company that encouraged all this is being inconvenienced by it, what a shame