How do you see the firehose ?

I've always had showdead on but don't often actually see a ton of dead comments. Occasionally I see one that's dead and seems odd (and sometimes interesting). Lot of the time it is stuff I'm not surprised is dead.

And rarely I see something that seems very very odd it's dead - although in those cases I usually assume it's just a bunch of bots or people downvoting (vs some kind kf moderator conspiracy)

I wonder if we could learn to provide a check layer by simulating (in real life) a similar philosophical idea to increased context in LLM to something similar using real people. And then based on those simulations create a framework to both automatically check LLM errors as well as providing a better way for actual real people to be involved in the process in the most efficient way.

What kind of earthquakes in California ?

You can if you don't tell them :-D

Or "developer" in this case is the AI ignoring its own iterative self improvement

Or the ones doing the stealing are so competent (or embedded) we don't hear about it

Probably Panasonic. They're like the Apple of the B2B world. Except they also make everything

It used to be that " 5 nines " was the gold standard. I cant believe were now down to 0 for a major service........

Isnt downdetector just people reporting its down though? Its useful for sure but not actually hooking into any officialy API or anything. Great for when the status page also goes down but surely a lag time

No lag time for popular services. Always faster than e.g. GitHub’s or Chat GPT’s status pages.

Do they do alerts ? Been also using UpDog (based on DataDog) which actually has been quite good. They have a single status page for many services who integrate their products

I go to status pages to find out if 1) I’m crazy, 2) if our IT fucked up DNS.

Every service I’ve ever paid for or someone paid for on my behalf has gaslit me about their status page because it’s impolitic and bad for sales to update the page before you know what’s going on, just because some users are reporting issues.

So a third party doesn’t have to deal with VPs kneecapping the engineers’ access to the status page. Or some services can’t update the status page when the site is hard down because they are so obsessed with keeping it up that they have no mitigations when they are down.

I was the one at my biggest gig that had to push to get static 404 and 500 pages uploaded to S3 so we could show something for vanity URLs even if customer ID lookup was down. And then a customer noticed they hadn’t updated since they changed their contact info and I found the job was timing out without an alert or deployment failure for five months. Five. Months. The guy who wrote it had quit, and he didn’t follow my advice on copying a batch job I’d poured way too much effort into. The damned thing was timing out after 50 minutes. I followed my own advice and got it to 4.5 minutes. Almost all of that time delta was waiting for fanout calls, which were pounding the shit out of consumer facing services. 90% of the calls he was making didn’t need to be made.