4 ms·

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

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.

edraferi 9y ago
> anyone on the IPFS network could have a copy of your page Yes, but critically they can't modify it thanks to content addressing [0]. > and serve them in your behalf. Yes, over IPFS. So anyone with an IPFS client will have a robust way to view your status page. If people want to view it via HTTPS, they hit ipfs.io, which is an IPFS/HTTP gateway. While it's possible for other people to run gateways, I believe ipfs.io is the main one. It could theoretically be a bottleneck. [0] https://dweb-primer.ipfs.io/avenues-for-access/lessons/power-of-content-addressing.html https://dweb-primer.ipfs.io/avenues-for-access/lessons/power...