So welcome to Night Talk and welcome to Security Village. Just a few words about me, because I don't have a lot of time and I like to talk, so I'm going to talk a lot. So I'm Ben, I'm co-founder of Armo, maintainer of Cubescape, also contributor at Tech Security, and I used to be white hacker for a really long time. And yeah, I have a big family of four kids at home who are waiting for me.  Now, I really hope that this is going to be a different cyber talk. So I'm going to share with you something with this at Armo, the way we leveraged cloud-native technologies in order to create what we call continuous security. How much of you are using CI CD? Can I have hands up with Kubernetes? Yeah, so I think it's going to be relevant for you, like a good match here. So what we're going to talk today about three different aspects of your security. These three different aspects, two of them are Kubernetes-native policies. One of them is related to your vulnerability posture in your applications. And we're going to talk about them, how you can leverage your CI CD to make those things much better and like what we call decrease your blast radius in your systems. I'm going to show you that how we are generating runtime policies from application behavior during testing and how we are adding it to our CI CD. And I'm going to talk about is it good, is it bad, or I guess you know where I'm going with this, but it's going to be good, hopefully, for all of us. So today's threat model is like, I think, a very classical threat model around the Kubernetes cluster. So most of the times our pods can be either accessed from the direction of the public internet, either by a service, a load balancer service, or ingress. This is how they are getting traffic from the outside world, or maybe an attacker will try to penetrate your pods through supply chain, through image registry, and so on. But first thing I'm going to show you is actually the application exploit, so your vulnerability posture in your workloads. I'm going to show you how you can decrease the noise around them and only focus on the real things that really matter here. The second thing is that if the attacker was able to penetrate your workload and have code execution in your workload, in the confinement of your pod, the attacker has two directions to do lateral movement or progress. Either he can target your kernel trying to escape the confinement of the containers, which are making up the pod. And we are calling them kernel exploits. We had a flow of a few of them. And as soon as if an attacker is able to escape in a Kubernetes node, escape the confinement of the pods, he or she will be able to mostly be able to take over your cluster, because every Kubernetes node has its node secret. And if the attacker is able, in most of the time, they are simply files on the file system of the Kubernetes node. So if the attacker will be able to take over these files and these secrets, he will be able to talk, as a Kubernetes node, with the Kube API server. And he has a lot of leverage there. The other way the attacker can progress from here is from a pod. He's actually doing lateral movement in the network, going after other pods, going after unprotected parts of the cluster. It should be internal. But when the attacker was able to enter one of the public-facing pods, then he's going to be able to move in that direction. So this is our threat malware for today. I'm going to show you three things. One is how to reduce the noise around potential application exploits. Second, if how to decrease the attack surface for the node and how to reduce the attack surface for lateral movement. And together, we are decreasing the blast radius of the attack itself. So the first thing is application vulnerabilities. So most of us using different kinds of security scanners in our systems in order to know what are the vulnerabilities inside our software packages in the container images. So these tools are very good. Good tools like Trivi, GRIPE, Encore, Sneak, and so on. But there is a small problem with that. Like in general, at least for our production system, we have open-source images with more than 100, even 200 vulnerabilities, which are really, really hard to handle. And for us as a relatively small company, it's really overwhelming. But even with a bigger company who has more resources, they will have obviously more microservices, more images. So this is not something that scales very well. So it is really hard to handle all these application vulnerabilities and always update them. So it's very, very costly to manage them. So the first thing we are going to use in our CI CD is a new feature by Cubescape. Actually, we are releasing it this week or maybe in the first days of next week, which is, we call it the Cubescape Relevancy. Cubescape is a CNCF project. I'm one of the maintainers I said before. And what we do at Cubescape is we are installing an eBPF agent inside every node. And this agent reports to us back all the file activities on every workload which is running inside the cluster. Now, we are getting a stream of files which are touched inside the workload. This enables us to take the sBom of the container image, which is running inside the workload, cross the information of which files been opened inside the workload with the list of files inside the sBom, and mark all the packages, software packages, inside the sBom, which has been really used and opened inside the container runtime. Now, this enables us to create, remove all the packages, which haven't been touched during the runtime of the container. And we can remove all those which are not relevant, not really loaded, and feed back to the vulnerability scanner. And we'll get a filtered vulnerability scan results list. Now, I'm going to show you in a demo at the end of the presentation. But I can tell you that in our production system, it lowered the number of vulnerabilities by 80%, which is a huge noise reduction for us. And I really, really suggest all of you who are working with vulnerability scanners to look into this. So this is our first component. The second component is, as I told you, is how to protect the kernel, how to remove the attack surface on a Linux kernel inside the Kubernetes node. So in the pod security context, you have all these classical things of what's the user ID and group ID of the container, which either you can change or cannot change depending on the container image. Obviously, the right thing is not to run your containers as root. But sometimes, the container image itself requires user ID 0. So you have to recompile and change it. It's really hard sometimes. The other thing which you need to handle here is the capabilities, Linux kernel capabilities of the process inside the container. And remove all the things you don't need. Or even if the container is a privileged container, check whether you really need it to be a privileged. But I have to tell you that since here the default is off nearly for everything, most of the applications are OK from this perspective. The third thing, which was the thing which we are going to talk about, is actually second policies. Second policies are there to enable you to control the containers inside your pod what kind of system calls they are allowed to make to the kernel. Now, the reason why we are talking about it that I did a small research half a year ago, looked over all the CVs of the Linux kernel, which were showing container escape. And as it turned out, most of them were using system attack. They actually needed to use system calls, which were very exotic system calls, which are usually made by only applications which are managing the node. And our applications usually don't need that. So it is a very good way to protect our kernel by removing all the unneeded system calls. So in order to apply second profiles, either we are using pre-made profiles, pre-made list of system calls our applications are allowed to do. Either it breaks the application, or it allows the application, or the application can run. But usually, even if they are running, they are over permissive. You can, the other way is to do a manual definition of these second profiles and create a list of system calls your workloads are allowed to do. But it is a very tedious job for every each workload. And honestly, we don't usually have the professionals to do this work. Because if you are telling application developer today that ask him what are the system calls you're making, you won't understand what you're talking about. So the best thing we thought is to generate from actual application behavior, check what are the system calls the application is doing, create the recording, and turn it into a policy. Katelyn was talking about it yesterday. So there is a Kubernetes security profile operator. It's a Kubernetes security project, an awesome project which enables you to record using all the system calls your application is making, create a recording, turn this recording into an actual policy object, and apply the policy. Again, what you have to take from this slide is that you're using a premade tool to generate the list of system calls your application is doing. And you can use it also to turn into actual profile object and have Kubernetes enforce it. Network policies, on the other hand, I think the least complex thing to explain here in the security village, I think everyone knows why network security is important and why locking down a different network, unneeded network paths in an application environment is very important. There are reasons to the attacker will need can do if there is no micro segmentation in the network of a Kubernetes cluster. The attacker can do reconnaissance, lateral movement, and can excretory data from other ports through unprotected APIs. So the major problem with network policies in not just cloud native, but in general in cloud environments as opposed to old style monolithic self-hosted environments is that the application we have microsurface architecture with multiple components and it's really hard for it to know who needs to talk to whom. And if you're investing time in it and you're defining it once, you're working really, really hard. But at the end of the day, you're applying it and you might be breaking some of the application features then you have to go back, iterate it, talk to the application developer and so on back and forth and you're creating your application, your network policy. But at the end, what turns out that the application within two weeks changes again and it's again broke because it uses a new network path which wasn't used before. So it's very, very hard also to maintain because it is spread around multiple functions in the organization and there are a lot of things to break. So here we also decided to go after an automated tool, inspector gadget, another CNCF project. I think it's got to sandboxing in a month or two months before. It's a great project. Again, same thing using eBPF to detect who's talking to whom inside the Kubernetes cluster. The inspector, you can run the inspector gadget as a record mode. It will create you the list of who's talking to whom and then you can turn it into a network policy object in Kubernetes and apply the network policy which is actually the network policy object where we reflect the actual connections itself before. So think about the following. Had we have a magic box where we are throwing our application with all of its workloads inside the box and everything it needs, everything it runs and also out of the box comes a short list of vulnerabilities your application has. You really have to concentrate on network policies and security and second policies. So it would be really great. And why it is really, really great? Because this is what we're good to hear. We are really good at automating things, right? We really love it. If you really have to work manually, we'll break things always, we'll have all of these problems. If we can automate all of these processes, we can earn a lot with this because we can have automated security. So it will make our security people, our DevOps people and DevSecOps people very, very happy. By the way, all of the images here, I've generated them with mid-journey. So it was a really nice thing to play around preparing this presentation. So they're smiling here, slightly, by the way. So this brought us really to the concept of if we have CI and CD, we should have continued security, right? Because it's a really good approach to trying to hook up all these things in our existing processes. In our CI-CD, we're already running tests. We are already doing a lot of things of testing out application behavior. If we could capture all this information during the testing phase, we could actually turn these behaviors into policies and apply these policies into our systems. So we should improve our security much better. So let me go through the simple way of how we can do this. So the first thing is to create a namespace where we'll throw off our components and we'll test them. We start recording with all of these tools, either of those are just one of them, and we can deploy the application, run the tests on the application, stop the event recording when we finish the testing, generate policy objects. Now we are rebuilding the application with these policy objects, applying them to the Kubernetes cluster, all of those, re-running the test in order to make sure that we haven't generated policies which are actually breaking our application. And after we retested the application, we are committing these objects into our Git repository, so they are picked up by Argo in the production. So, I don't know, is there anyone who saw my teaser at Twitter before coming here? Like, I've promised a joke, but actually about Inspector Gadget, the panda and Captain Cube going into a coffee shop in Amsterdam. This is the picture, mid-journey generated from it, but I couldn't come up with a joke. I mean, I'm sorry, but I think it's cute. At least the people told me it's cute. So, what I'm going to show you is I'm going to show you a demo of all these three things we talked about. I'm going to do a small environment setup. We are going to see how the second profile is generated. We are going to test out and prove that the second profiles are working and indeed protecting us. We are going to do some network policy generation. Again, using the testing phase, we will test out the network policies. And at the end, I'm going to also show you the vulnerability reductions I've told you before. So, let's hope that the streaming is working. Okay, so the first thing is I'm creating a mini-cube. By the way, at the end, you will see I'm publishing a GitHub repo with all these things as goodies and examples. So, I'm installing in the mini-cube the search manager. I'm installing the Kubernetes security operator. I'm installing InspectorGadget and Cubescape, all three things during the installation phase. By the way, I'm not sure that you have seen the mini-cube starting up so fast. I have edited the video. But now, the first thing I'm doing is, actually, I'm running the test for creation of second profiles. So, the third thing is I'm creating the recording objects for recording all the applications I have in my namespace. I'm creating the applications, and then I'm waiting for other deployments to start up. After the deployments have start up, I'm running tests for 60 seconds. We are not going to wait here for 60 seconds. I've edited the video, but believe me. And after, sorry. So, after it, I'm scaling down all the deployments. And after, which triggers actually the generation of the second profiles, which you can see on the screen, after the second profiles have been generated, I'm reapplying the second profiles which have been created to all of the deployments automatically, and restarting the whole application. Sorry. You can see that we've created all these, during this phase, we've created all these YAML files with the profile objects themselves. I'm going to open here one just to show you what you have in the YAML files. These are the second profiles. So, you can see here a list of different system calls the application is doing. As you can see, it's not really good to generate this manually, but it's really great to generate them automatically. So, what I'm doing now is I'm trying to show you how it protects the cluster. So, I'm trying to open a shell on one of the pods, which is protected with the second profile. The thing, what you're going to see is that you don't see anything, which is kind of cool because I'm trying to open a shell here and the shell is not opened. It is not opened because the shell itself uses system calls, which the application haven't used, and therefore the shell is not allowed and it is killed by the system.  You can see at the security contacts of the pod, you can see here the second profile with the JSON file, which contains all the system calls. I'm deleting and restarting the pods after the editing the deployment. And what you will see here, that I've removed the second profile, is that I will be able to actually open a shell. You can see here the second pod is the one who's been the second version which is just been created. I'm doing a shell, trying to open a shell using exec. And you can see that I was able to, without the second profile was able to open a shell. Now again, just for like explaining shortly, let me just stop it for a sec. So, the way I've presented, I didn't try to do an actual attack on the Linux kernel, I just show it through the second profile works through the shell I tried to open. But think of it, most of the use you're getting out of this is not just like protecting against processes which are shouldn't running inside your container, but you're protecting your kernel as well. So I'm showing the second process where I'm creating network policies. So I've enabled the recording and restarted the hipster shop application. By the way, the application is called Google Microservices application, which is a great demo app for these things. I'm again recording all the network events. After I recorded all the network events and run the application for a minute, I've generated a network policy file, which I'm going to show you here. Again, I'm using Inspector Gadget. So I'm opening the network policy object and you can see these network rules that which pod is allowed to talk to which pod inside the cluster. Now I will show you that it's indeed, it's working and protecting your cluster. So I will try to, as you remember, I said that the attacker would come from the first public-facing pod. So in our case is the front-end workload. Here I'm opening a shell on it and I will try to access the Redis component inside this demo application, which should be the database in this demo app and would be very logical for the attacker to try to exploit. In general, they shouldn't be talking one to another. They should be like, the front-end should get information through other microservices from the Redis. In this case, I'm opening a shell and I'm trying to telnet into the Redis cart Redis component to its port. And if it succeeds, then it will say that it's connected. If not, then it won't say anything and you can see that it's stuck because network policy is protecting actually this pipe and I'm going to delete afterwards the network policies just to show you that in general, they are able to talk to one to another and there is interesting thing here because in Kubernetes native network policies, you have the ingress and egress part. So you're protecting from both parties. In our case, I needed to delete both of the network policies both for the Redis and both for the front-end because one of them is denying going out to the Redis. The other is denying accepting from traffic from the front-end. So now I'm trying to, after I deleted the network policies, I'm trying to connect the Redis cart and I'm going to be, it's very surprising but because you don't have network policy, you can connect and it's not good obviously. And I forgot how to use telnet properly, sorry. So, and now the third thing is the vulnerability scanning. So I've installed Cubescape in the cluster and deployed again the application and Cubescape is scanning the image vulnerabilities in the background and what I'm doing here is I'm after it's scanned already continuously the vulnerabilities and it has all the information and let me stop it for just a minute to explain you. It generated two vulnerability objects. Both of them are in SPDX format. One of them for the base image, not the base image, for the image itself. The second is based, vulnerability list is based on the actual application behavior. So we can compare them one to another here and you will see that in the case of this worker which I chose, which is called recommendation service, I will try to extract the number of vulnerabilities through the Cubes CTL to show you how many critical vulnerabilities you have in this application and you have seven. Now I'm trying to show you that you have high 74, again, 58 medium vulnerabilities which is kind of a lot but now let's check when we overlay the information of the runtime from DBPF which I told you how many actual vulnerabilities we get after the filtering and you will see that it is much less which is actually a kind of point of this demo. So I'm trying to find how many critical vulnerabilities I have. Only three out of seven are indeed in the memory. 19 out of the 74 of the high and 17 out of the 58. So we have a huge number of vulnerability reduction here and I can say that even this is very well maintained, these are very well maintained images. So we've seen images where we got like 90% out. So this was the demo. I hope you could follow because it was a lot of information. I'm sure for like in a short time. Okay, so this means that our DevOps is like really, really happy and also not just DevOps but a security guy and also developers because they've saved a lot of time and now they have time for cakes and I don't know what the drink is, but it looks good. So let's talk about what is wrong with this because it's nice for me coming up here and promoting an idea, but let's talk about what's wrong with the idea. So what we noticed actually when we install this in our systems and this process, we noticed that we have to allocate much more CPU for this EBPF based tools during the testing phase and it costs some money. I cannot deny it, but it's not too much but you have to be aware of it. The second is that these tools, although they are great tools, CNCF tools and I can say a lot of things of them but they are not very broadly adopted. So there can be like some usability issues and so on.  Also things like a few of them are managed through CRDs which are kind of, we've talked about it with Kellen here that like in an imperative process like a CICD process is sometimes really hard to follow what's happening inside the CRs. And obviously when you are missing some of the test paths in your CI CD tests, then actually resulting policy objects might break your application at the end because if the real application is using different paths then you might get to broken policies or broken applications. And also if your system is incomplete when you are capturing this information, obviously again your policies will be broken. Think about the very smallest thing we didn't have in our dev environment, we didn't have our Prometheus app and no one was calling into exporter APIs. Therefore when we promoted into the production, when we started to use the exporter API, the expert API wasn't answering because the network policy logged it out. So you have to take in these things to account and go more, do these information captures more in the direction of CD than CI. But what's good? So what is the positive things? So the positive things are actually you are improving your security posture by like far. Like adding network micro-segmentation, adding sec comp profiles limiting the number of vulnerabilities you have to follow and update is like something that's really like by order of magnitude raises your security game. And I know that it's cheating to say that set up once and forget it. It's not always true and you always have to have some maintenance but in general it is like any other CI CD process we have and you have to sometimes maintain it but you are earning a lot of value from it. And you are really getting into the fence where what you call least privilege principle is applied for sure because you are only unable of things which are in use. So I've created this demo repo. You can scan the QR codes. I will let you like give you a minute. You can jump here. Actually, I have to say it was working on my machine. So, but if there is a problem I think I would really like to maintain this like in a way that's to promote the idea. So if you are getting into problems just open issues and I don't know we'll like sort it out and I would be really happy to like make of use it as a educational repo for people who are want to implement advanced network policies and second policies inside their clusters. Also about the Cubescape which is I've added to this presentation but it's not released. It's going to be released next week. So if you are interested in the vulnerability part you have to wait until next week and you will be able to use it as well. So that's about it. Rate my talk, send me messages on CNCF Slack or on Twitter on I don't know Pigeon or something. You're more than welcome. And if anyone has any questions I'm open here for questions because I see that I was able to make it which is great.


If you want to verify a scientific study, you should get an undergraduate and then a graduate degree in the field of study. Read the literature, typically several dozen to several hundred articles relating to the study. Secure a grant or a self-fund your own study on the same topic. But unless it's your career, you don't have time for that. However, everyone should be able to read the study. So let's talk scientific papers. A peer-reviewed paper is the gold standard of research publication. To publish a peer-reviewed journal, the author writes a paper and submits it to a journal. The journal's editors prepare, or have the author prepare, a blinded copy that removes any identifying information, like the author's name or location. The blinded copy is submitted to a group of professionals working in a similar field. Most of the time the paper is sent back with requests for revisions and clarifications. The paper is only published after it passes the review process. This usually takes a year or more. Now in some cases, particularly fast developing fields, say research on an ongoing pandemic, authors will publish studies to the web. No one can stop them. However, if their research is legitimate, it should have all the features of a peer-reviewed paper and be in the process of being peer-reviewed. So what does that look like? So a scientific paper begins with a title. The title is based on the fact that tens of thousands of papers are published every year and no one could read more than a fraction of these. But you can title scan, and most titles can be understood by anyone with a reasonable education. Minus perhaps a few technical terms that would be known to specialists in the field. Now if the title indicates the paper is of interest, you then read the abstract. This is a synopsis of the main results. And this is a little bit more complicated. The abstract is geared for the trained non-specialists. And so here's where you'll start to see some of the more technical terms. Now you might think the next thing is the paper itself, but the next thing you really want to take a look at in a scientific paper is the authors. A legitimate scientific paper will also list the authors and their institutional affiliations. And the important thing about this is you can check their institutional affiliations. For example, they might be faculty at a major university or staff at a well-respected hospital. Or maybe their professional standing is based upon the accreditation of an organization they created by themselves for themselves. The other thing to check out is the bibliography. Remember we talked about the hundreds to thousands of papers on a similar subject. That's what we call the literature. The bibliography shows you what the authors examined prior to and during their research. It's not unusual for a one-page paper to have dozens of items in the bibliography. And finally we come to the article. Now the article itself is written for trained specialists. Again, you're probably talking about someone who has a graduate degree in the subject and who's been working on the subject of the paper for several years. And the problem is that unless you have a lot of technical knowledge in the field, it probably won't make much sense. But there are a few things to look for. And let's consider an epidemiological study. A legitimate epidemiological paper will give you three things. Detailed information about the research subjects. Detailed information about the data collection. And in-depth discussion of the limitations of the study. The population is a group on which the study was conducted. And things to look for. The number of research subjects. Generally speaking large studies are more reliable than small studies. But you should also look at the variability of the research subjects. So a study of 1,000 people is probably more reliable than a study of 20. But if those 1,000 people came from the same family, then the results of the study might not be as generally applicable. In this particular study we're looking at a base group of 53% of the entire population. The design will tell you how the study was conducted. And again things to look for. Precise definitions of outcomes and how the data was collected. So here the outcomes are defined on a published set of criteria documented by hospital admission or positive tests. And finally there will generally be some sort of discussion of the result. And in the discussion section the authors will describe some of the limitations of the study and possibly how they got around it. Often this section is a sneak peek at what their next paper will be about. Now let's take a look at one of the most notorious scientific papers in recent years which led to the anti-vaxxer movement. The Lancet is a peer reviewed well respected medical journal. And in 1998 they published a paper that suggested there might be a link between vaccines and autism. But if you take a look at the original paper in the Lancet a couple of things stand out. First the sample size was 12 children. This is a very small sample size for an epidemiological study. Also these children were all referred to a single pediatric gastroenterology unit. And so there was very limited variability in the test subjects. And finally the paper had no discussion of the limitations of the study. All of these things should have been red flags that cast doubt on the validity of the results. The study's results were questioned and within 18 months further studies cast doubt on the link. And this study included a larger sample of 498 children and a broader sample by being pulled from children registered with developmental disabilities. What's noteworthy is the first debunking of this misinformation came from scientists and in fact came from the original publication of the flawed report. In other words, scientists did the job they were supposed to do. It wasn't until five years later that investigative journalists published their own findings about the fraudulent report. So what does this mean? Well think of a scientist as a Wild West gunslinger. The fastest gun in the West was routinely challenged by those hoping to make their reputation. Similarly any established scientific belief is constantly challenged by scientists hoping to make their reputation. Now since scientists are human flawed papers and fraudulent results are published but they are quickly identified as bad research by other scientists.


Their purpose in towards us is to be like, man's best friend. They're used to hunt for us, you know, like back then. Why do I care? Cows, we've lived alongside cows as food. That's how it's been. What gives us the right to dictate what your purpose is? Is it power? If we're more smarter than certain species or stronger? We are, we are smarter. So even though they're sent in the experience of the world, what happens to them matters to them. Because we are smarter, we can dictate what their purpose is to us. So it can be to be shot in the head, cut up into pieces and eaten. I think so, yeah. If a group of beings are smarter, they can dictate what another group of beings who are less smart what their purpose is, yeah?  It is Nazi thought. Because we're more powerful than a certain group, a minority or those who are less intelligent, we can do what we want to them. Because we say so. We could do that to different races, we could do that to people of different intelligence. A race of aliens could come here and do that to us. And we'd be screaming out, this is unjustified, wouldn't we? Yeah, I can see. So why do we get to do it to other animals? Is that not hypocrisy?


ow wow that's incredible thank you so much so my question is like the Gutenberg has been a hot topic for such a long time and we've seen like a massive change that it created and now every bit of information is about AI so our company has been developing an AI software that will help basically any firm a company who deals with um customer support and make it automatic so it's called Sappilot for everyone and my question is how how soon do you see this Gutenberg and AI integration and what should we expect in this term yeah thank you so much thank you thank you in my entire career in technology which is about 20 years now I've never seen things moving as quickly as they are right now it's really incredible and it feels like entire years of progress are happening in weeks or months um in the AI in the AI field and uh so I think that some really cool stuff is shipping I actually just a few days ago Jetpack AI launched with a number of blocks and everything we're still figuring out pricing models and usage models and everything for this new technology um but the the other exciting thing is that like the demos are amazing like check out the Jetpack AI stuff and it's not just the demo you can actually run it today and create content and very soon it'll be able to like create blocks or maybe entire themes you can already ask chat tbt to write wordpress plugins and they they execute it's weird it's it's it's read all of wordpress's code it's read all the 55 000 plugins and themes um so it already knows us you know and that's why I think I've said it many many times but I believe that the two mega trends of the next 20 years are going to be open source and AI they're highly complementary because when you think about it AI is going to want to as AI is building things it's going to do it on open source frameworks and technologies for obvious reasons the same reason we all open source um I guess the final thing I'll say is what's deciding is like the the really cool stuff we're seeing is the worst stuff we're going to see it's going to get so good so fast so I think we're still on like the MS DOS command line versions of this but like literally later this year I think it's going to get much better and I think you know as we start to look to like this time next year when we're back we announced where work camp is going to be next year nope nope I won't spill it then what do they say uh no wordpress or automatic it's a ship that leaks from the top the uh the it's it's I I can't wait to see what's going to be around and um it's going to put so much power that it's a very democratizing technology it's um just like one of the most beautiful things about technology is like um you know Tim Cook's iPhone is not better than the iPhone that you or I have and how amazing is that um so like we all have access at some level to to these technologies and you know for free now on barge chat tbt other things we can all get access to essentially the most advanced new intelligences in the world and it does almost feel like we're we're creating a new intelligence or I won't call it a form of life but definitely a form of new intelligence so um if you know I think I said this but you know in 2016 I came on stage I was like learned JavaScript deeply that's right and um that's actually gone pretty well so thank you good job we like basically most new code and wordpress now is JavaScript and what we've done with Gutenberg and everything has been pretty incredible and um and obviously JavaScript has become kind of the standard of uh most modern development um I would encourage everyone here in this room to be playing with these tools uh play with chat tbt play with other AI tools the open source stuff is catching up really quickly and um I would encourage you all to be spending at least a few hours a week um following up and just honestly just playing with it it's an amazing personalized tutor you can use it to ask questions you can use it for rewriting your posts there's just it's the possibilities are endless and as you get better and better just like in the early days like some people were better at googling than others and that was kind of a competitive advantage what they call prompt engineering or talking to the AI and asking it what to do in an intelligent way you can get amazing results so if you if you try it out and it doesn't do what you want um keep trying keep playing with it and like look up some of these things um I feel like this capability is going to be as important as like literacy or typing or something like that the ability to leverage these AI's so everyone learn AI tools deeply we also yeah there is also a current and I think currently active discussion happening about AI in WordPress particularly um someone on our social and or things team will share that that link but there's an active discussion at the moment so you can join that as well yeah thank you hi uh I'm adam I've been doing some work on WordPress playground and I don't have a question I just wanted to share something I'm excited about that I'm just starting to realize during this conference because WordPress playground is WordPress running in javascript it brings WordPress to all the devices where we could run javascript apps which means you can build a native mobile application using WordPress program ship it in App Store a tablet app a desktop app my colleague Ella sitting over there she's working on a notes application that allows you to write notes in Gutenberg and then synchronize them over all your devices so we may see the entire WordPress ecosystem storming over the all all the devices that we're using every day WordPress will be everywhere yeah so imagine building a mobile app that's just a WordPress plugin and then you just ship it on all the devices and oh yeah uh and maybe even creating it in Gutenberg by clicking things and if you want to change how it looks just apply a different theme so just something I wanted to share thank you just spend a day in that way hello my name is Patricia I'm from Geneva in Switzerland I'm a community contributor by organizing local meetups and wordcams um my question is the usual suspect in Europe at WordCamp Europe is a GDPR or multilingual yeah the second one so basically basically a lot of people are eager to know uh an approximate ETA for the end of phase four or when we will be able to use multilingual in the Gutenberg editor or the Gutenberg project wow protect the future I think we said something on stage before do you recall we said phase three we're starting next year we're starting now like but we're starting at this yeah yeah after 6.3 we'll start with phase three properly I think there's enough overlap there that we can start getting a clearer sense of when phase four can happen I think it's also good like for example we're thinking about like what I don't know in like five years we're like AI for translation where it's going to be like and yeah how can we like make sure that we're building towards for that leapfrog yeah yeah we're like we're not um getting too ahead of ourselves in there um but it's like I think like maybe next year like we can start with some and I think you have a community exploration plug-in that's kind of taking a look at that not you Patricia you Toby next to you I think that's right I know that's great sorry everyone who's watching this I actually brought up my question from last year I was planning to say Matt that okay uh I can talk more about that thing with you after consuming at least one ticket tonight I hope it will digest well that ticket of it um but yes it I get the feeling now that when you're talking about maltylingual you're talking about some machine translation and you want it to be good enough so but when I hear that I tremble with because to me machine translation yes it is getting better by the week but my view is and a lot of people who are with me on this that it always needs to be checked by a human before you publish it and therefore I don't see a reason to delay the maltylingual part of uh WordPress core too much because it's more about making a decision and then and just to clarify where it's not um we're not delaying so WordPress is fundamentally trying to be a content management system for everything and so the the complexity of maltylingual becomes that now every single object in WordPress categories tags blocks everything which right now is kind of like a one to one relationship or you know the data types has to become a many to many relationship that's part of why we have to do collaboration and workflow before we get to maltylingual because we need to have workflows for how when something is changed in one language it flows to another language so we're very much now whether you're choosing machines or humans to do the translation that's up to the site owner um I 100% agree with you that I think that for many many many publishers you know across Europe for many many reasons it will be human driven maybe they'll use a machine to accelerate the human but like you still want a person kind of saying like this is the content that that we're publishing on the website you're not just going to take what's automatically generated so um it's but it it adds uh a multifactorial level of complexity to all of our data models and doing that right is part of uh it's going to be the most complex thing we've ever done in WordPress and so that's why we're we're really um I would actually extend Matias's timeline sorry I think we need like 12 18 to 24 months of phase three before we can really start breaking apart the data models in WordPress and we need to figure out how to do so in a backwards compatible way which is going to be you know because we we go backwards compatible basically to like WordPress .72 so it's like 2003 so we need to um we need to figure that out before we move on to your answer of that Patricia I want to help you reclaim your time and make sure your question got answered I messed that up I'm sorry did your question get answered with that yes thank you very much oh cool thank you yeah no I just want to say also that's that's why like it was important to like conclude phase two where we're like essentially making all the aspects of your website accessible to people so they can edit it once we model all of that then we'll have a better idea of like how can we make all these objects also like translatable in more ways and we're still like at contributor day we were like um sort of tossing some ideas on how to connect custom fields with blogs and so then like once we add that dimension we also need to think about okay what's going to be the multilingual story of custom fields when they are connected with logs so it's like it's important to get like the base layer in a good place start developing some of these collaborative editing ideas because I think many things will start falling into place much better and also I think we really rely on all the community explorations that are already going around like how to approach how to do multilingual isn't it just I think that really gives us a sense of like which paths are working best what things are resonating with people and so on that's important to see and the architecture is going to be so tricky like I literally stay up at night thinking about this sometimes because like do we do we do it in a single site model and then make the data structure is much more complex or do we basically do a multi-site model where each language is like a separate word press in the multi-site and then have some way to synchronize them and have workflow between them and permissioning between them so that they sort of appear as one site to the user or as a multilingual site but in the back end where we're doing essentially a multi-site which I think might be a good approach but I don't want to say that is the right approach because I think we really need to spend many many hours like actually kind of building some of these different approaches and just trying them out looking at all the plugins out there and like seeing what because performance is going to be so important and so we you know WordPress is getting faster and faster with that release we want to make sure as we add this complexity that we don't slow it down. Also like the translation UI there's really cool explorations happening on the Glotpress side on how to translate the software itself like more the interface not the content but there's a lot that we can take from that experience that that's something I think we can get going much earlier to get like information on what works for translators what's the best user experience and so on. If someone can share that live translation link I don't know it off the top of my head or I would say it that would be excellent I don't know why I'm looking up there is someone down here. Folks I keep gesturing to our committers and team reps that are down here to help me. Question over there. Oh we're gonna go upstairs. Thank you. Hello. I'm up here. Michelle Frischat here in New York and the question has to do with mentorship. No panacea for inclusion. It's cutting out. You said I heard you say there's no panacea for mentorship and inclusion. Sorry. There's no panacea for mentorship inclusion and getting the next generation of people into WordPress but mentorship can be one way to help people into the community. I think we do a really good job of our release squats with shadowing and mentorship there with my side projects that I have I'm always being asked to add mentorship to those things but my projects are small by comparison to all of WordPress so do we have any ideas or plans for official mentorship programs in the WordPress community? I do. I'm dying the hero. Thank you. It's a great question. Anyone want to take this before I take it? Just in case. Go for it. Ready to go. Wonderful. So yes I'm so excited. So for the most part when I talk to people who are currently contributing to WordPress or tried to contribute to WordPress and kind of took a break one of the things that makes the biggest difference is whether or not they found someone to mentor them they don't always call it a mentor they sometimes call it a buddy or they're like oh so and so it's just like hey that looks like you are worried about asking dumb questions ask them to me I'm happy to help like those are always every time I talk to contributors the thing that makes the biggest difference for people who want to stay for a long time and so we do we have a trial program right now happening so in our Five for the Future program we have a trial a pilot program I think that's launching today did launch yesterday July 12th where we have asked those companies that are part of the Five for the Future program as part of what they're giving back be mentorship of especially underrepresented voices but anybody who's trying to get started as an individual contributor in the WordPress project I think it's very exciting but I also think it's going to take a lot of time and attention and resources to get it right and so for anyone who also feels like gosh I really succeeded because of this one person or these three people that really helped me to figure out where I was going versus where I wanted to go go check it out someone's going to share it also on social media so that we can see the pilot and keep an eye on how we can help get that done but absolutely 100% I will I will do that until we can't figure out how to do anything better about it I agree hi my name is Jonathan I'm a member of the training team and I work with a few other contributors in the training team creating content specifically for our extender community so plugin developers theme developers anybody writes in code and one of the questions I get a lot from folks is does WordPress have an engineering best practices document handbook whatever the case may be and I know that we don't so I will usually send them things like WordPress VIPs engineering best practices human made 10 up all those enterprise level sort of agencies that have those best practices my question is do you think as an open source project we should have a best practices document if you don't why and if you do what should we start doing to make it happen thank you I don't like my impressions that I think that it's it's very important to have like these the ones you mentioned around like the the extended ecosystem having like a bit more opinionated things and see like more than the core project having like two strong opinions on some things but it's a balance I think like what we don't have like a super formalized things I think it's important to have like I don't know similar to like Apple's human interface guidelines things that we can do for well these are the things that we have learned and we want to encourage other to do like when you're developing a blog when you're developing a plugin or a theme we do some of those things through but I think there's always a risk to become like too prescriptive and stifling some of the innovation and exploration and diversity that can happen in the ecosystem so I think that's the balance that we need to achieve I wouldn't be like super categorical in one way or the other I think it's good to be thinking about it and bringing it up and and also learning from like if there's something that again human made or other agencies or 10 up are coming up that really works and it's really like we can bring it back in but I think it's important to not be too um too stifled with cool I know we're running out of time but we have a lot more questions should we try to go through them quickly or how how are we doing do we need to end right up five or can we go a few I saw a shaking head and a nodding head okay we go a few extra minutes so let's try to go through the the remaining ones quickly so we'll do the people who are still at the mic and then uh those will be the last questions so okay hello I'm toby global mentor for the polyglots first I have a quick question to the room who here does not have english as their native language wow wow so um the point I want to make with this is that um for word press mission to stay true about democratize publishing we really need to make sure that wordpress becomes available uh in a lot of different languages and we are doing that already uh and we are trying step by step but it's hard to add more languages but what I see now is that there are so many different teams struggling with how to get their content translated and these translations maintained I'm talking about training I'm talking about documentation um subtitling um developer I mean so many different things and we need to create some new or additional way of handling these translations in an efficient and smart way and my quick question probably to Giuseppe is do we have the full support from the project we may need financial support we may need some organizational support in actually making this happen I mean I always hesitate to say that you have my full financial support which is what you asked but in general you always have I mean our polyglots always have my full support to make sure that what you need that I can provide that wordpress can provide that the community can provide that you should have it um I I know that sometimes it feels like you all come to me with questions and I'm like I'll come back to you and then a week later I'm like hey you might have forgotten but I said I'd come back and here I am like there's just a lot of things that are that are part of it so I will not pledge anything that I will not be able to actually get my hands on but obviously you all have my full support to get efficient stuff yeah so um we're gonna jump to another question though just yeah so I'm just saying we are going to need other people's support as well because with only one person supported one word thank you thank you it's really great being here and asking questions again I'm Courtney Robertson I'm at GoDaddy I am also a part of the training team um and last year at the same conference I asked about uh getting multilingual working inside of Learn WordPress happy to report a year later we've got many languages it's not elegant it's all in the same site and it's not ideal but uh there was a great meeting that during contributor day worked with Toby and a few others for improving that so ask your questions because you will see progress my question today uh it revolves around I was part of a talk in the WP Connect session on funding open source M5 for the future and it's very very deeply personal to me in my journey through WordPress and to where I am now and I am one of the founding members of the WPCC and I'm happy to have those conversations to explain further what's going on with that I've had people ask even last year Europe was my first time to take a last year's Europe was my first time to take a plane to get to a work camp and there I met Sean from American Eagle and he was sharing with me that it's hard to bring from their organization it's hard to bring contributors in to do something for a particular length of time because without it being organized like they're used to internally working as a team in sprints that gets a little bit lost and this idea came up again yesterday and could we do it in a way that is open and inclusive that maybe organizations could be a little more they would have more transparency of exactly where across are now 22 teams we have 22 of them now um so across the 22 teams could we see that plug and review was needing some more staff could we have a public way of seeing where the needs are across the teams and maybe some initiatives that we certainly want and want to be exclusive but could bring some clarity organization that for this period of time maybe between the holidays some companies have slumps at that time maybe between their holidays they could dive in and do a thing during that time and then move on for a little bit and then come back again so ways of creating opportunities in unique ways of contributing that would not be exclusive by any means and again I think elevating that transparency of what the teams need would perhaps open up more of that staff labor and funding directly to help contributors yeah I have a quick answer here which is an idea I've been thinking about and we'll try to keep this short yeah so I think uh in organizations when I say this work well is you change what you measure and one thing I'd love to get more on wordpress.org is some sort of like dashboards essentially like we have the download counter we have some stats or plugins and other things but like like what if you could kind of look across the 22 teams and each of those 22 teams hatch a metrics attached and like a health metric and you know this was how many work camps there were last year this year whatever each team can define its own metrics but then there was kind of like a red-yellow green for how things were going I think that would be really powerful and then you know that'd be fun for emotivating I think for everyone working on it and then also if you're coming in and you're like okay what needs help look at the red stuff so just want to plant that seed of an idea in everyone's mind thank you. Hello I am Kamrul Islam I came from Bangladesh and I have two questions teeny question first one is will you add volunteer badges on wordpress.org profile and my second question is can I take a selfie with you guys right now right now go ahead and take the selfie why answer your first question oh you're going to come up oh maybe don't come up on stage you could do it from here and I will definitely be at the party and by the way I love meeting people I love taking pictures so all right so while you're doing that it's a quick one yes we could definitely add volunteer badges to the profile pages and I think actually wordpress.org profiles are going to get way cooler over the next year I was just actually talking to you about some ideas around that earlier so definitely something I want to work on thank you. Hi everyone I'm from Libya and I have a couple really quick questions first one is recently I started with three of my friends we started web designing startup and now that we're here in work camp Europe I couldn't pass on the opportunity to ask the great Matt for his advice for us second question is now with the release of Gutenberg and now without bearing into mind that wordpress is a privately traded company Matt do you have any plans to take the company public yeah that's all Matt cool and so to clarify wordpress is an open source thing automatic is probably what you might have been referring to is a privately traded company and then advice for web design startup yeah sure so for automatic I'll just say that it's it's great having flexibility so we're lucky to have like great long-term investors I do wish that more of the wordpress community could could own a chunk of automatic and and just like you can own many other companies in the wordpress space there's something nice about that so that's the one thing that would make me want to be more public but other than that I would say that the flexibility that's allowed for us to make very very long-term bets that's a private company is really nice thank you so much as a as a web design company I would say I would repeat what I said earlier around learning that you to leverage AI tools and also remember that what you're charging for is not how long it takes you to do it or what it cost the value you're generating for your clients so charge based on that value thank you so much matt I appreciate the opportunity thank you thank you and then finally raise your prices almost everyone should raise their prices I think we have one last question one last question all right bring it home hello thank you my name is piotrek and I just came from the sustainability workshop and there is a very specific question that just we came up with is it possible to make one simple change in terms of where all the files for the wordpress repository are stored so that would definitely be a one step further to make it you know more sustainable yeah to choose the proper storage that would generate less co2 so if that's think it's possible to change where the wordpress is so like I'm not sure if I understand we were thinking about many ways of how we can decrease the co2 yeah so this is like minimizing the file size of the wordpress itself as a file oh and then all of the plugins all of the other files everything that is running our ecosystem the good news is that more's law and other things is is on the on our side you know wordpress is getting faster more efficient but if you added up all the wordpresses in the world it's probably like less than one like container boat or something of co2 emissions so yeah I would say I'm a technological optimist in this regard there's obviously so much work we need to do around carbon capture and other things but I think we are on the cusp of abundant clean energy and and that many of these issues we've been dealing with over the past hundred years hopefully we can start to reverse so that that's my optimism that's actually a good place to end yes a very optimistic note so thank you Matt Joseph thank you all stay around for closing remarks thank you thanks to Matt Matias and joseph and thanks to all of you for attending we're nearly finished we've got a few more moments we're going to spend with you all so they party tonight is at lohan nightclub in Athens it is at 8 30 bring your badge you need your badge and you can get the some drinks and I'd like to introduce the organisers shard evangilia and joseph and I want you to give them a massive round of applause this incredible conference thank you so much looks like they're still getting mic'd so I can stand awkwardly on stage for a few minutes while they're all doing that who's coming to the party tonight I'll be there is it going to fit all of us I hope it's a really really big nightclub um so anyone want to tell me their best presentation we're going to invite all of the volunteers up let me go and check are we ready here we go welcome joseph look at the audience so oh you can hear me now yeah wow okay before I start with the closing remarks because I like noise since I am Greek um can you scream oppa for me okay that was good acceptable yep first of all I want to thank you all for being here because without you we wouldn't have work in Europe 2023 uh this is basically the closing remarks so we're going to wrap up the three days of the event it was an amazing experience for us the global leads but also for everyone else and especially for my local team from the team of Athens thank you because they have been preparing for a lot of time to host this event and that made us really really excited so this is it I can't believe it's over yep I won't cry okay shoulder no okay no because I know what we're gonna do next year oh yeah you see yeah so I think that yeah so next year we will be in a few minutes let's start for something extra can I get a new remote please as long as the remote control works of course because we have something to show oh now it works so we were 2545 attendees on the event and in this picture that you will see now there are 94 countries represented wow picture yeah thank you thank you this is just an idea of all the people not even everyone was in this picture because yesterday I think there were more people there could have even been more people on the picture but it's already crowded thank you use a lot of zoom to find yourselves in that picture okay well you can download the picture I think pretty soon from our photo album on flicker.com yeah so this is really impressive yeah it was you are really impressive basically and thank you again thank you so for Contributor Day the first day of the event we have 658 contributors working within 23 teams it was an amazing day with a great set of results congratulations to all and we always work with media partners and media supporters but 10 of them as media supporters and 11 media partners and they sent all the awesome news of wordpress and wordcamp to the world so everybody would know about this event thank you for sharing the news I was never good at mathematics I always failed at that class at school however I do like statistics and numbers and what the world did with us these days is the following numbers that have to do with how many people we reached on social media and on streaming so on social media we had an impressive interaction it goes to 23.2 million interactions 14,000 tweets and posts on Twitter and 2,000 times we have seen mentions on Twitter these days about wordcamp Europe there was content like your pictures your videos and everything that you posted around the conference that was shared 4,000 times unfortunately I didn't have much time to do that but I will do it after the event it would have been higher if you had been clicking yeah and we have been liked people liked us this time really like over 12,000 times in general wordcamp Europe you know okay okay okay they don't like me often but wordcamp Europe is likable yeah pretty good fair oh during these days we had an amazing schedule provided by 102 speakers from 29 countries thank you to all the speakers so we want to hear your ideas your feedback and you can use it our feedback form on our website and share all your ideas compliments etc it's on europe.wordcamp.org 2023 slash feedback please do so and we will use it to make it an even a better wordcamp next year yeah definitely this is going to be very helpful because the content and everything else depends on you basically exactly oh I went too fast I think yes yes we want to thank our great members because without them we wouldn't be able to succeed in this event because it's not only us the global we have another two people that have more knowledge about the community and the event so they are supporting us they are advising us all the way since when we started organizing and that goes back to March 2022 so it's a long time and we want to thank Timmy and Moncho hey Moncho are you hiding Moncho there he is yeah no pointing figures thank you Moncho and Timmy I hope you're watching at home thank you get well soon so of course thank you to all the organizers it takes a big team to create this amazing event thank you all the organizers I'm starting getting emotional we're really proud of them I hope they're proud of us too I don't know but it was an amazing team this year we faced a lot of challenges but you know we're here wrapping the event up so we made it we all made it we all made it we did thanks to all these people with the plutisants yeah we go so we have 13 team leads running 11 teams and I want to thank you say thank you to all those team leads Poros, Wendy, Juan, Matt, Steve, Laura, Matt, we have Marcel, we have Estella, we have Takis, we have Lena, we have Costa and we have Josson thank you lovely team leads thank you very much we would like to start welcoming the teams the team leads on stage to thank them properly to appreciate them and show our respect so thank you attend this services team Uros Uros thank you man now is it done that you call your team you can call in your team my team I need to remember the names I tried this not the best not the best try to do it Vagelis, Marietta, Aleksandros, Nikola, Telma, Tozze, Ivelina sorry oh and now the budget team Juan Hernando the man with the bag the budget team had a real real fun event and I want to welcome Evangelos, Kael, Emma and Justina so we have of course the communications marketing and PR team thank you Steve and Matt come on get your team on stage all right call them in so this year we've been co-team leads of communications marketing and PR so we'd like to welcome up some of our team right now so we have got George, Mike, Karthik, Tom or Pohe rather than George we have Samena and Tom and Mike thank you and we did have an amazing content team that is basically responsible for everything that you attended as talks workshops and all that jazz so oh so I would like to see our two leads again for the content team Laura and Marcel on stage now please first Marcel oh Marcel is here I was expecting you from the other side surprise thank you um please come on stage Kaminesh, Ryan, Francesca, Panos, Anchan, Piamario we cannot be here Nate Finch, Mateos, the Almeida Martins and I also would like to thanks Sabrina Seydan, Matt, Raul de Sarka, José Ramon, Padrán Garcia and all our amazing panel guests thank you good job another great team in this continent we'd like thank you also to the community team Estella Rueva okay so my team let me call them Isota, Johanna oh you start forgetting the name too she's emotional Wahadi Elisa so I guess this is all of us and we are missing Ohaya somebody that worked with us the designer of the Wapu but she couldn't come she couldn't be with us thank you thank you so um thank you for a design team Lana come to the stage so this one is responsible for our desserts our branding our website yeah she's doing the branding the website everything the shirts the colors lovely thank you thank you so Deborah, Johanna, Sofia, Vangelia, Vangelis, Fotis, everyone thank you because we have usually some technical problems and we need support never happens well we had to establish an IT team this year to take care of the tools that we're using and several other things we are constantly whining about when we are organizing so we'd like to thank our IT team Padelis, Pascal, Fotis and Nemanja and now the incredible amazing well other things local team Takis this has been so amazing having a work in Europe here in Athens I cannot be more excited on that thank you very much and thank you to my team Nikros, Eli, Kostakis, Giannis, Yakovoz, Panos Fotis, where is Fotis? Fotis come here. Come on Dream Team, come on Dream Team thank you so much guys you have been an amazing team thank you so much thank you all and thank you thank you to the people that managed to show us the money Zesong thank you sponsors team so thanks for the sponsors so this year we are 64 sponsors who made it possible because we raised the money thanks to them to the budget so the team is composed of Anna Mikke, Dean, Angelos, David, Lukas, Marion and Marine thank you and also thank you all volunteers thank you we had 142 from 40 countries it's amazing and without these volunteers it wasn't possible to run these events yes I know there are a couple of teams waiting yeah somebody mixed up the slides so your volunteers you will get on stage afterwards because we have a few more teams so that is the thank you Wendy volunteer team so right so when you call in your team thank you this was the for the unicorn joke okay so I want to thank my team Aida, Angel, Francesco, Jelena, Stefanos and Sveta please come up and we also have three people that are unfortunately not here Stiana, Jose and Gebenga but they worked all year as well so thank you to them I hope they're watching at home and now is the moment that we get to the stage to our amazing volunteers please no no no we'll have another one no really look you see that guy over there waving no no no no no okay there is okay there is there is a mix up here um of course the photography team is very important and actually we wanted to have all the volunteers on the stage so the photographers could take the picture thank you so have it your way the way you want to do it cost us you decide thank you which order I only want stage my team good go ahead that's it nilo nilo come come on stage okay we have a photographer we have someone to take the photo don't worry nilo nilo come come on stage and Elise Nastia and Jelena and please welcome all the photography team who stays thank you very much I'm gonna take this thank you no it's safe here well safe safe there so basically we are proud of them because they take our portraits for the social media we're gonna change Facebook Twitter profile pictures later we wanted to have them taking more pictures but we will do that later can I have a very very nice smile for all of you since we're getting a family picture for what came Europe yeah we can do it smile say cheese cheese we go I guess this is it right I mean enough photos for today we have enough of it then now we can slowly proceed calling our volunteers yes let's go ahead volunteers please volunteers thank you thank you all for this side for this side thank you all thank you volunteers thank you thank you stage is big enough sir sir you won the line number three you are a volunteer also okay oh okay Milan don't fall the one hey Moncho you are a volunteer also come the one and only Milan Ivanovich and Moncho it's a crowd huh yes it's crowded amazing so another family photo did you call it's my call yes I know we we're gonna take another family photo first still more okay we'll do it you deserve this moment please stay in stage so we want you near stay on the stage we are getting very emotional and we we need your help you need we need your support I'm gonna keep thanking people now that we are here because I'm good at this okay so we want to thank our closed captioning staff because they made the event more accessible we worked again with a specialized human closed captioning company in order to provide everyone with the best captions in a live event and make wordcam Europe 2023 even more inclusive so thank you very much for being part of this and for giving us this kind of assistance it was really necessary yes it was thank you very much thanks also to the Megaron staff for doing the best they could to welcome everyone of us this was an amazing venue for the event we are grateful for it thank you also thank you to the volunteers of the Red Cross and they have been a wonderful assets to this event again they supported a couple of people thank you very much for your voluntary support thank you yeah thank you for keeping us safe basically yeah and now we have to thank our sponsors because without them this event wouldn't be reality because they have been supporting us they have been funding us and i'm gonna start with our super admin sponsors thank you house singer thank you jetpack thanks to our admin sponsors blue host elemental google ionic type grant we're glad blue and wp engine and we have the editor sponsors cloudways paypal lepros and yours thank you very much for your support thank you thank you very much also for the generous support of our author and small business sponsors because the small businesses are always part of what can be events and it doesn't matter if you're not a huge company you're still part of the word press ecosystem and thank you for being able and willing to support us thanks also to our micro sponsors this year we have 103 micro sponsors thank you please be sure to visit the sponsors until the end it's the moment do it yeah here's the time to say goodbye it is time for us to say goodbye and we're very grateful to have the opportunity and to have the opportunity to help build such an amazing event as work in europe in athens and now it's time yep to click to the next slide yep and introduce to you the new global lease for 2020-2024 Juan Hernando this is it we're done we're leaving good luck thank you so much good luck with a bunch thank you thank you for all your work we were going on vacation all three of us i hope you have a good time thank you let's go people thank you so much for all your hard work thank you for all your hard work and now the big moment you have all been waiting for the revelation of the work in europe 2024 host city it's going to be it's going to be 24 and let us introduce to you as is customary i am passing the torch to you first of all let me welcome Enrico for the wonderful video thank Enrico i'm thrilled to host World Camp Europe in Italy and in my beloved Torino and the Italian community is ready to welcome all of you in our Torino so my question is for you are you ready to book your trip and accommodation for the next World Camp Europe ready to welcome you a can't wait thank you thank you so much Laura and now in order in order to make World Camp Europe 2024 happen in Torino we would like to invite all of you to apply for organizers for that year our call for organizers is already open in the new website europe.work.com.org slash 2024 and we're waiting for your applications we want all of you with us sorry sorry before we go to Torino we need to party right this is happening tonight we are going i need to read it i'm sorry um we are going to have a 20-year anniversary party so bring your best outfit and the after party will be at the low hand Athens club tonight starting at 8 30 you will need your badge to get in and there is a hard limit of 1500 people so don't be late we hope to see you all there are we moving on 1500 i already told them two free drinks and light snacks two free drinks and light snacks see you in World Camp Europe 2024