4 ms·

This is awesome. We've been running an IPFS gateway at Origin for about a year and are huge fans of the technology. It's nice to see Cloudflare investing in dec

This is awesome. We've been running an IPFS gateway at Origin for about a year and are huge fans of the technology. It's nice to see Cloudflare investing in decentralized technology despite contributing to the over-centralization of the web with their core business. There are quite a few public IPFS gateways available, but not all of them are broadly advertised. A few others that I know of: ipfs.io ipfs.infura.io siderus.io ipfs.jes.xxx gateway.originprotocol.com

diggan 8y ago
I just went through our "Public IPFS Gateway Checker" and added a bunch of new ones (include the Cloudflare) one. You can see it running here: https://ipfs.github.io/public-gateway-checker/ https://ipfs.github.io/public-gateway-checker/ And of course, the source code: https://github.com/ipfs/public-gateway-checker/ https://github.com/ipfs/public-gateway-checker/
- joshfraser 8y ago
  Oh neat. Should I send a PR to add the others?
  - diggan 8y ago
    Please do :)
burdakovd 8y ago
Just want to add an alternative gateway that I've been working on recently: dapps.earth It is somewhat different in the sense that it redirects from `gateway/ipfs/hash` to `hash.ipfs.gateway` to ensure different ipfs websites are hosted at different origins (Cloudflare also talked about origin issues in their announcement). Now with what Cloudflare release, they do seem to solve some of the similar problems, but they still ask users to register the domains by themselves (or access in unsafe way with `/ipfs/hash` urls), which means those domains become a centralization point, and also most of the content is served from the same domain. It would be fantastic if they allowed access in form `hash.cloudflare-ipfs.com` or `ens-name.cloudflare-ipfs.com`. In the meantime I may just abandon the idea of serving ipfs content myself, and instead can just operate a small DNS-server that will return CNAME record pointing to Cloudflare and TXT record pointing to ipfs hash for each subdomain.

diggan 8y ago

I just went through our "Public IPFS Gateway Checker" and added a bunch of new ones (include the Cloudflare) one. You can see it running here: https://ipfs.github.io/public-gateway-checker/ https://ipfs.github.io/public-gateway-checker/ And of course, the source code: https://github.com/ipfs/public-gateway-checker/ https://github.com/ipfs/public-gateway-checker/

joshfraser 8y ago
Oh neat. Should I send a PR to add the others?
- diggan 8y ago
  Please do :)

burdakovd 8y ago

Just want to add an alternative gateway that I've been working on recently: dapps.earth It is somewhat different in the sense that it redirects from `gateway/ipfs/hash` to `hash.ipfs.gateway` to ensure different ipfs websites are hosted at different origins (Cloudflare also talked about origin issues in their announcement). Now with what Cloudflare release, they do seem to solve some of the similar problems, but they still ask users to register the domains by themselves (or access in unsafe way with `/ipfs/hash` urls), which means those domains become a centralization point, and also most of the content is served from the same domain. It would be fantastic if they allowed access in form `hash.cloudflare-ipfs.com` or `ens-name.cloudflare-ipfs.com`. In the meantime I may just abandon the idea of serving ipfs content myself, and instead can just operate a small DNS-server that will return CNAME record pointing to Cloudflare and TXT record pointing to ipfs hash for each subdomain.