Live data from Hacker News

Show HN: A Decentralized StatusPage on IPFS

dstatuspage.net

21–30 of 130 posts

Re: Show HN: A Decentralized StatusPage on IPFS

#21
post #15

Earlier quoted context omitted.

I think you can run IPFS locally and access the IPFS network without a gateway this way.

Sounds like IPFS needs more ubiquity before this is something you can rely on. I know IPFS support is coming to Firefox soon, but I suspect it's much further off for other browsers.

"IPFS support is coming to Firefox soon"

Not exactly, as far as I understand it; you still need to manually install an addon, it's just that the addon can now handle ipfs:// links when you click on them.

https://news.ycombinator.com/item?id=16243530

Re: Show HN: A Decentralized StatusPage on IPFS

#22
post #12
post #9

Earlier quoted context omitted.

IPFS has a so called IPNS system that use mutable hashes. So when you publish using this piece of software you got always a permanent link to share with your users.

What if I wanted to always link to the latest, like from my normal HTTPS powered web site? Is there a way to link to the head so that it always references the latest version?

The latest would be a link like /ipns/yourcompany.com, and you'd have a TXT record pointing at your node's IPNS hash (or an IPFS content hash directly) and you update it by either updating what your node's IPNS hash points to, or by editing the DNS record to point to the latest IPFS content hash.

Re: Show HN: A Decentralized StatusPage on IPFS

#24
post #6
post #2

One of the main problems while I was researching about status page services and saw many having the same doubts here was about where to deploy the status page. Besides this market has a lot of players even the biggest one had problem when the big S3 outage happened last year (see ref-1). What about do not depend on a centralized infrastructure to deploy you status page and kept always alive? This project aims to depl…

I'm brand new to the IPFS concept, this looks really cool! I was surprised to see that the page served via IPFS supports HTTPS, do you happen to know how the secret key is securely shared among nodes in the decentralized environment?

The https version is served thru a proxy. This is the way you can get your status page visible to the HTTP world. The gotcha is that anyone on the IPFS network could have a copy of your page and serve them in your behalf.

Re: Show HN: A Decentralized StatusPage on IPFS

#25
post #12

Earlier quoted context omitted.

What if I wanted to always link to the latest, like from my normal HTTPS powered web site? Is there a way to link to the head so that it always references the latest version?

The latest would be a link like /ipns/yourcompany.com, and you'd have a TXT record pointing at your node's IPNS hash (or an IPFS content hash directly) and you update it by either updating what your node's IPNS hash points to, or by editing the DNS record to point to the latest IPFS content hash.

Now I'm even more confused. I suppose I'll watch a talk on youtube or something.

Edit: currently watching this - https://www.youtube.com/watch?v=BA2rHlbB5i0 (10 minutes)

Re: Show HN: A Decentralized StatusPage on IPFS

#26

I love that the background image is a schematic of a centralized network. Look at that single point of failure! ^^ https://www.dstatuspage.net/decentralized.png

I think that the edges represent links across which information did/does flow, not where it can flow.

Re: Show HN: A Decentralized StatusPage on IPFS

#27

I love that the background image is a schematic of a centralized network. Look at that single point of failure! ^^ https://www.dstatuspage.net/decentralized.png

Well, I think it's showing a decentralized network, not centralized. Maybe closer to federated, who knows, it's not clear. It's for sure not distributed though, while IPFS is a distributed file system.

If the graph contained at least one other link between the nodes than via the center one, it would make it more clear.

I think this famous graph (from Paul Baran https://www.rand.org/about/history/baran.html) does a good job of showing the difference: https://ipfs.io/ipfs/QmdYtMUTnz6vaQNRUAzhh8YiSSGzBCyQrCXE5Ag...

Re: Show HN: A Decentralized StatusPage on IPFS

#29
post #8

One thing I'm missing (or misunderstanding) about IPFS is updates. In a centralized system, like HTTP, a site has a single address: something.example.com. Any new entry (e.g. blog post) I create gets its own entry address, but is also referenced from the main site address. As far as I understand, IPFS contains static copies of documents, so any document that would be the "front" page would have to be copied before up…

One word: IPNS. It's a DNS-like system, though much slower than DNS due to propagation delays. It points to the latest version (hash) of a document, much like a git branch.

Being slow is kinda a deal breaker for a status page, isn’t it? The whole point is to notify your customers of an issue, and you need to do that fast. Most issues are only going to last a few minutes anyway, so any delay in update makes the whole thing pretty moot.

Re: Show HN: A Decentralized StatusPage on IPFS

#30
post #28

Naive question: if data on IPFS is permanent, meaning it's hard or impossible to remove things from it, what mechanisms, if any, exists to prevent unlawful content from being uploaded to it?

> What mechanisms, if any, exists to prevent unlawful content from being uploaded to it?

Probably the same ones used against P2P, lawsuits and pressure on national governments to crack down against the offenders :)

Post reply on HN