HNHacker News
TopNewBestAskShowJobs

paulogr

152 karma · joined August 22, 2013

9c65f2681dfe4995ab9096e0b3abb109b3662d4361ba0ddef5c84f2e8f97aa1f
submissionscomments
paulogr··on Show HN: Auto generating SEO-friendly URLs with Scrapy pipelines
why are you mirroring website's content?
paulogr··on Show HN: Twitter bot that tweets changelogs of popular front end frameworks
Hi! The page doesn't load :/
paulogr··on Show HN: A Decentralized StatusPage on IPFS
For IPNS, my experience says it could take up to 30 seconds to publish and up to 10s to resolve.
paulogr··on Show HN: A Decentralized StatusPage on IPFS
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.
paulogr··on Show HN: A Decentralized StatusPage on IPFS
The gotcha there is that you can use multiple gateways to access you page. So you are right, you need to have a http <--> ipfs but you can have many of then and anyone hosting an IPFS node can have a copy of your page and serve it.
paulogr··on Show HN: A Decentralized StatusPage on IPFS
This is a bug from development :) I saw this and will be fixed on next release. Thanks for reporting.
paulogr··on Show HN: A Decentralized StatusPage on IPFS
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.
paulogr··on Show HN: A Decentralized StatusPage on IPFS
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.

paulogr··on Show HN: Pingpoint – Business logic alerts to the right person at the right time
I'm curious if you already got some subscribers for you service. Did you?
paulogr··on Pooper – get paid to pick up dog's poop
"Your dog's poop in someone else's hands." kkkkkk