ipfsx
ipfsx copied to clipboard
ipfs-shipyard
Experimental IPFS API
https://blog.ipfs.io/2020-02-01-async-await-refactor/ landed some this year: should we deprecate / archive this repo and move it to https://github.com/ipfs-inactive/? cc @alanshaw
Perhaps this could all be under `.ls` and be a thin wrapper around the [unixfs exporter?](https://github.com/ipfs/js-ipfs-unixfs-exporter#exportercid-ipld) (since it supports more than just unixfs nodes?)
`ipfsx.stat` could operate on arbitrary IPFS hashes as well as `mfs` paths, though it would not return all the fields for non-unixfs nodes.
The `mfs` operations have a `flush` flag to not write to disk immediately. Unless I'm missing something there's no way in this API to explicitly flush an mfs path after...
Here in IPFSX adding content always returns an iterator, which is a [nice consistent API](https://github.com/ipfs-shipyard/ipfsx/blob/master/API.md#add), but when adding a single file calling `.first()` or `.last()` on the iterator feels a...
Everything we can do with the block API we can do with the DAG API, and the DAG API prevents us from putting invalid data in IPFS.
`cp` and `ls` have the issue of not being able to distinguish between an IPFS path and an MFS path. If we prevent any writes (including cp, mv etc.) to...
Please read https://github.com/ipfs/specs/issues/98#issuecomment-236615179
Add should accept a URL or a file path as it's input argument. Please read https://github.com/ipfs/interface-ipfs-core/pull/378
The current rationale wants [`ls` size to be the TOTAL size of the node and it's children including any protobuf wrappers](https://github.com/alanshaw/ipfsx/blob/master/RATIONALE.md#todo-consistent-sizes). There is existing a `cumulativeSize` field and I think...