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 Jun 29, 2022. It is now read-only.
Most of our IPLD implementations from js-ipld to js-ipfs-ipld assume that there is only one way to encode an IPLD object and this is CBOR. However, from the new CID conversations, IPLD+CBOR is what we all have implemented.
Generalize our modules
Create a module js-ipld-cbor(-parser|-serializer)?
note: All this is of course abstracted from the IPLD modules that by default will choose to use IPLD+CBOR
The text was updated successfully, but these errors were encountered:
Taken from (meeting-notes/2016-09-19-ipld.md#layers)
Most of our IPLD implementations from js-ipld to js-ipfs-ipld assume that there is only one way to encode an IPLD object and this is CBOR. However, from the new CID conversations, IPLD+CBOR is what we all have implemented.
note: All this is of course abstracted from the IPLD modules that by default will choose to use IPLD+CBOR
The text was updated successfully, but these errors were encountered: