4 ms·
There are many gateways that allow viewing IPFS content over HTTP (e.g. ipfs.io), but the "true" IPFS experience is not over HTTP, it's done via P2P and address
by lekevicius 5y ago
There are many gateways that allow viewing IPFS content over HTTP (e.g. ipfs.io), but the "true" IPFS experience is not over HTTP, it's done via P2P and addressed using content hashes. For example, one of my NFTs has content hash of
QmTqkpmbKmciQgqhUWpML7dsJ59MBEjgQd7wH853n4ASZM
I keep a copy of it on my computer (+ backups). If for some reason it were to be unhosted by every IPFS participant, I could become one, and re-establish my NFT. Image content -> content hash, so everyone would agree about content re-establishing.
Not sure if I fully answered your question.
- spenczar5 5y agoThanks, that is indeed a good description. It does sound like this is basically the content hashing Moxie was hoping for.
- mkl 5y agoSpecifically, that gateway (and some (all?) others) needs "/ipfs/" in the URL: https://ipfs.io/ipfs/QmTqkpmbKmciQgqhUWpML7dsJ59MBEjgQd7wH853n4ASZM https://ipfs.io/ipfs/QmTqkpmbKmciQgqhUWpML7dsJ59MBEjgQd7wH85... Took me a while to figure it out, but the docs are here: https://docs.ipfs.io/how-to/address-ipfs-on-web/ https://docs.ipfs.io/how-to/address-ipfs-on-web/ I also ran into several apparently no-longer-functional gateways in lists from just a few months ago. So yes, not the true experience.