WEBVTT 00:00.000 --> 00:12.520 I'm a random teacher in IOT. I had the chance to work with Arduino in the past. Now, I 00:12.520 --> 00:21.520 collaborate with entity developing open hardware in GenCOSI Studio. But I teach and do interactive 00:21.520 --> 00:27.400 physical computing stuff and basically try to give meaning to technology with surrounds 00:27.400 --> 00:32.760 us and most of the time. Unfortunately, it doesn't take in account our point of view 00:32.760 --> 00:39.680 to our technology. Events like PhosDem promote a very clean and mature approach towards 00:39.680 --> 00:46.000 technology. So I really thank PhosDem to accept me here. When I applied, I thought I would 00:46.000 --> 00:51.720 be given a very little room, but then they ended up giving this very big room. So, wow, thank 00:51.720 --> 00:59.720 PhosDem. I love you. I tend to work with IOT. So, I ended up working with the smart city 00:59.720 --> 01:08.160 concept at the beginning. It was, for the domotic, it was most of it. Wi-Fi, Bluetooth, for 01:08.160 --> 01:15.800 wider ranges, Zigbee, or cellular. But then it came Laura. So, I started dealing with Laura 01:15.840 --> 01:22.120 kind of long ago. When anything's happening in the last years, at some point, it was 01:22.120 --> 01:27.680 a crypto based on Laura called L.U. My don't like to remember. Nowadays, we are kind 01:27.680 --> 01:33.240 of in a mature moment of Laura and a lot of interesting things are happening. So, part 01:33.240 --> 01:37.480 of these things are part of this presentation, which is not that technical. I mean, at the 01:37.480 --> 01:42.200 end, we are getting a little bit technical. But it's more of a storytelling that explains 01:42.280 --> 01:48.080 to the average Joe. It is an horrible way to explain it. All my personal. The average 01:48.080 --> 01:55.800 Joe, what are we talking about when we talk about the Meshivers? I often recall, to my students, 01:55.800 --> 02:02.640 this moment, back in the days, almost 100 years ago, when Guillermo Marcónia allowed the 02:02.640 --> 02:10.280 pulp of the time to switch on the crystal of the interior. I think it's one of the earlier 02:10.280 --> 02:14.840 examples of IOT because it was a push-button in Rome, the trigger crystal of the interior. 02:14.840 --> 02:19.960 Actually, if you go to crystal of the interior, there is a statue of Marcónia because of 02:19.960 --> 02:26.440 this. And I imagine the people of Rio, seeing switch. I mean, if they were told that this 02:26.440 --> 02:32.040 was switched off by Pope, but the Pope, I guess, it was all over Globu and the main newspapers 02:32.040 --> 02:38.680 in Rio at the time. They must have said that there was a, what they was to sell. It was magic. 02:39.240 --> 02:46.440 So most of this presentation actually involves the concept of this technology that is always 02:46.440 --> 02:53.400 getting more inside our life. And most of the time we don't understand it, that ends up being 02:53.400 --> 03:00.200 magic. It is to me that I'm into technology. I wonder, how is it for an average person that 03:00.200 --> 03:08.600 is not into all of these things? I often recall this moment we are leaving as a moment of, we are 03:08.680 --> 03:15.320 unaware of being in a cyberpunk moment, in a cyberpunk life, in a cyberpunk era. Actually, 03:15.320 --> 03:21.400 there are many shades of cyberpunk. I often go to Shenzhen, it's ten years, I go to Shenzhen, 03:21.400 --> 03:27.160 and actually Shenzhen shifted to be a cyberpunk city. Now, it became a solar punk city. 03:28.760 --> 03:35.640 Yeah, I mean, there are many different levels of good and bad we can experience, but the main 03:35.720 --> 03:44.280 concept is that we are experiencing an ever-going offering technology. We have seen most of us have 03:44.280 --> 03:50.280 seen the videos of CES, of the Sierra Las Vegas with all these robots, brings glasses, 03:51.320 --> 03:57.960 whatever robots doing all sorts of things, vehicles, flying vehicles, whatever. So we are in this age 03:57.960 --> 04:04.920 of super high offering technology, but the level of life is lower in down, at least in my 04:04.920 --> 04:12.520 home country, which is easily, but I suspect it's kind of a common trend. And this is actually what 04:12.520 --> 04:21.400 is this concept about a cyberpunk. So many are we living in a cyberpunk, this is not a 04:23.640 --> 04:31.400 stupid question in my opinion. So the technology is outpacing social development. There is 04:31.480 --> 04:39.960 an ongoing inequality. Corporations are becoming more relevant than states, not even just that, 04:39.960 --> 04:47.320 but single people own more money than states, as we speak. It's not that it's going to happen. 04:47.320 --> 04:52.280 It's like it's happening since several years now, and there is an increasing feeling of 04:53.240 --> 05:01.000 obsolescence among people. So we are less intelligent than several AI's we can chat with. 05:01.560 --> 05:08.200 So how long we're going to get old and we're going to replace it. Somebody has it's a fear 05:08.200 --> 05:13.880 we have worse technology. And again, I want to end the line. Events like Faustem are fighting this 05:13.880 --> 05:21.080 kind of fear, because our empowering us to be again author of the technology, to be put our hands 05:21.160 --> 05:28.040 on insight technology without being held outside of the box. One of the things that is not in the 05:28.040 --> 05:34.600 cyberpunk novels written by William Gibson, Bruce Berlin, and other major author is that the average 05:34.600 --> 05:39.880 character in this novel is super aware about technology, but most of the people are not. 05:39.880 --> 05:45.080 The most of my friends, they they call it's not that I hate them, but I'm very critical with them, 05:45.080 --> 05:53.960 and I'm kept like I'm treated like the teamfoil hat guy, but they keep information from Facebook, 05:53.960 --> 05:59.240 they share them on Instagram and they tell their friends throughout WhatsApp. So they live in this 05:59.240 --> 06:03.800 wall garden and they are not even aware of it. So I mean, this is most of us in this room, they 06:03.800 --> 06:09.160 keep on telling. You are the teamfoil people probably, but I want to underline this. Anyway, 06:09.160 --> 06:16.280 Mondo Magazine in 93 was depicting this man of the future. Some kind we are something like that 06:16.280 --> 06:22.520 nowadays, we go around with a lot of devices, but the main device we have is this tool, which is on 06:22.520 --> 06:28.360 on this table right now. Most of us are carrying at least one of these, it's called Smartphone, 06:28.360 --> 06:34.600 but it's not a phone at all. It's something that allows us to pay to express our level of citizenship 06:34.680 --> 06:46.040 to do all kinds of things. And this underlines the way I was back earlier today in a 06:46.040 --> 06:54.280 the Macedon conference and it was super interesting how Macedon and other tools are promoted by 06:54.280 --> 07:01.160 you to substitute this wall garden approach, where actually we are exposed to several kind of 07:01.160 --> 07:09.480 information rather than other. But again, the concept of cyberpunk megacorps is indeed real. 07:09.480 --> 07:18.200 And this is legally speaking is not even legal, because actually I had this presentation in 07:18.200 --> 07:25.320 Hungary in Germany and now in Belgium. And I found the same article in Constitution, which 07:25.480 --> 07:32.120 is promoting the freedom of secrecy in correspondence. And that's what is not happening. 07:32.120 --> 07:38.280 Right now, in the sixth of January in UK now you have some kind of check on your messages. 07:38.280 --> 07:46.280 And this is the basic idea behind a law that is being proposed exactly in this town, by the way, 07:46.280 --> 07:51.960 in Brussels about how we are going to be monitored. Apparently now is lightly changed. The 07:51.960 --> 07:57.720 chat control is going to be you that you want to be checked. I still don't understand how this 07:57.720 --> 08:05.000 is going to happen. But the concept that all of our messages are going to be checked is somehow 08:05.000 --> 08:11.640 lies a little bit, but it's scary enough. I'm telling you this, because these are all the elements 08:11.640 --> 08:17.000 that are promoting, have been promoting a lot, a new concept of communication. We're going to 08:17.000 --> 08:22.520 see four of them, but the point is that I've been seeing this thing blooming, exploding, 08:22.520 --> 08:27.240 and I didn't understand why, and I came to the conclusion. It was related to all of this 08:27.240 --> 08:35.800 fear of control, fear of being monitored. Some people possibly the most paranoid of us are following 08:35.800 --> 08:42.360 this, but some of you are possibly. This is related to another concept, which really 08:42.360 --> 08:47.400 be ranged me, and I found it really interesting, and is a book by Janis Varufakis called 08:47.400 --> 08:54.680 techno feudalism, and it depicts the shifting from capitalism or turbo capitalism of the late 08:54.680 --> 09:05.720 90s, early 2000s, and how we changed using this portion network, so to say. So somebody really 09:05.720 --> 09:12.200 made, I don't actually, I'm not 100% sure this is correct, but somebody really made 09:13.160 --> 09:20.040 the feudal word versus the nowadays word, and they try to tie the levels, but at this stage 09:20.040 --> 09:31.480 of my presentation, I do this exercise, the techno feudalist exercise, where I took this picture 09:31.480 --> 09:41.000 from an old painting, from the feudalism, even the evil time, and actually these represents 09:41.000 --> 09:47.080 in a way what happens. We are the serves. I am a content creator, I'm not even a content creator, 09:47.080 --> 09:53.080 or from time to time, I share some videos, some pictures online, and whenever we do that is somehow 09:53.080 --> 10:01.560 we are the serves to a person, an entity, a company, most of the time. There is giving us 10:02.040 --> 10:13.080 the feudal medieval master some space for us to make some vegetables grow, something we can 10:14.200 --> 10:21.000 we can harvest, which is our hedonism for some people that are gaining money from their social 10:21.880 --> 10:28.120 sharing is there on money, and we share it with them. So actually, 10:28.200 --> 10:40.440 we are basically harvesting hard drives, and we are turning a blank hard drive with our zeros 10:40.440 --> 10:48.200 and ones in order to be coming valuable. I think this is a powerful metaphor of what we do 10:48.200 --> 10:57.320 when we share this contents on somebody else's cloud. So I think what some initiatives are promoting 10:57.400 --> 11:07.240 is a way to change the point of view, and the sharing in a different way, this kind of 11:07.240 --> 11:13.720 of contents, which are also used by many other YouTube changes license, so now you can even 11:14.360 --> 11:23.080 be your content and be used to trade AI. This is going through and gets even darker from time to time. 11:23.080 --> 11:29.960 So there is this different, I guess the blockchain one is kind of correct, somebody may raise their hands 11:29.960 --> 11:38.360 and say, no, that is not good, but I hope it covers in a very superficial and acceptable way 11:39.080 --> 11:44.840 three different approaches. So today we are in this brief presentation, we can have questions. 11:44.840 --> 11:50.200 I hope Liam from the reticulum meet up with yesterday's present because some people may have specific 11:50.520 --> 11:55.480 question about reticulum, he can answer rather than me. But anyway, we are talking about this approach, 11:55.480 --> 12:03.240 a distributed network. Each node is the same, so to say, so each one has the possibility to 12:03.240 --> 12:13.080 host as much as any other, to be as much as any other node. And in a way, I have seen 12:13.240 --> 12:22.280 this kind of experimentation, because when I start using meshtastic in my own town, nobody 12:22.280 --> 12:28.200 used meshtastic, so I add the chance to test meshtastic in taz. What is a taz? Actually, 12:28.200 --> 12:34.200 it falls in his taz, basically. It's a temporary retinomalous zone, and there is this American 12:34.200 --> 12:39.960 philosopher, Hacking Bay, the growth of wonderful book in 1991, depicting the concept of temporary 12:40.040 --> 12:51.160 autonomous zone. What is it? It's obviously a temporary retinomalous space, and it's somehow self-organized 12:51.160 --> 12:59.640 and focused on experimentation, which is what we have seen in this space. It can be either physical 12:59.640 --> 13:07.640 or digital, so I guess some discords, not very big discords or some telegram groups or some forums, 13:07.720 --> 13:13.720 they may be a temporary retinomalous zone. I don't know too much as to how much extent temporary, 13:13.720 --> 13:20.600 but they are autonomous zones and self-organized, and they are designed to dissolve in this 13:20.600 --> 13:27.560 appear. So I have been going to this taz, and I have seen experimenting the use of these meshtools, 13:27.560 --> 13:32.680 mostly that I'm a tested meshtastic. Now I've been testing a little bit meshcore, even though 13:32.680 --> 13:39.640 in the places where I tested, there is not much people using it of next to nobody. But it was 13:39.640 --> 13:45.400 really interesting. I met people, and I understood how people used it in many different ways. 13:47.640 --> 13:55.160 These are all examples of taz. Some of them are events like related to code. Some other 13:55.160 --> 14:01.240 are events related to dance, but they are, but some of them last one day, today is some of them 14:01.320 --> 14:10.360 last week, but they all share this common feeling of temporary approach and sharing some 14:12.600 --> 14:18.040 some house and secrets. It's a temporary private thing. It's an experience. You go back to 14:18.040 --> 14:26.360 your place and you tell about it. So I'm besides being a workshop that teacher, I also 14:26.760 --> 14:32.920 wearable computing workshop in one of these taz since 13 years. So at some point, I understood 14:32.920 --> 14:40.840 that I was the one who could bring this meshtastic experience in those festivals, in those taz. 14:40.840 --> 14:49.640 These up in two years ago. Basically, the old presentation is an assumption. You can be either 14:49.640 --> 14:55.480 a festival-golder error that plays with innovation, or you could be an error that plays with innovation. 14:55.560 --> 15:00.040 These are the two options that make you playing with these kind of new things. 15:00.040 --> 15:03.880 You could be an error that doesn't do any innovative, you're free to do whatever you want of course. 15:05.400 --> 15:13.480 So in 2024, I predict the experience to connect all festivals with place and antenna. 15:14.440 --> 15:19.000 We place an antenna in the taller place, and then other things happen, because that year 15:19.000 --> 15:23.800 of burning men, people started using meshtastic in a very heavy way. To the point that we're 15:23.800 --> 15:29.000 going to see meshtastic develop a special firmware for a very high density event, because that 15:29.000 --> 15:34.840 time, the work, the first time that everybody used the basic meshtastic. And last year, I went to 15:34.840 --> 15:41.880 two festivals checking and also promoting this approach. And then I am here at Fazem. This is a friend 15:41.880 --> 15:48.360 of mine with me installing an antenna in the tallest place of one of these event. It's also a YouTube 15:48.440 --> 15:56.200 video, I jokingly made about this adventure, but there is a very big and strong community 15:56.200 --> 16:02.760 that organize the communication using meshtastic at Burning Men. They also have very good 16:02.760 --> 16:09.000 documentation, so if you are planning to camp with your friends, our good starting point is going 16:09.000 --> 16:15.480 to Burning Mesh, because they have a very self-explanatory tutorials about how to create a camp 16:15.480 --> 16:20.040 chat, because you can have a private chat, of course, not just this primary chat where everybody 16:20.040 --> 16:27.880 is sending a mojji right now for them. And so, and then, I mean, which are the main reason why people 16:27.880 --> 16:34.840 started using this infestity, but most of the time was not losing your friends. So, for example, 16:34.840 --> 16:42.280 in 2024, this YouTuber self-made with a lot of radio and a little ESP32 board, this self-made 16:42.440 --> 16:48.040 is on tracker. Without using meshtastic, it was something that was really failed from people. 16:48.040 --> 16:55.640 And we started seeing a product sold in order to solve that specific problem, not using meshtastic 16:55.640 --> 17:01.080 again. They were just solving that specific problem, so they were talking, they are on close network, 17:01.080 --> 17:07.560 with their own specific protocol. So, this was interesting and allowed me to go to the Fusion 17:07.880 --> 17:14.040 which is a very big, I think is the biggest one of the biggest festival in Europe in Germany. 17:14.040 --> 17:20.680 And I brought this and I understood that it was German people who were using consistently 17:20.680 --> 17:28.600 at Fusion Festival this kind of meshtastic radio. And this made me updating this presentation comparing 17:29.720 --> 17:35.480 four different tools. Actually, they are all mesh, but they are not all using the same 17:36.040 --> 17:44.200 same communication, because the first one, BChat, is using just the Bluetooth of your phone, 17:44.200 --> 17:50.120 which makes it so perversive, because all of the people in this room, not just the one that 17:50.120 --> 17:57.080 have a radio that they have to buy, flash it, understand. Now, everybody of you can download this app 17:57.080 --> 18:04.680 from Jack Dorsey. And I don't particularly like BChat, but 1990 percent of the people that 18:04.760 --> 18:09.160 knew this passion of me going to festival talking about this right, that they all told me, 18:09.160 --> 18:14.600 that with the understood what you are doing, you install BChat and I said, no, it's not that 18:14.600 --> 18:20.360 all this, but it's important how we perceive this, because all of the imaging, how many people 18:20.360 --> 18:28.040 learned about BChat that don't even know about meshtastic. So, I wanted to add this tool and I wanted 18:28.040 --> 18:34.920 to compare with the other. So, in order to measure how powerful, so to say are these tools, 18:36.680 --> 18:41.960 avoiding to enter too much between the fighting that is now happening between meshtastic and 18:41.960 --> 18:46.280 meshcore. And I don't know, I don't stand with none of the two, I'd be using a lot of meshtastic. 18:46.280 --> 18:50.680 You'll see some of the projects that I made with meshtastic, but I don't have the, I don't have the 18:50.680 --> 18:56.360 clue. I mean, I see a lot of people using meshtastic, and obviously, to me, it's a way to communicate 18:56.440 --> 19:02.360 with other people, I don't know, but mostly, it's up to you. But anyway, the number of ops, the concept 19:02.360 --> 19:08.920 of op is basically the number of meshtastic stays alive. You imagine the number of op is like 19:08.920 --> 19:15.320 the expiry date of the yogurt of your meshtastic. Three hops, it means that it jumps three nodes, 19:15.320 --> 19:25.960 and then it dies. So, it's shut and meshtastic, they have up to seven ops, which, which may sound 19:26.600 --> 19:32.200 very low, but you have to understand that meshtastic allows nodes to have MQTT, so you can have a 19:32.200 --> 19:39.480 node that teleport to you somewhere else. And most of the time, you edit the settings to have 19:39.480 --> 19:45.560 three ops, rather than seven. To seven ops is a very heavy message. Seven ops gets 19:46.920 --> 19:52.760 is heavy and so lowers down the speed of the network. But, for example, meshcore by changing 19:52.760 --> 20:02.040 several parameters and chopping out several services or possibility, meshtastic was giving, 20:02.040 --> 20:09.960 like telemetry, for example. They are now offering you up to 64 ops, up to 64 ops. I don't think 20:09.960 --> 20:16.600 a standard meshtastic has so many ops. And then we're going to see that the column is the only 20:16.680 --> 20:23.880 service that was either, I think, represented very good in this false them edition, because we had 20:23.880 --> 20:29.960 free presentation about the article one, I think, is just finishing right now. So, there are 20:29.960 --> 20:35.560 I'm going to send you the, there is a very good presentation, Liam, gave yesterday about the future 20:35.560 --> 20:39.960 of the article, I think you should also check that one. It's very specific about the article, 20:39.960 --> 20:46.040 but I think it was offering 124 ops, but is using all solar, it's also using other, it's, 20:46.040 --> 20:52.280 I think the column is a protocol, it's a communication stack, it's a network stack. So, it allows 20:52.280 --> 21:02.120 you to use Laura as much as other, as other two protocols. So, the first is a, 21:02.280 --> 21:10.200 apparently, it allows you not from the, the, the app allows you just to chat throughout, 21:10.200 --> 21:17.400 Bluetooth, to anybody else having the chat, you can also create private rooms, apparently, 21:17.400 --> 21:21.720 we're going to see that some people are saying this private rooms are not that private. 21:23.000 --> 21:27.880 The difference between the white paper, they published this project has seven miles, 21:27.880 --> 21:34.600 super, super reason. And, and the offering of the app is kind of big, because they are offering 21:34.600 --> 21:41.160 also to be sending an allowing you to send these messages using the nostril protocol, 21:41.560 --> 21:46.040 which is a way to communicate privately online, so to say, in a very, 21:46.040 --> 21:51.880 the way, but the app doesn't allow you to do so, but online, if you go to be chat online, you can. 21:52.200 --> 22:02.840 I was amazed, preparing this presentation, I discovered that Bichot is heavily used in very 22:02.840 --> 22:11.960 difficult situations, like in Gaza, or, for example, in Uganda, there were, I don't know if 22:11.960 --> 22:17.480 you were, there were some election like three weeks ago, and internet was switched off, and a lot 22:18.440 --> 22:24.040 I've seen this article going around, they internet a lot of people use Bichot to communicate, 22:26.040 --> 22:34.040 without the internet. I wonder how this happened if you have the possibility to have 20 to 30 22:34.040 --> 22:40.040 meters in an open round with the Bluetooth antenna, and you have three ops, you're going 90 meters, 22:40.360 --> 22:47.000 60 meters, 7 ops, you're going to be 100 meters, so maybe during a riot is useful, 22:47.000 --> 22:53.080 but I don't see, I think it can replace a communication chat as much as mechanistic, 22:53.080 --> 23:00.600 can, or, or the other tools that we're going to see. And, so I was amazed by these news, 23:00.600 --> 23:07.160 so I put it because, wow, I didn't think, it was possible. It's very common nowadays, it's 23:07.160 --> 23:14.920 a trend to stop internet, this is a, in geoccal access now, they track specifically this, 23:14.920 --> 23:20.600 and the internet was stopped last year, I mean, we're just about 20, 24, 1296 times, 23:21.480 --> 23:27.240 and this is, this number is increasing, and you wonder, oh, this is happening outside of Europe 23:27.320 --> 23:35.320 now, in 2017 or 1970, the internet was stopped in Catalonia because they were rioting against 23:35.320 --> 23:42.280 the central state. Again, I'm not taking part in the Catalonia versus Madrid, the Castilla 23:43.560 --> 23:49.080 fighting and the fact that Catalonia wants to take off Spain, but the internet was stopped in Europe, 23:49.080 --> 23:57.000 so it's not that wrong to say that it can happen again. And this issue, apparently, a very heavy 23:57.080 --> 24:04.120 issue, or I did, if you're going to be chat, this issue is, the one that says, possibly is not that 24:04.120 --> 24:10.440 private because they tested that some of, sometime when you create a private group is, is actually 24:10.440 --> 24:18.280 achievable, reachable from other, which had user. So, we, well, where is the beach at community? 24:19.160 --> 24:24.680 I couldn't find, I mean, in, in, in the discussion, there is one discussion that was open 24:24.680 --> 24:29.320 when it was lunch in August, or ready to people are saying that it doesn't work. 24:30.360 --> 24:34.840 So, apparently, a group of developers are working for Dorsi, that is releasing and 24:34.840 --> 24:40.520 updating the app, but we don't have, as the other tool we're going to see, a strong community 24:40.520 --> 24:47.320 that fights for you, that is solving issues, that is meeting, that falls them, like, the reticulum 24:47.320 --> 24:53.480 one did today, and yesterday, finding solution for the future. So, apparently, the chat is like 24:53.560 --> 25:01.640 something that came from, from top. Then you master16, I think we all understood what 25:01.640 --> 25:08.440 master16's about the Soy as about chatting through Laura, you can share several things as your 25:08.440 --> 25:17.720 position, telemetry, you can use mqt75 to make your message be sent very far away using the internet, 25:17.720 --> 25:23.460 using your own mqt75 tracker is gpL free, so everything has to be released open 25:23.460 --> 25:30.980 source and publicly, and has a lot of things in the packet system in the messaging system. 25:30.980 --> 25:35.700 So some of the people that are criticizing and we're going to see this after what we 25:35.700 --> 25:47.180 talk about, the fact that the broadcast into many is easy. DM is difficult. When 25:47.180 --> 25:51.420 is going to be used, the hiking in the sports, when you go in the field, you can set 25:51.420 --> 25:58.540 up a temporary network, simply by turning on a little node that has days, hours, 25:58.540 --> 26:06.060 today's of battery, or in emergency, like war zones, or simply privately talking to a 26:06.060 --> 26:14.860 friends in a urban scenario, or in big events of festival, as we saw. We have several, I think 26:14.860 --> 26:20.820 the Guinness World Record in a mesh communication is held by Mishtastic, is like 331 26:20.820 --> 26:28.500 kilometers between Rieca, Abobri, Rieca, is a nice city in Slovenia, and a place 26:28.500 --> 26:35.580 we above destroy our cuisine. So it works, actually, I mean, I have never experienced any 26:35.580 --> 26:40.660 problem in the static not even in DMs. And we have seen several events that made 26:40.660 --> 26:49.380 Mishtastic a very cool tool that made a lot of people far away from these topics, aware of 26:49.460 --> 26:55.460 the need of Mishtastic, one of which was the big blackout in Spain, and a lot of communication 26:55.460 --> 27:00.220 relied on Mishtastic, it's one of the case study, I brought not just me. A lot of people 27:00.220 --> 27:04.900 brought, mentioned then this year in last November, I met one of the people that tried to 27:04.900 --> 27:11.620 set up and restore communication in Madrid, and obviously, a lot of people are using 27:11.620 --> 27:18.100 for IoT. Obviously, nowadays, I don't know if ice is, but a lot of police has 27:18.100 --> 27:25.380 jammers. So if you jam on the 800, 800, 800, 800, 800, 800, I think Mishtastic is not going 27:25.380 --> 27:31.860 to help you, but we have been seeing a strong use of Mishtastic in riots, when the rioters have 27:31.860 --> 27:40.700 a variety of course. So this makes us another interesting topic, and another interesting term, 27:40.780 --> 27:48.060 Shanzaiism. So Mishtastic is developed by a team in USA, and there is a very big community, 27:48.060 --> 27:55.980 and they just released what they need in a radio. So I don't think, I don't think Mishtastic 27:55.980 --> 28:02.860 contact any Chinese producer to make our own radio. I don't think maybe it happened. Mishkor, 28:02.860 --> 28:10.300 again, is a British or British offer similar to Mishtastic, they didn't neither connected 28:10.300 --> 28:17.420 or communicate specifically to a producer, or maybe they did with one. But this is where Shanzai 28:17.420 --> 28:25.260 enters in the room. Shanzai is a very interesting term and concept in Chinese production. 28:26.460 --> 28:34.540 In Shanzai, in Chinese means a castle on the hill, but a Shanzai producer is a term that was used 28:34.620 --> 28:41.420 as an offensive kind of a fancy term at the beginning of 2000. Now I think is a compliment, 28:41.420 --> 28:47.100 when you start producing something that is closed to something by you, you add elements, 28:47.100 --> 28:54.140 you add things like an example of Shanzaiism is this phone, they added the television 28:54.140 --> 29:01.340 communication. So you could see television on a phone, but nowadays Shanzaiism means that 29:01.340 --> 29:07.980 they understood that this was interesting, they being several Chinese producers in Shanzai. 29:07.980 --> 29:17.100 And they started pushing products that were compatible with Mishtastic based mainly on ESP 32 chipset 29:17.100 --> 29:25.820 and Nordic one. So we've seen all kind of creative things. We have, we have keyboard, 29:26.780 --> 29:34.700 things we have artistic PCB running Mishtastic or Mishkor because they are, you can like flash 29:34.700 --> 29:43.420 is the same concept or we have static nodes that are solar power or nodes that are meant to be put 29:43.420 --> 29:51.660 on balloon, balloon, balloons or on drones to create a temporary network. So this is really interesting. 29:51.740 --> 29:58.860 Most of the time you use a node and you connect it with a Bluetooth, with a Bluetooth app, 29:58.860 --> 30:04.860 but these other nodes with the keyboard look in like a little bit the black barrier experience 30:04.860 --> 30:09.100 are becoming really popular because allow you not to use this smartphone and you can simply 30:09.100 --> 30:19.500 chat chatting with your friends using. So this is okay. So one of the things I really like 30:19.500 --> 30:25.500 on Mishtastic is the custom feasibility software. It offered and maybe is paying for this. 30:25.500 --> 30:32.060 It offers so many solutions. I played a lot with the fact that you can create devices that 30:33.340 --> 30:42.140 allow you to create bots of the Dom Mishtastic. So you can create a bot of the Dom Mishtastic node. 30:42.140 --> 30:47.820 I really is actually a little example is not even a framework. It's several examples you can 30:47.900 --> 30:53.500 follow if you're using a SP32 board that allows you to control and trigger server motors, 30:53.500 --> 30:59.020 turn on light, read the server sensors. Apparently it's very difficult to port this to Mishka because 30:59.020 --> 31:04.940 the effect exactly what they didn't like. This kind of communication that was full feeling the bandwidth. 31:07.100 --> 31:13.260 I also create because of the problem you are going to experience when you use Mishtastic 31:13.260 --> 31:19.660 is that if you are not receiving the message when it was sent you lost the message unless 31:19.660 --> 31:27.980 several store and forward settings are enabled. So in order to solve this problem I created this 31:27.980 --> 31:37.020 little printer that prints everything going on in the channel. And then in order to make Mishtastic 31:37.660 --> 31:48.140 more understood somehow by users. I created this game. It's like an escape room game but for 31:48.140 --> 31:55.260 an event we maybe next year I bring it to for them where people use to solve quests interacting 31:55.260 --> 32:05.180 with the people of the event like the stands using radios. So this was my friend Andra Khuzuma from 32:05.180 --> 32:09.500 Indonesia is a friend of mine helping me out in this project and then we did in November. 32:09.500 --> 32:16.700 This was one of the map of one of the paths somebody had to solve but the point was 32:17.740 --> 32:23.500 putting these things in a n-course situation when they have to deal with people they don't know 32:23.500 --> 32:31.740 in order to fight their shyness. So to say, well, what cool experience I had lately using Mishtastic. 32:31.740 --> 32:38.540 So high density event, most of the time I would have seen on rabbit request special 32:38.540 --> 32:44.620 firmware. This happened in Burning Man also a deathcon this year and this is one of the reason 32:44.620 --> 32:51.420 why Mishtastic is one of the reason why Mishtastic was born. So just to close Mishtastic communities 32:51.420 --> 32:59.500 I think the only cool community I've seen on rabbit is on Mishtastic is on rabbit. If anybody else 32:59.580 --> 33:05.180 here has cool local communities I can update this page of the presentation. 33:05.980 --> 33:13.420 And then we reach Mishtastic. Mishtastic is very similar to Mishtastic but they chopped out several 33:13.420 --> 33:19.660 things in order to make the protocol working better. We are going to see a table where we compare 33:19.660 --> 33:27.420 several things but the main concept is that in Mishtastic we previously came, let's say we want to 33:27.420 --> 33:32.940 bring Mishtastic to Foss Dam. We are using Mishtastic right now to Foss Dam and we didn't experience any 33:32.940 --> 33:40.220 decreases. If you were to use Mishtastic in Foss Dam in their idea, you should have like a static 33:40.220 --> 33:47.660 node, a big static node, maybe 60Di antenna. The one that makes the 20 kilometer circle around 33:47.660 --> 33:54.140 sphere which you are on Mishtastic. It's a router and you use that in order to communicate. So this is 33:54.140 --> 34:02.140 kind of the difference. It's a little bit more in the presentation here, a stable backbone. 34:02.140 --> 34:08.700 So there are several places. Is used is meant to be used in a urban area where supposedly 34:08.700 --> 34:15.420 with Mishtastic you have a lot of nodes and Mishtastic is got lost. In a urban area with Mishkaur you 34:15.420 --> 34:25.020 should be able to see all your messages be received. That's their challenge. Actually nowadays there 34:25.020 --> 34:33.180 is this big, big plane between the two communities to the point that if you go to red it on Mishtastic 34:33.180 --> 34:43.020 which is the main community of Mishtastic and you write the word Mishkaur you are banned. Wow. They should 34:43.020 --> 34:49.580 talk, I don't know, or many Mishtastic should add some of the feature but in this long list the 34:49.580 --> 34:56.220 most important thing is packet propagation and all of control. So the fact that how the things are 34:56.220 --> 35:04.140 are announced and how the packets are sent, these are the two main differences and actually 35:04.140 --> 35:11.100 the way Mishkaur sends the packets is more related and more close to the water reticulum does. 35:12.060 --> 35:17.900 So these are the two main things. Everybody playing with Mishtastic could play with Mishkaur. 35:17.900 --> 35:23.100 The big difference is when you have to flash a Mishtastic device, you flash one firmware and the 35:23.100 --> 35:31.660 device can become anything. I mean on this device if I open it there are the solar panel and 35:31.660 --> 35:37.980 then then I can put a big antenna and it can become a polar node, a big node or it's just a portable 35:38.540 --> 35:45.500 Mishkaur in the download and in the firmware process you have to choose which is going to 35:45.500 --> 35:55.020 become this node. So it's more complex thing. I think if you want to start playing, start with Mishtastic 35:55.020 --> 36:00.460 and then understand which are the differences between Mishtastic and Mishkaur but the community is here 36:00.620 --> 36:07.900 only enough. I discovered that Mishkaur I'm not a Facebook fan but there is a big community 36:07.900 --> 36:15.260 on Facebook and then there is NDKB which is this youtuber, British youtuber that is behind the 36:15.260 --> 36:23.100 core with other people that is releasing a lot of Mishkaur related stuff throughout by 36:23.100 --> 36:28.620 me a coffee slash repo beads and then of course there is the reddit that I did five. 36:29.740 --> 36:35.580 We are reaching the end of this presentation up not you bored too much. We are reaching 36:35.580 --> 36:41.740 reticulum. So I deeply have to thank Liam yesterday morning yesterday we had this present day. 36:41.740 --> 36:47.580 Liam are you in the room? Maybe no. I discovered a lot of new things about the 36:47.900 --> 36:58.540 important thing yesterday. So it's a complete network stop, start network stack like Mishkaur 36:58.540 --> 37:08.940 and Bitschat is MIT license with a specific edit to the meat license which implies not to be used 37:08.940 --> 37:15.500 in not to be used to to create arm to anybody. So you cannot be used in any worse situation 37:16.140 --> 37:23.980 and you cannot be used to train AI. Apparently these two edit in the MIT license prevents 37:23.980 --> 37:32.700 the distribution of reticulum throughout the day beyond alpine and asteroid. I wonder why but maybe 37:32.700 --> 37:40.620 I'm naive but it's so. Yesterday actually if you take a picture of this slide you can reach 37:40.700 --> 37:46.540 the presentation of yesterday. Liam really shared his slides are very very good slides about 37:46.540 --> 37:54.780 just reticulum and during this presentation I discovered that Mark found that over a ticulum 37:54.780 --> 38:02.140 stepped back last month. So this is one of the reasons possibly well I don't think it's a reason 38:02.140 --> 38:08.380 because the application for this event closed long ago but the free events we had about reticulum 38:08.460 --> 38:15.420 during this post them were about the future. How is this going to evolve now that the main founder 38:16.780 --> 38:25.180 left and there are seven six different implementation or five different implementation 38:25.180 --> 38:33.900 of the original branch made by Mark. As you can see choose your own favorite language and you 38:33.980 --> 38:42.380 can contribute. Again thanks to Liam for the presentation here yesterday. Some of these slides 38:42.380 --> 38:49.580 were updated by by watching his presentation and making question to him. Oddly it's very odd that 38:52.460 --> 38:57.420 I'm not following that I wasn't following that much the matrix channel of reticulum but I'm 38:57.420 --> 39:02.140 really attentive about the topic and read it and I wasn't aware of the fact that the founder came 39:02.540 --> 39:07.580 so possibly there wasn't a public communication of it. Anyway when you play with reticulum there are 39:07.580 --> 39:16.220 two main ways just to close the reticulum story. One is using this best top up claw or called 39:17.180 --> 39:22.220 meth chat is developed by Liam Kotel which is one of the developer of Nashville by the way. 39:22.940 --> 39:29.980 And the other is super new if you're an android user you should be like having a blast using 39:29.980 --> 39:41.660 columb who is who is basically a client for android of reticulum and well as everything you can 39:41.660 --> 39:51.820 even hook up a node what is an R node I'm going to show you okay this is mess chat just a few 39:52.460 --> 39:58.700 quick thing and then we're done you can ask question and so well there is a network visualizer 39:58.780 --> 40:04.780 is going to take some time to these are all the nodes I am hooked up with right now there are 40:05.660 --> 40:16.700 I had these nodes in the interfaces so the big red one are the bigger nodes are in this list over 40:16.700 --> 40:27.180 year. I can message people if I know their address and as you can see I'm announcing myself so the 40:27.500 --> 40:37.980 people know that I am I am lying two more tools that are into this client for desktop client for 40:37.980 --> 40:51.980 reticulum one is this nomad network two basically this is like a BBS I wonder if it's going to 40:51.980 --> 40:57.500 upload because I'm on my phone I'm not even connected so yeah I'm not going to work 40:59.500 --> 41:10.940 one second maybe it's going to work during the questions yeah yeah it's not so one of these is if 41:10.940 --> 41:18.140 if it would be working you would see several internet pages made of text a lot of them were in 41:18.140 --> 41:25.500 Italian which was really strange to me wow but very very from all over the world it's very kind 41:25.500 --> 41:33.260 of interesting how this approach is used the other thing is there are not flashes so if you have 41:33.260 --> 41:40.060 one of those radio you're playing with with mechanistic and mesh core you can flash it using this tool 41:40.780 --> 41:48.700 and use basically it as an interface so these messages if you take off the internet 41:48.700 --> 41:55.260 connection like like I'm now by the way you can check with any other node having obviously the 41:55.260 --> 42:06.060 Laura on because basically the protocol can use Laura to to to send messages so just to finish 42:06.140 --> 42:13.260 the presentation you can enter in the communities which are really really active of reticulum 42:13.260 --> 42:19.020 using this link of metrics or the zoolip apparently they were promoting zoolip because it's 42:19.020 --> 42:26.620 less less noisy and I think I'm done so if you have any questions or if you want to share 42:26.620 --> 42:32.300 your experience as well I know there are many users here with plastic pretty too to add your 42:36.860 --> 42:47.500 so thank you very much David for this very insightful talk and all the work that you do 42:48.140 --> 42:57.660 before we do the Q&A as short announcement we need to clear this room before 6 or 450 so everyone should 42:57.660 --> 43:04.140 leave only through this door please don't use this door only through this door and if you want to 43:04.140 --> 43:09.820 talk more to Davida you could go outside the building and talk and that's mainly because we need 43:09.820 --> 43:21.180 to clean this room and prepare for the closing I think the mother's going okay it's okay it's okay 43:21.180 --> 43:26.220 thank you man thank you very much thank you 43:51.260 --> 43:56.220 thank you 44:16.400 --> 44:16.440 that's all I need 44:21.180 --> 44:22.180 Miyaki 44:24.180 --> 44:25.180 Miyaki 44:28.180 --> 44:29.180 Miyaki 44:39.180 --> 44:40.180 Miyaki 44:51.180 --> 44:53.180 You 45:21.180 --> 45:23.180 You 45:51.180 --> 45:53.180 You 46:21.180 --> 46:23.180 You 46:51.180 --> 46:53.180 You 47:21.180 --> 47:23.180 You 47:51.180 --> 47:53.180 You 48:21.180 --> 48:23.180 You 48:51.180 --> 48:53.180 You 49:21.180 --> 49:23.180 You 49:51.180 --> 49:53.180 You 49:53.180 --> 49:55.180 You 49:55.180 --> 49:57.180 You 49:57.180 --> 49:59.180 You 49:59.180 --> 50:01.180 You 50:01.180 --> 50:03.180 You 50:03.180 --> 50:05.180 You 50:05.180 --> 50:07.180 You 50:07.180 --> 50:09.180 You 50:09.180 --> 50:11.180 You 50:11.180 --> 50:13.180 You 50:13.180 --> 50:15.180 You 50:15.180 --> 50:17.180 You