You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
As we've discussed today, it would be a big UX win if as part of this project we detect CIDv0 passed to ipfs:// and fix it up by converting it to case-insentive CIDv1, allowing users to load legacy CIDs.
The text was updated successfully, but these errors were encountered:
While the ecosystem moves towards base insensitive CIDv1 in Base32,
we still have a lot of data addressed with CIDv0 (case-sensitive Base58btc).
Unfortunately, the authority component of URL entered in the address bar gets force-lowercased, which breaks the case-sensitive CIDv0 identifier:
ipfs://QmbWqxBEKC3P8tqsKc98xmWNzrzDtRLMiMPL8wBuTGsMnR
→ipfs://qmbwqxbekc3p8tqskc98xmwnzrzdtrlmimpl8wbutgsmnr
This is the same problem as ipfs/ipfs-companion#1006 (more examples there).
As we've discussed today, it would be a big UX win if as part of this project we detect CIDv0 passed to
ipfs://
and fix it up by converting it to case-insentive CIDv1, allowing users to load legacy CIDs.The text was updated successfully, but these errors were encountered: