ipld

• Version: ipfs-core: 0.14.1
• Subsystem: types, core

Severity: Very Low

Description:

in type definition put: (...) => Promise<CID>, but docs Promise<Block>

Which type is correct?

This was cut from the v0.2.0 release for present time constraints however making ipfs-http more accessible as "the" ipfs binary would make the project more accessible to anyone just wanting to try it out. At the moment I see the following obstacles:

• http/README.md has no tutorial on how to try out ipfs-http
• ipfs-http supports only `i

Ideally, we'd take a page from the https://github.com/multiformats/js-multiformats book and support cjs, esm, etc builds via rollup and friends to support multiple platforms/use-cases. Since this is designed to be a light-weight alternative to other ipds-based libraries, it should have a really low barrier to usage out of the box. In fact, moving forward, this should be a pretty critical require

Another possible method of filtering data would be using bayesian classification such as https://github.com/lytics/multibayes.

To complete this issue research should be done to see if this provides any notable benefits, and if so provide a small prototype of the functionality.

The ls and resolve commands shows my .pinset entry as having a size of 60. Let's force it to add units in all cases.

? > ls
.       2.4G  QmSc9pcnm4N1QC1u2oSNL6eRgFjxDq2Aex6cGhTkvw91xc
.pinset 60    QmYJmoKWDFh1wmZLATh3fiVzMuhhTyNm9NLGuLEJM7HdNZ
dapps   17.5M QmQN6bA5YEPEaPDUDLq6o9fm24Ye2bbnA4YUT2rBeAR5cm
foo     2.4G  QmPkNdFzNFZfM9QixL3ZowBNvveFmufbnRuM36K1SrnmB1

Currently the FileAPI is only capable of uploading single files, we should enable directory uploads