WEBVTT 00:00:19.350 --> 00:00:23.510 Herald: Hello and welcome to Infrastructure Review. This review is 00:00:23.510 --> 00:00:28.080 being translated into a lot of languages and we don't know yet which one, but the 00:00:28.080 --> 00:00:35.020 c3lingo team will be on stage and will tell us how and what it did. I'd like to 00:00:35.020 --> 00:00:42.340 start, as always and every year, with the NOC, right. So please give the NOC a hand. 00:00:42.340 --> 00:00:48.130 *applause* [Filler, please remove me in amara] 00:00:48.130 --> 00:00:54.810 Momo: All right, everyone, welcome to the State of the Internet manufacture report. 00:00:54.810 --> 00:00:58.850 This is JC, I'm Momo and we're going to talk to you about what we did this year 00:00:58.850 --> 00:01:05.730 for the network. So obviously, organizing Congress is a quite tedious task. Took us 00:01:05.730 --> 00:01:10.110 about six months of pre-planning. We came in on the 15th, did a fiber day and then 00:01:10.110 --> 00:01:14.500 it took us from the 18th and will take us till tomorrow to tear everything down with 00:01:14.500 --> 00:01:18.400 like 20 to 40 people. And we'll be busy wiping every device because that is 00:01:18.400 --> 00:01:21.470 actually what we do every year. We delete everything. There are no logs leaving this 00:01:21.470 --> 00:01:27.540 building and this will take us probably the next 24 hours. So yeah, for the usual 00:01:27.540 --> 00:01:31.610 numbers. Edge capacity: this year because you didn't use all the Internet last year, 00:01:31.610 --> 00:01:36.520 we only brought you 300 gigs, but that was fine as well, I suppose. We got 100 gig 00:01:36.520 --> 00:01:40.620 from HLKomm here in Leipzig, 100 gig from Deutsche Telekom and as well as 100 gig 00:01:40.620 --> 00:01:48.479 from BCIX which we got via DWDM wave to Berlin. In the core we used Juniper 00:01:48.479 --> 00:01:56.549 MX960s, MX480s, MX204s and QFX10002 in the yolocolo. Basically all the halls were 00:01:56.549 --> 00:02:02.280 connected via a 200 gig link and yolocolo had three times 100 gig. As probably the 00:02:02.280 --> 00:02:09.330 last five or so years, we're using IS-IS and BGP for our protocols of choice. And 00:02:09.330 --> 00:02:13.860 this year we also first off rejected RPKI invalid routes and secondly applied for 00:02:13.860 --> 00:02:19.890 the first time at congress BCP38 ingress filtering to be a good internet citizen 00:02:19.890 --> 00:02:26.830 and not to allow you to spoof IP addresses. So yeah, that was nice. As 00:02:26.830 --> 00:02:31.330 Congress keeps on growing, we have 2500 tables somewhere around the building in 00:02:31.330 --> 00:02:35.459 all the assemblies, but we only have 300 switches. So sorry if you had to bring a 00:02:35.459 --> 00:02:40.401 long cable and if you have switches to spare with 10 gig uplinks and POE+, feel 00:02:40.401 --> 00:02:47.530 free to donate them to us. Access and Wi- Fi. We had like 300 access switches. We 00:02:47.530 --> 00:02:51.330 are obviously again running Aruba Wi-Fi controllers. This year, like at camp we 00:02:51.330 --> 00:02:57.630 had a few 802.1x access points, more on that later. We tried to use Juniper vMX to 00:02:57.630 --> 00:03:03.000 route the Wi-Fi traffic. And had quite a shitload of switches, most of them from 00:03:03.000 --> 00:03:08.849 Juniper, some Cisco 2960s, some Brocades which are new to us, and some crappy old 00:03:08.849 --> 00:03:13.470 HPE stuff which is basically configured for us to work like a brick you get from 00:03:13.470 --> 00:03:18.610 like eBay or whatnot. We had a few incidents this year we'd like to talk 00:03:18.610 --> 00:03:23.150 about. First off, we had, I'm not sure if any of you noticed, quite a lot of packet 00:03:23.150 --> 00:03:28.560 loss and missing router advertisements on the Wi-Fi. This was caused by some weird 00:03:28.560 --> 00:03:32.780 Juniper vMX behavior. We couldn't figure out what it was. So we had them running in 00:03:32.780 --> 00:03:38.739 a redundant VRRP setup. We shut down one of them and then it worked. So yeah, fuck 00:03:38.739 --> 00:03:45.239 redundancy. There was a pixelflut client which somehow messed up his IP address and 00:03:45.239 --> 00:03:52.650 caused a broadcast storm which took down most parts of Hall 2. We found them, shut 00:03:52.650 --> 00:03:59.671 it down and deployed storm control to all our access switches. Yeah, to the Congress 00:03:59.671 --> 00:04:06.120 motto resource exhaustion: someone was running aggressive zmap scanning over the 00:04:06.120 --> 00:04:10.989 whole internet, came by our Wi-Fi access controller and caused a state table 00:04:10.989 --> 00:04:15.620 exhaustion. And that brought it down. We null-routed the source and yeah, there was 00:04:15.620 --> 00:04:23.990 this issue. So thank you to whoever was that. And in the morning of day 3, we had 00:04:23.990 --> 00:04:27.890 another issue with Juniper vMX where it forgot it had a network card. We rebooted 00:04:27.890 --> 00:04:33.139 it and everything was fine again. So yeah, some numbers. You actually managed to use 00:04:33.139 --> 00:04:39.340 more bandwidth, thank you. [Filler, please remove me in amara] 00:04:39.340 --> 00:04:43.380 *applause* [Filler, please remove me in amara] 00:04:43.380 --> 00:04:47.830 M: But it's still only 20% of our uplink capacity. So use more. 20% of that was 00:04:47.830 --> 00:04:53.650 IPv6, which is good, but could be more. We had like 11000 clients into Wi-Fi. 86% 5 00:04:53.650 --> 00:05:02.240 GHz, 96% in a peak. We had eleven 802.11ax clients. Our 00:05:02.240 --> 00:05:09.240 favorite one was obviously the one with the lovely hostname ILOVETHENOC. So yeah, 00:05:09.240 --> 00:05:14.919 about that number we have, 96% 5 GHz obviously shows us that we are finally at 00:05:14.919 --> 00:05:20.440 the point where we can say: thank you 2.4 GHz, it was nice. Goodbye. 00:05:20.440 --> 00:05:24.919 *applause* [Filler, please remove me in amara] 00:05:24.919 --> 00:05:32.240 M: Also, obviously, thank you to our sponsors. We couldn't do this if we would 00:05:32.240 --> 00:05:37.110 not get like 10 millions, of list price obviously, of equipment and loan and quite 00:05:37.110 --> 00:05:40.350 a lot of services. So give them a round of applause as well. Thank you. 00:05:40.350 --> 00:05:46.389 *applause* [Filler, please remove me in amara] 00:05:46.389 --> 00:05:50.889 M: And obviously NOC not only stands for Network Operation Center, but if you 00:05:50.889 --> 00:05:55.870 extend it, it is No CO2. So we believe in green power and clean traffic and 00:05:55.870 --> 00:06:01.039 therefore we obviously see that sustainability is a great part of our 00:06:01.039 --> 00:06:05.420 role. This is why we even use old crappy HP switches to cut our lines for our 00:06:05.420 --> 00:06:07.919 tchunk to serve your cheese boards, whatever you need. 00:06:07.919 --> 00:06:10.400 *laughter* [Filler, please remove me in amara] 00:06:10.400 --> 00:06:13.240 M: Also... [Filler, please remove me in amara] 00:06:13.240 --> 00:06:15.729 *applause* [Filler, please remove me in amara] 00:06:15.729 --> 00:06:21.270 M: Also, we somehow estimated what our network will run us in CO2 and that was 00:06:21.270 --> 00:06:26.229 about 11 tons. We're not very good with mass and not very good with CO2 emissions, 00:06:26.229 --> 00:06:31.410 but this was roughly what we came up with. And to make Congress or the world a bit 00:06:31.410 --> 00:06:40.970 better place, we actually offset all our CO2 and bought eleven tons of CO2 00:06:40.970 --> 00:06:49.419 emissions. And now Frederick is gonna tell you how we got all those numbers. 00:06:49.419 --> 00:06:54.849 Frederick: Yeah, as a good internet manufacture, we also do monitoring a lot 00:06:54.849 --> 00:07:00.069 and we run our own Prometheus server inside. You probably know the dashboard 00:07:00.069 --> 00:07:06.300 that we propagate all over the internet and that's powered by Prometheus. We have 00:07:06.300 --> 00:07:12.250 an internal Grafana that is part of this whole ecosystem. And if you are a little 00:07:12.250 --> 00:07:16.000 bit of a nerd, you might have clicked on the dashboard sections and seen that there 00:07:16.000 --> 00:07:23.420 are more dashboards than this. We fill our Prometheus with lots of different sources: 00:07:23.420 --> 00:07:30.080 we get SNMP data from, and screw SNMP, but it does a quite good job at getting all 00:07:30.080 --> 00:07:34.740 the insights we need from all the network equipment. We have node_exporter, influx 00:07:34.740 --> 00:07:40.650 and all that, but we got a decent amount of data from everyone in the Congress 00:07:40.650 --> 00:07:45.699 ecosystem and we had that at camp as well where we got the water pressure of the 00:07:45.699 --> 00:07:52.169 showers. And we get the colo power, which also helps with estimating the CO2 00:07:52.169 --> 00:07:58.190 footprint. And everything is being configured by Netbox, which is a tool that 00:07:58.190 --> 00:08:06.139 is an asset database. And as I said, we have lots of dashboards and graphs. Of 00:08:06.139 --> 00:08:09.660 course, the public one where you can see lots of different things from everyone. 00:08:09.660 --> 00:08:15.950 This is only part of it. If you scroll down on the dashboard, you see a lot more. 00:08:15.950 --> 00:08:19.319 But this helps everyone to have a good understanding of what is happening 00:08:19.319 --> 00:08:23.669 currently. And we even draw a nice little Christmas trees on the Wi-Fi traffic for 00:08:23.669 --> 00:08:28.270 you. That is mostly because it's a router- on-a-stick and we cannot measure it 00:08:28.270 --> 00:08:32.570 correctly. We have an internal dashboard which gives us a little bit of a status 00:08:32.570 --> 00:08:40.120 for build-up mostly: which switches and routers are up? And that gives us a very 00:08:40.120 --> 00:08:45.620 quick sight of all the devices that are out there. What's broken? What's not 00:08:45.620 --> 00:08:50.070 broken? We improved it a little and now have alarms so someone can look at stuff 00:08:50.070 --> 00:08:58.540 and see if things are broken, run out there and fix it. We also built 00:08:58.540 --> 00:09:03.850 weathermaps. As you can see that's a little bit of a mess. But we couldn't do 00:09:03.850 --> 00:09:11.459 it better because the graphing library doesn't allow us to do it better. If 00:09:11.459 --> 00:09:16.029 someone has a good idea to do it better in Grafana or anywhere else with sources from 00:09:16.029 --> 00:09:21.370 Prometheus, please come to us, we're happy to talk. But this shows our core and all 00:09:21.370 --> 00:09:26.399 the links between it and how much capacity is being used. Red indicates that it's 00:09:26.399 --> 00:09:32.980 used more heavily. We also have that for the yolocolo. And all the traffic around 00:09:32.980 --> 00:09:41.149 it as well. And, yeah, teardown starts now. Please don't touch our equipment. And 00:09:41.149 --> 00:09:45.709 if you want to come and help, please come to Hall 4 and get in touch. We always need 00:09:45.709 --> 00:09:50.089 helping hands. But please in an organized way don't disassemble switches or access 00:09:50.089 --> 00:09:56.220 points. We have lists and everything. We need to account for everything. So please 00:09:56.220 --> 00:09:59.970 come to Hall 4 if you want to help. And yes, use more bandwidth and offset more 00:09:59.970 --> 00:10:03.930 CO2. Thank you. [Filler, please remove me in amara] 00:10:03.930 --> 00:10:06.029 *applause* [Filler, please remove me in amara] 00:10:06.029 --> 00:10:11.399 H: So thanks a lot. Actually, because you're clearly the backbone or one of 00:10:11.399 --> 00:10:15.950 those many backbones of the conference, is there any Q? Let's do a Q&A for like one 00:10:15.950 --> 00:10:18.769 or two questions. Is anyone having a question right now? 00:10:18.769 --> 00:10:23.390 Someone is standing up. Right, microphone number one, please. 00:10:23.390 --> 00:10:26.930 Q: Hey, we've absolutely don't ... [Filler, please remove me in amara] 00:10:26.930 --> 00:10:28.930 H: Nearer, nearer. [Filler, please remove me in amara] 00:10:28.930 --> 00:10:33.670 Q: We've absolutely done bcp38 in previous years, by the way. 00:10:33.670 --> 00:10:37.730 M: Sorry for what I said then, I'm sorry. Q: So I wanted to correct the record. 00:10:37.730 --> 00:10:40.920 We've been good netizens in previous years as well. 00:10:40.920 --> 00:10:46.399 H: Oh, you're right. Thank you. Was there another question or something else to 00:10:46.399 --> 00:10:49.020 correct them? Because they clearly don't know what they're doing. 00:10:49.020 --> 00:10:50.830 *laughter* [Filler, please remove me in amara] 00:10:50.830 --> 00:10:57.010 H: Yeah. Feel free. Microphone number two. Q: So if 2.4GHz is over, what's going to 00:10:57.010 --> 00:11:02.450 happen to all of the ESP32 in various IoT devices? Are they going to have a home 00:11:02.450 --> 00:11:06.260 here next year? M: They'll definitely have a home. But as 00:11:06.260 --> 00:11:09.390 usual, we cannot support it as good as we can on 5GHz because obviously this band is 00:11:09.390 --> 00:11:17.860 overused and not even remotely suited for that amount of clients we put on it. 00:11:17.860 --> 00:11:24.820 Q: A follow-up for the ESP32. How exactly can you locate them through the wireless 00:11:24.820 --> 00:11:31.150 if they are lost? M: Well, we can't. We can basically look 00:11:31.150 --> 00:11:34.820 at which access point they are, and then if someone really would want to, we could 00:11:34.820 --> 00:11:38.610 start triangulation, but we've never done that before. So yeah, we can just pin them 00:11:38.610 --> 00:11:46.120 roughly to an access point. H: Maybe we can ask c3nav next time. So 00:11:46.120 --> 00:11:49.560 please give the NOC a hand. Thank you. 00:11:49.560 --> 00:11:52.389 *applause* [Filler, please remove me in amara] 00:11:52.389 --> 00:11:59.639 H: So, the next team up is the POC. Do we have to click this? Use more bandwidth, 00:11:59.639 --> 00:12:04.770 I'm going to try. Ah! Thank you. Your stage. 00:12:04.770 --> 00:12:07.990 Garvin: Thanks. [Filler, please remove me in amara] 00:12:07.990 --> 00:12:11.590 *applause* [Filler, please remove me in amara] 00:12:11.590 --> 00:12:14.060 Maria: Hi, my name is Maria. [Filler, please remove me in amara] 00:12:14.060 --> 00:12:17.950 G: Hi, and I'm Garvin and we're from Phone Operation Center and we want to talk a bit 00:12:17.950 --> 00:12:20.850 about the phone infrastructure at this event. 00:12:20.850 --> 00:12:27.420 M: Yeah. So we arrived at day -6 and planned on hacking some things 00:12:27.420 --> 00:12:34.100 and socializing and we planned a team event, but then everything was different. 00:12:34.100 --> 00:12:40.079 G: Yeah. When we arrived, I went into the NOC office and they said to me, "Ja, CCL 00:12:40.079 --> 00:12:44.490 is up, internet is up, everything is just working nicely. You can start hook up your 00:12:44.490 --> 00:12:51.050 telephony system right now." And I was like, whoa. So thanks a lot NOC. Really 00:12:51.050 --> 00:12:54.810 great performance this year, we were amazed. Nobody expected that it works so 00:12:54.810 --> 00:12:57.970 well. [Filler, please remove me in amara] 00:12:57.970 --> 00:13:01.140 *applause* [Filler, please remove me in amara] 00:13:01.140 --> 00:13:06.399 M: Yeah. So we put up the first antennas and then we decided to have our team event 00:13:06.399 --> 00:13:16.399 anyway. And yeah, so we did a lot of things. So we handed out 150 orga loan 00:13:16.399 --> 00:13:26.621 DECTs and we deployed 51 SIP telephones. We also deployed 67 antennas and we had a 00:13:26.621 --> 00:13:32.690 POC party on day three until 7:30 a.m. G: So you can see almost everything is 00:13:32.690 --> 00:13:40.170 done. I guess the remaining things are not that important. So this is the overview of 00:13:40.170 --> 00:13:45.459 DECT coverage at the event. Only level zero, because otherwise I think it would 00:13:45.459 --> 00:13:50.839 be overcrowded to show. Just so that you can get a rough impression on how many 00:13:50.839 --> 00:13:55.650 antennas we deployed in order to give you this DECT coverage. That you can be 00:13:55.650 --> 00:14:00.130 reached almost everywhere in the event and that you can see how our tooling looks 00:14:00.130 --> 00:14:04.460 like, where we see how good the antennas see each other, and that we can see that 00:14:04.460 --> 00:14:10.279 seamless handover work so that you can start at our desk, walk through the area, 00:14:10.279 --> 00:14:16.380 into the lounge and just continue talking. And oh, there are also some antennas that 00:14:16.380 --> 00:14:19.930 are outside of the building. What could that be? 00:14:19.930 --> 00:14:25.759 M: That is our hotel DECT. And you can see a typical hotel DECT installation on the 00:14:25.759 --> 00:14:32.250 photo. And people got really confused about it because we also had DECT coverage 00:14:32.250 --> 00:14:37.230 at main station. G: Yeah. So I got a call roughly at 4:00 00:14:37.230 --> 00:14:39.230 p.m. in the morning. [Filler, please remove me in amara] 00:14:39.230 --> 00:14:43.589 *applause* [Filler, please remove me in amara] 00:14:43.589 --> 00:14:50.150 G: And somebody told me. Oh, my DECT rang. Why? Now I need to turn it off at the 00:14:50.150 --> 00:14:57.720 night. Why did you do this? M: Yeah. So we also had problems. We have 00:14:57.720 --> 00:15:04.190 a new feature since Camp where you can see your DECT devices and can assign them to 00:15:04.190 --> 00:15:07.680 your number before you even arrive, and then everything is set up and you don't 00:15:07.680 --> 00:15:12.450 have to call your token anymore. And people get really confused because they 00:15:12.450 --> 00:15:17.920 would call their token anyway and it calls it invalid. So we had to explain a lot of 00:15:17.920 --> 00:15:26.680 this unexpected simplicity to them. G: And then we had a battery issue this 00:15:26.680 --> 00:15:31.870 year. We had not enough batteries and, you know, batteries are always empty in the 00:15:31.870 --> 00:15:37.010 phones when it's the most important. So we were thinking what what can we do about 00:15:37.010 --> 00:15:41.070 that? M: So we build a new device. That's our 00:15:41.070 --> 00:15:49.640 microwave and it can also charge devices. So, many thanks to C3Power, because they 00:15:49.640 --> 00:15:55.050 helped us with tooling and actually they have expertise to put power cables on 00:15:55.050 --> 00:16:04.002 devices like this. Thank you very much. [Filler, please remove me in amara] 00:16:04.002 --> 00:16:05.002 *applause* [Filler, please remove me in amara] 00:16:05.002 --> 00:16:08.810 G: In the last years we were often asked "how expensive is your service actually?". 00:16:08.810 --> 00:16:13.449 So we decided that we now provide invoices so you can see how expensive our services 00:16:13.449 --> 00:16:21.579 are and we send out a lot of invoices. And we got paid some money. But as you can see 00:16:21.579 --> 00:16:28.329 on the invoices, most is sponsored by CCC. M: Yeah. And people also paid with Mate 00:16:28.329 --> 00:16:34.560 which is really awesome. G: Yeah. And also people have invoices on 00:16:34.560 --> 00:16:39.230 a fraction of a cent and they got quite creative on how they can pay us. 00:16:39.230 --> 00:16:46.460 *laughter* [Filler, please remove me in amara] 00:16:46.460 --> 00:16:51.930 *applause* [Filler, please remove me in amara] 00:16:51.930 --> 00:16:54.569 M: So here are some more stats. We have 7473 registered extensions. 00:16:54.569 --> 00:16:58.290 G: Oh, we didn't remove this. So we were thinking on how to compare this with 00:16:58.290 --> 00:17:02.779 things and we were looking at villages in Saarland and then we thought, this is a 00:17:02.779 --> 00:17:05.959 stupid comparison, but we didn't remove this. 00:17:05.959 --> 00:17:17.199 M: So there were 5021 attached DECT phones and 3251 concurrent DECT phones. Which is 00:17:17.199 --> 00:17:21.920 about more than 1000 more than last year. G: So thanks a lot for using DECT. 00:17:21.920 --> 00:17:25.390 M: Yeah. We had... [Filler, please remove me in amara] 00:17:25.390 --> 00:17:27.309 *applause* [Filler, please remove me in amara] 00:17:27.309 --> 00:17:36.150 M: There were also max 120 calls in parallel, and we had more than 300 00:17:36.150 --> 00:17:43.890 thousand calls in total. That's also really, really much. We had five eating 00:17:43.890 --> 00:17:52.900 meetings at heaven, the angel eating place, and there were an average of 42 00:17:52.900 --> 00:18:01.270 eating meeting live viewers. We had two lectures. You can see them on media.ccc.de 00:18:01.270 --> 00:18:05.490 and we had 23 super fast charged phones in our microwave. 00:18:05.490 --> 00:18:11.930 *applause* [Filler, please remove me in amara] 00:18:11.930 --> 00:18:17.580 G: Like the NOC, we also had to deal a bit with issues during the event, and actually 00:18:17.580 --> 00:18:24.870 there were some DDOS attack on our account system and somebody configured over 4000 00:18:24.870 --> 00:18:29.130 extensions with really stupid names. And it took us quite a while to get rid of 00:18:29.130 --> 00:18:33.210 them again cleanly from the system because the synchronization turned out to be 00:18:33.210 --> 00:18:39.660 really slow. So you can see it took us a while to get them removed again. So we can 00:18:39.660 --> 00:18:44.330 only say, you all know it's a hacker congress, but it's kind of stupid to hack 00:18:44.330 --> 00:18:48.620 your own infrastructure. [Filler, please remove me in amara] 00:18:48.620 --> 00:18:51.850 *applause* [Filler, please remove me in amara] 00:18:51.850 --> 00:18:58.480 G: So as a consequence of this, we only allow now only 50 extensions per account 00:18:58.480 --> 00:19:03.040 and per event. If you think you need more, feel free to contact us if you have a 00:19:03.040 --> 00:19:06.530 valid use case. [Filler, please remove me in amara] 00:19:06.530 --> 00:19:12.640 M: So every device has an IPEI that is like a MAC address and we ask the 00:19:12.640 --> 00:19:19.090 responsible institution to give us the manufacturer. But it's really secret. So 00:19:19.090 --> 00:19:23.240 they don't give it to us. So we ask you for help. Please enter the models of your 00:19:23.240 --> 00:19:29.260 devices for your phones. And then we can match to the IPEI and get some data to 00:19:29.260 --> 00:19:32.990 build more awesome features for you. [Filler, please remove me in amara] 00:19:32.990 --> 00:19:37.391 G: This would really help us. And the only way for us is to crowdsource it because it 00:19:37.391 --> 00:19:40.650 seems to be super secret. Whatever. [Filler, please remove me in amara] 00:19:40.650 --> 00:19:45.570 M: You can find it in guru3 on the device page and there's this little pen. And if 00:19:45.570 --> 00:19:49.350 you click on it, then you can enter the model. 00:19:49.350 --> 00:19:57.610 G: Thanks upfront. And yep, that's from us, and I guess now we have a little time 00:19:57.610 --> 00:20:01.500 for you to ask questions. [Filler, please remove me in amara] 00:20:01.500 --> 00:20:04.909 *applause* [Filler, please remove me in amara] 00:20:04.909 --> 00:20:13.880 H: Great. So, any questions for the POC? I don't see... were they correct or do we 00:20:13.880 --> 00:20:20.240 have to...? Ah, someone is getting up. So microphone number 1, please. 00:20:20.240 --> 00:20:25.150 Q: Yes, a few years ago there was a translation service via DECT. Is the 00:20:25.150 --> 00:20:29.830 capacity enough to service also this crowd? 00:20:29.830 --> 00:20:36.560 G: The problem is that we switched the phone system a while ago last year at the 00:20:36.560 --> 00:20:43.820 Congress. And the old phone system had a way how we can do the translation via one 00:20:43.820 --> 00:20:48.510 channel and the problem is that the new system doesn't support this. Let me say 00:20:48.510 --> 00:20:55.120 the new system doesn't support it yet. So have a look at our talk and then you can 00:20:55.120 --> 00:21:01.690 see that there is some potential. H: I see someone at microphone number 3, 00:21:01.690 --> 00:21:05.140 please. This would be the last question because we have to hurry a bit. 00:21:05.140 --> 00:21:10.080 Q: Can I know a little bit more about the super charging microwave? I'm confused. 00:21:10.080 --> 00:21:14.330 *applause* [Filler, please remove me in amara] 00:21:14.330 --> 00:21:20.550 M: Sure, you can come to our POC desk and then we answer all your questions. 00:21:20.550 --> 00:21:28.780 H: Ooh... mystery. Please, give the POC a hand. 00:21:28.780 --> 00:21:39.940 So next team, is it from the GSM crew? Someone there? I think we have two. I see 00:21:39.940 --> 00:21:44.919 some Chaos Post, you have to wait one round. So, GSM guy thank you. I am good 00:21:44.919 --> 00:21:53.500 with computers, I think. Yeah, I am. Have fun. If it's working or not. Look at this 00:21:53.500 --> 00:22:03.679 smile then looks better. Try this. Yeah. Right. Try this. 00:22:03.679 --> 00:22:09.849 - 423. - Maybe you have to use GSM. 00:22:09.849 --> 00:22:13.599 - 23 test. - What happened? 00:22:13.599 --> 00:22:16.599 - Hello. Hello. - Aah. 00:22:16.599 --> 00:22:24.630 GSM Person 1: So as every year we ran our own mobile phone network at the Congress 00:22:24.630 --> 00:22:32.620 using osmocom open source software for 2G and 3G, and open5gs interfacing with the 00:22:32.620 --> 00:22:37.909 osmocom HLR. And all you need to take part is a SIM card that you can buy from the 00:22:37.909 --> 00:22:47.250 POC and for 5 euros you get a flat rate. The price increases because we have less 00:22:47.250 --> 00:22:53.150 SIM cards every year. We need to manufacture new ones. You can even call 00:22:53.150 --> 00:23:02.830 outside like you can with DECT phones. Lynxis: Hello. I'm Lynxis. So as every 00:23:02.830 --> 00:23:09.450 year for the GSM team, the first problem is the license. That's the first step 00:23:09.450 --> 00:23:16.539 usually. Because in Germany, you have to get the official form, get a license but 00:23:16.539 --> 00:23:22.510 ... Where do you get it? What can you ask for frequencies? Because, for example, the 00:23:22.510 --> 00:23:28.940 POC for DECT or Wi-Fi, you just place it and you can use it. You're fine. 00:23:28.940 --> 00:23:35.480 But for GSM, they didn't think about it or for 3G or 4G. So yeah, this year we 00:23:35.480 --> 00:23:41.520 usually get the license middle of december, maybe start of december. So it's 00:23:41.520 --> 00:23:51.380 already late. So this year we didn't get all our licenses. But we get some. We got 00:23:51.380 --> 00:23:59.409 850 MHz, which is not assigned in Europe because it's usually in the US only. But 00:23:59.409 --> 00:24:06.760 we have a small hole. This year we got a 4G license instead of a 2G license with 10 00:24:06.760 --> 00:24:11.640 Mhz from Telefonica. So thanks Telefonica for borrowing us spectrum. 00:24:11.640 --> 00:24:18.780 *applause* [Filler, please remove me in amara] 00:24:18.780 --> 00:24:24.080 L: Just a short example of how the spectrum looks like. The yellow stuff is 00:24:24.080 --> 00:24:31.830 usually somewhere behind actually. By the way, this microphone, it might share the 00:24:31.830 --> 00:24:36.450 same frequency with us. But so far, we haven't found any interference together 00:24:36.450 --> 00:24:45.770 with the VOC. Down there you can see the small hole which we are using. Because we 00:24:45.770 --> 00:24:51.850 didn't get the 2G license there, we thought, OK. Let's take a look. Can we fit 00:24:51.850 --> 00:24:56.919 them both in the same frequencies? It's not good. But you see the spikes, this 00:24:56.919 --> 00:25:03.880 nice antenna on the right. That's the GSM, which is sending on the same frequency. It 00:25:03.880 --> 00:25:07.250 works because they are using different codings. But I have heard from people who 00:25:07.250 --> 00:25:10.039 know more about it, this is not the way you use it. 00:25:10.039 --> 00:25:13.289 *laughing* [Filler, please remove me in amara] 00:25:13.289 --> 00:25:17.830 L: So we took some photos of our base stations. This is actually the fairy dust 00:25:17.830 --> 00:25:23.909 from the 2G base station, so we have a idea what we are using here. We have even 00:25:23.909 --> 00:25:31.200 more fairy dust in our 3G femtocells and our 4G cells. They are looking like small 00:25:31.200 --> 00:25:37.600 toasters. They are taking actually 90 watts via POE, they have special POE 00:25:37.600 --> 00:25:44.740 adapters. So maybe we could ask if somebody can do a similar adapter to get 00:25:44.740 --> 00:25:52.770 even running a toaster on the line. So basically for the 4G setup this year, 00:25:52.770 --> 00:25:57.830 we weren't sure if it's stable enough or we lose all our phones to the LTE and they 00:25:57.830 --> 00:26:05.960 don't like to come back to the 2G and 3G setup where we have voice, because on LTE 00:26:05.960 --> 00:26:10.590 we don't have yet voice so you have to select specifically to join the LTE 00:26:10.590 --> 00:26:16.919 network. That worked quite fine if you change it. So your phone will register. 00:26:16.919 --> 00:26:24.299 Everything fine there. GSM1: So the rollout this year: we had the 00:26:24.299 --> 00:26:30.690 voice working on day 0 which is new. [Filler, please remove me in amara] 00:26:30.690 --> 00:26:34.710 *applause* [Filler, please remove me in amara] 00:26:34.710 --> 00:26:41.760 GSM1: Someone even noticed on Mastodon, I saw it, too. We already had LTE at the CCC 00:26:41.760 --> 00:26:48.441 camp this year. Yeah, but unfortunately we lost crypto password, so LTE roll out took 00:26:48.441 --> 00:26:59.860 a bit longer this time. Sorry. So some numbers. In total we saw just about 1100 00:26:59.860 --> 00:27:06.490 people doing a location updating on our network and 845 eventphone tokens were 00:27:06.490 --> 00:27:15.620 dialed on the GSM. That is 2G or 3G. And there were roughly 200 phones actively 00:27:15.620 --> 00:27:21.110 subscribed on the network at all times. And even though we basically only deployed 00:27:21.110 --> 00:27:29.240 3G nano stations in all the halls and only had two 2G BTS in the glass halle, there 00:27:29.240 --> 00:27:35.390 were roughly more than half of all the phones were still subscribed on 2G instead 00:27:35.390 --> 00:27:43.169 of 3G. We had like 18 3G stations and only two plus one in the GSM room 2G stations. 00:27:43.169 --> 00:27:50.799 So that's a bit surprising. And SIM cards: starting from the bottom, we sold about 00:27:50.799 --> 00:27:56.909 700 SIM cards, but only saw half of them activated, which is curious. And luckily, 00:27:56.909 --> 00:28:02.320 most or some people bring old SIM cards from previous years. And it's not so easy 00:28:02.320 --> 00:28:07.640 to get cards manufactured. So we are very glad for everyone who brings old SIM cards 00:28:07.640 --> 00:28:14.460 from previous events. We might even consider introducing charging phone calls 00:28:14.460 --> 00:28:18.890 only for SIM cards that are newly bought. So if you want to continue calling for 00:28:18.890 --> 00:28:22.950 free, rather bring your old SIM cards. [Filler, please remove me in amara] 00:28:22.950 --> 00:28:25.350 *applause* [Filler, please remove me in amara] 00:28:25.350 --> 00:28:31.190 GSM1: So you see the numbers, I'm not going to go through them. And you can also 00:28:31.190 --> 00:28:40.130 get the ADM, the admin keys for your SIM cards if you like to write to them. 00:28:40.130 --> 00:28:46.850 L: Or if you have seen the talk from LaForge, you might want to play with the 00:28:46.850 --> 00:28:53.140 SIM cards, we give out all the keys you want to have to play with it. 00:28:53.140 --> 00:29:02.640 GSM1: So operation was mostly smooth, except iPhones, for unknown reasons. And 00:29:02.640 --> 00:29:06.401 except the data service, which might even be related because maybe Apple is a bit 00:29:06.401 --> 00:29:12.150 more strict on whether data service is working reliably. Yeah, we still had some 00:29:12.150 --> 00:29:18.360 problems in the SGs instance introducing 3G changing between the radio access 00:29:18.360 --> 00:29:25.559 technologies. It's a whole new ballgame so there are still some bugs in there. And as 00:29:25.559 --> 00:29:30.480 you see, we had many more tickets than the POC. This is actually reversed from the 00:29:30.480 --> 00:29:37.330 POC, the "done" is on the left. So this whole bunch of stuff is done and there's 00:29:37.330 --> 00:29:45.010 some backlog and canceled and fantasy tasks. It worked pretty nicely. Are you 00:29:45.010 --> 00:29:50.799 taking over? Oh, yeah, no, this is still mine. And this year we actually had also a 00:29:50.799 --> 00:29:56.519 denial of service attack. The code was the same as previous years and we never saw 00:29:56.519 --> 00:30:01.770 this before. But this year we got an invalid mobile identity which managed to 00:30:01.770 --> 00:30:06.429 crash our mobile switching center. And thank you very much for uncovering this 00:30:06.429 --> 00:30:12.669 bug and thanks to fixeria for fixing it on day 2. Ever since the mobile switching 00:30:12.669 --> 00:30:19.820 center for Voice and SMS and subscription has been running stable. 00:30:19.820 --> 00:30:30.899 *applause* [Filler, please remove me in amara] 00:30:30.899 --> 00:30:38.120 L: Maybe some interference. We recovered the old phones again. Last year we 00:30:38.120 --> 00:30:41.500 couldn't support them. But we managed to implement the missing parts. Old phones 00:30:41.500 --> 00:30:46.360 could work if they support the frequencies. So that's really nice. Maybe 00:30:46.360 --> 00:30:54.880 next time. Since camp, we also did a nice angel helpdesk. And it was really 00:30:54.880 --> 00:31:00.000 impressive to see that we even had to add more shifts in our shifts. We had so many 00:31:00.000 --> 00:31:06.000 motivated angels. Thanks to everybody who helped us, it was really great. 00:31:06.000 --> 00:31:12.420 *applause* [Filler, please remove me in amara] 00:31:12.420 --> 00:31:18.330 H: Unfortunately, we don't have enough time for a Q&A. So please give them a hand 00:31:18.330 --> 00:31:20.340 for everything they did. [Filler, please remove me in amara] 00:31:20.340 --> 00:31:21.420 *applause* [Filler, please remove me in amara] 00:31:21.420 --> 00:31:32.039 H: Thank you. There are quite a lot of teams next. I count at least like eight, 00:31:32.039 --> 00:31:39.940 maybe nine. So we need to speed up a bit. Our next team for now will be... We don't 00:31:39.940 --> 00:31:42.840 have working microphones. Chaos post 1: Sorry, we need to interrupt 00:31:42.840 --> 00:31:46.840 you anyway. H: OK. So tell them, chaos post! Chaos 00:31:46.840 --> 00:31:48.840 post! [Filler, please remove me in amara] 00:31:48.840 --> 00:31:49.840 *applause* [Filler, please remove me in amara] 00:31:49.840 --> 00:31:54.590 Chaos post 1: Sorry, guys, we interrupt... [Filler, please remove me in amara] 00:31:54.590 --> 00:31:59.149 H: Let's get rid of the broken one because it's not working anyway. 00:31:59.149 --> 00:32:03.820 Chaos post 1: All right. Sorry, we are interrupting for a few minutes only. We 00:32:03.820 --> 00:32:07.290 would like to deliver a few statistics as well. So thanks of all, we had multiple 00:32:07.290 --> 00:32:14.070 chaos deliverers working throughout the whole Congress 24/7 basically, delivering 00:32:14.070 --> 00:32:18.710 at the speed of chaos, as our mission statement clearly states. So thank you 00:32:18.710 --> 00:32:21.549 therefore, first of all thank you very much to all of you who contributed to 00:32:21.549 --> 00:32:24.149 that. [Filler, please remove me in amara] 00:32:24.149 --> 00:32:26.750 *applause* [Filler, please remove me in amara] 00:32:26.750 --> 00:32:31.770 Chaos post 2: So let's have some numbers, because you all love numbers, right? So we 00:32:31.770 --> 00:32:38.049 delivered about 3000 external postcards. So that means with like outside chaos, so 00:32:38.049 --> 00:32:44.280 to the real world or the default world, as we call it. We delivered those to over 42 00:32:44.280 --> 00:32:49.250 countries all over the world. So you guys are really good connected internationally. 00:32:49.250 --> 00:32:57.549 And also, we don't have exact numbers, but we estimate around 3500, no, 35000, 00:32:57.549 --> 00:33:07.909 internal postcards. And you also use our online office for a total of 789 times. So 00:33:07.909 --> 00:33:12.630 that is only 15 less than camp, and that was a longer event. So, hey, you guys 00:33:12.630 --> 00:33:16.200 write a lot of postcards! [Filler, please remove me in amara] 00:33:16.200 --> 00:33:19.049 *applause* [Filler, please remove me in amara] 00:33:19.049 --> 00:33:23.730 Chaos post 1: As you might already know from camp, we also do have a few special 00:33:23.730 --> 00:33:29.360 services. As already on camp, we had the serving proposal, basically a pre- 00:33:29.360 --> 00:33:34.490 assembled text, you just had to cross what you want. The postbox certification and of 00:33:34.490 --> 00:33:38.620 course, the bi-directional chaos, in Germany also known as "Einschreiben mit 00:33:38.620 --> 00:33:40.620 Rückschein". H: Wow. 00:33:40.620 --> 00:33:45.870 Chaos post 2: And this time we also offered some new services. We had like 00:33:45.870 --> 00:33:51.149 sang telegrams, gesunges Telegram in Deutsch. We had a forever alone box for 00:33:51.149 --> 00:33:56.809 people wanting to write postcards with or exchange postcards with no idea who to 00:33:56.809 --> 00:34:02.100 write it to. We had love letters, so we had some nice pre-assembled texts and also 00:34:02.100 --> 00:34:07.760 a really nice selection of perfumes for scented postcards. You could write some 00:34:07.760 --> 00:34:12.919 secret messages. We had some UV pens and also we had some, let's say call it 00:34:12.919 --> 00:34:17.679 security, or rather temper evidence, because we had some scratch off stickers 00:34:17.679 --> 00:34:23.570 for you. And also we had over 30 new postcard designs that you could use for 00:34:23.570 --> 00:34:25.570 postcards. [Filler, please remove me in amara] 00:34:25.570 --> 00:34:26.820 *applause* [Filler, please remove me in amara] 00:34:26.820 --> 00:34:30.679 Chaos post 1: Short remark for the love letters and the perfumes. Well, that was 00:34:30.679 --> 00:34:39.329 kind of not really thought through. It was a bit... it was fun sorting them out, and 00:34:39.329 --> 00:34:42.950 stamping all of that, smelling all the perfume all the time. 00:34:42.950 --> 00:34:46.419 Chaos post 2: And then brushing your hands really thoroughly because, well, that 00:34:46.419 --> 00:34:51.899 stuff gets on your hands when you do that. Chaos post 1: Also for UV pens. Just a 00:34:51.899 --> 00:34:55.280 little remark. It's not a good idea to use it for addressing and the message. 00:34:55.280 --> 00:34:57.560 *laughing* [Filler, please remove me in amara] 00:34:57.560 --> 00:35:04.099 Chaos post 1: You can take the risk. All right, then let me close up. We also 00:35:04.099 --> 00:35:08.869 supported mail this year and we had 130 letters for activists in 00:35:08.869 --> 00:35:13.220 prison, which I find really great. I think that's something we can all support. 00:35:13.220 --> 00:35:16.349 Amazing. [Filler, please remove me in amara] 00:35:16.349 --> 00:35:19.490 *applause* [Filler, please remove me in amara] 00:35:19.490 --> 00:35:25.070 So thank you all for this amazing event, and have some fun for the rest of the 00:35:25.070 --> 00:35:27.070 Congress. [Filler, please remove me in amara] 00:35:27.070 --> 00:35:29.010 *applause* [Filler, please remove me in amara] 00:35:29.010 --> 00:35:40.380 H: Chaos post! So the next team is the VOC. Yes, you can have it. Here, the VOC. 00:35:40.380 --> 00:35:45.410 We only have 20 minutes left in total for every team. So you know what to do. 00:35:45.410 --> 00:35:54.579 VOC1: Hurry up. Welcome, guys. So. Yeah. We don't have as many statistics as usual. 00:35:54.579 --> 00:36:00.570 But we have some great stories too. We'll hurry up. So this year in total, we 00:36:00.570 --> 00:36:07.790 covered 10 stages apart from the 5 stages that we do usually for Congress. We had 00:36:07.790 --> 00:36:11.950 streams from the critical decentralisation cluster, Sendezentrum, Wikipaka WG, Open 00:36:11.950 --> 00:36:20.020 Infrastructure Orbit, Chaos West. And in total, we served 255 hours and 35 minutes 00:36:20.020 --> 00:36:26.640 of total talk time. So you know what to do until the next Congress. 00:36:26.640 --> 00:36:33.500 *applause* [Filler, please remove me in amara] 00:36:33.500 --> 00:36:40.730 VOC1: And of course, sustainability was a big topic during this Congress. So part of 00:36:40.730 --> 00:36:48.720 what we have to do is stream reencoding so you can watch it with the VP5 codec or use 00:36:48.720 --> 00:36:57.950 it at lower resolution. And so far we've been using 4 Xeon-based machines and 2 00:36:57.950 --> 00:37:04.540 desktop machines. And thanks to hardware- based encoding, we now replace this with a 00:37:04.540 --> 00:37:13.130 single laptop. As you can maybe read, this is critical infrastructure now. And for 00:37:13.130 --> 00:37:18.510 all the streams, for 30 reencoding streams, we are on a 45 watt power budget 00:37:18.510 --> 00:37:32.260 now. And as an added benefit, because we also encode the master slides with 00:37:32.260 --> 00:37:36.990 hardware encoders, and hardware encoders can generally use a higher profile that 00:37:36.990 --> 00:37:45.360 allows for better quality in real time, you now get a better picture as well. So, 00:37:45.360 --> 00:37:50.990 yeah. [Filler, please remove me in amara] 00:37:50.990 --> 00:37:56.790 *applause* [Filler, please remove me in amara] 00:37:56.790 --> 00:38:04.579 VOC1: And of course, we had some minor fuckups this year. We thought the audio 00:38:04.579 --> 00:38:11.030 setup was a bit less complex. But when we checked rooms, we had buzzing everywhere. 00:38:11.030 --> 00:38:17.950 So we replaced some SDI lines with fiber and turns out buzzing goes away. Then the 00:38:17.950 --> 00:38:26.040 PA sound console had a buggy DANTE card. After you reboot them, the auxiliary out 00:38:26.040 --> 00:38:34.079 to the VOC cameras was muted. So that messed up the particular talk that has 00:38:34.079 --> 00:38:40.830 been redone today, but other than that, we are rather happy. And we figured that 3 of 00:38:40.830 --> 00:38:47.470 our audio mixers actually had broken outputs. I don't know how we did that, but 00:38:47.470 --> 00:38:51.980 it clearly shows that they've been used on one event or another during the last 00:38:51.980 --> 00:39:01.310 years, which is actually a good thing we may think. On the Wikipaka stage, we did 00:39:01.310 --> 00:39:05.570 not use Ansible because there was sort of a playground for us. But if you don't do 00:39:05.570 --> 00:39:14.390 things properly, well, then you run into edge cases with things. And yeah. So I 00:39:14.390 --> 00:39:22.410 need to hurry up. And one virtualization host suddenly started leaking memory. And 00:39:22.410 --> 00:39:26.463 so if you were affected by that during the main talk season in the evening, we are 00:39:26.463 --> 00:39:31.350 very sorry about that. Updating the kernel helped and we have no idea what happened. 00:39:31.350 --> 00:39:40.930 Yeah, and Icecast got stuck as well. And some relive... so if you want to see talks 00:39:40.930 --> 00:39:48.970 later, that may not be possible because we ran temporarily out of space. But if you 00:39:48.970 --> 00:39:54.230 watch this on media.ccc.de, and the talks were not yet released, we have relive 00:39:54.230 --> 00:39:57.990 integration, so the talks show up in media.ccc.de even though there is no 00:39:57.990 --> 00:40:03.880 proper release yet, for your convenience. And main track and assemblies are now 00:40:03.880 --> 00:40:08.820 integrated in all events, so you don't have to click through 4 separate events to 00:40:08.820 --> 00:40:15.609 find your favorite talk. And now I pass to Pat to talk about VOCTOMIX 2. 00:40:15.609 --> 00:40:23.690 Pat: Yeah. Thank you. Okay. I have now 20 seconds, I think. I made a redesign of 00:40:23.690 --> 00:40:31.220 VOCTOMIX, it's now called VOC2MIX. And Peter was doing that meme some weeks ago, 00:40:31.220 --> 00:40:37.589 because we had to switch to VOCTOMIX 2 and we wanted to try it in 2 rooms. And in the 00:40:37.589 --> 00:40:45.060 night from day 0 to 1 we decided to do it for every stage because the old solution 00:40:45.060 --> 00:40:55.640 was not working anymore. That was a little bit hot, but it worked. And, the redesign 00:40:55.640 --> 00:41:01.790 caused the new UI, complete with some new base features. We have now transitions 00:41:01.790 --> 00:41:10.390 where pictures are moving, and we have insertions for blending text into the 00:41:10.390 --> 00:41:16.780 picture and we have a new audio mixing and we are now proper A/V Sync in every case, 00:41:16.780 --> 00:41:19.760 I think. [Filler, please remove me in amara] 00:41:19.760 --> 00:41:22.740 *applause* [Filler, please remove me in amara] 00:41:22.740 --> 00:41:29.109 Pat: And some mixer angels were exploring the software and they found some bonus 00:41:29.109 --> 00:41:36.310 features like random video distortion in some cases, which I have to fix, I think. 00:41:36.310 --> 00:41:40.660 And the party mode where you click some buttons and they are clicking without any 00:41:40.660 --> 00:41:46.849 doing of the user and everything is flickering and they called it party mode. 00:41:46.849 --> 00:41:51.730 This is what the current pipeline looks like. We have now over 200 gstreamer 00:41:51.730 --> 00:41:56.480 elements doing all this stuff to get your pictures, which you are having on the 00:41:56.480 --> 00:42:03.480 stream and in the recordings. That's it. VOC1: So, of course, there were some 00:42:03.480 --> 00:42:06.230 issues. I mean VOCTOMIX2 is essentially a rewrite. 00:42:06.230 --> 00:42:11.930 H: You have to speed up a bit. Actually we are stealing time from the other teams. I 00:42:11.930 --> 00:42:17.810 might call it a quit. VOC1: OK OK OK. So... 00:42:17.810 --> 00:42:21.560 H: Pressure! VOC1: Yes, I know. But you're not making 00:42:21.560 --> 00:42:32.280 things better. So one thing to mention: we had to deploy a sweaty finger fix after 00:42:32.280 --> 00:42:39.869 the first talk started. Ok, here are your stats, read them now, read them read them 00:42:39.869 --> 00:42:44.099 read them! [Filler, please remove me in amara] 00:42:44.099 --> 00:42:45.165 *applause* [Filler, please remove me in amara] 00:42:45.165 --> 00:42:55.800 H: Please give VOC a hand. Thank you. So what's next? Oh, the Stage manager and 00:42:55.800 --> 00:43:02.920 Herald Operation Center. I'm part of it. And we have 36 heralds, every one of them 00:43:02.920 --> 00:43:07.690 very eloquent and good-looking. Then we have 70 stage managers and stage 00:43:07.690 --> 00:43:15.780 supporters. We had 150 shows on official stages and the assemblies on top of it. We 00:43:15.780 --> 00:43:20.470 have one stage fright council yet for the speakers who took care of at least six 00:43:20.470 --> 00:43:29.070 talks. And then we threw away over 100 hosting cards on day 1 only. So clearly, 00:43:29.070 --> 00:43:35.690 give a hand for the SHOC. [Filler, please remove me in amara] 00:43:35.690 --> 00:43:41.180 *applause* [Filler, please remove me in amara] 00:43:41.180 --> 00:43:45.180 H: So next, c3power. Your time. Arif: So my name is Arif Guy. I am from 00:43:45.180 --> 00:43:49.770 the power team and from the radio operation center. We make the power. We 00:43:49.770 --> 00:43:55.900 load five double trucks of shit out on Sunday 15th. We deploy a lot of power 00:43:55.900 --> 00:44:02.950 boxes and many cables. So we have teardown today so every help is needed. We have 00:44:02.950 --> 00:44:09.410 only one day to bring us back. The main thing, we had the power meter that we made 00:44:09.410 --> 00:44:18.190 on the camp this year. We have two nice setup on room H. You see the power factor 00:44:18.190 --> 00:44:25.560 is very bad. And the other one was the Waffle Operation Center so you see they 00:44:25.560 --> 00:44:31.730 have a nice power factor. So please use more ohmic devices like heaters, waffle 00:44:31.730 --> 00:44:42.960 iron or something. We only have 5 Seaview to monitor Yolocolo. You have on 00:44:42.960 --> 00:44:48.849 c3power.top a Grafana link that also links to the main Grafana to the NOC. Another 00:44:48.849 --> 00:44:57.520 nice thing we have on the lounge, I have a video here. It started now. You can see 00:44:57.520 --> 00:45:06.349 the current on all 3 phases to the audio and you can see the audio from the lounge. 00:45:06.349 --> 00:45:16.220 *recorded music from the lounge* [Filler, please remove me in amara] 00:45:16.220 --> 00:45:25.190 Arif: It's very nice. [Filler, please remove me in amara] 00:45:25.190 --> 00:45:28.140 *recorded music from the lounge* [Filler, please remove me in amara] 00:45:28.140 --> 00:45:33.440 Arif: As you see, the only thing is... [Filler, please remove me in amara] 00:45:33.440 --> 00:45:36.400 *applause* [Filler, please remove me in amara] 00:45:36.400 --> 00:45:44.670 Arif: Use more bass, or make more current. Later we can show you another slide. Go to 00:45:44.670 --> 00:45:56.420 next slide please. So for the radio team we have 120 portable radios. We have 00:45:56.420 --> 00:46:01.670 updated them to a new firmware, and a new programming software with a new feature 00:46:01.670 --> 00:46:07.440 that is a lot slower than the last version. Very nice. 50 bring-your-own- 00:46:07.440 --> 00:46:13.160 device radios. 5 dead radios from the camp. 2 dead from 36c3. 2 dead repeaters 00:46:13.160 --> 00:46:18.410 from the camp. 1 dead on arrival on this stage. 3 rental repeaters from 2 00:46:18.410 --> 00:46:24.460 companies, one we picked up in Hannover just before the Congress, and even the 00:46:24.460 --> 00:46:30.470 windows PC crashed down dead on arrival. Business as usual. So, next team! 00:46:30.470 --> 00:46:42.760 H: Thank you! So, the next is c3subtitles. I think it's Amy and Julia. Amy. They are 00:46:42.760 --> 00:46:51.760 not. C3SOS. S.O.S. It's you. Okay. Okay. Sorry. Oh, I'm sorry. Not the subtitles. 00:46:51.760 --> 00:46:55.370 It's well, sustainability. Your stage, go for it. Here, feel free. 00:46:55.370 --> 00:47:03.819 Amy: Hello. Okay, hi. My name is Amy, I'm part of the c3sustainability team. I only 00:47:03.819 --> 00:47:08.880 have four slides, so I'll be very quick. You can see, the first of our biggest 00:47:08.880 --> 00:47:13.650 projects was the drinking water dispensers. So for angels, we had drinking 00:47:13.650 --> 00:47:17.880 water from a dispenser rather than from bottles and they could refill their 00:47:17.880 --> 00:47:22.060 bottles. We go through some stats there. So when we started planning how difficult 00:47:22.060 --> 00:47:27.250 it was to implement it, the locations, and how many volunteers, satisfaction was very 00:47:27.250 --> 00:47:32.250 high for this one. So thank you to c3geld who really helped organize the water 00:47:32.250 --> 00:47:36.830 dispensers with us. We're very happy. They were really great. Please give them a 00:47:36.830 --> 00:47:38.830 round of applause. [Filler, please remove me in amara] 00:47:38.830 --> 00:47:39.910 *applause* [Filler, please remove me in amara] 00:47:39.910 --> 00:47:43.800 Amy: Thank you. The next one was a give and take electronic box. So we wanted to 00:47:43.800 --> 00:47:47.530 encourage people not to throw away their electronics. Of course, they can be 00:47:47.530 --> 00:47:52.859 recycled. So we have deployed 10 boxes. You can find them in the sticker stations. 00:47:52.859 --> 00:47:58.440 And we did this in collaboration with the hardware hacking area. Thank you. And 00:47:58.440 --> 00:48:00.440 other assemblies. Oh, wow, you are really fast. 00:48:00.440 --> 00:48:02.440 H: Yes I am. Amy: Okay! 00:48:02.440 --> 00:48:05.960 H: Others are waiting! Amy: Okay. So the last one I wanted to go 00:48:05.960 --> 00:48:10.780 through. We have two initiatives on this one. I'm sorry for the trashy picture 00:48:10.780 --> 00:48:17.240 there. We have organic bins in the halls. It was very, very difficult to do this. 00:48:17.240 --> 00:48:21.339 But actually it was quite satisfactory. But I would say there is room for 00:48:21.339 --> 00:48:26.930 improvement there. And there was also an initiative for recycling cigaret butts. So 00:48:26.930 --> 00:48:29.480 we actually had two people go round, collect your cigaret butts and they will 00:48:29.480 --> 00:48:37.460 be recycled into cool ashtrays. What a success! Thank you so much to everyone who 00:48:37.460 --> 00:48:40.750 collaborated with us. We couldn't do out without your help. 00:48:40.750 --> 00:48:44.100 H: Thank you. Your applause, please. [Filler, please remove me in amara] 00:48:44.100 --> 00:48:46.670 *applause* [Filler, please remove me in amara] 00:48:46.670 --> 00:48:51.089 H: So unfortunately, the c3sign is not coming. So just take a look at those 00:48:51.089 --> 00:48:57.400 pictures while I go through them. And now the next one is C3 Assemblies. Here, take 00:48:57.400 --> 00:49:03.960 this one. Thank you. Be quick. Pingu: Hi, my name is Pingu. I'm here for 00:49:03.960 --> 00:49:11.460 the assembly team. And I just want to ask, give a hand who hasn't found his assembly 00:49:11.460 --> 00:49:19.020 on day zero or day one? So then give a big applause to c3nav because they really 00:49:19.020 --> 00:49:28.690 helped us a lot. Because without them, it wasn't able to do this event just for us. 00:49:28.690 --> 00:49:37.329 Because for some figures we had 419 assemblies to place on this area which is 00:49:37.329 --> 00:49:45.060 about 35000 square meters. We had 3000 tables all over, 2500 in the assemblies, 00:49:45.060 --> 00:49:53.820 with 6000 chairs. And here, please give a big applause to the C3Möbelhaus or IKEA as 00:49:53.820 --> 00:49:57.359 you call it. [Filler, please remove me in amara] 00:49:57.359 --> 00:50:00.520 *applause* [Filler, please remove me in amara] 00:50:00.520 --> 00:50:07.930 Pingu: Because the Möbelhaus basically placed all the tables in a magic night on 00:50:07.930 --> 00:50:16.990 basically day -2. And they will disappear with the help of C3Möbelhaus today. We 00:50:16.990 --> 00:50:25.450 assigned the last assembly on day zero at 22:00 and we started our work in mid- 00:50:25.450 --> 00:50:33.460 October with weekly meetings. And yeah, as you can see, it was a lot of work and... 00:50:33.460 --> 00:50:36.119 Oh. H: Thank you. 00:50:36.119 --> 00:50:44.950 Pingu: Thank you. And just one thing, for teardown, for tearing down the assemblies, 00:50:44.950 --> 00:50:54.010 please stack the chairs on the assembly but leave every chair and every table on 00:50:54.010 --> 00:51:13.900 the assembly, we will get rid of them. H: Thanks a lot. Your applause. So the 00:51:13.900 --> 00:51:20.569 next ones are... Les prochains, ce sont les gens de c3lingo, voilà, vos tours! 00:51:20.569 --> 00:51:26.161 c3lingo 1: Hallo! Schön euch mal (...) Wir sind übersetzet. (...) 00:51:26.161 --> 00:51:32.190 German> Oh, sorry. Well, I'm also fine with that. 00:51:32.190 --> 00:51:35.540 We translated all the German talks into English. All the English talks into 00:51:35.540 --> 00:51:40.170 German. All in all, fifteen thousand minutes in seven different target 00:51:40.170 --> 00:51:45.089 languages. And here is from the second language team, who talk all the non- 00:51:45.089 --> 00:51:49.480 English and non-German things. c3lingo 2: Okay. So basically we did have 00:51:49.480 --> 00:51:57.450 about 1/3 of the talks were translated to French. Yeah. You can read the rest. And 00:51:57.450 --> 00:52:00.900 we even have currently, exactly, right now, another one which is translated into 00:52:00.900 --> 00:52:05.060 Swabian. So if you want to listen into it. [Filler, please remove me in amara] 00:52:05.060 --> 00:52:07.030 *applause* [Filler, please remove me in amara] 00:52:07.030 --> 00:52:11.491 c3lingo 2: Which means that if you were listening to a talk, there is 2 chance out 00:52:11.491 --> 00:52:17.710 of 3 that it was translated not only once, but twice. Into either French, Spanish, 00:52:17.710 --> 00:52:21.900 Russian, or Polish. One special mention for the Russian and Polish teams, that was 00:52:21.900 --> 00:52:25.010 their first time this year. So one big round of applause for them, please. 00:52:25.010 --> 00:52:29.790 *applause* [Filler, please remove me in amara] 00:52:29.790 --> 00:52:36.760 c3lingo 2: And one more big thank about for the guys who brought the cough candies 00:52:36.760 --> 00:52:41.380 and cough drops in the booth. That's a lifesaver. Thanks. 00:52:41.380 --> 00:52:48.559 H: Thank you. Merci beaucoup. So we have some heart operation going on here. You 00:52:48.559 --> 00:52:50.790 have to switch it or not? Oh, you're good with computers. 00:52:50.790 --> 00:52:54.790 *laughing* [Filler, please remove me in amara] 00:52:54.790 --> 00:53:00.829 H: He just *mimicks something*. So c3infrastructure from the subtitles. Your 00:53:00.829 --> 00:53:09.430 stage. Yeah. My microphone. Ha ha. td: So, thanks. Just a quick look into the 00:53:09.430 --> 00:53:13.980 subtitles. So what do we actually do when we subtitle a talk? Well, first of all, we 00:53:13.980 --> 00:53:18.600 take the video from the C3VOC and put it through speech recognition just to get a 00:53:18.600 --> 00:53:24.290 rough transcript that we can then give to angels to actually correct, because, well, 00:53:24.290 --> 00:53:29.569 machine speech recognition doesn't work so good at all. And then once we have a 00:53:29.569 --> 00:53:34.390 working transcript that humans have looked at, we put that through auto-timing, which 00:53:34.390 --> 00:53:38.220 just takes the transcript and aligns that with the audio, and that usually works 00:53:38.220 --> 00:53:43.010 pretty well. And, well, once that is finished, then we actually have working 00:53:43.010 --> 00:53:47.299 subtitles, but we give them to angels for another round of review just to fix any 00:53:47.299 --> 00:53:51.980 mistakes that got overlooked. And maybe sometimes the timing needs to be adjusted. 00:53:51.980 --> 00:53:55.720 And then, when that is done, well, the subtitle is released. And actually one of 00:53:55.720 --> 00:54:01.010 our angels did a nice chart about all this process that you can see here. It all 00:54:01.010 --> 00:54:09.800 sounds better, so thank you for that. Well, no presentation without graphs. As 00:54:09.800 --> 00:54:12.420 you can see, the important thing is really: everything goes up and to the 00:54:12.420 --> 00:54:19.440 right. On the bottom here we have finished seconds of transcribed talks. So this is 00:54:19.440 --> 00:54:22.300 really completed subtitles here. And it starts already quite high because it 00:54:22.300 --> 00:54:28.470 includes all the Congresses before. Then we have stuff that has been reviewed in 00:54:28.470 --> 00:54:34.790 orange. Stuff that has been timed but not reviewed yet in yellow. And transcribed 00:54:34.790 --> 00:54:44.609 but not yet timed stuff in green. All in all, we had 144 distinct angels. Yeah, I 00:54:44.609 --> 00:54:53.140 need to hurry up. 71% of which took 2 shifts and 10% took 7 or more shifts. So 00:54:53.140 --> 00:54:58.500 433 hours of work for 126 hours of material. And so far we've had 6 releases 00:54:58.500 --> 00:55:02.859 from this Congress and then lots of hours worked. All of these numbers are at least 00:55:02.859 --> 00:55:07.380 as high as last year's numbers, so good, thanks. When you have transcripts, you can 00:55:07.380 --> 00:55:11.200 do cool stuff with that. So, for example, generate word clouds to see what people 00:55:11.200 --> 00:55:15.190 like. And this case, people seem to like people and questions and time, which we 00:55:15.190 --> 00:55:20.610 don't have any here. So. Well, how do we actually keep track of all this 00:55:20.610 --> 00:55:26.070 complicated stuff? Well, we use a state- of-the-art NoSQL lock-free columnar data 00:55:26.070 --> 00:55:32.390 store, like many of the other teams also do. And well, thank you all of our angels 00:55:32.390 --> 00:55:38.070 for your hard work. And also thanks for the Heaven for supporting us. And then, 00:55:38.070 --> 00:55:41.440 well, if you if you feel bored between Congresses, you can still continue to work 00:55:41.440 --> 00:55:44.200 on transcripts. You have all the informations here, these slides will be 00:55:44.200 --> 00:55:47.219 online, follow us on Twitter. And thank you. 00:55:47.219 --> 00:55:49.450 *applause* [Filler, please remove me in amara] 00:55:49.450 --> 00:55:54.420 H: Please do your thing again, like your thing again, like do *mimicks 00:55:54.420 --> 00:55:57.630 something*. Take your laptop. [Filler, please remove me in amara] 00:55:57.630 --> 00:55:59.869 *laughing* [Filler, please remove me in amara] 00:55:59.869 --> 00:56:04.400 H: So this was the last one. I think I will try my best to do something like this 00:56:04.400 --> 00:56:09.010 too. Actually I'm not good with computers, but I know someone who is and who takes 00:56:09.010 --> 00:56:15.070 very great care of everyone of us. So one of my highlights of every Congress, feel 00:56:15.070 --> 00:56:25.079 free, the LOC! LOC: Hello. I'm the stand-in for LOC. As 00:56:25.079 --> 00:56:30.450 with all good projects, they're too busy for documentation. They're packing. So LOC 00:56:30.450 --> 00:56:36.270 doesn't have anything. I'm more of the Department of Health and Safety again. So 00:56:36.270 --> 00:56:40.900 for everyone: we have the message from CERT that there were no work-related 00:56:40.900 --> 00:56:47.660 accidents that caused real harm. The odd broken Mate bottle maybe. But thank you 00:56:47.660 --> 00:56:56.849 for having built a city again safely and orderly, even with all the chaos. For the 00:56:56.849 --> 00:57:01.069 people who are driving, please make sure that the drugs wear off and that you get 00:57:01.069 --> 00:57:08.220 some sleep and for all people riding along, please keep the guys awake. That 00:57:08.220 --> 00:57:11.710 would be greatly appreciated. Go home safely. Thank you very much. 00:57:11.710 --> 00:57:15.960 *applause* [Filler, please remove me in amara] 00:57:15.960 --> 00:57:25.660 H: So. Wow, ah, OK. So I'm very sorry to have to rush some teams and I'm very sorry 00:57:25.660 --> 00:57:29.160 that we don't have any time left. We are 1 minute over and I promised the teardown 00:57:29.160 --> 00:57:36.530 crew to not do overtime. So please, please give all the teams their respect and clap 00:57:36.530 --> 00:57:40.240 and tramp as loud as you can for now to finish! 00:57:40.240 --> 00:57:43.280 *standing ovation* [Filler, please remove me in amara] 00:57:43.280 --> 00:57:50.280 H: Everything! They did! For us! We did! For them! Why are you still sitting? You 00:57:50.280 --> 00:57:54.280 have to leave. Thank you. From the c3infrastructure Review. Goodbye. 00:57:54.280 --> 00:57:56.285 Subtitles created by many many volunteers and the c3subtitles.de team. Join us, and help us!