10 ms·
> We can't expect each client to have an ipfs client installed. Couldn't they serve [js-ipfs](https://github.com/ipfs/js-ipfs https://github.com/ipfs/js-ipfs)
by asymmetric 8y ago
> We can't expect each client to have an ipfs client installed.
Couldn't they serve [js-ipfs](https://github.com/ipfs/js-ipfs https://github.com/ipfs/js-ipfs)?
AFAIK that would make every user of the web app run an IPFS node.
- sillysaurus3 8y agoThis was very interesting, but sadly: https://github.com/ipfs/js-ipfs/tree/master/examples/exchange-files-in-browser https://github.com/ipfs/js-ipfs/tree/master/examples/exchang... > Note: As js-ipfs@0.29.0 currently doesn't support DHT peer discovery, the peer from which you are fetching data should be within the reach (local or in public IP) of the browser node. The PR to implement DHT has been languishing since May 2017: https://github.com/ipfs/js-ipfs/pull/856/files https://github.com/ipfs/js-ipfs/pull/856/files
- asymmetric 8y ago> The PR to implement DHT has been languishing since May 2017: https://github.com/ipfs/js-ipfs/pull/856/files https://github.com/ipfs/js-ipfs/pull/856/files But it just received an update 4 days ago! :)