 All right, so my name is Patrick. I am the developer of JTX port, the one and only Android app that implements the virtual standard on Android and also, like, in general, actually, except for some other two Linux applications, in fact. But in this talk, I don't want to talk so much about the Android app itself. I would like to talk about the context what brought us to the fact that we wanted to implement this app. So I was saying the virtual standard. So in order to give you some context, what is the virtual standard, actually? We need to go one step back to the iCalendar standard. Before we already heard about the vEvent component in the iCalendar standard, so let's go to this question. What is iCalendar? So the definition here says the iCalendar is a media type which allows you to store and exchange calendaring and scheduling information, such as events, to-dos, journal entries, free busy information. So it's not only about calendaring. It's also the whole context of calendaring. There's also the to-do component, the vToDo component, and the vJournal component, the vEvent component you might know from normal calendar entries. When you export any calendar entry from your calendar, you end up getting an ICS file. The ICS file contains the iCalendar format that has an iCalendar core object that wraps the vEvent component. There inside, we have the textual interpretation of the event itself. The same for vToDo. A to-do is just like a task. We have this task component inside the iCalendar core object. And this is our textual interpretation of the task. The vEvent is widely used. So it's like the de facto standard on the internet to exchange calendar entries. The vToDo not so much anymore, but still it is used. And the vJournal is almost not used at all. So what is the vJournal, actually? So the vJournal attaches descriptive text to a particular calendar date. So basically, we have an event that does have a start date, or it has a date, but no end date. So it doesn't cover up any space in the calendar. So we can have a start date. We could also have just not a start date, which would just make this entry a node. So basically, it defines a format, like an interoperable format, to exchange journal entries like a diary or meeting minutes over the internet, and also a format to exchange nodes with other apps. Also, the standard was defined many, many years ago. There's only KOrganizer and Devolution Client on Linux that actually supports this component inside the standard. So why did we actually want to implement this JT export? Because exactly of this reason, the standard was defined many years ago. There were almost no applications that supported this standard. And we just wanted to be the first. We wanted to give this food for thought to actually do, as we did, make another app, make more diverse, interoperable apps that can support nodes and journals. But so we decided not only to do the Vgenl component, we also said, let's also support the V2Do component inside. So we don't only have the nodes and journals, but also the tasks inside. Because the standard actually allows the linking of those entries. So we can say we have a journal entry, like our meeting minutes. We write our text. But then usually after a meeting, we also have some tasks to do. And we link directly our tasks to our V2Do's actually, to our Vgenl. That's all included in the standard. So basically, if other apps would just support what the standard defines, you could have a very, very powerful tool where you can link one component to each other and have a complete picture of what is going on. So we already heard before about DAFX5. So the question is, now we implement this locally. JT Export would just work as a standalone app as well. You can export entries in an ICS format. But you also won't like to synchronize your entries over the internet. So that's why we said DAFX5 is the logical step to say, let's continue. Let's enable the app to also synchronize V journals. And as any way, a lot of cloud of servers, including Next Cloud, already support this component, it was just a logical step to also enable this in DAFX5. And as we already heard before, it's DAFX5 gives you this free choice of your server infrastructure. Theoretically, also, you could use another app for tasks. But JT Export is the only app that supports the Vjourner standard at the moment. Yeah, so the development is ongoing. We are continuing to develop new features. We do a refactoring in Jetpack Compost, a new UI framework from Android, a widget will come. The calendar integration will be an interesting topic when we say we have journals, nodes, and tasks, and maybe a fourth step in the app for calendar entries. So you can not only link journals and tasks, but also link your tasks to a specific calendar entry. Yeah. And one thing that I would like to point out as JT Export is the only app that currently supports this component on Android. Maybe one of you is interested to make something similar for Next Cloud. So basically, Next Cloud does not offer a front end for editing Vjourners at the moment. So if you feel like starting a project, I think it could be really interesting and enriching project for the whole community. Yeah. To close this talk, here's some links where you can find out more. Try it out. I hope I could inspire you to also get a bit deeper into this topic. If you have any questions, we'll be around. Grab a sticker, grab a flyer. Let's have a conversation. Or if you really would like to start a project to implement something for Next Cloud, it would be a great idea. Thank you. Thank you, Patrick. Thank you for this high-speed talk of yours.