Comment by nexuist 5 years ago Then we'd need a .status.status to tell if the SaaS is down :) 14 comments nexuist Reply IgorPartola 5 years ago Clearly we need to put this on a blockchain. bob33212 5 years ago Mint coins so that they can be used to check the status. Then trade the coins. Karunamon 5 years ago 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. AceJohnny2 5 years ago Status updates do not need distributed consensus or proof of work.not the "Right tool for the job" cguess 5 years ago 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. 3 replies → KingMachiavelli 5 years ago You could use something like IPFS to publish a static page every X minutes. No blockchain required. 1 reply → toast0 5 years ago Well, it should be on a different domain, so status.com or statusstatus.com jaredsohn 5 years ago or status.statusstatus ezekg 5 years ago Statuses all the way down myth_buster 5 years ago Clearly it ends at HN.
IgorPartola 5 years ago Clearly we need to put this on a blockchain. bob33212 5 years ago Mint coins so that they can be used to check the status. Then trade the coins. Karunamon 5 years ago 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. AceJohnny2 5 years ago Status updates do not need distributed consensus or proof of work.not the "Right tool for the job" cguess 5 years ago 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. 3 replies → KingMachiavelli 5 years ago You could use something like IPFS to publish a static page every X minutes. No blockchain required. 1 reply →
Karunamon 5 years ago 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. AceJohnny2 5 years ago Status updates do not need distributed consensus or proof of work.not the "Right tool for the job" cguess 5 years ago 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. 3 replies → KingMachiavelli 5 years ago You could use something like IPFS to publish a static page every X minutes. No blockchain required. 1 reply →
AceJohnny2 5 years ago Status updates do not need distributed consensus or proof of work.not the "Right tool for the job"
cguess 5 years ago 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. 3 replies →
KingMachiavelli 5 years ago You could use something like IPFS to publish a static page every X minutes. No blockchain required. 1 reply →
toast0 5 years ago Well, it should be on a different domain, so status.com or statusstatus.com jaredsohn 5 years ago or status.statusstatus ezekg 5 years ago Statuses all the way down
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.
3 replies →
You could use something like IPFS to publish a static page every X minutes. No blockchain required.
1 reply →
Well, it should be on a different domain, so status.com or statusstatus.com
or status.statusstatus
Statuses all the way down
Clearly it ends at HN.