3 ms·
This is an interesting point. In my experience, it's very common for HTTP(S) to be used for the "last mile" for content that originates from IPFS. Generally t
by eminence32 5y ago
This is an interesting point. In my experience, it's very common for HTTP(S) to be used for the "last mile" for content that originates from IPFS. Generally this is done via public or dedicated IPFS gateways.
Even when you have a local IPFS node (which is not common), the "last meter" delivery is still done using HTTP too, via a local gateway
- capableweb 5y ago> it's very common for HTTP(S) to be used for the "last mile" for content that originates from IPFS Indeed, it seems very common, but that doesn't make my original point less true. > the "last meter" delivery is still done using HTTP too, via a local gateway Yeah, that seems common too, but less "wrong" to call it "IPFS support" in that case, in my opinion. Running your own IPFS gateway at least makes the content actually fetched from the network (internet) via IPFS while using ipfs.com/cloudflare-ipfs.com is not any different than just using a CDN (except usually you have to pay for CDNs, IPFS gateways seems to be free (for now)).
- Datagenerator 5y agoDepending on centralized CDN's with logging is not using native IPFS, correct if wrong
- capableweb 5y agoI don't understand what you mean, what's the question?
- eminence32 5y agoYup, agreed with all your points
- AgentME 5y ago>Running your own IPFS gateway at least makes the content actually fetched from the network (internet) via IPFS while using ipfs.com/cloudflare-ipfs.com is not any different than just using a CDN (except usually you have to pay for CDNs, IPFS gateways seems to be free (for now)). I think there's still a lot of value in this way of using IPFS: using ipfs.com/cloudflare-ipfs.com makes it much easier to swap to another IPFS gateway (including your own local one) if those gateways ever give you issues.