3 ms·
I find this so infuriating that the standard flow is: 1. Notice issue; 2. Check provider status page which says all fine: 3. Have to go to HN to find the info t
by rollulus 3y ago
I find this so infuriating that the standard flow is:
1. Notice issue;
2. Check provider status page which says all fine:
3. Have to go to HN to find the info that should’ve been on their status page.
- inductive_magic 3y agoLow hanging fruit: HN-based LLM-powered status page for *
- latexr 3y agoYou don’t need an LLM for that. Grab the feed and filter for post titles with “Ask HN”, “is”, and “down”. Or use one of the myriad websites which tracks this stuff, such as https://downforeveryoneorjustme.com/ https://downforeveryoneorjustme.com/
- throwaway02472 3y agoI'm not sure if the "downforeveryoneorjustme" would detect this issue. In my case, only the desktop app failed. I was still able to use the web version
- latexr 3y ago> I'm not sure if the "downforeveryoneorjustme" would detect this issue. It would (and did) because it’s not just a service check, it also allows for users to report issues. Scroll down on the page. https://downforeveryoneorjustme.com/slack https://downforeveryoneorjustme.com/slack
- joshspankit 3y agoThe underlying problem seems to be that “status pages” are now marketing and branding touchpoints instead of sources of information.