WEBVTT 00:00.000 --> 00:11.000 So, welcome everyone. So, I'm Timote. I will show you a bit about the 00:11.000 --> 00:14.000 movie. So, one first question for the audience, who knows 00:14.000 --> 00:18.000 movie? Who are the heard of movie there? Okay, so we do have a few 00:18.000 --> 00:22.000 person that are aware of this thing. So, I'm also introducing the new 00:22.000 --> 00:26.000 logo, new design, new mascot and everything. I've been working with 00:26.000 --> 00:30.000 a good friend, it is doing all the drawing and design about that. 00:30.000 --> 00:33.000 And I will have a maybe stickers for the next fall 00:33.000 --> 00:38.000 them because it was a bit present, like those change. 00:38.000 --> 00:42.000 So, I'm Timote. I can also know me as Adelaas. 00:42.000 --> 00:47.000 And I'm being meeting movie since 2010. There was a lot of 00:47.000 --> 00:50.000 changes and evolutions back then. I was just learning 00:50.000 --> 00:57.000 about PhD and how to do web stuff and then I grew into the 00:57.000 --> 01:01.000 example because it's a PhD exam and now you will see what's the 01:01.000 --> 01:05.000 result after all those years. And I'm also, yeah, 01:05.000 --> 01:10.000 cooking, I like to cook like a kish. I think I don't always say 01:10.000 --> 01:15.000 in a language. So, what is the movie? The movie is actually 01:15.000 --> 01:19.000 a social platform that connects between the exam 01:19.000 --> 01:22.000 people world and the web world. On the exam 01:22.000 --> 01:25.000 people side, it's used to have some, we used to have an 01:25.000 --> 01:29.000 exam paper like web socket and HTTP request to directly do 01:29.000 --> 01:31.000 exam paper, but now it works like any exam paper 01:31.000 --> 01:33.000 client. So, you don't even have to configure anything. 01:33.000 --> 01:37.000 You just start moving and then connect with your credential 01:37.000 --> 01:40.000 and it will just connect any exam paper clients. 01:40.000 --> 01:43.000 And it provides you a real time interfacing your browser, 01:43.000 --> 01:46.000 browser that can also be put on your phone as a 01:46.000 --> 01:50.000 progressive web app. So, it's like a really kind of native app 01:50.000 --> 01:53.000 that's fully responsive. The goal of the movie is actually to 01:53.000 --> 01:57.000 create and expand all the social feature and a bit more 01:57.000 --> 02:02.000 you will see later on exam paper. And no, in 2025 and 02:02.000 --> 02:05.000 26 we'll start to see other clients. I was able to 02:05.000 --> 02:08.000 convince my friends about the fact that social 02:08.000 --> 02:11.000 features can also be interesting on the exam paper. 02:11.000 --> 02:15.000 So, there is three axes about Mavim. So, the social 02:15.000 --> 02:18.000 networking, as I said, the instant messaging, obviously 02:18.000 --> 02:22.000 because I will not prefer also to use all the 02:22.000 --> 02:26.000 awesome exam paper feature about instant messaging. 02:26.000 --> 02:29.000 And more recently, like the video conferencing feature. 02:29.000 --> 02:33.000 Because I saw that there was a lot of nice things to do 02:33.000 --> 02:37.000 on this part and actually a lot of people that were also 02:37.000 --> 02:41.000 looking for alternative teams or zoom and all those 02:41.000 --> 02:46.000 kind of platforms. So, technically, it's based on 02:46.000 --> 02:49.000 SAP HP, CSS and JavaScript. There is not a lot 02:49.000 --> 02:53.000 where React app is quite light and simple. 02:53.000 --> 02:57.000 Database-wise, polygraph-scale and MariaDB, but 02:57.000 --> 03:01.000 business-post-dress works way better. It's quite light 03:01.000 --> 03:06.000 and yeah, I do have about two releases per year. 03:06.000 --> 03:09.000 So, one question that comes quite often is, like, 03:09.000 --> 03:12.000 what actual difference between activity and 03:12.000 --> 03:16.000 exam paper and how social networks are working there? 03:16.000 --> 03:21.000 So, I made this little graph, like, two graphs to actually 03:21.000 --> 03:24.000 show you the difference. So, from my point of view, 03:24.000 --> 03:27.000 activity pub is more like a platform-first system. 03:27.000 --> 03:31.000 So, the activity pub protocol is actually defined 03:31.000 --> 03:35.000 between the platform. So, you create an account on the platform 03:35.000 --> 03:38.000 and then the platform through activity pub are 03:38.000 --> 03:41.000 interconnecting themselves and exchanging messages. 03:41.000 --> 03:44.000 So, basically, peer-tube will have to understand 03:44.000 --> 03:47.000 on top of activity pub. Okay, what master's is actually doing 03:47.000 --> 03:50.000 on those things and same with pixel feeds. 03:50.000 --> 03:53.000 So, it's like an Instagram-like activity pub system. 03:53.000 --> 03:57.000 An example is the other way around, actually. 03:57.000 --> 04:01.000 So, you have accounts and you do everything through 04:01.000 --> 04:06.000 your clients on your accounts. So, it's just a view of 04:06.000 --> 04:09.000 the XMPP network and then there is an 04:09.000 --> 04:12.000 interaction in the XMPP ecosystem. So, it means that all the 04:12.000 --> 04:15.000 interaction, the XMPP ecosystem are standardized. 04:15.000 --> 04:18.000 So, I will show you just after what a story is. 04:18.000 --> 04:21.000 A story on, it's not a modern story. 04:21.000 --> 04:25.000 It's an XMPP story. So, it's quite easy for a new client 04:25.000 --> 04:29.000 to just implement the startup and then be fully 04:29.000 --> 04:32.000 compatible with all the others. 04:32.000 --> 04:35.000 So, you see actually for the question that we had just 04:35.000 --> 04:37.000 before that we actually have an interaction between the 04:37.000 --> 04:39.000 servers. So, this is in the library and 04:39.000 --> 04:41.000 one of the main servers. So, what we call 04:41.000 --> 04:45.000 S2S server to server and client to server is 04:45.000 --> 04:47.000 what can be the same like email. You know, you have 04:47.000 --> 04:50.000 those email servers and then Thunderbird or Outlook 04:50.000 --> 04:53.000 connected to your servers and your account on the server. 04:53.000 --> 04:56.000 So, yeah, one of the drawback of I think 04:56.000 --> 05:00.000 activity is that, and I have this issue myself is that you 05:00.000 --> 05:02.000 have to create an account on all the platform. 05:02.000 --> 05:05.000 You basically have one account on MasterDone, 05:05.000 --> 05:08.000 it's a bit more difficult to find where actually your 05:08.000 --> 05:10.000 data is. And example, when you remove your 05:10.000 --> 05:13.000 account, you basically destroy all all your 05:13.000 --> 05:17.000 information in one unique place. 05:17.000 --> 05:22.000 So, what's new in a little story is a thing. 05:22.000 --> 05:25.000 So, what's was introduced in 2025? 05:25.000 --> 05:30.000 Pub sub stories. So, as I said, for those 05:30.000 --> 05:32.000 that were there for the previous presentation, 05:32.000 --> 05:35.000 it's just at 1.0 on Pubesubscribe. 05:35.000 --> 05:37.000 So, I will just repeat quickly what is 05:37.000 --> 05:41.000 Pubesubscribe is like a Pubesubscribe system. 05:41.000 --> 05:44.000 So, you create nodes on your account or on the network 05:44.000 --> 05:46.000 and then you publish information there and people 05:46.000 --> 05:49.000 subscribe to it and you can manage the node like 05:49.000 --> 05:52.000 configure it and put like another tower and all those things. 05:52.000 --> 05:55.000 And then the information is actually spread across 05:55.000 --> 05:57.000 the whole network in real time. 05:57.000 --> 06:01.000 And stories where actually came like last year and 06:01.000 --> 06:03.000 there is already two clients compatible. 06:03.000 --> 06:06.000 And I've talked with a couple of other clients that 06:06.000 --> 06:08.000 might be also interested to that stories. 06:08.000 --> 06:12.000 I see someone in the room that is there for that. 06:12.000 --> 06:18.000 So, just diving the protocol, that's actually a story. 06:18.000 --> 06:20.000 As you see, it's super simple. 06:20.000 --> 06:24.000 You just connect to your example piece error and you publish a story. 06:24.000 --> 06:26.000 So, I'm publishing a story to myself. 06:26.000 --> 06:29.000 So, this is me, oh, by the way, it's the mascot. 06:29.000 --> 06:34.000 So, you say, I can stop up sub item that you publish on 06:34.000 --> 06:38.000 the story node. So, your example piece actually namespace on the story. 06:38.000 --> 06:40.000 And then inside you are your item. 06:40.000 --> 06:44.000 It's just a simple atom item with a title. 06:44.000 --> 06:47.000 So, it's basically the little text that you have on your story. 06:47.000 --> 06:49.000 Some ID, some time. 06:49.000 --> 06:53.000 And obviously the picture of the story that you created on your clients. 06:53.000 --> 06:54.000 It's super simple. 06:54.000 --> 06:58.000 And if you want to make an error set for item field, 06:58.000 --> 07:00.000 a lot of that is directly. 07:00.000 --> 07:03.000 Just have to take your database and then recreate 07:03.000 --> 07:06.000 and another behind that. 07:06.000 --> 07:14.000 Something that also came in 2025 are the multi-party jingles. 07:14.000 --> 07:19.000 So, it's something that I did with the NLNet funding. 07:19.000 --> 07:21.000 So, really, thanks to them. 07:21.000 --> 07:26.000 I was able to respect a lot of time on this to really integrate 07:26.000 --> 07:29.000 in the web UI, all those features. 07:29.000 --> 07:33.000 So, it's, as I said, fully compatible with already another client 07:33.000 --> 07:37.000 or able to call with multiple person with desktop clients 07:37.000 --> 07:41.000 and a web clients easily. 07:41.000 --> 07:45.000 And I added also a similar to web cam and screen sharing. 07:45.000 --> 07:48.000 There is a little example that is coming from it to actually tag those things. 07:48.000 --> 07:50.000 So, you can actually share your screen. 07:50.000 --> 07:52.000 And your web cam at the same time. 07:52.000 --> 07:55.000 So, for a presentation like this, it's actually quite useful. 07:55.000 --> 07:58.000 Or you should be streaming, maybe, will have like a twitch light 07:58.000 --> 08:00.000 like system on volume after. 08:01.000 --> 08:03.000 It's where you see this. 08:03.000 --> 08:06.000 So, it works like just in all the browsers nowadays. 08:06.000 --> 08:09.000 And yeah, as I said, it's founded by NLNet. 08:09.000 --> 08:12.000 So, yeah, that's the mobile versions. 08:12.000 --> 08:17.000 And yeah, I will tell you a bit more about that for, for 26. 08:19.000 --> 08:25.000 What's actually came in 2025 is the improved social flow. 08:25.000 --> 08:30.000 So, yeah, I actually created a new step that was upgrading 08:30.000 --> 08:33.000 a really old one that was called micro-blugging. 08:33.000 --> 08:35.000 Because for 15 years in example, 08:35.000 --> 08:39.000 the only kind of thing that was about social feature was micro-blugging. 08:39.000 --> 08:40.000 There was a micro-blugging example. 08:40.000 --> 08:43.000 So, I said, let's take this thing, make it more general 08:43.000 --> 08:45.000 and call it purpose social feature. 08:45.000 --> 08:47.000 So, it's like a more generic jet to say, 08:47.000 --> 08:50.000 okay, you put a tool on Pubsebb. 08:50.000 --> 08:54.000 And stories, the stories are one of the subting of this thing. 08:54.000 --> 08:56.000 Of this, perhaps, sub-sub-social feature. 08:56.000 --> 08:58.000 So, it's stories, basically, perhaps, 08:58.000 --> 08:59.000 such a field class. 08:59.000 --> 09:03.000 You must publish one picture at least in your item, 09:03.000 --> 09:06.000 because a stories, obviously, one picture. 09:06.000 --> 09:11.000 So, it's super easy to make it extensible 09:11.000 --> 09:14.000 and add new exhibits on top of that. 09:14.000 --> 09:17.000 And to implement a same thing, like you just need, 09:17.000 --> 09:21.000 like a simple XML parser database, and then you're done. 09:21.000 --> 09:24.000 Something that was added in 2025 09:24.000 --> 09:26.000 is to follow with everyone. 09:26.000 --> 09:29.000 Because you used to have this system where actually, 09:29.000 --> 09:32.000 you need to add the person as a friend to actually follow it. 09:32.000 --> 09:35.000 And now there is just a follow button follow and follow. 09:35.000 --> 09:41.000 And I open a couple of tickets in the XMPP servers 09:41.000 --> 09:44.000 to ask them about Pubsebb missing feature. 09:44.000 --> 09:46.000 Basically, it's the follow-over feature. 09:46.000 --> 09:49.000 For now, you see some of the follow-over, 09:49.000 --> 09:51.000 but you are not notified about it, 09:51.000 --> 09:53.000 and you don't have the counter of follow-over. 09:53.000 --> 09:55.000 So, if you are an influencer, 09:55.000 --> 09:56.000 and you want to come to XMPP, 09:56.000 --> 09:59.000 you will be happy to have the follow-over counter soon. 09:59.000 --> 10:01.000 Yeah, there are comments and likes, 10:01.000 --> 10:03.000 will be, as being a redesign. 10:03.000 --> 10:05.000 And I introduced the briefs, 10:05.000 --> 10:07.000 which is basically like, 10:07.000 --> 10:10.000 an art, because in a movie, 10:10.000 --> 10:12.000 you were publishing articles with a title, 10:12.000 --> 10:14.000 and a content, and people that were, 10:14.000 --> 10:17.000 like a incident or other social network like this, 10:17.000 --> 10:19.000 I wanted, like, just, I want to post one text. 10:19.000 --> 10:22.000 So, a brief is, like, a smaller, like, article 10:22.000 --> 10:25.000 that you can just easily publish. 10:25.000 --> 10:27.000 Uh, chat. 10:27.000 --> 10:30.000 Yeah, so I did not only work on a social feature, 10:30.000 --> 10:32.000 I also work on a, 10:32.000 --> 10:33.000 uh, I am feature. 10:33.000 --> 10:35.000 So, there is a message, 10:35.000 --> 10:36.000 which is to research for content. 10:36.000 --> 10:38.000 So, that's thanks to poserscule 10:38.000 --> 10:40.000 that can easily index content, 10:40.000 --> 10:42.000 and you can just type any keyword, 10:42.000 --> 10:44.000 and such, you whole history, 10:44.000 --> 10:46.000 works with, like, millions of messages. 10:46.000 --> 10:47.000 This is quite impressive. 10:47.000 --> 10:49.000 Uh, there is a new navigation bar, 10:49.000 --> 10:51.000 so on the right there. 10:51.000 --> 10:53.000 Uh, you actually have, like, 10:53.000 --> 10:54.000 all the connected person, 10:54.000 --> 10:56.000 and you can click, click on them, 10:56.000 --> 10:58.000 like, send them a private message, 10:58.000 --> 10:59.000 like, things that you see, 10:59.000 --> 11:01.000 you saw on a many other applied, 11:01.000 --> 11:02.000 a social platform. 11:02.000 --> 11:05.000 Uh, I work on a year resolver, 11:05.000 --> 11:06.000 so that's a little, 11:06.000 --> 11:08.000 technical thing. 11:08.000 --> 11:10.000 Uh, because on movie, 11:10.000 --> 11:13.000 so when you start a movie in instance, 11:14.000 --> 11:15.000 uh, 11:15.000 --> 11:17.000 a bunch of people can connect on this instance, 11:17.000 --> 11:18.000 so you can have, like, 11:18.000 --> 11:20.000 20 person that are connected on one of your instance, 11:20.000 --> 11:23.000 and those 20 person can be in the same chatroom, 11:23.000 --> 11:24.000 obviously. 11:24.000 --> 11:26.000 So, if someone is sending a URL, 11:26.000 --> 11:27.000 uh, 11:27.000 --> 11:28.000 it's used to have, like, 11:28.000 --> 11:30.000 all those person requesting their URL 11:30.000 --> 11:31.000 to have this little card. 11:31.000 --> 11:33.000 So, the poor guy that actually have the, 11:33.000 --> 11:35.000 the web server will have, like, 11:35.000 --> 11:36.000 20 requests. 11:36.000 --> 11:38.000 So, no, there is a worker for that, 11:38.000 --> 11:40.000 that you can just send a menu URL 11:41.000 --> 11:42.000 will resolve the card, 11:42.000 --> 11:44.000 and actually give it only once to, 11:44.000 --> 11:45.000 like, everyone. 11:45.000 --> 11:46.000 It works really well, 11:46.000 --> 11:47.000 and really, really help, 11:47.000 --> 11:49.000 especially when you load this story, 11:49.000 --> 11:50.000 and you have, like, 11:50.000 --> 11:51.000 you know, like, 11:51.000 --> 11:53.000 a lot of means that we're share or things like that, 11:53.000 --> 11:54.000 and you know, 11:54.000 --> 11:57.000 you have, like, a 50 year old to a result. 11:57.000 --> 11:58.000 Uh, there is a, 11:58.000 --> 12:00.000 negation flow that was, uh, 12:00.000 --> 12:01.000 yeah, quite improved, 12:01.000 --> 12:03.000 like, a special mobile. 12:03.000 --> 12:05.000 It's quite difficult to pack all those, 12:05.000 --> 12:07.000 social and IM features, 12:07.000 --> 12:08.000 so there was, like, 12:09.000 --> 12:12.000 mostly, like, touch feature 12:12.000 --> 12:14.000 that we're introduced to actually make it, 12:14.000 --> 12:16.000 like, more easy to work. 12:16.000 --> 12:18.000 And a little thing that I was added, 12:18.000 --> 12:19.000 at the end of the year, 12:19.000 --> 12:20.000 uh, is shortcuts. 12:20.000 --> 12:23.000 Uh, something that you have in this code, 12:23.000 --> 12:25.000 I think, is basically, like, 12:25.000 --> 12:26.000 on the left bar, 12:26.000 --> 12:27.000 if someone is, like, 12:27.000 --> 12:28.000 you know, 12:28.000 --> 12:29.000 or you are coated in a, 12:29.000 --> 12:30.000 in a chat room, 12:30.000 --> 12:31.000 you can easily have, like, 12:31.000 --> 12:33.000 this quick button that you click 12:33.000 --> 12:34.000 to go directly to the, 12:34.000 --> 12:36.000 to the, 12:37.000 --> 12:39.000 the conversation. 12:39.000 --> 12:41.000 Um, 12:41.000 --> 12:42.000 yeah, 12:42.000 --> 12:44.000 there was also many other things. 12:44.000 --> 12:45.000 So as I said, 12:45.000 --> 12:46.000 uh, 12:46.000 --> 12:47.000 I'm still using, 12:47.000 --> 12:48.000 I'm still supporting my IDB, 12:48.000 --> 12:50.000 but I dropped my SQL 12:50.000 --> 12:52.000 because those two of the bases were coming this way, 12:52.000 --> 12:53.000 and I, it was, like, 12:53.000 --> 12:54.000 too much work, 12:54.000 --> 12:55.000 and I actually, 12:55.000 --> 12:56.000 and I didn't add a lot of 12:56.000 --> 12:57.000 person as well using my SQL, 12:57.000 --> 12:58.000 so, 12:58.000 --> 12:59.000 please move to my RDB or 12:59.000 --> 13:01.000 positive SQL for that. 13:01.000 --> 13:02.000 Uh, 13:02.000 --> 13:03.000 it was upgraded to PHP, 13:04.000 --> 13:06.000 the two that actually improve 13:06.000 --> 13:08.000 a bit the performances. 13:08.000 --> 13:09.000 Uh, 13:09.000 --> 13:10.000 there was a fully refactor 13:10.000 --> 13:11.000 notification system, 13:11.000 --> 13:13.000 because a movie is actually doing 13:13.000 --> 13:14.000 web push. 13:14.000 --> 13:15.000 You can have push notification 13:15.000 --> 13:17.000 and your phone on your devices. 13:17.000 --> 13:18.000 Uh, and, yeah, 13:18.000 --> 13:19.000 now it works really well. 13:19.000 --> 13:20.000 You have the, 13:20.000 --> 13:21.000 the conversation. 13:21.000 --> 13:22.000 If you actually read on one, 13:22.000 --> 13:24.000 one of your browser, 13:24.000 --> 13:25.000 actually clear the notification 13:25.000 --> 13:27.000 because you read it and all these kind of things. 13:27.000 --> 13:28.000 Uh, 13:28.000 --> 13:29.000 I added the programs in the profiles. 13:29.000 --> 13:30.000 Uh, 13:30.000 --> 13:31.000 I saw that it was, 13:31.000 --> 13:34.000 and a new RFC with new kind of things in the 13:34.000 --> 13:35.000 vehicle. 13:35.000 --> 13:36.000 I said, 13:36.000 --> 13:37.000 why not? 13:37.000 --> 13:39.000 And I have a friend that is actually doing, 13:39.000 --> 13:40.000 um, 13:40.000 --> 13:41.000 well, 13:41.000 --> 13:42.000 uh, 13:42.000 --> 13:43.000 that is actually doing a bridge. 13:43.000 --> 13:44.000 And we work quite, 13:44.000 --> 13:45.000 uh, 13:45.000 --> 13:46.000 a lot together, 13:46.000 --> 13:47.000 the, 13:47.000 --> 13:48.000 the last year, 13:48.000 --> 13:50.000 with bridging with the telegram, 13:50.000 --> 13:51.000 WhatsApp, 13:51.000 --> 13:52.000 discord, 13:52.000 --> 13:53.000 and a couple of other networks. 13:53.000 --> 13:54.000 And those have, 13:54.000 --> 13:56.000 I'd like those kind of information, 13:56.000 --> 13:57.000 actually, 13:57.000 --> 13:58.000 why not to actually show it in the movie 13:58.000 --> 14:00.000 UI and fully stand out. 14:00.000 --> 14:01.000 Uh, 14:01.000 --> 14:03.000 I'm using the material design from Google, 14:03.000 --> 14:04.000 actually to do the whole implementation. 14:04.000 --> 14:06.000 So I did an upgrade to the latest one. 14:06.000 --> 14:08.000 And I redesigned the movie, 14:08.000 --> 14:09.000 but you and joined the movie, 14:09.000 --> 14:10.000 but you. 14:10.000 --> 14:11.000 So join movie, 14:11.000 --> 14:12.000 but you is a bit like the, 14:12.000 --> 14:13.000 the, 14:13.000 --> 14:14.000 join, 14:14.000 --> 14:15.000 I think, 14:15.000 --> 14:16.000 page to basically if you have, 14:16.000 --> 14:17.000 uh, 14:17.000 --> 14:18.000 a movie instance, 14:18.000 --> 14:20.000 you can easily register your instance on this page. 14:20.000 --> 14:22.000 And then someone that is like, 14:22.000 --> 14:23.000 want to join the movie, 14:23.000 --> 14:24.000 that what actually, 14:24.000 --> 14:25.000 see like many instances, 14:25.000 --> 14:26.000 and can pick one, 14:26.000 --> 14:27.000 uh, 14:27.000 --> 14:29.000 it wants based on the location or like, 14:30.000 --> 14:31.000 specific aspects. 14:33.000 --> 14:35.000 Okay, what news for 26, 14:35.000 --> 14:37.000 because I'm will not stop there. 14:37.000 --> 14:39.000 I will do more stuff. 14:39.000 --> 14:40.000 Uh, 14:40.000 --> 14:41.000 this is a technical thing. 14:41.000 --> 14:42.000 Uh, 14:42.000 --> 14:45.000 the movie architecture is full real time. 14:45.000 --> 14:46.000 So yeah, 14:46.000 --> 14:47.000 I'm actually doing a full, 14:47.000 --> 14:49.000 full real time things in PHP, 14:49.000 --> 14:50.000 and it works really well. 14:50.000 --> 14:52.000 But I used to have like, 14:52.000 --> 14:53.000 10 years ago, 14:53.000 --> 14:54.000 uh, 14:54.000 --> 14:55.000 like blocking code. 14:55.000 --> 14:56.000 No, 14:56.000 --> 14:58.000 it's clearly a request that where like, 14:58.000 --> 15:00.000 a bit along or like, 15:00.000 --> 15:02.000 resolving URL and things like that. 15:02.000 --> 15:04.000 And if you put everyone on the same, 15:04.000 --> 15:05.000 like, 15:05.000 --> 15:06.000 process with blocking codes, 15:06.000 --> 15:08.000 then if one guy is joining, 15:08.000 --> 15:10.000 is connecting on moving with, 15:10.000 --> 15:11.000 and a lot of, 15:11.000 --> 15:12.000 and all friends, 15:12.000 --> 15:13.000 and a lot of synchronization today, 15:13.000 --> 15:15.000 will slow down everyone else. 15:15.000 --> 15:17.000 So what I did back then, 15:17.000 --> 15:18.000 I was a bit like, 15:18.000 --> 15:19.000 I had a simple solution to say, 15:19.000 --> 15:20.000 okay, 15:20.000 --> 15:21.000 everyone is actually having a PHP process, 15:21.000 --> 15:22.000 and I had a, 15:22.000 --> 15:23.000 uh, 15:23.000 --> 15:24.000 uh, 15:24.000 --> 15:26.000 and that actually routes everything. 15:26.000 --> 15:28.000 That works really well for 10, 15:28.000 --> 15:29.000 15 years, 15:29.000 --> 15:30.000 but the thing is like, 15:30.000 --> 15:31.000 each PHP process is actually 15:31.000 --> 15:32.000 copy, 15:32.000 --> 15:34.000 pasting a lot of information, 15:34.000 --> 15:35.000 like the whole movie, 15:35.000 --> 15:36.000 uh, 15:36.000 --> 15:37.000 uh, 15:37.000 --> 15:38.000 uh, 15:38.000 --> 15:39.000 the whole movie, 15:39.000 --> 15:40.000 a system in memory. 15:40.000 --> 15:41.000 So no, 15:41.000 --> 15:42.000 I'm actually introducing 15:42.000 --> 15:43.000 into the 2006, 15:43.000 --> 15:44.000 uh, 15:44.000 --> 15:45.000 in between system, 15:45.000 --> 15:47.000 where actually people are, 15:47.000 --> 15:48.000 uh, 15:48.000 --> 15:49.000 you have worker, 15:49.000 --> 15:51.000 where you have five to ten people on those worker, 15:51.000 --> 15:53.000 because the code was optimized, 15:53.000 --> 15:55.000 and you're looking anymore for a lot of things. 15:55.000 --> 15:57.000 So you can actually share, 15:57.000 --> 15:58.000 uh, a process, 15:58.000 --> 15:59.000 uh, 15:59.000 --> 16:00.000 between other person. 16:00.000 --> 16:01.000 So that's why I say, 16:01.000 --> 16:03.000 80% of the summary is just because there is five 16:03.000 --> 16:05.000 percent on each worker or ten, 16:05.000 --> 16:06.000 and not one only. 16:06.000 --> 16:07.000 Uh, 16:07.000 --> 16:08.000 and I, 16:08.000 --> 16:09.000 I did some tests, 16:09.000 --> 16:11.000 and the performance impact was minimal, 16:11.000 --> 16:12.000 and actually you can, 16:12.000 --> 16:13.000 yes, 16:13.000 --> 16:14.000 save up a lot of memory, 16:14.000 --> 16:15.000 uh, 16:15.000 --> 16:16.000 this way. 16:16.000 --> 16:17.000 So I'm not having, 16:17.000 --> 16:18.000 like, five kilobytes, 16:18.000 --> 16:19.000 like, 16:19.000 --> 16:20.000 like, 16:20.000 --> 16:22.000 like, 16:22.000 --> 16:24.000 especially for smart server. 16:24.000 --> 16:27.000 And we all know how the RAM price is now, 16:27.000 --> 16:28.000 so it's always good to have, 16:28.000 --> 16:29.000 like, 16:29.000 --> 16:30.000 a little optimization on this, 16:30.000 --> 16:31.000 uh, 16:31.000 --> 16:32.000 this part. 16:32.000 --> 16:33.000 Uh, 16:33.000 --> 16:34.000 So what's news is, 16:34.000 --> 16:35.000 uh, 16:35.000 --> 16:36.000 also on the video conference, 16:36.000 --> 16:37.000 in part, 16:37.000 --> 16:38.000 is the last step of the NLNet, 16:38.000 --> 16:39.000 uh, 16:39.000 --> 16:40.000 uh, 16:40.000 --> 16:41.000 funding that, uh, 16:41.000 --> 16:42.000 hired. 16:42.000 --> 16:43.000 Uh, 16:43.000 --> 16:44.000 So I had three steps on this funding. 16:44.000 --> 16:46.000 The first one was to just modernize the, 16:46.000 --> 16:47.000 uh, 16:47.000 --> 16:48.000 uh, 16:48.000 --> 16:49.000 video calling system. 16:49.000 --> 16:50.000 The second one was to, 16:50.000 --> 16:51.000 uh, 16:52.000 --> 16:54.000 the third step is actually to either, 16:54.000 --> 16:55.000 as a few. 16:55.000 --> 16:56.000 So, uh, 16:56.000 --> 16:57.000 who is, 16:57.000 --> 16:58.000 who knows about as a few, 16:58.000 --> 17:00.000 who need to go to the technical there. 17:00.000 --> 17:01.000 Okay. 17:01.000 --> 17:03.000 So as a few is basically, 17:03.000 --> 17:04.000 normally, 17:04.000 --> 17:05.000 on the, 17:05.000 --> 17:06.000 the current system is like this. 17:06.000 --> 17:08.000 So if you call five friends in a room, 17:08.000 --> 17:09.000 like, 17:09.000 --> 17:10.000 you're sending five time, 17:10.000 --> 17:12.000 your video stream to everyone. 17:12.000 --> 17:13.000 So you see for two, 17:13.000 --> 17:14.000 three person, 17:14.000 --> 17:15.000 it works for audio, 17:15.000 --> 17:16.000 it works well, 17:16.000 --> 17:17.000 well, 17:17.000 --> 17:18.000 quite well up to 10 person, 17:18.000 --> 17:19.000 I think. 17:19.000 --> 17:20.000 But you see that, 17:20.000 --> 17:21.000 it's not possible, 17:21.000 --> 17:22.000 especially on your mobile, 17:22.000 --> 17:23.000 you will send, 17:23.000 --> 17:24.000 like, a lot of data for, 17:24.000 --> 17:25.000 for nothing. 17:25.000 --> 17:27.000 So as a few is quite simple, 17:27.000 --> 17:28.000 is that you actually have, 17:28.000 --> 17:29.000 like, 17:29.000 --> 17:30.000 one server that takes the video 17:30.000 --> 17:31.000 streams. 17:31.000 --> 17:33.000 And sometimes we compress it, 17:33.000 --> 17:34.000 sometimes we mix it, 17:34.000 --> 17:35.000 sometimes like, 17:35.000 --> 17:36.000 yeah, 17:36.000 --> 17:37.000 do some work with it, 17:37.000 --> 17:38.000 and then send it to the others. 17:38.000 --> 17:39.000 So then you have, 17:39.000 --> 17:40.000 like, 17:40.000 --> 17:41.000 a minimal impact on that. 17:41.000 --> 17:42.000 Uh, 17:42.000 --> 17:43.000 so for this part, 17:43.000 --> 17:44.000 actually, 17:44.000 --> 17:45.000 I'm not, 17:45.000 --> 17:46.000 uh, 17:46.000 --> 17:47.000 writing it, 17:47.000 --> 17:49.000 I'm using, like, 17:49.000 --> 17:50.000 an online, 17:50.000 --> 17:52.000 that is a really well made, 17:52.000 --> 17:53.000 as a few in a go. 17:53.000 --> 17:54.000 And then, 17:54.000 --> 17:55.000 there will, 17:55.000 --> 17:56.000 it will be wrapped in a, 17:56.000 --> 17:57.000 jingle, 17:57.000 --> 17:58.000 uh, 17:58.000 --> 17:59.000 an example, 17:59.000 --> 18:00.000 and then, 18:00.000 --> 18:01.000 uh, 18:01.000 --> 18:02.000 we will work with movie, 18:02.000 --> 18:03.000 and the nice thing, 18:03.000 --> 18:04.000 because there will be a standard about that, 18:04.000 --> 18:06.000 it means that other clients can easily 18:06.000 --> 18:07.000 reuse that, 18:07.000 --> 18:08.000 plug them to their example, 18:08.000 --> 18:10.000 and then do video conferencing, 18:10.000 --> 18:11.000 massively, 18:11.000 --> 18:12.000 uh, 18:12.000 --> 18:13.000 with, 18:13.000 --> 18:14.000 with example. 18:14.000 --> 18:15.000 So you have a little, 18:15.000 --> 18:16.000 uh, 18:16.000 --> 18:17.000 screenshots of, 18:17.000 --> 18:19.000 the best of you of this video, 18:19.000 --> 18:20.000 uh, 18:20.000 --> 18:21.000 called system. 18:21.000 --> 18:22.000 And the goal, 18:22.000 --> 18:23.000 also of movie, 18:23.000 --> 18:25.000 is that it's easy to deploy. 18:25.000 --> 18:26.000 Uh, 18:26.000 --> 18:27.000 if some of you are, 18:27.000 --> 18:28.000 deploy like at gc, 18:28.000 --> 18:29.000 system, 18:29.000 --> 18:30.000 it works quite well, 18:30.000 --> 18:31.000 but you have a lot of blocks 18:31.000 --> 18:32.000 to connect to each other. 18:32.000 --> 18:33.000 Movie, 18:33.000 --> 18:34.000 the goal to that is like, 18:34.000 --> 18:35.000 you just, 18:35.000 --> 18:36.000 and still, 18:36.000 --> 18:37.000 the movie projects, 18:37.000 --> 18:38.000 start a demon, 18:38.000 --> 18:39.000 and automatically, 18:39.000 --> 18:41.000 you have all those features, 18:41.000 --> 18:43.000 uh, 18:43.000 --> 18:44.000 built in. 18:44.000 --> 18:45.000 And the big thing that is, 18:45.000 --> 18:47.000 the space is, 18:47.000 --> 18:48.000 uh, 18:48.000 --> 18:49.000 uh, 18:49.000 --> 18:50.000 just to introduce spaces, 18:50.000 --> 18:51.000 I think, 18:51.000 --> 18:53.000 there is that already on many other things, 18:53.000 --> 18:54.000 including matrix. 18:54.000 --> 18:55.000 Uh, 18:55.000 --> 18:57.000 it's basically to group chat room together, 18:57.000 --> 18:58.000 to have like, 18:58.000 --> 18:59.000 not only one room, 18:59.000 --> 19:00.000 but, uh, 19:00.000 --> 19:01.000 group of rooms, 19:01.000 --> 19:02.000 where, 19:02.000 --> 19:03.000 um, 19:03.000 --> 19:04.000 an illustrator, 19:04.000 --> 19:05.000 uh, 19:05.000 --> 19:06.000 can actually play with them. 19:06.000 --> 19:08.000 So there was already some work done, 19:08.000 --> 19:09.000 and we are, 19:09.000 --> 19:10.000 like, 19:10.000 --> 19:11.000 kind of, 19:11.000 --> 19:12.000 a working, 19:12.000 --> 19:14.000 uh, 19:15.000 --> 19:17.000 the good thing is that it's fully retractable, 19:17.000 --> 19:18.000 so for, 19:18.000 --> 19:19.000 for the many example, 19:19.000 --> 19:20.000 clients that don't do that, 19:20.000 --> 19:21.000 you can actually join, 19:21.000 --> 19:23.000 some of the room of the whole, 19:23.000 --> 19:24.000 like, 19:24.000 --> 19:25.000 space easily. 19:25.000 --> 19:26.000 Um, 19:26.000 --> 19:28.000 and one of the first goals that I have in 19:28.000 --> 19:29.000 movie with this, 19:29.000 --> 19:31.000 is not read to build the whole discord, 19:31.000 --> 19:32.000 or, 19:32.000 --> 19:33.000 matrix system, 19:33.000 --> 19:34.000 but actually to have those, 19:34.000 --> 19:35.000 uh, 19:35.000 --> 19:37.000 chat room where you have audio and video room, 19:37.000 --> 19:38.000 below it, 19:38.000 --> 19:39.000 like you have on, 19:39.000 --> 19:40.000 uh, 19:40.000 --> 19:41.000 uh, 19:41.000 --> 19:43.000 uh, 19:43.000 --> 19:44.000 audio of your room, 19:44.000 --> 19:45.000 so it will be a small space, 19:45.000 --> 19:46.000 and then after that, 19:46.000 --> 19:47.000 it will expand on it, 19:47.000 --> 19:48.000 so it will basically mix the, 19:48.000 --> 19:49.000 as a few system, 19:49.000 --> 19:51.000 and the space system together, 19:51.000 --> 19:52.000 and, 19:52.000 --> 19:53.000 yeah, 19:53.000 --> 19:54.000 lots of other things that are, 19:54.000 --> 19:55.000 plan after that. 19:55.000 --> 19:59.000 And that's it, 19:59.000 --> 20:00.000 I think, 20:00.000 --> 20:01.000 uh, 20:01.000 --> 20:02.000 so I was quite fast, 20:02.000 --> 20:04.000 uh, 20:04.000 --> 20:05.000 uh, 20:05.000 --> 20:06.000 so yeah, 20:06.000 --> 20:07.000 that's, 20:07.000 --> 20:08.000 that was a long, 20:08.000 --> 20:09.000 uh, 20:09.000 --> 20:10.000 long year, 20:10.000 --> 20:11.000 with a lot of, 20:11.000 --> 20:12.000 work done, 20:12.000 --> 20:13.000 uh, 20:13.000 --> 20:14.000 and the, 20:14.000 --> 20:15.000 exemplifies to me that we are just, 20:15.000 --> 20:16.000 just before the first day, 20:16.000 --> 20:17.000 I'm actually brought a lot of new, 20:17.000 --> 20:18.000 uh, 20:18.000 --> 20:19.000 interesting topics to, 20:19.000 --> 20:20.000 to do, 20:20.000 --> 20:21.000 for this year. 20:21.000 --> 20:22.000 So I hope that, 20:22.000 --> 20:23.000 uh, 20:23.000 --> 20:24.000 movie will be like, 20:24.000 --> 20:25.000 one of the, 20:25.000 --> 20:27.000 nice platform that you want to try, 20:27.000 --> 20:28.000 in 2021, 20:28.000 --> 20:29.000 and, uh, 20:29.000 --> 20:30.000 yeah, 20:30.000 --> 20:31.000 I'm joined and see if, 20:31.000 --> 20:32.000 it, 20:32.000 --> 20:33.000 gives you like nice, 20:33.000 --> 20:34.000 nice features, 20:34.000 --> 20:35.000 and also, 20:35.000 --> 20:36.000 I'm, 20:36.000 --> 20:37.000 uh, 20:37.000 --> 20:38.000 something that I forgot, 20:38.000 --> 20:39.000 I actually continue to work with, 20:39.000 --> 20:40.000 uh, 20:40.000 --> 20:41.000 uh, 20:42.000 --> 20:43.000 yeah, 20:43.000 --> 20:44.000 we did a lot of, 20:44.000 --> 20:45.000 a lot of, 20:45.000 --> 20:46.000 uh, 20:46.000 --> 20:47.000 work with the bridging system, 20:47.000 --> 20:48.000 so actually movie, 20:48.000 --> 20:49.000 really interesting, 20:49.000 --> 20:50.000 really well with this core telegram, 20:50.000 --> 20:51.000 what's up, 20:51.000 --> 20:52.000 and a few others. 20:52.000 --> 20:53.000 So, 20:53.000 --> 20:54.000 I didn't show you, 20:54.000 --> 20:55.000 but like, 20:55.000 --> 20:56.000 on my accounts, 20:56.000 --> 20:57.000 basically, 20:57.000 --> 20:58.000 I have all those platforms in one unique, 20:58.000 --> 20:59.000 UI, 20:59.000 --> 21:00.000 and fully bridge with the others. 21:00.000 --> 21:01.000 Uh, 21:01.000 --> 21:02.000 and I say, 21:02.000 --> 21:03.000 really well integrated, 21:03.000 --> 21:04.000 you have the reaction, 21:04.000 --> 21:05.000 you have like the history, 21:05.000 --> 21:06.000 management, 21:06.000 --> 21:07.000 the file management, 21:07.000 --> 21:08.000 and all those things. 21:08.000 --> 21:09.000 And one of the goal of the spaces, 21:09.000 --> 21:10.000 are actually to integrate, 21:10.000 --> 21:11.000 with those, 21:11.000 --> 21:13.000 actually to see the discord spaces inside, 21:13.000 --> 21:15.000 moving with maybe the matrix spaces, 21:15.000 --> 21:17.000 and all the others in one UI. 21:17.000 --> 21:18.000 That's it. 21:18.000 --> 21:19.000 So, 21:19.000 --> 21:20.000 if you, 21:20.000 --> 21:22.000 thank you for everything. 21:22.000 --> 21:23.000 There is some goodies there, 21:23.000 --> 21:24.000 and, 21:24.000 --> 21:25.000 more, 21:25.000 --> 21:26.000 uh, 21:26.000 --> 21:27.000 on the other room. 21:27.000 --> 21:28.000 Thank you. 21:28.000 --> 21:31.000 Uh, 21:31.000 --> 21:33.000 I will be available if you have any questions, 21:33.000 --> 21:36.000 but if there's already some questions in the room, 21:36.000 --> 21:37.000 I will be happy to answer, 21:37.000 --> 21:38.000 uh, you. 21:39.000 --> 21:41.000 Wow. 21:41.000 --> 21:43.000 I was super clear. 21:43.000 --> 21:46.000 So, yeah. 21:46.000 --> 21:53.000 So, the question was about how the bridges are working. 21:53.000 --> 21:55.000 So, uh, 21:55.000 --> 21:57.000 you have different kind of bridges. 21:57.000 --> 21:58.000 Uh, 21:58.000 --> 21:59.000 in Japanese, 21:59.000 --> 22:01.000 like, 22:01.000 --> 22:04.000 exactly implementing SMPP, 22:04.000 --> 22:05.000 uh, 22:05.000 --> 22:06.000 and then maybe matrix, 22:06.000 --> 22:08.000 and act as a matrix server. 22:08.000 --> 22:09.000 So, 22:09.000 --> 22:10.000 that's this very executive, 22:10.000 --> 22:11.000 fluid transparency, 22:11.000 --> 22:15.000 but the sledge project is actually acting as a client 22:15.000 --> 22:16.000 to this network. 22:16.000 --> 22:17.000 So, 22:17.000 --> 22:18.000 basically, 22:18.000 --> 22:19.000 when you are installing, 22:19.000 --> 22:20.000 um, 22:20.000 --> 22:21.000 sledge, 22:21.000 --> 22:22.000 you are installing it on your XMPP server, 22:22.000 --> 22:23.000 and you provide new, 22:23.000 --> 22:24.000 uh, 22:24.000 --> 22:25.000 what you call services, 22:25.000 --> 22:26.000 which is, 22:26.000 --> 22:27.000 like, from movie, 22:27.000 --> 22:28.000 somebody in the TU, 22:28.000 --> 22:29.000 I have, like, telegram, 22:29.000 --> 22:30.000 that movie, 22:30.000 --> 22:31.000 that TU, 22:31.000 --> 22:32.000 WhatsApp, that movie, 22:32.000 --> 22:34.000 and you provide your credential, 22:34.000 --> 22:36.000 uh, to that or, like, 22:36.000 --> 22:38.000 like, secure authentication system, 22:38.000 --> 22:40.000 that actually connects for you to the discord, 22:40.000 --> 22:44.000 and then sledge is basically translating this to XMPP, 22:44.000 --> 22:46.000 and your, 22:46.000 --> 22:47.000 uh, 22:47.000 --> 22:50.000 XMPP server is basically showing the clients, 22:50.000 --> 22:52.000 pure standard XMPP, 22:52.000 --> 22:53.000 uh, things. 22:53.000 --> 22:54.000 So, that's really nice, 22:54.000 --> 22:55.000 because once you do that, 22:55.000 --> 22:56.000 when you plug it, 22:56.000 --> 22:58.000 then the whole client's connected to it, 22:58.000 --> 22:59.000 actually see, 22:59.000 --> 23:00.000 the discord, 23:00.000 --> 23:01.000 uh, 23:01.000 --> 23:02.000 like, 23:02.000 --> 23:03.000 this system, 23:03.000 --> 23:05.000 as an XMPP one. 23:05.000 --> 23:07.000 Yeah, that's, that's it. 23:07.000 --> 23:08.000 It's quite tricky, 23:08.000 --> 23:09.000 because I know that, 23:09.000 --> 23:10.000 my friend, 23:10.000 --> 23:11.000 I have to follow, 23:11.000 --> 23:12.000 hold, this code changes, 23:12.000 --> 23:14.000 and telegram all the time, 23:14.000 --> 23:16.000 but it's boxed really, really well. 23:16.000 --> 23:18.000 Uh, so, yeah. 23:18.000 --> 23:21.000 There are more questions, yeah. 23:21.000 --> 23:22.000 But, yeah, 23:22.000 --> 23:25.000 what's good is about the front end. 23:25.000 --> 23:26.000 Yeah. 23:26.000 --> 23:29.000 Yeah. 23:29.000 --> 23:30.000 Yeah. 23:30.000 --> 23:40.000 Yeah. 23:40.000 --> 23:41.000 Yeah. 23:41.000 --> 23:42.000 Perfectly, actually. 23:42.000 --> 23:43.000 Uh, yeah. 23:43.000 --> 23:44.000 That's a really technical question, 23:44.000 --> 23:46.000 because I can actually show you how it's done. 23:46.000 --> 23:47.000 It's quite simple, 23:47.000 --> 23:48.000 but, uh, 23:48.000 --> 23:49.000 yeah. 23:49.000 --> 23:50.000 On the front end, 23:50.000 --> 23:51.000 it's pure JavaScript and, uh, 23:51.000 --> 23:52.000 and, uh, 23:52.000 --> 23:53.000 CSS, 23:53.000 --> 23:56.000 and actually most of the states are built in PHP, 23:56.000 --> 23:57.000 uh, 23:57.000 --> 23:59.000 and pushed in real time to the, 24:00.000 --> 24:02.000 I think when there was a react at the beginning, 24:02.000 --> 24:03.000 it's like, 24:03.000 --> 24:04.000 let's do everything in the browser. 24:04.000 --> 24:05.000 And at the moment, 24:05.000 --> 24:06.000 you guys say, yeah, 24:06.000 --> 24:07.000 browser, 24:07.000 --> 24:08.000 I quite slow, 24:08.000 --> 24:09.000 so maybe we can gener, 24:09.000 --> 24:10.000 uh, 24:10.000 --> 24:11.000 render some of the stuff, 24:11.000 --> 24:12.000 set aside and push it. 24:12.000 --> 24:13.000 Well, that's the thing. 24:13.000 --> 24:15.000 It's like PHP can actually do easily, 24:15.000 --> 24:17.000 like a lot of HTML, uh, 24:17.000 --> 24:18.000 like, 24:18.000 --> 24:19.000 so there is a website, 24:19.000 --> 24:20.000 and then, 24:20.000 --> 24:21.000 when you, for example, 24:21.000 --> 24:22.000 receive a message, 24:22.000 --> 24:23.000 moving is parsing it, 24:23.000 --> 24:24.000 putting into database, 24:24.000 --> 24:25.000 and then, 24:25.000 --> 24:27.000 create a little HTML, 24:27.000 --> 24:28.000 and it's a bit more complex than that, 24:28.000 --> 24:29.000 but yeah, 24:29.000 --> 24:30.000 that's it. 24:30.000 --> 24:31.000 So that's how it is, 24:31.000 --> 24:32.000 that's why it's simple. 24:32.000 --> 24:33.000 And, uh, 24:33.000 --> 24:34.000 I made, like, a little, 24:34.000 --> 24:35.000 two, uh, 24:35.000 --> 24:36.000 almost like a couple of, 24:36.000 --> 24:37.000 weeks ago, 24:37.000 --> 24:38.000 showing, like, 24:38.000 --> 24:39.000 different, 24:39.000 --> 24:40.000 between Discord and moving, 24:40.000 --> 24:41.000 and we have, like, 24:41.000 --> 24:42.000 in Discord, 24:42.000 --> 24:43.000 it's, like, 24:43.000 --> 24:44.000 300 or 400 megabytes, 24:44.000 --> 24:45.000 and moving is, like, 24:45.000 --> 24:46.000 20 or 30 megabytes in the memory. 24:46.000 --> 24:47.000 So, 24:47.000 --> 24:48.000 works quite well. 24:48.000 --> 24:49.000 Yeah. 24:49.000 --> 24:50.000 Uh, 24:50.000 --> 24:51.000 do we have more time for questions, 24:51.000 --> 24:52.000 or? 24:52.000 --> 24:54.000 Yeah. 24:54.000 --> 24:55.000 Yeah. 24:55.000 --> 24:56.000 So, um, 24:56.000 --> 24:57.000 the question was about, 24:57.000 --> 24:59.000 who host the SFU server? 24:59.000 --> 25:00.000 So, that's your choice, 25:00.000 --> 25:01.000 actually. 25:01.000 --> 25:02.000 Uh, 25:02.000 --> 25:03.000 you can, 25:03.000 --> 25:04.000 normally, 25:04.000 --> 25:05.000 it's, 25:05.000 --> 25:07.000 good to host it next to your 25:07.000 --> 25:08.000 XMPP server, 25:08.000 --> 25:09.000 to actually, for it, 25:09.000 --> 25:10.000 like, 25:10.000 --> 25:11.000 as a service, 25:11.000 --> 25:12.000 and, like, 25:12.000 --> 25:13.000 you know, 25:13.000 --> 25:14.000 I mean, 25:14.000 --> 25:15.000 I mean, 25:15.000 --> 25:16.000 I mean, 25:16.000 --> 25:17.000 I mean, 25:17.000 --> 25:18.000 I mean, 25:18.000 --> 25:19.000 I mean, 25:19.000 --> 25:20.000 I mean, 25:20.000 --> 25:21.000 I mean, 25:21.000 --> 25:22.000 I mean, 25:22.000 --> 25:24.000 I mean, 25:24.000 --> 25:25.000 I mean , 25:25.000 --> 25:26.000 so, 25:26.000 --> 25:27.000 So, 25:27.000 --> 25:28.000 looks like like a service, 25:28.000 --> 25:30.000 but you can actually have it, 25:30.000 --> 25:32.000 like another network, 25:32.000 --> 25:34.000 and then Codex to that server, 25:34.000 --> 25:35.000 so, 25:35.000 --> 25:36.000 you imagine you have, 25:36.000 --> 25:37.000 like, a small XMPP server on your Raspberry Pi, 25:37.000 --> 25:38.000 and you kind of easily re-encode video on that thing, 25:38.000 --> 25:39.000 uh, 25:39.000 --> 25:40.000 then you want to have something in the cloud. 25:40.000 --> 25:42.000 You can actually say, 25:42.000 --> 25:44.000 okay, this is where you should go to actually co, 25:44.000 --> 25:45.000 uh, 25:45.000 --> 25:46.000 an SSU and then just do the XMPP 25:46.000 --> 25:47.000 eroding, 25:47.000 --> 25:48.000 it is quite light way 25:48.000 --> 25:50.000 between your Raspberry Pi and the cloud, 25:50.000 --> 25:51.000 server. 25:51.000 --> 25:52.000 So, 25:52.000 --> 25:53.000 that's one of the goal. 25:53.000 --> 25:56.800 with movie, is that maybe to offer some kind of video call 25:56.800 --> 25:59.600 service like this, where actually maybe you pay 25:59.600 --> 26:03.800 per like a bit to actually make the server runs. 26:03.800 --> 26:06.000 And then after that, like you have just an example 26:06.000 --> 26:09.400 on top, so you use the clients you want. 26:09.400 --> 26:10.400 Yeah. 26:10.400 --> 26:12.200 I have an online question. 26:12.200 --> 26:14.920 How many is asking the DS a few features 26:14.920 --> 26:17.600 is pretty cool, and I hope the development goes well. 26:17.600 --> 26:19.440 Do you think we'll get the next NPG live stream 26:19.440 --> 26:21.000 of the first-end talks next year? 26:21.120 --> 26:23.360 Ah, yeah, maybe. 26:23.360 --> 26:24.200 Maybe. 26:24.200 --> 26:27.040 I actually am quite confident about the galene. 26:27.040 --> 26:31.240 Galene works really well, and it's a little goo 26:31.240 --> 26:34.120 binary, it's quite magical, like what a form of a tested. 26:34.120 --> 26:37.920 So maybe, because I think for them is about scalability. 26:37.920 --> 26:40.760 First, like you want to, like, everyone connected. 26:40.760 --> 26:44.760 So yeah, maybe it could be done. 26:44.760 --> 26:47.760 One of the goal of movie, as I said, 26:47.760 --> 26:50.320 was to bring the zoom and telegram experience, 26:50.320 --> 26:53.000 because I'm not far from that, because you can actually 26:53.000 --> 26:55.120 do that in the browser, so I think, like, 26:55.120 --> 26:57.600 a URL invitation system that you can send your friend, 26:57.600 --> 27:00.400 and then they create an anonymous account, 27:00.400 --> 27:03.880 just for the call, is super useful for that. 27:03.880 --> 27:05.680 And then at the end, you have a little, like, 27:05.680 --> 27:07.560 but on to say, hey, do you want to create an actual 27:07.560 --> 27:08.880 example API account, which already 27:08.880 --> 27:11.080 information to actually join next time? 27:11.080 --> 27:13.440 So that will be a really nice thing to have, like, 27:13.440 --> 27:16.160 this little unique URL will be just a join, 27:16.160 --> 27:17.880 and then do a bit of example API, 27:17.880 --> 27:20.640 and at this nice conversation. 27:20.640 --> 27:25.680 And I saw more politically, I saw the bit of companies 27:25.680 --> 27:28.720 and big government interested about that, also, 27:28.720 --> 27:31.600 with the European Union and Zoom and all those things. 27:31.600 --> 27:34.680 So maybe it's time to build those kind of solution in Europe, 27:34.680 --> 27:37.600 as well, to actually say, like, look, 27:37.600 --> 27:40.240 we did something similar, but actually better, 27:40.240 --> 27:43.080 because it's turned out, and fully compatible 27:43.080 --> 27:45.760 with a million other clients. 27:45.760 --> 27:48.920 So maybe I would be interested to see 27:48.920 --> 27:51.600 with the thousand people, if it's doable. 27:54.000 --> 27:55.480 Yeah, and the other question, 27:55.480 --> 27:57.640 I think we still have a few minutes left. 27:59.880 --> 28:02.920 Okay, so if you have more technical things 28:02.920 --> 28:05.600 or more other questions to ask, 28:05.600 --> 28:07.160 I will be on the XMP people 28:07.160 --> 28:09.080 for the rest of the afternoon. 28:09.080 --> 28:13.320 And you're welcome to actually just go on the movie 28:13.320 --> 28:15.600 website and tradeout. 28:15.600 --> 28:18.680 There is also more of that I am that is the main instance. 28:18.680 --> 28:22.520 You can just create an account and join and trade out there. 28:22.520 --> 28:23.680 It's quite easy. 28:23.680 --> 28:26.200 And if you have any other XMP clients, 28:26.200 --> 28:27.320 everything is compatible. 28:27.320 --> 28:29.440 So just try it.