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, thoughts 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 sit in there, what we're going to talk about, what they're going to talked 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 just talking about, what we're going to talk about, what we're going to talk about, what we were 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 should talk about, what we should talk about, 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 ID Connect for the authentication, 13:59.000 --> 14:02.000 all the others I've been mentioned before. 14:02.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:20.000 And the technology are, so we need a framework. 14:20.000 --> 14:24.000 So, it's not Django, it's not really a noise, but it's Phoenix. 14:24.000 --> 14:28.000 It's based on the go-in-ice language, which is Elixir, 14:28.000 --> 14:34.000 looks a lot like Ruby, but it's on top of the air-long open telecom platform. 14:34.000 --> 14:36.000 So, the open telecom platform, if you don't know it, 14:36.000 --> 14:41.000 it's what is used in the telecom, like it says, 14:41.000 --> 14:43.000 and also on what's up. 14:43.000 --> 14:47.000 And each time you want billions of people talking together, 14:47.000 --> 14:51.000 you have the open telecom platform behind. 14:51.000 --> 14:56.000 For the persistence, we use post-gray, and for the front end, 14:56.000 --> 14:59.000 we use UGS and TypeScript. 14:59.000 --> 15:03.000 We glue with this thing with a lot of libraries, 15:03.000 --> 15:08.000 and then everything is working, so you can come and contribute. 15:08.000 --> 15:11.000 It will be easy. 15:11.000 --> 15:14.000 Since we want people to be able to self-host, 15:14.000 --> 15:20.000 we have prepared, we try to make things easy for people 15:20.000 --> 15:24.000 at least running on Linux, and you have some package for Docker, 15:24.000 --> 15:26.000 for Debian Fedora. 15:26.000 --> 15:28.000 You have package, I don't know, it fits well, 15:28.000 --> 15:31.000 but you have a package for Unhost. 15:31.000 --> 15:34.000 Thank you very much. 15:34.000 --> 15:37.000 And if you have something more exotic, 15:37.000 --> 15:40.000 you can still be from source, but at least you have all those package, 15:40.000 --> 15:44.000 like we'll help you to go fast. 15:44.000 --> 15:48.000 This one I will be very quick, but like I said, 15:48.000 --> 15:52.000 we don't just confate to be empty when you come on the platform, 15:52.000 --> 15:55.000 so we use the open data from our governments. 15:55.000 --> 16:01.000 It's mainly in France, but we have probably 200,000 events 16:01.000 --> 16:04.000 in the France at any time, so if you will, 16:04.000 --> 16:07.000 to a small village, you will have at least some events 16:07.000 --> 16:12.000 for your next weekend. 16:12.000 --> 16:15.000 So that's it for the technical part, 16:15.000 --> 16:19.000 and I end over Alex for the future. 16:19.000 --> 16:23.000 So we're done with icons. 16:23.000 --> 16:29.000 So as I've said, we have been granted a phone 16:29.000 --> 16:31.000 by NLNet last year. 16:31.000 --> 16:34.000 It was for this year, right, 2024, 16:34.000 --> 16:38.000 which was great, so we could transition from 16:38.000 --> 16:42.000 from our self to maintaining ourselves. 16:42.000 --> 16:46.000 And what we did is that we abstrained 16:46.000 --> 16:51.000 what had been developed aside of the main branch, 16:51.000 --> 16:55.000 and that was really great to have that support, 16:55.000 --> 16:59.000 and also skill developers that jumped in. 17:00.000 --> 17:03.000 And now we can look forward, 17:03.000 --> 17:06.000 and think of what we want to do next, 17:06.000 --> 17:12.000 develop new features, so in 2025 and beyond. 17:12.000 --> 17:18.000 We'd like everybody to be able to use mobilization 17:18.000 --> 17:21.000 and create local and thematic instances. 17:21.000 --> 17:24.000 So our dream would be that anywhere in the world, 17:24.000 --> 17:28.000 when there's a local initiative, it's on mobilization, 17:28.000 --> 17:32.000 because it's created there or built there by interoperability. 17:32.000 --> 17:35.000 But if we just start with our neighborhood or 17:35.000 --> 17:38.000 our nearby streets, that's good. 17:38.000 --> 17:41.000 So we'd like to offer hosting services 17:41.000 --> 17:45.000 and develop the community of users and contributors. 17:45.000 --> 17:51.000 And also to define what to do with the new branch, 17:51.000 --> 17:55.000 we got from NLNet to go forward, 17:55.000 --> 18:00.000 we'd like to involve mostly instance administrator, 18:00.000 --> 18:05.000 but also end users to give their ideas and help together 18:05.000 --> 18:10.000 to define what's the most meaningful to deliver to the community, 18:10.000 --> 18:13.000 basically refine and prioritize the backlog, 18:13.000 --> 18:16.000 and finally a little bit because we know we cannot do 18:16.000 --> 18:19.000 at once everything we'd like to do. 18:19.000 --> 18:23.000 So there are two things we'd like to do 18:23.000 --> 18:26.000 is to improve the quality. 18:26.000 --> 18:30.000 So as quality, I think of UX accessibility, 18:30.000 --> 18:37.000 performance, fixing bugs, improving the tests and the security. 18:37.000 --> 18:42.000 And then there are the features we would like to develop as well. 18:42.000 --> 18:47.000 And we'll see also what comes from the other people 18:47.000 --> 18:51.000 that we'll have on the change advisory board 18:51.000 --> 18:53.000 that we're trying to build. 18:53.000 --> 18:58.000 So we have an open call for that. 18:58.000 --> 19:02.000 So what we've been thinking of and also we 19:02.000 --> 19:06.000 received a feedback from the community that 19:06.000 --> 19:10.000 would be nice to have, would be to be able to link groups 19:10.000 --> 19:12.000 with one another. 19:12.000 --> 19:16.000 So they can kind of federate groups with one another 19:16.000 --> 19:19.000 and also display events that come from other groups 19:19.000 --> 19:22.000 not only from your own. 19:22.000 --> 19:24.000 Improved participation management, 19:24.000 --> 19:30.000 so take multiple places to an event and manage a weighting list. 19:30.000 --> 19:33.000 And there are a group members to see who participates 19:33.000 --> 19:36.000 to group events that's not there yet. 19:36.000 --> 19:40.000 Have a new search dimension that would be for the audience 19:40.000 --> 19:43.000 for a group is events. 19:44.000 --> 19:48.000 Annable instance administrator to moderate user account 19:48.000 --> 19:52.000 creation for spam and also in case you don't want to open 19:52.000 --> 19:55.000 registration to everybody. 19:55.000 --> 19:58.000 Annable instance admin also to manage a bit more 19:58.000 --> 20:02.000 the homepage and be able to pin posts and events 20:02.000 --> 20:05.000 or groups on the homepage. 20:05.000 --> 20:08.000 Have some kind of instance ball. 20:08.000 --> 20:12.000 So not all of people but all of the instance with everything 20:12.000 --> 20:15.000 that is new like a news feed for the instance, 20:15.000 --> 20:20.000 new posts, new events, new groups created. 20:20.000 --> 20:24.000 Small one have mobile apps available on stalls. 20:24.000 --> 20:28.000 And also we would like to have auto generated newsletter 20:28.000 --> 20:33.000 either at instance level, like here are the upcoming events 20:33.000 --> 20:35.000 for the two coming weeks for instance. 20:35.000 --> 20:37.000 Or maybe at group level. 20:37.000 --> 20:39.000 If we can make that we can make that a group 20:39.000 --> 20:43.000 event and it comes in somebody's mailbox. 20:43.000 --> 20:52.000 And we would like to info federation so that we can so 20:52.000 --> 20:55.000 for now if one instance for follow another one 20:55.000 --> 20:57.000 it receives all the contents. 20:57.000 --> 21:00.000 Sometimes it's relevant sometimes not. 21:00.000 --> 21:03.000 So we would like to enable instance to only share 21:03.000 --> 21:06.000 a selection of events. 21:06.000 --> 21:10.000 So maybe for we should have the instance administrator 21:10.000 --> 21:14.000 that decides which instances he federates with 21:14.000 --> 21:18.000 that are open to communicate with each other. 21:18.000 --> 21:21.000 And then it could be like users that push 21:21.000 --> 21:23.000 content on those other instance. 21:23.000 --> 21:26.000 Or on those that were on that pools. 21:26.000 --> 21:28.000 What's interesting for them. 21:28.000 --> 21:31.000 So we would love to have this kind of organic growth 21:31.000 --> 21:33.000 of instance content. 21:34.000 --> 21:37.000 But that's quite a big change. 21:37.000 --> 21:41.000 There are lots of use cases to consider. 21:41.000 --> 21:44.000 And also we need users and instance administrators 21:44.000 --> 21:46.000 to keep in control. 21:46.000 --> 21:50.000 We really think it would be like. 21:50.000 --> 21:53.000 Or you valuable thing to have in mobilization 21:53.000 --> 21:58.000 that makes it maybe more interesting than mainstream websites 21:58.000 --> 22:00.000 that exist today. 22:01.000 --> 22:04.000 So I hope you have a good feeling now about mobilization. 22:04.000 --> 22:07.000 If you want to support it there are two things you can do 22:07.000 --> 22:09.000 that are very easy. 22:09.000 --> 22:12.000 It's communicate about it and use it. 22:12.000 --> 22:15.000 So you can think of what you can do. 22:15.000 --> 22:19.000 Maybe talk to one person about mobilization after you live. 22:19.000 --> 22:21.000 And maybe find an instance. 22:21.000 --> 22:25.000 You would like to you can post on there are many available. 22:25.000 --> 22:30.000 And post on events just to try out. 22:30.000 --> 22:33.000 Thanks. 22:33.000 --> 22:35.000 Thank you. 22:35.000 --> 22:43.000 So we have one question online. 22:43.000 --> 22:46.000 And I know there's people in the audience at one 22:46.000 --> 22:47.000 to ask questions as well. 22:47.000 --> 22:50.000 So I'm going to ask you to find the somewhere else 22:50.000 --> 22:52.000 because we'll want to move on after this. 22:53.000 --> 22:55.000 So the question I have from Matrix is, 22:55.000 --> 22:58.000 what about attendance information for the event? 22:58.000 --> 23:02.000 If I sign up to an event, will that be public information? 23:02.000 --> 23:05.000 No, go and leave. 23:05.000 --> 23:08.000 But you say you want to participate in trial events. 23:08.000 --> 23:09.000 It's not the public information. 23:09.000 --> 23:10.000 Okay. 23:10.000 --> 23:11.000 So that's not public. 23:11.000 --> 23:14.000 So thank you so much for coming and talking about mobilization. 23:14.000 --> 23:17.000 That was something that I wanted to know about as well. 23:17.000 --> 23:18.000 So this great. 23:18.000 --> 23:20.000 Thank you all for your patience. 23:21.000 --> 23:24.000 I know that we've had very tight scheduling. 23:24.000 --> 23:26.000 We honestly had so much great content. 23:26.000 --> 23:29.000 The event and I were really struggling to figure out how we could 23:29.000 --> 23:31.000 fit the talks together. 23:31.000 --> 23:33.000 So we really appreciate everybody moving in and out. 23:33.000 --> 23:37.000 And bearing with us that we haven't had really as great time for 23:37.000 --> 23:39.000 questions that we would have liked. 23:39.000 --> 23:41.000 But do come along to the birth of a feather. 23:41.000 --> 23:42.000 Group session tomorrow. 23:42.000 --> 23:44.000 Do come along to the social out. 23:44.000 --> 23:45.000 I'm already evening if you can. 23:45.000 --> 23:48.000 Find folks in the around fuzz dam. 23:48.000 --> 23:50.000 And look them up on the fettie verse. 23:50.000 --> 23:52.000 Ask questions. 23:52.000 --> 23:54.000 This is great. 23:54.000 --> 23:56.000 Thank you very much. 23:56.000 --> 24:00.000 Thank you very much.