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 was archived by the owner on Jun 2, 2020. It is now read-only.
At the Berlin developer summit, we noted some shortcomings with the CID concept doc:
Should clarify that a CID specifies:
How to decode/interpret* content (“interpret” might not be a great term here; CIDs aren’t necessarily super-specific)
A version (but not a version of the data they identify)
A unique identifier (usually a [multi]hash)
We should explain how CIDs relate to “content addressing,” but need to be careful around the term “address” so as not to confuse it with either a multiaddress/peer address or with a full content address (e.g. /ipfs/<cid> or /ipfs/<cid>/some/sub/path).
The text was updated successfully, but these errors were encountered:
Improve CID concept doc (fixes#95).
- Explain format and components of a CID
- Explain how CIDs relate to label/address content
- Add more relevant links to specs and concept docs
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
At the Berlin developer summit, we noted some shortcomings with the CID concept doc:
Should clarify that a CID specifies:
We should explain how CIDs relate to “content addressing,” but need to be careful around the term “address” so as not to confuse it with either a multiaddress/peer address or with a full content address (e.g.
/ipfs/<cid>
or/ipfs/<cid>/some/sub/path
).The text was updated successfully, but these errors were encountered: