You’ve probably heard IPFS referred to as the permanent web, or the immutable web. This is a big idea… an immutable store of all the world’s information. It all ties back to the idea of content addressing, which we’ve talked about before on this blog. To refresh your memory: the immutability of content on IPFS gives us nice things, like de-duplication of data (because the same content from different peers will produce the same hash address) and content verification (so we can be confident that content has not been modified if its hash matches what we were expected/requested). This means nobody can add malicious code on its way to my peer (no MITM attacks here). Here’s a great video that explains a lot about how the immutability of IPFS is implemented.
This is a companion discussion topic for the original entry at https://blog.textile.io/the-definitive-guide-to-publishing-content-on-the-decentralized-web/