 Welcome, everybody, to our first announcement of 2022. We are super excited to have all of you here to talk about some really wonderful things. Of course, all these things are possible because of all of you. Our contributors, our users, our customers, all the people who are in and around NextLad. Thanks to you, we have become the content collaboration platform for people who care about digital sovereignty and who care about privacy. So today we want to talk about how we can bring this one step further to the benefit of course of our customers, like the companies and organizations we've been talking about lately on our blog like the city of Geneva or the tens of thousands of middle school students in Luxembourg and in France as well as the hundreds of thousands of students at universities in Sweden and of course at the same time also for all the private users, people who run NextLad at home or maybe at one of our wonderful hosting providers like OVH Cloud or IONOS or Deutsche Telekom. For all of you, we have made some real nice improvements, interesting improvements to NextLad that we're going to talk about, so let's get to it, shall we? In this release, we improved NextLad files in two areas. First we focused on performance and second we improved existing functionalities. Let's start talking about performance. Our goal here has been to reduce the load on servers and increase responsiveness for users with over two dozen improvements. One of the bigger improvements, for example, is having the option to scale preview generation using a microservice. This is basically having a separate service that handles the creation of thumbnails of photos and documents, which spreads the workload and especially has a strong impact for big servers. The second biggest improvement is having a smart background job scheduling to run intensive operations outside of normal peak hours. This means you can now define a time outside of your normal peak hours, where NextLad will execute intensive maintenance jobs in the background instead of throughout the day. Other improvements are smaller, like having a more intelligent avatar size handling. It used to be that a client requested an avatar of any size, however, the result was that the server spent too much time resizing images. The change we have now is that there are only two avatar sizes and this makes caching easier and having a reduced server load. We also made improvements that deal with caching, reduced page load time and optimized database access. I hope this gave you a good idea of the performance improvements in this release. Before I start talking about the new feature improvements, let me first mention our new profiler. In this release, we are introducing a new built-in profiler that is designed to identify performance bottlenecks. It can be enabled on a per user basis and should help administrators optimize the performance of their servers. So an additional part of NextCloud files is that we added onto existing functionalities. One of those involves the enterprise search. We have added a new API, which allows you to retrieve your data from NextCloud and index it in an external enterprise search. We also introduced more advanced sharing permissions. Now users can separately specify the edit, delete and upload permissions within shared folders. This gives you more control over who can make changes in an important folder that you share with other colleagues or external companies. There are many other changes. For example, the option to send a time-limited password token by email for email users. We hope you enjoy the new and improved NextCloud files. In NextCloud Hooper, the development efforts were directed to user conveniences in mail and calendar. In particular, the mail app introduces a new streamlined composer interface in two new great features. The first one is the option to undo a sending of an email and the second one is to schedule send an email. Let's talk about undo send. You might recognize it. You've wrote a mail, hit send and then you realize you forgot something. Now you can click on undo send in NextCloud Mail. Instead of sending the email right away, it will be only sent after about half a minute, giving you time to stop sending the email from a pop-up button. You can then add what you forgot. A second feature we added in Mail is schedule send. This feature lets you choose a time and date when mail should send out the email for you. An automated job will pick it up and send it for you even when you're not online. You can either choose some of the pre-configured options like sending it tomorrow afternoon or next week or simply pick a specific time and date. Let's have a look at the mail improvements. Here is our new composer interface. Let me write an email. Now I send it and use undo to bring it back. Let me schedule it instead. In the calendar app, there is now an accept or decline option for attendance and invitations, so you can update your attendance right there in the web interface. Previously, this was only offered through receiving an email, so now you don't have to rely on mail but through the app itself. With those changes, mail and calendar have become more efficient and easier to use. A very important part of NextCloud is communication. It's a collaboration platform after all. So let's talk about NextCloud Talk. Of course, we always work on scalability and performance, especially if you have calls with a large number of people, you will see performance improvements in this release. In the feature area, the most noticeable and probably most used feature is reactions. You can now react to messages from other people. Another nice addition is the media tab, where you can find all the images and documents that were shared in that conversation. In mobile apps, you now can select an audio device if you have more than one device connected. Speaking of clients, another cool improvement people have been waiting for is desktop client integration. We introduced two integrations in here. First, you can now immediately reply to chat messages from your desktop client. And second, you will not miss any calls anymore because you will get a call notification screen where you can pick up or decline right away. Last year, we've introduced NextCloud Office, a collaboration between NextCloud and Collabora. For this release, we continued work on the user interface and introduced a familiar tapped interface. We made a short video to show you NextCloud Office. The NextCloud Office team also made massive improvements to NextCloud Text. NextCloud Text is an application for note-taking during calls or for managing documentation. This new release introduces tables, info boxes and emoji auto-completion. You can now also just drag and drop images into a text document to insert them. NextCloud Text is perfect for taking notes, for example from team meetings. Let me check the notes from last January. I need to update that to do in the table. Unfortunately, Christine didn't finish her task. I did have a graphic I wanted to share. Let me simply drag that into the document and link to the original project proposal to make sure we all know what we're talking about. Now, these notes seem finished. As you can see, text is quick and easy to work with and it has become even better with the addition of tables, info boxes and image drag and drop. These features also directly benefit our knowledge management system Collectives. Collectives also introduces the option to share a full knowledge base for a public link. Our knowledge base app Collectives benefits from the improvements in text for this release. Like in text, you can now add tables, info boxes and drag and drop images. New in Collectives itself is the public link sharing. You can share a knowledge base as a public link if you want even with editing rights, so for example an external contractor can work on the documentation. We hope our knowledge base will help you retain organizational wisdom. But the biggest feature that NextCloud Office introduces is much improved file locking. Files will now be locked automatically when you edit them in one of the collaborative editing apps like text or Office. The clients will reflect this locked status and you can now lock and unlock files from the clients. The clients will do their best to prevent you from accidentally making changes to files that are already being edited. This reduces the chance of conflicting edits to files significantly. So, that covers the improvements in NextCloud and a lot of improvements. We're talking about NextCloud files, which introduced a lot of performance improvements, as well as of course the minor features like the sharing permissions. We talked about groupware, where you can now undo the sending of emails as well as schedule them. We talked about talk, where you have reactions, a media tab and other improvements. And we looked at NextCloud Office where you had a lot of improvements with the file locking and the new user interface as well as the improvements in text and Collectives. So, this is a huge release of the most popular content collaboration software platform in the world. But we're not done yet. So, NextCloud is all about digital sovereignty, about privacy and that is all about decentralization. That means you want to have more than one vendor for a product. You don't want to be stuck on a single platform. Now, of course, with Microsoft, Google, Dropbox, this is exactly what you have. There's one service out there and you're stuck on that service. They don't let you move easily from one place to another. And this is different with NextCloud. And this is also exactly the area where we're making a big step today. We are today announcing new feature of NextCloud, which is user migration. You will be able to take your NextCloud data, go from one server, let's say, maybe Raspberry Pi at home and move to another server, let's say, a service provider or an online hosting or the other way around. You can take your data back on premises. This is, of course, a huge deal and this is what the big providers, the big SaaS platforms like Google, Apple and others are too afraid to offer. We at NextCloud, all we want to do is make the best possible user experience possible and to help people decentralize their data. Not all the data in the world should be at one, two, three, four, five big companies. It should be at thousands of companies. You should be able to put your data maybe at your company. A part of your data should be maybe at a government agency or at home, on your own server or at a reliable service provider. It should be distributed and not all in one place. And the user migration feature can make a big difference in that regard. So in conclusion, this is our biggest release yet. And we think it's a game changer for the industry. Now there is a third way between staying away from the cloud or losing control over your data. We hope you enjoyed this. You will enjoy this release and you can go get it now because it's all available today. Thank you for watching. Hello everybody. Thanks for joining the aftermath of another release announcement video. Really happy to see a lot of comments. I was already looking at the comments in the chat. Thanks a lot of nice positive things. It's of course for us also very exciting release. A lot of big things. And that's why we're here to talk about that. I first want to say also congratulations to everybody who worked on it. And now a lot of community members who contributed of course to this release. Be it of course writing codes. There are as always a lot of bug fixes and featured improvements all over the place from hundreds of people. But of course also the testing. There was a lot of testing in the last couple of weeks for the clients as well as for the server itself. And I know sometimes it seems like there are a lot of issues in GitHub. Do we look at everything? Well, maybe not everything, everything. But it really makes a difference. This testing period is really important to make the next product a better product. And that's very important of course. There's so many more other things like translations. That's something I often forgot to mention. I mean we have like 100 languages or something. Like including important ones like Klingon for example. Big thanks to really everybody at your site, including the translators. Yes, exactly, yeah. Yeah, there's a lot happening in tech. I mean there's a lot happening in the world, right? It's a bit of a crazy year. So, but let's focus on the tech side. That's why we're here. And so, yeah, as I said, there's a lot happening. Especially in Europe now. There's the Digital Markets Act that's making progress. I'm sure many of you have seen the news. As well as Ursula von der Leyen who was in the US to talk with, I think with Biden about new privacy shield, successor to privacy shield. We have our thoughts on this. And this release also has some features related to it. We really did see of course a lot of this coming. And as I said, we have our opinions. And I think we should talk a little bit about that before we go into the details. Yeah, definitely. I mean, that's a very interesting topic. So, as some of you might know, the GDPR, which is like law in Europe, already requires data portability between different services. But this is not really lift, not really realistic in most cases. Now with the Digital Markets Act, which goes live basically in the next few months, again has this requirement that there should be a way to move data around between different services. And that's something that is so important, in my opinion, our opinion, I guess. Because just imagine if this would not be possible, then you just sign up with some service and you're stuck with the service for the rest of your life. And that's horrible in lots of ways for privacy, for free market, for all kinds of things, for innovation. And this is why portability is so important. And yeah, in the next cloud, we introduced a while ago already a way that you can migrate your data from Google, or from OneDrive, or from Microsoft, or from Dropbox, like to next cloud. This is a very popular feature where you can move your data from decentralized services to your personal next cloud. But something that we really introduced today, for the first time, is a real data portability where you can move it between different next cloud services or servers. That's what I just presented in the announcement video. You can really move your data from your private next cloud on some Linux machine, on a Raspberry Pi, to your university, to your school, to your company, to a service provider in all directions. So basically you can choose the service you want to use based on whatever price or reliability or compliance or reasons or whatever, but you can always take your data with you. And this is in our opinion, really how it should be because it's the way companies use this vendor login, like I have your data, you cannot really move to a competitor. This is really bad for everybody. Yeah, and exactly, and they often use or they offer some kind of export, but then there's nowhere you can import it, right? They're kind of useless. Like you got a bunch of XML and HTML files and weirdly named images. I mean, yeah, I think it's really good that we show how it should be done because I think there is a risk that things will go a little bit similar with the GDPR where there's been a lot of work done by everybody to be compliant with the GDPR, schools and hospitals and all these places are spending a lot of time and effort in it, but then really other important things like the compliance where data is and who has access to it. If you look at the US Cloud Act, you can't, well, you would have to force data hand over to the US government, thanks to the Cloud Act. Yeah, this is a rule in the US for an American firm. So if you put your data at an American company, you would have to hand over, they would have to hand over the data to the government if that is requested. This is incompatible with the GDPR and yet this is done everywhere. And well, Privacy Shield seems to be designed to shield the big tech companies from the GDPR there and that's just, yeah, we wanna show that it can be done properly and we hope that the DMA will be implemented also, well, in the right way in that regard. So let's talk a little bit about what's been happening with this release and the questions because there's a whole bunch of questions that we already have. So Tilo asked a question and he asked, oh, that's about the emojis because there's now reactions and a lot of people really liked the reactions and talk with us. I don't know, I personally, for me, this was like, ha, this is so nice. You know, I use this all the time. I mean, we use it like internally and in next cloud already for a while and like everybody's so excited about it. This really improves the overall like interaction so much with these reactions. And I also want to point out that's a bit cool and I'm a bit proud of that we actually introduced it before WhatsApp. So, yay, yay for the talk team. Yeah, exactly, that's true. And it's also on the mobile apps, right? Which is, it's on all the platforms, so that's, yeah, that's really good. So the question from Tilo is, will there be emoji type in shortcuts so that you do, you know, call on or something and let it then auto-completes to an emoji? I saw some work about auto-completion of emojis, yes, exactly. I don't know the correct status but I saw that someone is working on that, yeah. Yeah, because we have emoji auto-completion in text, which is the same as in GitHub, you know, you type colon and then you type happy or angry and, you know, you get emojis to choose from, which is also, yeah, it's nice. So there's some code library needs to be unified and then it works all over the place, exactly. Exactly, that would be cool. So Walter asked about scheduling emails. Is this possible with every mail account or only with Gmail? No, that's possible with every mail account. Yes, it's a feature on the cloud mail. You use Gmail with next cloud mail? I mean, you can, of course. I mean, Gmail has an IMAP in the feature, but yeah, no, that works for everything, yeah. Yeah. So Carl Emile Mika asks if the end-to-end encryption app is abandoned in development or put on hold? I think we did a release of it three weeks ago, so. Yeah, that's actually work being done at the moment to update it to 24, like right now. There were some discussions about it like two weeks ago. No, that's not abandoned at all. Yeah. Yeah. So Jan asks about to move the data from next out to another cloud source and the other way around. Will security permissions be preserved? So I think this is talking about the share permissions and such. Yeah, so at the moment, I think, what is the state of this right now? Yeah, so maybe this is something to clarify. Because this data migration that we just talked about 10 minutes ago, that's in discussions for years and years and years. And the reason why it didn't happen earlier is because it's really complicated. Because we have all kinds of data. I mean, as you know, in next cloud, we have calendar and contacts and tech and chat and all kinds of things. And really migrate everything over is a lot of work. And this is why we decided to just start with the basic data and we expand it over time with more data. So as far as I know, we have files, we have calendar, we have contacts. And I think that... So it does the profile also like the basic set. Yes, exactly the data profile data, yeah. And this kind of things. But it doesn't do everything yet. So this will be enhanced over time. And I think the shares are actually, I mean, shares is sharing with another user like a local share is tricky because if the other user is not in the new system, then this doesn't work. But one idea is of course to migrate share links, which again is a bit tricky because the link changes because you're a new server now, new URL. But the goal is to migrate it still like with the same permissions. But I think this is not done yet. No, I mean, this part is hard indeed because of course a public link no longer works because you're on the other server anyway, right? This is kind of tricky. And the share between users, I mean, I think the best you could do is kind of make it a federated cloud share. This is I think what they were discussing. Yes, that's the plan to still being able to share with the same user, but that's then a federated share which is server to server sharing to the old system, which is possible. We have the APIs for that, but it's, yeah. It's a work in progress, a bit tricky. So like your favorites get stored, your comments also and that kind of metadata. There's a whole bunch of stuff that gets migrated, but the shares at the moment, we haven't really figured out a good way to do that yet. So in the export screen, you can see from each app, there is a description of what is being exported and whatnot. So you can really see, for example, in profile, your profile gets updated, gets exported with your email address and your phone number and your social media links. Like it numbrates for each of the apps very clearly what is coming. Exactly. What's actually part of the design requirement at the very beginning that we're completely transparent about what data is actually exported and can be imported and so on. So that you're not later not surprised that like, I don't know or I thought like, I don't know some nodes are migrated while they are not. So we're completely transparent on this export screen as you're seeing. You can configure it, at least on the level of app. So you can say, okay, I wanna just export my calendars and nothing else or I want the files and the calendars and my profile, but et cetera. So you can configure this. So in time, of course, more apps will start to support this when they're updated to work with Nexel24 and with the migration feature. So someone asks, is Nexel24 better? It is not. No, it's not. It's final today. That's something, I mean, me personally, but I think everybody at Nexel24 are really, we're not big fan of pre-announcements. So we really try to, everything we announce is then really available. The code is there, it's production ready. You can download, you can use it today. So the desktop client should be available as well. The mobile clients, I mean, of course, there are gatekeepers there, Google and Apple, that can sometimes take a while before they approve an app. We try to do it in a way that the apps come out on the release day, but it's often very hard to do this by the hour. But yeah, these should all be coming out very soon. So there's another question from Jan about group and user access. So I think we've discussed this now with the migration. This just, some of the things are kept, but at the moment, we need to look how we can, yeah, what can be migrated sanely. I mean, public links, I think, is not possible, for example. So, Bunbot on asks, well, Nexel24 work after upgrading the host server to Ubuntu 22.04, I'm guessing that is very much a question about PHP versus Maria DP. I actually did this personally last week. So I can confirm that it works. There we go. I had not expected an answer to that. No, that's coincidentally, I did exactly that. It's working, yeah. I mean, Nexel, we always support new PHP versions, not like other projects where you have to be a bit more careful, but we always try to really be up to date with the latest PHP versions. Also like, not only support a deprecated one because there are no longer security fixes available from the PHP community. So yeah, we're trying to be up to date and we are in this release, of course. Yeah. Kind of related question is, if we support Maria DB 10.6, I'm now guessing you also know that, or is that too detailed? But there's, okay, I don't have the full information. I think there's a problem with newer Maria DB versions that change something in the table format. I'm not completely sure, I'm sorry. Please ask in the forum, in some other words. I'm sure we'll get to that. But yeah, I had also read something about Maria DB stuff, but I don't know the details either. All right, then uncle Dan says, not a question, I just want to thank the team for the all-in-one implementation. He migrated to it immediately on the release and it makes admin really easy. So, love you guys. Yeah, yeah, the all-in-one thing is we will get back to that in a few weeks. That's an ongoing project. We started and announced it in December last year. It's the idea to have this all-in-one package, which is Docker that is built in a way that you really don't have to do a lot of installation, work configuration, maintenance, updating. You don't need to do any command line stuff. You have this one container. You can run it. You can update itself. It's like reconfigured with all the most important next-glot apps. And the design goal was to make it just to run it super easy for everybody. And yeah, I think it's really working because thanks for the nice words. We also hear from a lot of other people that are happy with the approach. So this is an ongoing project. Yeah, it's really cool, the all-in-one, I think. Yeah. I mean, I'm still running kind of like directly on my open SUSE system. I don't know. It's still maintaining that. I'm really thinking at some point, I should just install the all-in-one. But of course, also the migration is a lot of work, so it's this kind of like difficult choices. David asks if there is a self-hosted email server within NextCloud. That's a regular question. We didn't implement an IMAP SMTP server, and we probably never will because there are actually great open-source mail servers out there that we can use from inside NextCloud. So the next-glot mail is the interface. It is basically an IMAP, an SMTP client, has advanced features, as we heard today with scheduled sending and stuff like that. But the actual IMAP and SMTP is something we are not doing in NextCloud. I think this is really out of scope. There are so many great mail servers out there. Several of them are part of the latest Linux distributions. Just pick one you like. But I don't think we should or will implement an IMAP server. That's not what we want to do. I think we should focus a lot more good ads, which is in the end the user interaction, the user interface, the user underlying technologies and not re-implement everything. Only where it makes sense and has a real end user benefit. I think that's the key for us. On that slightly related note, Meg asks if we discuss the possibilities for in-browser offline mail support. I don't know. Go to GitHub, look into the mail repository, into the issues if there's a discussion about it. I'm not aware of it personally. I'm personally not super sure. It's super high priority. I get it. I don't know. Maybe you're in a plane. You don't have internet. You don't have internet. You don't have internet. You don't have internet. You don't have internet. I don't know. Maybe you're in a plane. You don't have internet access. You want to write some mails and send them later. Yeah, I don't know. But I think you and me are also still very much desktop client email users. Well, I think in the future it will be the combination. That's the general thing by next slide, by the way. Sometimes I do file management locally and the desktop clients do it. Sometimes I do it in the web interface. Sometimes I do it on the phone. Or on the tablet. And it doesn't matter because, of course, we all work on the same data. Oh, I see. And I think it's the same with mail. I mean, there are some scenarios where I prefer a desktop mail client or a mobile mail client. But there are some scenarios where the integrated web interface is also very cool. And we have these integration features that we always like talking about. And at the end, it doesn't matter because they're all the same mails. They're just different UIs for different context for different situations. So. Yeah, it's true. So for now, the scenario in an airplane is a situation for an offline client. Yes, I just think so. Fair enough. Yeah. It's true. So question is about global scale from Homer Simpson, no less, who asks if global scale or how it works with Calabra slash next slide office. This actually works great. There is actually a very huge installation out there with 20 million users using global scale and Calabra slash next slide office exactly like that. So we improved next slide office like last few months that actually works like this remote editing. So it actually fits into the global scale scenario. It can also be fully clustered. You can have like, I don't know, 100 next cloud office servers and they handle different editing sessions in parallel and they can be accessed from different global scale nodes. Yeah, so this works really good. So it's a cluster of next slide clusters with a cluster of next slide office servers all talking to each other. Exactly. I mean global scale is a cluster of clusters already basically and yeah, next slide office can also be clustered and yeah. Sorry. Yeah, exactly. So Homer also asked how do you get one million users simultaneously? Well, that's how you get a million users. They're different. Actually, we have two installations with several million users. One is just mentioned, which is a huge installation with global scale. There is another installation that I cannot say the name yet hopefully soon which also have like millions of users, but this one is actually in one database which also works. Yeah. So yeah. And then Homer continues to ask, you have a lot of redundancy, proxy database, cholera cluster, et cetera, which is I think indeed how that is done. It's actually also one of the cool things about next cloud that the architecture is can be really scaled from very tiny to very big. So as you know, you can download the zip file or the web installer, put it on some web space and run it and then you have your next cloud. Of course, this is like one node with like, I don't know, no opcode caching, no Redis caching, no object storage. You're using SQLite as a database. So it's a very minimal setup, but it's working. It's fine for one, two, three, four, five users. And then from there, you can go bigger. You can, okay, let's use a, I don't know, Postgres or MariaDB as a database instead of SQLite. Or you can say, okay, I want to have like the storage somewhere, it's database, somewhere, maybe you have a cluster of application servers when you go bigger and bigger and bigger. And of course, if you have millions of users, or the setup is a little bit bigger, I mean, you have to really like cluster everything, cluster Redis, cluster the database, cluster everything. But it works and the code, the next load code is still exactly the same. And this works then from one user up to like millions of users. Yeah. And with this release, we did a lot of performance work as well. Yes, that's something that is, I don't know, I think it's best to experience it yourself. Just if you click around the next cloud, especially the file set, but everything is really a lot snappier. This is why we really reduce the load on the database a lot. So you will notice that, but just like using next cloud. And if you're really running next cloud for lots of users, if you're a university or school service provider, you will notice that your database is really a lot more relaxed than before. Yeah, absolutely. We had a graph in the video. You can find a bit more details in the blog, but it's overall, I don't know, the query is very, but it was really between 30 and 70, 80% decrease in load on the database. And this is often, you know, there's one database. This is often a bit of a bottleneck in large installations. And even on our internal next cloud, it was really noticeably snappier after we implemented it with next cloud 24. So, yeah, I think people will really notice this at home. It's a big difference. So, Stefan Linter asks, will there be an in-person next cloud conference this year? I think this question is for you. Yeah, it is. So we are preparing an event and the prize event soon-ish. And if once we have that a little bit going, I want to start looking at the conference and see if we can pull it off. We'd like to do it. So we try to do it. It's still possible that we encounter some roadblocks. We don't know how the COVID situation will be end of the year or late summer or something, but at the moment we are trying to do it here. Yeah. So then Ed Helmar asks, any plans to consolidate the codebase instead of pushing new features? But given all the work we did on performance, would that count as consolidation? I don't know what consolidating the codebase means. I mean, it's like we are constantly working on the full codebase to improve it in every possible way, which has talked about the performance improvements, which really touches like everything, right? I mean, the whole backend file handling database set up, that's really the core of everything. And this was really completely, I don't know, touched and improved in this release. So, I don't know, I think sometimes I hear the criticism that people think that we don't, like just building on top of it and we don't really care about the foundation of it, but that's not really true. I mean, just this release, we just heard that there are so many things that touches the foundation of NextCloud database queries, but other things like that we can outsource the creation of thumbnails to microservices now. For example, the full text search is completely redone, which really works a lot better. I mean, we are improving the foundation of NextCloud all the time. So, I don't really know what other consolidation is meant with it, but that's like an active maintenance and it's getting better every year. Even the share menu was improved now with more granular permissions. I mean, that's a tiny thing in a piece that is as old as the code base. That's like a decade plus old. So, yeah, we're working all over the place, I think. So, Huck Ola asks if there is a development platform for NextCloud. I'm not exactly sure what is meant, but I'm going to guess this is about the apps. I mean, NextCloud is a platform for applications. Yeah, I'm also not sure. I mean, the goal is not only goal. It's already like that. You can build apps on top of NextCloud. If you go to apps.nextcloud.com, we have hundreds of them already. So, it's like working. We have lots of external contributors who are building just extensions, but also full applications on top of NextCloud. NextCloud is a platform. And that's actually an aspect that we want to strengthen in the future to really integrate with more software, to encourage more people to build something on top of it. So, yeah, we're trying to be a platform there, and I think we are already. Absolutely. But I don't know what's exactly meant. Maybe it's also about, like, if there's an IDE or something, like a development environment. Yes, that we don't have. No, we don't have that. And I don't think we should. I mean, actually, also, I like our internal developers. They use all kinds of tools. I mean, I don't know. I know people who use, like, just VI for everything. I also still use VI, but I'm not really a coder anymore. But other people, they use full IDEs, like PHP Storms. I think Visual Code, VS Code is popular. I don't know. There's so many. We can do use whatever you want. We don't have a standard development setup here. Yeah, exactly. And that is important. Yeah. I had a question from Stefan, another Stefan, about the file locking. If it also works with only Office. At the moment, it does not work with only Office. Yeah. That's something that we have to see in the future if we also implement it there. But, yeah, we really wanted to implement it with next-load Office, which is our strategic Office component for the future. It has some benefits over only Office to be totally honest because it's like 100% open source, while only Office has this proprietary enterprise thing with some, there's a community decision, but it has some restrictions. So this does not fully fit into the next-load world. This is why we're working a little bit more with Colabra and implement next-load Office here. And that's why we started with this feature with them. Let's see, maybe it's also coming to own the Office over time. But that was not the focus here. Yeah. So here's an interesting question. Will you implement a feature that allows links between contacts and deck cards that would be a good CRM-like feature? So, okay. In general, I'm just not a big fan of pre-announcing features. We'll talk about that, right? Because, I mean, we have a community of people. We really have a lot of different opinions. And it's like, yes, we're trying to go in certain directions, but I cannot promise like this feature will be done in the next release. So I don't really want to do that. I know that there's actually discussion about exactly that feature. So the chances are not small that it might come because people are actually planning that. But I cannot pre-announce it. We have to see how it goes. The CRM part, I, at the moment, I don't think we will or plan or should implement the full CRM. The option to link different data, different things together, that's something that might come. But don't expect next lot to become a full CRM soon. Yeah, exactly. I mean, CRM is, again, a very specific tool, you know, like an IDE. I mean, NextLoud is really a platform that is for more like a wide range of use cases and people for very specific things. We have a lot of integrations, like web dev integration and all kinds of other integrations. Yeah. Streaming issue. All right. Sorry. There was a short streaming. But I think the point is for very specific things, there are often specialized applications that will integrate in NextLoud, either because there's an app or because they can use our REST APIs or web dev. So I think where NextLoud's strength is, is to have a easy user interface for common tasks. If you start to add super specific things for super specific use cases, like using NextLoud deck as a sales team to track your deals, you can do that. But you will then either need to accept that certain very specific things like, I don't know, getting an overview of the current amount of deals in a certain stage in the pipeline is not available with one button because like that's not how deck is built. If you would make that possible, then you would add something that a lot of people wouldn't need. I think your risk making things very complicated which hinders the normal day-to-day use. So it might make sense, of course, to build an app for that that maybe kind of builds on a feature or adds it. Maybe there's a generic way to do it. But I think we should be careful not to just take a very specific thing and say, oh, we need to be able to do that because it means you heard other things to some degree. And we really, I think, are actually quite good in finding this middle ground between a good user interface for the vast majority of use cases while often still allowing some of these specific things even if it takes a click extra. And then if you really need something very optimized, then you have all the integrations available. So I don't know. Again, I don't want to say we would never do CRM, but it's... I mean, to your point, not a dedicated CRM. Maybe you can use, like, DEC with the contacts and with some whatever text document and I don't know and use that as a CRM, but it... I don't know. It's a bit like using Excel as a CRM, I don't know. So you're trying to build generic tools and not special applications. But as I said, there are like hundreds of people who build like apps on top of it. And I mean, there are people who are building like an invoicing system on top of Next Cloud. So that's already awesome. So maybe someone is building a CRM in the future, but it's not for us as the core team, I think. Yeah. All right. So it's already been more than an hour. I think we should wrap it up. I have one interesting question which allows us to do a little shout out to partners because Rehan Ali asks if Next Cloud can be sold for corporate offices in India. And we have at least one partner in India that I'm aware of, maybe even more than one. And this is, of course, in general, first of all, Next Cloud is available all over the world. And there are a lot of regions where we have local partners where you can go to and, you know, get your Next Cloud services, as well as access to Next Cloud Enterprise, of course. Yeah, exactly. I mean, the software is, as you all know, is open source. Obviously, it can be downloaded from the website. Next Cloud 24 can like directly now download from the website already. But of course, the question was about introducing this into companies in India, I think. And there you need a little bit more than a zip file. And there you need like a local company with customization and training and stuff like that. And we have like different partners, as you said, can go to the website and find someone who can help you with that, if this needs. Yeah, exactly. So once again, go get it. Thanks a lot for joining for this live Q&A and, of course, the announcement. Share the news, tell other people about it and, of course, read our blog post. A lot more details in there. We kept the video quite short this time. So, yeah, and let us know what you think. We really look forward to see what you're going to do with Next Cloud 24 and everything else. Have a good day. Thank you.