WEBVTT 00:00.000 --> 00:12.000 Thank you for joining us, so the next talk will be about recent advances in privacy and 00:12.000 --> 00:13.000 collaboration. 00:13.000 --> 00:21.000 Thanks for the introduction, so I will present a quick pad today and basically, more 00:21.000 --> 00:25.000 said, like recent advances, actually, in quick pad not in privacy and collaboration. 00:25.000 --> 00:27.000 I mean, yes, it is part of it. 00:27.000 --> 00:32.000 And so I am Fabric Morten, I am a quick photographer and I am one of the developers of 00:32.000 --> 00:38.000 the, I mean, I am part of the quick pad team and now I show a presentation to 00:38.000 --> 00:41.000 what, um, kids not working. 00:41.000 --> 00:44.000 What created, what created the quick pad is. 00:44.000 --> 00:50.000 So, first of all, a quick pad like is a collaborative office suit, like really an office suit 00:50.000 --> 00:52.000 with many different applications. 00:52.000 --> 00:58.000 And actually, even in this, this screenshot, this cascade of screenshots, there is one 00:58.000 --> 01:03.000 missing, there is not the diagram apps which helps making nice diagrams. 01:03.000 --> 01:07.000 But we have a large span of different applications. 01:07.000 --> 01:11.000 So, I don't know why it did this. 01:11.000 --> 01:19.000 So, we have like all the office, usual suspects, like spreadsheets, document and presentation. 01:19.000 --> 01:26.000 And also, other things, like Markdown HD, rich tech edition, which is a bit different from 01:26.000 --> 01:31.000 documents because we, it's really like to produce rich tech documents and not like type set 01:31.000 --> 01:37.000 type set it document and some whiteboard apps and actually other things for collaboration, 01:37.000 --> 01:44.000 like Kenban and forms, which we don't have, which is, which we don't have in other 01:44.000 --> 01:48.000 aspects, in end-to-end encryption, in an end-to-end encrypted fashion. 01:48.000 --> 01:53.000 And as I said, also, the diagram, like just the diagram in apps where you can 01:53.000 --> 01:56.000 make things as nicely as you want. 01:56.000 --> 02:01.000 And the thing that, so they say it's an online collaborative office suit. 02:01.000 --> 02:06.000 And the main difference with all those solutions, it's open source. 02:06.000 --> 02:11.000 And it's end-to-end encrypted, meaning that in, in, or you don't need to trust 02:11.000 --> 02:15.000 us to have your data stored with us. 02:15.000 --> 02:18.000 And it has been born at XWeKit 10 years ago. 02:18.000 --> 02:24.000 It's actually started as a small, like, a research project, like just to have real 02:24.000 --> 02:29.000 time in XWeKit, which is, which you will see other presentations today. 02:29.000 --> 02:35.000 And so, that's where the name comes from, CryptPad, where it's a bit misleading because 02:35.000 --> 02:39.000 we will think that it just like hit our pad, for instance, encrypted, but in the end it's 02:39.000 --> 02:40.000 a little official. 02:40.000 --> 02:46.000 And, actually, not many people know that, but that's a bit sad for on our side. 02:46.000 --> 02:48.000 And it's really false. 02:48.000 --> 02:50.000 It's a GPL V3, as a lesson. 02:50.000 --> 02:55.000 And we have, like, this breakthrough site, and we also host, as, I mean, 02:55.000 --> 02:56.000 it took here as a company. 02:56.000 --> 03:02.000 Also, host, flagship instance, CryptPad.fr, which is one of the biggest one I 03:02.000 --> 03:03.000 did actually in use. 03:03.000 --> 03:07.000 And then it's, there is a question, like I said, that it's end-to-end encrypted, 03:07.000 --> 03:12.000 and why do we need to have end-to-end encrypted, like, office, office things. 03:12.000 --> 03:17.000 So, I think that, like, one of, I mean, the biggest actors in office will be, like, 03:17.000 --> 03:19.000 Microsoft and Google. 03:19.000 --> 03:25.000 And they are not really known for, like, respecting GDPR, there are other things with 03:25.000 --> 03:28.000 that the data may be stored in the in the US. 03:28.000 --> 03:34.000 It's a new, both are US companies, which are not really compatible with EU laws. 03:34.000 --> 03:37.000 And, especially this day, it becomes worth and worth. 03:37.000 --> 03:39.000 But, I mean, it's kind of important. 03:39.000 --> 03:44.000 And the thing that, there are many, like, institutions where, 03:44.000 --> 03:48.000 they have the need of using office shoots. 03:48.000 --> 03:55.000 And, like, schools, for instance, and then, there are, there are sensitive 03:55.000 --> 04:01.000 sensitive data, for instance, children's data, which may be stored in this unsafe 04:01.000 --> 04:02.000 environment. 04:02.000 --> 04:05.000 So, that's where we come, we come. 04:05.000 --> 04:10.000 And we want to say, like, yes, in this context with ScriptPad, you can have both 04:10.000 --> 04:14.000 real-time collaborations, something that is quite easy to use. 04:14.000 --> 04:19.000 Where you don't need to have, like, all this knowledge about cryptography, about, like, 04:19.000 --> 04:22.000 how things work, like, for instance, with PGP, where even, like, 04:22.000 --> 04:28.000 trying to, getting started, like, the onboarding step is kind of complicated 04:28.000 --> 04:31.000 because then you have a list of different keys you need to check. 04:31.000 --> 04:33.000 And so, we do all this. 04:33.000 --> 04:37.000 I mean, iPad does all these choices for you and gives you, like, something 04:37.000 --> 04:41.000 that doesn't change a lot from your everyday use. 04:41.000 --> 04:46.000 Also, with other things that, obviously, are missing because we are doing everything, like, 04:46.000 --> 04:47.000 in a secure manner. 04:47.000 --> 04:51.000 For instance, for instance, like, pass forward recovery. 04:51.000 --> 04:55.000 We don't have it because we don't, we have no way to link, 04:56.000 --> 05:02.000 I mean, one of your drive in our, in our storage and your user name. 05:02.000 --> 05:06.000 We need, like, both your name pass forward and we can do anything from that. 05:06.000 --> 05:10.000 And so, yeah, there are some things missing, but we try to give you, like, 05:10.000 --> 05:16.000 as a best user experience as, as we can provide in this context. 05:16.000 --> 05:18.000 And how do we do that? 05:18.000 --> 05:22.000 So, the development is made, like, mainly on GitHub. 05:22.000 --> 05:29.000 You know, it's not the best way to do it, but, at least, we can reach a large community. 05:29.000 --> 05:34.000 And the development is led by the crypto team, which is hosted at XWC. 05:34.000 --> 05:39.000 And it, which is made of nine people, which I'm glad to be part of. 05:39.000 --> 05:45.000 And we have quarterly release where we moved from, to calendar versioning, like, this year, 05:45.000 --> 05:49.000 because we noticed that semantic versioning doesn't mean a lot for a product that is, like, 05:49.000 --> 05:56.000 basically, um, running release, like, we are basically, like, here, every quarter, 05:56.000 --> 06:01.000 we, we met a new release with all the bug fixes, all the improvements, all the features, 06:01.000 --> 06:09.000 uh, in it, after, like, a strict, uh, release calendar with testing and everything, 06:09.000 --> 06:13.000 as much as you can do in a, with our team. 06:13.000 --> 06:18.000 And, uh, if you need anything, like, we have, uh, different ways to contact us. 06:18.000 --> 06:23.000 So, inside the crypto pad, we haven't, and to an encrypted, uh, support system, 06:23.000 --> 06:26.000 which uses, like, actually, the crypto mechanism to, to do this. 06:26.000 --> 06:32.000 Uh, actually, I won't enter into details on how it works, uh, for that, they're, I mean. 06:32.000 --> 06:36.000 There are other resources, uh, and, and, even other tools I gave, for instance, 06:36.000 --> 06:39.000 at Puzzle Salt, uh, last year, uh, so, and so, let's come back. 06:39.000 --> 06:45.000 So, we have also, like, uh, GitHub issues, uh, community forum, and, uh, 06:45.000 --> 06:49.000 a metric space issue need, like, have to ask, like, a quick question, 06:49.000 --> 06:53.000 if you are, like, for instance, hosting your own instance, and you want to have some help, 06:53.000 --> 06:55.000 on that metrics and be the nice place to be. 06:55.000 --> 06:59.000 Uh, community forum, if you have a question, you're not sure if you need to open a GitHub issue, 06:59.000 --> 07:04.000 or simple debugging on, uh, on your instance, and, uh, then GitHub issues for 07:04.000 --> 07:07.000 really development, uh, development parts. 07:07.000 --> 07:10.000 We try to keep everything, like, we separated this way. 07:11.000 --> 07:16.000 And so, no, the introduction is done, and let's see what, uh, what, 07:16.000 --> 07:19.000 have we done in Trippad, like, in the past year. 07:19.000 --> 07:24.000 So, one big change is, I mean, one big thing is on only office. 07:24.000 --> 07:29.000 So, if you are using Trippad, you may know that, um, so we have different applications, 07:29.000 --> 07:34.000 and if you are, and, uh, we are using only office for the office part, 07:34.000 --> 07:38.000 for the main, uh, for, for the quality. 07:38.000 --> 07:44.000 And so, there are, like, uh, spreadsheets, documents, and presentation. 07:44.000 --> 07:49.000 And if you have a free account on Trippad, if, but FR, or even if you are hosting 07:49.000 --> 07:54.000 your own instance, by default, you want, you will only have access to spreadsheets. 07:54.000 --> 07:58.000 And, um, one reason for that is that is, um, was, um, 07:58.000 --> 08:03.000 stability issue we had with, on your face, because if you also know, like, 08:03.000 --> 08:07.000 how only office works, basically, it's mostly the client, which is, 08:07.000 --> 08:08.000 HEPL, which is open source. 08:08.000 --> 08:11.000 I mean, which has an educational license, and then on the server, 08:11.000 --> 08:13.000 it's a little bit more complicated. 08:13.000 --> 08:15.000 And, uh, in our side, what we are doing is, basically, 08:15.000 --> 08:19.000 hiking the client, and we are emulating a server with Trippad, 08:19.000 --> 08:23.000 which will replace the patches that, uh, on your face, does. 08:23.000 --> 08:26.000 So, we are working directly with only office spaces, and, uh, 08:26.000 --> 08:30.000 it leads sometimes, because it has, it has been something that has been hacked 08:30.000 --> 08:34.000 in the world, uh, stability issues, especially with other apps and spreadsheets, 08:34.000 --> 08:40.000 because spreadsheets, but it is, um, the atomic part will be a cell, 08:40.000 --> 08:43.000 and then you have let will, you will have less. 08:43.000 --> 08:46.000 It's less error-pronged, and documents where I try on your face, 08:46.000 --> 08:49.000 sends a lot of, uh, of changes. 08:49.000 --> 08:52.000 I mean, the, the patch are like kind of complicated when you are changing, 08:52.000 --> 08:54.000 something in a paragraph and stuff like that. 08:54.000 --> 08:56.000 And also for presentations. 08:56.000 --> 09:01.000 But the nice thing is that, in 2024, we improve this stability a lot, 09:01.000 --> 09:04.000 and actually this, uh, those two applications with foreign, 09:04.000 --> 09:08.000 like, basically in detail, like, will be released, uh, 09:08.000 --> 09:12.000 in the next, uh, I mean, I think it's, it will be in the next weeks, 09:12.000 --> 09:17.000 next weeks, and at, at most, uh, in the next release, which will be in March. 09:17.000 --> 09:21.000 So, I keep, uh, stays, I mean, stay tuned for that. 09:21.000 --> 09:25.000 And also, like, we want to upgrade it to only office 8, 09:25.000 --> 09:33.000 which has been released, and, uh, like, brings new, new features, uh, for only office. 09:33.000 --> 09:37.000 And now, uh, there are other changes, as well, for, in accessibility. 09:37.000 --> 09:40.000 So, basically what we want to have, um, will, 09:40.000 --> 09:46.000 to point a, uh, web content accessibility guidelines, uh, compliance. 09:46.000 --> 09:51.000 And, uh, for that, we have different focuses, like, 09:52.000 --> 09:57.000 like, on keyboard navigation, like, having it, uh, working as much as possible in 09:57.000 --> 10:01.000 the iPad, we have a lot of, like, fixes to do around it, but, um, 10:01.000 --> 10:08.000 but yeah, it, uh, you can mostly use keyboard navigation to do almost everything in 10:08.000 --> 10:13.000 the iPad. It may not be the most, uh, usable, but at least it's doable. 10:13.000 --> 10:18.000 Uh, there are also, like, focus indicators, like, when you are focusing something, 10:18.000 --> 10:24.000 you need to see where the focuses, especially when you are, like, navigating with 10:24.000 --> 10:30.000 keyboards, and obviously some responsive design, which will be, um, linked, uh, 10:30.000 --> 10:36.000 linked to usability in mobile as well. So, you want to have things that, 10:36.000 --> 10:42.000 can be used in many different devices. And, for that, we did last year, uh, 10:42.000 --> 10:44.000 the next, the next accessibility scan, actually, 10:44.000 --> 10:49.000 collectivity scans, um, in, uh, last August, which was done by, uh, 10:49.000 --> 10:52.000 H.A. University in, uh, in the Netherlands, and, um, 10:52.000 --> 10:58.000 technically, University of Atlanta in the Netherlands. And so, it, it targets, 10:58.000 --> 11:04.000 like, uh, WCAG 2.2, which is basically 2.1, but, but with extra, 11:04.000 --> 11:08.000 I mean, minor changes. I mean, some changes, uh, and it's, 11:08.000 --> 11:14.000 and it's strictly stronger than, uh, 2.1. And if it has done for apps, 11:14.000 --> 11:18.000 so, uh, not it was done for different apps, and for the drive, which is, 11:18.000 --> 11:22.000 which is, uh, why you arrive when you connect on creditpad, and which released all 11:22.000 --> 11:26.000 your files, because it's two different interfaces, and, uh, wanted to have the, 11:26.000 --> 11:31.000 them assessed, uh, differently. And, uh, at the end of, at the end of this, 11:31.000 --> 11:36.000 accessibility scan, basically, the issues are labelled on GitHub with, uh, 11:36.000 --> 11:40.000 hand, uh, accessibility scan, obviously. But the thing that, actually, 11:40.000 --> 11:45.000 the audit says that, um, the suite is quite accessible already. 11:45.000 --> 11:48.000 I didn't put the one for drive, which basically said that the drive is, 11:48.000 --> 11:52.000 I mean, is there a good and well labelled, which is not the case for all the apps, 11:52.000 --> 11:56.000 because, basically, we have integrated many different apps, and we want to have 11:56.000 --> 12:01.000 a, um, protein-nice together, and, um, and yeah, and then we have other, 12:01.000 --> 12:06.000 like, contrast issues and things that we want to address, but it's already in our, 12:06.000 --> 12:11.000 it's in our roadmap, it's in our issues tracking, and we hope to handle them, 12:11.000 --> 12:15.000 as soon as possible. Also, and, uh, 12:15.000 --> 12:18.000 similar or not, like, they have been, uh, 12:18.000 --> 12:24.000 advances in mobile, um, a mobile, like, on the usability of crypto 12:24.000 --> 12:28.000 mobile, uh, we had some good reports about it. 12:28.000 --> 12:32.000 And, um, the thing that here at the goal, what I've been to, 12:32.000 --> 12:37.000 improve the UI responsiveness, having things nice, uh, on mobile, 12:37.000 --> 12:40.000 and improve the mobile experience, uh, 12:40.000 --> 12:45.000 unfortunately due to the way crypto is more, I mean, uh, 12:45.000 --> 12:49.000 I mean, because we have everything integrated, and the way everything is loaded, 12:49.000 --> 12:52.000 is not really mobile friendly, as for now. 12:52.000 --> 12:55.000 So, even if we are, like, having improvements on, like, 12:55.000 --> 12:58.000 the mobile experience, we still have a lot of bottlenecks to, 12:58.000 --> 13:01.000 I mean, a lot of issues to tackle, uh, 13:01.000 --> 13:03.000 before having something very smooth. 13:03.000 --> 13:07.000 And that can work on many different mobile devices. 13:07.000 --> 13:10.000 Obviously, if you have a very good mobile phone, if we'll, uh, 13:10.000 --> 13:14.000 work on, I mean, at least, as, uh, 13:14.000 --> 13:20.000 I mean, in a manner similar to, uh, a computer experience, 13:20.000 --> 13:22.000 but, um, magic. 13:22.000 --> 13:25.000 So, the thing that we, what we did, like, 13:25.000 --> 13:28.000 was to have all elements that, uh, 13:28.000 --> 13:30.000 that are easily accessible and visible and mobile. 13:30.000 --> 13:34.000 So, basically, it's a responsiveness thing, 13:34.000 --> 13:37.000 but basically, when you are on mobile, you want to have things bigger, 13:37.000 --> 13:39.000 so that you can press on it with your big fingers, 13:39.000 --> 13:41.000 at least me, I need that. 13:41.000 --> 13:43.000 And, um, so that's the thing, like, 13:43.000 --> 13:45.000 we optimize the scaling and, uh, 13:45.000 --> 13:48.000 on all the, uh, on all the elements, 13:48.000 --> 13:52.000 especially, like, both that can be quite small, 13:52.000 --> 13:55.000 and also, yeah. 13:55.000 --> 13:57.000 And now, uh, as I said, like, we need, like, 13:57.000 --> 13:59.000 to have, uh, I mean, 13:59.000 --> 14:02.000 there are some bottlenecks on the mobile impact 14:02.000 --> 14:04.000 and, uh, those are actually, like, 14:04.000 --> 14:07.000 in the, in the architecture of Crepad, 14:07.000 --> 14:09.000 and we did also some, uh, 14:09.000 --> 14:11.000 improvement, like, not really on the architecture, 14:11.000 --> 14:13.000 but on the server side, uh, 14:13.000 --> 14:14.000 which is just there for this increment, 14:14.000 --> 14:16.000 I mean, to enable this synchronization, 14:16.000 --> 14:19.000 the thing that we, one of the things we provided this here, 14:19.000 --> 14:23.000 because we met actually in, um, 14:23.000 --> 14:25.000 I mean, in Crepad, we met, like, 14:25.000 --> 14:27.000 some, some scalability issue. 14:27.000 --> 14:29.000 Uh, and, uh, 14:29.000 --> 14:32.000 it was basically, because of the, uh, 14:32.000 --> 14:34.000 Creptography plugin, I mean, 14:34.000 --> 14:35.000 Creptography library, sorry, 14:35.000 --> 14:38.000 that was used in our server to verify the signatures, 14:38.000 --> 14:40.000 basically when you are sending a patch before, 14:40.000 --> 14:42.000 committing it into our servers, 14:42.000 --> 14:45.000 we verify that the signature and the encrypted data 14:45.000 --> 14:48.000 is, uh, is a valid one. 14:48.000 --> 14:50.000 And, uh, this verification step part, 14:50.000 --> 14:52.000 like, was, uh, very heavy. 14:52.000 --> 14:54.000 And, uh, the reason was that we're using, 14:54.000 --> 14:56.000 like, tweet, tweet an SEO, 14:56.000 --> 14:59.000 which is, uh, like, uh, 14:59.000 --> 15:01.000 uh, Creptography, uh, 15:01.000 --> 15:03.000 Creptography library, so jam library, 15:03.000 --> 15:06.000 in JavaScript, in full, in full JavaScript, 15:06.000 --> 15:07.000 which is, like, quite simple, 15:07.000 --> 15:09.000 which is really small, uh, like, 15:09.000 --> 15:12.000 in, uh, in terms of number of characters, 15:12.000 --> 15:14.000 which is not the most, uh, 15:14.000 --> 15:15.000 optimized for hardware, 15:15.000 --> 15:16.000 and, uh, 15:16.000 --> 15:18.000 so we use sedium-native, like, 15:18.000 --> 15:19.000 basically, which will, uh, 15:19.000 --> 15:22.000 which will call the native sedium library in, um, 15:22.000 --> 15:24.000 in your server, uh, 15:24.000 --> 15:25.000 I mean, in our server, 15:25.000 --> 15:27.000 and, uh, as we have an open source license, 15:27.000 --> 15:29.000 especially HEPL, which is, 15:29.000 --> 15:31.000 as it tells us to, uh, 15:31.000 --> 15:34.000 when we are providing a service to show what we do, 15:34.000 --> 15:35.000 so we also, like, 15:35.000 --> 15:36.000 ready for, to the community, 15:36.000 --> 15:38.000 as a cryptographic plugin, 15:38.000 --> 15:41.000 I mean, as a plugin on, uh, on our GitHub. 15:41.000 --> 15:43.000 And if you have an instance, 15:43.000 --> 15:45.000 and you meet this kind of scalability issues, 15:45.000 --> 15:49.000 like, there's actually a blockpost tutorial on it. 15:49.000 --> 15:50.000 Uh, and don't worry, like, 15:50.000 --> 15:52.000 the slides are already on, uh, 15:52.000 --> 15:54.000 on the first-name website. 15:54.000 --> 15:55.000 Yes. 15:55.000 --> 15:57.000 It's divided by two of the CPU, uh, 15:57.000 --> 15:58.000 yeah. 15:58.000 --> 15:59.000 Yeah. 15:59.000 --> 16:00.000 Yeah. So, as we were saying, 16:00.000 --> 16:02.000 like, we divided by two of the CPU's edge, 16:02.000 --> 16:03.000 on the server, with this, 16:03.000 --> 16:05.000 simply with, with, by changing this. 16:05.000 --> 16:06.000 Uh, but yeah, 16:06.000 --> 16:08.000 if you have a, uh, a smaller instance, 16:08.000 --> 16:10.000 it may not be, uh, 16:11.000 --> 16:12.000 like, very useful. 16:12.000 --> 16:13.000 But, yeah, for us, 16:13.000 --> 16:14.000 we have a big instance. 16:14.000 --> 16:16.000 I will show you some figures at the end, 16:16.000 --> 16:18.000 about the use of crypt. 16:18.000 --> 16:20.000 Uh, also, uh, 16:20.000 --> 16:22.000 we also added, like, some, uh, 16:22.000 --> 16:23.000 monitoring plugin, 16:23.000 --> 16:24.000 because, I said, 16:24.000 --> 16:25.000 we have, uh, we have some figures, 16:25.000 --> 16:26.000 and before that, 16:26.000 --> 16:28.000 it was mostly log analysis. 16:28.000 --> 16:29.000 But, uh, 16:29.000 --> 16:31.000 we needed, like, some more fine-drained, uh, 16:31.000 --> 16:32.000 like, measurements, 16:32.000 --> 16:34.000 especially, like, for, um, 16:34.000 --> 16:36.000 on your, different actions. 16:36.000 --> 16:37.000 Why not, 16:37.000 --> 16:38.000 leaking, 16:38.000 --> 16:39.000 and, uh, 16:39.000 --> 16:40.000 we'll just be, like, counting, 16:40.000 --> 16:42.000 for instance, how many times you, 16:42.000 --> 16:43.000 how many times, 16:43.000 --> 16:44.000 for instance, you will download an image, 16:44.000 --> 16:46.000 which can be useful for us. 16:46.000 --> 16:47.000 And, uh, 16:47.000 --> 16:48.000 actually, this way, 16:48.000 --> 16:49.000 you know, 16:49.000 --> 16:50.000 you don't have a good example, 16:50.000 --> 16:51.000 because you can also have it with 16:51.000 --> 16:52.000 log analysis, but yeah. 16:52.000 --> 16:53.000 Like, for more, 16:53.000 --> 16:54.000 more fine-drained, 16:54.000 --> 16:55.000 uh, 16:55.000 --> 16:56.000 monitoring. 16:56.000 --> 16:57.000 And so, 16:57.000 --> 16:58.000 we hope, uh, 16:58.000 --> 17:00.000 we hope in the future that it will help us, 17:00.000 --> 17:01.000 like, uh, 17:01.000 --> 17:02.000 understand more, 17:02.000 --> 17:03.000 how people are using cryptat, 17:03.000 --> 17:04.000 because we have our, 17:04.000 --> 17:06.000 our own idea of what cryptat is. 17:06.000 --> 17:07.000 We are also, like, 17:07.000 --> 17:08.000 we are, like, 17:08.000 --> 17:10.000 obviously a lot of people in, 17:10.000 --> 17:12.000 uh, I mean, in the tech industry, 17:12.000 --> 17:15.000 and so we may not know how people will use 17:15.000 --> 17:17.000 our product in the real world, 17:17.000 --> 17:19.000 because then we just, uh, 17:19.000 --> 17:20.000 like, 17:20.000 --> 17:21.000 give it, 17:21.000 --> 17:22.000 for people to use. 17:22.000 --> 17:23.000 So, yeah, 17:23.000 --> 17:24.000 that's the thing. 17:24.000 --> 17:25.000 And, uh, 17:25.000 --> 17:28.000 the main point will be, uh, 17:28.000 --> 17:29.000 to monitor the usage, 17:29.000 --> 17:30.000 uh, 17:30.000 --> 17:31.000 the data usage for, 17:31.000 --> 17:32.000 I mean, 17:32.000 --> 17:34.000 to have a data that we can use on graph, 17:34.000 --> 17:35.000 and, uh, 17:35.000 --> 17:36.000 to be, 17:36.000 --> 17:37.000 which is, 17:37.000 --> 17:38.000 also, 17:38.000 --> 17:39.000 one thing that can be nice for, 17:39.000 --> 17:41.000 uh, 17:41.000 --> 17:42.000 different, 17:42.000 --> 17:44.000 companies will be, 17:44.000 --> 17:45.000 some single, 17:45.000 --> 17:46.000 some plugin, 17:46.000 --> 17:47.000 uh, 17:47.000 --> 17:48.000 actually, 17:48.000 --> 17:49.000 dates from last year, 17:49.000 --> 17:50.000 but there have been some, 17:50.000 --> 17:51.000 uh, 17:51.000 --> 17:52.000 improvements, 17:52.000 --> 17:54.000 improvements on it. 17:54.000 --> 17:55.000 And, uh, 17:55.000 --> 17:56.000 we can use, 17:56.000 --> 17:57.000 uh, 17:57.000 --> 17:58.000 the main main, 17:58.000 --> 17:59.000 main SSO system, 17:59.000 --> 18:00.000 like, 18:00.000 --> 18:01.000 like, 18:01.000 --> 18:02.000 YTC and, 18:02.000 --> 18:03.000 and you can have both, 18:03.000 --> 18:04.000 actually, if you want, 18:04.000 --> 18:09.000 can have many single sign-on systems on a single instance. 18:09.000 --> 18:12.000 And it's kind of important for organization. 18:12.000 --> 18:14.600 And we also added something that was requested 18:14.600 --> 18:18.000 is like SSO login, I mean, restriction, 18:18.000 --> 18:21.000 I mean, login on Lydia, single sign-on. 18:21.000 --> 18:26.400 And also you can add on top of it, 18:26.400 --> 18:29.200 like also your own password in order to keep your data 18:29.200 --> 18:31.200 really private. 18:31.200 --> 18:34.800 And as I said, like we have some scalability issues. 18:34.800 --> 18:39.000 And one way to address this was, I mean, 18:39.000 --> 18:43.000 was to develop a new server prototype, 18:43.000 --> 18:44.800 which is distributed actually, 18:44.800 --> 18:47.200 because right now, our server is really, 18:47.200 --> 18:49.200 is a single server, I mean, 18:49.200 --> 18:52.000 have to be running on a single machine. 18:52.000 --> 18:54.400 Also call that to be run on a single machine. 18:54.400 --> 18:57.800 So yes, so this is something I actually led last year. 18:57.800 --> 19:02.400 And so it's an independent prototype for the main code base. 19:02.400 --> 19:05.200 And we hope to integrate it at some point. 19:05.200 --> 19:07.000 It's still very exploratory. 19:07.000 --> 19:11.200 We just started having our different components, 19:11.200 --> 19:14.200 and have them communicate one to each other. 19:14.200 --> 19:20.400 So results are quite encouraging, but we hope to finish it 19:20.400 --> 19:26.800 and include it in a real server and have this, 19:26.800 --> 19:30.000 but I mean, maybe done with this bottleneck. 19:30.000 --> 19:33.800 And I have something that will be scalable in the future. 19:33.800 --> 19:35.800 One other thing that I've been done this year, 19:35.800 --> 19:41.200 I've been end-to-end testing with end-to-end testing 19:41.200 --> 19:43.600 with Sprite. 19:43.600 --> 19:50.200 So there is a repository that is available on GitHub. 19:50.200 --> 19:53.400 And we use Sprite to have some automated end-to-end testing. 19:53.400 --> 19:57.600 So basically, simulating real world actions. 19:57.600 --> 19:59.800 There is also integration with browser stack 19:59.800 --> 20:04.400 for different, I mean, to be used on different platforms. 20:04.400 --> 20:11.800 And also test, accessibility with it with X Core framework. 20:11.800 --> 20:14.640 And there are about 300 tests to check 20:14.640 --> 20:19.320 like breaking changes before releases, before each release. 20:19.320 --> 20:25.120 And actually, some bugs were discovered with automated tested testing. 20:25.120 --> 20:29.520 We also, I mean, you also saw that there were some tests that didn't pass. 20:29.520 --> 20:31.520 I mean, in the previous screenshot, it was not one of them. 20:31.520 --> 20:37.920 But actually, there are also some issues that we integrate in the end-to-end, 20:37.920 --> 20:40.320 in the test and giant wing. 20:40.320 --> 20:45.920 In the test suit, to that we also know, like when we are solving some issues, 20:45.920 --> 20:50.920 sometimes we say the effects we can solve those or bugs. 20:50.920 --> 20:59.520 And we also have dedicated testing sense for the releases for that. 20:59.520 --> 21:06.920 And one thing that people have asked a lot is client-side API. 21:06.920 --> 21:09.920 Because basically, the thing that has everything is end-to-end cryptid, 21:09.920 --> 21:15.720 is we provide the web application, and that's basically all we are providing. 21:15.720 --> 21:21.720 It's hard to use in other context. 21:21.720 --> 21:25.720 Actually, it's not a server-side API, which would be really nice to have, 21:25.720 --> 21:34.720 which will, for instance, allow us to connect our calendar to other applications, 21:34.720 --> 21:36.720 because right now we cannot. 21:36.720 --> 21:40.720 But here it's a client-side API, which allows you to use 21:40.720 --> 21:45.720 as a synchronization tool, like elsewhere. 21:45.720 --> 21:49.720 And the goal is to use, I mean, to have an end-to-end cryptid editor, 21:49.720 --> 21:55.720 without any data processing sense that you can use in other contexts. 21:55.720 --> 22:02.720 And we also have an integration, which next cloud was your project for this. 22:02.720 --> 22:07.720 And so that was what was new on the crypto development part. 22:07.720 --> 22:15.720 And now I will tell you a bit about our many instance, and how we are managing it. 22:15.720 --> 22:22.720 So basically, the thing that we had some locality of service issue at the beginning of last year, 22:22.720 --> 22:29.720 our server was like crashing or like very low, I mean, slow to answer. 22:29.720 --> 22:35.720 And so that's what I said with our scalability issues and everything. 22:35.720 --> 22:45.720 And the thing that what we did, we did the object thing, like, is to give more resources to put more resources in it. 22:45.720 --> 22:49.720 But it won't solve the issue in the long term. 22:49.720 --> 22:54.720 And so there have been also, like, this crypto collaboration change to solve this. 22:54.720 --> 23:01.720 And we also change the file system we use, because actually, in crypto, our database, our database, 23:02.720 --> 23:04.720 is the file system. 23:04.720 --> 23:09.720 And so it's really dependent on the performance of the file system. 23:09.720 --> 23:17.720 So before that, we had a BTRFS, and we had issues with it, especially. 23:17.720 --> 23:22.720 And so now we move to the interface and the data access is also faster. 23:22.720 --> 23:27.720 And only in all, like, it makes crypto, like more reliable nowadays. 23:28.720 --> 23:33.720 And the crypto ad part, we also introduced, like, crypto cloud at the end of last year, 23:33.720 --> 23:42.720 which basically allows you, I mean, which is a form, a form that will allows you to create a cloud demo instance, 23:42.720 --> 23:52.720 like simply like with some clicks create on the crypto ad cloud, I mean, a subdomain of a crypto ad cloud, 23:52.720 --> 23:56.720 create a crypto ad instance. 23:56.720 --> 24:00.720 And then explore, like, the different, I mean, the administrative part of crypto ad, 24:00.720 --> 24:05.720 and the crypto cloud features, if you want to trade, you can go and 24:05.720 --> 24:09.720 crypto ad.org it at the bottom of the page. 24:09.720 --> 24:13.720 And then customizes, as you need, I mean, for your needs, because, for instance, 24:13.720 --> 24:19.720 you may want, like, when, for your association, or for your company, 24:19.720 --> 24:23.720 and it can be a way to create it, like, easily. 24:23.720 --> 24:30.720 And have, like, I mean, that we will, we will all, we will all sit, but as an independent instance, 24:30.720 --> 24:37.720 and as part of crypto ad.fr, and, yeah, and the thing in the, you can manage your own instance, 24:37.720 --> 24:42.720 which we saw else as well, if you have a page instance. 24:42.720 --> 24:48.720 And on the usage statistic part, like I said before, I will give you, like, some insight. 24:48.720 --> 24:52.720 The thing that, like, we have on the crypto ad, for instance, 24:52.720 --> 24:57.720 like, basically six, six point five thousand people, like, 24:57.720 --> 25:00.720 registering, like, every month on a crypto ad. 25:00.720 --> 25:04.720 And the bad activities actually, how many times, I mean, one productivity is 25:04.720 --> 25:08.720 counted when you open a pad, or created or created one. 25:08.720 --> 25:14.720 And so, basically there is, there is one million pads open per month. 25:14.720 --> 25:19.720 But to give you an idea of how much traffic we have to handle. 25:19.720 --> 25:21.720 Yeah, no, yeah. 25:21.720 --> 25:23.720 We don't know for the other instances. 25:23.720 --> 25:26.720 Yes, it's only for crypto ad.fr, is the instance we are managing. 25:26.720 --> 25:32.720 And also, like, in terms of, unique IP addresses, it's not exactly how many people, 25:32.720 --> 25:34.720 but it gives a real idea. 25:34.720 --> 25:40.720 We also had, like, 20 more, percent of people using crypto ad per month. 25:40.720 --> 25:44.720 And all the figures are actually, like, mostly average. 25:44.720 --> 25:48.720 So, when the end lecture is, like, something like this, 25:48.720 --> 25:53.720 seven thousand people, like, I mean, new registrations last year, 25:53.720 --> 25:55.720 for free account. 25:55.720 --> 26:00.720 And one other thing that is kind of, like, funny to look, like, 26:00.720 --> 26:05.720 doesn't give a lot of information, but it's kind of interesting. 26:06.720 --> 26:11.720 So, most of our users are actually from the United States, like, more than a quarter, 26:11.720 --> 26:12.720 and a little bit less. 26:12.720 --> 26:16.720 I mean, and with Germany, it's, like, exactly half of our users. 26:16.720 --> 26:18.720 Different of that, it was, uh, many Germany, but yeah. 26:18.720 --> 26:22.720 And actually, as you, I mean, I, for the say, but crypto ad, 26:22.720 --> 26:26.720 of the crypto ad.fr is, from a French company. 26:26.720 --> 26:30.720 And actually, there is only seven percent of people from France using it. 26:30.720 --> 26:34.720 And, uh, yeah, that, uh, kind of interesting. 26:34.720 --> 26:39.720 I think that the first word is related to the fact that many thought 26:39.720 --> 26:42.720 exit in all that need to. 26:42.720 --> 26:46.720 But, uh, it may be possible, because we are only, uh, I mean, 26:46.720 --> 26:49.720 we only analyze, uh, IP addresses and GUIP, so. 26:49.720 --> 26:50.720 Ah, yes, sorry. 26:50.720 --> 26:54.720 Uh, the question is, like, was that, uh, do I think that it may be 26:54.720 --> 26:56.720 related to the, to the tour nodes? 26:56.720 --> 27:00.720 I mean, exit node distributions, and, uh, my answer is, like, 27:00.720 --> 27:02.720 it's, maybe possible, because we, 27:02.720 --> 27:05.720 I mean, we don't have that many data to analyze. 27:05.720 --> 27:06.720 So yeah. 27:06.720 --> 27:08.720 It's a possibility. 27:08.720 --> 27:12.720 Uh, and now for the funding, uh, status of crypto, uh, 27:12.720 --> 27:14.720 uh, a neat question. 27:14.720 --> 27:18.720 Uh, so, we have a transparent management, so, like, 27:18.720 --> 27:20.720 actually, we just published, I mean, 27:20.720 --> 27:24.720 Ludovic here, uh, wrote, uh, the funding status, uh, 27:24.720 --> 27:27.720 uh, of last year, which is on our blog. 27:27.720 --> 27:31.720 And, uh, to summarize it, basically, we have medium-term financing, 27:31.720 --> 27:35.720 with, with our products, uh, which gives us, 27:35.720 --> 27:37.720 basically, two, three years, uh, of safety. 27:37.720 --> 27:41.720 Uh, however, it's on research projects, and then it's also 27:41.720 --> 27:43.720 have the, I mean, I mean, it's not really, 27:43.720 --> 27:45.720 we cannot choose it as we want. 27:45.720 --> 27:47.720 It's really, like, oriented. 27:47.720 --> 27:51.720 Uh, and I think that we don't, uh, achieve sustainability. 27:51.720 --> 27:57.720 So, as I said, like, we, we had, um, two, I mean, 27:57.720 --> 28:00.720 24,000 new accounts. 28:00.720 --> 28:02.720 Basically, we rich these years, uh, 28:02.720 --> 28:03.720 270K. 28:03.720 --> 28:07.720 I mean, 270,000 accounts, like free, uh, 28:07.720 --> 28:08.720 uh, registered. 28:08.720 --> 28:10.720 But in the end, we rich. 28:10.720 --> 28:14.720 And Wednesday, the 10,000 paid subscription and crypto. 28:14.720 --> 28:15.720 Yeah. 28:15.720 --> 28:16.720 So, thousands, sorry. 28:16.720 --> 28:18.720 There's a 1,000 subscription and crypto. 28:18.720 --> 28:22.720 So, you can see that it's not, uh, a very good, uh, 28:22.720 --> 28:26.720 conversion ratio, but, uh, right, but yeah. 28:27.720 --> 28:31.720 We need, like, basically, uh, more independent revenue streams. 28:31.720 --> 28:34.720 We also have donations, like, for different, uh, 28:34.720 --> 28:36.720 uh, the natals on open collectives. 28:36.720 --> 28:40.720 And I said, like, uh, we, we have, we have many different products, 28:40.720 --> 28:42.720 like funded by VPA friends, that is, uh, 28:42.720 --> 28:48.720 which is our major, main, medium-term financing, uh, financing. 28:48.720 --> 28:52.720 Uh, we also receive, like, uh, 28:52.720 --> 28:55.720 money from NNAT and NJ, NJ zero and, 28:56.720 --> 28:57.720 more generic NJ. 28:57.720 --> 29:00.720 And, uh, your, your opinion as well, but, uh, yeah. 29:00.720 --> 29:04.720 We're not, uh, we don't know how we, how we will go, 29:04.720 --> 29:06.720 but, uh, if you want to learn more about it, 29:06.720 --> 29:10.720 actually there is, there will be a talk from Ludo at 10, 30 tomorrow. 29:10.720 --> 29:13.720 Um, in the first funding, uh, room. 29:13.720 --> 29:16.720 And, uh, so, basically, to compute. 29:16.720 --> 29:20.720 Uh, so the crypto project, I mean, 29:20.720 --> 29:22.720 the progress on, uh, many different fronts. 29:22.720 --> 29:26.720 We, we had, like, progress in, uh, 29:26.720 --> 29:29.720 different, different fronts and, uh, which are kind of, um, 29:29.720 --> 29:31.720 I mean, which are important, like, accessibility, 29:31.720 --> 29:33.720 which is, uh, really important. 29:33.720 --> 29:35.720 We want to, make it, I mean, 29:35.720 --> 29:39.720 basically, uh, our main point is not to give, 29:39.720 --> 29:43.720 I mean, our main point is to give something that people can use. 29:43.720 --> 29:45.720 I mean, everyone can use, uh, 29:45.720 --> 29:48.720 uh, while knowing that behind it's secure. 29:48.720 --> 29:51.720 So UX is really, uh, is really important here. 29:51.720 --> 29:56.720 And, uh, we had, we had improvement on, uh, UX UI on this, uh, 29:56.720 --> 29:59.720 we had improvement on UX UI and also some back-end improvements 29:59.720 --> 30:02.720 that you won't feel like directly, but, 30:02.720 --> 30:05.720 that we had to do to make it still usable, 30:05.720 --> 30:07.720 at least on crypto.fr. 30:07.720 --> 30:10.720 And, uh, so I also like new plugins for the crypto ecosystem. 30:10.720 --> 30:12.720 We hope to have more in the future. 30:12.720 --> 30:16.720 And it can be used, like, that you can install as a server 30:16.720 --> 30:18.720 depending on your needs. 30:18.720 --> 30:20.720 So if you need SSD, you can install the SSD plugin, 30:20.720 --> 30:22.720 but it's not there by default. 30:22.720 --> 30:26.720 And, uh, and, uh, on the product side, 30:26.720 --> 30:28.720 then, uh, we have, like, like, 30:28.720 --> 30:30.720 as you see that there is, like, 30:30.720 --> 30:32.720 20, 30% growth and, uh, 30:32.720 --> 30:34.720 crypto that they further are more and more people using it. 30:34.720 --> 30:37.720 We hope that it will, um, 30:37.720 --> 30:38.720 okay, continue. 30:38.720 --> 30:40.720 And actually, for the thousand people, uh, 30:40.720 --> 30:42.720 there will be, um, 30:42.720 --> 30:44.720 there will be a promotion, uh, 30:44.720 --> 30:46.720 promotion could, uh, next week, I guess. 30:46.720 --> 30:48.720 So stay in touch. 30:48.720 --> 30:52.720 And, uh, if you want to have your own crypto instance, 30:52.720 --> 30:56.720 you can also try, I mean, we can also use a crypto cloud if you want. 30:56.720 --> 30:58.720 And, uh, for the next steps, um, 30:58.720 --> 31:00.720 so here is a QR code for the roadmap. 31:00.720 --> 31:02.720 And, actually, if you go on the slides, uh, 31:02.720 --> 31:05.720 online, uh, those are applicable. 31:05.720 --> 31:08.720 If you don't have to scan them, try to open the link. 31:08.720 --> 31:10.720 Um, 31:10.720 --> 31:14.720 so, uh, we, there will be some works on, uh, 31:14.720 --> 31:16.720 first content, uh, integration. 31:16.720 --> 31:18.720 So what it means that we want to have, 31:18.720 --> 31:21.720 like, something like, that is more crypto agile. 31:21.720 --> 31:24.720 And, uh, where basically we can go, 31:24.720 --> 31:25.720 I mean, we can have hybrid encryption. 31:25.720 --> 31:26.720 So meaning that we will have, 31:26.720 --> 31:28.720 we will encrypt with the first one term. 31:28.720 --> 31:30.720 I mean, a quantum secure, um, 31:30.720 --> 31:34.720 an encryption and, uh, 31:34.720 --> 31:36.720 layered with, um, 31:36.720 --> 31:38.720 classical, I mean, uh, 31:38.720 --> 31:40.720 standard one, one of the standard, I mean, 31:40.720 --> 31:42.720 what we have today, um, 31:42.720 --> 31:43.720 actually it's not free encryption, 31:43.720 --> 31:44.720 if we be signature that is, uh, 31:44.720 --> 31:46.720 the most important in our case, but, uh, 31:46.720 --> 31:47.720 uh, yeah. 31:47.720 --> 31:49.720 Uh, so there will be works on it, uh, 31:49.720 --> 31:52.720 this, uh, this summer with, uh, 31:52.720 --> 31:53.720 an intern. 31:53.720 --> 31:55.720 We will continue as well the efforts and 31:55.720 --> 31:57.720 accessibility that is ongoing and, uh, 31:57.720 --> 31:58.720 mobile usage. 31:58.720 --> 32:01.720 Uh, we also, like, 32:01.720 --> 32:03.720 will have an other focus on the quality of life 32:03.720 --> 32:05.720 improvements, so I, 32:05.720 --> 32:07.720 uh, if you are using Crippad here and, 32:07.720 --> 32:09.720 you need, like, more improvements, 32:09.720 --> 32:11.720 don't hesitate to contact us and ask 32:11.720 --> 32:12.720 thing we will, uh, 32:12.720 --> 32:13.720 take it into account. 32:13.720 --> 32:15.720 Uh, there was also one of the things 32:15.720 --> 32:16.720 that have to be done this year. 32:16.720 --> 32:17.720 I mean, 32:17.720 --> 32:18.720 the replacement of, uh, 32:18.720 --> 32:19.720 sick a little four, 32:19.720 --> 32:21.720 which, uh, end of life was, uh, 32:21.720 --> 32:23.720 was less, uh, 32:23.720 --> 32:25.720 last year, uh, not 25. 32:25.720 --> 32:29.720 Yeah, one point five years ago, uh, 32:29.720 --> 32:31.720 for, which takes addition. 32:31.720 --> 32:33.720 I mean, we may replace with, uh, 32:33.720 --> 32:35.720 something between it in the world map. 32:35.720 --> 32:37.720 And also, I said, like, the only of this upgrade. 32:37.720 --> 32:39.720 And so, all of this is, uh, 32:39.720 --> 32:41.720 is provided by you, uh, 32:41.720 --> 32:43.720 uh, from, I mean, 32:43.720 --> 32:45.720 by the Crippad team, which I said is, uh, 32:45.720 --> 32:47.720 made of, like, 32:47.720 --> 32:49.720 10 people, uh, 32:49.720 --> 32:51.720 and, uh, so yeah. 32:51.720 --> 32:53.720 Thank you for, for your attention and 32:53.720 --> 32:54.720 if you have questions, uh, 32:54.720 --> 32:56.720 I think we have, like, eight minutes or something. 32:56.720 --> 32:57.720 Thank you. 32:57.720 --> 32:58.720 Thank you. 32:59.720 --> 33:05.720 So we have, uh, questions. 33:05.720 --> 33:06.720 I think. 33:06.720 --> 33:12.720 Let's consider a case when, uh, 33:12.720 --> 33:15.720 a few users, let's say three users are collaborating 33:15.720 --> 33:17.720 on a document at the same time, 33:17.720 --> 33:19.720 changing one paragraph of text. 33:19.720 --> 33:20.720 So, uh, 33:20.720 --> 33:22.720 conflicts between their changes are, 33:22.720 --> 33:24.720 likely, yes. 33:24.720 --> 33:26.720 And more or, on top of that, 33:26.720 --> 33:28.720 uh, some users may have network issues, 33:28.720 --> 33:31.720 and their updates are coming with a delay. 33:31.720 --> 33:33.720 Uh, do you handle such cases because, 33:33.720 --> 33:35.720 in an end-to-end encrypted setup, 33:35.720 --> 33:37.720 it may be quite tricky. 33:37.720 --> 33:38.720 Yeah. 33:38.720 --> 33:39.720 Actually, uh, 33:39.720 --> 33:40.720 here's a trick, 33:40.720 --> 33:41.720 a trick as part will be, uh, 33:41.720 --> 33:43.720 a network issue, uh, 33:43.720 --> 33:45.720 because actually the thing that, uh, 33:45.720 --> 33:46.720 uh, we are doing it, like, 33:46.720 --> 33:47.720 we are sending the patches, like, 33:47.720 --> 33:49.720 in a very, I mean, 33:49.720 --> 33:50.720 very small patches, like, 33:50.720 --> 33:51.720 it would be one to three letters, like, 33:51.720 --> 33:53.720 as you type and, uh, 33:53.720 --> 33:54.720 something like, 33:54.720 --> 33:55.720 three, four hundred, 33:55.720 --> 33:56.720 and a second delay. 33:56.720 --> 33:57.720 So, there will be, like, 33:57.720 --> 33:58.720 three small patches, 33:58.720 --> 34:00.720 but then when you say that, uh, 34:00.720 --> 34:02.720 so usually when you are working on the same paragraph, 34:02.720 --> 34:03.720 and it's also real time, 34:03.720 --> 34:04.720 and you see the curve sort of, 34:04.720 --> 34:05.720 other people. 34:05.720 --> 34:06.720 So usually you see, 34:06.720 --> 34:09.720 when you are going to create a conflict, 34:09.720 --> 34:11.720 uh, and as the patches are really small, 34:11.720 --> 34:12.720 they won't be that many conflicts. 34:12.720 --> 34:14.720 However, when there is, um, 34:14.720 --> 34:15.720 a network issue, 34:15.720 --> 34:16.720 and as you said, 34:16.720 --> 34:17.720 there are editing the same paragraph, 34:17.720 --> 34:19.720 so there is a probability that there are editing the same thing, 34:19.720 --> 34:20.720 uh, 34:20.720 --> 34:22.720 then basically I think what will happen, 34:22.720 --> 34:23.720 I mean, 34:23.720 --> 34:24.720 what will mostly happen, 34:24.720 --> 34:25.720 uh, 34:25.720 --> 34:26.720 that the people who will have a good connection 34:26.720 --> 34:28.720 will continue editing their things, 34:28.720 --> 34:30.720 and, uh, 34:30.720 --> 34:31.720 it will create a, 34:31.720 --> 34:33.720 a brand, I mean, a fork there, 34:33.720 --> 34:34.720 which will be small, 34:34.720 --> 34:36.720 and our conflict resolution in this context 34:36.720 --> 34:38.720 will be taking the longest branch. 34:38.720 --> 34:39.720 So basically, 34:39.720 --> 34:41.720 the smallest branch will disappear, 34:41.720 --> 34:44.720 but then when the person will have that connection, 34:44.720 --> 34:45.720 we'll come back, 34:45.720 --> 34:46.720 I mean, 34:46.720 --> 34:47.720 they will see that, 34:47.720 --> 34:49.720 it just, uh, 34:49.720 --> 34:50.720 disappear. 34:50.720 --> 34:51.720 Yeah. 34:52.720 --> 34:55.720 Um, 34:55.720 --> 34:57.720 considering the legal topic to GDPR, 34:57.720 --> 34:58.720 do I get it right, 34:58.720 --> 35:00.720 that derived by zero knowledge, 35:00.720 --> 35:01.720 architecture, 35:01.720 --> 35:04.720 it is not necessary for your customers 35:04.720 --> 35:07.720 to have a data processing agreement with you, 35:07.720 --> 35:09.720 or is this necessary, 35:09.720 --> 35:11.720 if I use this in a business environment? 35:11.720 --> 35:13.720 Oh, this, I don't know. 35:13.720 --> 35:16.720 Frankly, 35:16.720 --> 35:17.720 um, 35:17.720 --> 35:18.720 not sure. 35:18.720 --> 35:19.720 So, 35:20.720 --> 35:22.720 this is, 35:22.720 --> 35:23.720 this is, 35:23.720 --> 35:25.720 it would be nice that the GDPR says, 35:25.720 --> 35:28.720 if you're really making data impossible to, 35:28.720 --> 35:30.720 to be seen or to be, 35:30.720 --> 35:32.720 then you would need it, 35:32.720 --> 35:33.720 but I, 35:33.720 --> 35:35.720 I don't really think that it completely, 35:35.720 --> 35:37.720 waves the need for a DPA. 35:37.720 --> 35:38.720 Uh, 35:38.720 --> 35:40.720 and we do provide DPAs, 35:40.720 --> 35:41.720 only for, 35:41.720 --> 35:43.720 um, 35:43.720 --> 35:44.720 uh, 35:44.720 --> 35:47.720 25 user subscriptions at 500 year, 35:48.720 --> 35:52.720 so if a school or something like that wants a DPA 35:52.720 --> 35:54.720 to be fully compliant with GDPR, 35:54.720 --> 35:56.720 they can get it on Crip at a far, 35:56.720 --> 35:57.720 uh, 35:57.720 --> 35:59.720 at 500 year year, 35:59.720 --> 36:02.720 or 1000 year dependent on the number of users. 36:02.720 --> 36:03.720 Uh, 36:03.720 --> 36:05.720 but we don't provide it for individual accounts, 36:05.720 --> 36:06.720 because it's just, 36:06.720 --> 36:07.720 it's a, 36:07.720 --> 36:08.720 it's a huge paperwork. 36:08.720 --> 36:09.720 We have to sign, 36:09.720 --> 36:11.720 we have to sign documents and stuff like that, 36:11.720 --> 36:13.720 and we don't want to sign something just for free, 36:13.720 --> 36:14.720 or for five years, 36:14.720 --> 36:16.720 because we also need some revenue. 36:16.720 --> 36:18.720 So that's the difficulty. 36:22.720 --> 36:24.720 So I was very, 36:24.720 --> 36:26.720 I went very entested by Crip, 36:26.720 --> 36:28.720 but there is two limitations, 36:28.720 --> 36:30.720 or problems for me, 36:30.720 --> 36:31.720 or for the organization. 36:31.720 --> 36:33.720 The first one is the, 36:33.720 --> 36:35.720 two block of tax of, 36:35.720 --> 36:36.720 right panel, 36:36.720 --> 36:38.720 left panel on the screen. 36:38.720 --> 36:39.720 I have, 36:39.720 --> 36:40.720 uh, 36:40.720 --> 36:42.720 I tried to have a full screen, 36:42.720 --> 36:43.720 but I don't, 36:43.720 --> 36:44.720 uh, 36:44.720 --> 36:45.720 succeed in that. 36:45.720 --> 36:46.720 So, 36:46.720 --> 36:47.720 it was for me, 36:47.720 --> 36:48.720 very important, 36:48.720 --> 36:49.720 and that's cloud. 36:49.720 --> 36:50.720 Next up, 36:50.720 --> 36:51.720 only of this much better, 36:51.720 --> 36:52.720 but it need, 36:52.720 --> 36:53.720 a several, 36:53.720 --> 36:54.720 uh, 36:54.720 --> 36:55.720 framework, 36:55.720 --> 36:56.720 and so that, 36:56.720 --> 36:57.720 Crip, 36:57.720 --> 36:58.720 but for me, 36:58.720 --> 36:59.720 for me, 36:59.720 --> 37:00.720 it's a good alternative to Google 37:00.720 --> 37:01.720 workspace. 37:01.720 --> 37:02.720 It's not safe, 37:02.720 --> 37:04.720 not for user friendly, 37:04.720 --> 37:05.720 and so on. 37:05.720 --> 37:06.720 Uh, 37:06.720 --> 37:08.720 and so the other problem is the, 37:08.720 --> 37:09.720 lack of, 37:09.720 --> 37:10.720 uh, 37:10.720 --> 37:11.720 uh, 37:11.720 --> 37:12.720 guest mode, 37:12.720 --> 37:13.720 not every day, 37:13.720 --> 37:15.720 to have temporarily access 37:15.720 --> 37:16.720 for other people, 37:16.720 --> 37:17.720 very, 37:17.720 --> 37:18.720 uh, 37:18.720 --> 37:19.720 easy, 37:19.720 --> 37:20.720 easy, 37:20.720 --> 37:21.720 not, 37:21.720 --> 37:22.720 complicated tools, 37:22.720 --> 37:23.720 only to test, 37:23.720 --> 37:24.720 or to drive, 37:24.720 --> 37:25.720 prepats, 37:25.720 --> 37:26.720 so, 37:26.720 --> 37:27.720 and so, 37:27.720 --> 37:29.720 I have not discovered this kind of thing. 37:29.720 --> 37:30.720 And so, 37:30.720 --> 37:31.720 okay. 37:31.720 --> 37:32.720 So, 37:32.720 --> 37:33.720 thank you for, 37:33.720 --> 37:34.720 you're interesting, 37:34.720 --> 37:35.720 repeat and, 37:35.720 --> 37:36.720 you're, 37:36.720 --> 37:38.720 what you want about the UAUX. 37:38.720 --> 37:39.720 Uh, 37:39.720 --> 37:40.720 actually, 37:40.720 --> 37:42.720 I don't, 37:42.720 --> 37:44.720 it's a possibility, 37:44.720 --> 37:45.720 possibility for, 37:45.720 --> 37:46.720 uh, 37:46.720 --> 37:47.720 other people, 37:47.720 --> 37:48.720 so to test, 37:48.720 --> 37:50.720 if it is convenient for them, 37:50.720 --> 37:51.720 but temporarily, 37:51.720 --> 37:53.720 it's possible with, 37:53.720 --> 37:54.720 next cloud, 37:54.720 --> 37:55.720 this kind of thing, 37:55.720 --> 37:56.720 and we, 37:56.720 --> 37:57.720 after, 37:57.720 --> 37:58.720 uh, 37:58.720 --> 37:59.720 the given date, 37:59.720 --> 38:00.720 it is, 38:00.720 --> 38:01.720 the, 38:01.720 --> 38:02.720 this facility is shipwessed. 38:02.720 --> 38:03.720 So, 38:03.720 --> 38:04.720 uh, 38:04.720 --> 38:06.720 it will be good to have this kind of thing. 38:06.720 --> 38:07.720 Okay, 38:07.720 --> 38:08.720 because, 38:08.720 --> 38:11.720 actually, 38:11.720 --> 38:12.720 actually, 38:12.720 --> 38:13.720 I think, 38:13.720 --> 38:14.720 it's very easy to test, 38:14.720 --> 38:15.720 you can go to prepare the far, 38:15.720 --> 38:17.720 you can create a document in two clicks, 38:17.720 --> 38:20.720 you can create the document with any of the pads, 38:20.720 --> 38:21.720 you can create an account, 38:21.720 --> 38:23.720 so it's actually very simple to test, 38:23.720 --> 38:24.720 so, 38:24.720 --> 38:25.720 but for, 38:25.720 --> 38:26.720 anybody, 38:26.720 --> 38:27.720 you can do, 38:27.720 --> 38:29.720 and you can share the document with anybody. 38:29.720 --> 38:30.720 I mean, 38:30.720 --> 38:31.720 even if you pay an account, 38:31.720 --> 38:33.720 you can actually share with any people, 38:33.720 --> 38:34.720 they don't have to pay. 38:34.720 --> 38:35.720 Uh, 38:35.720 --> 38:36.720 so, 38:36.720 --> 38:37.720 you can actually, 38:37.720 --> 38:38.720 test very easily. 38:38.720 --> 38:39.720 For my point of view, 38:39.720 --> 38:41.720 you can test more easily than next cloud, 38:41.720 --> 38:43.720 where you have to install the server, 38:43.720 --> 38:44.720 and so on. 38:44.720 --> 38:45.720 If you want to test, 38:45.720 --> 38:46.720 if you want to test, 38:46.720 --> 38:48.720 like an enterprise or an organization, 38:48.720 --> 38:50.720 to test the full instance, 38:50.720 --> 38:52.720 a credit cloud has been made for that, 38:52.720 --> 38:54.720 so we launched it in December, 38:54.720 --> 38:57.720 and you can create an instance and test it for, 38:57.720 --> 38:58.720 for, 38:58.720 --> 38:59.720 for 10 days, 38:59.720 --> 39:00.720 and, 39:00.720 --> 39:02.720 and see, 39:02.720 --> 39:04.720 what it would mean to run an instance, 39:04.720 --> 39:06.720 if it was inside your company. 39:07.720 --> 39:17.720 How practical is it to self-host such a solution? 39:17.720 --> 39:18.720 I mean, 39:18.720 --> 39:19.720 as an organization, 39:19.720 --> 39:22.720 I would probably like to have an access to all the documents, 39:22.720 --> 39:23.720 internal, 39:23.720 --> 39:24.720 organizational documents, 39:24.720 --> 39:25.720 or, 39:25.720 --> 39:27.720 isn't it always the case? 39:27.720 --> 39:28.720 I mean, 39:28.720 --> 39:29.720 let's say, 39:29.720 --> 39:30.720 some, 39:30.720 --> 39:33.720 my employees share some document between themselves, 39:33.720 --> 39:35.720 but me as an administrator, 39:35.720 --> 39:36.720 I can't see it, right? 39:36.720 --> 39:37.720 No. 39:37.720 --> 39:38.720 So, 39:38.720 --> 39:40.720 what if, 39:40.720 --> 39:42.720 the access to this document is lost, 39:42.720 --> 39:43.720 how to restore it, 39:43.720 --> 39:44.720 for example, 39:44.720 --> 39:46.720 what are the real use case for, 39:46.720 --> 39:48.720 for the self-hosting setup? 39:48.720 --> 39:49.720 Okay, 39:49.720 --> 39:50.720 so, 39:50.720 --> 39:52.720 I think there are many questions in one question. 39:52.720 --> 39:53.720 So, 39:53.720 --> 39:54.720 first thing, 39:54.720 --> 39:55.720 for organization, 39:55.720 --> 39:56.720 we have something, 39:56.720 --> 39:57.720 which is called Teams, 39:57.720 --> 39:58.720 where you need, 39:58.720 --> 39:59.720 like some, 39:59.720 --> 40:00.720 team administrator, 40:00.720 --> 40:01.720 and like, 40:01.720 --> 40:02.720 everyone in, 40:02.720 --> 40:03.720 you, 40:03.720 --> 40:04.720 organization, 40:04.720 --> 40:05.720 you need it, 40:05.720 --> 40:06.720 and so that like, 40:06.720 --> 40:07.720 the files will be shared by, 40:07.720 --> 40:08.720 with all the people, 40:08.720 --> 40:09.720 like, 40:09.720 --> 40:10.720 which are part of the team. 40:10.720 --> 40:12.720 So, on this side, 40:12.720 --> 40:13.720 it's, 40:13.720 --> 40:14.720 okay, 40:14.720 --> 40:15.720 then the thing that, 40:15.720 --> 40:16.720 like, 40:16.720 --> 40:18.720 for losing access to a file, 40:18.720 --> 40:19.720 it's, 40:19.720 --> 40:20.720 I mean, 40:20.720 --> 40:21.720 it's basically stored in your drive, 40:21.720 --> 40:22.720 or in your team drive, 40:22.720 --> 40:23.720 like some, 40:23.720 --> 40:24.720 so it, 40:24.720 --> 40:25.720 shouldn't be that, 40:25.720 --> 40:26.720 I mean, 40:26.720 --> 40:27.720 it should be complicated, 40:27.720 --> 40:28.720 like, to lose access to it, 40:28.720 --> 40:29.720 but it's still possible. 40:29.720 --> 40:30.720 But, you know, 40:30.720 --> 40:32.720 if you really lose access to a file, 40:32.720 --> 40:33.720 and you lose the keys, 40:33.720 --> 40:34.720 you're a browser story, 40:34.720 --> 40:36.720 which is one way to find, 40:36.720 --> 40:37.720 your data, 40:37.720 --> 40:38.720 and then, 40:38.720 --> 40:39.720 yeah, 40:39.720 --> 40:40.720 you cannot do much, 40:40.720 --> 40:41.720 that's, 40:41.720 --> 40:42.720 well, the thing. 40:42.720 --> 40:43.720 I said, 40:43.720 --> 40:44.720 like, one of the limitations, 40:44.720 --> 40:45.720 like, 40:45.720 --> 40:46.720 when you lose your password, 40:46.720 --> 40:47.720 you're, 40:47.720 --> 40:48.720 basically, 40:48.720 --> 40:49.720 then, and, like, 40:49.720 --> 40:50.720 uh, 40:50.720 --> 40:51.720 thank you very much, 40:51.720 --> 40:53.720 the police. 40:53.720 --> 40:54.720 Thanks. 40:54.720 --> 40:55.720 And thanks, you all. 40:55.720 --> 40:56.720 Thank you. 40:56.720 --> 40:58.720 Thank you. 40:58.720 --> 40:59.720 Thank you. 40:59.720 --> 41:00.720 Thank you. 41:00.720 --> 41:01.720 Thank you. 41:01.720 --> 41:02.720 Thank you.