Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Red Squares – GitHub outages as contributions

red-squares.cian.lol

Post reply on HN
Print view View original

141–150 of 175 posts

Re: Red Squares – GitHub outages as contributions

#143

Post by u_fucking_dork »

dijit wrote: post #123
u_fucking_dork wrote: post #112

Earlier quoted context omitted.

The avalanche of same comments to every meme tier post about this is the opposite of curious. Very little discussion of any merit happens on these posts. It’s mostly bandwagoning and repeating the same comments they read on the last iteration.

I agree... https://news.ycombinator.com/item?id=48026924 Yet here we are. I just don't feel comfortable with you defending the trillion dollar company as if we owe them something, or as if they're somehow the victim in all of this. I can buy that there's more demand for service, but; A) They are the ones pushing the AI hype (microsoft especially but github too) B) These issues existed before the AI hype anyway and, o…

Pointing out that attackers are targeting the wrong area is not defending anyone my friend.

I’m just saying that scaling is very likely the issue, no reason not to believe their own statements on that. And yes they are to blame for their own success here.

Re: Red Squares – GitHub outages as contributions

#146

Post by vtbassmatt »

linsomniac wrote: post #101
dijit wrote: post #76

Earlier quoted context omitted.

> the GitHub team is shit, their tech stack is shit 1) Criticism of being unable to achieve service is not a fault of the individual; it simply is a fault of the system. You can criticise the system, it's permissible. Especially if they have more resources than many countries and some of the best tech talent in the world on staff. 2) Their tech stack is shit, and they've gone on record for years defending it, quite a…

>not intellectually curious or open This checks out. I once was at a conference where they (Azure) had a giant booth. A fairly well known person in the community brings me over to talk to his manager who is working the booth. "We should hire him, he's really smart." Within a minute of talking to this manager he says "You're a Linux guy? We do Windows." and physically turns away from me, conversation over. You know, f…

Wait, is this Azure or GitHub who had the booth? If it was GitHub, I’m super confused and there must have been some serious missing context. I was at GitHub from 2020-2023 and am not aware of _any_ Windows usage in the service. The only meaningful Windows footprint was for client dev (`gh`, GitHub Desktop, etc.) and even there, Windows was the exception. Service side is all Linux; most engineers worked from a Mac.

If the context was an Azure booth, I’m still mildly surprised (they’ve long been invested in beyond-Windows) but not shocked.

(Edit: I forgot about the Actions stack. Some of that was on Windows. I was pretty far removed from that world and much closer to the classic Ruby monolith side.)

Re: Red Squares – GitHub outages as contributions

#148

Post by john_strinlai »

s_dev wrote: post #82
u_fucking_dork wrote: post #61

Every time one of these vibe coded meme sites gets posted there’re endless comments about how it’s not actually because of load, the GitHub team is shit, their tech stack is shit, Microsoft is shit, Azure is shit, etc. Just compare the GitHub status page for public GitHub vs the enterprise cloud pages. Enterprise has much better numbers and I’ve personally can’t remember the last time there was an outage that prevent…

It's common knowledge that the official status pages don't actually reflect downtime due to SLAs and the status page could be weaponised against them. So comparing them is useless. You rarely see "outages" even if that what happens in reality, in marketing speak it's referred to as 'degraded performance' i.e. the cheque is in the post, your data is in the tubes on it's way, it's just slow! A business oriented lie. Fa…

>Far more useful are the 'independent status pages' maintained by enthusiasts that are unaffiliated with whomever they are measuring.

unless, like this one, they:

- treat "some copilot chat models are failing" and "teams notifications app down" as a major outage, the same as git operations or actions failing... those are very obviously nowhere near the same operational impact and its dishonest to group them as the same

- aggregate downtime so that there is greater than 1 day of possible downtime in a 24 hour period. if 3 services are down for the same 1pm-2pm time period, that is being counted as 3 hours of downtime despite a developer only being impacted for 1 hour.

it would be cool to have an accurate status page. the only two options seem to be company-owned status pages (incentivized to under-state impact) and karma-hunter/meme status pages (incentivized to make as much red as possible for retweeting or whatever).

Re: Red Squares – GitHub outages as contributions

#149

Post by EE84M3i »

semiquaver wrote: post #75
u_fucking_dork wrote: post #61

Every time one of these vibe coded meme sites gets posted there’re endless comments about how it’s not actually because of load, the GitHub team is shit, their tech stack is shit, Microsoft is shit, Azure is shit, etc. Just compare the GitHub status page for public GitHub vs the enterprise cloud pages. Enterprise has much better numbers and I’ve personally can’t remember the last time there was an outage that prevent…

What do you mean by enterprise cloud? The default GitHub enterprise cloud plan is hosted on the same infra as “public github.” Do you have a link to what you mean?

It sounds like they're talking about "GitHub Enterprise Cloud with Data Residency." This is a separate product to the standard "GitHub Enterprise Cloud" (including Enterprise Managed Users) which runs on normal github.com infrastructure.

If you have a Data Residency tenant, you access it through an endpoint like octocorp.ghe.com

GitHub seems to try to use specific language here to avoid this confusion, because they are quite different products, but it seem to me they were named confusingly in the first place...

Post reply on HN