IPFS Companion 2.2.0 brings window.ipfs to your Browser
1–10 of 27 posts
Re: IPFS Companion 2.2.0 brings window.ipfs to your Browser
#2I'd really love to see something like this show up as a proposal with the W3C (or the WHATWG -- I'm not entirely sure who's the authority on this?).
Re: IPFS Companion 2.2.0 brings window.ipfs to your Browser
#3Dat+Beaker is way ahead of IPFS in tooling, developer mindshare, consumer friendly UI, etc. With $250 million it's pretty shocking they don't seem more worried/focused on that.
Re: IPFS Companion 2.2.0 brings window.ipfs to your Browser
#4Dat+Beaker is way ahead of IPFS in tooling, developer mindshare, consumer friendly UI, etc. With $250 million it's pretty shocking they don't seem more worried/focused on that.
Interestingly I've heard of IPFS many many times and this is the first I've heard of Dat+Beaker. Do you have a starting point you suggest to get an idea of what it is or does?
Re: IPFS Companion 2.2.0 brings window.ipfs to your Browser
#5How do I know that the embedded mode works? It says "IPFS resource loaded via Public Gateway".
Re: IPFS Companion 2.2.0 brings window.ipfs to your Browser
#6Dat+Beaker is way ahead of IPFS in tooling, developer mindshare, consumer friendly UI, etc. With $250 million it's pretty shocking they don't seem more worried/focused on that.
Interestingly I've heard of IPFS many many times and this is the first I've heard of Dat+Beaker. Do you have a starting point you suggest to get an idea of what it is or does?
Here are the official websites of the Dat Project and Beaker Browser:
https://datproject.org https://beakerbrowser.com
And a short video for Beaker: https://www.youtube.com/watch?v=U2B9mwRFE8U
Re: IPFS Companion 2.2.0 brings window.ipfs to your Browser
#7How do I know that the embedded mode works? It says "IPFS resource loaded via Public Gateway".
I think you can click "switch to local node" or something like that. At least that's what I did with my external gateway and it worked and started to redirect locally.
Re: IPFS Companion 2.2.0 brings window.ipfs to your Browser
#8Dat+Beaker is way ahead of IPFS in tooling, developer mindshare, consumer friendly UI, etc. With $250 million it's pretty shocking they don't seem more worried/focused on that.
Can dat be accessed without that browser? I haven't found something like the IPFS node, and that's what made me not want to run dat.
Also, ZeroNet seems more advanced than both in terms of things that actually work today.
Re: IPFS Companion 2.2.0 brings window.ipfs to your Browser
#9How do I know that the embedded mode works? It says "IPFS resource loaded via Public Gateway".
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/...
Re: IPFS Companion 2.2.0 brings window.ipfs to your Browser
#10Dat+Beaker is way ahead of IPFS in tooling, developer mindshare, consumer friendly UI, etc. With $250 million it's pretty shocking they don't seem more worried/focused on that.
How about adoption, e.g. Dat+Beaker vs IPFS+existing browser? Arguably, for these use cases, adoption matters more than all of the other items combined.