 Speaker, kommen beide aus Ulm, sind sehr interessiert in Open Data und Mobilität und werden über die Verkehrswende selber hacken mit euch sprechen. Welcome to this translation of the talk Hacking Your Own Traffic Revolution. Your translators are going to be Waffle, Whitey Chan and Lingvi. And the speakers are Robby Five and Uban Falay. Thank you. Welcome to Hacking Your Own Traffic or Transit Revolution. Like many of you, we use mobility every day. And all of us pay indirectly or indirectly for this kind of infrastructure. And honestly, it's not great. The first contact with public transport is very exhausting for most people. That's a bit disappointing because we want to have great transit that can be used without having to think about it. And from this frustration, we got our motivation to do it a bit better. And so how can you as Open Data Activists hack your own Transit Revolution? This is the first thing many people think of. I photoshop this myself by the way. It's always nice to be rewarded for your photoshop skills. That's the first thing many people think of when they hear traffic revolution and mobility. Of course, it's not great because it's one part of mobility. It's electric vehicles. And it's more of a revolution in propulsion than in mobility. And of course, it's important because you don't want to diesel, have your buses diesel all over the place. I brought you my favorite picture. It's from 1990 from the city of Münster. And I think it's still very up to date. Because it shows how much space you need to move 72 people with varying modes of transport. And you can see that the car takes up an incredible amount of space. And of course takes this amount of space in our cities. And we have the very same problem with electric vehicles. They still need the same amount of space. Possibly even more because cars have grown in size. We like to speak, technologists like to speak of Uber and call it ride sharing. But there's not a lot of sharing being done there. It's more of a taxi. And if Uber wasn't there, maybe that car wouldn't be driving in the first place. And of course the bleeding edge of mobility is autonomous driving. We currently have an occupancy rate of 1.1 to 1.2 people per car. And autonomous driving might make it possible to actually get below 1 for the first time. So less than one person per average per car. You're applauding, but it's not a good thing. It means that we need more space. And of course this lack of balance in our cities is a problem in our cities. And this is what ride sharing companies thought of too. They wanted to optimize things that tech companies collect a lot of data. And they know what trips people like to take. And so they said, all right, we're going to optimize this. How about we have regular scheduled routes along these routes that people often take. And maybe let's not pick them up at the front door. Maybe just let's have them along a line and schedule intervals. Well done Silicon Valley, you invented the bus. It's nice for these ride sharing companies, but it's really silly because they're attacking public transport, which should be the backbone of the mobility revolution. And it also means that these operators only focus on the regions where there's a financial interest for them. And that's probably just city centers. So they're not going to serve the suburbs maybe or places where people can't afford transport. So they're rebuilding public transport, but only for rich people. There's no regulation to accessibility either. And it's a lot of cherry picking and they're simply picking cherries and leaving the rest on the table. And public transport planners have a problem too. They could go and say, all right, we have these commercial operators offering their services. How can we integrate that into our system? But the thing is, these operators can be gone as quickly as they came. I don't know how many of these scooter operators are going to survive the winter. But even larger companies that have been on the market for a while, such as Car2Go, they recently retired completely from the American market. And there's a huge gap now. Even after six or seven years, people are still sad for their departure. It's like the Google Reader effect. But everything is going to be great now because ridesharing companies are looking for the next big thing. Bicycles are definitely better than cars. They're all buying up companies. Lyft, for example, bought social bikes, Uber bought a jump. So you simply gobble up these companies and the next mode of transport. But it's not about being environmentally friendly. It's about building platforms because these companies want to have as many modes of possible in their apps and be able to extend their monopoly. And, of course, they have to serve the hype. These startups are less driven by innovation than they often say. They're more driven by hype. Of course, there's this golden age, this gold-digging mentality where the people profiting are the ones who own the shop. And so, yeah, we try to shop around for all of this equipment that is needed to have a bike-sharing system. We could just click that together online. In Munich, there were lots and lots of these bikes, but nobody dared to try something like this. So, we just started a fake startup and went shopping on Alibaba. The companies on there, we've asked about, we're a startup, we need locks for our bikes. We need documentation for the locks for our bikes and also for privacy reasons. We would like to build the app ourselves. And the fun thing about that is that these companies, we're like, yeah, let's talk about it. One of them said, sign an NDA, give us 10 grand and we'll give you the money back in locks. And another one said, we have a Chinese version, but tomorrow you're going to get an English one. And then we sat down, ordered one of these locks and just built a small app to open this lock. I started taking this lock further apart and just documented what we did, what we found, how this works. And the security angle, for a year, we didn't think about it anymore. But then we had the Gulasch programming night in Karlsruhe. And we had a famous bike-sharing company that works together with municipalities and other companies. And so they have this touchpad. They had that earlier to open them. And now we saw that these locks look really familiar to us. And so we were like, hey, wait a second, we built an app for that. And then we just tried it out. So, the question is, what the heck, why did these locks open? Because all of this communication between the locks and the app, you know, it's pretty okay. It's transport encrypted. And there's a unique unlock key, just like with classical mechanical locks. Turns out the operator used the default keys that were printed in the documentation. They just didn't change them. And this is quite absurd, das means that everyone who has the app installed, which opens the locks, carries around the default key. And then we found out they don't even do Bluetooth. These locks have a built-in SIM card, use mobile Internet. And when you click in your app, you know, they just unlock. And so, they forgot to lock the Bluetooth communication down and just use the default keys. And then on CAM this year, we also found that these keys are also part in not just in bike locks, but also chain locks. Scooters, when we talk about scooters, we always think of these sharing scooters that are all the hype right now. But it's always this hype-driven start-ups. We had bike sharing before, and then we had scooters apparently a long way back. But they're well-known for quite another fact, because there's lots of operators in the same cities. And this leads to the situation that, you know, five different apps, you want to use a scooter, it doesn't work well with public transport. And basically, it's just about, I want to find the nearest means of transportation for me. It could be public transport, it could be a scooter, and it would be so nice to have one app for all of that. And of course there's a standard for that called GBFS, which is intended to give out precision data of vehicles, of transportation vehicles, and make them public. But none of these scooter operators actually use this standard. So again, it's like building a platform, building a monopoly, and nobody else can access it. But again, it's apps, and they have to have data somewhere in the background, so that they have to be APIs. And then we started documenting these APIs. We did that for bike sharing, but for the scooter sharing there were lots and lots of APIs. And so we just concentrated on where are the scooters right now, on the location data. And yeah, so we went through all these operators and then we thought, wait, we know this API, don't we? We've seen that before. And you know, they do something so differently. They have different investors, but they all use the same API. And so it turns out, it was all bought. And this is a famous German song from the 90s. Yeah, and so we're back to the gold rush and the shovels and the digging. There's multiple software companies building this software for sharing systems and selling them. And so if I want to operate a scooter sharing business, I just have to buy this, put my sticker on it, buy scooters, put my sticker on it, buy software and roll it out and start up done. And not everyone does it that way. There's also operators building their own software. So one of them, we found their admin login page when we were looking for their API. And you know, modern web development. Oh, there's a login screen. We don't have the login data, right? But of course, the whole source is being loaded. And so we can just check what APIs do they talk with internally. And what APIs need authentication and which don't. And that really sucks when the API dealing with customer data doesn't need any sort of authentication. And yeah, the media really got on that here with the Bavarian radio, which had reports on this. And so, we just wanted the location data for scooters and then suddenly you have this private user data. But really, what we wanted to show is where are the scooters and document that. And so it didn't take long for people to start building apps in which multiple operators, location data was combined. And then we also were able to check which APIs these apps talk. And so one step further is to see where are the scooters actually. But also, you know, these scooters have pretty much unique IDs. And so we can just check, like, where is it now? Where has it been? And where will it go? And so I can check at the end point of a rental and the end point of a rental ride. And then I can visualize this. And so the city lab Berlin did exactly this, did this nice visualization and, you know, it looks great, right? But you can actually use that to analyze traffic within a city to see from which point A's to which point B do people move about in a city zu be able to see stuff like that Yeah stuff like that. The Los Angeles Department of Transportation did something similar and they were thinking of something similar because on the west coast that's where the whole scooter hype started and suddenly the city had thousands of scooters lying around and they were wondering, well maybe we should dass sie mit einem technischen Standort gekommen sind, die Mobilität-Data-Specification, die es schreibt, das, das basically sagt, dass die Provider alle Fahrzeuge registrieren müssen, aber auch, dass sie einen Rettungsverkauf werden müssen, wenn der Schilder von den City Streets beinahe wird. Sie haben auch Daten über die Rentale und wo die Leute gehen, die wirklich die Traffik planieren. Wir reden einfach über, wo die Leute gehen, in welchen Bereichen sie nicht benutzen, vielleicht, weil es eine neue Bikelin ist, das ist einfach schlecht. Aber auf der anderen Seite, es ist nicht nur über Daten von den Provider, aber die City itself auch die Daten und die Traffik-Data geben. Es gibt viele, z.B. mit den Regierungen zu Bereichen, wo die Leute wirklich die Schilder parken wollen. Aber auch Bereiche und Bereichen, wo sie vielleicht nicht wollen, wo sie vielleicht nicht parken wollen, weil es die nächsten Tage eine Marathon wird. So, LA hat auch eine Ordnanz, die sich verabschiedet, dass eine Schilder-Provider die Service in LA auf der Stelle geöffnet hat, dass sie die Spezifikation erfüllt. Und diese Ordnanz war komplett aufgetupft. Das bedeutet nicht, dass es nur aufgetupft wurde, sondern es ist jetzt nur Muldi, aber es wird kontinuierlich geupft, durch die City of LA, aber auch durch andere Citys und durch die Providers und die Volunteer. Sie haben nicht nur die Ordnanz, die sie verabschiedet haben, sondern sie haben auch die ganze Software online geöffnet, die sie für die Regulierung verabschiedet haben. Alle von ihnen sind aufgetupft. Alle von ihnen sind auch aufgetupft. Und sie werden jetzt auch verabschiedet und weiterverabschiedet durch andere Citys. Wir haben uns gefragt, dass alle von ihnen eigentlich cool sind. Die Citys sind also reguliert mit Schildern, ohne die Leute auf die Städte zu senden, die die Schilder in den falschen Platz parken. Wie können wir das in irgendein weiterporten? Weil es gut ist, und es gibt ready-made Software für das. Wir haben also ein paar Forschung gemacht, und wir haben es realisiert, dass, außer für uns, niemand in der deutsch-sprecherischen Welt so etwas zu finden sieht. Wir haben ein paar Blog-Posts geschrieben, wo wir das erklärt haben, und wir haben auch eine Begründung und eine Begründung auf dem Schilder, die man wirklich an die Leute, die in der City-Administration arbeiten, weil sie wirklich etwas auf dem Schilder magen. Der Zeitpunkt war wirklich gut, weil die Citys meistens von diesen Bilder gedacht haben. Das ist in Munich, wo vor einigen Jahren die All-Bike, basically just dumped thousands of bikes in the city, which were just kind of lying around everywhere, and the city was really not happy about it. But in addition to that, scooters weren't legal in Germany yet at the time. But it was kind of becoming obvious, but this legalization was probably going to happen at some time reasonably soon. In addition to that, all scooter providers had announced, or many scooter providers had announced that they wanted to become active in the German market. So the cities were scared and really had a strong interest in some kind of regulation. And we were, well, that's kind of stupid, because we don't actually know which cities we should talk to. We just wrote some kind of blog post. Nobody's going to read that. So we started researching where do these providers want to go. And so Maxi had this amazing idea. Well, they all want to go to all these different cities, and, of course, they want employees in these cities. And so they have job postings. And so we just crawled all these job postings to look at which providers wanted to go to which cities. So we created this map, this beautiful map, which tells you which city has how many providers who want to go there. You can see which state they want to go into. Every German federal state has at least one, except for Saarland. Well, and then we got these cities and sent them emails, which was something like, hello, do you know? Are you aware of this whole scooter thing that's coming your way? Do you have a plan for regulating it? Have you heard of the mobility data specification? Well, maybe you haven't, but we've prepared a blog post. You should read it. We also got a lot of feedback about it. And then what that led to is that now Hamburg, Ulm and several cities in North Rhine Westphalia are actually using this mobile data specification and are demanding this type of information from all providers there. So that means what we realized. If you recognize a topic in time and you look at which technical specifications or solutions exist, come up with something that might make sense and then we give that to the municipalities and talk to them constructively, then you can just make policy and implement your own solutions. And yeah, it worked incredibly well. And maybe there are other topics that you are interested where you realized in time that something interesting might happen. Well, it might make sense to just go up to people and talk to them. Another thing that's also really nice about the mobility data specification is that the providers are not just providing the location of the scooters to the municipality, but that they also have to be provided in this GPFS format and that it's provided in, specifically provided as open data. And open data is exactly the right thing for this because it means that this data is available for anyone without registration at no cost at a free license. And that's exactly what you need. If you want to integrate the location of scooters into your own apps or analyses. And funnily, that's exactly what LAM wanted to do with the mobile data specification, which was to essentially break up these platforms and provide us a bit and make mobility easier for everyone. The absurd thing about the whole thing is that now we are demanding open data from private providers, but with regards to public transport, which are being paid for and operated by the government, this whole open data thing doesn't really look super well because things such as stops, like locations or schedules would be incredibly important from these providers, but we don't even have those in many cases. So we came up with three examples. The first is Digitransit. You can use that to use the data to basically provide an information provision platform. Digitransit is an open source routing stack that was developed in Helsinki in Finland and that we could just implement for ourselves. And the beautiful thing is that it's not just about like a nice way of providing public transport data, but because once you start getting GPFS, you can also implement and integrate bikes, car sharing scooters. So what it basically does is that it tries to integrate as many different ways of mobility and portray as many of them, visualize as many of them as possible at the same time. Another thing that goes a bit further is the decentralized car sharing, the decentralized ride sharing, mit Padezentrale in German, where you basically can do mobility for other people because it essentially understands these different types of mobility as extensions of public transport. So there's these different ride sharing platforms and all of them are turned in, you essentially scrape recurring routes from these ride sharing platforms and then you can put those into Digitransit to enable people to figure out how they can get from a place that maybe doesn't have a bus and how they can get from there to somewhere that actually has a public transport stop or transport location. Another nice project is one that was shown to me on the Bahn Hackathon a few weeks ago. It was called Missing Buses and it was about using public transport data and demographic data to find out in which areas where people live is there a lack of public transport. But where one bus route would be enough to connect these buses to the network at large and make people less dependent on their cars. We have more than 100 public transport authorities in Germany and only very few of them open up their data. And we often asked, what can I do to get this data? And we noticed that it's not very efficient to ask these authorities themselves because all they do is they drive buses. They exist to drive trams and buses and that's what they give money for. They get money for. They also develop timetables but essentially they get financed by the by the municipalities. And that's why we started a project called Rettedain Afrika, Save Your Public Transport. And you can enter your postcode and you get a generated PDF that you can then print out. And it tells you why mobility data is great and why it's great and important for municipalities. And the nice thing is it worked. Lots of people use this. Thank you very much to all of you who use it. It actually changed things. We could use it to accelerate this process in many transport authorities. And in some cities this was what first got this topic onto the agenda and what finally opened up public transport data. Another player in mobility is Deutsche Bahn, the German railway company. They have an open data portal. It contains lots of nice data. It has an interface that tells you which elevator is currently running and which isn't. So if I'm doing my own routing, because I'm a, well, I can see, okay, I have reduced mobility, so I'm not going to use this station because the elevator is not working, but I can use this alternative station. And so I can adapt my route. But the thing that they don't have is what everybody wants. It's timetable data and there's a lot of work still to be done. Feel free to annoy Deutsche Bahn a bit more and to tell them that they should publish that data. And we have car sharing companies. Some of them say, yeah, wealth data. I mean, should we tell you where our cars are? No, it's a company secret. And if you want to have that secret to tell potential customers where one of their cars are, then they want to have license fees for that. It sounds like Germany's ancillary copyright law. And we thought that was bullshit. Those, everybody who offers mobility solutions should open up their data if they're using the public space for that. And it's not even very extraordinary. This is law in Finland, for example. And that's why we're saying, as long as this is not law in Germany, people who don't want to play along are going to find the data published on transitbay.org. It's a platform where scraped data can be uploaded and it's not even that illegal. There's no copyright for factual data. I mean, it is fact that there is a bus running a certain route at 18, 30 in the evening. I doubt that this reaches the threshold of originality. And neither is it is there a copyright on the fact that there's a scooter in a certain place. And of course, this does not guarantee that the start-up from Silicon Valley is going to come along and platformize mobility. And so, what's the alternative to this? Can we maybe build our own ability? And building our own sounded interesting. So we had a look, driving our own trams sounded fun, but it's very expensive. So we got back to the original idea and that was bike sharing in places where there isn't any bike sharing yet. So we looked for a cheap mode of transport and considered options of doing that. And a great thing happened last year, or this year, it was camp and it allowed us to experiment. And we asked people to bring along bikes that they might have sitting in their basement and bring it to camp. And we built a backend and web app and some combination locks for the bikes. And so we sat down and built a bit of hardware as well and printed it. And it allowed us to plot the location of bikes on a map. And so camp happened and this call for bikes worked. We had more bikes than we had trackers. And people showed up, borrowed a bike that we only just screwed a tracker on and went on their merry way. And as all bike sharing companies do, we lost all our bikes the first night because we didn't have any monitoring for the trackers. You learn a lot when you do this kind of thing. And thanks a lot to everyone who gave us a bike and to those who built the software at camp. Something that surprised us was that these purple dots started appearing on the official camp map because we simply offered the location of these bikes as GBFS. And because there's documentation for GBFS and there's a specification, people who built this map were able to plot the location of the bikes on the map. And we only started noticing this when the server load started increasing a bit. And of course we didn't only want to build this for camp. Our motivation was to have bike sharing in our city. But unfortunately, bike sharing companies aren't very interested in the city of Uem because Uem has a problematic mountain. Well, we have a lot of mountains actually and bikes have this annoying habit of liking to ride down hills, but not up. And that makes bike sharing a bit difficult. So we thought, can we maybe have it in the city center first and then think about e-bikes later? That would be great, wouldn't it? So we said, this is our motivation, this is what we want to do. And we started telling people that we want to build our own bike sharing and start building it. And the city of Uem said, hey, bike sharing sounds great, we want to have it. But then there was this matter of that all open source problems face where people suddenly stop working for it. And that's why the city of Uem said, hey, what do you think? We're going to pay you to build open source bike sharing. And we're building open data by default into this. Of course, this system is going to retain this open API. So everybody who sets up one of these instances is going to have open data by default, and it's very difficult actually to pull this out of it. And of course, the problem is going to remain open source. It's important, this project is being paid for by public money and that's why the code has to be public as well and has to be open source. And the city of Uem has used a lot of funding for that. And usually when a city that gets money, all other cities that applied for this aren't getting anything, but this is not the case with open source because all other cities can use this system as well. They can run their own instance and then they have bike sharing too. Reality check though. I don't know how realistic you think it is that all cities are going to run a system like this. There's a lack of technical expertise in cities and municipalities and authorities. And it's a topic that we've laughed at a lot over the past 10 years, but laughing at people hasn't really worked. So maybe it's time to realize that the people in this room and in the streams and in this scene have expertise and maybe these people should use that expertise and offer it to municipalities and show them what great stuff you can build. Build things like departure monitors. Don't just build them in your hackspaces. Tell people about it. Tell the restaurant next door to have it. Tell them how great it is to make mobility visible because only if it's visible, then those mobility solutions are going to get the money that they need. Start setting up open source projects. These are great because lots of people started running software like this and started developing it and that made it better. Talk about it. And if you need data, then request it. Show what you've built. Speak to the right people. Go to the municipalities. Go to cities, authorities. And tell them what great stuff you've built. And maybe you want to start not just talking to municipalities, but actually work from the inside. Hack mobility from the inside. Thank you. Thanks a lot for this amazing talk. So we'll now get to Q&A. If you have any questions, just come to the mics here and just line up there. Thank you for the talk. When O-Bike started in Berlin, they said that company secrets definitely include the usage of mobility data. But this doesn't really fit with your open data approach, does it? Yeah. So also when this entire hype happened of these providers from Asia, they had all these slides that said things such as the whole thing about private data. But I haven't heard anything of them getting data. So I think I don't know about bikes. And at least for the scooters when it became such a big thing. I know that also the administrations themselves didn't even know where these scooters were. So they also asked for this data and so they specifically requested this location information. Oh, that worked great. Thanks for the talk. I started a petition in my city and there's a lot more of those happening. Did you network in that scene? Is there anything they can learn from you or you can learn from them? Well, we actually in Uem we are actually talking to the ADFC, which is a biking club, which did something in that regard as well. In 2011, I think we already had a petition on the local political level as well, that they wanted to have 20% of all transport to be bikes by 2020, guess what didn't happen. And we are definitely in touch with people there and are discussing how we might be able to push this further by cooperating. But, yeah, come talk to us. Thanks again for the talk. Meine Frage wäre so, erstens, planen wir ... Are you planning to extend this project to other cities long-term because it's not brilliant if all the cities are doing their own thing? And do you have any suggestion for generating money for this? Oh, I have a suggestion, actually. If many university towns include bike-sharing in their semester tickets, in their public transport tickets, and the universities are fairly, or the student associations are fairly unhappy with these commercial companies, and they'd be happy to invest money that's currently going to next bike into non-commercial bike-sharing projects. Ja, so, was wir fokussed on is turning all of this into software. Obviously, we're working with the city of Ulm, and so now we have a prototype there that we can use to learn. And what we're really interested in is also making sure that administration is something that you can do yourself, because we don't want to put ourselves out there and say that we're providers of bike-sharing, but we want it to be possible for people who are interested in it to be able to implement it. That can be a university, but that can also be a small tourism association or a hex-base, that you can essentially do it yourself and try. And in addition to that, we also, this whole thing about every city doing their own thing, that's also kind of part of the idea that you're not supposed to register in 10 different systems, but what we hope is possible that you can kind of have a system that basically the systems can talk to each other, but we don't have the software for that yet. Die nächste Frage vom Mikrofon 2. I'm impressed with what you've been building in a very short amount of time, respect for that. But there's one aspect that I would like to ask about. This using of public data usually also means that you should protect private data. And once this data is in the hands of the municipality, how long is it going to take until they get very interested in how they can use data of the position data for vehicles to, for example, prevent terrorism. And if all of this is within the same framework and maybe even across several operators, it's going to be even more difficult to prevent that. The funny thing about this is that LA was thinking of exactly the same thing. They published just a pretty long white paper that also included the technical plans, which this was a part of. And but they were also doing other things. They very clearly have that on their radar. So in the MDS, it also says that the data that providers submit cannot have any relation to customers. Customers cannot have any identifying information. Those things should not be linked. And that's also what I consider the solution here, that they're kind of going past the goal here, which is what's funny, because they're basically trying to come up with some kind of scare campaign. But the people who develop MDS and you can also just participate in that. That's a GitHub repo. They have a mailing list and they're weekly calls or something like that. And so they're definitely thankful for input data to totally stand behind something like that as well. Another thing is that I don't know what the difference would be between this data, being with the provider and being with the city, because if the police wants to have access to this data, then they can probably get it from the city and then these private providers in similar ways. I don't know. But it's definitely a topic and it's definitely a thing. There were also already attempts, especially with regards to the rights. So when right data is being submitted to the relevant institutions, that maybe you could get rid. But that maybe you could make an Analyzation easier by cutting off a random bit in the beginning of the end of the route. I don't know how exactly and how well that Analyzation works. Maybe you should have a look at a kind of data set to see whether this is an actual option. Brilliant hacks and a great talk. Thank you very much. I was missing one thing, though. It's the infrastructure of cities. You talked a lot about bicycles, but you can probably use that data to find out where people are riding their bikes and where you should build a bike path. I mean, those exist, but they don't tend to be very safe. Are you in touch with people who are trying to buy and build cycle paths where they're needed? I mean, we also know the typical campaigns that are working on stuff like this, such as ADFC, which you are also probably aware of. But infrastructure obviously is a very important topic. Infrastructure is really bad in this country. We should really invest way more money into it. And that's funny, this is also something that you can pour to somewhere else. And just as we have no bike infrastructure, we also have very little infrastructure on the municipal level to just host a project like this or just implement something like this. And that really needs a lot more political focus. And that's something that really makes this very, very obvious, that there is a deficit here. This whole routing thing doesn't really help you. And this routing data doesn't help you. If the only piece of information you get is that the only bus you could take leaves at 7.30 a.m. People need we need to focus on this much more to not only see the problems, but feel the pain and then hopefully do something about it. And maybe in addition to that also go and say we don't we're not doing something like save your public transport, but the campaigns are just like save your bike lane and start implementing campaigns like that. Die nächste Frage von Mikrofon 6, bitte. I'm a student from Kartswood. Do you know if the public, if the biking company in Kartswood has already fixed that vulnerability? Why they sent us an email where they said that they fixed the vulnerability and switch the Bluetooth keys. We couldn't check. Oh, it actually doesn't work anymore. Ah, that's a shame, but thanks. I'd like to pick up where you ended your talk. And you said that the people should go into a public administration and into politics. And I think it's important that we don't simply don't just use Congresses like these to build or build things and then only reach up. Peer groups, we should actually get society into the digital age. And it feels to me that these municipalities are often approached by companies that want to sell them student solutions that are then taken up by politics. But where the people have this kind of competency and we should take it to where it's desperately needed. Thank you very much. Am Mikrofon 3, bitte. Thanks a lot for the talk. Maybe you'd like to say one or two sentences about the open bike sharing that you're building. You said you're mainly hacking away at the software. But what about the hardware? Do you have any bikes in Ulm that are refurbished or maybe bought new? What are the plans and how realistic is it that you can tell your municipality, hey, here's a system, all you need is bikes and off we go? We were extremely lucky because we actually found some money in the city that we could use, that we were able to use to buy 20 bikes. So we just provided this very basic infrastructure that you can play around with. Locks, we're really starting from a very basic starting point, such as what you know from the from camp this summer with the basic number lock is what we're using right now. But we're also looking into other options and maybe putting some other things together, possibly building a prototype, how you could maybe implement and realize something like this, to also implement this on a hardware level, because it doesn't really help if we just buy them from somewhere else. And that's also something, all of that is already on this GitHub repo. And we've also written down in a lot of detail, where we kind of started from. And what we wanted to achieve with this open bike sharing. And by now, the GitHub repo, also in GitHub.com slash Radforschung, also includes not just all the software data, but also an experimental software for the trackers for these bikes. And then soon, they will hopefully also be locks. And then in addition to this, another appeal, if you're interested in this, come talk with us, talk to us, this is a really interesting thing. You can do this in a decentralized way. And like beautifully, if there's a Hackspace that wants to build some hardware, or just wants to give us some Hackspace, some bikes that we can use in some, or we can try some stuff, that makes it easier. And the more we can do together, the more people participate, the easier we can do this. And check out, try whether, for example, our roaming idea works as well. In addition to that, it might also be interesting, if you also start implementing a similar system in different places, because obviously different cities are different in terms of application. So it would obviously be interesting for us to not just build it for the city, in the case that we know, which is all, but also figure out how this would work in other places, where there might be problems that we had, maybe not even thought of. And in addition, with regards to hardware, we also, yeah, we definitely want to try something there. Vielen Dank. Die nächste Frage am Mikrofon 2, bitte. Ich hätte auch noch was zu tun. I was wondering about use cases. There are these high-load bicycles. Do you know if they're being used anywhere? We've been contacted about this by several people already. We just don't have a ready-made lock yet. So if you want to have one of these high-load bikes, that's also slightly more valuable than the typical ride-sharing bike, you really need a proper, a bit more there. And with regards to these bikes, they're also amazing. But you need at least 15 minutes of an introduction to learn how to use them, especially if it's one where you have kind of the load in front and it suddenly completely changes the weight of the bike and how it drives it, how it's driven. So we're not entirely certain, actually, how to integrate something like that into the system, to properly integrate into the system, because how do you essentially do this introduction? Die nächste Frage vom Mikrofon 3, bitte. Hi, super talk. Great talk, thank you. What about maintenance? Maintaining the fleets, things such as tire pressure or brakes, this is going to become relevant sooner or later. Do you have any thoughts? So we have a maintenance module, which you can put to this vehicles currently under maintenance. All we were thinking is what can we do in order to implement this. And so we set the starters, we're going to try to implement this ourselves. And so if something is broken, we're just going to do it ourselves and fix something broken ourselves, especially with regards to maintenance and real provision and operation. That's something where we will learn a lot and where we have to learn a lot. And that's also something where we're motivated and part of our motivation, because we know that we need to learn how to make sharing. And then this type of information that we learn there, we also don't want to just keep that to ourselves. But this stuff that we're learning and can try in this practical test, we're going to document all of that, so other people don't have to make the same mistakes again that we're making. Well, then another round of applause. You're listening to the English translation for Hack Your Own Mobility Revolution.