Re:Introducing Cloudflare’s IPFS Gateway
by deckar01 on Monday September 17, 2018 @02:27PM
(#18008555)
IPFS is a protocol that dictates how it's clients are supposed to validate the data. If you use any of the client libraries they will do this for you (go-ipfs/js-ipfs). If you want to use cloudflare to distribute your index, you need to trust them to use a valid client implementation. Otherwise you can serve an index file off of your own server/network and distribute the rest of the assets via IPFS.
Re:Introducing Cloudflare’s IPFS Gateway
by the8472 on Monday September 17, 2018 @03:25PM
(#18009135)
> You'll have to add some checks on your end for this as HTTP/browsers cannot provide these guarantees currently
Browser extensions could by verifying content as it arrives.
https://developer.mozilla.org/en-US/docs/Mozilla/Add-ons/Web...
Re:Introducing Cloudflare’s IPFS Gateway
by AgentME on Monday September 17, 2018 @04:49PM
(#18009942)
A browser extension could be used to request the data straight from ipfs instead of Cloudflare.
Re:Introducing Cloudflare’s IPFS Gateway
by akavel on Monday September 17, 2018 @05:03PM
(#18010069)
The extension exists: https://github.com/ipfs-shipyard/ipfs-companion
Re:Introducing Cloudflare’s IPFS Gateway
by bren2013 on Monday September 17, 2018 @05:04PM
(#18010074)
I believe the IPFS team has already built a browser extension that runs a js-ipfs node. Running an IPFS node is not ideal for power and bandwidth constrained devices like a mobile phone. This is where I see gateways fitting in, long-term. Not having to trust a gateway unconditionally is necessary to make this viable.
So if you start a IPFS node locally, it won't get content pushed to it (well, some DHT data which is basically routing information, but not the content itself).
> ultimately, how can I know for sure that CloudFlare won't play the game where as acting as a proxy they will modify some of the files served?
You'll have to add some checks on your end for this as HTTP/browsers cannot provide these guarantees currently (maybe in the future?). So, download file A and add it to IPFS from your end. If you end up with the same hash, the content was not modified.
> isn't p2p file system like this all about trusting the network and not 1 server
Yes, IPFS <> IPFS is trustless as this verification happens automatically and the clients can verify content locally when it gets fetched. IPFS <> HTTP is harder as there is no functionality for doing this verification.