 The rating system, which is a Debian-based derivative, bringing open-source technology for sailors, and we also built a lot of software for that. To do that, we started building a framework called Isomere, which delivers basic stuff for that. We'll come to that later. So the history is pretty old already, like 10 years almost. We were founded shortly before the camp back then, and since then we've been organizing hackatons. There was one big one for the Euro Python, for example, or some maneuvers in the Baltic Sea where we tested our prototypes and developed maritime concept and technology. Open-source is always a must. I've already mentioned it, and it's kind of like what sailors do. Sailors love open data. They all have lots of reference manuals and data on atmospheric conditions, for example, and it's open-source because otherwise it would be difficult. There's some problems with proprietary stuff in this market because, for example, sea charts are often commercially only available, and we're trying to change that by developing something to actually make the open-sea map better. That's one of our purposes. It's one of the most driving things, so we try to optimize things here. Then there's the isomeric community, which is a small GitHub organization which is aimed or was founded to promote the development of the application framework which we're using, which I'll detail later. So I hope if you join the organization and maybe see my other lectures which are revolving around isomer again. So what are those things, actually? I'd like to start with a Hecker-Frieder operating system because it demonstrates what isomer actually is capable of, and for that, I've made a few slides to describe half us. Yeah, it's a German pronunciation unless somebody comes up with a better name. We had lots of acronyms. This one just stuck too long. Okay, to give you an overview, as I already mentioned, the Debian-based operating system with pre-installed modules and isomer system, which offers a user interface and it's optimized for low cost, low budget, low power, what sailors need. It's kind of ruggedized. We often build Raspberry Pi units that you can easily mount in your ship. It's comparable to something like OpenCPN or SignalK or various other programs and you can combine them, actually. So core functionality is sea charts and navigational aspects, but we also do data logging and analysis, crew information, management systems, and we'd like to integrate external data sources. As I already mentioned, it's all about open data after all. It also includes a few utilities for ships like an anchor manager, anchor watch, or crew registration systems, information systems. You can document your travels or organize your imagery, your pictures you took while sailing, and lots more. Let's have some screenshots to see what actually is in there right now. This is the boot menu. There we have some basic functionality. It's just open street map with a small dashboard. But here you can see a little more complex example. This is a prototype screenshot of the AIS system, which we integrated, where you can see other vessels around you and see your own position on a satellite hybrid map because this is actually not only satellite, it's also open street map overlaid with it. Here we have a real dashboard application where you can actually see the course that was sailed and some performance parameters up here. Here's another screenshot, which demos off the dashboard and AIS functionality. As you can see, there's these red lines, and those are five-minute markers of those vessels where they will be, if they continue sailing for five minutes. As you can see, some of them would crash into land, so they're probably going to change the course. You can observe all this in the AIS view. We also came up with the idea of combining Freifunk with maritime technologies, like every sailor should have a Freifunk installation on his boat, so you can share your Wi-Fi with other people. For that purpose, we built a radio range display, which shows you where other sailors with network access might be in your region, so you might actually grab some internet coverage where your own antenna won't really be able to help you, but you can use other people's mesh network nodes. We also integrated some small tools for classical sailing materials, like raster charts. Vector charts are really problematic right now because they are encrypted and it's a very proprietary format, but we're trying to change that as well in the long run, especially by integrating open data sources like Open CMAP and other available data. So for that purpose, you can combine layers and have very sophisticated setups for various data sources that are available online. You can also take these data layers with you by downloading them, at least with some it's possible, and you can always cache tile imagery data, but it's not perfect, so another reason why we want vector data. These are some weather maps. I don't know if they are still existing. These screenshots are a little bit older, but you can see that there's lots of interesting stuff to do. We also have some rather uncommon visualization. I'm not even sure what this was meant to visualize, but I thought it was a nice screenshot, so I added it. We also have responsive in our mind. So classically you have one board computer on your ship, and maybe it's in your navigation corner. There's a screen, keyboard, mouse, and you run some Windows software on that mostly, and we thought, let's bring your own device concept to Sailors. Why can't I use my smartphone or my tablet? I mean, almost every Sailor's got some of these sketches on his ship these days. Why not use them for navigational purposes, for communication with crew? Maybe they are in the harbor or somewhere. It brings a lot of interesting aspects, combining these new tools we have with a rather old trade, such as sailing. There's more like we have a switchboard, which you can use to turn off and on your 12-volt supplies. Also, Night View, this is an early prototype. You can still see some white elements, which are not supposed to be there. And that brings me to the end of the screenshots, and I hope I'll be able to present some more new ones next year, because right now I am in the background working on a new front end, which has been overhauled, because what you've seen here is mostly a very old version of Angular, and right now we are modernizing this to be compatible with most modern systems by upgrading to Ionic. But these were the Hackerfleet operating system screenshots. Let's head over to the ISO application framework, which you've been kind of seeing already. It's the common functionality that was developed in a modular way to enable operations like sailing, and the data aggregation we do, and the user information services. And at some time in development we noticed that the framework itself is pretty versatile and has mustered up to a lot of other tasks. So I started splitting out the Hackerfleet operating system call functionality from the framework functionality, and that way, Isomer was born. There's a few very interesting features or technologies in the framework, which you can see in other frameworks as well. But I think the combination of them makes it pretty somewhat pretty unique. We are focusing on rapid development. Like, I don't want to be harassed by a platform specific, for example. That's the reason why we use Ionic for the front end, because you build it once and it works everywhere. There's a heavy focus on collaboration with synchronization. I'm investigating three clocks and interval clocks and other stuff to get data synchronized between clients so you can collaboratively edit any data object. There's no cloud necessary, because while sailing, you usually don't have access to cloud infrastructure. There's only the wind. Data clouds are far away from your ship usually. So this has to run offline, off the grid. Also, obviously, geodata is very, very important for sailors. So these are first-class citizens, and along the way, I came up with a proposal to not only treat geodata as first-class citizen, but any data. So it's driven by Shimata, and it's constantly validating data, and allows to, for example, take diffs and patches from data structures, which you then can seamlessly integrate with synchronization methods. There's also a lot of general functionality for your general website or application that you necessarily need somehow sooner or later, like an enrollment system or a gamification module or notifications for users, these kind of things. And I constantly see them being developed new and a new, and they're being rolled all the time, because people build those on a daily basis for their own projects. And the idea was to take all this functionality that's being redeveloped unnecessarily and combine it into a functional and working framework, which is open source, and I think we're on a good way. So what's it built with? It came to my mind that Python 3 is pretty nifty, and in general, the scientific community has taken up Python quite well. I don't think I need to explain its popularity much more for the front end. We decided to use HTML5, because as I already mentioned, it just works everywhere. The general communication between front end and back end has been overhauled, because REST is kind of like, it feels like an ATEEZ technology. It hasn't seen much overhaul. It's probably solid. But if you are aiming for low energy, very efficient radio communications, alone thinking about the overhead that REST imposes on your data communication is kind of like, no, I don't want that. So we decided to move on to WebSocket. And in the last few years, you may know things like Swagger or other API definition protocols. And recently, there's been this new maneuver, which is called Async API, which is meant to describe asynchronous APIs like you can do over WebSocket. And I've started integrating this into isomer, so you get nice data sheets about your API and auto-generated documentation. And yeah, for objects persistence and management, because that's one of the core aspects of every back end, back then I chose MongoDB, because it allows to store objects, not only tables. Some of the data objects we are handling in the marry team setting are quite complex. And doing this with SQL would be a major pain in the ass. So we decided to pick MongoDB not for its sharding functionality or all the stuff people are always complaining about, because when you're running it on one Raspberry Pi, you don't need sharding functionality, strictly speaking. So it was a good choice back then. I'm starting to regret it a little bit, but because of you may have noticed the license changes they opposed on their community, which are not so nice for open source projects. So I've started investigating into exchanging the MongoDatabase handler with the Postgres system, because you can do the same things in Postgres these days and there's no loss at geographic information functionality or anything. And also you can use JSON Schema very nicely with Postgres these days. JSON Schema is the core pillar of our data structures. Every data structure needs to be specified as JSON Schema. This helps us validate for one thing, which is the core functionality of JSON Schema, but there's also very nice front end libraries for rendering very sophisticated forms automatically without the developer even needing to touch any design specifics. I know this is often not perfect, but if you think about Django's admins views, for example, it's a great tool. I also use the click library, which is a very, very sophisticated and extremely powerful command line tool interface. So we have a Rappel interpreter and automatic command expansion in that shell, et cetera, et cetera. I hope that made you interested in the Isomer project and also in the Hackerfleet project. If you want to try it out, I'm always here to help you. You can find me on the contact channels I will be posting afterwards. I'd be happy if you reported any installation bugs or anything you stumbled upon or have any constructive critic. I would be happy to receive it. Maybe you can find something in here and realize your own projects with the framework. I'd be happy to welcome you in the community. So then there is this other topic, what is Hackerfleet doing on other fronts? And we've been busy, although we couldn't sail this year, not a lot at least, most of us, but we've come up with other things that might be interesting for the community as a whole. So let's dive into that. Some weeks ago, I came up with the idea of a virtual sailors club. It's kind of like a normal analog sailors club, but it's virtual. Yeah, maybe there's interest there and we actually have something similar. We started, when did we start? I think it was three or four years ago, maybe five. We started the Maritime Hackers Meetup, which is a small round table of interested community members gathering at CCC events. We'll also host one at this virtual RC3. It will happen tomorrow afternoon evening. I'm announcing it hopefully on some more channels by then. There's a GitHub issue on this task and our repository tracker, but I'm gonna send out more information on that. You can also join the mailing list. I will be announcing it shortly. And this is a low volume mailing list. You might be interested in what we're doing and sometimes we also organize hackatons on boats. This is the first address to talk about it. And some members also have ships and we do organize sail crews now and then for trips around the world. And another thing that I'm excited to present or to announce is that we're going to produce hardware very soon, like you may have seen previous hardware designs of ship boxes and mast boxes. And I'm proud to announce that I'm currently in the process of procuring a new bill of materials for a new product which will be available sometime next year. And it's a board computer with a little bit of Wi-Fi but you can extend it. It's open hardware, most of it at least. There's some tiny bits which we can't really have open source, but we're working on it and the community is always working on it. If you'd like to be informed about these movements, you might want to subscribe to the list that is mentioned in the slide. I'll be announcing the start of this campaign sometime next year. Yeah, I have another slide here for the MIT Makersmeeder. There's the issue I was talking about. This will be the final discussion point or announcement point. I just didn't find Vicky at the RC3 this year. It's maybe it's hidden away. I haven't found time to dig in, but maybe you want to watch this issue on when the MIT Makersmeeder will be started. But I'll announce it as soon as we have a final date. I'd love to see you there and discuss the international maritime topics with you. This may range from technology over social aspects, but we're also talking about economic things and ecological things like the overfishing of the oceans or the maritime rescue scene and activities in the maritime and Mediterranean Sea. For example, this can be a topic as well. There's been very interesting discussions been happening these last years, so maybe you want to join this. So that pretty much concludes my talk. I'm now looking forward to any questions from the intertubes. Maybe you have something. I would be glad to answer anything. Oh, wait, and did I? I'll stop. No, no, not questions yet. We're doing something we tried out on the 2015 camp, and I think it was at that time it was pretty much revolutionary. And I'm going to try it again. Crowd management, please give us your input on how we are supposed to proceed. What are your current wishes? Maybe you have some. How would you want to see technology evolve in the hacker fleet context? Yeah, I'm getting funny notice here. We had some technical issues, and we need more better hardware, definitely. Is there anything from the internet? Oops, we're looking for the community manager? Well, I think we're going to do this asynchronously because asynchronous is always better. You can just join the hacker fleet channel or join the contact methods that we have here, and then just post them virtually, and I'll be answering them. I'll be here all day. My next lecture starts in half an hour. I will be proud to present the obvious shoot, which is something very different than the hacker fleet operating system, but it's been built with Isomer. It's a multimedia suit for mixing or managing mixed media sessions, and it was meant to showcase the performance aspects of Isomer, the framework itself, and Python, especially. Yeah, getting still more funny messages from them. So yeah, that pretty much concludes it. I hope you enjoyed it. I'd also like to greet the hacker fleet community. My flat and sea base mates, it's a breeze to work and live with you. I love you all and my family, of course. Greetings, go out to my family. Yes, world peace, please. Let's have the contact details a little bit more so you can know where to, oops, that didn't work. File, click in. And no, next, I need to catch myself. Thank you for your attention. All right, thank you very much, Wright. And thank you very much, Wright, the sailor, and I think you'll be back in half an hour with the next talk. Yes, looking forward. And that's about? 1400. Yes, that's the time, 1400, and? And it's about the avios suite, which stands for Audio Video Input Output. Audio Video Input Output, okay. So stay tuned, in half an hour we'll continue with the audio framework. Thank you.