Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Show HN: A Decentralized StatusPage on IPFS

dstatuspage.net

Post reply on HN
Print view View original

1–10 of 130 posts

Re: Show HN: A Decentralized StatusPage on IPFS

#2

Post by paulogr »

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 deploy you status page on a decentralized infrastructure IPFS (see ref-2), after installed it, you will be running a status page service on top of a local IPFS node. So you’ll be able to to publish you status pages on IPFS while being part of the network.

I thought this use case fits perfect on a decentralized environment.

You can deploy this service on a VPS for 1/4 of the price you pay for your current status page service provider.

See an example of a status page deployed using D StatusPage:

https://gw1.dstatuspage.net/ipfs/QmePTzsSVae8BK8antLHfV2xWfE...

http://gw2.dstatuspage.net/ipfs/QmePTzsSVae8BK8antLHfV2xWfEf...

What are you thoughts?

https://www.dstatuspage.net https://github.com/paulogr/dstatuspage

This software is still in alpha state with basic status page service functionalities, feel free to ask for a feature or address any issue you have:

https://github.com/paulogr/dstatuspage/issues

- ref-1: https://blog.statuspage.io/a-birds-eye-view-of-the-amazon-s3...

- ref-2: https://ipfs.io

The software will be distributed for free and open source under MIT license.

Re: Show HN: A Decentralized StatusPage on IPFS

#3

Post by heavenlyblue »

paulogr wrote: 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…

So how do I (perma-)link the user to the latest status page?

Re: Show HN: A Decentralized StatusPage on IPFS

#5

Post by TeMPOraL »

Nelkins wrote: post #4

How timely, considering I am intermittently getting gateway timeouts on HN right now.

Speaking of which, what's up with the Twitter frame on the status page? I keep getting HN errors quite regularly, but the Twitter bot reports that the most recent failure happened two years ago...

Re: Show HN: A Decentralized StatusPage on IPFS

#6

Post by foxhop »

paulogr wrote: 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?

Re: Show HN: A Decentralized StatusPage on IPFS

#7

Post by ComputerGuru »

I mean, your status page itself may be on ipfs but since ipfs isn’t natively supported as a browser protocol, your “decentralization” fails since you’ll likely need to host the http ipfs gateway somewhere. Might as well stick your status page on a couple of vps (literally just two on two different continents) and round robin them.

Re: Show HN: A Decentralized StatusPage on IPFS

#8

Post by rhn_mk1 »

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 updating with new entries, and would receive a new address.

How to let readers know that a new entry is available then? Would there need to be a centralized place referencing all existing entries?

Re: Show HN: A Decentralized StatusPage on IPFS

#9

Post by paulogr »

heavenlyblue wrote: post #3
paulogr wrote: 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…

So how do I (perma-)link the user to the latest status page?

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.
Post reply on HN