Experiment with embedded js-ipfs

[lidel]

Not sure how feasible JS implementation is at this time, but in future it should be possible to bundle it with the add-on and add a setting "Use embedded IPFS node" which would automatically start js-ipfs instance and use it instead of external HTTP gateway.

Ref.
https://github.com/ipfs/js-ipfs#use-in-the-browser-with-browserify-webpack-or-any-bundler

[lidel]

There is ongoing effort at ipfs/in-web-browsers#42 (comment)

[dignifiedquire]

Subscribing, please ping me if there is anything you need help with making this happen.

[lidel]

@dignifiedquire
In short, WebExtension could use embbeded js-ips for two things:

1. Expose IPFS API as window.ipfs on EVERY page, so that site developers can look for it and take advantage of it.
   There is unfinished PoC at https://github.com/VictorBjelkholm/js-ipfs-in-the-browser.git
   This is something we may revisit in future, but is not production ready yet due to security concerns. There is a ticket about securing API with ACL and Tokens at HTTP API, access control and API tokens notes#159

2. Provide local IPFS2HTTP Gateway (just like go-ipfs does) so that WebExtension can run without go-ipfs and redirect HTTP requests to a local js-ipfs node.
   This is something I could integrate with right now, but js-ipfs's gateway functionality is not ready yet.
   I think if you could look at No routes for HTTP Gateway js-ipfs#693 and Add gateway route /ipfs/* js-ipfs#698 it would be a good step towards that goal. 👍

[lidel]

Continued in #248