Should we connect to known ipfs nodes here or wait for 3box.js to request to connect to known ipfs node as it does right now. Which is faster?

🚨 You need to enable Continuous Integration on Greenkeeper branches of this repository. 🚨

To enable Greenkeeper, you need to make sure that a commit status is reported on all branches. This is required by Greenkeeper because it uses your CI build statuses to figure out when to notify you about breaking changes.

Since we didn’t receive a CI status on the greenkeeper/initial branch, it’s possible that you don’t have CI set up yet. We recommend using Travis CI, but Greenkeeper will work with every other CI service as well.

If you have already set up a CI for this repository, you might need to check how it’s configured. Make sure it is set to run on all new branches. If you don’t want it to run on absolutely every branch, you can whitelist branches starting with greenkeeper/.

Once you have installed and configured CI on this repository correctly, you’ll need to re-trigger Greenkeeper’s initial pull request. To do this, please click the 'fix repo' button on account.greenkeeper.io.

In the repo configs, ipfs allows you pass an instance of different storage backends - https://github.com/ipfs/js-ipfs-repo#setup. Some are listed there, but you can also implement and pass your own. So this story is to create a lib like https://github.com/3box/orbit-db-cache-postmsg-proxy which we did for orbitdb, and do it now for https://github.com/ipfs/js-datastore-level#readme which is the default ipfs storage in the browser.

This is worth trying, but first proposed changes should be implemented first. (Only 2 point to time box and try, real implementation would be more like 5pts in total)

The fallback would be for both orbitdb and ipfs to fallback to use localstorage instead of indexdb.

Based on this 3box/3box-js#267 (comment) and after further looking it looks like ipfs does implement an abstract-leveldown compliant store interface for their store. There are libs that implement the same interface for local storage. So there is could chance a reliable lib could allow us to implement this quickly.

Subtasks

• Code cleanup, modularize and make it easy to read and understand
• Add testing, aim for 80% coverage
• Enable circleci
• Enable greenkeeper

The client/library calls this window to connect to peers. We should optimistically connect to the default known pinning node on page load. Don't have to change anything in lib, the promises to connect will just return faster if already connected to the node.