| Its not like that.... If you send you code to github, then deleted that code in our computer, and github goes down before any other person cloned your repo and decided not delete, then you code is lost. You same question can be applied here: Why someone will download a random repo on the github and store just for fun? No one will do that without any reason. So, on git the only people that keep any file/repo offline, has any interest on that content to be hosted with then. The same here, if I send any file using IPFS, the same file will be accessible using any gateway, my own gateway, my neighbor, or some other that i dont know who owns in other part of the globe. The gateway is just a gateway. Its one way to find some asset on the network, and has a optional cache. Months ago I send one file using IPFS, then accessed via cloudflare (and others) gateway, then I deleted my file, and in few hours the file was inaccessible in every gateway that i tested. No gateway keep you file forever.... But then can if they want, anyone can keep any block if they want. So, the same way as my previous example using git! The asset will exists util everyone that hold that asset want to keep, but because you cant control the others nodes, once some asset is public over the network, thats can be "forever" or just few hours. So... IPFS is more about in how you can share assets privately than the lifetime of the object. And with or without cloudflare IPFS is decentralized because at any point i can setup any gateway that can listen my assets in the same way (same hash) than any other gateway. IPFS gatway is much more about node discovery + cache.... No centralization happens here. You can store third party blocks in you node if you want, or rely on other nodes if want, but thats is up to you. Its the same as upload anything to any cloud then delete the local copy. |