ash

Currently tests only run against js-ipfs. We should run against go-ipfs also so that proxying for features available in go-ipfs that are not yet available in js-ipfs can be tested....

(not currently spec'd or tested by interface-ipfs-core) * [ ] `log.level` * [ ] `log.ls` * [ ] `log.tail`

(not currently spec'd or tested by interface-ipfs-core) * [ ] `diag.cmds` * [ ] `diag.cmds.clear` * [ ] `diag.cmds.set-time` * [ ] `diag.sys`

The currently implementation of the progress option is incorrect - it tracks progress of files being buffered into memory. Progress needs to be sent from the IPFS node over postMessage...

https://github.com/ipfs/interface-ipfs-core/blob/master/SPEC/UTIL.md

If calling code never consumes a stream then it'll leak the event listener that `pull-postmsg-stream` adds to consume the stream

This is just a shell module that depends on importer/exporter and js-ipfs has not depended on it for a while now. Also, right now the published version of this module...

[WIP] feat: adds tests for name.publish and name.resolve

3

* Adds test which: 1. creates two nodes 2. connects them (`swarm.connect`) 3. calls `name.publish` on node0 4. calls `name.resolve(`/ipns/${node0.peerid}`)` on the other **I could do with some advice possibly...