 a strange right, and we actually started last century, that's probably before some of you were born, and we were thinking about that we needed something to collaborate among the users at University of Constance. So first of all, we have lectures, we have seminars, and we have meetings, and for all of those, it's always nice to have some notes, and it's not always the same person who wants to take notes, and at some point, you need to add something. So then, there was this great tool called EZPAD, which came out and which we installed. Of course, that was end of life from the beginning, and we were not very happy. At some point, the cloud solution came out, and we had WebODF to install on it, and we were very happy. And then, what happened again? WebODF, as you probably know, more or less started sleeping as the Sleeping Beauty. So we were still looking for the excellent collaboration solution where we could work together on a document, but also chat if there was something to notice about the document we could chat. And of course, there was the option to go with the big guys, and as we are the kind of privacy-liking guys, and we are very big fans of federations, namely being the same thing as one of the first internet protocols started, namely email, we saw that this is not the right way. It's not the right way to put everything to a big corporation and have no longer the control of your data. XMVP was for us the right way of going. XMVP as the extensible messaging and presence protocol, a protocol which from the beginning and in turn and directly supports federation so you can have control over your data, over your chats, over your communication, and at the same time be able to talk to everybody in the world who is also using the same protocol. Since many years, we have a nice client, JSXC, the JavaScript XMVP client that integrates very nicely into several applications, including, of course, NextCloud, which now has our biggest user base. But integrating an application which has requires to sign up at another server is something that's not very easy to be done. So we started a small side project and I'll tell you about that side project and what possibly great future might come from that. So this is what typical NextCloud will look like. So you will have the NextCloud installation, you will have a user database and maybe you're feeding it from an LDAP or Active Directory instance. But more importantly, this user base is not only LDAP and Active Directory behind, but we have a lot of data additionally in the NextCloud. We have the web app tokens, we have groups that we create additionally and yeah, of course, we have local users as well. Sorry, I need to read my own writing. Professors can't read their own handwriting, not even on their slides. So, okay, so we need to pass on that information as well, not just the information that we get from there. So when we started to create JSXC, the first idea was, hey, at the login, we'll hook into it, we'll grab the password from the login panel and then pass it on along to the XMPP server to authenticate. That has this advantage that if you close your laptop screen for a few minutes, that connection will time out. And then you have to re-login but the password is no longer there. Of course, you might want to store that password, but if you're in the browser, the only thing to store it is in a way that all JavaScript in all of your browser essentially can access it, which is of course a no-no. We needed a different solution. So we came up with the XMPP cloud authentication client and the idea was to pass on the information that came from an original authentication source, was augmented by the next cloud and in addition to some time limited tokens that we generate, which solves the password problem, pass it along to the XMPP server using our XMPP cloud authentication app and then have pros of the and so on use the information and at the same time be able to have the groups that are in the next cloud created as groups as well for the chat. And because we were bored or we also started creating additional information, we noticed that the same protocol that we used to talk to the XMPP clients was very similar to what is being used in the mail service environment. So now we can have an entire mail server and my family mail servers are operated like that. These mail servers don't have their own user database but they directly access the user database that is used by next cloud and maybe there are a few more options that can be useful. So we started off trying to make a collaboration but in the end, we ended up creating a new single sign-on solution that we think is very nice for small medium enterprises or families where you don't have to set up some other authentication source but you have the nice way of dealing with the next cloud users app and just have those as a back-end. Thank you very much.