Closed jbenet closed 1 year ago
Oh and i wanted to say: let's propose this for the proper multihash spec, in a section like CID's (maybe "Loggable Multihash" or "Multihash Inspection string" or something that emphasizes dev use but not identifier use)
I would want to ensure people don't use the string versions to rely on them for identifiers
This was one reason I didn't implement a way to decode the URN version back into a multihash. :)
This was one reason I didn't implement a way to decode the URN version back into a multihash. :)
@greglook :heart:
closing due to inactivity, archiving repo
Saw this in readme:
nice-- i ran into the same need when making the CID spec here: https://github.com/ipld/cid#human-readable-cids. I would discourage use of
:
end prefer-
because it would be great if people use the compressed representation in URNs instead of the expanded one... but i can be persuaded.(I would want to ensure people don't use the string versions to rely on them for identifiers-- as the whole copy-pastability and versatility of multihash goes down with that).
See also