WEBVTT 00:00.000 --> 00:13.400 Thanks to everyone for coming here and for looking at this, so I'm very happy to be here to 00:13.400 --> 00:15.280 present this ID to you. 00:15.280 --> 00:20.400 So it's kind of like a very different ID from what you saw before. 00:20.400 --> 00:25.000 I guess that's a pretty different way of doing things like IPFS or stuff like that. 00:26.000 --> 00:29.600 I don't have an academic background or I'm not a researcher. 00:29.600 --> 00:38.600 I'm really just a hacker and yeah, I enjoy building things and having people to use these things. 00:38.600 --> 00:42.000 So that's what I try to do here and what I want to show you. 00:42.000 --> 00:47.800 So just to note first is that in the abstract, I mentioned a lot of things I wanted to talk about, 00:47.800 --> 00:49.800 but we don't have a lot of time. 00:49.800 --> 00:53.800 So all this stuff about ethics and legal, I want to go for it. 00:53.800 --> 00:57.400 But if you want to talk about it, please ask the question at the end. 00:57.400 --> 01:04.400 There will be enough time at the end to talk about any specific topic you want to talk about that. 01:04.400 --> 01:08.400 So I will just say a few things about myself, but I'm here to talk about that. 01:08.400 --> 01:13.000 But I started coding pretty young. 01:13.000 --> 01:16.200 I was 11 years old and it was in the late 90s. 01:16.200 --> 01:18.200 And at that time the internet, that was this. 01:18.200 --> 01:21.400 I don't know if you remember that, but that's how we were looking at internet. 01:21.400 --> 01:23.800 It was like we could serve in the internet. 01:23.800 --> 01:25.600 It was revolutionary. 01:25.600 --> 01:29.200 And I learned like most of the things I know about software engineering. 01:29.200 --> 01:35.400 I learned from people, very generous people on a recipe that helped me to learn these things. 01:35.400 --> 01:40.000 And it was really about exchanging ideas, but other exchanging data. 01:40.000 --> 01:46.200 And there was, for me, a whole revolution around peer-to-peer data exchange. 01:46.200 --> 01:49.200 And really, I missed those days. 01:49.200 --> 01:53.000 And when I looked at internet right now, I'm pretty sad, 01:53.000 --> 01:55.000 because I see many of you, many of you, 01:55.000 --> 01:58.200 they spend time doing strolling on their phone. 01:58.200 --> 02:03.000 And I think, for me, it became like, I mean, the way I look at it is that people, 02:03.000 --> 02:05.000 they are enslaved by recommendation system. 02:05.000 --> 02:06.200 This is this neural network. 02:06.200 --> 02:08.800 It creates this fees of recommendation. 02:08.800 --> 02:10.200 It can be in social network. 02:10.200 --> 02:13.800 It can be on any website to consume. 02:13.800 --> 02:17.400 And they actually manipulate us in deep ways. 02:17.400 --> 02:20.600 And I think people start to realize that more and more. 02:20.600 --> 02:22.000 I mean, I hope. 02:22.000 --> 02:23.400 So personally, I don't like that. 02:23.400 --> 02:25.600 I think it's really fucked up. 02:25.600 --> 02:26.600 And I don't want to use it. 02:26.600 --> 02:29.200 So I try to find alternatives. 02:29.200 --> 02:30.600 So I don't want the internet. 02:30.600 --> 02:34.800 Now I want, I call as a judge of the interwebs. 02:34.800 --> 02:40.000 So it's not like the web free for five, because I think that's bullshit as well. 02:40.000 --> 02:45.000 People are really pessimistic before about hacking the browser. 02:45.000 --> 02:46.200 I think this is wrong. 02:46.400 --> 02:51.000 I think we should not let the stack giants dictate how the web should be built. 02:51.000 --> 02:55.600 I think we should not let this crypto bro dictate how we should deal it, 02:55.600 --> 02:57.000 because they don't know. 02:57.000 --> 02:58.600 We did it back in a days. 02:58.600 --> 03:01.600 I mean, I'm not talking about the internet protocol, right? 03:01.600 --> 03:04.600 But the web, this is something that was built by hacker. 03:04.600 --> 03:05.800 And we can still do it. 03:05.800 --> 03:09.400 I don't see why we wouldn't be able to do it. 03:09.400 --> 03:15.800 So I think the door project did something pretty amazing to show us a good interface 03:15.800 --> 03:18.400 to expose to the people. 03:18.400 --> 03:21.000 And that's by building a web browser. 03:21.000 --> 03:24.400 So what I'm going to show you is a fork of the door browser. 03:24.400 --> 03:31.600 More specifically, it's a fork of Melva browser. 03:31.600 --> 03:33.600 And I try to demo that on the Wi-Fi. 03:33.600 --> 03:37.400 So before the Wi-Fi was working, but it's a real demo. 03:37.400 --> 03:39.200 So bad things can happen. 03:39.200 --> 03:41.800 I hope they won't happen. 03:41.800 --> 03:43.600 I just pre-do not know that the application. 03:43.600 --> 03:52.000 So you can get it right now if you go on a coupad.net. 03:52.000 --> 03:56.600 I just finished building it like yesterday. 03:56.600 --> 03:57.400 So it's brand new. 03:57.400 --> 03:58.400 You can try it now. 03:58.400 --> 03:59.600 You might destroy the network. 03:59.600 --> 04:03.600 And then I won't be able to do my demo, but it doesn't matter. 04:03.600 --> 04:05.400 So if you try it, let me know if you have an issue. 04:05.400 --> 04:08.000 It should be working on any Linux operating system. 04:08.000 --> 04:12.000 Later, they will be for our operating system, but for now that's it. 04:12.000 --> 04:17.400 So just to say, if you want to try, you can go on a coupad.net. 04:17.400 --> 04:19.200 And you have linked to the source code. 04:19.200 --> 04:20.400 It's not yet an radical. 04:20.400 --> 04:24.000 I mean, I add some issues, but I think some people from a radical are here today. 04:24.000 --> 04:27.600 You can download the tar against zip. 04:27.600 --> 04:30.800 That's the instruction from the command line, 04:30.800 --> 04:33.800 but you can just right click and hit and run it like a DD here. 04:33.800 --> 04:38.000 And if you want this mailing list and our community stuff, anyway. 04:38.000 --> 04:41.800 So once you start the browser, you're welcome with that. 04:42.800 --> 04:44.400 The about page. 04:44.400 --> 04:48.000 And here you have a link that's encouraged you to enter the interwebs. 04:48.000 --> 04:50.000 So as you can see, this is a weird link. 04:50.000 --> 04:53.000 And for now, we'll be really practical and going to it. 04:53.000 --> 04:57.200 And if I have issues and slow down, which is not the case if everything is working, 04:57.200 --> 04:59.200 I will talk about everything. 04:59.200 --> 05:01.400 So this is the first page of the new interwebs. 05:01.400 --> 05:02.800 This is the first one. 05:02.800 --> 05:05.400 And I can have music. 05:05.400 --> 05:08.000 I'll set a net. 05:08.000 --> 05:09.600 Hopefully. 05:09.800 --> 05:11.400 We didn't download everything yet. 05:11.400 --> 05:13.800 So let's look at the jargon file first. 05:13.800 --> 05:18.000 The jargon file is a PDF file that is downloading. 05:18.000 --> 05:21.000 So I will wait and see if everyone should eat it happen. 05:21.000 --> 05:28.000 So in the meantime, what I wanted to say is that I tried to take a different approach. 05:28.000 --> 05:29.600 Everyone talked to you about the cloud. 05:29.600 --> 05:31.400 But what I want to talk to you is the Granary. 05:31.400 --> 05:34.400 So we'll explain what I mean by Granary later. 05:34.400 --> 05:38.200 So this is a really old file that evolved over time. 05:38.200 --> 05:41.200 It's a dictionary for a cyberpunk. 05:41.200 --> 05:45.600 So if you don't know what cyberpunk means, because you hear all these cool kids talking 05:45.600 --> 05:50.400 about it, you can access the interwebs and get there and look at it. 05:50.400 --> 05:52.600 If you look at the address bar, it's a bit funky. 05:52.600 --> 05:54.600 So why is it funky? 05:54.600 --> 05:58.200 Because I mean, you can embed movies like this one. 05:58.200 --> 06:01.200 Elephant dreams is the first open movie. 06:01.200 --> 06:04.200 It was made entirely with a console software. 06:04.200 --> 06:08.000 I mean, 10 years ago, since then, Blender did many better movie. 06:08.000 --> 06:10.600 But I just took the first one, I think it was funny. 06:10.600 --> 06:15.800 So that is also embedded on that first interwebs page. 06:15.800 --> 06:21.000 And then we can see, we can have a link that will directly to that movie. 06:21.000 --> 06:25.200 So if you look at the address bar, here we have that long hash. 06:25.200 --> 06:27.200 Then we have this domain name. 06:27.200 --> 06:29.200 And then here we simply add the name of the file. 06:29.200 --> 06:34.000 And it's just streaming directly in the web browser, right? 06:34.000 --> 06:39.400 So now, what it is about this address and these links. 06:39.400 --> 06:44.600 So I think one way to show you exactly what it is, it's to build one of these links by hand. 06:44.600 --> 06:50.600 So we can go on this great website, which I think does not need an introduction, right? 06:50.600 --> 06:52.400 And we can search for something. 06:52.400 --> 06:56.200 I mean, I don't know what could we download right now. 06:56.200 --> 06:58.200 Well, I use a resource right. 06:58.200 --> 06:59.200 They are great. 06:59.200 --> 07:01.800 It's what everybody goes there to download stuff, right? 07:01.800 --> 07:04.000 So let's do that. 07:04.000 --> 07:05.200 Let's take a popular one. 07:05.200 --> 07:09.200 So that increases the chance of my demo to be working. 07:09.200 --> 07:12.800 So here, on the paradigm, you get what is called the info hash. 07:12.800 --> 07:16.800 So this is a hash of the name of the termans, all the metang from, 07:16.800 --> 07:22.200 you know, not all of the information, but then the hash of the contents, right? 07:22.200 --> 07:24.000 This is a way to identify the termans. 07:24.000 --> 07:25.400 So I copy that. 07:25.400 --> 07:26.400 I open a new tab. 07:26.400 --> 07:30.000 I do HTTP as colon slash slash. 07:30.000 --> 07:31.600 I put the info hash. 07:31.600 --> 07:36.000 I say dot terrons dot alt slash. 07:36.000 --> 07:40.400 And there, I can go at the bottom of the page where you see the list of files. 07:40.400 --> 07:45.000 In this case, there's only one file. 07:45.000 --> 07:46.000 Oops. 07:46.000 --> 07:47.600 I have such a big mouse. 07:47.600 --> 07:48.600 I don't know to use it. 07:48.600 --> 07:51.600 Here it is. 07:51.600 --> 07:54.000 So now I just added at the end of the path. 07:54.000 --> 07:56.000 I do enter. 07:56.000 --> 08:03.600 And then I have to be a bit patience because, I mean, the first turn to access for 08:03.600 --> 08:05.800 the first page is hosted by me. 08:05.800 --> 08:11.000 So I did optimize the configuration of my nodes to be like really efficient for 08:11.000 --> 08:12.000 this kind of case. 08:12.000 --> 08:14.000 But here, we have to wait a few seconds, right? 08:14.000 --> 08:15.800 So now it's starting. 08:15.800 --> 08:18.000 And I propose that I leave it running. 08:18.000 --> 08:24.000 Why, oops, shouldn't do the same mistake before which is shutting down. 08:24.000 --> 08:26.000 So we don't see perressing now. 08:26.000 --> 08:29.000 And that's just one mismatch between the abstraction, right? 08:29.000 --> 08:33.000 Because a torrent don't know things in parallel, right? 08:33.000 --> 08:36.000 I won't explain everything about a torrent goes. 08:36.000 --> 08:41.000 But here, I can only send the bytes in a continuous manner. 08:41.000 --> 08:42.000 So I need to wait. 08:42.000 --> 08:46.000 So probably right now it's downloading a lot of stuff. 08:46.000 --> 08:49.000 We can verify that by running, 08:49.000 --> 08:53.000 if top and the host. 08:53.000 --> 08:59.000 And yeah, you see, I just started if top and there's already 36 megabytes transfer. 08:59.000 --> 09:03.000 So we will come back to this later. 09:03.000 --> 09:08.000 And now I will continue with the rest of the presentation. 09:08.000 --> 09:13.000 So I mean, I guess, like most of you are beginning what bit torrent is. 09:13.000 --> 09:15.000 I mean, I don't need to raise your hand. 09:15.000 --> 09:17.000 I think most people know what it is. 09:17.000 --> 09:19.000 Just briefly how it works. 09:19.000 --> 09:22.000 You are a peer in a peer-to-peer network. 09:22.000 --> 09:26.000 And using that protocol, you can exchange files, right? 09:26.000 --> 09:29.000 So usually what you do, I mean, that's one way of doing things. 09:29.000 --> 09:31.000 There's another way I will discuss more later. 09:31.000 --> 09:37.000 But one way to find other peers that contain the data you need is to actually contact what is called a tracker. 09:37.000 --> 09:39.000 You can use a UDP or HTTP. 09:39.000 --> 09:43.000 And then, so you get an over peer and you can start transfer data with it. 09:43.000 --> 09:46.000 So this is basically how bit torrent is working. 09:47.000 --> 09:49.000 And now this is what you just saw, okay? 09:49.000 --> 09:54.000 But now I want to tell you about the future of what I'm building because this is like pretty simple. 09:54.000 --> 09:57.000 And I see, I mean, it was a quite a piece of work to get it working. 09:57.000 --> 10:03.000 But initially I got to put a type of this working like six hours just by hacking existing libraries. 10:03.000 --> 10:05.000 But then I wanted to read nicely. 10:05.000 --> 10:10.000 And this means using lip torrents because it torrents as far as I can see is the best implementation. 10:10.000 --> 10:11.000 And that took more time. 10:11.000 --> 10:14.000 Then I wanted to embed it in a web browser and that took more time. 10:14.000 --> 10:16.000 But I mean, the basic idea is pretty simple. 10:16.000 --> 10:25.000 But I don't think it's enough for our new interwebs because let's go back to the core issue, which is a privacy and stuff like that. 10:25.000 --> 10:31.000 So first of all, like thanks a lot to the Tor project for building such a great thing. 10:31.000 --> 10:37.000 And what they do is that there is a torrent network, but there's also the base browser, which is by Milvad, which I'm using here. 10:37.000 --> 10:41.000 The advantage of that web browser is that it's prevent finger printing. 10:41.000 --> 10:45.000 So maybe you saw before they were like the letter boxing and stuff like that. 10:45.000 --> 10:47.000 They really spent a lot of time in this. 10:47.000 --> 10:50.000 So in the design I want to go there. 10:50.000 --> 10:54.000 I want the browser to be able to operate in two different mode. 10:54.000 --> 10:58.000 One is a public and one is a private mode. 10:58.000 --> 11:02.000 So now let's talk about what I want the public modes to be. 11:03.000 --> 11:07.000 So currently, it is bitterrants and internet to get the data. 11:07.000 --> 11:10.000 And then if you access the normal internet, it is bitterrants. 11:10.000 --> 11:12.000 But what I want to do is that I want to use the Tor network. 11:12.000 --> 11:17.000 It's actually pretty easy things to do because I'm already integrated with the whole Tor project stack. 11:17.000 --> 11:22.000 I can just add the Tor demon and then I can use as a proxy for my own proxy. 11:22.000 --> 11:26.000 Because my masterfocus as a proxy in the web browser. 11:26.000 --> 11:33.000 So while doing that, it's actually really important for privacy. 11:33.000 --> 11:45.000 Because on the right, people that are on the right, they don't know what is your tolerance. 11:45.000 --> 11:48.000 Activity is so they cannot like to relate it. 11:48.000 --> 11:53.000 And people that see you using Torons, they don't know what is your web activity. 11:53.000 --> 11:54.000 They cannot color it. 11:54.000 --> 11:57.000 So basically people that are selling advertisement, they cannot know things about you. 11:57.000 --> 12:00.000 This does not prevent state actor. 12:00.000 --> 12:03.000 It's a three-letter acronym agency to know what you're doing. 12:03.000 --> 12:06.000 Because they can observe the complete stuff. 12:06.000 --> 12:14.000 So this is good to like a desktop application for people that can use Torons in region that are not heavily censored, 12:14.000 --> 12:18.000 or that there are a few issues like that. 12:18.000 --> 12:24.000 So we can also imagine like I was talking about a web browser, but this could be also a web app. 12:24.000 --> 12:27.000 Sorry, an appliance for like a Raspberry Pi. 12:27.000 --> 12:30.000 And you could have at home like working as a seat box. 12:30.000 --> 12:34.000 And that's when the concept of Granary, you know, I was explaining before. 12:34.000 --> 12:41.000 We'll start to make sense, but I will do more details about that later. 12:41.000 --> 12:45.000 So then that is for the public peer. 12:45.000 --> 12:54.000 But now let's say you're someone in a country like Iran, or I don't know, in places where you don't want people to know what you're doing with internet, 12:54.000 --> 12:58.000 which is a totally for concern in my opinion. 12:58.000 --> 13:04.000 You really don't want to have any public Toronto activity, especially the DHT. 13:04.000 --> 13:10.000 DHT is another way to find over peers, but it's using a decentralized data structure. 13:10.000 --> 13:14.000 So in that case, when you install the browser, you put it in a private mode. 13:14.000 --> 13:23.000 And in that mode, everything you do is going through tour, which is good because it's proven to people from knowing what you're doing, 13:23.000 --> 13:30.000 but that has some limitation. Like for example, you're not, it's not possible for you to distribute new contents to bootstrapped. 13:30.000 --> 13:35.000 I mean, you can distribute new content, but you cannot bootstrapped a swarm if there's no one that is active. 13:35.000 --> 13:41.000 That's a big technical, but for people that know about Bitcoin and stuff like that, hopefully it makes some sense. 13:41.000 --> 13:55.000 So now, what is important to remember is that the tour project, the tour demand, it only supports TCP protocol. 13:55.000 --> 14:00.000 There's a lot of stuff going on in UDP with Bitcoin. 14:00.000 --> 14:05.000 So now there's the added secret that I kind of like overlay network. 14:05.000 --> 14:12.000 Well, the public peers, they act as proxies for the DHT and the UDP director. 14:12.000 --> 14:17.000 For the HTTP trucker, it's fine, right? The private pair can connect it through tour. 14:17.000 --> 14:28.000 So I mean, I think proxies, but it's like in the tour terms, it would be a relay, but I think it's better not to use the same term because I also used tour, so it would be super confusing. 14:28.000 --> 14:38.000 So I call them proxies. The constraint they have is that you cannot announce yourself. They only forward a readily queries. 14:38.000 --> 14:48.000 But they basically, they serve as a bridge for people that are running a private node to find peers and, you know, don't know, don't know, tolerance. 14:48.000 --> 14:54.000 And I think it's something else to see about this. Oh yeah, the onion character. 14:54.000 --> 15:03.000 It's like currently in the Bitcoin protocol, you act change IP address when you connect to a peer, right? When you act change in the swarm, the address. 15:03.000 --> 15:08.000 Usually you get this IP address from the tracker or from the DHT. 15:08.000 --> 15:17.000 But there's something in Bterons, which is formalized, which is an implemented in much in most of the clients, which is called the peer actions protocol. 15:17.000 --> 15:21.000 So when two peers they connect together, they exchange what they know about the swarm. 15:21.000 --> 15:26.000 This is really cool because it allows people that use only the DHT to know about peer from the tracker. 15:26.000 --> 15:34.000 Without connecting to the tracker, it's just a way to disseminate, you know, the member of the swarms using peer to peer. 15:34.000 --> 15:40.000 So the idea is to implement something like that, but for onion addresses. So this way people are running private peer. 15:41.000 --> 15:45.000 They can behave like an active Bterons node. 15:45.000 --> 15:49.000 Through, I mean, node that run the software stack and building. 15:49.000 --> 15:54.000 So far, everything I described is backward compatible with Bterons. 15:54.000 --> 15:57.000 You know, I just show you, right? We were broadcasting like normal terrons, right? 15:57.000 --> 16:01.000 But I know what I'm showing here with that onion thing is specific. 16:01.000 --> 16:06.000 It's still backward compatible, but there's like an extension, and if the extension is implemented, 16:06.000 --> 16:14.000 this allow private peers to join the swarm actively. 16:14.000 --> 16:19.000 And that's it for that. So there's a lot of stuff enough stuff to do. 16:19.000 --> 16:22.000 I just presented you like address crash, the surface here. 16:22.000 --> 16:25.000 There's like a lot of stuff that can be done. 16:25.000 --> 16:31.000 There's research to be done. There's things to build, and there's many way to contribute, I think. 16:31.000 --> 16:38.000 Probably then things that are common with people doing IPFS, people doing like working on other projects. 16:38.000 --> 16:41.000 So first, I think a concept that is really interesting with that. 16:41.000 --> 16:45.000 And now I'm going back to the idea of Granary versus the Cloud. 16:45.000 --> 16:48.000 We could use the social network to decide. 16:48.000 --> 16:54.000 Because once you have something in your browser catch, you're going to see that. 16:54.000 --> 16:58.000 So anything you browse, unless you just like a private node, like to hide your ass, 16:58.000 --> 17:02.000 because you're going on website, you don't want your family or people to know. 17:02.000 --> 17:07.000 Otherwise, that would be like in your browser catch, and that would be seated to the rest of the world. 17:07.000 --> 17:12.000 So the idea then is that you could receive a request from a friend that tells you, 17:12.000 --> 17:16.000 hey, would you be okay to store, to see the stuff I'm the author. 17:16.000 --> 17:20.000 And then that could be like this concept of Granary versus talking about. 17:20.000 --> 17:25.000 So you could have like authorization, and you know, add people from a social circle. 17:25.000 --> 17:30.000 In your Granary, and that Granary is like a virtual space that exists when you run the browser, 17:30.000 --> 17:35.000 or where you run like a Raspberry Pi at home, or, you know, you can imagine renting a seat box anywhere. 17:35.000 --> 17:40.000 And you will let people that you trust store data there. 17:40.000 --> 17:46.000 There's other some research around like, there's, I think, stuff to formalize, 17:46.000 --> 17:48.000 and way to improve the Bitcoin protocol. 17:48.000 --> 17:53.000 Because unlike the web browser, we don't have to ask Google if they okay with it. 17:53.000 --> 17:56.000 We can just do it, you know, that's the way we do it with Bitcoin. 17:56.000 --> 17:59.000 It's always been done like that, and we continue to do it like this. 17:59.000 --> 18:05.000 I think one thing which is important is to have content addressable storage, 18:05.000 --> 18:08.000 which is something IPFS is doing, but you cannot do it with a bit of rent. 18:08.000 --> 18:11.000 I guess at the time, Bitcoin was designed. 18:11.000 --> 18:14.000 It was not really a big trend, so, you know, it was not very well known, 18:14.000 --> 18:17.000 but I think being able to do content addressable storage will be nice. 18:17.000 --> 18:21.000 It can be easy by adding a new name space in the DHT. 18:21.000 --> 18:27.000 And basically, you link the content hash to the info hash, the hash we saw before. 18:27.000 --> 18:32.000 And by having that data structure, which is, I think, relatively simple to implement and to formalize, 18:32.000 --> 18:34.000 and then we can have content addressable storage. 18:34.000 --> 18:36.000 Why, you know, why having that? 18:36.000 --> 18:39.000 So, one simple thing we can do is that we could compose a tournament content. 18:39.000 --> 18:42.000 You could have one tournament that has a content of another tournament. 18:42.000 --> 18:45.000 Let's imagine you take all the recordings of the conference of this year. 18:45.000 --> 18:50.000 You put them in a tournament, but you also want a tournament with every year, you know. 18:50.000 --> 18:56.000 Then you can do that with recordings of first them, we've got like wasting space. 18:56.000 --> 19:01.000 This will be also nice to, I mean, if you want to know more, ask me questions, 19:01.000 --> 19:02.000 and I will be talking more about that. 19:02.000 --> 19:05.000 There's like a lot of nice properties about that. 19:05.000 --> 19:10.000 One other really interesting area is about naming and TLS. 19:10.000 --> 19:13.000 So, I won't go too much in details, because there's other people talking about TLS. 19:13.000 --> 19:18.000 Today, like Jeremy runs from a name kind, and they know that subject better than me, 19:18.000 --> 19:21.000 but basically I have kind of like the same concern as them. 19:21.000 --> 19:23.000 Basically just think about that. 19:23.000 --> 19:27.000 Here, I show you a tournament contents, right? 19:27.000 --> 19:32.000 So, it's actually completed. You have your Linux, I don't know. 19:32.000 --> 19:38.000 And you can see that it's using HTTPS, right? 19:38.000 --> 19:44.000 And now you should consider, so what happened if the content of a tournament, 19:44.000 --> 19:51.000 you have to do a HTTP request to an API on another domain, right? 19:51.000 --> 19:54.000 You don't want to, so it's like, we have cross-site scripting, 19:54.000 --> 19:58.000 but now we are talking about cross-terrants, slash-site scripting, right? 19:58.000 --> 20:02.000 This open a wall kind of forms of like things that we have to do proper. 20:02.000 --> 20:04.000 Right? No, this is just an alpha version. 20:04.000 --> 20:06.000 So, you know, use it as your own risk. 20:06.000 --> 20:11.000 Be mindful, this is tolerance, you know, if you, if you, is it properly? 20:11.000 --> 20:13.000 But really, I think we should think about that. 20:13.000 --> 20:17.000 And we should think about how we give certificate right now, you know, 20:17.000 --> 20:21.000 because it's not ideal in my opinion, but that this people are working on that. 20:21.000 --> 20:24.000 And hopefully we can, you know, collaborate to thank good solution. 20:24.000 --> 20:26.000 And I think we can just do it and implement it. 20:26.000 --> 20:29.000 We don't have to wait for the giants to agree with us, 20:29.000 --> 20:31.000 because they don't have the same concern. They don't care. 20:31.000 --> 20:36.000 But I don't, you remember the Claude Fair outage, like, why do I go? 20:36.000 --> 20:39.000 Yeah? So, that wouldn't happen if you use something like that. 20:39.000 --> 20:42.000 So, I don't see why we all have to use Claude Fair, you know, 20:42.000 --> 20:44.000 to do a quantum distribution. I think that's ridiculous. 20:44.000 --> 20:46.000 And I hope that you realize that and that day. 20:46.000 --> 20:50.000 Because there was so many stuff that were down, you know, and it's really a shame. 20:50.000 --> 20:53.000 When we actually have the technology to do things differently. 20:53.000 --> 20:55.000 So, that is really my main motivation. 20:55.000 --> 21:00.000 But as one of my motivation is that I think anybody that have a device that can connect to internet 21:00.000 --> 21:05.000 with a relatively good app time and bandwidth should be able to expose the website, okay? 21:05.000 --> 21:09.000 But one of the big issues, because here, I mean, I just did it, right? 21:09.000 --> 21:12.000 But you saw the name of the website. It's not so friendly. 21:12.000 --> 21:16.000 So, we can integrate that with normal DNS, but you still have to pay for DNS. 21:16.000 --> 21:18.000 We can integrate that with name coin, which is great, 21:18.000 --> 21:20.000 but you still have to pay for name coin. 21:20.000 --> 21:25.000 So, I think there is space for another name service, which is complementary to this, 21:25.000 --> 21:32.000 which is a globally unique, but hard to remember, but locally, you know, easy to remember. 21:32.000 --> 21:35.000 So, if you have a question about that, we can also discuss. 21:35.000 --> 21:40.000 One thing, last thing I mentioned in terms of research and development that I think is really interesting, 21:40.000 --> 21:43.000 is that here, I just show you static content, right? 21:43.000 --> 21:47.000 I guess that would be your first question, like, yeah, it's nice, but this is just static content. 21:47.000 --> 21:51.000 I mean, I would say, you can do a lot with static content, and if you do smart things, 21:51.000 --> 21:54.000 but then yes, I mean, how can you do a dynamic website with that? 21:54.000 --> 22:00.000 So, one of the way to design, I think, decentralized application with that, 22:00.000 --> 22:04.000 and it's not web free, right? We don't have to follow the stuff. 22:04.000 --> 22:08.000 It's to have like a web DHT API. 22:08.000 --> 22:14.000 So, it's an API that you have in the web browser, and you can put keys in a DHT, 22:14.000 --> 22:17.000 in a namespace, or retrieve keys from that namespace. 22:17.000 --> 22:21.000 And that namespace should be authenticated using certificate. 22:21.000 --> 22:25.000 So, again, we can go back to TLS and how we design this stuff. 22:25.000 --> 22:27.000 But I think that would be a big deal, because if we do that, 22:27.000 --> 22:31.000 then you can implement something like a social network using this, right? 22:31.000 --> 22:35.000 But that's far in the future, I think. 22:35.000 --> 22:38.000 And then, you know, of a contributor contribution funding, 22:38.000 --> 22:40.000 well, I'm doing that on my spare time. 22:40.000 --> 22:45.000 If you have many, I give it to the door project, because I think that's where the menu should go. 22:45.000 --> 22:49.000 But if you have really too much money, you can give it to us. 22:50.000 --> 22:53.000 This is the European sovereign tech fund. 22:53.000 --> 22:56.000 And, you know, that might sound like crazy, because that's a hacker thing, 22:56.000 --> 22:59.000 but I think it's really relevant to European sovereignty. 22:59.000 --> 23:01.000 Because, again, CloudFair. 23:01.000 --> 23:04.000 You know, CloudFair can manage the middle of you, 23:04.000 --> 23:06.000 but when they want, you know, do you realize that? 23:06.000 --> 23:08.000 It's important to realize that. 23:08.000 --> 23:13.000 I mean, CloudFair can actually pretend to be your website, if you use it. 23:13.000 --> 23:16.000 At any point, so you should remember it's an American thing, 23:16.000 --> 23:19.000 you can, like, you know, they can completely screw us. 23:19.000 --> 23:24.000 With this, you cannot, you know, it's something you can do that. 23:24.000 --> 23:26.000 So, I'm getting over time. 23:26.000 --> 23:29.000 I just want to thanks all the people behind this project, 23:29.000 --> 23:31.000 because we've all done, I wouldn't be here. 23:31.000 --> 23:34.000 Not only because of what they do, but the help they gave me, 23:34.000 --> 23:39.000 because they really were super helpful, especially the Tor project, 23:39.000 --> 23:41.000 people working on the Tor browser, people from Melva, 23:41.000 --> 23:43.000 that helped me with the build system. 23:43.000 --> 23:48.000 The bit around community, the name coin as a Jeremy around that help a lot. 23:48.000 --> 23:51.000 So, big thanks to all these people. 23:51.000 --> 23:55.000 A big thank you to the critical decentralized cluster for inviting me 23:55.000 --> 23:57.000 and making this festival. 23:57.000 --> 24:01.000 And finally, so this is my cat, because internet is made to exchange cats picture, 24:01.000 --> 24:02.000 I think, fundamentally. 24:02.000 --> 24:04.000 They just make us build that, right? 24:04.000 --> 24:07.000 So, I give the browser her name, which is a koopa. 24:07.000 --> 24:09.000 So, she said you should subscribe to the mailing list. 24:09.000 --> 24:12.000 You can see it on a koopa.net. 24:12.000 --> 24:16.000 I'm usually mostly on RSC, I'm old-style, old-fashioned, hacker, 24:16.000 --> 24:19.000 but I make the efforts to create a matrix room. 24:19.000 --> 24:24.000 So, you serve the interwebs and thanks a lot for your time. 24:24.000 --> 24:29.000 Thank you so much. 24:29.000 --> 24:31.000 We're going to have to pass on the Q&A, 24:31.000 --> 24:33.000 but if you'd like to ask for some questions, 24:33.000 --> 24:35.000 feel free to go ahead and find Koopa. 24:35.000 --> 24:39.000 And we'll go ahead and meet him off to the side here. 24:39.000 --> 24:42.000 I'm guessing he'll be around in the center for a little bit. 24:42.000 --> 24:43.000 Okay, awesome.