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