Show HN: A Decentralized StatusPage on IPFS

Re:Show HN: A Decentralized StatusPage on IPFS by diggan on Wednesday January 31, 2018 @11:06AM (#16274858)

The slowness of IPNS is something we're actively working on. Currently we have fixed so resolutions are faster after the first lookup, by using the libp2p feature pubsub. It being faster/slower than DNS depends on your case, but if you're close to the next node, it'll probably be faster. If you're offline, DNS won't work at all :) We also have more fixes for IPNS in general that will come soon.

So, depends on your use case in the end.

Disclaimer: I work for Protocol Labs on IPFS

[ Parent | on HN ]

Re:Show HN: A Decentralized StatusPage on IPFS by Cyberdog on Wednesday January 31, 2018 @12:21PM (#16275486)

Now if my service is screwed up enough that I can't host my own status page or easily find another service to host my status page - like all of Amazon's infrastructure or the entire east coast fiber network or something like that is down - I can see where IPNS would be useful for hosting. But since standard DNS is already distributed, why can't I continue using that to do name resolution? Why does IPFS need its own reimplementation of DNS?

(I ask this as someone very unfamiliar with IPFS, so please forgive if this is a stupid question.)

[ Parent | on HN ]

Re:Show HN: A Decentralized StatusPage on IPFS by johnmw on Wednesday January 31, 2018 @03:35PM (#16277309)

First, thanks for your work on IPFS.

I've been trying to get into IPFS recently. One thing I can't wrap my head around is that IPNS only seems to persist for about 12 hours and then stops working.

It seems to defeat the purpose of a truely distributed name system, as my computer that needs to keep republishing the name becomes a critical part of the system?

Am I missing something or are there plans to resolve this in the future?

[ Parent | on HN ]