WEBVTT 00:00.000 --> 00:30.000 So, we're going to talk about what we're going to talk about, what we're going to talk about is what we're going to talk about, what we're going to talk about, what we're going to talk about, what we're going to talk about, what we're going to talk about, what we're going to talk about, what we're going to talk about, what we're going to talk about, what we're going to talk about, what we're going to talk about, what we're going to talk about, what we're going to talk about, what we're going to talk about, what we're going to talk about, what we're going to talk about, what we're going to talk about, what we're going to talk about, what we're going to talk about, what we're going to talk about, what we're going to talk about, what we're going to talk about, what we're going to talk about, what we're going to talk about, what we're going to talk about, what we're going to talk about 00:30.000 --> 01:00.000 what we're going to talk about, what we're going to talk about, what we're going to talk about, what we're going to talk about, what we're talking about, what we're going to know about, what we've done and what we're going to talk about, what we're going to talk about, what we're going to talk about, what we're going to talk about, what we're going to talk about, what we're going to talk about, what we're going to talk about, what we're going to talk about, what we're really going to talk about, what we're going to do, we're going to talk about, what we're going to talk about, what we're going to talk about, what we're going to talk about, what we're going to talk about, what we're going to talk about, what we're going to talk about, what we're going to talk about, what we're going to talk about , what we're going to talk about, what we're going to talk about about, because what 01:00.000 --> 01:05.000 What do you think you're going to miss here over to make one of it? 01:05.000 --> 01:09.000 Also, when you took about ten minutes, there's a big problem. 01:09.000 --> 01:11.000 On the other hand, there's a lot of trouble. 01:11.000 --> 01:14.000 You can tell if that you make the first thing, 01:14.000 --> 01:18.000 and you're going to miss it. 01:18.000 --> 01:23.000 It's not green, but you can do it. 01:23.000 --> 01:24.000 Okay. 01:24.000 --> 01:25.000 So, here we go. 01:25.000 --> 01:27.000 You're on this side, the right side should do it. 01:27.000 --> 01:28.000 Okay. 01:28.000 --> 01:33.000 Sorry for people who have only the lips. 01:33.000 --> 01:37.000 But what I'm seeing is that, sometimes that's on my own. 01:37.000 --> 01:38.000 Not that good. 01:38.000 --> 01:39.000 I'm explaining why. 01:39.000 --> 01:40.000 And you will see why. 01:40.000 --> 01:43.000 Maybe it's a good alternative. 01:43.000 --> 01:47.000 So, I was speaking about the ergonomic of those platforms. 01:47.000 --> 01:50.000 Most of the time, they are done for posting, posting contents. 01:50.000 --> 01:52.000 They are not made for events. 01:52.000 --> 01:54.000 And events are very particular. 01:54.000 --> 01:55.000 They are days. 01:55.000 --> 01:57.000 There is location. 01:57.000 --> 02:00.000 There are also audience on who can attend and not. 02:00.000 --> 02:03.000 And the searchability is really bad. 02:03.000 --> 02:06.000 So, I don't know how you manage, but you have to follow a very specific people. 02:06.000 --> 02:12.000 And it's crude for events at your local access message or something. 02:12.000 --> 02:14.000 So, you have to be very careful. 02:14.000 --> 02:15.000 You can really search. 02:15.000 --> 02:16.000 You can bookmark. 02:16.000 --> 02:21.000 So, you can't really sense what you have found to your friends. 02:22.000 --> 02:25.000 And they have to go to the platform again and search again. 02:25.000 --> 02:32.000 And also, it's also, again, also there's a lot of fragmentation. 02:32.000 --> 02:36.000 So, if you are on a social network, you are not on another. 02:36.000 --> 02:40.000 And by that, you turn share contents. 02:40.000 --> 02:44.000 And also, they like a lot of interoperability. 02:44.000 --> 02:46.000 They don't play anything for it. 02:46.000 --> 02:53.000 And it's very easy to add the content to, for example, to have a agenda. 02:53.000 --> 02:59.000 So, last year, from a self-step aside from the project. 02:59.000 --> 03:03.000 And we offered them to take over the maintenance. 03:03.000 --> 03:08.000 And we've been financially supported by an internet for this challenging transition. 03:08.000 --> 03:11.000 So, we sense them a lot. 03:11.000 --> 03:17.000 Now, after a year, we are here in front of you. 03:17.000 --> 03:19.000 What? 03:19.000 --> 03:24.000 It's still the same. 03:24.000 --> 03:26.000 The next one will come. 03:26.000 --> 03:29.000 Thank you. 03:29.000 --> 03:36.000 So, we are very glad to be there in front of the first day to speak about mobility. 03:36.000 --> 03:45.000 To share with you all our ambition for the future. 03:45.000 --> 03:50.000 And we really want to build this roadmap with the community. 03:50.000 --> 03:54.000 We have a lot of users, we have a lot of instance owners. 03:54.000 --> 04:03.000 And we want to build the next steps with them along with all the diverse ecosystem. 04:04.000 --> 04:11.000 And so first of all, Alex is going to present to you what is mobility zone for the users. 04:11.000 --> 04:14.000 And then I'll take over to explain our works. 04:14.000 --> 04:20.000 And then finally, we'll share with you our ambition for the future. 04:20.000 --> 04:28.000 So, I will drive you through the main features of mobility zone that you might not know. 04:28.000 --> 04:32.000 So, it's a web site. 04:32.000 --> 04:36.000 Basically, on the homepage, you find local agenda. 04:36.000 --> 04:40.000 And then you can search and dive for more contents. 04:40.000 --> 04:44.000 You will find, so you can search for events based on lots of criteria. 04:44.000 --> 04:48.000 But date, location, location is quite a key feature. 04:48.000 --> 04:52.000 And you can also search for activities. 04:52.000 --> 04:56.000 Like for instance, if you look for yoga class or anything that lasts all year long, 04:56.000 --> 05:01.000 you can find it there as well and local books. 05:01.000 --> 05:05.000 So, events, so you can publish them. 05:05.000 --> 05:10.000 You can share them on social measures and email them. 05:10.000 --> 05:16.000 You can also publish activities, as I said, that lasts all year long. 05:16.000 --> 05:24.000 You can search by location, by keywords, by dates, and also by categories. 05:24.000 --> 05:28.000 You can manage box situation to events. 05:28.000 --> 05:34.000 Users will get notified by email, for instance, if there is a change. 05:34.000 --> 05:42.000 And also there are possibilities that events get automatically published that stuff will explain a bit more. 05:42.000 --> 05:44.000 Then you have groups. 05:44.000 --> 05:49.000 So, you can create groups for several things. 05:49.000 --> 05:53.000 So, first groups have a public page where they can post content. 05:53.000 --> 05:58.000 So, you can post events or activities from a group. 05:58.000 --> 06:04.000 And you can also create posts like news or information related to the group. 06:04.000 --> 06:08.000 You can manage group members. 06:08.000 --> 06:13.000 And they will have access to some private content, like something like a small forum. 06:13.000 --> 06:19.000 You can share links to documents and also have private events. 06:19.000 --> 06:25.000 And the groups have their own ICS feed and RSS feed. 06:25.000 --> 06:31.000 So, you can follow whoop news like that. 06:31.000 --> 06:39.000 So, if you understood some of these websites that we call instance. 06:39.000 --> 06:47.000 So, instance administrator, they can create their own website with their own visual identity. 06:47.000 --> 06:53.000 They will also define who's terms and conditions and who can register. 06:53.000 --> 06:58.000 So, it can be open for anybody to register and post or it can be a little bit more private. 06:58.000 --> 07:03.000 Where they choose which users can join. 07:03.000 --> 07:08.000 They are responsible for moderation of users and contents. 07:08.000 --> 07:13.000 And there are also the one that we choose which instance to federate with. 07:13.000 --> 07:20.000 Which one to follow or which ones can follow them. 07:20.000 --> 07:25.000 So, there are quite some dozens of instances. 07:25.000 --> 07:32.000 You have the full list of the ones that self registers themselves on the website. 07:32.000 --> 07:35.000 As an example, I listed a few. 07:35.000 --> 07:41.000 So, there is one case called one for family and kids. 07:41.000 --> 07:47.000 There are some from activism, activist movements. 07:47.000 --> 07:50.000 We have some in various countries. 07:50.000 --> 07:53.000 For instance, there is a mobilized Italy. 07:53.000 --> 07:59.000 We have a university that chose to have a mobilized website for their events. 07:59.000 --> 08:04.000 Some local agenda for a city or an area. 08:04.000 --> 08:09.000 And there is quite a great variety of them. 08:09.000 --> 08:16.000 In other words, it is available in 20 languages. 08:16.000 --> 08:18.000 And they can federate with the users. 08:18.000 --> 08:22.000 So, what it means is that one instance will follow another one. 08:22.000 --> 08:25.000 And it will retrieve automatically all its contents. 08:25.000 --> 08:33.000 So, all the groups and events posted on one instance will be also visible on the other instance that follows. 08:33.000 --> 08:40.000 And you need to accept, of course, that other instance will follow you. 08:40.000 --> 08:41.000 That's it. 08:41.000 --> 08:46.000 We'll have a little bit more, maybe. 08:46.000 --> 08:49.000 So, how it works. 08:49.000 --> 08:54.000 So, I will probably explain activity people for the 10th time in the day. 08:54.000 --> 08:57.000 Maybe the best one, but I will try to do my best. 08:57.000 --> 09:02.000 And so, if you want to build a federated distributed service, 09:02.000 --> 09:05.000 you need a protocol to agree on. 09:05.000 --> 09:10.000 So, everyone knows email, SMTP for email, and GSM for mobile. 09:10.000 --> 09:16.000 For the Fedivers, we mainly have activity pub. 09:16.000 --> 09:19.000 So, this schema is taken from activity pub. 09:19.000 --> 09:22.000 The drugs, probably, be all of them to you. 09:22.000 --> 09:23.000 Nobody knows about it. 09:23.000 --> 09:31.000 But the main concepts are that an actor, as an inbox, and an outlet box. 09:31.000 --> 09:39.000 So, every time you subscribe to something, you receive new content on the inbox. 09:39.000 --> 09:44.000 And every time you want to put something to others, you push it to the outbox. 09:44.000 --> 09:49.000 So, pretty simple, like explain before it's a mailbox. 09:50.000 --> 09:56.000 And what it means that it's validated, it's that we first of all, 09:56.000 --> 10:01.000 we enable those kinds of use case where people can total together, 10:01.000 --> 10:05.000 even if they belong to different service providers. 10:05.000 --> 10:10.000 So, you can think about two instance of mobile reasons, 10:10.000 --> 10:14.000 but also one instance of mobile reasons, and one instance of most of, for example. 10:14.000 --> 10:19.000 And also that we accept, on one instance, the content, 10:19.000 --> 10:24.000 and the identity of someone coming from another instance. 10:24.000 --> 10:27.000 So, those two aspects, on sharing content, 10:27.000 --> 10:32.000 and federated identity, is key to our Fedivers service, 10:32.000 --> 10:35.000 and distributed platform. 10:35.000 --> 10:43.000 So, when you want to provide the service in the open, 10:43.000 --> 10:46.000 it's key to our interoperability. 10:46.000 --> 10:51.000 And for example, on mobile reasons, so, the main obvious one is activity people. 10:51.000 --> 10:53.000 So, what is interoperability? 10:53.000 --> 10:58.000 It's enabling service to talk together and to understand themselves. 10:58.000 --> 11:06.000 So, activity people, it allows mobile reasons to be able to interoperable with all the Fedivers. 11:06.000 --> 11:12.000 So, Mastodon, Pleroma, PixelFed, Piatuben, so on. 11:12.000 --> 11:16.000 But also, with tools that have done been built for the Fedivers, 11:16.000 --> 11:22.000 explicitly, but are now adopting this protocol to share content. 11:22.000 --> 11:26.000 So, there are some plugins for WordPress, also for next cloud, 11:26.000 --> 11:32.000 and those are open source projects. 11:32.000 --> 11:38.000 For mobile reasons, we have a private API that is in GraphQL. 11:38.000 --> 11:42.000 So, for people not familiar with this technology, it's a bit more, 11:42.000 --> 11:45.000 let's say, elaborated than rest. 11:45.000 --> 11:51.000 So, you can query the world graph of objects that we have in our model. 11:51.000 --> 11:53.000 So, for example, a Mactor and OLED school. 11:53.000 --> 11:59.000 It's events, an event, and all its comments, et cetera, et cetera. 11:59.000 --> 12:03.000 So, this is very art implement, and we haven't done it ourselves, 12:03.000 --> 12:05.000 and there are frameworks to do that. 12:05.000 --> 12:10.000 But on the other side, it's very easy to develop new clients. 12:10.000 --> 12:14.000 So, for example, so, mobile reasons, it's a progressive web app, 12:14.000 --> 12:17.000 that is also provided with the project. 12:17.000 --> 12:21.000 But there are also tools that we can plug on it. 12:21.000 --> 12:25.000 For example, you can write some script in Python, 12:25.000 --> 12:28.000 and importing it automatically, some events in the platform. 12:28.000 --> 12:31.000 That's what we do with some open data information. 12:32.000 --> 12:35.000 We also have a side project, which is the mobile zone importer, 12:35.000 --> 12:39.000 that will allow you to make a bridge between Facebook. 12:39.000 --> 12:44.000 I think, Eventbrite is managed, so private platform. 12:44.000 --> 12:48.000 You can take the content and put it on a mobile instance, 12:48.000 --> 12:53.000 and also you can import like an SS, that is published by any website, 12:53.000 --> 12:58.000 and regularly, all the new events will be pushed to your mobile instance. 12:59.000 --> 13:00.000 So, yeah. 13:14.000 --> 13:17.000 And I'm pretty sure that most of the language 13:17.000 --> 13:21.000 have the client side implementation of GraphQL. 13:21.000 --> 13:22.000 So, it's very easy. 13:22.000 --> 13:25.000 We have also some minor interoperability, 13:25.000 --> 13:29.000 thanks to a calendar you can have the event, 13:29.000 --> 13:34.000 push to your, to your calendar application, like on the bird. 13:34.000 --> 13:38.000 And for all the posts, there are published as an SS feed, 13:38.000 --> 13:40.000 so you can have it in any new feed. 13:40.000 --> 13:43.000 So, on the left you are more the red and right, 13:43.000 --> 13:48.000 and on the right you have riddenly protocols. 13:50.000 --> 13:53.000 So, what do you use to do all of that? 13:53.000 --> 13:56.000 So, we have a bunch of protocol to implement. 13:56.000 --> 13:59.000 I did open and I did connect for the authentication, 13:59.000 --> 14:01.000 all the others I've been mentioned before. 14:01.000 --> 14:07.000 And so, we have, we've based our codebase on Playorma, 14:07.000 --> 14:10.000 like five years ago, so maybe it has diverge a lot, 14:10.000 --> 14:15.000 but it was a great accelerator to take start the project, 14:15.000 --> 14:19.000 and the technology are, so we need the framework, 14:19.000 --> 14:22.480 very much. Web frameworks, so it's not Django, it's not 14:22.480 --> 14:24.480 probably a noise, but it's Phoenix. 14:24.480 --> 14:27.400 It's based on the go-in-ice language, which is 14:27.400 --> 14:32.360 Elixir, looks a lot like Ruby, but it's on top of the 14:32.360 --> 14:35.800 Erlang, open telecom platform, so the open telecom platform 14:35.800 --> 14:40.280 you don't know it, it's what is used in the telecom, 14:40.280 --> 14:44.600 like it says, and also on what's up, and each time you 14:44.600 --> 14:48.040 want billions of people talking together, you have the 14:48.040 --> 14:51.120 open telecom platform behind. 14:51.120 --> 14:55.360 For the persistence, we use post-gray, and for the 14:55.360 --> 14:58.960 front end, we use UGS and TypeScript. 14:58.960 --> 15:04.600 We glue with this thing with a lot of libraries, and then 15:04.600 --> 15:08.120 everything is working, so you can come and contribute 15:08.120 --> 15:11.320 it will be easy. 15:11.320 --> 15:16.120 Since we want people to be able to self-host, we have 15:16.120 --> 15:20.760 to prepare, we try to make things easy for people 15:20.760 --> 15:23.200 at least running on Linux, and you have some package for 15:23.200 --> 15:25.960 Docker, for Debian, Fedora. 15:25.960 --> 15:28.040 You have package, I don't know, it fits well-maintained, 15:28.040 --> 15:30.600 but you have a package for Unhost. 15:30.600 --> 15:35.000 Thank you very much. 15:35.000 --> 15:37.640 And if that's something more exotic, you can still 15:37.640 --> 15:39.480 build from source, but at least you have all those 15:39.480 --> 15:43.880 packages that you will help you to go fast. 15:43.960 --> 15:48.280 This one, I will be very quick, but like I said, we 15:48.280 --> 15:52.280 don't just confate to be empty when you come on the platform, 15:52.280 --> 15:55.200 so we use the open data from our governments. 15:55.200 --> 16:00.840 It's mainly in France, but we have probably 200,000 16:00.840 --> 16:03.240 events in the France at any time. 16:03.240 --> 16:06.280 So if you will, to a small village, you will have at least 16:06.280 --> 16:08.080 some events for your next weekend. 16:08.080 --> 16:15.520 So that's it for the technical part, and I end 16:15.520 --> 16:19.040 over on Alex for the future. 16:19.040 --> 16:23.600 So we are done with icons. 16:23.600 --> 16:29.520 So as Taf said, we have been granted funds by 16:29.520 --> 16:30.720 NLNet last year. 16:30.720 --> 16:35.280 It was for this year, right, 2024, which was great. 16:35.280 --> 16:40.640 So we could transition from Hamas soft to maintaining 16:40.640 --> 16:42.960 ourselves. 16:42.960 --> 16:46.320 And what we did is that we upstreamed what 16:46.320 --> 16:51.600 had been developed side of the main branch. 16:51.600 --> 16:55.360 And that was really great to have that support, 16:55.360 --> 16:59.680 and also skill developers that jumped in. 16:59.680 --> 17:03.440 And now we can look forward and think 17:03.440 --> 17:08.880 of what we want to do next, develop new features. 17:08.880 --> 17:16.880 So in 2025, and beyond, with everybody 17:16.880 --> 17:20.080 to be able to use mobilization and create local and thematic 17:20.080 --> 17:21.120 instances. 17:21.120 --> 17:24.320 So our dream would be that anywhere in the world, 17:24.320 --> 17:27.920 when there's a local initiative, it's on mobilization 17:27.920 --> 17:32.440 is because it's created there or built there by interoperability. 17:32.440 --> 17:35.640 But if we just start with our neighborhood or nearby 17:35.640 --> 17:38.760 streets, that's good. 17:38.760 --> 17:42.200 So we'd like to offer hosting services and develop 17:42.200 --> 17:45.640 the community of users and contributors, 17:45.640 --> 17:51.920 and also to define what to do with the new branch. 17:51.920 --> 17:55.560 We got from NLNet to go forward. 17:55.560 --> 18:00.040 We'd like to involve mostly instance administrator, 18:00.040 --> 18:04.440 but also end users to give their ideas and help 18:04.440 --> 18:07.560 together to define what's the most meaningful 18:07.560 --> 18:12.280 to deliver to the community, basically refine and prioritize 18:12.280 --> 18:14.840 the backlog and funnel it a little bit, 18:14.840 --> 18:17.320 because we know we cannot do at once everything we'd 18:17.320 --> 18:19.840 like to do. 18:19.840 --> 18:23.040 So there are two things we'd like to do 18:23.040 --> 18:25.840 is to improve the quality. 18:25.840 --> 18:30.240 So as quality, I think of UX, accessibility, 18:30.240 --> 18:37.640 performance, fixing bugs, improving the tests and the security. 18:37.640 --> 18:42.720 And then there are the features we would like to develop as well. 18:42.720 --> 18:47.360 And we'll see also what comes up from the other people 18:47.360 --> 18:51.200 that we'll have on the change advisory board 18:51.200 --> 18:53.320 that we're trying to build. 18:53.320 --> 18:57.960 So we have an open call for that. 18:57.960 --> 19:01.880 So what we've been thinking of and also 19:01.880 --> 19:04.920 we received a feedback from the community 19:04.920 --> 19:08.000 that would be nice to have. 19:08.000 --> 19:12.320 We'd be to be able to link groups with one another. 19:12.320 --> 19:16.080 So they can kind of federate groups with one another. 19:16.080 --> 19:18.840 And also this event that comes from other groups 19:18.840 --> 19:21.920 and not only from your own. 19:21.920 --> 19:24.320 Improved participation management, 19:24.320 --> 19:30.560 so take multiple places to an event and manage a waiting list. 19:30.560 --> 19:33.560 And there are a group members to see who participates 19:33.560 --> 19:36.880 to group events, that's not there yet. 19:36.880 --> 19:40.640 Have a new search dimension that would be for the audience 19:40.640 --> 19:44.240 for a group is events. 19:44.240 --> 19:47.880 Annable instance, I'm a straight up to moderate user 19:47.880 --> 19:52.200 account creation for spam and also, in case you don't want 19:52.200 --> 19:55.840 to open registration to everybody. 19:55.840 --> 19:58.160 Annable instance admin also to manage a bit more 19:58.160 --> 20:02.040 the homepage and be able to pin posts and events 20:02.040 --> 20:05.560 or groups on the homepage. 20:05.560 --> 20:07.800 Have some kind of instance ball. 20:07.800 --> 20:11.840 So not all of people but all of the instance 20:11.840 --> 20:14.920 with everything that is new, like a news feed for the instance, 20:14.920 --> 20:19.560 you pass new events, new groups, create it. 20:19.560 --> 20:23.720 Small one have mobile apps available on stalls. 20:23.720 --> 20:27.600 And also we would like to have auto-generated newsletter 20:27.600 --> 20:32.760 either at instance level, like here are the upcoming events 20:32.760 --> 20:34.920 for the two coming weeks, for instance. 20:34.920 --> 20:37.200 Or maybe at Google level, like if we can make that, 20:37.200 --> 20:40.520 we can make that a group, we just have to post their events 20:40.520 --> 20:43.560 and it comes in somebody's mailbox. 20:43.560 --> 20:52.560 And we would like to improve federation so that we can, 20:52.560 --> 20:55.400 so for now, if one instance follow another one, 20:55.400 --> 20:57.560 it receives all the contents. 20:57.560 --> 21:00.080 Sometimes it's relevant, sometimes not. 21:00.080 --> 21:03.160 So we would like to enable instance to only share 21:03.160 --> 21:06.320 a selection of events. 21:06.320 --> 21:10.280 So maybe we should have the instance administrator 21:10.280 --> 21:14.080 that decides which instances he federates with 21:14.080 --> 21:18.240 that are open to communicate with each other. 21:18.240 --> 21:22.040 And then it could be like users that push content 21:22.040 --> 21:24.720 on those other instance or on those other way around 21:24.720 --> 21:27.520 that pulls what's interesting for them. 21:27.520 --> 21:30.600 So we would love to have this kind of organic growth 21:30.600 --> 21:33.880 of instance content. 21:33.880 --> 21:36.720 But that's quite a big change. 21:36.720 --> 21:40.480 There are lots of use cases to consider. 21:40.480 --> 21:43.200 And also, we need users and instance administrators 21:43.200 --> 21:46.160 to keep in control. 21:46.160 --> 21:51.160 We really think it would be like, or you valuable thing 21:51.160 --> 21:54.000 to have in mobility zone that makes it maybe more 21:54.000 --> 21:59.280 interesting than mainstream websites that exist today. 21:59.280 --> 22:03.000 And it's a dispossessed exciting. 22:03.000 --> 22:08.720 So I hope you have a good feeling now about mobility zone. 22:08.720 --> 22:11.280 If you want to support it, there are two things you can do 22:11.280 --> 22:13.080 that are very easy. 22:13.080 --> 22:16.280 It's communicate, about it, and use it. 22:16.280 --> 22:18.760 So you can think of what you can do. 22:18.760 --> 22:23.160 Maybe talk to one person about mobility zone after you live. 22:23.160 --> 22:26.240 And maybe find an instance you would like to, 22:26.240 --> 22:29.280 you can post on there are many available 22:29.280 --> 22:32.960 and post on events just to try out. 22:32.960 --> 22:34.560 Thanks. 22:34.560 --> 22:36.560 Thank you. 22:36.560 --> 22:38.560 Thank you for that question. 22:38.560 --> 22:46.960 So we have one question online, and I know there's people 22:46.960 --> 22:48.560 in the audience at one to ask questions as well. 22:48.560 --> 22:51.120 So I'm going to ask you to find somewhere else 22:51.120 --> 22:53.480 because we all want to move on after this. 22:53.480 --> 22:55.920 So the question I have from Matrix is, 22:55.920 --> 22:58.240 what about attendance information for the event? 22:58.240 --> 23:02.920 So if I sign up to an event, will that be public information? 23:03.880 --> 23:06.200 No, go ahead and leave if you want. 23:06.200 --> 23:08.520 But you say you want to participate in trial events. 23:08.520 --> 23:09.960 It's not the public information. 23:09.960 --> 23:11.320 OK, so that's not public. 23:11.320 --> 23:13.520 So thank you so much for coming and talking 23:13.520 --> 23:14.920 about Mobilism. 23:14.920 --> 23:17.520 That was something that I wanted to know about as well. 23:17.520 --> 23:19.080 So this great. 23:19.080 --> 23:20.800 Thank you all for your patience. 23:20.800 --> 23:23.600 I know that we've had very tight scheduling. 23:23.600 --> 23:26.840 We honestly had so much great content that Evan and I 23:26.840 --> 23:29.440 were really struggling to figure out how we could fit the talks 23:29.440 --> 23:30.280 together. 23:30.280 --> 23:32.400 So we really appreciate everybody moving in and out. 23:32.400 --> 23:34.880 And bearing with us that we haven't had really 23:34.880 --> 23:38.600 as great time for questions that we would have liked. 23:38.600 --> 23:41.000 But do you come along to the birth of a feather group, 23:41.000 --> 23:41.800 session tomorrow? 23:41.800 --> 23:43.160 Do you come along to the social out? 23:43.160 --> 23:45.200 Am I even if you can? 23:45.200 --> 23:47.920 Find folks around Fosdam. 23:47.920 --> 23:49.160 Look them up on the Fedeverse. 23:49.160 --> 23:50.600 Ask questions. 23:50.600 --> 23:52.000 Oh, this is great. 23:52.000 --> 23:53.000 This is great. 23:54.000 --> 23:54.920 Oh yeah. 23:59.540 --> 24:00.800 Thank you very much.