 So I have a question about me, my name is Dr. Chise, I'm a senior doctor here at Mexico and I work for the Social Security Technology Department for years. For example, I'm a senior doctor here at Mexico, I work for the Social Security Technology Department for years. I work in all the years, I work in many areas, I work in the normal studies, I work in the lab, I work in the social security department, and I work in the immigration department. So I started with a short introduction on what is the health of the region. When we started in Mexico, we had the first time in the island, we wanted to provide the sounds in the left control of the data, we installed a lot of new machines in the company, in your education, we used to do a lot of charts at home, and the data, there are a lot of things like this, you know, who has access to it, and you can go to the pizza office, because there is no pizza office in the pizza office. And also I have developed as a team staff, this is the discount point for all back, and this approach is very high in the island, because in the worst case you can say, the paragraph is a small box at home, and then there is a box that says, maybe only one user is allowed, and then you put it in the box for a company, it's just a place, but of course you want to share the rights and work with them, and you also have the whole Mexico Association, or a different research institute for a company. So we had to find a way to connect them somehow, and that's the whole idea of how the federation came into the room with it. So we thought about a solution to connect this system with the Mexico Association, so that it can share with the people the files, and also work together on the files, as seamlessly as all people do the same on the server. So you can get a solution now, you can have any different, which is any different, to feel the same server or a different server. We have already achieved a lot from that, and I think it's possible to do that, and I'm really proud of that. We also work together on the cloud platform, where we have the idea of technically the ES6, where we have the cloud collaboration stuff over in 2016, but what's most important is that we have the members of the cloud, and we have the initiative right from the beginning, just as a company, and now I think I'm going to show you, because again, we want to continue to work with them, and we want to encourage them to apply for it, and to develop it, and also to sign up to a stage where everybody can use the cloud, address different cloud solutions. And right today, as well as at my friend, we have at least three of them, in the API ecosystem. Next up, of course, this is the volume cloud and the video. So we have three different products. So I will do a little bit about the current state of the cloud, so everything I told you in this part of the cloud, this already in the right-of-the-place. And before that, the next thing we are going to do is the right-of-the-place. When we start developing this cloud stuff, we start with the most obvious thing, and we always have the possibility to create a share, a file or a folder, and sign it up to be by Google, or in a different way, and you can go through this in the browser, and see the files or the folder to share inside. And there we have it, just from the top right of the button, you can share with your editor in Mexico that people who also have a next cloud stuff like this, can click the button, enter the federal cloud ID, and then this gets added to the whole next cloud as a cloud platform, that's the technology behind it. And in the beginning, this was directly integrated as a cloud platform. When you click on it, now it's this next cloud app, and the app standard is the server who has to create a real family to share with you. This is an advantage for the whole of the cloud, that you can see, every first cloud is just up and new. And also, in terms of the mission of the stuff, I can see that it's also new to me, because it's, at some point, when you share the cloud, you just want to get the root quality for some people. And also, if you have to click the mouse, it's still exist, because it's also, by the side example, yeah, I don't have to click anymore, but I still want to see the whole next cloud can still use it in the whole next cloud, so it gives you more flexibility in this stuff, which was added now to the whole next cloud. Yeah. So, I can say, if somebody has a search engine, I don't want to share it. And they can download the root set, I don't want to share it. So, in this case, you can share it with others, because it's a free app. Exactly. You can see in the shell list, it's the factory, and the factory sharing model, and I can change the permissions for you, or I can remove the link, and you will be fine, I can remove you and Lim, which is later, but as a owner, I see it with access to the client and I can completely control it. And then, the second step, of course, was to be treated deeper in the internal shell, the private or base shell. So what we have to do is add to the next step of how we do the page, we back it up and I'll direct it to the share head and I'll say, okay, I want to share this part of this folder with this other user, also it is on a different next step. And definitely by getting this, I mean, cloud landing is quite similar to the e-mail address, which has the user app and the server where the next step is installed. So we can enter this here in the share header and then we can share it with the user to have a base for page. The next thing about this is also that you have the same behavior as the other users that have exactly the same permissions. This also changed here because at the beginning when people just put part of the public, there would be just two options. Two were for the private business, three for legal and two for right. But internal shares has more permissions, so we can allow them to share it and start like this. And as soon as you share it this way, you have also a full set of permissions that you cannot set. You can read it, you can write it, you can reshare it, or whatever, you can propagate all the permissions to the other server to adhere to it. Of course, I can now also use Google shares. You can address a completely different server. So it was something like this, so there's no need to charge for a server to have a server, but that's also something you want to build on, which will come later in the store. And then the next thing we developed was if we had all these two parts in place, then we realized that sometimes it's kind of convenient to fight people, because sometimes you need to know their current cloud ID. So someone would need to tell you, OK, this is my cloud ID and you can share something with me. And we oriented some auto-competition, for example, in the context of it. They could actually find it there, but otherwise it was not possible. Especially for large institutes, which were quite distributed by universities, this happens quite often. Every university has its own next cloud installation, but they work together in regular projects and stuff like this. So this might be a good idea to somehow exchange the use of this, so that you can help people also, if I'm a student or a researcher in a team of people, that are working on a project ensemble like the University of Zürich, but I just can handle this and I can fight all kinds of cloud ID and stuff. I'm working on this because I work on a three-month project. And they're going to use this concept of trusted and serviced. We have two options. One of them is that in such a setup, the university is going to exchange the next cloud software with us manually. And then they add it to the list in the add-ins, I think. And then they add the next cloud to start working together with each other and they exchange the use of this. So as I said, even if they add this list manually, you know the type of university is going to partner companies and work with each other like this, and then they exchange their trust books. And you could also, since I think it's all the same, but we can also handle both the next cloud. Every time I create access to the share with another user, then I add this next cloud to the trusted server. And the same if I accept the sum of the share and I add it out of my credit card and so on. So this way, for example, expand the network of the type of next cloud to know. And then they do what they need to do out of condition and so on. I use a trusted server for the other way or out of my credit to expand the network and then it will open more and more and more and more and more and more. Of course, I also use a private server that comes with all of this. That's why it's a trusted network. As I said, the share will be out of condition from two sources. One is the context that is included later and the other is not. At first look at the context, you can actually have a context that you might want to have a cloud ID and then you can find this in the private server and then extend it to just type in your name and stuff like this. And the trusted servers which are connected to the cloud. So the sum of the shares and the sum of the share I don't want to spy on the other ones from my instance. How is it directly from the other instance? It is directly from the other instance. So also I should share the card with you. You can look at the context for example. You can look at your number one that you will still have a card. It was the connection directly from the other instance. And the card also is also directly from my instance. It is directly from the other instance. It was not insulated by you but the connection can still be directly from the other instance. How is the share out of condition? The share is now connected as a vector to your instance and the sum of the shares can take changes directly from the other instance. It is directly from your instance and you can place your name in your name. Because all shares are always connected to the other instance and it is another vector now and also from the share as in the cloud. So the sum of the shares can take changes from the other instance. I'm very ... You're not epoxy? No. I don't know when the epoxy time will be when you can get the connection between the share and the share. So if you connect the same line if you share a share with either you you are in the same line the same line connects to your server So sometimes you always talk to yourself, sometimes you connect to the next talk, but then my next talk will take a paragraph from me, because it's a really big issue, I don't know what you're talking about. Yes, sometimes you talk to yourself, sometimes you talk to yourself, sometimes you talk to yourself, sometimes you talk directly to yourself. I'm really interested in this and I try to do it as well. I don't want to know. I mean, we have something to transfer only from Files, but the shares... That's why I'm interested in Files, and I think it's really important to stay, because information about who can share which file and who owns the file is not in the file. The file doesn't know who is the owner and who can share me. So next time I can look up who owns the file, because in the file cache, the database will receive the pitch home directory in the file, so I can use it. I think we should merge this external storage app with this federated thing. At the moment, I think there are a few features that can take away this data. Exactly, at the moment that the connection is created, we can use it as a model. So it's basically the same file that we can do a laptop on. It's already the same laptop back then, but of course it might be more basically different than what happens in the future. It's definitely important. What can you do as a player in Mexico? I want to remember the usual. What do you think about launching the next steps in the next few months and maybe in years? Some things are going forward. I think for example, in a few days, but I still want to share the slides. The one point is that I want to make sure that you first decide to send it to Mexico. At some point in time, you can contribute to the point that you can say it's a new term of regulation that you're using, but just shouldn't make a difference. You just share the part of the user, and you shouldn't care if it's a different server or not. So I really want to think that it's as seen as possible. Of course, the moment that you're sharing is really not in file sync. But as you know, the next time you can do much more. You can tell the context. In the future, you can do that collaboration. You can have people who can chat with people. And you really want to go through this federation by just files. And I want to make it more easy to find people. There are a lot of new stuff like this. I trust those, but of course, you can show off and make it more easy to find people you want to share. So one idea is to move this integration forward, this time, to interweave, really represent the user and the group. Always the filter and identify. Always group, type, server, or user, and so on. And first, you can also allow us to talk about this is a user group from the change. Because the moment the user shares to a different group, so I'm just going to identify who's right. But if everybody is going to be identified by the user idea at the server, it means the user share. I'd say the group, the first thing would also be group sharing. Because the first thing you could say, hey, this other company, you're losing two days. This group, I watch most of it. Everybody's message should get inspired, not just the user. And what I'm really interested in, if you really get this done, is that in the long term, you couldn't even think about it. You could even think about the key to a group, which would be different from what an expert also was. And they would keep all the shares. Because in the shared, they would always have the company ID. The company user ID. And just the expert would decide, hey, now it's a user. Now, it's a user share ID connected to a company. And it's an external share ID, which is a very good share. And so our business is at length in the future. We can move that part. We can move people to one side of the line. And we can also contribute ID to share system access to the company. Of course, this is a long time machine. We should not have that in the future. So we need to have that in the future. What was the reason for that? Yes? As I've heard, you think we have to change the share team. Yes, we have to change the share team. Yes, but the share team is supposed to be back then. But we want to move it in this direction. We will see what problems there are there. But that's what we're going to do. We're going to be a share team today. And I want to make sure of that. It has to be a share team. I trust the rest of us as a user, as an expert, user-editor, as an expert to share a value of two to three, and this is going to be a share team. Maybe, as I said, it's just like I just made it. We're also going to send some additional ID to share with you when we start the task. Then we're also going to put together the other software that we're going to use. And then we're also going to put down the standard part that we really need to do in this standard. So we don't want to make it easy to share that and we're going to make it out. But we're going to be a share team. We're also going to be a share team. Yes? Yes? As it was, I think that's it. That's the thing that's there. Yes, that's right. Next. Next. I think it was an open road. Yes. I think it was an open road. Yes. Yes. This is quite a surprise. I will show you quite a lot of stuff. One of the easiest of the lotions of the providers is to provide very much sharing for kind of the public. We've already discussed it here. We've seen it there. We saw it there before. But at least a very good amount of ideas. We've talked a lot about what can we start from and of course we're going to do the same. I hope we can get this done relatively fast. I can't say we can get it in extra 11 or 12, but I think this is something that we can achieve relatively short-term. We want to put it in the category of content, share, highlight, and shoot. I want to say a special level. We want to do the same operations. I was actually going to say that it didn't work just like with us. Because of the same level, I should share it. Exactly. Exactly. We also expect it to be the same level and it's going to be the same level. Of course we want to try for that. We get 7, 7, 7 and it's very, very good. We're going to create this on a whole video chat, video, text chat, start, and then talk a little bit about it before the speed generation. Speed being is a web RTC solution. So I don't want to talk about speed being and people who are on the same server. I can't say I'm on the ring to use the server to join the server, but you can't really say I want to call the user on a different server. And the server also will be bigger about how it was useful to do the video chat in English. Also we didn't have a cloud ID so that I can say directly to my conference and call those X on it. So while I'm in the chat, I'm going to try to know how to call them. And then the server should get in contact with the other chat, the information, the interaction for the call. Yes, sir. I'm missing here. You have read the characters. Corning. How about checking? Texting is also part of the project. It's hard to read. That's the story of the project. Of course it won't be the same kind of information as the project I had before. Yes, sir. You have recently noticed that the sharing from the best of the client-clubs are very important to us. And a lot of the people are just federated with the sharing. Yes, it's also part of the project sharing because the chat doesn't share traffic so we have to set it up. So it should also work for the readership. And I'd like to continue to make it easier to find people. And one concept we need to think about here when we start the work is that we want to put a kind of profile page in the first and second. And much more information about which I think will be seen in this video. But we're going to add much more information in the chat so you can use it in your password and then put it down again. But you can also share your phone and your address, your Twitter ID, your location and stuff. And then we're going to be able to decide who can read this paper. But before that, we need to do some sort of analytics part as we're going to have a personal problem. Because you can share your analytics across the other units of the network all about the public. And it's hard to do it when you're publishing this on an external server that it can't find you. And what to think about putting the stuff like the individual ID model to the page to get it find you. So with this example from my feedback And make sure that people who ask you if it is true that a couple of millions of people at least own the children a couple of millions of children a couple. Yes, I know. Certainly, and that's the people who want to share it. So this is... Why are you doing that? Why are you doing that? Why are you doing that? Of course, yes. I didn't say it, but it's also a distinction. Of course, it's also even interesting. All the typical stuff people are talking to very often. Yes, it's also interesting. We want to give it... Yes, because we want to give it to the thousands to thousands of people. You can go for an email and then you can go for a picture. And then you can... Then look at your next book and ask them what sort of special person. And then you see which account was the most identified. So then you see the phone, can I just email you and fill a comment. That was very fun. And then you can get some sort of information because I want to share that. So what you want to create here is basically a local address book. Similar to what we know from four people who are already in this association. But you can often... Because it's also a private scene. After all the data they want, if they want to... If you want to find an incident and then share it. You can have any name with Michelle there. And you can put that in your browser. And say, hey, where is this person? Where is Michelle? Where is this person? No, no, that's very interesting. So that's what I said. Thank you, everyone. And if you need to ask some questions. I'm happy to answer them. We thought about where to open this. That's very interesting. That's a discussion on how to post the videos. Also, my partners have suggested that we post them. I guess I'll go out here. DNS is also... There's also some discussion on how to use DNS to do this. There's no idea about that. It's still a really tough discussion. I guess I don't know. Of course, I want to go from our director at first. But this is happening because we are sure that there's a lot of people here. And also there's this central service that we don't really like. At least we would have, for example, a beach here, where we get a multiple service which is free somehow. But then we have another output. Only right now we can update the state power. So that's still a lot of problems we have to solve. We want to start easy to do different things. So we just want to explore the hardware. To see how the products are used. And then, of course, there are new ways. DNS is a very good tool. Somehow, we can do that. There are many kinds. That's awesome. We really want to discuss and start with that. That's what we're doing for sure. We're trying to enhance this future, like the beach side. But for users that would like to change their orders, they want to keep online. And they want to do the servers. At some point they think about every new month or a year. And the moment we always have a child in the way because it's always the start of something. It's always the start of something. It's always the start of something. We need to solve something. But it's an English top start. I don't know the thing about that. And maybe it's something. That's what I said. I think our idea is to start with somehow the same result. The people that can decide that I can finish my information with the same result. Similar to the regular phone we have in Germany, we have the Deutsche Telekom. We can say, okay, I can have my name and my address in my phone number. And then they publish these nice yellow books about people who can find them. And this is the first simple idea. We have the same result about people who can accept it. I want the people to find me. I share this and that information with the server. But then, as I said earlier, of course, it's the first time that we want to explore this approach for the dog walkers and the server. And we want to at least start with just a little bit of something. Maybe there are complete different technologies like a nice little bit of software that will give you published information. That's a start of an idea. You see how people use it and how they evaluate it. Thank you.