4 ms·
They are, however, essential for the transition to it; at least as long as they continue the goal of becoming the new web.
by setr 8y ago
They are, however, essential for the transition to it; at least as long as they continue the goal of becoming the new web.
- imhoguy 8y agoWithout major players joining - browser vendors, it will be like IPv6 transition.
- ndnxhs 8y agoFirefox has partly added support recently. They recognise ipfs:// as a valid protocol and allow extensions to implement it.
- detaro 8y agoExtensions can't implement the raw IPFS protocol though, they need a companion application running the actual gateway, or can maybe use the WebRTC transport.
- lgierth 8y agoNo, js-ipfs can run a full ipfs node right in a web page. It'll peer with other nodes over websockets, and do relaying if neccessary.
- jstanley 8y agoDoes js-ipfs work yet? Around the time I first wrote hardbin people were saying you could use js-ipfs, but it just didn't work. My non-javascript node couldn't access content published by js-ipfs, which seems like a major flaw.
- jstanley 8y agoIf you want to use IPFS without using a public gateway, it is very easy to install and use a local gateway. If you also use a browser extension like "IPFS Companion", it can automatically redirect all IPFS-looking URLs to your local gateway. I agree this doesn't help for casual users who have never heard of it, but it's at least better than "everyone has to use a public gateway all the time".