4 ms·
This incident page really needs a diff mode or just less boilerplate. It's really difficult to tell at a glance what's changed with each update.
by jvolkman 4y ago
This incident page really needs a diff mode or just less boilerplate. It's really difficult to tell at a glance what's changed with each update.
- jlmorton 4y agoCame here to say this. Each update almost subtracts value. Updates should only contain information that has changed. Very frustrating when you're anxiously awaiting new information, and you have to do a word-by-word mental diff.
- willhackett 4y agoI really like this. I think a change to the input questions could solve this — clearer, more specific questions like "What's changed?", "Is it worse/better?".
- scary-size 4y agoAdd to that all timestamps being US/Pacific for an outage in Europe...
- davidkuennen 4y agoIt's funny how HN always complains about every status page. I think Google Cloud has one of the only status pages that is always up to date and very forthcoming in giving as much detail as possible. Personally I couldn't ask for more.
- the_sleaze9 4y agoIt's casual feedback, sure. But it is (by and large) specific and actionable. I think "you couldn't ask for more" is disingenuous at best, and an actively harmful outlook at worst.
- POPOSYS 4y agoIf you are really that interested in the content of a status page of one cloud service provider you should redesign your infra. The value proposition of "cloud" for is not "I can haz cloud of big corp as my own" but "I can haz many cloudz to make resilient infra!". If you rely on one cloud provider you are doing it wrong.
- mloughran 4y agoTotally agree. I literally piped updates to diff last night to see whether GCP were actually making progress fixing anything or just spamming the same update message. Would make a useful twitter bot…