Pushing the Limits of IPFS and OrbitDB

Re:Pushing the Limits of IPFS and OrbitDB by detaro on Tuesday May 29, 2018 @07:30AM (#17178126)

ipfs.io is a gateway, fetching the content from the IPFS network and serving it to you over HTTP.

[ Parent | on HN ]

Re:Pushing the Limits of IPFS and OrbitDB by fwdpropaganda on Tuesday May 29, 2018 @07:35AM (#17178152)

So sort of an intermediary between how the internet works these days, and how it should work in IPFS view.

Does the "deliverying JS to browser" thing that I described make sense at all?

[ Parent | on HN ]

Re:Pushing the Limits of IPFS and OrbitDB by Confiks on Tuesday May 29, 2018 @09:01AM (#17178725)

There is already a Javascript implementation [1], but it is not feasible to setup a full IPFS node in every browser tab that loads an IPFS resource. Instead you can use ipfs-companion [2], a browser extension that lets you easily load IPFS resources in your browser. While it can use the Javascript implementation, this is not recommended as it is currently pretty resource heavy [3].

[1] https://github.com/ipfs/js-ipfs

[2] https://github.com/ipfs-shipyard/ipfs-companion

[3] https://github.com/ipfs-shipyard/ipfs-companion/blob/master/...

[ Parent | on HN ]

Re:Pushing the Limits of IPFS and OrbitDB by detaro on Tuesday May 29, 2018 @07:38AM (#17178179)

There's work on running the IPFS protocol over WebRTC, so yes, it makes sense and is another way of enabling normal browsers to access it.

[ Parent | on HN ]