Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

Clearly we need to put this on a blockchain.


Mint coins so that they can be used to check the status. Then trade the coins.


You 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.


Status updates do not need distributed consensus or proof of work.

not the "Right tool for the job"


Sure, 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.


>committing the status every few minutes (seconds?) to a blockchain Only if the status actually changes every few minutes.


I’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…


Which 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.


You could use something like IPFS to publish a static page every X minutes. No blockchain required.


IPFS 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.




Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: