WEBVTT 00:00.000 --> 00:18.840 Hello again, I apologize, this is very much last minute, but that is how this works, 00:18.840 --> 00:24.760 because some of the people with a hacker train just arrived today, so I only learned 00:24.760 --> 00:33.080 how it went at noon, so I had until from noon until now to do slides from scratch. 00:33.080 --> 00:42.000 Okay, so, um, hacker train, or, you know, the subtitle that we choose this year is 00:42.000 --> 00:47.440 a quote from one of our participants this year, which is like, yeah, you know, train delays, 00:47.440 --> 00:54.560 they're just bonding opportunities, why that is, you will soon see, um, so what's a hacker 00:54.560 --> 00:55.560 train? 00:55.560 --> 00:59.840 Well, I mean, obviously, it's a hacker, it's a train with hackers on some clearly some 00:59.840 --> 01:08.160 plushies on it, um, so just a short intro for those who were not on last year's presentation, 01:08.160 --> 01:14.760 so the main idea is, you know, we have around 10,000 people at Phosphum, many of them are 01:14.760 --> 01:21.800 from Europe, many of people from Europe are going by train, which means there's likely a few 01:21.800 --> 01:27.600 thousand people going to Phosphum by train every year during the same days, probably on 01:27.600 --> 01:33.880 the same trains, so let's meet and possibly hack on those that trains, so that was the 01:33.880 --> 01:43.760 main idea, um, so clearly as any reasonably thought out project, which we are, but we did 01:43.760 --> 01:49.360 have some goals, so there's some short term goals, um, and the first one is clearly like, 01:49.360 --> 01:55.480 make traveling fun again, so make it ecological and comfortable within reason, uh, to travel 01:55.480 --> 01:57.800 and to meet other hackers along the way. 01:57.800 --> 02:03.280 I think we succeeded that we proved last year during the beta run, which was, as a reminder, 02:03.280 --> 02:10.480 was a single route from Lubljana, Prague, and then, to Brussels, Night Train, um, that is 02:10.480 --> 02:14.320 possible, um, and this year we made it a bit more difficult. 02:14.320 --> 02:19.880 So the Lanke term goals are to make it more efficient, affordable, convenient, and ultimately 02:19.880 --> 02:28.240 book a whole freaking train, to hack on, to so have a hacker train on the way to Phosphum. 02:28.240 --> 02:35.600 So compared to last year we actually have infrastructure now, uh, we have website, we have, 02:36.560 --> 02:44.360 some task list, um, so this is the website, this is, you know, some information about 02:44.360 --> 02:49.320 this trip, like Phosphum trip, so it was really useful, I think. 02:49.320 --> 02:55.320 So, so, uh, of Frange also made a really cool map where people could register their interest, 02:55.320 --> 03:03.920 so you see, like, how many people are going from which place, which helped, and planning, 03:04.000 --> 03:13.680 how we have, uh, organization on Codeberg, um, this is how we manage our, um, our routes, so you 03:13.680 --> 03:19.520 can see, like, for example, like the seal group is going to Phosphum, it's going through Belgium, 03:19.520 --> 03:26.720 check check Republic, Germany, and the Netherlands, um, and, yeah, just, uh, it's going on 03:26.720 --> 03:32.800 the 27th of January, so this is how you find your route if you're looking for it. 03:33.360 --> 03:41.440 Uh, we also made it a bit more visual with, uh, with, you know, uh, with, with a Kanban board, 03:42.400 --> 03:49.040 um, and yeah, we have contacts. Now we have, uh, IRC and Matrix channels, which are, which are 03:49.040 --> 03:57.600 bridged together, um, XMPP, if there's a nice interest soon. So how did the infrastructure work? 03:57.680 --> 04:02.240 It worked surprisingly well, all things considered, so and the things to be considered are, 04:02.800 --> 04:11.520 this was the first distributed system, roughly 10, 20 routes in total, 80ish people, 04:12.880 --> 04:20.160 and things happened. So the trip itself, like, so let's first set the baseline, because you 04:20.160 --> 04:26.720 see a lot of very tired faces who were on the hacker train, so the baseline was, things happened. 04:28.560 --> 04:31.680 Uh, my favorite quote from the things that happened were, 04:32.640 --> 04:37.680 our train is not compatible with the Belgian electricity we need together to get on a different train. 04:37.680 --> 04:46.000 And, oh, um, because of the Belgian, um, the railway strike, uh, we have railway placement, 04:46.800 --> 04:52.480 transport, and Luxembourg just sent trains to replace the trains. 04:53.360 --> 04:58.000 Which I think, in technical terms, is a cluster fuck. 04:59.440 --> 05:04.880 So that baseline, but that said, so there's going to be some harsh words later on, 05:06.000 --> 05:10.000 but we try to package those harsh words into constructive criticism. 05:11.600 --> 05:19.280 So the report from the routes themselves, um, we had a fight calculated correctly 12 routes, 05:19.360 --> 05:24.240 go to Brussels, plus a few routes that weren't technically train routes, so they don't count. 05:25.440 --> 05:30.640 For returning routes, plus two routes that are not actually in fact returning. 05:31.760 --> 05:38.800 So the p-fowl route over there, if anybody wants to go, uh, on a return trip through 05:40.000 --> 05:44.000 knees and south, uh, I think you're going through south Italy. 05:44.320 --> 05:55.200 I mean, there's a route for that going from Brussels to finish, um, and there's an even more 05:56.400 --> 06:03.840 adventurous route, uh, the nightingale route, which is going from Brussels on, uh, on a hacker exchange with Kiev. 06:06.400 --> 06:11.680 Um, we also had like two short meetups in Brussels, one was at the pinball museum, and one was 06:12.400 --> 06:18.160 earlier today when I actually learned what happened, um, so that was fine, I think. 06:18.160 --> 06:25.680 So if I summarized the route from, uh, the routes in ascending order of excitement of them, 06:27.120 --> 06:31.280 I originally thought that we're going to pass the mic, but I'll just do it myself. 06:31.280 --> 06:35.600 Um, so it's not going to be as, from the heart as it would have otherwise been. 06:36.560 --> 06:44.240 So the hedgehog line had no issues. The shadow route, uh, which is was unannounced, but was like a very 06:44.240 --> 06:50.640 late show, um, they also had no issues. Uh, the pigeon route, which went from London, had no issues, 06:50.640 --> 06:59.360 but there were a loan. Um, so where things started happening was duck route, which was the one I was on. 06:59.680 --> 07:06.560 Uh, we ended up with a three hour delay, but it was partially on us because we could have 07:07.120 --> 07:13.200 catch, we had to change a train in cones, so in the night train stopped in cones instead of going to 07:13.200 --> 07:21.360 Brussels. Um, but we could have just took, take the first icy that popped up, but we decided to not. 07:22.160 --> 07:27.920 So that's on us. Um, the seal route had a completely different route. They went with the European 07:27.920 --> 07:33.600 sleepers from Prague to, uh, to Brussels, and they had a three hour delay with 07:35.520 --> 07:41.920 something's happening, but not too much. And the boring people route, uh, emerged at some point, and they 07:41.920 --> 07:46.800 also had a three hour delay. They were also a European sleeper route. Um, they there was some 07:46.800 --> 07:55.120 technical issues involved. Um, I saw in the morning when I was scrolling on my phone on the toilet, 07:55.680 --> 08:01.840 somebody was said, who the, er, triggered the fire alarm on the night train at four in the 08:01.840 --> 08:10.400 front morning, uh, and five. Yeah, so three hours later, I saw somebody else saying, oh, so that's 08:10.400 --> 08:19.360 what it was. So, and then we have the unfortunate Diplodocos line, which I will not be able to 08:19.360 --> 08:24.720 summarize in a correct order, but there were technical issues, including three hours waiting for 08:24.800 --> 08:34.080 a bus. There was a knife, but knife have fight on the tracks, which caused a severe delay, 08:35.120 --> 08:43.360 which eventually caused the train to go backwards to Munich. I think then they had to wait for a bus. 08:43.360 --> 08:49.360 Some people went, um, and tried the different approach. Um, and in the end, they didn't get the 08:49.360 --> 08:55.440 tickets back for the night train, which is going to be a problem eventually. So, what did we actually 08:55.440 --> 09:00.640 do any hacking on the trains, right? So, there was some improvements on the, somebody improved, 09:00.640 --> 09:09.840 like the pigeon line improved some matrix stuff, the snail line, uh, finished some really fancy 09:09.840 --> 09:15.680 malware detection things that I have no clue of to tell you what it is actually. With it, some 09:15.760 --> 09:21.760 discussions, and conferencing, um, and the most important part is we suddenly saw our 09:21.760 --> 09:28.160 matrix IRC chat suddenly became the go-to help line for the 80 plus people that were traveling 09:28.160 --> 09:33.520 on the hacker train, plus all the dozens of people around them. So, again, like the Diplodocos line, 09:33.520 --> 09:41.440 was officially two people, um, and when 10 hours after, they had a 10 hour delay ultimately. 09:41.520 --> 09:52.800 So, 10 hours, uh, 11. So, within those 11 extra hours, they've done a lot. Um, and one of those things 09:52.800 --> 09:59.040 was when I talked to one of the guys on the, on the Diplodocos line, he was like, yeah, we were officially 09:59.040 --> 10:06.880 two people, but we had like 20, 30 people rely on us to get them to Brussels or home. 10:07.440 --> 10:18.960 There were, there were young kids involved. So, again, I mean, this is the baseline plus what 10:18.960 --> 10:25.200 happened. So, you know, you do with the clusterfuck, what you do with the clusterfuck, a clusterfuck 10:25.200 --> 10:31.920 is by definition, several things going wrong that together caused a big chaos. So, we're not going 10:31.920 --> 10:37.600 to blame anybody, um, but we had some suggestions for the future. So, the one, some, there's some 10:37.600 --> 10:43.360 for organizers. So, for the hacker train project itself, um, some groups would be really good 10:44.160 --> 10:49.600 to start planning sooner, especially the euro star ones, because you have to reserve. So, 10:50.800 --> 10:58.640 you cannot just find people on the train, you have to plan in advance. Um, we'd like to 10:58.640 --> 11:04.800 simplify group bookings with more operators. So, if anybody can help with very happy to 11:06.160 --> 11:14.400 do that, um, the map is kind of cool, but not as useful as we thought it would be. So, there will 11:14.400 --> 11:24.160 be some improvements there. Um, also how we use the issues could be improved, but what we figured 11:24.240 --> 11:29.680 out would be really good is to create the travel train travel beginner tutorial that we would put 11:29.680 --> 11:34.000 on the website, because there's a lot of people, I mean, when you tell people to go with the train, 11:34.000 --> 11:38.000 you know, you people think, oh, you buy a ticket, you hop on a train done. 11:39.600 --> 11:45.040 There's something happens. And then, I mean, even when you're book when we're buying a 11:45.040 --> 11:48.880 train ticket, there's, you know, options where do I band a train ticket? What if I'm, you know, 11:48.880 --> 11:54.000 using different lines or different operators, et cetera? It's a bit complicated. So, 11:54.160 --> 11:59.840 we hope to, if anybody can help, we would like to write a short tutorial and, or at least some 11:59.840 --> 12:07.200 links for people starting to put it on the website so they can start with traveling. Um, again, 12:07.200 --> 12:15.840 we would still love sponsors or any other way to subsidize the trip. And yeah, we would also 12:15.840 --> 12:20.960 expand to other conferences, so we're already talking about CCC and so the infrastructure is there. 12:21.040 --> 12:27.440 So, if you have any conferences you would like to use the hacker train for, just join, 12:28.640 --> 12:33.440 we'll share whatever we know. It's not that hard. And for the railways, 12:35.440 --> 12:42.480 it would be a need to fix the rest of the mass notification. I'll just leave it here for a few seconds. 12:43.280 --> 12:54.160 Yeah, and, but, well, it's, it's a mess. So, like, like, there's like, apart from the colors, 12:54.160 --> 12:59.120 like, there's half of words are missing. So, you cannot figure out what sentences mean because 12:59.120 --> 13:07.600 there's no sentences. Um, Deutsche Bahn, when the cluster fuck happened, you know, one of the, 13:07.600 --> 13:13.520 one of our members was trying to help, and it couldn't reach Bomb Day because it's 13:14.400 --> 13:21.840 trying to, it's telling him he's a bought and he cannot access it. And then this happened to, 13:21.840 --> 13:28.080 again, unfortunately, Plodocosline. So, they didn't get the night train tickets back. So, 13:28.080 --> 13:35.600 they eventually got a paper written by hand that they actually have tickets and the tickets are on 13:35.760 --> 13:41.200 a different train. So, they can continue their travel, but I don't know how this is going to go 13:41.200 --> 13:49.280 when they're trying to get some reimbursement for the things that happened. Um, European sleeper, 13:49.280 --> 13:55.920 there was an issue with the referral link. So, they need to make sure that it works throughout 13:55.920 --> 14:03.440 the time, not just, you know, initially. Um, Trenitalia, this was a pain point. Um, 14:03.840 --> 14:14.400 again, PFO, um, tried to, you know, got noticed that they have to be a cancellation or change, 14:14.400 --> 14:20.800 and that he can only do it with phone or in-person visit in an Italian train station. 14:20.800 --> 14:29.040 Here's from India. So, this is where he started. So, this was a problem. Um, generic wishless 14:29.120 --> 14:33.600 is the same as last year more or less. So, I'm not going to, not going to waste time on it. 14:34.880 --> 14:43.360 Um, so future plans. Yeah, what's still like to do this. Um, and you can already use our infrastructure 14:44.160 --> 14:49.360 for other events. Um, if anybody wants to use it for other continents, um, you can also use it, 14:49.360 --> 14:54.880 but I think there would need to be some tweaks. So, let's discuss, but it's something that we can do fairly 14:54.960 --> 15:05.200 easy. Um, this is the QR code to the, to our new website. And if we have some time left, I can just 15:05.200 --> 15:12.240 let some slideshow roll in the background. Um, and questions. If there's any, if we still have time, 15:12.240 --> 15:21.200 I don't think we do, but. So, this is just some random, yeah, this looks great. Um, some random 15:21.200 --> 15:27.360 pictures from the, the, the, the trips. So, questions, comments, tomatoes. 15:51.600 --> 16:04.640 Um, don't think so. I mean, there's people that I know there's people in this room who were on a 16:04.640 --> 16:11.520 hacker train who would be able to do that, but at least when we originally pitched the idea, 16:12.160 --> 16:17.200 we had, we didn't document that on the website yet, but when we originally pitched the idea, 16:17.280 --> 16:20.880 we already said, training for structures of limits. 16:27.760 --> 16:33.360 Yeah, no, no, it was, we, we also decided that the penalty would be will throw you off the train, 16:33.360 --> 16:38.400 the moment we learn about it. We don't care where that place is to your problem. 16:47.680 --> 16:50.720 Not this year. 16:57.280 --> 17:03.280 Yeah, yeah, yeah, I mean, I, I mean, I, as I, again, I was on one of the more lucky lines, 17:04.240 --> 17:12.160 but I think like some people, you know, that the, the unlucky lines had like the 20, 30 people 17:12.240 --> 17:17.280 attached to them that were not the had no clue of the hacker train before they started relying on 17:17.280 --> 17:22.800 people who knew about it. Um, I think those, some of, I've heard from some of those people that 17:22.800 --> 17:28.320 they had like stories, how people went, you know, all different routes to try to get to place 17:28.320 --> 17:33.680 and then he went somewhere and went back and then they all ended up on the same train and, you know, 17:33.680 --> 17:36.640 four hours afterwards, they met on the same train again. 17:43.120 --> 17:46.640 It says something about how you do great, so I'm going to make it easy for the population 17:46.640 --> 17:50.880 of what to do in case the late issues. I would say this is so complex that there's like a huge 17:50.880 --> 17:55.600 blow chart in line so I'm going to think, like, not necessarily out of what the house 17:55.600 --> 18:01.680 is going on. So I don't think it's simple to throw it all this. I mean, even that, I mean, 18:01.680 --> 18:07.200 in, in the case that we were in the past few days, having that flow chart, I'm pretty sure, 18:07.200 --> 18:10.800 like some of the people in the room would have loved to know that there is this flow chart 18:10.800 --> 18:17.120 and have a direct link to it. So just, if you have a flow chart, please send it to us and we'll 18:17.120 --> 18:21.280 put it on the link on the website for future reference. 18:23.280 --> 18:30.240 Yeah, to, to, on the, when we aligned that our locomotive was broken, we even tried calling 18:30.240 --> 18:36.720 the company that I'm still a locomotive, which is not European-slipper and, like, yeah, it was 18:36.720 --> 18:43.840 a huge last traffic in Tostan, which also ties into the questioner. So would we do this again 18:43.840 --> 18:48.080 and how was it? It's like, yeah, it was a cluster fuck, but I think, like, everybody, 18:48.080 --> 18:54.480 like, including the unfortunate Diplodocos line, when they finally arrived, they were like, 18:54.480 --> 18:59.360 I'm so fucking tired, but this was pretty nice. 19:07.360 --> 19:15.600 Right, yes, but still, you know, traveling alone, plus cluster fuck is not fun, but now only, 19:15.600 --> 19:22.640 now we actually have a nice story, not just paying, right. There's another question if we have time, 19:22.640 --> 19:30.800 but okay. So thank everyone for sending time for the last today. Hope you have a good time. 19:30.800 --> 19:40.560 I think there will be some, thank you. Thank you to all the others who helped with this. So it's up to 19:40.560 --> 19:49.600 anything.