ipfs-companion

These libdweb Browser Extension APIs never landed in any official Firefox Nightly build. Mozilla stopped working on libdweb in 2019 (https://github.com/ipfs/ipfs-companion/pull/533#issuecomment...).

That is correct. If you have the IPFS Companion[0] browser extension installed then it can automatically recognize URLs of this form and rewrite them to use your local IPFS node instead of the public ipfs.io gateway. The advantage of using https://ipfs.io/ipfs/... in your links instead of ipfs://... is that the former still works even if the visitor doesn't have the extension installed. [0] https://github.com/ipfs/ipfs-companion

Anyone would like to try IPFS in Browser, you can use the IPFS Companion(https://github.com/ipfs-shipyard/ipfs-companion) and IPFS-Desktop(https://github.com/ipfs-shipyard/ipfs-desktop). IPFS Companion supports many mainstream browsers.

Note that IPFS has had a browser extension for quite some time for IPFS support. This inclusion is mostly akin to bundling a browser extension. While it is great to see it included by default, it really isn't a great reason to switch browsers unless you have other reasons: https://github.com/ipfs-shipyard/ipfs-companion

Not only possible but already done! - https://github.com/ipfs-shipyard/ipfs-companion - https://chrome.google.com/webstore/detail/ipfs-companion/nib... - https://addons.mozilla.org/en-US/firefox/addon/ipfs-companio... And I think Brave already ships with IPFS-Companion installed.

The extension exists: https://github.com/ipfs-shipyard/ipfs-companion

Indeed, that's a good idea! I took the freedom to open a issue about this idea on the repository for the IPFS-Companion extension here: https://github.com/ipfs-shipyard/ipfs-companion/issues/581

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/...

This is a interesting point and I agree, pretty important privacy feature that we should discuss more. Off the top of my head, there could be some things we could do to help this, but the async/sync nature of `window.ipfs` makes it harder. If variable access was async, we could prompt before exposing it, but since we want to enable the browser extension to be a migration path to having native IPFS support in the browser, it becomes harder. lide went ahead and opened a issue (https://github.com/ipfs-shipyard/ipfs-companion/issues/451), so if you're reading this and have ideas, we'd love to hear from you! We care deeply about this issue but was not required for the initial prototype we have now. (Disclaimer: I work on IPFS)

Keep in mind that HTTP gateways are provided just for convenience. Due to WebExtension API limitations embedded node can't act as a local HTTP gateway and extension falls back to public gateway. I imagine it was what you were experiencing. Use window.ipfs property to play with pure IPFS (without HTTP gateway): window.ipfs.id(console.log) window.ipfs.add(Buffer.from('hello')).then(console.log) window.ipfs.cat('/ipfs/QmWfVY9y3xjsixTgbd9AorQxH7VtMpzfx2HaWtsoUYecaX').then((data) => console.log(new String(data))) More info: https://github.com/ipfs-shipyard/ipfs-companion/blob/master/...

Yup, DTube, like most projects related to STEEM still have a high degree of centralization. This reddit comment gives a good evaluation of DTube: https://www.reddit.com/r/dtube/comments/7ysdn1/how_distribut... So most parts of it could at their core be used in a distributed fashion, but are actually accessed via CDNs. E.g. you could use ipfs-companion[0] to alter all instances of ipfs.io URLs to point to a local IPFS daemon that is connected to the IPFS network in a distributed fashion. I did just that and streamed a video on DTube via a local IPFS daemon and the result was pretty underwhelming, since it took quite some time for the video to load, but I don't dare to evaluate why that is so. After that it does have the nice benefit though that the same video streams instantly on any other machine in my home network! In a transitional phas

All IPFS needs is less install friction. The local IPFS server packaged as a chrome extension is what is keeping it back: https://github.com/ipfs-shipyard/ipfs-companion/issues/248

That's entirely correct. Before it had to be prefixed with `web+` and now just `ipfs://` will work. For the extension, the IPFS community have been developing one which will use this new feature: https://github.com/ipfs-shipyard/ipfs-companion PR for tracking the protocol handler is here: https://github.com/ipfs-shipyard/ipfs-companion/pull/359 Disclaimer: I work for Protocol Labs on IPFS

We are working on extensions/addons for all major browsers -- you can see an early version here: https://github.com/ipfs/ipfs-companion