 Hi, I'm Marcus. I've become more involved in the Afterword project for one and a half years now, and since become one of the main contributors. And I want to tell you what happened in the last year, basically. So Afterword is an app store for Android or rather software repository for free and open source apps for Android. It's modeled after Debian. So what's new? There's a new client release about a year ago. It was a brand new UI, which was all fancy and tile-based and pretty images for categories. It also has a lot of new features. You can now have localized app descriptions, for example, or localized icons and screenshots and feature graphics, and so on and so forth. Also, a long requested feature of us that if you want to know what changed, if you get an update for an app, you can now see that inline in the app details page. You don't have to click on Change Log and open a browser, and so on and so forth. There's also been a brand new website we launched, which is also a lot prettier and a lot easier to maintain for us. And we're pretty excited about now we're slowly able to distribute reproducible builds of apps, which means after it builds an app and compares it to the upstream developers build of the same app. And if everyone involved did everything right, we got the same binary, and we can actually publish the upstream APK with upstream signature, which means upgrading between Play Store or GitHub releases and after it releases will become a lot easier, because you don't have to reinstall the app and lose all your user data. And that also means we got FE, which is a pretty popular transportation app, now open source and distributed in after it as a first reproducibly built app almost the first. We also, for a few months, have been doing now weekly status updates on our blog, which is called This Week in After It, which is mainly done by a contributor called Koffee. And you can get to after it or again read all about what happened in the last months in after it. So what's next? We have a long way to go for making contribution to after it easier. Getting started and maintaining build recipes for apps is not as easy as we'd like it. So there's some server improvements we need to do, and also we want to finally set up CI for app building, which is not that easy, because there are a lot of tool change versions after it provides. Yeah, we want to push more for reproducible builds. And also one of the main problems with after it is reducing the bus factor, making us less dependent on one person which maintains the build server. Some statistics, since about a year ago, there's been about 270 new apps published after it. We published 150 index updates, which is we're aiming for once a day, but this was broken for quite a while last year. We actually built over 4,000 APKs, which means updates or new apps. And yeah, corresponding to that, there's been a lot of commits. We actually got a few new contributors, which helps a lot in keeping up with the issues. And there are currently about almost 2,500 apps in the main after it repository. But yeah, there's also, like in the whole project, almost 1,000 open issues, 140 open metrics, and curiously also the same amount of apps that we know need updating there probably lots more. So how can you help? You could adopt an app and maintain it inside after it. It's not that hard. You don't actually need Android development experience. You can also add screenshots, descriptions, those what's new text to upstream app repositories. It helps a lot in polishing the experience the user gets. If you want to help with the clients, after a client development, we'd be really glad because we're lacking lots of resources and also the website. So come talk to us on IRC or wire matrix or on Mastodon, on GitLab, on the forum, wherever. Thank you.