Honestly?

If the problem is scalability, just rate limit git commands on free accounts already. Nobody realistically need to push multiple times per minute, and that alone is bound to trickle down to anything that triggers on commits and pushes.

▲

brazukadev 7 hours ago | parent | next [-]

Sure. The problem is just an easy fix that nobody there thought about yet.

▲

guhcampos 7 hours ago | parent [-]

My point is: they blame it on scale. If that's the story they want us to believe, then they have to explain WHY such a simple fix isn't possible.

There may be non technical reasons for it, even: legal, or PR, but if they want me to believe the "scalability excuse" they need to convince me they're trying.

	▲	materielle 6 hours ago \| parent [-]
		I don’t know, but typically when orgs don’t make logical decisions, it’s because internal politics are incentivizing something else. I suspect that rate-limits would fly in the face of a lot of narratives like “Azure is ready for hyperscale”. And getting eyes on Github is probably a part of their Copilot product strategy.

▲

pydry 6 hours ago | parent | prev [-]

realistically the problem is vibe coding.

▲

roncesvalles 5 hours ago | parent [-]

The problem is when you stuff your codebase with so much unreviewed vibecoded slop that engineers lose their grasp on how it all works.

▲

NewJazz 4 hours ago | parent [-]

Keep pulling the lever, uptime has to improve eventually!

	▲	cluckindan 2 hours ago \| parent [-]
		Just create an MCP server for the uptime history and tell Claude to optimize the business.