NINETY DAYS

NINETY INCIDENTS

NINETY PERCENT

YOU PAID FOR ALL FIVE NINES BUT YOU’LL ONLY NEED THE EDGE

#github

@0xabad1dea There are five nines on the screenshot, I don't see any problem.
@dos @0xabad1dea might have been 6 if the waited two days!
@0xabad1dea is that a sequel to "Nine Hours, Nine Persons, Nine Doors"?
now i'm thinking of the cover of the DS game "999: nine hours, nine persons, nine doors" but it's "909090: ninety days, ninety incidents, ninety percent"
@0xabad1dea i bet i know what's going on here
@0xabad1dea Before you can improve your process, you have to make it consistent.
@0xabad1dea Give it time and they'll get it to nine fives.
@0xabad1dea This is what happens when the “official” Whitehouse grift app loads JavaScript from some random GitHub pages.
Shut the whole site down for a month to fix stuff and you'd still have a better uptime
@0xabad1dea Maybe they meant 9 5s?
@0xabad1dea I'm sure #AiSlop can't be the problem! /s
@0xabad1dea www yeah baybeeen looks at dem nines!
@0xabad1dea You're looking at this all wrong. If you express it as eighty nine point nine repeating, it's infinite nines. Microslop wins this one!
@0xabad1dea fun fact: that's about a month and a week's worth of downtime.
@0xabad1dea does 89% uptime count as one nine ?

@gkrnours @0xabad1dea Ooh ooh, I can answer this!

Given that 100% is hard to reach and 0% is not, we can use a simpler version of the logit function and take log₁₀(1÷(1−.89)) = ~0.96 which means it's still a tad below 1 "nine".

(The full logit function is log₁₀(x÷(1−x)) and is useful when both 0% and 100% are hard/impossible to reach.)

@0xabad1dea

hey, 89.99% reliability is still 3 9s reliable :3
@0xabad1dea
I paid for the whole uptime status bar, so I am going to use the whole uptime status bar!
@0xabad1dea I'm more of a nine fives kind of sysop
@0xabad1dea this rocks, pick any random homelab on fedi and it's probably destroying github lol

@0xabad1dea Once upon a time, at a small entertainment company that rhymes with 'misery', I was responsible for the operations of the Github Product.

It came as a vmdk. No documentation.

I was told "Backup" was as simple as snapshotting the VM.

It ran gunicorn.

There was no tuning, monitoring or built-in telemetry.

They refused to give us an extension on licensing when they forgot to cash our check, and shut it off from remote.

Every call was with techbros.

I cannot stress enough, how happy this makes me.

@0xabad1dea THERE ARE FOUR NINES!!!
@0xabad1dea Grok, is this true? 🤖💩
@0xabad1dea insanity. when i worked for microsoft they would have fired me and then launched whatever was left into the sun if i let this go on for four hours much less ninety goddamn days
@0xabad1dea I nearly choked on my cheese. Good job!
@0xabad1dea Where did this come from? status.github.com paints a very different picture, though also not particularly great honestly…
@slembcke @0xabad1dea This is from the "missing GH status page": https://mrshu.github.io/github-statuses/
The Missing GitHub Status Page

Historical GitHub uptime reconstructed from archived status data.

@0xabad1dea There's a 996 joke in here somewhere, I swear.

Edit: 996: one 9 of uptime, 9-0 incidents, and the third nine in "90 days" is upside down lol. We can workshop it.