Webapp work on top of IPFS api directly

[jbenet]

Offline: You can also run the application locally by cloning the project and start webserver of choice, serving the root folder. python -m SimpleHTTPServer is a handy command for serving from current folder.

Why need server? why not just access it on the IPFS daemon's api directly? (with proper CORS setup)

(once ipfs/kubo#1886 is merged, we wont even need that)

[victorb]

Good question! Looked into why and this is why.

Some API methods in js-ipfs-api gets different responses depending on where they run, ipfs.add seems to be one of them. When running via my local gateway, http://localhost:5001/ipfs/QmURTVk4xWXXNHE5xBTDojSmLJr9BvJXeHqVNr63XJ2fzC, it returns a array of objects that has the hash. But, when running from ipfsbin.xyz, it instead returns an object directly. Probably/Maybe has to do with ipfs-inactive/js-ipfs-http-client#79 or ipfs-inactive/js-ipfs-http-client#76

[jbenet]

ipfs/kubo#1886 is merged as part of 0.3.9 release.

[victorb]

Now just waiting for ipfs/infra#105 then I'll enable writing to the public gateway by default, falling back to ipfsbin.xyz if not working.

[jbenet]

Sounds good. Though 0.3.9 means you no longer need the private API, can do everything through the public Gateway/API now.