WEBVTT 00:00.000 --> 00:11.480 Hi everyone, I'm Virgil, I work at the Flint Government on a project that's called 00:11.480 --> 00:20.600 Lasfitte, a collaborative workspace for public agents to replace Microsoft and it's all 00:20.600 --> 00:23.800 open source, you can find it on GitHub. 00:23.800 --> 00:29.980 So I just say that, it's only published MIT, it's using first libraries for the Arts 00:30.020 --> 00:35.900 of nature guys are doing, thank you for open sensing all that because we wouldn't have 00:35.900 --> 00:43.020 figured out the Cerditsy part and the cool editor, like Blacknotes doing and for the stuff 00:43.020 --> 00:48.300 around, we just use framework so we don't take too much tricks because we need to ship 00:48.300 --> 00:53.380 fast, so don't go react next, kind of like boring stack but it works for us, so we have 00:53.380 --> 01:02.340 a bunch of apps, one not taking up, that uses Blacknotes and YGS for the editor part, fail 01:02.340 --> 01:10.260 sharing a video conference that just made New York Times first page two days ago because 01:10.260 --> 01:17.620 they are sending it to all public agents in the central states, animal clients that use 01:17.620 --> 01:22.700 spot postfix and the YGS chatbot that uses Versailles decay and you can just choose 01:22.700 --> 01:24.700 your LMA plug. 01:24.700 --> 01:29.620 So this is the application I'm working on, could have wrote the declarations of the 01:29.620 --> 01:37.460 right of the situation, on the season of the Cerditsy, this is actually the home page of the 01:37.460 --> 01:44.300 government website, I'm pretty happy, I was a lot to do that, so you might wonder where 01:44.380 --> 01:52.060 I'm here, this is not really local first, there is a Django server and people connect 01:52.060 --> 01:58.020 to it over the web and it's not actually running on your computer, but we are actually 01:58.020 --> 02:05.020 running the direct message of the public agent is running on Matrix, which is probably the 02:05.020 --> 02:11.060 largest matrix instance of the world, it has 400,000 public agents connecting to it 02:11.140 --> 02:17.340 every month and it's kind of decentralized, it's ministry, it's on server and they're all 02:17.340 --> 02:23.260 connected through gateway and also we work for a year and a half, we've been working with 02:23.260 --> 02:27.100 youself and Kevin from Blackmail to YGS and every time we meet with them they want to 02:27.100 --> 02:35.260 take us to local first meetup, so we started, we started, say okay maybe we can look at 02:35.260 --> 02:39.980 this and try to understand a little bit better, so you might wonder who wants local first 02:40.020 --> 02:48.060 in the government, you might guess the army, so the army is actually deploying its own 02:48.060 --> 02:55.940 lastweeds, they need to work offline, you know, on the ground, it will be, we are not doing 02:55.940 --> 03:01.740 that, they are just having their own lastweeds, on their own private network, not connected 03:01.740 --> 03:09.940 to this internet, but that's it, so why didn't we do local first, well, they did 03:10.020 --> 03:16.540 gave us the mission to build lastweeds three years ago, so we had to put public agents in 03:16.540 --> 03:22.460 production, like really quickly, and this still feels really cool, but a bit experimental 03:22.460 --> 03:30.300 still, so maybe we can like start putting some stuff in local first, but we had to deliver 03:30.300 --> 03:35.580 really fast, so that's why we used the boring start to build fast to allow for iteration 03:35.660 --> 03:43.020 to scale quite quickly on Kubernetes, and to focus on usability, because we have like normal 03:43.020 --> 03:49.660 public agents who don't come to first them, that uses this, so you know, the average person 03:49.660 --> 03:55.460 sitting in an office, but we have the army, like saying you need to do end-to-end encryption 03:55.460 --> 04:01.780 otherwise we won't be able to use you for kind of like sensitive communication, so we try 04:01.820 --> 04:06.860 to do our back end as dumb as possible, not too much in the post-greSQL, and do as many 04:06.860 --> 04:14.700 future clients' side, for example, export, so that we can, Indian move to Italy, my biggest 04:14.700 --> 04:20.100 first, yeah, my biggest fear about local first is usability, like matrix at first, it was 04:20.100 --> 04:24.860 a nightmare for public agents, and we have flatty Golot, and we have still people saying hey 04:24.940 --> 04:33.940 lost my keys, okay, so it's tough, so what I'm here actually to present is that we are 04:33.940 --> 04:40.420 really put a lot, we are not very innovative, the tech will give you that to you guys, but 04:40.420 --> 04:45.340 we are doing a lot of effort in doing good UX, and I'm actually reassured by the model 04:45.340 --> 04:50.540 collective, it seems to be doing a really cool job thinking about the UX, we've done an 04:50.540 --> 04:57.540 accessible, and I'm done, but this is it, you can be used it