 All right, so as in Frank's keynote, you all might probably know Next Cloud Text and I will give like a quick overview, maybe a bit more technical look on it, what we did. As you've seen, it's like, it's collaborative text editing. It has a focus on simplicity, so we try to only like offer formatting that is like really useful to most of the people. We use an open format, we use markdown as the basic file format, but we don't expose it to the user interface, so the editing is basically what you see is what you get, but the resulting file is markdown. We also have support for plain text editing, like you can edit source code files with syntax highlighting also collaboratively and we also support resolving conflict. So if someone still uses the desktop client to edit a file and save it, you will see a nice screen. As you can see, like this is the text app, as we all have seen it in the demo before. This is the conflict resolution. On the left side, we have the file version from the currently open in the web browser user session and on the right side, we have the version that got overwritten by the desktop client in that case. Yeah, we didn't start writing from scratch, but we based the code on two libraries basically. One is TipTap and TipTap uses ProsMirror. ProsMirror is basically a framework for building rich text editors in JavaScript and it comes with nice, yeah, like a nice feature set, all this collaboration features come with ProsMirror, so we don't need to do much implementation on the client side there. And also they are used by several other companies like GitLab is using it, Atlassian, I think. So this is like the whole document internally and it is a tree format. You can always like pass it to Jason. You have a base document and then you can have different nodes under it. In that case, a paragraph where there's a text node inserted and there's this other type that is a mark which can basically apply any styling on the node. So in that case, we have the text inserted, as you can see in the second line from below and it basically gets marked as bold. Collaboration also uses this JSON-based format, so every change is basically transformation of the document that gets synced to the server then. And the nice thing is that the server doesn't need to take care about applying changes and resolving conflicts. That is all done on the client side. Right, and at the moment we do smart polling because as you might know, next cloud is running PHP and there's no real way to have a background task running that opens a web socket, for example. So we do regular polling to the server which is backed by memory cache, so we gain some pretty nice performance. But yeah, you could also, of course, at a later point for high performance setups have a separate web socket process that is running. Yeah, this is like the basic how conflicts are resolved. So the client sends his latest changes to the server and if the client isn't based on the most recent version, the server will just deny accepting those and the client needs to rebase those changes. So just a quick overview, like we started the text set but we still have plenty of features that would be nice to be implemented in the future, like different formatting options, of course, all with markdown as a basis and inserting images could still need some improvements and we also want to bring rich editing to other apps. So if you, for example, have the notes app which also uses markdown, you could also, like in the future, you should be able to also use the text set for editing those files. And of course, mobile editing, similar to like we do it with Colabora, you open the file right from your next dot app and start editing. And as usual, text is fully open source, it's a GitHub. We have plenty of good first issues. So if anyone wants to start contributing, there are like easy issues with predefined steps if you want to start helping us, implementing something or fixing something, feel free to check that out. Yeah, thank you. Yeah, hello, my name is Tobias. I'm the developer of the NextLoud Android Files app and I want to show you the next steps on the Android development over the next year. But first let us step one back a year back and see what we did last year. In the background, you see the active installations count and on the black line, it's just the date of the event. So in September, we released a 3.3 version with a major highlight of trash bin support. Next was the 3.4 with the action on notifications. So you could accept or deny, for example, a log in or you could edit text or spreadsheets directly via collaborative log online. With 3.5.0, we integrated the possibility to take an image and directly upload it to a certain folder and also change the uploading system so that it's on a mobile connection as it was using one megabyte chunks and on the wifi connection, it was using 10 megabyte chunks. On March of this year, we reached the goal of 300,000 active installations and as you can see, we shortened our cycle for 100,000 active installations and we will soon reach 400,000 active installations. 3.6.0 was introduced with a new storage path chooser for local files, so you could directly jump to your picture folder or to your camera folder or movies or music. Also, you could see notes when you shared a file. Another big milestone we reached on June this year, we had 100 unique active contributor on GitHub, so this is very, very, very cool and I'm really excited about it, because this means that it's not only one-minute or a next-door GBH-driven project, but it's really a community-driven project. The last release was 3.7.0 with Chromebook support as Frank already mentioned at the keynote and today, exactly this morning, we released 3.8.0 with the UTF support and the remote vibe for NextLoud 17. So, what are the plans for the next step for the 4.x version? We wanna change the internet network library because right now it's rather old and we wanna change it and use the DAF library by DAF-X5. If needed, we want to exchange that and then implement the missing features upstream, so we will not fork it, but really want to collaborate in an open source meaning. So, also there will then be the new Android library called 2.x and we will maintain our old, currently used library for two years so that enough time is given for people to switch. Also, we wanna change the internal caching system. Currently, it's self-made implementation and we wanna rely on Clyde, which is just a major and a good adopted library. On the opposite, we want to go away from the system of Google account manager because it makes problems with external storage when the app is there installed or also when you have a work profile available. A long-wished feature is also the two-way sync to have a certain folder totally in sync, but this is something we cannot do right now because first we need server-side support for it. Also, we wanna change the new structure system using Kotlin and a new model system to have a better testability. And last but not least, there are long-wished and often mentioned dark theme support. And as mentioned, all this will not be possible without the help of the community and here to name the five most users that helped us last year. Andy, who did most of the UI and UX changes. Chris, who did the Decker implementation and the new logging system. David, who implemented last year the Symmetrical Sign System and enhances this year. RFT did most of the test cases and as you saw, Daniel X did the dark theme system. So, yeah, maybe you wanna join us and maybe then we'll be mentioned next year here. Thank you. Hi, everyone. I'm here to talk about why you know the next cloud, the server cloud for better privacy. So, some words about me. I am Gilmar, I am French. I have a blog where I speak in French. I have a Twitter. I am a member of Formasoft, the Googleized Internet. I'm a free software user since many years. I do self-hosting with why you know host and I pretty say I'm an excellent user, maybe a kind of evangelist. While I'm here, I'm here to talk about why you know host. Why you know host, it's a number rating system braided to desendrize internet. It's the operating system used in the internet cubes. Maybe you have about that. It's a kind of omu2 for self-hosting if I'd like to introduce you why you know host. You need, if you need more information, you can go on the website. Why you know host, some features of our view. It's debian-based. It's simple on the web administration interface. You can add some apps by just clicking on the web interface. There is SSO supports, backup, let's encrypt integration, firewall, file 2.1. All you need to do self-hosting on the, it's cool. You can find some information about why you know this architecture if you need, it's documented. What does it look like? When you know, this is why you know host default login interface. You can customize it. You have just to login. There is no two authentication factor yet. After you are connected, this is a user interface. Each blocks represent an app you can choose. There is a part for administration interface. It's graphics. You have different parts and all the new things you need to do for administration, you can do it basically with a web interface. All the things you do with a web interface are available with command line interface. It's the graphical interface is just an UI for all the command lines. So if you are an administrator system who likes command lines, you can do it. When you know apps are packages, it's a very standard for how you package an app to make it works on why you know host. It's also documented. So next load on why you know host. Install the next load in few clicks. Next load is package as over apps. So in background, it's a shell script where you have all the steps, step by steps to make the next load works on the way you know host. So when I need to learn how to install a web app, I check first if there is a way you know apps and I know how to install these apps because it's well documented. It's a shell script. You can use graphical installation. So you search for next load. You click on install. You have some fields to answer where you want to put it on the subdomain, the main users. And after, you have a new apps. You click on next load works. Interesting, convinced. You can deploy a when you use for yourself. Tell your friends, organize install party, give us some feedbacks on the UX. You can contribute to the codes from the backend, from the front end. You have, you can do some documentation supports in the forums. Thanks for your attention. So hello, my name is Fanid Dimu and I will tell you a beginner story about my Google Summer of Code experience. A few things about me. I am a junior software engineer coming from Greece. I have just graduated from the School of Electrical and Computer Engineering in Athens. I am the creator of Secure Wheelie. Hold on to this, I will explain it in a second and guess what? I have successfully completed Google Summer of Code this summer. So the project I worked on was Next Cloud Pie. Next Cloud Pie is a ready to use solution for Next Cloud where everything is pre-installed and pre-configured. And although it's a great job, there are still some features that are missing. So my job was to spot these features and do my best to fill the gaps. My mentors have been Padelisa Rados and Stathis Yosifidis, both active members of the Greek community of Next Cloud and also of the books, Nacho, who is the main developer of Next Cloud Pie and had been giving me really useful coding tips. Okay, so why did I choose a Next Cloud related project? Because it's cool and I use it for my personal data. And also because I have used it in the past as a benchmark for Secure Wheelie. Secure Wheelie is an open source software that I created which automatically produces a partner profiles for Docker containers. Briefly, I picked a Docker compose file of Next Cloud and I produced a partner profile for the server and one for the database service. Okay, and let's see what I did in Google Summer of Code. First of all, I adapted Next Cloud Pie to continuous integration. I used Travis in order to build images for each architecture, the Docker images, do some tests and push the images to Docker Hub. This automates the whole process and saves time and it also provides transparency of the building phase to users. Next, I created an automation tool which asks for a minimum input and gives a ready to use virtual machine on virtual books. And it also provides an option for easy cloning of an existing NCP VM. This makes a beginner's life easier as it does not require any technical skills at all. Another automation tool which creates a distributed system of NCP Docker containers where the data storage is replicated over all nodes. I used Docker Swarm and cluster FAs. It provides high availability and data persistence, meaning that if your machine crashes, then you still have access to your Next Cloud Pie data via another machine of the system. Another task I worked on was uncivilizing Next Cloud PI server. I had to convert every single bus script of NCP server into uncivilized playbooks. This work is still in progress, though. It sounded like a good idea because many 80 people are using Uncivil and it's also easier to learn than bus for non-programmers and lowers the barrier for future developers. Lastly, I helped Nacho with the update system where I implemented the mechanism for backward updates and I have also written some blog posts about each feature I created which you can find on my blog and some of them are also posted on your bits. Some of the existing features can still be improved and expanded like Uncivil or Travis CI for board images and there are several new ideas that I intend to work on in the future. If you want to learn more about my work, you can see my contact details. That's all, thank you. A very non-technical presentation will fall in now. I work at the German Federal Youth Council and actually, next cloud is just a part of our work supporting organizations in their digital transformation. I just wanted to present you a bit to understand what use cases are for non-profit organizations. Traditional file sharing and group work, that's very obvious. Then we have one bigger project. It's actually 60 organizations, six zero organizations. They are monitoring political and physical attacks against NGOs, especially with the raise of the right-wing party, IFD, that has increased dramatically. And so we have an anonymous letter inbox in Next Cloud. We have tagging and support mechanisms there. Then another very typical thing is they are using Next Cloud plus Collabra for time logging because the administration forces us to use Excel sheets. So that's the easiest way to use Collabra. Youth organizations or other youth welfare organizations don't start with zero. They usually have a lot of tools running. That's the usual, like the things they use. And each of these are replaced by Next Cloud now, which is quite impressive, I think. There's two symbols you can see without a name. That's the surveys because we are not fully convinced yet about forms, but I know that it will be improved. So the pre-Next Cloud problems in organizations were that obviously in so many different tools, each activist has to find his or her own set of tools. And the overview just gets lost, who has access to what, if people leave, so where is the data. Then organizations like mine have offices, of course, like employed people, but also non-employed people, volunteers, and if there's a monoculture of whatever, Microsoft Office or whatever, it's very easy for them, but it's very difficult for volunteers. License fees, we actually had a problem that one of our member organizations lost all of their contacts, like address books because they didn't pay the license fees because sometimes they just forgot. So their whole, my contact is gone. That will not happen with Next Cloud. And also the separation of private and professional life. I leave the office and then just switch off whatever the chat. But with Next Cloud, we came across several of new challenges. First of all, people are totally confused like what is a group? There's user groups, there's the circles, there's the contact groups in the address book, and there's, because we use the XMPP extension, there's also XMPP groups and people really, really have trouble to understand that. Then the next thing is sharing, the logic of sharing and like inheriting the rights of documents. And also they are totally confused if they are allowed to move a folder or if it changes with your colleagues and like this is really something that leads a lot of explanation at the moment. Then we realized people, like many organizations are really moving the whole infrastructure to Next Cloud, but if you had a file server of two terabytes and people start just using their sync client, suddenly the notebook is just full and they realize maybe we shouldn't have synced everything. And then the simultaneous use of apps is not consistent at the moment. For example, text is really cool because people can work together on like other apps, for example, I think Decker and so on. You can just work each person after like another, what's English word, like separately. And that's also confusing to people. For Collabra, we realized, I mean people love it, but to understand which fonts are available because the server has fonts, but you have fonts on your computer and included fonts, it's really difficult for people. Also, because it's not consistent, in Collabra you can just close the document and it's not saved and it's just gone. And people don't expect that because text, for example, saves automatically. And end-to-end encryption is a big challenge for people to understand. I think this is the most important slide here. Something that you should know. If, especially youth organizations and many nonprofit organizations get a lot of public funding, and that makes it difficult to contribute to open source software, which is really strange because funding cannot be donated. So for example, we can switch to a Libre Office, but we cannot donate to the project. So we have to pay something. We have to get an invoice for something, then we can do it. And then the other thing is the 50 user support gap, it seems as if there is nobody who has like offers support for below 50 users. And because many organizations have like 20 people in the secretariat and some volunteers, they're always under 50 regular users. And Microsoft makes it much easier to just pay and then think they have a support. Thanks for listening. Hi, everyone. My name is Marie. You probably know me from when I used to work at Nextloud. Now I'm an event manager and program manager at Prototype Fund, which we're gonna present to you today. Yeah, my name is Thomas. I'm also program manager from Prototype Fund. It's also part of an NGO. So this is another non-tech part of these lighting talks. So the Prototype Fund is a project part of the Open Knowledge Foundation in Germany. And we want to support development of software ideas. And we have four focal points. We want to support, which is civic tech, data literacy, security, and software infrastructure. In short, with Prototype Fund, we want a fund common, good oriented software development, or we want to promote open source projects that add value to the whole society. The Prototype Fund itself is funded by the Federal Ministry of Education and Research. And with the Prototype Fund, we want to deny another way to distribute money rather than giving large amounts of money to large organizations. We want to give small amounts to individuals and small groups. We evaluate what we are doing and want to share our results and our experiences that we find many imitators and multipliers. So in numbers, we are now waiting for applications until September for our round seven. And up so far, you see the numbers, how many projects we funded and everything else. Funding period lasts six months and you get 4,700, 500 euros. So the focal points we want to support is civic tech. With civic tech, we want to provide digital tools for every citizen. In security, we want to support privacy, secure communication and data economy. With data literacy or data competence, we want to make everyone being able to use and analyze open data sets. And with software infrastructure, we want to empower groups and individuals to operate their own applications and networks. So, we're here because we think Next Cloud is really interesting. Next Cloud projects are really interesting for us to fund. And we actually already have funded one. It's called undo from ransomware. It was presented in the lightning talks at the conference last year. It's basically a tool to get back in time if your computer gets infected with ransomware based on Next Cloud. Our round this time is called engineering trust for Trauenbaum. And the applications are open until September 30th. And basically, with engineering trust, we mean everything related to trust. Think about trust in information with, for example, journalism or social media. Trust in communication with secure messengers and other encrypted apps. Things, our trust in government and businesses with all tools for transparency and accountability. Think about trust between people, between people and their devices, between citizens and institutions. And literally any trust link that you can think of that can be helped with tech we're interested in. It doesn't mean that you can't apply with anything else. Like we're open to anything also not related to trust. This focus just means that we're like particularly happy to have projects about trust, but literally any open source projects is welcome. If your project is open source, it's innovative and it fits in one of the categories that Thomas listed before, then you should apply if you need the money. If you're considering applying tips, just use very clear language. Make sure that you make clear why we need it, what is it about and how you're gonna do it and communicate over about how innovative your project is because the jury will look at that. On that note, we're looking forward to your applications and we're here a bit for the rest of the day, at least a few hours and then tomorrow again to answer your questions or shoot us an email. Thank you. So hello again. Now I'm going to talk about why the open source center by Atos is developing a business model around next load. So who I am. You have already seen me as Genma. It's not my twin, it's already me. And now I'm as Jerome working for Atos and as a project manager architect on open source specialist. So Atos, it's the corporate part. It's why I am here during my work time. So it's a French multinational international technology services and consulting company. Our headquarters is in Bozon in France and we are specialized in different services, cloud, data, security and services and Atos operates worldwide under different marks. Atos, Atos Intel, you can check the Wikipedia pages if you need it. What is the ROAC? Atos open source center is where I work. It's a center of expertise and support for open source software. Reddit and community, we are Reddit partner but there is, I am actually developing a part for community open source software. We are offering different offer and services, consulting, advice and expertise, supports, we do supports from big company for ministry in France. The kind of supports you can expect, bug correction, outline with a desk. You can ask us to correct some software and after we release the patch to the community. What else? We have DevOps factory, we are working to build open source software from the source faster to provide our customer some new software patch and after before we released the patch and it's integrated in the main branch in the source code of the website of the software. And we are working on digital transformation with micro services, architecture, yes, pass, gas, cloud, private, public. So I ask myself, why Atos on this cloud? Okay, so why the open source center by Atos is developing a business model around next cloud? As I said before, no, no, I'm an open source specialist and above all, an excluder. I'm very proud to use next cloud. I really believe and I know it's true that next cloud is a response to Vigafan. It's why you're a member of Formasoft or against Chinese cloud. And I think I'm not the only one. You are here, so you are already convinced. Next load, popularity increased. In the end of August, there was a big announced. The French Ministry of Interior is now preparing a rollout of a prediction ready next load to the users designed to scale to the 300,000 people of the ministry. So why Atos? As I say, Atos is a very big and large company. We have many thousands of collaborators from all expertise. We are able to respond to all the customer needs in the corporate parts, but it's true. And what we plan to do with the next load? Just to do what we do with open source software. We are convinced to you, we are convinced or customer to use next loads as an alternative for their cloud needs. We are Google Cloud's partner, Microsoft partners, and I want to develop a third way with next load on the other free software. Instal, what we can do? We can install them next load on their own infrastructure or on our infrastructure. Because we are cloud provider, we can provide them supports. So let's create the next load offer for our customer. Benefits for next loads on next loads community. Most customers on user, on school, bug reports. It's really important for me to do some big reports and to sensibilize the overall customers to do some bug reports, contributions. Maybe we can ask our customer to pay for new apps that we will release on their free software license for the next load community. Exist, doing some improvements on the existing apps. So next, we need to find customers to have money. We need to finish to constrict the offer to communicate about it. It's the first official communication we do about it. We are searching for some partnership with next load, we've got a bar with only office. So during the coffee break, we are going to talk with you. We are playing to do a meetup in Paris. My plan is to organize a meetup to talk about next load, maybe to do a bug correction party with you. Thanks for your attention. I'm Ulf, I already talked this morning about the integration. Now some more details. I will, okay, I have about 10 charts. The first six or seven are a little bit more about our product. So we understand some foundation about the product and it's important to understand how next cloud fits into it and then the value for our customer base. I talked this morning about the acceptance criteria that are typical supercomputers that are our heritage. The largest system that we deployed is 250 petabytes. There are about 25 racks with storage and then there are a couple of hundreds or thousand outs. There the file system is mounted. You can think about Spectrum Scale as the file system that is overspending all these nodes. There's an agent running on each node and we provide very fast access. Similar to NFS, like a distributed file system, but super fast. That we had this morning. So Scaliable Performance is one piece, but when you are on the storage at that scale, then you also need automated data management. We have, for instance, placement and movement policies. If you think about next cloud, you have maybe smaller documents like a Word or a PDF, you can have large movies. And with the placement policies, you can integrate flash and spinning disk, for instance, in one file system and based on the ending, the movies would go to spinning disk and the other one to the faster, more expensive storage. You don't see it from the user perspective. It's always the same pass and we do it on our knees. And if our time gets older, we can also automatically move data from SSD or flash to the spinning disk under the knees. So your users and even on the next cloud level, you don't see it. Yeah, so data management is important for that, yeah. And we also developed one new feature that is the notification. And that is where we have the integration with this next, yeah, this next cloud. So here that is, we provide one file system in different access methods. Users can access via POSIX and the agent, but also via NFS, SMB, or via OBJECT, or if you have a next cloud running on it, the same data can also access via next cloud. Yeah, so there's no data copying, nothing. This in one file system, then you have the different access methods. That is the environment, yeah, so we have storage nodes providing the storage, the compute nodes where the analyze of the data is running, access nodes, and then next cloud would be installed as an utility node or an utility node for additional service. Yeah, in next cloud, yeah, we integrated a spectrum scale as external storage, yeah, so a local file system. And in the past then, there you'll run, yeah, defaults every 15 minutes, there you'll scan for updates, and for file systems at that scale, the traversal of the file system just takes too long. Yeah, so that was the past, and now the integration is about, we have a new feature that was introduced in our latest release that is called Clustered Watch, and with Clustered Watch, we have an agent on all nodes, the changes are sent to Kafka, yeah, that Kafka is internal in spectrum scale, and from there, we push out the messages to an external Kafka, yeah, that you would need to provide to get it out. That is the tooling that we have in spectrum scale. In next cloud, on the other hand, yeah, there you have Redis for memcaching, and we have a small example script to convert the Kafka messages into entries in Redis, yeah, and from there is a plug-in in Vailable that reads the Redis advance, and then updates the next cloud, the file system view, yeah, and in that way you can have at large scale on large deployments, changes in the file system outside next cloud, and get real-time updates, yeah, in the file system view, and then you think about the workflow that you heard this morning, yeah, we can, on our side, ingest the data from some instruments to the analyzes, yeah, then put the result in next cloud, and then you get an email with a link into next cloud to your work group, you hear the results, or the rendered image is available at that link. Yeah, I have a GitHub project ongoing with Ansible scripts and so on to document it and to end, that's still private because my colleague has it running, but it's not working on my system, so I have it running that the events appear in Redis, I see that the next cloud agent is pulling out and removing the essence, but I don't see the updates in the view, so once I have this fixed, then this project will get public and you can see how this is running and integrated and to end. Hello everybody, this is Aisa, so I am going to present Daikonweaver. Is it enough? Okay, today I'm going to present Daikonweaver, which allows medical imaging in next cloud. Okay, what is Daikon? Have you ever heard about it? No, did you? Great, maybe you haven't, but you already met that guy before if you got a hospital to get a part of your body scant. For example, you injured your arm and you went to a hospital and your doctor asked for MR scan of your arm and you are going to the scan room and the scanner takes your MR images of your arm. After you leave the scan room, you go to doctor's room and you are very excited to see your MR results. So the question is how are your Daikon images stored and transferred to doctor's office and how can your doctor show the MR images your arm in his office? Here is the magic of Daikon. Your old MR images are stored in Daikon format and your doctor is able to view your MR results thanks to Daikonweaver. Here's a little background. I have been working on medical imaging software for a long time. Also, I was storing my old Daikon images in next cloud and had to find a simple way to store and weave them and demonstrate them. Of course, there are many native desktop applications but installation steps are really painful. Also, they are based on the platform, usually Windows and we are restricted to a single machine and it's impossible to weave and collaborate them. Also, there are many zero footprint Daikonweavers in the market. I'm also the core team member of the OpenHealth Imaging Foundation which develops a zero footprint Daikonweaver. But just like other Daikonweavers or if it requires a PEC server to weave images and infrastructure to store them securely. And all Daikonweavers should be HIPAA compliance and next cloud takes care of it for us and thank you guys. Also, we are working on, also you may want to import your existing Daikon images from your PEC server to next cloud for better migration and you may want to synchronize your Daikon images with next cloud for better migration. We are working on a solution which provides this with the third-party integration. Daikonweaver uses sharing and collaboration features provided by the next cloud and who can use it? Hospitals, clinics, radiology centers, researchers, patients and developers. If you want to check the features of the next cloud, Daikonweaver, you can see the screenshot of a Daikonweaver. You can see the toolbar on the top and serious panel on the left and the main report shows the Daikon image. You can see the all details of a Daikon file and you can single and group weaving options. Next, we plan to implement several features for Daikonweaver and thanks to all the supporters of the Daikonweaver and after that we are open to collaboration and any help. And the last thing I have to say on your help data and keep it your safe. Now let's see if this works. Very interesting as always. Oh, first of all, let me say thank you to everybody here because I might forget that. I and the journalism community really owes you guys and girls a big thank you for all the work that you have put in into things like next cloud. My name is Fredrik Loren. I'm an investigative reporter since 25 years working for Swedish Public Service Television and I often work together with other colleagues all over the world because the world is global and so is must journalism be. One of the, oh, now we have not the correct one. Okay, I'm really sorry for that. It was not the correct slide. Interesting, how, okay, I have to fake it until you make it, at least it's a blank page. You have heard about Panama Papers. That was a source who came to a very reputable newspaper in Germany, Suddeutsche Zeitung. And they gave us terabytes and Suddeutsche came to us which are the ICIJ, the International Consortium of Investigative Journalists. We are a bunch of 3, 400 people all over the world who have realized that cooperation is needy if you are going to challenge big corporations and the tax evasion and things like that. With the data from Suddeutsche, we were 400 people who all across the globe could investigate the Chinese leading the party apparatus up there showing that they really, they are using offshore to store their wealth. We could show how the most famous was the Icelandic prime minister who had to resign because he had hidden stuff in offshore, et cetera. Puttins, hidden millions or billions were found, et cetera. All through collaboration and by very, very different journalists. People from Russia who are under great pressure. People from Sweden where there's a strong constitution and not really big threats to journalists. People in Africa who are under physical threat every day and economic threat, et cetera. We managed because we had a joint collaboration platform that we built ourselves, ICIJ. But that's where we shared the documents and that's where we could pull and search in all of the Panama Papers and get them home to our computers and do our own local reporting. My challenge and why I'm thanking you guys is because I know that there are not only 400 journalists out there, there are thousands out there who have a local situation that is often terrible. It can be terrible in the sense like Swedish public service television who has a contract with Microsoft. We do Office 365. That means that every investigation that Sweden does can, that we do in Sweden, can and up in an American court. It hasn't happened yet, but we will be there sooner or later. We can also end up in a court in Britain where some oligarch decides that he doesn't like what we report on him and then we can get sued and we will have to present it in court or face billions in fines. So there are some real big challenges and also there's a lot of simple challenges like losing your hard drive, et cetera, and having bad infrastructure. So we have implemented since 15 years things like our own server and we built it on own cloud and then patch work, et cetera. And since then, as in this last year, I have migrated to NextCloud and it's really fantastic and you know why I don't need to explain to you, but I think you're getting an idea of why this is important to journalists. This server is now running and is providing me with a fantastic tool and I'm fairly advanced and it's really working well in most parts. And it's also providing already Russian colleagues with a platform to work on and that's a very difficult environment and it's also providing an NGO already in Asia, I should say, who is under great duress. Basically that's what the investigative cloud is. It's just NextCloud used for journalists and implementing as many as the security features that you can come up with and the ease of use and well, let me show you why this is important. This is a secret American court that never published its decisions until very recently. It's a decision that there will be an investigation and a search for Julian Assange's document at Google. This is this decision and that's one thing. He's a sexual offender or he's a suspected sexual offender. You can say many things about that. But here, you're also find Brigitte Junstottir who is elected parliamentarian in European country, Iceland. And what this secret court in America ordered Google to hand out was not only all the documents or emails in Brigitte Junstottir's account, it was also all the IP addresses that has ever accessed the account. And you know better than I know where those IP addresses are stored and who is now inside of European parliamentarians iPad. You name it. This is why this is so important. And again, thank you. Hi, my name is Galina. I'm from one office and today I hope to give you some ideas of how to make your work and documents within NextCloud even more secure and effective. So let me briefly introduce what we are doing, what we are working on and give you some background. So I think about 15 years ago, we were fond of converters for all the file types like audio, video, images, et cetera, and later also documents. And our mission was to make the documents look the same and keep the formatting after conversion. On the other hand, we also had our own collaborative platform for sharing documents and we wanted to teach this platform to edit documents online and even better to collaborate on documents online. Just to avoid this downloading, uploading, to make some changes offline, et cetera. And the most important thing here is to secure this process. So since 2010, we are working on our online document editors which are as powerful as desktop ones but providing the advantages of the online working so that means that you can access them from anywhere, from any device, you can share files, you can co-edit the files, et cetera. Our core technology is HTML5 Canvas and our internal format is DocX. So we keep the same core for web version, desktop version and mobile and this is how we support all the versions we do have on our GitHub. Right now, OnlyOffice has more than 5 million users worldwide. So let's have a look on the software itself. It has stepped interface with feature reach tool set to edit your documents. You can set up fonts, styles, paragraph, et cetera, add some shapes, charts, use content controls and you can even extend the functionality of our editors by adding the plugins. As for co-editing, OnlyOffice offers flexible access rights. You can use two co-editing modes. You can review, track the changes at commands, use the built-in chat, et cetera. And what's important that every user can choose his own settings without being dependent on all the other users who are working on the same document. So data security, it's the most crucial question, I think for all who are working with documents online. So OnlyOffice is an open source solution. You can install it on your servers without any access from any third party companies. We are using JSON web-talking between our editors and storage of the files. Limited cache lifetime, you can hide download copying. We have also released the watermark option. You can set it up and see who has created the files and who has opened it last. We have released the end-to-end encryption reinforced by blockchain technology, which is used to store and transfer the passwords for encrypted files. And what's important, not only the files, but also the traffic, all the changes, all the temporal files, they are also encrypted. So since we met last time, we had two huge releases. We have new interface, new customization options, mobile apps for integration, desktop integration with NextCloud, auto conversion, not only of the formats, we work not only with the DocX, but also with all the other formats with ODF, we auto convert them and edit them directly. We have a lot of features which we plan to implement for NextCloud connector, like force safe for advanced sharing permissions. And this is the idea, actually, how to make the NextCloud work even more secure with your documents. You can just install on the office by any options, option you can find on our GitHub, like Snap, which we have just released, or DocX script, Univansion, or any other option. If you would like, you can also test this software without installing by our TestCloud. We have, again, just released it. You can easily connect to your NextCloud with the latest version of NextCloud connector to our public test cloud, just to see how Office works within your NextCloud. So I think that's all, thank you. So thanks, everyone. That's the end of the talks for today.