Thanks very much. What I'd like to do for you today is catapult a cabbage through the air and catch it on a spike on my head Thank you, I thought of it all by myself Now look I know what you're all thinking Luke Skywalker meets Albino Mick Jagger. I Get it relax. You're among like-minded friends I Designed this about ten years ago using the knowledge that I gleaned for my two years of first-year engineering And since then I've traveled around the world doing what you're about to see I performed in 13 English-speaking countries and every province of Canada Which which is pretty much the same distance covered if you think about it and and Yeah, I've settled in London now. I've lived in London for six years I London's an incredible city where people from around the world and different cultures They all kind of come together to avoid eye contact You have to respect that So yeah, my catapult is pretty simple But I would like to share with you one thing quickly before I move on the word catapult is really cool It's an English word, but it's made up of two smaller Latin words The Latin word a pult which means to throw and the Latin word cat meaning cat now The the English originally designed catapults in order hurl cats at the French Because they didn't like cats or the French and then this turns out to be a really good solution to both of those problems My catapult is is pretty simple. I'm just gonna Get this out of the way here It's powered by these high-quality Norco brand bicycle inner tubes That's a 18-inch bike inner tube. This is what holds the air and your BMX size bike tire They're super stretchy and I use them like this which is obviously not with the manufacturer had in mind and Because I use them like this they rip and they tear and they break and I have to replace them pretty much everywhere I go and at some point I thought to myself, you know, wouldn't it be great if I could eliminate that cost from my life Entirely if maybe in exchange for mentioning the Norco brand bicycle inner tube I could get free Norco brand bicycle inner tubes from the the people who make them So, you know, I I called them up and I told them my idea and they said hey Mike listen We the Norco brand bicycle inner tube people Would really rather not be mentioned in the crazy catapult show So I'm still buying them Now, of course catapults don't see a lot of use in military actions anymore except in the Canadian army Our troop has a catapult that he uses from time to time And as a result of this there are very few trained catapult operators in the world today So few in fact that I would be I would not be surprised at all if there were none in the audience here today No, so I'm not I am gonna need someone to help me out I'm not asking for you to be fully trained But there are some some characteristics that you must have some pre-qualifying characteristics If you want to be Mike Woods catapult operator here today, you need to be female 18 to 35 single with your own apartment There are any Actually, would you mind coming up and joining me that'd be great Let's bring up with a round of applause Hi, thank you. Your name is hi Becky. Hi Becky is a beautiful name. Yeah, it's it's gonna look so good in granite Yeah Okay, now Becky. It's pretty simple.  Okay in the catapult operating area you'll be holding on to this rope and You'll notice right now the catapult doesn't look super dangerous it's in its sprung position later on it's gonna be in a cocked down position and The danger is that it could move rapidly from cocked into sprung And and when that happens, you don't want to be leaning into what I've named the face ripping area So so no leaning. No, we do need you in the catapult operating area for reasons that will become clear now I've made you feel unsafe. So I'm gonna get you some safety equipment here. This is a Safety vest If you just like to slip this on You just drop the rope that's fine. It will actually fit a little bit better if we can get you get out of the shirt. No, okay Put that on now Becky don't worry about it too much because as anyone here can tell you there's absolutely no safety in that vest Where the real safety is gonna come is in these Norco brand safety underpants So if you just like that's all right, don't worry about it. It's a it's a 40 pound site gag Now I'm gonna sorry, I'm just gonna slip past you here Becky. This is a cabbage.  Hold on. We created some kind of not situation. There we go So you're gonna have to pull on the rope pretty hard not super hard But pretty hard and we would ask is that you have your left foot up on the frame of the catapult That's right right there on the bloodstain perfect Now you need to pull pretty hard not super hard, but pretty hard and because you're pulling so hard You need to step down equally hard because if those two forces are not equal and opposite The whole catapult will swivel Newton's second law kicks in and the whole catapult will swivel and yeah coal slaughter Okay, I'm just gonna slip this on here. This is my cabbage catching helmet I'm gonna be over here. Remember the whole audience is gonna count one two three pull when you hear him say pull You'll pull okay. Let's have a big round of applause for Becky just in case she doesn't survive Buddy all together and thank you very much Thanks Becky. I never said it was hard. I thought of it first and then I made it interesting Thank you


Bonjour, Paris. So wonderful to be here today. 12 people, right here. This is the largest KubeCon ever. I mean, it's so big that even my parents are here. It's a big year for cloud natives. It's turning 10 on June 6. Our CTO, Chris Anastricht, will tell you a lot more about all the celebrations and how much this means for us. But how far we have come in 10 years? Together, as a community, we've built up Kubernetes and Cloud Native to power the majority of web applications and extending to new and unique workloads almost every few years. Together, we have made platforms more resilient, stable, and secure. Some of the largest brands in the world rely on Kubernetes and Cloud Native. Spotify, Mercedes-Benz Tech Innovation Group, Airbus, Deutsche Bahn, Intuit, McDonald's, Disney, Apple, Adidas, Zalando, you get the gist, are all powered by us. I believe the reason for that is the extensibility of Kubernetes. Today, bring us an edge device, a stateful or batch workload, and we got this. Our ecosystem wouldn't be veritous today without the members who have supported us. Today, we welcome Akamai, Mercedes-Benz Tech Innovation, and Trend Micro as gold members as we continue to build infrastructure that supports every workload. Yes, thank you to all those companies. The past 10 years have been remarkable. I'm also looking forward to the next 10, maybe even 20. I mean, six years ago at KubeCon Cloud Native in Berlin, this conference, OpenAI told us that the future of AI was going to be powered by Cloud Native. Fast forward today, and what we see is that the world of AI has expanded and entered what Alan Greenspan, the former chair of the Federal Reserve of the United States, would perhaps call an age of irrational exuberance. It can be off-putting sometimes. The wild valuations, humongous investment rounds, every startup with AI in its name. But as Fred Wilson, a venture capitalist who lost almost 90% of his wealth in the dot-com bus said when quoting a friend, nothing important has ever been built without irrational exuberance. If we need proof, the technology inspired booms of the past, including railroads in 1840s, automobiles in the early 20th century, radio in the 1920s, television in the 1940s, transistor electronics in the 1950s, computer time sharing in the 60s, home computers and biotechnology in the 80s, and smartphones, and the app store in the mid-Ox, all brought lasting change to humanity and were a little bit gritty and preposterous when they were under wear. In this latest AI era, we are the people who are building the infrastructure that supports the future and are the partners that AI innovators need. Today, every company I have talked to utilizes cloud native. For those in the know, Slurm is a fan favorite for research and training workloads for AI. But even there, the realities of developer friendliness are making folks either move to Kubernetes or use Slurm plus Kubernetes, a favorite of mine. This big promise of AI will be actualized by our end users, people in this community here. And y'all are not wasting any time. End users developed a technical sophistication in the digital transformation and cloud journeys. The platform teams built, that's you all, and really know what is needed for infra. The AI centers of excellence need us, as they eventually find out. Question, how many folks or organizations are prototyping AI-enabled features right now? Raise your hands. Yep, a lot of you. And how many of you are seeing them have challenges go from prototype to production? They're the same people raising hands. Yep, yep. And that's because prototyping with generated AI is incredibly easy. But going to production at scale is how the AI dream is going to be realized. Feedback from our end user community indicates a significant push towards adopting the optimal AI stack for teams dedicated to gen AI development, but they're stymied by the prevalence of proprietary cloud-based solutions. This is not a new story. Proprietary or less open options can be faster to adopt, sure, and develop against, but there's a cost. You're buying into an opinionated solution that offers less configuration and interoperability. Wald gardens are not for everyone. As you may recall from the cloud computing era, the irrational exuberance of a new type of user experience leads to rapid prototyping, and that can reflect on the bills. Our friends at the FinOps Foundation ran a state of FinOps report in 2024 and found that 60% of large organizations are experiencing or expect to experience a rapid increase in costs because of AI ML workloads. Some are saying it's the wild west of cost and knowledge. Costs are growing exponentially. It's all very stressful, but it's also understandable. We are trying to shift as fast as possible, new models, new versions of models, inference features, and we are doing this without standardization. So each time is a huge lift to package and deploy to production. This narrative is familiar and seamless. In the cloud-native world, we saw standardization emerge with the Open Container Initiative, or OCI. In the AI world, with the order of magnitude of data and hardware choices being so much greater, we also need standards to emerge, and that will help encourage the same interoperability and consistency of how workloads are built, run, and deployed. And cloud-native is here to help in that journey. Right away in the present moment, the answer to cost management and interoperability both lie in open source. With the right guardrails, platform engineering teams, which is all y'all, can help your organizations. And I'm going to show you how. Just this past month, I discovered Moondream. It's a VLM, or visual language model. And what it does is, if you show it an image or a video, it will tell you what is happening in that picture or video. I tried it out on Hugging Spaces, which is Hugging Face's sandbox environment. Think of Hugging Face as the GitHub for machine learning. Now, Moondream is epic. It is so cool. When we were building the demo, Moondream had not yet been open sourced, so I couldn't use it. Today, it is Apache licensed, and I'll have a link for you to see it later. What I'm going to do now is I'm going to go to my terminal and get my kind cluster going. This is how I'll be running Kubernetes on my laptop. Those who have seen my demos before know that's kind of what I do. All right, let's get started. So just picking this off. And while that's happening, can we please go back to the slides? Perfect, thank you. I'm going to show you the architecture I'm using while the cluster is spinning up. So everything I have used is Apache 2 or MIT licensed. Oops, sorry. On the development side, I have an LLM application, which is an Image Summary Inference App built on Kubernetes. Now, Image Summary Inference App is a fancy way of saying, well, give it a picture, it'll tell us what's in the picture. And with Kubernetes, we have the flexibility and scalability we'll need for the modern software life cycle, which is essential once my app takes off. Now, on the other side, you'll see here, I have Lava. This is a visual language model and what I'm using instead of Moondream. And Ulama is running locally on my laptop. Lava serves as our building block, a component that offers the runtime environment for the application. Ulama is our model registry service and acts as a gatekeeper, managing traffic and ensuring secure communication protocols are upheld. Think of Ulama as the repository and distribution hub for all AI models our LLM app might need. Kind of reminds me of Docker Hub. And the LLM artifacts make me think of OCI artifacts. Now, if you look on the production side, it's a mirror environment with Kubernetes at the heart of the entire operation. The CNCF platform engineers, Taylor, George, Jeefi, have allow listed the libraries I used and we can go into production with Kubernetes the minute we want to. From a guardrails perspective, the model registry is the single source of truth for model management and serves as a consistent dependency between our development and production environments. Platform teams push approved models into Ulama, which are then version controlled and managed according to an organization's specifications. Let's go and check if my cluster has loaded yet. OK, it looks like it. Before I get started on the URL, what I'm going to do is I want to show you all the options that I have for models that I could use. You'll see three, oh, can people read? Should I make it bigger? It's always a good idea to make it bigger, so just did that. Hopefully that helps. OK, so you'll see here I have three models, Baklava, Lava, which I said I'm using, and Mistral. Mistral is a text-based language model, so that's not a fit for my app. Baklava is a combo of Lava and Mistral and is something I could use should I want to and just swap it out very easily. Now, going back, OK, here is my local host environment. OK, this is my application. And here's the camera. So what we're going to do is everybody here is going to join me and say Kubernetes and we'll take a photo. So everyone, one, two, three, say Kubernetes. Kubernetes. Awesome, great work. Best audience ever. Oh, and the app has already given me an answer for what's happening in this image. And it says it's an indoor setting. It resembles a conference hall, spot on, rows of chairs, facing a stage or platform, et cetera. You can see how it's very accurate. So now that applause tells me we need to get to broad ASAP. No problem. All we need to do is change the variables and run the pipeline and we'll be good to go. If you are interested in checking out this demo or the Moondream VLM, please feel free to use these QR codes to get access. Everything's available. My last demo got 145 stars. Pretty stoked about that. Let's please beat it if you like this. And this demo ran fully without a hiccup, so I'm just saying. This architecture demonstrates not just the harmony between development and production, but the seamless flow of work from the hands of our developers into the lives of our users. Cloud native isn't just connecting AI development with AI infrastructure. It's facilitating the connection between services, teams, and people. Our projects and ecosystem allow folks to focus on their areas of expertise and provide a trusted interface on which we can all depend. So I urge you, tell your developers going from prototype to production can be easy even when they start with open source. Give them the guardrails they need to be successful and help them make their dreams a reality. Roger type to production at scale turns irrational exuberance into sustainable growth for mankind. Speaking of turning things to reality, the cloud native AI group has released a white paper and reference architecture that's available to you today. And you can see the cloud native AI landscape that they have outlined here in this picture. I'm going to focus on a couple of sections, and you're going to see some pink logos and blue logos alongside the standard template purple ones. Pink is CNCF, blue is Linux Foundation, and you'll see a comforting amount that's already within our purview. So here, as you can see, this is general orchestration, lots of pink over there, no surprises. There's MLflow and Kubeflow. Sorry for the twisted workload observability. And the rest you will see on our social channels soon after this conference. And this is the cloud native AI working groups or reference architecture for AI workloads that's released in the paper. I highly encourage you to read it. As you can see, the community is hard at work on these infrastructure problems for AI. You will hear from Nvidia, Microsoft, Bloomberg, among others about the latest developments after me. I want to focus on another element. I want to bring up on stage some of the brightest minds in generative AI today and hear how they want to work with cloud native to support them in building the next generation of AI. Please welcome on stage Timothy Lacroix, come on Timothy, of open and portable generative AI for devs and businesses. Hi, Tim. Thank you for coming. They have received a lot of love and attention from press and investors alike for their open source models. Next up, Paige Bailey, who leads generative AI at Google, and they recently released Gemma, the open source slash language model. Excellent. Good to see you, beautiful. Thank you. Oh, I appreciate that. And last but not least, please welcome Jeff Morgan, founder of Olama, and open source tool for running models with 48 plus stars. Welcome. Good to be here. All right, folks. Thank you for joining me. It's such an honor to have you. It's an honor to be here and to get to see so many people who are enthusiastic about AI and cloud native solutions. This is awesome. Thank you for coming.  In the demo that I just did, it was so evident that Olama provides a very similar experience to Docker. Being a cloud native OG and someone who worked at Docker was that intentional. Part of it was just what we knew after using containers and Kubernetes for 10 years. We kind of couldn't help but design it similarly. But the bigger idea here is one of keeping paradigms the same. And it ends up that there's a lot in common with distributing, running, and serving models with applications. And so for that, it made a lot of sense to lean on existing paradigms and ways of designing tools as Docker, Git, and other cloud native tooling. Makes a lot of sense. And now you're positioned between the Infra and AI developer teams. What does that look like? There's definitely a gap. And it's a gap of tooling and concepts and community. The best way to think about it is what we were all working on together 10 years ago, which was the gap between developers and ops. And obviously, we've worked to conquer that together and to build tooling to bridge that gap. But the same gap exists between AI research and AI engineering as well as developers and ops today. Yeah. I remember, I definitely agree. I remember when I first started doing machine learning around 2009 and then started talking with some of the folks at Microsoft around 2017 and 2018 like Lachlan and Bridget about how I would go about deploying some of these solutions, the tooling stack was completely different. And not just languages, but also libraries, infrastructure. Most of the machine learning engineers weren't even thinking about containers and still aren't. So I really do feel like there's a lot that we can learn from each other, especially as more and more of these AI applications are getting deployed out into the world instead of being stuck in research land. Here, here. I mean, speaking of, there is so much innovation, fast innovation in AI and LMS right now. How does your infra team keep up with your scientists and model builders? Oh my gosh, they don't. So as an example, as we're training out these models, people want to try different architectures. They want to do tailpatches. They want to incorporate more data, train bigger and bigger models or models of different sizes. And each of those sizes has different hardware constraints, different latency constraints, different deployment targets or configurations that would need to be included. So I feel really fortunate to be able to work with all of the AI infrastructure engineers that we have at Google. They help make sure that the stuff that we build is actually useful out into the world. And it's a really, really hard challenge. Yeah. Tim, is your experience similar? I mean, it must be a bit different because I don't have access to all of Google's crowd of infrastructure engineers. So there are like three different workloads that we consider. There is training, which has lots of large homogeneous resources that we have to allocate between researchers. For this, we use SIRM that runs on Kubernetes, which has been a very nice experience for us. Everything that goes to prod is deployed on Kubernetes directly. Nice. The third workload, so inference, is like short workloads on single node. The third workload is fine tuning, for which code looks like the code for training, but it is on much smaller resources, much shorter time spans. So this can also be allocated on Kubernetes as well. Very nice, Saif. It seems like we're being useful. You know, you're building so fast in your startup, it's gone zero to a billion in nine months. What are the scaling constraints you might see as different models are evolving in sizes and capabilities? So I think demand for all sizes will grow from edge to huge models that take up multiple nodes. I think right now people are still discovering the models and still don't know which size is the right one for their application. Once people start to figure this out and get more confident, they will be able to pick the right price point for their use cases. What's interesting as well is that as the architectures are getting more settled, chip makers have the occasion to build more dedicated chips that are more efficient for these use cases. And so the variety of hardware that this community has to support will also grow, so that I don't have to think about it. Absolutely. And definitely, I also think that some of these inference constraints are driven by use cases. So as an example, in the AI for software engineering space, for things that are low latency like code completion, you might want to have smaller models, perhaps even local models that are used for very, very fast efficient inference. Whereas for some of these more complex planning workloads, where you have massive models kind of building target opportunities for migrations or for being able to do things like performance optimizations, you're using a much, much larger model, which would need to scale across multiple nodes. So I definitely think that we're going to be seeing a more interesting land in the hardware space for these inference cases, but also people using smaller and smaller models more efficiently, maybe doing fine tuning or using long contexts. So big, big opportunity space there. A lot is evolving, it seems. And like you said, the GitHub co-pilot-esque use case is one kind of model, targets, migration plans, different kind, yeah? And then as you were describing, we have to think of all kinds. There's three types of AI workloads with the training, fine tuning, inference. The app that I had deployed was an inference application for those who might want to know. And that I could run locally on my computer, thanks to y'all at Olama. But it was a CPU, M1 chip, M2. So I'm curious, in the land of AI right now, there's a lot of what can be called open source washing going on. What are technologies that need to be Apache 2 or MIT licensed? I think the obvious answer is the models themselves. That wasn't quite true six to nine months ago. But thankfully, to models like Mistral, we're able to have Apache 2 large language models and foundation ones. The reason for the model needing to be open source is one of access and trust. Customers are deploying this and using it with their own customers as well. And so you have this situation where the surrounding infrastructure on the model needs to be open source. Because today, the cloud tooling we use is open source like Kubernetes. But if the model is not open source, how are we supposed to extend that in a way that's unique to our business? And how are we supposed to go build our dreams for not able to actually open up the model, understand how it works, and ultimately secure it so that it's a good steward of our customers as well? I know you have a take on that, Tim. Yeah, my take on what needs to be open source is really all of the tooling. So from the languages that we use every day, like JAX or Bytorch, down to all of the compiler stack that lowers this to the hardware, I think that's what I really hope will stay open source. Because I don't know, it gives us so much more opportunity to just swap out things without asking ourselves, like, am I optimizing during this one year something for hardware that I'll have to throw out next year? So having this freedom of switching from one vendor to the next is really great. I have plus one to everything that's been said. I really loved when I was first exploring machine learning, being benefited by looking at all of the libraries, at all of the models that had been open sourced, and really being able to teach myself some of these concepts. If we don't do that as a community, then we run into this scenario where the next generation of AI scientists and the next generation of people who are wanting to deploy AI applications, they don't have that opportunity to learn. And the only place that they might be able to pick up those skill sets are by embedding in one of the companies that are doing it professionally. So I really do feel like we should make the models open source, the compilers and the frameworks. And then also, it's just been magical to see what people build. When we released the Gemma model externally from Google, it's a smaller model. But almost immediately, like three days after, people were building a mixture of experts versions of it and testing it out, building like a code version or like a special fine-tuned version for their particular use case. So I've been just super enchanted to see that. And the only way that we can understand what these models can do are by people kind of testing the boundaries, pushing them for new things. And that's just amazing. So if the cloud native community here could do anything for you, what would you ask for? Well, these models don't run in a vacuum. I think we built an immense amount of powerful tooling together to run applications at scale. And the same challenges are going to repeat themselves, just like you mentioned earlier, in this new world of running AI-based applications. And so my big ask is, how do we take the amazing tooling around monitoring, security scanning, logging, and how do we bring that into this new world of AI-based applications? The challenge is really that we're going to have to do it fast because these AI models are evolving so quickly. I would love. I feel like everybody's prototyping with paid service APIs right now, which really obfuscates some of the infrastructural requirements. I would really, really love for the community to create patterns for how you could replicate the experience that you're getting with paid service APIs with purely open source solutions. And not just using them for inference, having these retrieval patterns, but also the things that are very, very important for deployments, like observability, logging, all of these things. So I would love, if anybody has a yearning to have a weekend project, that would be wonderful to see. For me, I think it would be like keep abstracting the hardware, basically. I had to know Kubernetes one year ago, so I'm really an end user. And when we run things in prod, basically, I don't want to care about whether my GPU is going to die in some weird way. And so I think knowing that all of this management of health and checking that everything is good, replacing the machines if they're not well, all of this I think should be done by this community. And I would feel much safer knowing that all of these health checks are done by the cloud-native community, basically. Awesome. That's a word of confidence. Thank you so much. Yes. There are so many questions I want to ask you, things I want to delve deeper. And I'm sure folks in the audience want to have a more conversation as well. So we don't have time right now, but let's do this after the keynotes. If any of you want to chat with the panelists, have a conversation. Come to the AI Hub at 2.30 PM today. And the panelists will be there. And all questions and ideas are welcome. Panelists, I hope you saw that the cloud-native ecosystem, we are a way of working, we're a community. And our innovation is across all workloads. And we are here for you. Audience, the Generative AI Revolution is going to change the world. These people are changing the world right now. And they will do so with our help. Let's help our organizations, our friends, go from irrationality to completely thoughtful, rational exuberance, and give the prototype to production story a happy ending. Thank you so much, and enjoy the show.


Hello everyone, good evening. Welcome to this amazing session, the first after the keynote which kicks off our APM Light Conference. I'm very happy to have Shruti on stage with us to take us through what is new with APM Inspector. Shruti, we still have few people coming in but I'll hand it off to you. So hello all, this is Shruti Pandey. I'm born and raised in Mumbai. I've been a QA Automation Lead myself for a decade now, been into solutions engineering space for two plus years now, helping different clients across the globe integrate automation products and setups and platform. So I hope the session that I've created today for all of you comes in really handy and adds some value in your learning as well. So what you see on the screen that I'm currently sharing is our classic APM server, right? So most of us would have seen this. That's basically like a prerequisite when we start our automation or testing or want to just inspect elements, right? When we want to automate a native application or a hybrid application or a web view version of an application. So this is a classic way how you have an APM server installed and you start the server and then you start the inspection session. I am pretty sure most of the people, that's how you go about starting an APM Inspector. And what I'm going to talk about today is no more this setup for APM Inspector or inspection or creation of your X paths and codes really. Rather, I'm going to talk about what's really new in APM Inspector. So there's no need for us to do any of this. We are going to leverage most of what we have seen in the past. In case you have not seen APM Inspector in the past, I hope whatever I'll be talking about today will give you an insight of how to do this and how you can go about using it. So I'm just closing this off because we don't need this setup anymore. In case you are still comfortable with that, you can go about using it. But what we have new in APM Inspector is the APM Inspector itself. What you see launching at my screen is the APM Inspector app. So there are two things that I'm going to talk about the APM Inspector app and the web version of the APM Inspector. And I hope this comes really handy because I understand the first part of automation or inspection of elements. And especially when it comes to mobile applications or something that you want to do on a mobile interface or a mobile device is really very tricky, right? In part of inspection or creation of your automation scripts. So this is the new brand new APM Inspector app version of it that you can install depending on a Mac, Windows, Linux, whatever you might be using. It's more or less the same that it used to be in the past. So if you go about checking it out here, we have stuff like if you want to start it on a remote host, the port you need to give. What's new here is you don't need to give a path which is like slash WT slash hub that used to be in the past. No longer the need of doing something of the sort. Now you just give a slash there and it's all good to go. It can also take care of SSL. It can also take care of advanced settings, which could be our certificates on the applications or any proxy setup. Because most of the time when people are using this kind of a setup, they are basically behind firewalls or VPNs. And when in the work from home setup, you might be having all the all the more restrictions with respect to accessing your setup or your application. Now you can actually have a mobile device or a device of your own which is connected to this local host, or you can go about accessing any of the cloud providers. So we, as you see, there are a lot of integration of different cloud providers that we have, which can actually give you a device to basically help you create the session or launch the session on. For the ease of my use rather than having a local device, I chose head spin, but you can go about choosing really anything for that matter. All the options are available for you on the screen. So when I come to my choice, I come here. And if you see, I have kept some capabilities set here. But what you really need to do is create these capabilities, right? So I'll very quickly glance over that as well. So whenever we start making use of our Appium scripts or creation of it, or even the Appium inspector session, you need to pass on capabilities, which are basically Appium capabilities. Right. Otherwise, how does Appium know what you want to do with respect to this inspection session really?  Then you go about giving more details, which are really capabilities. So I have basically selected the device name. It's UDID. Since I'm using an Android phone, so I give the platform name as Android and the automation name as UI Automator 2. Depending on what you want to use, it could be iOS. It could be different versions of automation that you might be wanting to use. You can definitely change that on fly. Again, what is more important when we're doing this for an app is we need to pass the app package and an app activity. So in case you're working in a QAT, even if your developers setup is there, you may ask from them as to what your app package and app activity is. Or maybe you can also go about checking a couple of these details on your own via the application that you're using. So I basically wanted you to know that these are a couple of capabilities that we need to add here. So if I come here, it's the same capabilities that you see. So if I just go about saving it, if I just click here, all of these capabilities come in here and I'm just making a save of it. And I want to start the session. So it's very, very similar to what we were doing in the past, just that now we are doing it on an Appium Inspector app. We started a grid of our own and we gave it the capabilities of the device I need to use. If I need auto accept alerts as true or false, that's something that I gave for myself. I'm using an Android. If you see for my session, I basically have given the native app as the settings app itself on the phone. You can go about doing this for any app for that matter. So you might be using any different kind of applications really to go about testing. It could be just for namesake eBay, Flipkart or I don't know, Samsung, whatever that might be. And I've kept this very generic because I wanted everybody to have a benefit of doubt as to how to go about it. So this is a classic native app of settings on the phone that I'm using currently and what's new with Appium Inspector is this. So if you see on the top, there are different modes of accessing the different kind of applications you want to inspect your element on. This session particular that I want to talk about or go about automating is for the native app mode. Hence I launched application of the setting apps itself. There is also another mode which we'll see in a while. You can go about selecting elements, you can go about swiping on the coordinates or tap by the coordinate. So these are different gestures as to how you want to basically select the elements or create their experts or investigate them basically. My personal feature that I really find very interesting with Appium Inspector is recording the session. And I know most of the people in the testing fraternity ask for a record and playback because it makes life easier. So I just started recording on this session. I'll do a couple of clicks because if I were to automate this as a user flow for myself, I just clicked on a software update is available. And I do a tap because I need to perform an action right for that to happen. I'll maybe do a few more clicks so that we understand what I'm doing and what it sufficiently generates for us. So I'll now maybe cancel it and I'll now maybe also stop the recording. So what I typically did here was I started off my app by setting the capabilities. It launched for me the setting apps. I'm trying to do a couple of things there by hitting on the button or the hyperlinks or whatever pop ups that are coming into picture and I'm interacting with them. So when I stopped my recording, you can see a recorder has generated all these experts for me and I can go about leveraging them or making use of them to automate my scenarios or get these elements basically. You can also go about selecting the language of your choice. So in case you're using any particular language or setup or script or framework. So why not leverage the option right. Another cool feature which I find is the recorder. If you just click on the boilerplate code, it created that entire code right from import web driver launching your capabilities and your web driver URL everything until the things that I've done. So I came to the expert. I clicked it I hovered up more and then I did a driver dot quit. Anybody who is just very novice or starting new with Appium can really go about making use of this right and like why not so I can just do a copy paste and start off with a script creation for myself not just recording the experts but also recording some very generic vanilla flow for myself. So this is what I wanted to talk with respect to how I did a complete end to end thing of setting my application as a capability in the native app on on the app version of Appium inspector to the recording of it to the creation of code to inspecting elements. I'm not yet done here so I'll just close this and I still have something more to show you guys. So now that we don't have any dependency on the Appium server and starting our inspector there, and I did a start on the session for the app itself. We also have something as cool as this. So, even with the app you need to install the application on your setup right so it's as simple as downloading a app. But if at all you're too, too nerd or too geeky and don't want to have any of the hassles around you can just go about launching a web session of it. No prerequisite required again very similar setup it's just a difference of the UI right there you were using it via the app itself for Appium inspector. You're you're using the web version of the Appium inspector by a URL. Again, if you see most of the things remain the same. It's just a UI change. I'm again selecting a headspin for my option you can go about selecting whatever you want what we saw in in that previous recording was for inspecting elements for a native app right in that case I was doing it for the setting apps on my phone. Now I want to do some inspection with respect to a hybrid app. So, I know a lot of this is getting in so common these days right because now I want to check my website on on a mobile device or I want to test my application which has been since interacting or an app which is really hybrid in nature right all of that can be counted in as a hybrid or a web view or a web version testing of my app on a mobile device. So the only difference I did here is if you remember, I'm most of mostly utilizing the same features I'm again trying to do it on the Android, I'm doing auto except alerts through you can add more in case you need that for your application I passed my device and you did the more thing that I've added here is I want my Android to start off a Chrome browser session. Again, I've kept it very basic because I want to show you how this goes really so I'll start on my session. I gave my app packages Android Chrome app activity as Chrome main. I really want to start off a Chrome browser on my phone this time so the only difference you're I've done is now I'm accessing my app inspector via its web version. It started off the session for me on the phone, and it has launched a Chrome session for me. Again, if you see your what's important for us or the only difference here is I need to go in the web hybrid app mode right because until now we used to be complaining I know as a test of myself that how do I automate all of this on Appium inspector right so I'm very glad that the team who did this at Appium inspector and at Appium really has worked hard to get all these features available to us. So I just switched my mode to web or hybrid app mode because I want to do some recording some inspection for the web application cell that I want to automate again I'll start recording for the ease of this. And what should I click on maybe I should just click on Facebook it's like something that most people use maybe not that I use but I'm just clicking it for the generic usage that people might do so I just clicked on it. And what more should I hover on to maybe I should click on the name element itself in case I want to do something amazing the tab field which means there's something wrong in the top and the element is not present anymore classic things right which we basically see going on for us. Again, if I want to just go about going back or switching my language I can do that as well. And now if I basically stop my recording again, I've changed my language to Ruby you can be using again any of the languages that you may want to use. And now we go to our boilerplate code again do a very easy copy paste and generate this code with basically launch a web application for me so from here you can actually go about traversing any application really right so in case you are trying to automate Amazon or IBM or I don't know it could be anything right I'm just trying to give you examples here. But in case you want to just go about traversing to any web application for that matter, you can generate the code for that and go about creating the script for it, or automating the application for it, and that's pretty much about it so mostly what we have done so far is now I just launched the web version of Appium Inspector. I wanted a device for myself to be hosted I passed the capabilities, I wanted to do the inspection or recording or creation of my elements for a web application for myself so I chose that as an option I chose that as a mode like web hybrid app mode, and I started my recording I created my code. Again I just maybe stop the session and release this so I'm done here and I can have my capabilities saved for myself and I can go about doing more things. I know in the past you've seen a lot different things that were happening at Appium Inspector or were not working at Appium Inspector, but I personally think that we've come a very very long way with Appium Inspector itself, which is the precise reason why I chose this as a topic to talk today because I think it runs so much more things right. And this is very much like a prerequisite for all of us testers out there when we start automation or scripting or inspection of elements and I hope this session that I've carried on so far made sense to you. In case there are any questions now I would really like to take that. Thanks Anand for that. Yes Shruti so there are a few questions now do you want to go through it on your own. Sure. All right so I think I can see what's the difference between UI Automator one and UI Automator two. I think it's just a wrapper that they guys added on to and most people these days are using UI Automator two because there's no dependency or there's no really support offered for that it's basically if you're using Android. Most people either use UI Automator or in case you're using something like a espresso or that kind of a setup you may want to go about using that but it's just basically a framework or a wrapper or a setup for myself because android in tandem needs something as a platform name for you to basically start accessing your server or start accessing your Android test so that's pretty much and the difference between the two. I also see another questions where somebody mentioned how to handle interactions not available for this element while inspecting. That was precise reason why these guys created at Appium or Appium inspector the entire new native app mode right because earlier we used to not really get elements with respect to that. We never saw what was happening with the web view so now you basically can overcome these errors by switching on to the web or the hybrid app mode and go about inspecting your elements. So most of the time I think that is what you would like to take on your approach in case your development team keep on changing the x path you can still go on seeing that error because the dorm would have changed. So that's a very classic scenario that a QA tester would come across another thing. Okay, I think it's not a question but really a thank you saying that you're happy and got to know today. So yeah, thank you for that Vishnu. Do you think I missed any of the questions and I tried to cover most of them and I know I'm really dot on time I guess. No we covered the questions and you are spot on time you're not delayed at all. I do have one question though if I may I'm taking the liberty of asking. I've used the recorder and by the way at the web version of the inspector is amazing. I can't wait to try it out myself. And but one thing which I've always found in the recorder while it is a great way to get started. Is there a way to customize what locator strategy should be used for a preference of the locator strategy when recording the elements for the actions because typically the complex experts are shown in the recorder. Whereas that might not be the most optimal one. Correct. So I think it's also what we used to do very historically or primitively so you would have seen three options coming on the top right where I can either go about tapping on the element or I can go about swiping on the coordinates or doing something with respect to the the coordinate so I think those are the classic options that you can go about customizing while you're trying to record the session right so it's not just a tap. But even while I'm trying to record a session on the right hand side I can do a sense dot key so I can put an enter or I can put a backspace or whatever action I want to perform. So I think those are the classic ways we had earlier also but I think we may want to leverage that a little more in case we are not doing very generic actions and make the most of it. Sure. Thanks to the there are no more questions right now and we are indeed out of time now. So again I want to take this opportunity to thank you for speaking with us and sharing the APM inspector with everyone live demos always fun I'm sure it's challenging for the speakers but I'm glad you did that and you pulled it off magnificently.


Is it a real kiss? Yeah, you do actually have to touch lips I mean unless it's very hidden and you don't have to you might not but in general Yes, you actually do have to kiss the other person Will this be a deal-breaker in an acting career for you because every actor one time or another you might have to become Intimate or kiss somebody if that makes you extremely uncomfortable if you have any trauma around it Just the idea of having to be intimate with somebody else isn't okay with you Then just don't audition for those roles if your dream is to be in romantic comedies and be in stories about love and Relationships then that's gonna be something that you definitely are gonna have to work at Because if you are auditioning for something that already has an existing kiss in it and it's integral to the storyline They're not gonna remove it just because you're uncomfortable. I would advise you to not put yourself in those situations by not auditioning


Okay, welcome everybody. Again, I'd like to remind you to sign up for Angel Shift's Drink Sufficient Water. If you have water with you, consider sufficient water to drink now. I'd like to start up with this first talk in the opening of May Contain Hackers 2022. We had to wait an extra year for this, but it is even cooler. Well, it's actually quite hot and happening. Yes. So, the next talk, the first talk, will, warning, this talk may actually contain hackers. There may be hackers in the room. There may be hackers surrounding the room. There may be hackers recording this. There may be hackers listening in. There may be hackers that actually trade data. There may be hackers wearing shirts. Well, some of them do. There may be hackers carrying spying devices. Oh, no. There are hackers everywhere. What can we do except having a party? Stitch co-organized 2017 already, and MCH 2022, a help design the new generation tool of all the colors. It's also really nice. I mean, look at all the designs. The lines are awesome. He also worked on setting up hackerspaces like Hack 42 and Awesome Space. Well-known. Give a round of applause to Stitch. Wow. Oh, it's, I cannot express my feelings now. It just took three years. So, thank you all. Thank you, family, friends. It's really, really, really nice to see you all again. I'm really honored to be standing here.   And we are finally here. And we did it.  So, yeah, the road to here was interesting to give you a few tiny highlights. So we had to cancel due to COVID. So we were in organization mode and meetings. And then COVID happens, which ended up very bad for a lot of people. So pretty bad. I'm really happy to see people wearing face masks and masks in the stand. Thank you very much. Thank you. So, and we got to the point where the cash flow became a really interesting issue. And it was the point where prices started raising. We had to do down payments really, really early on. Everybody wants to have full payments because there was a lot of uncertainty.  So that was not fun. Thanks to all the people that did the startup donations. Thanks to you, we could actually do those down payments and have a conference. So give it up for everybody that did a startup donation. So in March this year, we started organizing like endure die modes. If COVID would happen that it would have disastrous consequences, mostly for the people that have COVID, not for us. So I'm well aware. But due to the crisis, COVID crisis, the war in Ukraine, and everybody and their dog wanting to have a conference this year, we had a lot of issues with suppliers. It wasn't the level of EMF camp 2018, but it was really terrible. And I want to give a shout out to the people that fixed the water stuff in the past few months, especially Lupus Reinder and people from PG Rental. They basically saved the day and that's why you have water now. And even worse, we had a power issue. Like we ordered it way, way back when. And Aggreco is a company that we work with. They are very nice people. But every piece of equipment that we loaned is still stuck in France. So what they did is get the generators and everything else rushed from Dominator Festival to here. It was too late. It has burned up people. We again had to rent a lot of people. There were night shift and it was basically very, very, very bad. So be especially nice to the power people and consider helping out tearing it down. Because they are all burned out because of the late delivery and the complete clusterfuck that ensued. But we have power here thanks to the power team. So give it up for them and please help out. And there's some other very interesting points. And this one is actually not really the worst one. But we work with our own scouting estate. It's a very nice place. And we work with scouting a lot in the past I think three years to figure out a contract.  They have this really nice planning system. And you can reserve your time slots. Turned out they have two of them. So that's why there's a lot of scouts here. And we have like 1200 scouts switching in the next few days. And that causes some interesting cultural differences. Which I would like to highlight a few. So we reduce the amount of stress. Which is basically this PowerPoint karaoke. So noise and music please be silent at one. So they can also have a nice sleep. There's a lot of kids, very young kids. So if you have these... Of course you can play music near a tent. And not at the too loud volume. But if you have like the speakers that we have here or I don't know... The stage over there or any other village basically. Consider being silent at one. Also scouting doesn't have the concept of villages. Now here you can walk in every village and say hi. And what do you do? And you get a tour and etc. Scouting doesn't have that. They're basically islands. So if you... I'm asking you to not go into those islands. And if you really, really, really want to talk to somebody from scouting out of interest. Their protocols basically wait outside and ask if it's okay to come in. And then it might be okay that you get a tour or something. But generally leave them alone. So they're really nice. But there's a cultural difference. And yeah, please respect that. And nobody asked for these double bookings. We didn't. They didn't. It's just... This is the situation at hand. Please be kind, be nice to each other. And let's all have a nice party. Thank you. There is a tiny visual cue where the scouting part starts. So this is a hint. It also has some tape around their part. So it will be pretty clear. Let me see. I did already do this. So I have got the honor to do this section new and improved. So new hacker camp, new stuff. There's a lot of stuff that you already know. Like a harbor and such. This time we have these very decent 200 gigabytes per second up and down. So I was asked to not use it for nefarious purposes in some country. And they have 10 gigabits wired for everybody. And they have all kinds of new technologies for the network nerds out there. There's a blog post about that on the site. I want to highlight this device, which is a... You cannot read it, it's a bit low. It's a course wavelength division multiplexing optical atrop multiplexer. There you go. It has the squirrel that bites through the UTP cable. That's the logo of the nog. So another nice thing that's new and improved is the badge. I've got one here. There's no component shortage. It runs Doom. I don't know if you can see it, but it actually runs Doom here. It basically can run Doom on two chips. I heard they were engineering to offloading the graphics. So you can get this 60 FPS experience, which you need. That's the logo of the badge team. It's here. There is an app store. So if you need new kinds of ransomware ideas or shady payment systems, mch2022.badge.team and it has tons and tons of apps on it, just like last time, you can develop Python stuff with it. And please do. There will be a badge review talk. They will hand out some prizes and stuff for the people that make the most insane and crazy apps. So please do so. Give it up for the badge team. Next up is something that is very, very, very new to hacker events, which are hoodies, and not just any regular hoodies. They contain something that is non-standard and maybe even out of the norm. That is a non-dark part. So it's custom-made, everything, just like last time. I hope I can show it a little bit. The design made by Nicolette and Bleeptrack. So thank you. There's a butterfly with this nice prism effect. Equations, a badge. It has, of course, a cyber label in it. Yes, sure, you can clap for cyber. So it's embroidered, so it will stay long and nice, well, blah, blah, blah. Thingy. And yeah, I like the sleeve. So we are on the way of making a maybe non-dark hoody next time. It will take a few years of development, so give us some time, please. Right, then we have something else that's special, and therefore I need the holoblot people. They're probably in the room, and they have a tablet where they have demo effects on it. So there's this audio system in this room, which, yeah, it's a small system, and it does something special. It basically can not just make noise in the wide sense, or like any direction. It can also do beams of noise. So we're going to play the jungle thing, and you will hear different parts. So who hears the crickets very loudly? Mostly there. Who hears the birds chirping very loudly? There's this line. What else special things we have? The birds' crickets? Yeah, there's a lot of insects. What we do tonight, between 11 and 1, we have a session where we will just experiment with the system and you can walk around. The funny thing is that you can walk around the room and have different points in the room for different audio. That's something new. For example, they have a demo where you can walk across the street, like a virtual street, and there you hear people clamoring, and there you absolutely don't hear them, which is crazy. Of course, this is not a really optimized tent for such a system. So tonight there will be a lot of experimentations. See where it works, where it doesn't work, might work in another room, et cetera. So I invite you to join. It will be music, including the Dutch traditional quality music at the end. So we can see how far it goes and how well the bass does their thing and such. But it's a new system, and a lot of people drove it all the way from Berlin to here. And it's basically the most expensive item on our insurance, so please don't break it. Another thing that's new is the MCH payment system. It's the all-round spherical payment system with all kinds of excellent features. I've got it with me. Actually, we have a version two of them. Our engineers came up with a, we can also do this on paper, and then another engineer came up, we can also do this on plastic. So basically you can exchange your money into a QR code and pay on the field where if you want. You can get many QR codes, so if you want to have vouchers of 10 euros and have multiple of them, fine. If there's still money on them in the end at the event, you get reimbursement, of course, so that's very nice. And we have cashless payments basically everywhere. So you can use your standard PIN cards, credit cards, whatever card payment you have, your phone, you can use that just like a supermarket, basically. And the QR codes. I recommend the QR codes because of better anonymity. And there's a lot of complex stuff going on there, so if you want to be sure, better anonymity using QR codes. So I see a long line of people getting QR codes tonight. Then there's a slide that I accidentally left in, so we can skip this. Something else that is new and improved is the secret token game, which is an idea we got from Bornec. Hello, people from Bornec. Anyone here? Give it up for Bornec. Yeah! Bornec is a hacker conference in Denmark. It's after this one, so if you think I need more hacker conferences this summer, yeah, you can. You can just drive to Denmark. So I have more fun. And there's this game where you can look for tokens which start with secret, and then to accolade or curly braces, and a text twin in it. You can enter that on the secret token website, and the more you find, it's basically token.mch2022.org. It's on the bottom of the slide, which you probably cannot see. And they're spread out through the entire camp, everywhere. There's tons of them, and you can basically make even more of them. So, yeah, the challenge is to find them all. We have a nice price for the people in the end that found the most. We have to figure out what that is, but that will be fine. Another thing that is new and improved is... I'm wondering what happened to the slide deck. Is the stage... We have a laser show stage. I'm using laser shows because of licensing issues, and there's also a support with audio.  And we said, no, you cannot have music, but you can have lasers. So, hence the laser stage. And if you like making music, you're invited to do something there. Also new is that we now can go full circle on this terrain. So we have a circle on route. There's this bridge, and you can basically walk through the Zusa field, which saves you one kilometer of walks between this track and that field, which is nice. It took two months of effort getting this. Just these rubber things and the bridge is two months of mailing back and forth. I pity the people that work in these permits things. And something else that is new is the supermarket. We have a supermarket on site, and I just like ten minutes ago made this picture and I tried to have no people in it, so it's not a very nice representation. It has basic... This implies they only have sugar and salt. I hope they have a bit more, but at least you can get some beverages over there. And so, thanks for the supermarket. And the things we know and love, such as finally normal people to talk to for a few days. Villages, the family village, a lot of workshop tents, track tents, lasers, flamethrowers. Let's see if it works. Lasers. Wow, lasers, yeah. Flamethrowers. A lot of retro gaming due to a sponsor. I'll get back to that. Very inefficient parking. You get VIP tickets.  So you can try to obtain it if you drive from the field and back. We have got a lot of different cards this event. Try to collect them all. There's a ton of them. If you get the VIP ticket, you are asked to park way, way in the back. And this time we use emojis for track names because that's all the rage. Silent camping, silent lounge again. Food vendors. There's a party area. Capture the flag, of course. So there's like, you're at the camp and you think you are here, but you're basically missing 80% by just being in this room. So that's how this works. So the program. There are hundreds of talks. You can find more... Oh, I switched some slides. So you can find it on program.mch2022.org. There are like hundreds of talks for the next five days. And every day there are lightning talks. Somebody rushed in the HQ said, like, every day there are lightning talks. Okay, every day there are lightning talks. And if that's not enough for you and you need more clones of yourself to visit more things at the same time, there's also Wiki with self-organized sessions. Also, like, 80 sessions up right now. So there's more than enough to do for the entire day. The content team has been working, like, yeah, for months also. Hundreds of talks, submitted, reviewed. Yeah, and some of the talks about, I don't know... I'm missing the English word for people that have problems with that deny that COVID exists and all the other stuff, like, blockchains and all the other stuff has been... kicked. So we actually have a nice program. So thank you. Give it up for the content team. So this time we have a lot of sponsors. It's ridiculous. The sponsors slots have been sold out, except the Diamond one. If somebody is in a room that wants to throw away 50K on the hacker scene and make sure the hacker scene gets better, then we're mission complete. But the sponsor team has been working insanely hard, and they started calling MCHs many consumed hours. So... And this is also the first time that I... Yeah, we actually have to announce sponsors during the opening talk because, yeah, they did a lot of... Spent a lot of money, but also give something back in the sense of content, which we wanted to highlight. Sponsoring and donations all together is like the inflation correction of the last few months. So if you know that the budget was 1.2 million euros, then... It's like... Normally sponsors are just an add-on. We do the normal stuff by using the ticket price, and this time we could not live without it, and I think that's not a good sign. So we'll have to re-evaluate, but making the ticket like 600 euros is also not really a good deal. So it's a struggle. That being said, I wanted to get that off my chest, I wanted to highlight the first sponsor, the computer test, which is a testing company, it's in the name, and they bring the arcade, the home computer museum, and game in. They are all at the most southern part of the terrain. It's a lot of fun, and they have a bar as well, and a lot of people that work day in, day out to make that a really, really nice area, so please visit it. Then we have Adgen. I don't know, it's not in their name what they do, except adding Jens or something. They support the MCH payment system. They are also a platinum sponsor, and they said, oh, here are all the pin terminals. You can get them for free. They work till the next year. So we got 16 of them, and it was not enough, so we called, like, could you add some more? We got another 16, so there's enough payment terminals and ridiculously low transaction fees and such, which are basically not possible normally. So thanks to Adgen. Thank you very much. Also Deloitte. Deloitte is an auditing firm, but they also have a security auditing part, which is, I think, actually a nice part of it. They also provide a separate track of content, which is on the wiki. Maybe it will be also somewhere on the program, in one of the stripes of content. They have to unlock the city with a lot of talks there. And Deloitte is actually somehow, interestingly, our favorite sponsor in one sense. That is that sponsors are really restricted in what they can do. We don't want to have banners plastered everywhere with all these sponsor logos and etc. And the lawyers from this company said, like, you are not allowed to use our logo in any other way, except that the things that we approve. So, well, we like that. So we don't have to use it. But in case we need to refer to them in the future, there has been a company asked to make an alternative logo, which is using a different font, a different style, a different tagline, etc., which is this. So, you know, yeah, it's not been pre-approved, but this is an entirely different company. And just for the record, to be nice to all the other sponsors, it barely fits on this slide from Gold, Silver, Community and Material sponsors. The Creative Industries Fund, especially for all the speaker reimbursements and travel reimbursements for speakers. So, thank you, all sponsors. So, MCH is a community event. Like, we're all from the hacker scene. There's this angel system. If you've never been to a hacker camp or congress or hacker events before, the angel system is a system where you can have, like, shifts of two hours to do something, like recording this track or driving the shuttle, a luggage shuttle, or the shuttle from Nike Air Station, or any other task. Basically, everything is done on a volunteering basis.  And if you want to do something at the event and help out, please do so. We need your help. You can find the angel system in the heaven, which is the large tent next to the road, the white one, and on angel.mch2022.org. I have already two special requests I want to mention, which is, because of the burnout of the power team and such, we are looking for three teardown coordinators to help us assisting teardown in planning what supplies come when. So, if you would like to help and really make a difference during teardown, please help us out. Step forward after this talk to that side of the stage, and you can talk. And also, tearing down, when we're tearing down, facilities will still be up and running, such as showers and toilets. So, you can stay during teardown and help with teardown. There's excellent food by the Macklinburgers.  Yeah, it's the best vegetarian food I've ever eaten, so it's really good. So, please try and help with the teardown and we are still looking for the teardown coordinators. Then some general announcement before we start the show, which are, please remove your car from the field. This picture was made a few days ago by the same team, and they were like, oh, we can do everything, and then this happened. A special request from my treasurer. Henry did all the insurance stuff, and we were explicitly told we are not insurers against cyber. I'm sorry. So, please, yeah, cyber is a problem. Also, if you want to know more, please check the booklet. There's some at the entrance, you also probably got one when you entered the camp. It contains everything you want to know about the family village, phone numbers, important opening times. A lot of practical stuff. It also contains a map, which is slightly off-centered. But that works fine because you will basically save it like this anyway. So, there's also this map. There are also all around the campsite. If you think making a booklet is easy, no, it's not. It's also like weeks of work and a lot of lost sleep. So... Then, I think this was the opening, the moment we've been waiting for for three years. Again, thank you very much for attending, for helping out. And next up, there will be a... What's it called? Sorry? The Silicon Passion, yeah. It's something different than just a regular talk. I'm sorry. They have all these devices here. If they're going to tell me they don't use MIDI, I'm really severely impressed. So, thank you again. It's lovely to see you. Oh, are there some questions? What's up? All right. Yeah, of course, I see what's happening. So, please, I'm reminding you again. My face mask is somewhere there. Please wear face mask inside of the public tents and have a spectacularly awesome MCH 2022. So, I want to get the project lighting on the stage. Could the project lighting please come up the stage? This is the team that in the past three years worked their asses off the project lighting first. So... Silicon Passion is like... Finally! I just wanted to show some faces of the people that have been working really, really hard in the past few years. Just so you have seen their faces. And if you are stressed, then you might not want to ask a question. Because they also want to have a holiday the next few weeks, days. Henry is the... There's Henry. So, from left to here, it's Halcyon, Resume, Resume, Hookamurm, Netsmurf, and last but not least, Henry. Alright, let's party! Thank you!