I noticed since new release a change in URL path.
http://localhost:8080/ipfs/Qm_HASH
becomes
http://subdomainHASH.ipfs.localhost:8080
I wonder how this is done?
And which CLI commands make relation between Qm_HASH_ and subdomainHASH ?
I wonder how this is done?
Magic!
And which CLI commands make relation between Qm_HASH_ and subdomainHASH ?
The Qm hash is a CidV0 Content Identifier (CID) which uses base58 encoding.
The subdomain hash is a CidV1 content identifier which uses base32 encoding. It is the same underlying hash, just represented differently.
You can covert between hashes using ipfs cid commands. ipfs cid base32 <QmHash> for example.
2 Likes
thanks for you clear answer.
I wonder if the file I open with URL like that is “pin” by my local ipfs daemon?
I don’t see it in my “Compagnon IPFS”, but is only shows “ipfs files”
Do you know how I could know where is that Qm_HASH_ ?
Things you visit using your local gateway etc are not pinned by default. They are just cached locally.
ipfs refs local shows all the things that exist locally (pinned or not, root and non-root nodes).
thank you @hector that ipfs refs local is a bit scary, none of file structure appears from it…
is there a way to seek for “human readable data”
No, there is no easy way to have a list of websites you have visited while using IPFS if you haven’t pinned them or added them to MFS.
thanks @hector
same discussion is starting here Why is ipfs url different now?