-
As far as I understand, the purpose of IPLD is to largely be codec agnostic, and correspondingly it seems like the derivations being tied to the Codec defeats this property. It is perhaps the case tha…
-
Currently the HTTP API only really supports JSON. Having Cbor API would be useful for js-ipfs-api (mainly for `api.dag.*`, see https://github.com/ipfs/go-ipfs/issues/3771), we could use https://github…
-
### Goals
- Single-user (but potentially multi-repo) PDS. Although perf-wise it could probably handle many users, being single-user means we can skimp on moderation and admin features.
- Low syste…
-
This is the result of some research in regards to passing JavaScript data into WebAssembly.
Currently the best integration between a language that targets WASM and a language outside WASM (a host l…
-
> This a placeholder for gathering references to create a more fleshed out plan.
We have distinct Gateway (/ipfs, /ipns) and API (/api/v0) endpoints today, and only the most basic read operations c…
lidel updated
11 months ago
-
go-graphsync currently uses google protobuf for messaging. Since graphsync depends on IPLD and IPLD can be used in place of GPB, we can reduce dependencies, tooling and simplify the design by replaci…
-
ipld 0.6 locks the node version to ^4.0.0. It is required by transmute-framework.
https://github.com/transmute-industries/transmute-framework/blob/b14becb8f42380870f467246d4d920289e8945c5/package.j…
-
Currently Helia takes a blockstore that it enhances with bitswap. This creates a hard dependency on bitswap.
To enable experimentation and adoption of faster/more use-case specific retrieval proto…
-
Context: https://github.com/ipfs/ipfs/issues/337
Currently, both js-ipfs and go-ipfs index blocks in the datastore by CID. Unfortunately, it's possible for a single block to have multiple CIDs due …
-
This deserves some discussion before implementation.
The largest contributor to our bundle size is codecs and hash algorithms. When unused these are completely unnecessary bundle bloat, and rarely …