WEBVTT 00:00.000 --> 00:13.640 So, the next presentation will be with Michael Meeks, and it's titled Colabora Online, Richard 00:13.640 --> 00:14.640 Collaboration. 00:14.640 --> 00:15.640 Thank you so much. 00:15.640 --> 00:17.640 Well, lovely to see you all. 00:17.640 --> 00:20.080 Oh, well, you know, I didn't do anything yet. 00:20.080 --> 00:21.640 I should leave on a high. 00:21.640 --> 00:24.360 I think I should quit now, but anyway, thank you for coming. 00:24.360 --> 00:25.360 You're rock. 00:26.080 --> 00:30.880 So, in case you've been living under a rock, I will just present some pictures initially 00:30.880 --> 00:33.560 off of the beauty that is, can't elaborate on mine. 00:33.560 --> 00:35.400 Look at this view, blue, familiar. 00:35.400 --> 00:42.880 Okay, so there is a Google, sorry, a more traditional toolbar UI that you can use, but there's 00:42.880 --> 00:47.520 also a more tabbed tool panel as well that makes it look nice, and of course, all of 00:47.520 --> 00:53.800 your nice spreadsheets and web processing documents in whatever newfangled or horrible 00:53.840 --> 00:55.720 legacy, file format you like. 00:55.720 --> 01:02.160 Lots of good interoperability presentations, even as well, and drawings. 01:02.160 --> 01:04.200 So, we can do it a little bit of diagramming. 01:04.200 --> 01:07.320 We could always improve the user experience there, that will be good. 01:07.320 --> 01:11.200 But, of course, on your mobile phone too, so we can shrink the thing down. 01:11.200 --> 01:16.920 We can turn, actually, the mobile thing you want is, effectively, this slide bar. 01:16.920 --> 01:22.320 So, this is a slide bar panel in the desktop PC version, and we can wrap that, and turn 01:22.320 --> 01:27.480 that into this very nice, one-handed format hang and properties UI. 01:27.480 --> 01:31.320 And you can either run that as a web view component, so you can suck that in, I can 01:31.320 --> 01:36.000 the next cloud app does this, so you can then collaborate inside that application, a very 01:36.000 --> 01:38.000 seamless leap. 01:38.000 --> 01:41.280 And build that into your app, or you can have a fact-lined app that brings, essentially, 01:41.280 --> 01:48.680 the server, the LibreOfficeK base, running offline on your device, so that's pretty nice. 01:48.680 --> 01:52.280 So, how do you deploy it, I mean, obviously, you want it, you've seen it. 01:52.280 --> 01:55.240 So, how can we get it out there? 01:55.240 --> 01:58.680 Well, there are a few tips and tricks, and I believe that the system administrators like 01:58.680 --> 02:02.840 to sneak into this conference, and that gets all sorts of clever things. 02:02.840 --> 02:06.600 So, the easiest way, probably, is to grab the HelmChart, or an all-in-one image. 02:06.600 --> 02:10.480 I mean, there are also people making images that bundle our technology with it. 02:10.480 --> 02:14.560 But, assuming you just want to deploy this at reasonable scale, the HelmChart is a pretty 02:14.560 --> 02:15.560 good way. 02:15.560 --> 02:18.320 Kubernetes makes this very, very simple for you. 02:18.320 --> 02:21.280 And, yeah, there's a whole lot of nice features here. 02:21.280 --> 02:26.560 But one of the things that seems like it might be an issue, but also is a massive benefit, 02:26.560 --> 02:29.000 is that our model is extremely simple. 02:29.000 --> 02:33.360 So, everybody editing the same document comes into the same machine, the same pods, the 02:33.360 --> 02:36.360 same process, the same address space. 02:36.360 --> 02:38.640 And so, the real trick then is that when you load a document, you have a thing called 02:38.640 --> 02:42.280 a WOPPY source, and you have to get through this routing matrix based on your WOPPY 02:42.280 --> 02:45.600 source into that place, and then you can collaborate. 02:45.600 --> 02:46.600 And that's very nice. 02:46.600 --> 02:50.240 So, we don't need very clever ways of synchronizing things. 02:50.240 --> 02:53.920 They're all already synchronized, which is beautiful. 02:53.920 --> 02:56.720 And it does mean that there's no real communication between any of those nodes. 02:56.720 --> 03:00.480 Like, don't load the same document on five different nodes, and then have a message bus that 03:00.480 --> 03:03.960 tries to, you know, that seems just very complicated. 03:03.960 --> 03:07.880 And when you look at the statistics of how many people are editing concurrently, it just 03:07.880 --> 03:09.200 doesn't make any sense either. 03:09.200 --> 03:11.400 So, this is a really, really good model. 03:11.400 --> 03:12.800 And it scales with the network. 03:12.800 --> 03:15.960 It works very nicely with all sorts of load balances. 03:15.960 --> 03:17.760 And it's pretty cool. 03:17.800 --> 03:20.760 And do you remember that I mentioned that each document then has this WOPPY source 03:20.760 --> 03:23.560 identifier that identifies uniquely that document? 03:23.560 --> 03:27.000 That WOPPY source actually has the URL for where to get the document from. 03:27.000 --> 03:29.000 And so, this protocol is really just a web download. 03:29.000 --> 03:31.880 It downloads it off the web, the document, loads it, allows you to collaborate. 03:31.880 --> 03:36.280 And then it posts it back again when it's done or when it all two saves in the background, 03:36.280 --> 03:37.480 which it now does. 03:37.480 --> 03:38.480 So, what does that mean? 03:38.480 --> 03:42.680 Well, that does mean that it's incredibly multi-tenant, right? 03:42.680 --> 03:47.160 So, with a single cool cluster, you can run here as a small selection of some of our 03:47.160 --> 03:51.000 open source partners, who, well, some of the conference here. 03:51.000 --> 03:56.440 I have two next clouds, primarily because, well, it's, you can have multiple systems, 03:56.440 --> 03:58.960 even at the same type, talking to the same cluster. 03:58.960 --> 04:04.680 So, you can get all sorts of economies of scale and wonder, which is really nice and, 04:04.680 --> 04:07.760 you can get the configuration from this from a remote web URL. 04:07.760 --> 04:11.480 So, you can have lots of pods, lots of different bits of server here. 04:11.480 --> 04:14.400 And they just download their configuration, they pull it every minute, and they read 04:14.400 --> 04:18.200 just to adapt for new instances of any of these things coming in. 04:18.200 --> 04:22.600 So, very nice, if you're deploying a real scale, if you're a host, if you want to, you 04:22.600 --> 04:25.320 know, to make this work nicely. 04:25.320 --> 04:30.600 So, since that's pretty all good stuff, but I'd like to just look at some of the, the 04:30.600 --> 04:34.600 most recent features we've added, and one of those is automatic documents. 04:34.600 --> 04:40.040 So, if you're, if you're in a government or a big organization, you'll discover 04:40.040 --> 04:45.720 that forms are, you know, the king, and filling out data, and interacting with that nicely, 04:45.720 --> 04:49.120 is really, really important, that my arrows are looking a bit faint. 04:49.120 --> 04:52.360 But, but essentially, what you want to do is you want to create multiple documents from 04:52.360 --> 04:56.960 templates, you want to get data out of forms, you want to see, see what's going on with 04:56.960 --> 04:57.960 documents. 04:57.960 --> 05:01.600 And so, there are many paths to that. 05:01.600 --> 05:06.640 What we've provided is a rest endpoint, which is very, very simple to use as a tool 05:06.640 --> 05:07.640 component earlier. 05:07.640 --> 05:08.640 The stopsters. 05:08.640 --> 05:12.840 And that then allows you to have a document, a DocX, a Doc, a OTT, what, what have you 05:12.840 --> 05:17.520 like, and to suck all sorts of information out of that as Jason, so you can get all of 05:17.520 --> 05:20.560 these properties, and then you can shove the information in as Jason. 05:20.560 --> 05:24.440 So, you have a document, and Jason, you post it, and you get something back in whatever 05:24.440 --> 05:27.440 format you like, you know, PDFs or whatever. 05:27.440 --> 05:28.440 So, very nice. 05:28.440 --> 05:33.320 So, if a document property is often used for content management systems and, you know, all 05:33.320 --> 05:38.280 sorts of things to tag and organize documents and work out what they are, but probably 05:38.280 --> 05:41.040 more useful are forms. 05:41.040 --> 05:45.320 So, creating forms is something any users should be able to do, and that's all built 05:45.320 --> 05:46.320 in. 05:46.320 --> 05:50.320 There's a nice form tab, which you can click, and get all of these things, and you can 05:50.320 --> 05:54.160 pop them into your documents, and even pre-populate them. 05:54.160 --> 05:55.880 And so, a user can do that very, very simply. 05:55.880 --> 06:00.320 We have a beautiful integration then with next cloud, that then allows you to pick, you 06:00.320 --> 06:06.320 can pick a template there, thumbnail it, and then you can actually just suck all of that 06:06.320 --> 06:07.320 stuff out of it. 06:07.320 --> 06:11.200 So, you know, you can actually start to fill in those template fields in a different UI here, 06:11.200 --> 06:15.600 and underneath it's still using that Jason, Jason API, not any to create documents, but 06:15.600 --> 06:19.640 then to be able to find you and them, edit them, tweak them to your use, which is really 06:19.640 --> 06:20.640 cool. 06:20.640 --> 06:23.480 Of course, it's no good just having text. 06:23.480 --> 06:27.440 We like to have pretty pictures, you know, how, how, how is your data going in this 06:27.440 --> 06:32.080 whole, you know, structure for doing this, you can create slides, you can put content in 06:32.080 --> 06:34.040 them, and we'll see where we'll let go. 06:34.040 --> 06:38.720 So, very, very rich and powerful API, if you need more things, come and tell me, but the 06:38.720 --> 06:39.720 punchline is simple. 06:39.720 --> 06:43.040 You have a document, you have some Jason, you can merge them together, or you can suck 06:43.040 --> 06:48.920 Jason out, and it's very simple, easy to use, and easy to develop things with, which is 06:48.920 --> 06:51.200 kind of cool. 06:51.240 --> 06:57.080 Another thing you discover in, in larger organizations is that some, that you need to be 06:57.080 --> 07:02.360 very polite when you talk to people, so it's no good if you're a vet saying, you know, 07:02.360 --> 07:08.040 dead hamster or something, and just posting that to the guy who's hamster has passed on. 07:08.040 --> 07:13.400 Instead, it's better if you press F3, and a beautiful sensitive block of text arrives, you 07:13.400 --> 07:18.680 know, expressing, you know, the regrets and so on about the, there's this tragedy, and, and 07:18.680 --> 07:19.680 that's great. 07:19.680 --> 07:23.760 And so, you know, the entropy may decrease massively, but the feel improves, you know, 07:23.760 --> 07:27.400 everyone is happy when they get, well, happier when they get this letter. 07:27.400 --> 07:33.000 And so all the text is a really good way of then deploying these large databases of nice 07:33.000 --> 07:38.920 sounding, friendly text that people can type in and complete, and then, then, build on. 07:38.920 --> 07:43.280 And, yeah, so it's just just one way that that sort of stuff goes, goes around the place. 07:43.280 --> 07:47.000 And we've also built a sort of, a nice eye frame, so there's a whole lot of configuration 07:47.000 --> 07:51.040 settings and beautiful things you can do in the underlying engine we have. 07:51.040 --> 07:54.760 And so far, we've really limited how they can be shown, but we now have an eye frame that 07:54.760 --> 07:58.240 you can now embed in an integration like next cloud. 07:58.240 --> 08:02.320 And yeah, you can then configure all of these sort of things, so dictionaries and auto 08:02.320 --> 08:07.920 text and all sorts of other settings to make it very, very easy way of embedding that in 08:07.920 --> 08:08.920 your integration and configure them. 08:08.920 --> 08:13.000 So, you know, when you, when you get your spelling, your spell checker is confused and 08:13.000 --> 08:16.960 can't keep up with the world, you know, you can right click on it, and you can add stuff 08:17.000 --> 08:20.040 to your dictionary and the end of your life is, life is good again. 08:20.040 --> 08:24.800 Actually, if you get back in time, interestingly, quite a lot of our performance problems, 08:24.800 --> 08:28.320 we're rendering this beautiful, busier spline underneath here, turned out this was the 08:28.320 --> 08:32.320 majority of rendering cost back in, you know, five, five years ago, you could render 08:32.320 --> 08:36.640 as many charts or whatever you like, but this is very carefully drawn, yeah, lots of 08:36.640 --> 08:37.640 floating point math. 08:37.640 --> 08:42.360 Anyway, it's fast now, but it would be nice to have fewer of them, which is good. 08:42.400 --> 08:48.240 So, again, this is a new API then that allows us to save many more, many more pieces 08:48.240 --> 08:53.080 back to the, to the, the filesync and share solution, or whoever is implementing that 08:53.080 --> 08:56.040 wapy back end, and then, then bring them back. 08:56.040 --> 08:59.600 It also means that we can start to move settings out of the browser, so there are some 08:59.600 --> 09:07.240 sets of settings, like, are you, are you, are you using dark mode or are you, you know, 09:07.240 --> 09:09.680 do you like to see non-printing characters and there's going to be something that we've 09:09.680 --> 09:13.360 traditionally stored in the browser? 09:13.360 --> 09:16.680 And that's fine, I mean, like it works very nicely, but there are a class of people 09:16.680 --> 09:20.720 who are sufficiently security paranoid that they don't want anything stored in the browser, 09:20.720 --> 09:25.280 not even, I like to see non-printing characters as, as dots and new lives, right? 09:25.280 --> 09:28.760 So, so they get very, very upset, and they inject all sorts of headers, and it would be 09:28.760 --> 09:32.920 nice to have all of our configurations stay on the server, so I think over time we'll 09:32.920 --> 09:39.160 be moving all of that back into our stateless containers and then essentially serializing 09:39.160 --> 09:43.840 them back into, you know, the faster they can share back end. 09:43.840 --> 09:47.240 In order to do that, as you can imagine, when these multi-tenant systems with different sets 09:47.240 --> 09:51.480 of dictionaries and whatever, there's all sorts of cleverness going in. 09:51.480 --> 09:57.080 So, so one of the things we do to make this efficient is that we effectively pre-forke 09:57.080 --> 10:01.640 a collaborative online, so we initialize the back end, which is reasonably large, thank 10:01.640 --> 10:02.640 you. 10:02.640 --> 10:07.840 And then we essentially, we fork that, and that takes about six milliseconds, so I mean, 10:07.840 --> 10:11.840 if you ever, you know, load time or something, you know, we can clone all that state 10:11.840 --> 10:13.520 copy on right, and that's fine. 10:13.520 --> 10:18.240 And we now have this multi-level version, so for each tenant, they may have different 10:18.240 --> 10:22.720 dictionaries, different state, different, everything, and so now we have a clever system 10:22.720 --> 10:27.840 to manage these multiple things, and so it's a double fork system, so it's kind of kind 10:27.840 --> 10:28.840 of fun. 10:28.840 --> 10:34.040 So, we don't hold the things and commenting, so which is really nice, so one of the things 10:34.040 --> 10:35.040 is in this, has funded? 10:35.040 --> 10:36.040 Ah, excellent. 10:36.040 --> 10:40.600 Is the apps at mentioning people in comments, very often, you want to comment on the documents 10:40.600 --> 10:45.680 and also notify someone that they should jolly well fix this piece, or whatever, and so 10:45.680 --> 10:48.040 they get a friendly mail saying jolly well fix this piece. 10:48.040 --> 10:51.440 And there's a comment, you know, you can come to it and see what's going on, and that's 10:51.440 --> 10:56.880 working now, really nicely in next cloud, and the API is there for anyone else. 10:56.880 --> 11:00.040 We've also improved the look of comments, so sometimes people write the whole document 11:00.040 --> 11:04.600 in the comment, instead of in the document, I don't know why, but anyway, that's all 11:04.600 --> 11:05.600 good for them. 11:05.600 --> 11:09.800 And so now you can sort of enlarge this and show comment bigger, I mean, I don't 11:09.800 --> 11:12.320 know, I think in large comment, we'll be about it anyway, we're trying to be working 11:12.320 --> 11:17.920 to improve the English, nested replies, so one of the cool things is that the open source 11:17.920 --> 11:22.920 institutes, you know, who are awesome, and, you know, defined as the open source as it 11:22.920 --> 11:28.080 were, really have big documents, they want lots of discussion and commenting on. 11:28.080 --> 11:32.640 So we added a feature for them, which is this comment only permission for write documents, 11:32.640 --> 11:39.320 we had it for PDF already, because people don't edit PDFs, I guess, much, or they shouldn't. 11:39.320 --> 11:44.160 And yeah, and so we added this for docs, so people can come in and then comment, say on 11:44.160 --> 11:48.760 a legal license document or something, and then we can then do comment threading and, you 11:48.760 --> 11:52.640 know, conversations and this sort of thing, and you can even delete only your own comment, 11:52.640 --> 11:53.640 which is helpful. 11:53.640 --> 11:55.560 So thank you to the OSI for that. 11:55.640 --> 11:59.640 Another thing they've arranged it in was WordPress, making a plug-in so you can just upload 11:59.640 --> 12:05.000 a file into WordPress, and, you know, install every easily and have, you know, your edit 12:05.000 --> 12:09.760 button here and then load that up and then collaboratively edit on your website, extreme 12:09.760 --> 12:15.840 easy to deploy, extreme easy then get commenting feedback, discussion around proposals. 12:15.840 --> 12:21.480 And yeah, kind of, kind of cool, so that's come in the last, last weeks, another thing 12:21.480 --> 12:26.640 we'd be doing with Digit, the European Commission's Digital Governance, whatever thing, 12:26.640 --> 12:31.080 which is an awesome and open social, it's a great company, is adding the same thing 12:31.080 --> 12:32.080 to Drupal effectively. 12:32.080 --> 12:35.360 So, you know, you have this viewing, collaborative online, edit, and collaborative online, 12:35.360 --> 12:38.440 and so you can really get stuck into your sharing documents. 12:38.440 --> 12:43.720 It's quite interesting that people use content management systems are a funny, funny 12:43.720 --> 12:48.080 use cases, you know, whatever you have, you really want to be collaborating in documents. 12:48.080 --> 12:51.960 So, people use all these quite amazing things, you know, you use a bug tracker and you 12:51.960 --> 12:55.960 upload an attachment and really what you want to do is collaboratively editing, or you, you 12:55.960 --> 12:59.080 know, use confidence, and actually it's not used as a wicked tool, it's used as a placed 12:59.080 --> 13:03.160 upload files that you can then collaboratively edit on, or it turns out that there's even 13:03.160 --> 13:08.000 better news, which is, X-Mikki has a beautiful integration here, and so, you know, obviously, 13:08.000 --> 13:13.840 you know, probably Wikki's a better way to collaborate on some situations, and, but if you 13:13.840 --> 13:17.840 have those rich documents now, you can stick those in as attachments and just get this 13:17.840 --> 13:22.920 beautiful, beautiful integration with X-Wikki to edit those files and kind of break on them. 13:22.920 --> 13:27.320 So, collaboration is the key, there's nothing, you just put it over tool, you can to get 13:27.320 --> 13:28.320 it done. 13:28.320 --> 13:34.240 Another thing that Zendis actually funded is user experience improvements, but particularly 13:34.240 --> 13:39.000 finding out what's wrong, so, hopefully you'll tell me at the end what's wrong anyway. 13:39.000 --> 13:44.760 I'm very interested in products input, so grab me at the end, we always try to improve, 13:44.760 --> 13:49.640 but we've built a whole lot of UI logging and some charting tools, the thing we're missing 13:49.640 --> 13:53.040 is that it's a lemantry, so if someone wants to come and do a, you know, so we're fully 13:53.040 --> 13:56.840 enterprise compatible and large American corporation compatible, really we should be 13:56.840 --> 14:00.840 sending all of your private information abroad as it's typed in. 14:00.840 --> 14:05.200 We don't have that bit at the moment, you know, and anyway, so there's no telemetry actually 14:05.200 --> 14:11.080 in there at all, but it will stream a set of anonymized commands in order and rough 14:11.080 --> 14:15.960 time stamps to some files that the system can use to crunch with some tooling we have, 14:15.960 --> 14:19.240 so, you know, it doesn't say what you've entered, it just says you entered some text at 14:19.240 --> 14:23.320 this point and you paste it and all of these other things, so you can then see, for example, 14:23.320 --> 14:28.000 how quickly people actually type versus how quickly they think they type, so, so that's 14:28.000 --> 14:32.240 quite fun, and this guy out here, you might think, is some kind of monster typing group, 14:32.240 --> 14:35.880 but almost certainly they're just mashing the keyboard in the text, test session. 14:35.880 --> 14:39.120 You can be about 10 times faster if you mash the keyboard than if you actually need it 14:39.120 --> 14:40.120 to make sense. 14:40.120 --> 14:45.960 So, other interesting things is you can see how commands correlate and which bits are 14:45.960 --> 14:51.320 used together and so on, you can build pretty heat chops of that, perhaps more interesting 14:51.320 --> 14:56.640 is what is undone, so if you're pairing undue with commands, you know, where is the highest 14:56.640 --> 15:01.280 regret, you know, people type something angry and then they undo it or something or 15:01.280 --> 15:05.920 they wrap their text or they delete pages and their presentations, I think, you know, and 15:05.920 --> 15:11.080 they try and get them back again, and they come back, which is good, so interesting to 15:11.080 --> 15:16.440 see this data and good to pull that out, another thing we've done is add a whole lot of 15:16.440 --> 15:22.960 deeper style features and integrations there, so there's a lot of power in styling documents, 15:22.960 --> 15:26.000 that's really cool, and we haven't had that in collaboration line and we've just added 15:26.000 --> 15:29.960 that, so there's now a style list button, the pops up not just paragraph styles, but all 15:29.960 --> 15:33.960 the character list and page and all the other different kinds of style, that you can 15:33.960 --> 15:39.760 have in managing complex documents, this is very good if you're subtenically neurotic, 15:39.760 --> 15:43.680 so you can find all of those things that shouldn't be in your documents and delete them, 15:43.680 --> 15:46.920 they're unused, you know, whatever, but you can also then see what's actually going on 15:46.920 --> 15:52.640 in your documents, is this spotlight button and you click it, and then suddenly it draws 15:52.640 --> 15:55.920 all of these beautiful things over the top of your paragraphs, so you can see in what 15:55.920 --> 15:59.520 style is being used and then you can correlate that with the numbers and the colors 15:59.520 --> 16:03.760 and work out, what's going on, and make your document as beautiful as it should always 16:03.760 --> 16:08.000 have been, which is great, or perhaps you can work out, you can put a comment in there 16:08.000 --> 16:12.200 going, Jim, you break the document again, please learn how to use styles, you know, or 16:12.200 --> 16:18.240 whatever, and send them a notification, so they learn and grow in a good way, I'm presentations 16:18.240 --> 16:22.480 we've done lots of work on presentations, so this is presenting window feature, which is great, 16:22.480 --> 16:26.960 presented console pieces, so you can see what's coming, which is always relatively helpful, 16:26.960 --> 16:31.240 and we talked about presenting, a lot of screens presenting windows extremely useful for 16:31.240 --> 16:36.840 your video calls, so you're sharing this little window, but not, you can still read 16:36.840 --> 16:42.400 something else while you're in a meeting, so yes, 3D transitions, a whole lot of good things 16:42.400 --> 16:46.680 here with WebGL, so you can see, you know, them all doing wonderful things, I like the WebGL 16:46.680 --> 16:52.600 because we're really providing functionality that no one else provides on web platform, 16:52.600 --> 16:55.720 a lot of the web office suites you'll see out there really kind of rather embarrassingly 16:55.760 --> 16:59.840 up-down and featureless, and we're trying to buck that trend and provide the full, the 16:59.840 --> 17:05.000 full solution for everyone, in as much as we can, the browser, you know, doesn't do everything, 17:05.000 --> 17:09.720 but it provides a lot of, a lot of goodness, and they even added a sound API in a few 17:09.720 --> 17:14.760 years ago, which is great, so you can make sound. Anyway, right, so you snap lines for 17:14.760 --> 17:20.680 arranging things in presentations, very helpful to get everything just right, if you want 17:20.680 --> 17:25.480 to convert your X wiki into a PowerPoint presentation, you know, you can add all these links, 17:25.480 --> 17:29.320 so that you can do sort of choose your own presentation and click on things and jump to slides, 17:29.320 --> 17:32.520 and, you know, it's like one of those novels you could buy as a child, where it's a different 17:32.520 --> 17:37.400 story each time you're all a dice or something, and, anyway, but there's all of these embedded 17:37.400 --> 17:42.040 actions that you can apply to your shapes and so on, and we've made it faster and better 17:42.040 --> 17:47.000 at the starting, so that's good. We try to make it easier for people to work out what they've 17:47.000 --> 17:51.320 done wrong, which is always good, so if you've misconfigured it horribly, maybe you can find 17:51.320 --> 17:55.320 out how, which is good, and we'd links to the SDK or install instructions to say, 17:55.320 --> 18:01.320 yeah, perhaps you need a certificate or something. We do a lot of work to try and isolate 18:01.320 --> 18:07.160 documents and containers, so each document is inside its own container, SCH routes, filtered 18:07.160 --> 18:10.600 system calls, can't do anything, there's no shell in there, there's just fonts and 18:10.600 --> 18:15.400 little information so on, so extremely secure. Unfortunately, we need privileges to do that, 18:15.400 --> 18:20.120 you need capsis admin to see a route, which seems like an odd odd requirement, but anyway, 18:20.200 --> 18:24.280 that was annoying, so within instead we switch to using Linux name spaces where we can't, 18:24.280 --> 18:28.520 so actually we can do both. Linux name spaces incredibly powerful, you can effectively become 18:28.520 --> 18:33.880 route inside your own name space with a different view of the file system, and lock something 18:33.880 --> 18:37.880 down really beautifully, the problem with that is that you become route inside it, anyway, so 18:37.880 --> 18:43.000 there's security concerns with user space name spaces as well, so as soon as we get a tool 18:43.000 --> 18:47.400 we can use to make things secure, some since admin disables it as a security hazard, 18:47.400 --> 18:53.480 which is a shame. But anyway, so the app armor and SELINICs both trying to turn this off, 18:54.760 --> 18:59.320 many things better for open shift, but we can install profiles that say, hey, we really do need to 18:59.320 --> 19:03.320 be able to actually make things secure, so please give us the privileges we need. 19:04.200 --> 19:09.240 Instructability is absolutely vital, obviously, we've done a whole lot of work with PDF 2.0, 19:09.240 --> 19:15.160 again, I think, funded by Zendes, so thank you, and lots of good things coming there and a 19:15.240 --> 19:20.360 better, pretty of standard, lots of interrupt improvements, I think, a better font, 19:20.360 --> 19:23.880 font metrics, we don't have the same font, maybe you can't see the difference between the two 19:23.880 --> 19:27.720 foxes, but there is a difference except they're laid out nicely, the metrics are exactly 19:27.720 --> 19:32.520 the same, and then lots of other interruptability improvements, you know, improve random 19:32.520 --> 19:37.000 count functions and more compliance here and there, and more systematic approach to testing 19:37.000 --> 19:42.600 and avoiding regressions there, and well, here we are, so our partners, customers and community 19:42.600 --> 19:47.560 make it possible, we can't do anything without them. There are some projects where, you know, 19:47.560 --> 19:52.440 there's a money ferry, and yeah, well, there's no money ferry in our world, so we have to actually 19:52.440 --> 19:56.680 work hard and do good things, and that's great, it keeps us close to the users and the customers, 19:56.680 --> 20:01.560 so just thank you again to everyone who's partnered with us, works with us, and does good things, 20:01.560 --> 20:05.960 and I'm trying to get this, this meme into people's minds, so if you just keep saying it to yourself, 20:05.960 --> 20:10.440 like a mantra, it'll help you sleep, and sleep at night, because you should pay for what you 20:10.760 --> 20:15.320 use to keep it free, so there you go, keep doing that pay for what you thank you, 20:15.320 --> 20:22.760 who's paid well, I don't know, I don't know, I don't know. So love is a very powerful force, 20:22.760 --> 20:26.280 but economics is also a very powerful force, and if no one pays, you know, then, then, 20:26.280 --> 20:31.400 well, for what they use, then it's hard to keep it free, so at least do, and there's a final bullet 20:31.400 --> 20:35.480 point, since I just told you it was not about politics, the conference, I thought I would just 20:35.480 --> 20:40.760 share you a friend of mine, Terrace Zoon, and actually this is his hand, and that's a machine 20:40.760 --> 20:45.480 gun bullet, he helped to remove from a civilian and Ukraine, and so I just encourage you to 20:46.040 --> 20:50.760 support Ukraine, and stick with that, and so these are the conclusions, join in, try our 20:50.760 --> 20:54.760 later stuff, it's brilliant, you can download it, there's a code, if you pay for what you use, 20:54.760 --> 20:58.920 you can keep it free, there are great code versions of this out there, that you can download 20:58.920 --> 21:03.560 and use and try, and they're integrated in many of our partners, systems out of the box, 21:03.560 --> 21:07.880 and hey, loads of new features, get involved, get stuck in, the source code is all open source, 21:07.880 --> 21:12.600 obviously, and yeah, the loads of cool stuff there, we'd love to work with you, so thank you, 21:12.600 --> 21:22.280 say very much, thank you, thank you, thank you, Michael, we have about three minutes in 21:22.280 --> 21:25.720 how for questions, there is one question, if you have quick questions, 21:25.800 --> 21:35.480 we have Klim on running now to make it all test test, first of all it's just a thank you for 21:35.480 --> 21:40.520 a frankly astonishing talk, it was very, very impressive, I've a single question about the 21:40.520 --> 21:44.520 automatic document stuff, which is really, it sounds really cool, imagine, so I'm just 21:44.520 --> 21:49.160 what I get clear about like what the inputs are, so imagine, I've got a company, I've got a 21:49.160 --> 21:53.560 bunch of people making documents already there like somewhat structured, maybe it's like a table 21:53.640 --> 21:58.600 with like structured field names in the left hand side and all the junk in the right hand side, 21:58.600 --> 22:04.760 is that the source thing you can deal with? Yeah, exactly that, yes, so if we can't, we'd love to 22:04.760 --> 22:08.200 know because we can fix it, but yes, the idea is that you take your existing documents, 22:08.200 --> 22:12.280 what we really want is not to reinvent the world, you want to take those existing dock eggs 22:12.280 --> 22:16.840 of what are the horror templates and then get them into an open source free world, you know, 22:16.840 --> 22:21.240 suck data out of them, put data into them, and tweak them often people do a mail merge, 22:21.240 --> 22:26.280 but they need to just check the last 1% or whatever, yeah and then, you know, we can convert it 22:26.280 --> 22:30.120 to any format you like, you know, your PDFs, your dock eggs, your XLSX, you know, it's all there, 22:30.840 --> 22:35.320 well hopefully you're open standards, your ADT isn't ODS is installed, so yeah, well this might be the 22:35.320 --> 22:40.360 thing that moves my company away from, awesome, from the office suite, so love, love together, 22:40.360 --> 22:44.920 that's brilliant, yeah, yeah, you, you won't regret it, so yeah, come and see me again and we'll 22:45.000 --> 22:49.800 talk. Great question. Thank you. Oh, is it genuine? Yeah, yeah, yeah, yeah, yeah, yeah. 22:52.200 --> 22:57.960 Just some thing, uh, if I follow me, it was lacking because I don't, I, it was the link was, 22:57.960 --> 23:05.960 it, uh, directs is to, to possibility to have a limited to comments, pay their files, uh, 23:05.960 --> 23:11.000 it was a problem. Yes, commenting on PDFs, so, uh, I, I, I rack my brains, there is some, 23:11.080 --> 23:15.320 some degree of commenting and stamping and putting things on top of PDFs, you can do at the 23:15.320 --> 23:20.200 moment, I believe, I think that's there. Um, so yes, that should be possible in collaboration 23:20.200 --> 23:25.080 with mine, that's my current take, but if, if it's not working in the latest version, we, you know, 23:25.080 --> 23:31.320 come and come and see me, um, yeah, we'll talk to the guy who, uh, who makes it work, it should be 23:31.320 --> 23:38.360 fine, I think. Thank you. Another question, maybe less fun. Oh, oh, what your question 23:39.000 --> 23:43.160 looks like the talk well is pretty clear. Thanks so much for being me. Thank you, Michael. 23:43.160 --> 23:45.160 Let's see guys. Enjoy yourselves.