You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I'd say that, in a sense, IPFS is a CDN. That's because popular content is automatically replicated to more nodes - by being cached on transit nodes and by allowing seamless and permissionless addition of replicas.
The name of this repo is probably a bit misleading.
What this tool can do is importing CDN contents to an IPFS node, replicating the directory structure with IPNS. This can e.g. allow easy transition in websites from conventional CDN paths to IPNS paths. But the IPNS part is optional. If somebody fetches e.g. a version of jquery based on its hash, it may as well be served by an IPFS node "equipped" with this file by this tool (in fact my IPFS node consumed a lot of bandwidth after I tested this tool).
The cloudflare gateway is something else again. It's basically a central gateway to IPFS.
Cloudflare itself maybe architecturally decentralized, but that's not the main point about IPFS. For a deeper understanding of the topic decentralization, I highly recommend to read https://medium.com/@VitalikButerin/the-meaning-of-decentralization-a0c92b76a274.
hello
recently cloudflare setup ipfs gateway online.
[https://blog.cloudflare.com/distributed-web-gateway/]
so I ask what the good point IPFS can help with currently CDN?
any suggestion would be appreciate. thanks.
The text was updated successfully, but these errors were encountered: