This is such a natural use case for IPFS that commercial adoption seems inevitable; as first mover you can offer the concierge edition and optionally gain a ton of credibility by open sourcing some of the core bits!<p>It sounds like your marketing will need to explain:<p>1. How updates work and how you guarantee staying universes away from NSFW/illegal content -- answered separately because nobody wants to find out what IPFS is infamous for as a part of discovering your service. (Both explanations need to function at two levels: one for techies and one for their bosses controlling the purse strings.) This may be possible to pull in quickly from existing CC-licensed documentation.<p>2. How users can link to content through multiple redundant WWW gateways/other services, and how to pay (you and others) for more reliability. Reliable reachability is absolutely key here, and should be built on multiple existing 3rd parties that are already used as status pages. For example: pay extra to whitelabel an auto-Twitter retweet bot.<p>Opportunity to be the "enterprise IPFS contact" here - explain from soup to nuts how to push status updates from anywhere (setup and simplified through your service but without requiring it be reachable) with any of multiple Yubikey/hardware auth tokens.<p>--<p>Consider a completely separate marketing push/landing page that doesn't even mention IPFS until potential customers ask how it works. IPFS is a buzzword here but commercial customers probably count it as a negative (analogy: ICO on HN). Focus on the unique features IPFS offers and write up how those features solve the status page problem!
I love that the background image is a schematic of a centralized network. Look at that single point of failure! ^^<p><a href="https://www.dstatuspage.net/decentralized.png" rel="nofollow">https://www.dstatuspage.net/decentralized.png</a>
I'm not sure this is actually Decentralized. I have been playing with IPFS quite a bit recently, and this looks to host the content on one node. That node goes away, your content goes away. You need more than one nodes 'pinning' the same content in order to actually be decentralized, and as far as I can tell this project doesn't provide that functionality.<p>That has been my biggest drawback so far with IPFS, there isn't really an easy way to get other nodes to pin the correct content, without passing around big nasty hashes (e.g., QmYwAPJzv5CZsnA625s3Xf2nemtYgPpHdWEz79ojWnPbdG) by hand.
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).<p>What about do not depend on a centralized infrastructure to deploy you status page and kept always alive?<p>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.<p>I thought this use case fits perfect on a decentralized environment.<p>You can deploy this service on a VPS for 1/4 of the price you pay for your current status page service provider.<p>See an example of a status page deployed using D StatusPage:<p><a href="https://gw1.dstatuspage.net/ipfs/QmePTzsSVae8BK8antLHfV2xWfEf3C8px7yQ9gUX5PY1N3/" rel="nofollow">https://gw1.dstatuspage.net/ipfs/QmePTzsSVae8BK8antLHfV2xWfE...</a><p><a href="http://gw2.dstatuspage.net/ipfs/QmePTzsSVae8BK8antLHfV2xWfEf3C8px7yQ9gUX5PY1N3/" rel="nofollow">http://gw2.dstatuspage.net/ipfs/QmePTzsSVae8BK8antLHfV2xWfEf...</a><p>What are you thoughts?<p><a href="https://www.dstatuspage.net" rel="nofollow">https://www.dstatuspage.net</a>
<a href="https://github.com/paulogr/dstatuspage" rel="nofollow">https://github.com/paulogr/dstatuspage</a><p>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:<p><a href="https://github.com/paulogr/dstatuspage/issues" rel="nofollow">https://github.com/paulogr/dstatuspage/issues</a><p>- ref-1: <a href="https://blog.statuspage.io/a-birds-eye-view-of-the-amazon-s3-outage" rel="nofollow">https://blog.statuspage.io/a-birds-eye-view-of-the-amazon-s3...</a><p>- ref-2: <a href="https://ipfs.io" rel="nofollow">https://ipfs.io</a><p>The software will be distributed for free and open source under MIT license.
One thing I'm missing (or misunderstanding) about IPFS is updates.<p>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 <i>entry</i> address, but is also referenced from the main <i>site</i> address.<p>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.<p>How to let readers know that a new entry is available then? Would there need to be a centralized place referencing all existing entries?
Has anyone here used both IPFS and DAT in-depth?<p>I am a happy IPFS user, and it seems that it has more traction than DAT. But on the other hand, the Beaker Browser project (which is based on DAT) is very interesting, and doesn't seem to have an equivalent in IPFS. I'm also worried that the IPFS team might get distracted by Filecoin and not invest seriously in the IPFS ecosystem beyond what Filecoin needs.<p>I'm interested to hear what others think?
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?
Decentralized is the new buzzword in the crypto community and it is used everywhere to justify everything. I lost count how many times people were trying to sell me ideas with "its decentralized, you get it???". I am getting more and more resilient to take anything seriously that is solved with this. For me S3 is a perfect storage and with Cloudfront is decentralized enough for my use cases. As far as I am concerned a node that is not under AWS or my control is not the definition of decentralized it just means that you have less control over a distributed object store that has worse access patterns than for example S3. Bandwidth is one of the problems. If a typical IPFS node is a home computer than it has 10x upload speed compare to the download speed. This is going to limit how somebody can access content from IPFS. And so on. These access patterns are pretty relevant when you are hosting something other than backups on such a system.
> Powered by D StatusPage on IPFS<p>The URI on the footer of the status page points to here: <a href="https://www.statuspage.co" rel="nofollow">https://www.statuspage.co</a> - but it doesn't appear to load, is this an artifact from development?
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.
Big fan of IPFS here, but silly question, isn't a status page suppose to have realtime updates of whether a service is online or not? This doesn't seem like a good fit unless you're using some realtime CRDT adapter on top like they list here <a href="https://github.com/ipfs/research-CRDT/blob/master/Readme.MD" rel="nofollow">https://github.com/ipfs/research-CRDT/blob/master/Readme.MD</a> (disclaimer: I'm the author of <a href="https://github.com/amark/gun" rel="nofollow">https://github.com/amark/gun</a>, which is one of the listed options). The StatusPage link is sparse on info, anybody know how it works underneath? Sorry if I'm confused on how status pages are supposed to work, can it really be static if it is supposed to be reporting services uptime liveliness (and thus requires some type of realtime monitoring)??
Apologizes for blockchaining every comment, but one of the cryptocurrencies I'm interested in, from a tech perspective, is doing something similar. It lets you host your website on IPFS as well.<p><a href="http://www.shiftnrg.org/" rel="nofollow">http://www.shiftnrg.org/</a>