IPFS GUI and Browsers Weekly, 21 Apr 2020

Previous Meeting Next Meeting

⏯

youtube image

►

From YouTube: Brave 1.19 with Companion; DNSLink on subdomain gateways - IPFS GUI and Browsers Biweekly 2020-04-21

Description

Meeting notes: https://github.com/ipfs/team-mgmt/pull/1199/files

IPFS in Brave v1.19:
https://github.com/ipfs/in-web-browsers/issues/64#issuecomment-763016248

Subdomain Gateway explained:
https://docs.ipfs.io/how-to/address-ipfs-on-web/#subdomain-gateway

About IPFS GUI and Browsers Biweekly: https://github.com/ipfs/team-mgmt/issues/790

For more information on IPFS
- visit the project website: https://ipfs.io
- or follow IPFS on Twitter: https://twitter.com/IPFS

Sign up to get IPFS news, including releases, ecosystem updates, and community announcements in your inbox, each Tuesday:
https://eepurl.com/gL2Pi5

A

Okay, welcome to bi-weekly call gui and win in web browsers, which happened months ago last time, but maybe.

B

A

Old days um yeah, so we've been busy with a bunch of stuff but uh breaking the silence. I guess uh to give a full, quick demos of recent developments in the browser land, so I'll just jump straight to that and share my screen.

A

um So this is a brave browser and I got a demo about brave bit later, but first I wanted to show how we solved the final feature gap on public subdomain gateways gateways. So the problem with the public subdomain gateways was that maybe I'll illustrate it will be easier. So.

A

So a wikipedia mirror has dns links set up and if you just load the original domain name, which has dns link dns txt record with a content path to ipfs resource, it looks like a regular website. So the problem is: what happens if this original http server goes down? The copy is still on ipfs, but how do you get to it? So in the past you would go to ipfsio ipns right and you enter the domain name here.

A

Wow, that's a bit slow.

A

Right so that may take uh some time to load or not not sure why it's loading so far so slow uh anyway. This way you can load it from a public gateway. It will eventually fetch the content you want. The problem is uh this is path k based gateway and you don't get a oh yeah, so you don't get any original isolation.

A

Every website loaded this way will share cookies with ev. It will be stored in ipfsio origin, so every page share the same origin, which is bad, so we have subdomain gateways to solve the origin problem.

A

um However, the problem- maybe I will also illustrate so I'm using cloudflare gateway because they are running a current, stable version of go ipfs, which is a good illustration. So if you try to load.

A

It similar fashion from a subdomain gateway. I believe it will redirect you to a subdomain.

A

However, what happened? Now you see this tls error? It says that connection to site is not secure, and the problem is that the name of a domain of a tls certificate is not matching.

A

It's not matching this domain. The problem is that you've got more than a single level.

A

You can see there's one level here here is another level and there's the third one and the tls certs support wild cards. However, those wild cards are only for a single level, so we solve this problem uh in the patch landed in, go ipfs and it will be released with go ipfs 0.8.

A

However, we already run this patch on the web link gateway.

A

A

So if you load this this way, you can see it loaded fine, because we encode we inline domain names into a single dns label which is compatible with tls cells. So it's a tiny fix and probably most of people don't care about it. But it was the final missing gap between path-based gateways and subdomain gateways.

A

It's not something! We expect people to use often, but if you are a web browser developer or you if you are running a website- and you want to link to some mirrors, you can just link to other subdomain gateways this way and even if your original server is down for some reason, people will still be able to load dns link websites.

A

This way and what happened here is you can see my second update, which is native support for ipfs in brave, and this is brave 1.19, and here you can see, I loaded the public, subdomain gateway and brave automatically detected hey. This thing looks like ipfs resource.

A

Would you like brave to load it using a local, ipfs, node and there's this enable ipfs button?

A

And if I click that button brave will download, ipfs, daemon and start it and you will be able to load ipfs uris resources like this from a local gateway by brave, but I will not do that. Instead, I will show you a much easier onboarding. So you go.

A

Maybe here you go to settings and you go to extensions and you enable ipfs, companion.

A

It takes a moment, but here companion is installed.

A

And you can see, I already got my node running. However, that's my local ipfs desktop- and I wanted to screen- share this because probably most of people who are watching this are already running ipfs node. So this is not a standard flow, but probably will reduce a lot of confusion, so you can see I'm using external node. This is go ipfs running in docker. However, I can switch to node provided by brave.

A

And this will trigger the same prompt if I enable ipfs here it will download the demand and start it. It was fast because I got a fast gigabit fiber at my place. It probably won't be as fast for everybody most of people on the planet, but I'm lucky uh just you and you just need to be patient, and um here.

B

uh And there are, there are interstitial texts if you don't have immediate, fast internet. Like light all, does you'll see step one of three step. Two is three step: three. You will see that guided. I'm.

C

Pretty sure you can play youtube, slowed it down.

B

And you watch youtube.

A

Yeah. Apologies for that I I I could like figure it out a better demo but yeah, and what happens here is it's a regular ipfs node running. You can even go to web ui. uh It's right now, 0.7.

A

However, the cool thing about this is all auto updates of ipfs node will be automatically handled by brave, so you don't need to update it. They will take care of it and, what's cool is that if I go once.

A

Again, if I go to that website with dns link.

A

And if you have ipfs companion, it will automatically redirect you to native uri, so you don't need to do anything fancy now it just works. I believe it's scheduled to hit a stable channel today. So probably when you are watching this, it's already in the production version of brave, if not stay, tuned or play with brave, beta or brave nightly, that's the demo, we'll probably add links to some blog posts in the uh in notes, um but right now it's pre-released. So that's all I wanted to show you.

A

Any last moment topics we want to discuss. We probably have more uh things to discuss next time. We see each other in two weeks, uh maybe something pinning service related or maybe not. Who knows?

A

I assume we don't have anything on an agenda so I'll stop my recording now I.

B

Think we're good yeah.

A

B

Out there on internet land see you in two weeks, one hour later than usual. The new usual is one hour later than the old usual yeah.

A

That's me, I move, I just moved the item, this call in the community calendar, but I did not update any description on our github issue, so I will do that.

B

You're gonna cool yeah. I will I will take that off my list. Thank you. Yeah.

A

Alright see you in two.

A