6 ms·
Then we'd need a .status.status to tell if the SaaS is down :)
by nexuist 5y ago
Then we'd need a .status.status to tell if the SaaS is down :)
- IgorPartola 5y agoClearly we need to put this on a blockchain.
- Karunamon 5y agoYou meme, but having status updates on a widely distributed network already being used for other things would make it incredibly resilient. You can already sign messages without involving currency malarkey in most blockchains that matter.
- cguess 5y agoSure, but actually committing the status every few minutes (seconds?) to a blockchain would use so much resources it's be... quite impolite. It'd be easier, and cheaper eventually, to have it on a properly sharded database, maybe with a few different DNS and server front ends.
- tnzm 5y ago>committing the status every few minutes (seconds?) to a blockchain Only if the status actually changes every few minutes.
- supermatt 5y agoI’d expect this would need to be like a heartbeat / dead mans switch, I.e keep flagging as up, and when you stop flagging, it’s considered down. Otherwise you would need a different status monitor to monitor the status agent…
- Karunamon 5y agoWhich is fine. Having a standardized .status domain for the pages, even if manually updated, is a big upgrade from the hodgepodge of what's out there now.
- KingMachiavelli 5y agoYou could use something like IPFS to publish a static page every X minutes. No blockchain required.
- Karunamon 5y agoIPFS for pages like this is like a random webpage with extra steps - content on IPFS disappears if nobody has pinned it, so I don't think its benefits would be realized.
- AceJohnny2 5y agoStatus updates do not need distributed consensus or proof of work. not the "Right tool for the job"
- bob33212 5y agoMint coins so that they can be used to check the status. Then trade the coins.
- toast0 5y agoWell, it should be on a different domain, so status.com or statusstatus.com
- myth_buster 5y agoClearly it ends at HN.