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
{{ message }}
This repository has been archived by the owner on Feb 8, 2023. It is now read-only.
Currently, the IPFS daemon plays it fast-and-loose with pathing and uses the CID (whether or not the object is stored as a protobuf) to decide on whether to path through it as an IPFS directory tree or an IPLD object.
Instead, we may want to consider using a /ipld/... prefix. We definitely should not be disambiguating based on the CID as the object encoding should have no bearing on how we path through it once we've decoded it.
The text was updated successfully, but these errors were encountered:
Currently, the IPFS daemon plays it fast-and-loose with pathing and uses the CID (whether or not the object is stored as a protobuf) to decide on whether to path through it as an IPFS directory tree or an IPLD object.
Instead, we may want to consider using a
/ipld/...
prefix. We definitely should not be disambiguating based on the CID as the object encoding should have no bearing on how we path through it once we've decoded it.The text was updated successfully, but these errors were encountered: