 I'm going to present what I've been hacking on for the last couple of weeks. It's called Web Transport. Web Transport is a new protocol developed by the ITF in the W3C. Conceptually, it's basically like web sockets, but over quick. So it gives you all the nice advantages that Quik has stream multiplexing at the transport layer, so I'm ahead of line blocking. It gives you a faster handshake. It gives you better hold punching success rates. It gives you an advanced loss recovery and congestion control and all the reasons why we love Quik. But this is not the reason I'm excited about Web Transport, actually. The reason I'm excited about Web Transport is because it allows us to do things that Web Sockets didn't allow us to do. And the reason for this is that the browser handles Web Transport different from Web Sockets. In Web Sockets, the browser always wanted to see a real TLS certificate. So a TLS certificate that was signed by a certificate authority, for example, Let's Encrypt. And this also works in Web Transport, but there's another option. It's called the server certificate hashes. And basically what it does, you can tell the browser, accept a certificate that has a certain hash. And then the browser performs the TLS handshake, looks at the certificate. And if the hash of the certificate matches, it will accept that one. So this is great for LIP2P, because we were never able to get TLS certificates for all of our LIP2P nodes. But shipping around the hash, that's totally something we can do. So I started programming. I have this Web Transport Go library now. It's still a work in progress. It builds on our QuickStack on QuickGo. And it can do basic things now. And I'm going to show you now. So let's just start up the server. And one thing to keep in mind here, I will now go to example.com, which is mapped to localhost. The reason is that Chrome, for some reason, refuses to do QuickConnections to localhost. So you have to map it internally to some kind of domain name. And then you can establish a QuickConnection. So we are just going to use the web developer tools. And first we'll try to establish a connection. Oh, and this is very small. And let me, yes. OK. Try to establish a Web Transport connection to example.com slash web transport, which is the server here at localhost. So what happens? We get a quick protocol error because the certificate is unknown. Now we can, this is because we just used the URL. We didn't pass in the hash anywhere. So now let's use the hash of the certificate here. So now we're telling the browser that this hash is OK and pass in the server certificate hash's option. Tell it that the algorithm is a SHA256 and the value is what we just entered here. By the way, I just wish that somebody came up with a solution to have a self-describing hash function. Somebody should really do that. So now we have a web transport connection. It works. Let's go one step further and actually use that connection so we can open a stream on this connection and then send something. Let's say we send a hello world and there we go. So this works now. This is pretty cool. I'm pretty excited about this. If you think that this could be useful for your project, that you would want to use this, please get in touch.