WEBVTT 00:00.000 --> 00:12.520 Hello, hello, hello, hello, hello, hello all right I was just saying hello a moment ago and so hopefully you got the gist of it I'm just going to dive right in because we'll be very very tight on time 00:12.520 --> 00:24.320 All right, so first of all why does sustainability matter like why do we why do we even care about so I think most people in this room can probably construct an argument about why sustainability matters 00:24.320 --> 00:33.320 That open source software can really but why particularly for decentralized networks and I want to present you this right to think about 00:33.320 --> 00:43.320 Decentralization without sustainability is just deferred centralization and if there's one thing that you take from this this talk, it's basically this side 00:43.320 --> 00:50.320 Right, this is hopefully the most important part of it if you need to leave now then now if you're option and you can go 00:51.320 --> 00:58.320 But this is really what we're going to be talking about and now this applies to matrix but applies to pretty much any decentralized system if you think about the internet a large over 00:58.320 --> 01:10.320 You know the last decade or so we see it increasingly centralized and that is because we have not found good ways to sustainably invest in all the different components that you need to have a truly decentralized internet 01:10.320 --> 01:17.320 It applies to political systems as well you have to invest in your decentralized knows otherwise at all the power just gets sucked into the middle 01:18.320 --> 01:34.320 So what does that mean when we say sustainability and the context of matrix like what's our what are we talking about and the way I think about it with matrix we want to have the same impact in the next 50 years as email had on the last 50 that's the sort of ambition that we need to be having 01:34.320 --> 01:43.320 But if you want that to be true then you're going to need to think about sustainability in a very specific way you're going to make decisions where this future can actually exist 01:44.320 --> 01:50.320 Okay, so a little bit of history I think some people know this but we'll just go through it quickly so you sort of understand the context 01:51.320 --> 01:58.320 2014 the matrix founding team came together working in a much larger organization doing this doing this matrix thing 01:58.320 --> 02:06.320 And it started to go pretty well and they actually spun out and created element and you vector in order to in order to fund themselves 02:07.320 --> 02:17.320 Started making some money out of out of feature sponsorship this was this was also successful it felt it felt good and going back for a point around decentralization 02:17.320 --> 02:27.320 Realize that this moment it'd be a good time to create an independent foundation that was nonprofit and so you've got the matrix foundation and you have an element as the profit entity 02:28.320 --> 02:36.320 From last time you're doing a little bit more feature sponsorship things were sort of sort of okay, but there's a problem 02:37.320 --> 02:50.320 Why is the true cost of feature development is it writing the feature itself is the design is it the LMM generated blog post claiming victory once you ship it 02:51.320 --> 03:05.320 Or maybe it's the maintenance and this builds up over time right it's cumulative the more complex your systems become the more maintenance that you have now who in this room thinks it's good to invest in maintenance of open source software projects 03:06.320 --> 03:15.320 Paray, lots of hands up who in this room today is willing to write me a check for unspecified maintenance in a matrix ecosystem project 03:18.320 --> 03:25.320 Right for those of you watching the live stream you can't see the whole audience hands hands hands were down and this is a problem 03:25.320 --> 03:38.320 Right, but there are plenty of professional services companies that make this kind of thing work or you do is you charge a little bit extra for your for your teams time and that and that margin allows you to invest back in the project you can do this 03:38.320 --> 03:45.320 Problem is element does a bunch of other stuff that we think is necessary for the long term sustainability of matrix 03:46.320 --> 03:52.320 But does not fit in that professional services model and so this isn't the whole list but the sorts of things 03:53.320 --> 03:59.320 We are significant sponsors of the spec core team but probably more importantly the spec authorship we've spend a lot of time there 04:00.320 --> 04:05.320 We bought out the element clients for ourselves but also for the ecosystem growth general and we saw Dave talking about that earlier 04:05.320 --> 04:10.320 We maintain the matrix to walk home, so for instance, we maintain the rest SDK, we maintain the JS SDK 04:11.320 --> 04:13.320 We look after synapse and now there's an admin console 04:14.320 --> 04:19.320 We do a bunch of work about protocol research the sort of much longer term things that we do 04:20.320 --> 04:25.320 And we provide the foundation of trust and safety and compliance and security we do public policy advisory so 04:25.320 --> 04:33.320 Poor admin dean and Denise have to keep going around Europe telling people that into an encryption is not about terrorism and there's actually some good things about it 04:34.320 --> 04:37.320 And finally provide things like finance and legal and business operations for the foundation 04:38.320 --> 04:40.320 Now I'm not trying to say that element does everything here 04:41.320 --> 04:51.320 That's not true the direction of travel is that more and more folks across the whole ecosystem are finding ways to really meaningfully support the foundation and matrix project, particularly coming out of the governing board 04:52.320 --> 04:56.320 But it's a lot and it doesn't add up 04:58.320 --> 05:03.320 So it's worse than that though because you can't just pray that the commercial deployments are going to fund your upstream 05:04.320 --> 05:09.320 There are some exceptions, but generally that does not happen and it's going to get worse over time because the more successful matrix becomes 05:10.320 --> 05:14.320 The more and more we see very large organizations not invested in the ecosystem at all 05:15.320 --> 05:18.320 Just kind of show up and provide a matrix installation, but they don't contribute back 05:18.320 --> 05:24.320 And while that annoys me they're totally cool to do that the licensing says they can they're not doing anything wrong 05:25.320 --> 05:27.320 So what are you going to do? 05:28.320 --> 05:32.320 Now we have seen lots of different approaches to this in the open source world 05:32.320 --> 05:37.320 We've seen people looking at licensing and particularly non OSI licensing 05:37.320 --> 05:41.320 We know why they've gone that way, that's not what we would do within the matrix ecosystem 05:42.320 --> 05:44.320 But you've got to find some way to capture value 05:45.320 --> 05:50.320 It's going to be something that you hold back if you're going to not go down this feature sponsorship route 05:51.320 --> 05:53.320 So when are you going to draw the line? 05:54.320 --> 05:59.320 The way we think about this with an element we think anything that empowers the end user 06:00.320 --> 06:07.320 That is false anything that empowers an enterprise over the end user or in way that an end user wouldn't really care about 06:08.320 --> 06:14.320 That goes into paid and by end user I'm talking like someone that would use a client or I'm just talking about someone that would administer a server 06:15.320 --> 06:21.320 So examples of what we would put into發 something like straight line performance, cryptography or core features, like spaces or threads 06:22.320 --> 06:23.320 All of that stuff that is false 06:24.320 --> 06:26.320 But things like clustering and high availability 06:27.320 --> 06:32.320 If you want to run a million person installation where you've got quite special this needs 06:32.320 --> 06:37.320 Just an admin trying to run it for your friends and family, you probably don't want that complexity 06:38.320 --> 06:42.320 If you want integration into a corporate directory, that's probably paid 06:43.320 --> 06:47.320 If you want to see a ray compliance, that's again something that we will consider as part of the paid offer 06:49.320 --> 06:53.320 We did two other things, we did change license, we moved from Apache 2 to AgPL 06:54.320 --> 06:57.320 This sort of ensures that companies that do fork the upstream 06:58.320 --> 07:01.320 They can either publish their changes or contribute them back somehow 07:02.320 --> 07:07.320 And we have a CLA which allows us to give exceptions to that 07:08.320 --> 07:15.320 Not all CLAs are equal, the element CLA actually has a specific term there that says if you contribute to it 07:16.320 --> 07:19.320 Whatever happens your contribution will always be made available for us 07:20.320 --> 07:24.320 So if we have a change of leadership element or something or we bought by somebody 07:25.320 --> 07:27.320 Your contribution is always for us 07:28.320 --> 07:29.320 Not all CLAs have that 07:30.320 --> 07:32.320 So did this work? 07:33.320 --> 07:36.320 Well, here's a disturb organisation that I able to support this model 07:37.320 --> 07:39.320 And you've got folks like NATO in the European Commission 07:40.320 --> 07:43.320 And I'm going to call it our friends at FK, I'm not going to pronounce them because I'm scared to do so 07:44.320 --> 07:45.320 But their logo is tiny 07:46.320 --> 07:48.320 There we go, there we go 07:49.320 --> 07:50.320 What he said 07:51.320 --> 07:54.320 So, okay, cool story 07:55.320 --> 07:58.320 We found a way to make some money but what's that got to do with open source software 07:59.320 --> 08:01.320 So let's talk about that 08:02.320 --> 08:03.320 Because this gives us some freedom 08:04.320 --> 08:06.320 This allows us to think about how 08:07.320 --> 08:12.320 What's the long term horizon, how can we invest in the matrix ecosystem at large 08:13.320 --> 08:14.320 Because that's why we're getting out of bed in the morning 08:15.320 --> 08:17.320 So I want to talk a bit about matrix 2.0 08:18.320 --> 08:21.320 I want to talk about LMAX transition, we're going to talk about ESAS community 08:22.320 --> 08:25.320 Accessibility, matrix RTC, rough-sister can, some protocol design 08:26.320 --> 08:28.320 We're going to do it super super quick and then there's going to be some demos 08:29.320 --> 08:31.320 And then I'll get off and you can go on with your day 08:32.320 --> 08:34.320 First of all, matrix 2.0 08:35.320 --> 08:38.320 This is this idea of a whole bunch of different MSEs that we think together 08:39.320 --> 08:42.320 allows us to really level up the sort of experiences that you can provide 08:43.320 --> 08:46.320 In a messaging app so that you can compete with centralised alternatives 08:47.320 --> 08:49.320 There are 28 of these MSEs 08:49.320 --> 08:52.320 27 of them were authored by element folks 08:53.320 --> 08:56.320 If you want to know the 28 that was written by your hand as Marbek 08:57.320 --> 09:00.320 But the 27 of them are from element 09:00.320 --> 09:01.320 And we're real close now 09:02.320 --> 09:05.320 We've got matrix RTC, we just sort of talk on what remains there 09:06.320 --> 09:07.320 And we have some sliding sink extensions 09:08.320 --> 09:10.320 What we've got that then we can call this, we can call this a little bit 09:11.320 --> 09:12.320 Done, little bit 09:13.320 --> 09:16.320 That's why element x transition, first of all is this manner for matrix 09:16.320 --> 09:20.320 For those of you that don't know, we've got our old mobile apps and then we've got element x 09:21.320 --> 09:23.320 And we've been trying to migrate across to that over the last couple of years 09:24.320 --> 09:25.320 It's been quite a painful process 09:26.320 --> 09:28.320 But why isn't that just element hygiene? 09:29.320 --> 09:33.320 Well, the thing is the element apps are still the dominant apps in the ecosystem 09:34.320 --> 09:36.320 If you join matrix, you'll probably start with element 09:37.320 --> 09:40.320 And that will ultimately judge people will judge matrix by it 09:41.320 --> 09:43.320 So it's important that people are on the best experience 09:43.320 --> 09:45.320 We believe that best experiences element x 09:46.320 --> 09:49.320 It's certainly a lot better than the element classic apps 09:50.320 --> 09:52.320 And we're super, super close now, the big things that I think stop people with migrating 09:53.320 --> 09:54.320 Or maybe spaces or threads 09:55.320 --> 09:57.320 The migration process itself is a little bit rough as well 09:58.320 --> 09:59.320 And we're fixing that 09:59.320 --> 10:02.320 But there's also a sort of long tale of sort of smaller features 10:02.320 --> 10:04.320 And we're going to get that all done by April 10:05.320 --> 10:08.320 And then at that point you're going to start hearing us talking a lot more 10:08.320 --> 10:12.320 And more assertively about hey really, really you want to be using element x 10:13.320 --> 10:19.320 If people in this room cannot use element x I'd love to hear why that is after the talk 10:20.320 --> 10:23.320 And yeah, just to give you a very brief demo people don't see it 10:24.320 --> 10:26.320 Do-do-do-do-do-do-do, can I do this? 10:27.320 --> 10:30.320 Oh woah, woah woah woah woah woah woah woah woah woah woah woah woah woahhhh, that's the one I want 10:31.320 --> 10:33.320 That's the one I want that's seen if we can get this going 10:34.320 --> 10:36.320 Yeah here we are, here we are 10:36.320 --> 10:38.720 I don't know, I've done that wrong. 10:38.720 --> 10:42.800 All right, so here's a real max, here's a room list. 10:42.800 --> 10:44.560 We've got spaces here. 10:47.040 --> 10:50.000 You've got Foss Dam, 2026, you've got the dev rooms. 10:50.000 --> 10:52.760 Let's see if we can get the decentralized room up, 10:52.760 --> 10:54.040 we're loading it. 10:54.040 --> 10:55.760 Hello. 10:55.760 --> 10:56.880 There we go. 10:56.880 --> 10:58.720 Very good. 10:58.720 --> 11:00.880 Okay, so, other than next, give it a go. 11:00.880 --> 11:01.880 If you haven't already. 11:01.880 --> 11:06.360 Right, ESS community. 11:06.360 --> 11:08.040 So, first of all, why does this matter? 11:08.040 --> 11:12.840 So, the ESS community is a distribution of matrix stack. 11:12.840 --> 11:16.720 When we started this project, what we were hearing about, 11:16.720 --> 11:19.280 this sort of matrix 2.0 ideas, 11:19.280 --> 11:22.040 it was quite hard to get everything together. 11:22.040 --> 11:24.080 Because you needed, not only a synapse, 11:24.080 --> 11:27.240 you needed mass, you needed a sliding sync proxy in that era, 11:27.240 --> 11:28.440 you needed a live kit back in. 11:28.440 --> 11:30.120 This is getting a bit complicated. 11:30.120 --> 11:31.760 And there wasn't a really nice way to do that. 11:31.760 --> 11:34.320 So, that's why we started building out ESS community. 11:34.320 --> 11:38.560 There are other two-point-O distributions available now, 11:38.560 --> 11:41.080 and they've all got different slightly different design goals. 11:41.080 --> 11:43.840 But this is the one that we're working at element. 11:43.840 --> 11:46.080 And the nice thing about this is because it's sort of, 11:46.080 --> 11:48.240 got the same lineage as I've paid offering. 11:48.240 --> 11:51.440 All of the sort of robustness things 11:51.440 --> 11:53.400 have been thinking about for folks like NATO. 11:53.400 --> 11:57.560 That is their architecturally in ESS community. 11:57.560 --> 12:01.320 Now, as a demo, I'd to show you how easy it is to get going with this. 12:01.320 --> 12:04.040 I'm going to create one of these from scratch 12:04.040 --> 12:08.360 during this call, according to this talk. 12:08.360 --> 12:10.760 But it takes about a minute to get going. 12:10.760 --> 12:12.240 So I'm going to start it now, 12:12.240 --> 12:13.680 and then by the end of it, it will be there, 12:13.680 --> 12:16.400 and then I'll give you a little tour around it. 12:16.400 --> 12:18.240 All right, so just bear with me. 12:18.240 --> 12:23.240 While we do exactly that, we will start here. 12:23.240 --> 12:27.080 We'll create our namespace. 12:27.080 --> 12:29.320 This is the command to get it going, 12:29.320 --> 12:31.400 and what you can see there is various different config files 12:31.400 --> 12:33.000 that we've got. 12:33.000 --> 12:34.000 Two men. 12:34.000 --> 12:35.520 Two men. 12:35.520 --> 12:36.720 Is that OK? 12:36.720 --> 12:37.400 Two men. 12:37.400 --> 12:38.560 Two men. 12:38.560 --> 12:42.320 LAUGHTER 12:42.320 --> 12:45.920 All right. 12:45.920 --> 12:50.520 And over here, which also needs zooming in, 12:50.520 --> 12:54.400 is my netty K9 Kubernetes, a viewer which 12:54.400 --> 12:55.600 Quentin introduced me to. 12:55.600 --> 12:56.480 So this is just the proof. 12:56.480 --> 12:58.000 I'm actually doing something behind the scenes. 12:58.000 --> 12:59.200 These pods are going to go off. 12:59.200 --> 13:00.600 And it's going to do stuff for the next minute, 13:00.600 --> 13:03.600 and then we're going to come back and see if it actually works. 13:03.600 --> 13:03.960 OK. 13:07.320 --> 13:08.160 All right. 13:08.160 --> 13:09.160 What is next? 13:09.160 --> 13:11.160 List, I think, we're in accessibility. 13:11.160 --> 13:12.360 Why does this matter for matrix? 13:12.360 --> 13:14.840 So I think this is an easy thing to argue. 13:14.840 --> 13:16.000 You've got to spend the time here. 13:16.000 --> 13:16.720 You've got to invest. 13:16.720 --> 13:18.720 It's obviously one of those things. 13:18.720 --> 13:22.480 But sometimes it doesn't get the love that it requires. 13:22.480 --> 13:23.920 If we want matrix speed for everyone, 13:23.920 --> 13:27.480 then we better make sure we're making time for accessibility. 13:27.480 --> 13:28.240 Matrix obviously. 13:28.240 --> 13:31.640 We just had a massive talk on matrix ITC. 13:31.640 --> 13:33.080 So I'm not spent too much time here, 13:33.080 --> 13:34.080 but I want to say two things. 13:34.080 --> 13:36.600 Firstly, VoIP is an expected part of a chat-up. 13:36.600 --> 13:37.720 That's why we have to work here. 13:37.720 --> 13:41.120 But matrix VoIP needs to have the same cryptographic guarantees 13:41.120 --> 13:41.720 as for messaging. 13:41.720 --> 13:44.440 You have to be confident that you know who you're talking to. 13:44.440 --> 13:46.120 It's taken a long time to get this going. 13:46.120 --> 13:49.080 And that is because we've had to build out completely new concepts 13:49.080 --> 13:51.760 within matrix to support these kinds of use cases. 13:51.760 --> 13:53.520 We didn't know we had to do this right at the beginning 13:53.520 --> 13:55.040 of the project. 13:55.040 --> 13:56.280 But we've now got something that we really 13:56.280 --> 13:59.880 think works well together. 13:59.880 --> 14:02.520 Last SDK, we talked about a lot that the rest 14:02.520 --> 14:05.360 is to cater to day. 14:05.360 --> 14:08.840 I mean, we want to SDK that everyone can rely on 14:08.840 --> 14:09.960 and build their own clients on. 14:09.960 --> 14:10.920 And that's really what we're going for. 14:10.920 --> 14:13.160 We considered this to be quite a success story 14:13.160 --> 14:14.520 within the Matrix eCo system. 14:14.520 --> 14:16.440 It's under the foundations organization. 14:16.440 --> 14:20.520 But element does sort of runs the governance for the project. 14:20.520 --> 14:23.000 But 25% of everything that is PR 14:23.000 --> 14:25.400 against this repo comes from outside of element. 14:25.400 --> 14:27.160 So we feel quite good about that 14:27.160 --> 14:30.960 and the direction of travel is more and more and more. 14:30.960 --> 14:32.800 And then finally, probably most importantly, 14:32.800 --> 14:33.760 is protocol research. 14:33.760 --> 14:35.960 Matthew spent a bunch of time explaining some of the things 14:35.960 --> 14:36.600 that we're doing here. 14:36.600 --> 14:39.400 This is important because we need to ensure 14:39.400 --> 14:40.480 that matrix stays current. 14:40.480 --> 14:43.400 We can all name other protocols over the years 14:43.400 --> 14:46.840 that weren't able to evolve and iterate. 14:46.840 --> 14:50.840 And if you do that, you stagnate. 14:50.840 --> 14:52.760 So a lot of the work that we're thinking about right now 14:52.760 --> 14:54.440 is our Federation Security, particularly 14:54.440 --> 14:57.120 with Hydra, with thinking about MLS, 14:57.120 --> 14:59.600 and we're thinking about peer-to-peer. 14:59.600 --> 15:01.920 All right, what's coming next? 15:01.920 --> 15:04.320 We're, how we're doing for time. 15:04.320 --> 15:06.480 OK, great. 15:06.480 --> 15:08.920 Matrix IDC lands, invisible crypto. 15:08.920 --> 15:10.680 You'll need to set hopefully. 15:10.680 --> 15:13.600 And this really sort of runs out of the Matrix 2.0 set. 15:13.600 --> 15:16.640 We sold that element classic Hydra lands. 15:16.640 --> 15:18.240 We do some peer-to-peer work, element X, 15:18.240 --> 15:20.680 where but Dave was exploring, we talked about earlier, 15:20.680 --> 15:21.760 an element called out of beta. 15:21.760 --> 15:25.720 These, I think, are going to be a big highlight in the coming. 15:25.720 --> 15:27.240 Yeah. 15:27.240 --> 15:29.720 Right, demos. 15:29.720 --> 15:31.400 We're going to be very tight for time. 15:31.400 --> 15:35.760 We can either do demos or we can do questions. 15:35.760 --> 15:38.000 If we do demos, it's going to be super cool. 15:38.000 --> 15:41.040 And I might just fall on my face, or we could do questions. 15:41.040 --> 15:43.400 Who here would like demos? 15:43.400 --> 15:45.200 And who would, right, brilliant, very good, very good. 15:45.200 --> 15:46.680 That is the correct answer. 15:46.680 --> 15:50.000 So you may remember from earlier in this talk, 15:50.000 --> 15:54.000 that we set things going. 15:54.000 --> 15:56.680 This is our K9 Viewers, so you can see the various different pods. 15:56.680 --> 15:59.440 You can see we've got synaps there at the bottom, 15:59.440 --> 16:01.840 but the various other pods as well. 16:01.840 --> 16:06.000 So let's go back and just make sure we've got a nice happy message there. 16:06.000 --> 16:07.400 Do I need to go in further? 16:07.400 --> 16:08.200 Further, still, right. 16:08.200 --> 16:09.360 There you go. 16:09.360 --> 16:13.080 And you can see the end points that it's created for me here. 16:13.080 --> 16:17.440 One thing we need to do, we need to create a user. 16:17.440 --> 16:22.000 So let's do that, and we've got this helpful tool, 16:22.000 --> 16:25.560 and we'll call it Neal, FontsDem. 16:25.560 --> 16:27.320 We're going to make them an admin, 16:27.320 --> 16:29.680 so I can show you the admin console. 16:29.680 --> 16:33.000 And we are going to set a password, that's well. 16:36.000 --> 16:38.000 OK. 16:38.000 --> 16:38.800 Yes. 16:38.800 --> 16:39.680 Right, you've got to use it. 16:39.680 --> 16:42.080 Let's go and see if any of this worked. 16:42.080 --> 16:44.880 The last time I did this, it didn't work, 16:44.880 --> 16:49.440 because I got rate limited by Let's Encrypt. 16:49.440 --> 16:53.200 And I can't test it because I don't want to get rate limited by 16:53.200 --> 16:55.600 Let's Encrypt in the live one. 16:55.600 --> 16:58.600 So there is quite large jeopardy here, 16:58.600 --> 17:03.520 but hopefully this can all go well. 17:03.520 --> 17:09.840 So let's see. 17:09.840 --> 17:10.960 Let's see. 17:10.960 --> 17:13.200 OK, that's all right. 17:13.200 --> 17:14.880 Continue. 17:14.880 --> 17:16.240 This looks promising. 17:21.520 --> 17:22.000 Continue. 17:25.440 --> 17:26.160 All right. 17:26.160 --> 17:26.840 And we're in. 17:26.840 --> 17:28.800 All right. 17:28.800 --> 17:31.080 So everyone's seen this. 17:31.080 --> 17:33.520 This is just this is the element web. 17:33.520 --> 17:38.960 But let's have a quick look at the admin console behind it. 17:38.960 --> 17:40.720 And what this tells you, you've got your dashboard. 17:40.720 --> 17:43.680 It tells you how many users you've got. 17:43.680 --> 17:46.880 And oh, that is cash. 17:46.880 --> 17:48.880 That is not what I'm expecting to say. 17:48.880 --> 17:50.400 That's really quite interesting. 17:50.400 --> 17:51.760 I don't know why it's doing that. 17:51.760 --> 17:52.080 All right. 17:52.080 --> 17:53.920 Well, well, well, well, well, well, well, well, not we're about that. 17:53.920 --> 17:54.960 Let's invite some people in. 17:54.960 --> 17:56.880 And let's just prove to you that the federation works 17:56.880 --> 17:58.120 and that things like calling works. 18:02.040 --> 18:06.840 There's some guy called Matthew. 18:06.840 --> 18:08.640 He normally likes to cheat. 18:08.640 --> 18:13.640 That doesn't mean this invite Matthew in. 18:17.800 --> 18:20.160 No, I'm here. 18:20.160 --> 18:22.560 Yeah, yeah, otherwise I was going to do it with myself. 18:22.560 --> 18:25.320 This is a better demo. 18:25.320 --> 18:27.440 How are we getting on here? 18:27.440 --> 18:29.560 It's on the element client. 18:29.560 --> 18:30.760 Are you saying it's my element? 18:30.760 --> 18:31.960 Yes, I am. 18:31.960 --> 18:34.920 If you're not ready for that, 18:34.920 --> 18:38.320 what if you're told in my fabulous? 18:38.320 --> 18:43.320 I can invite me, just in case. 18:54.240 --> 18:56.120 Let's do it. 18:56.120 --> 18:57.120 It's a request. 18:57.120 --> 18:58.120 Let's look at it. 19:09.240 --> 19:14.440 Oh, typing on a stage like this is a lot harder 19:14.440 --> 19:18.120 than typing otherwise. 19:18.120 --> 19:18.960 Okay. 19:21.160 --> 19:23.920 Let's talk to me and set. 19:25.680 --> 19:27.240 All right. 19:27.240 --> 19:30.240 The better luck, the, the, the, the, the, the, the, the, 19:30.240 --> 19:32.680 right, uh, what is that? 19:32.680 --> 19:33.520 You got in. 19:33.520 --> 19:34.720 It's better with it's for you. 19:34.720 --> 19:38.240 All right, so, first of all, 19:38.240 --> 19:40.000 first of all, proof it's done already. 19:40.000 --> 19:40.840 All right. 19:40.840 --> 19:41.680 All right. 19:41.680 --> 19:46.680 Let's just prove that element call is doing its thing. 19:51.680 --> 19:53.520 Witing, waiting. 19:53.520 --> 19:55.280 Let's go to the two. 19:55.280 --> 19:56.120 Who's this? 19:56.120 --> 19:57.440 Who's this guy? 19:57.440 --> 19:58.440 Yeah. 19:58.440 --> 19:59.440 All right, very good. 19:59.440 --> 20:00.440 Very good, very good. 20:00.440 --> 20:01.280 All right. 20:01.280 --> 20:02.120 All right. 20:02.120 --> 20:02.960 Very good. 20:02.960 --> 20:03.960 All right. 20:03.960 --> 20:04.960 Very good. 20:04.960 --> 20:05.960 All right. 20:05.960 --> 20:06.960 All right. 20:06.960 --> 20:07.960 All right. 20:08.920 --> 20:11.640 And I'm going to wrap up and then get off the stage. 20:11.640 --> 20:14.400 So, what have we got as the final thing? 20:14.400 --> 20:17.040 Takeaways, things that'd like you to take away. 20:17.040 --> 20:19.200 Decentralization without sustainability 20:19.200 --> 20:21.760 is just a third centralization, right? 20:21.760 --> 20:23.200 This is the main thing. 20:23.200 --> 20:25.360 Other things though, use element X. 20:25.360 --> 20:28.640 If you don't already, give ESS community a try out. 20:28.640 --> 20:30.520 I managed to install it and set it up. 20:30.520 --> 20:32.640 Once getting a talk out for them, 20:32.640 --> 20:35.000 that is how easy this to get going. 20:35.000 --> 20:37.080 And then just an obvious thing. 20:37.080 --> 20:40.080 If you're going to support an open source project, 20:40.080 --> 20:42.040 pay for vendors that are going to contribute 20:42.040 --> 20:43.440 to their upstream, that's the best thing 20:43.440 --> 20:44.560 that you can possibly do. 20:44.560 --> 20:47.240 Elements one, there are others available as well. 20:47.240 --> 20:48.000 Right, that's it. 20:48.000 --> 20:48.840 Thank you very much. 20:48.840 --> 20:49.800 I think we're all time. 20:49.800 --> 20:50.800 Thank you. 20:50.800 --> 20:51.800 Thank you. 20:51.800 --> 20:52.800 Thank you. 20:58.800 --> 21:00.280 My big time for questions. 21:00.280 --> 21:01.920 Then my big time for questions. 21:01.920 --> 21:03.960 What do you have for questions that you want? 21:03.960 --> 21:08.240 Well, I'll make some speakers here, so yeah. 21:08.240 --> 21:08.600 All right. 21:08.600 --> 21:11.200 I can do questions if you want a question. 21:11.200 --> 21:12.400 Question over here. 21:12.400 --> 21:13.600 If there's a little chat in this stuff, 21:13.600 --> 21:16.160 just make sure it's in, like, you do this, like, 21:16.160 --> 21:19.560 as much as you don't know, that's what I'm going to do today. 21:19.560 --> 21:20.880 How do they use them? 21:20.880 --> 21:22.720 Yeah, I don't know. 21:22.720 --> 21:23.680 It sounds very cool. 21:23.680 --> 21:25.040 That's like it's been a long time ago. 21:25.040 --> 21:25.880 Yeah. 21:25.880 --> 21:28.160 But my government is using open source 21:28.160 --> 21:30.440 and you have to utilize the communication software. 21:30.440 --> 21:34.200 Yeah, so they are long-term customers with element. 21:34.200 --> 21:38.400 And they use that within this we discover from them. 21:38.400 --> 21:40.080 I don't know too much about their source. 21:40.080 --> 21:44.520 Sorry, the question was who are FK. 21:44.520 --> 21:46.200 I don't know too much about their use case, 21:46.200 --> 21:47.160 and maybe someone else here can 21:47.160 --> 21:50.360 probably speak to it a little bit more concretely. 21:50.360 --> 21:54.280 But their big users of the web clients 21:54.280 --> 21:57.120 and they use that across government. 21:57.360 --> 22:00.800 They also just want to make a sort of occupational law. 22:00.800 --> 22:03.360 And they're interested in more about FK 22:03.360 --> 22:06.960 and the related to the room over there. 22:06.960 --> 22:08.160 Thank you. 22:08.160 --> 22:09.360 Thank you. 22:09.360 --> 22:10.560 Thank you. 22:10.560 --> 22:12.160 Any other questions? 22:16.160 --> 22:16.680 All right. 22:16.680 --> 22:19.680 In that case, I'll let someone else introduce you it.