All right, welcome to troubleshooting, hidden performance and cost and network traffic across multiple AZs with eBPF. Who here knows what eBPF is? Oh, we're done. You want to come up here? Yeah? OK. Awesome. Then we'll get right into it. I'm Nero Maitha. I'm a principal specialist solution architect at AWS. And I work on containers and serverless services and focus on observability. And a few months ago, Shahar and myself, we were talking about some of the customer problems, some of your own problems around visibility and network. And we started coming up with this idea for this talk. And so I'm joined by Shahar. Hey, everyone. I'm Shahar Azilay. And I'm the co-founder and CEO of Groundcover. Groundcover is a full stack observability platform built for cloud native environments, which uses eBPF, which we're going to talk about in this talk. Yeah. It looks like there's a lot of eBPF fans here. Who likes eBPF? There we go. Louder, louder. So why are we here? Why does eBPF matter? Why does visibility, observability matter? The Amazon CTO, Werner Vogels, he said a few years ago, everything fails all the time. Who's seen this slide before? Who's seen this quote? It's true, right? This is our North Star. This is our architectural principle at AWS. This is what drives what we do at AWS and also what we tell our customers to do. You have to be aware that everything fails all the time. And so that leads to an architecture that centers around resilience. You have to design your systems to be able to deal with those failures. But resilience comes with trade-offs. Sometimes it could be expensive. Or you don't know the cost of it. So what is resilience? Resilience refers to the ability of workloads to respond to and quickly recover from those failures. And we think of a mental model to help us think about resilience. On one side, we have high availability. And that's the resistance of your system to those failures through the design of your system. And then, disastery recover. So how fast can you recover when there was some kind of failure, something out of some high-impact failure? So together, this creates a spectrum that we think of as continuous resilience. And one of the main components of continuous resilience architectures at AWS is availability zones. Who here knows what an availability zone is? So this is just a quick recap. This is a perfect audience. They know EBPF. They know AZs. They can come up here and do this talk. So AZs are availability zones are one of our core components for designing for resilience. And these are fully isolated, one or more data centers in a specific region that are connected through highly available, fault-tolerant and scalable connectivity. And they're kind of like independent units. And this is the cornerstone of building our systems with resiliency in mind. All of you, I hope, are using more than one AZ in your architectures and your systems. Good. Now, keeping AZs in mind, we now are at KubeCon, right? So we have to talk about Kubernetes. I mean, I guess we could talk about something else, but we talk about Kubernetes. The Kubernetes networking is a different paradigm. So just a quick recap with respect to Kubernetes services. If you're new to Kubernetes, this is the main core component of networking. So a service enables load balancing to your pods, right? So in this case, we're going to be talking about back-end pods. And there's different types of services. Mostly you see two different types, which are cluster IP, which is used for internal cluster communication. And there's node port as well, but that's not as used as much these days. And then you have a load balancer service. And that's usually to expose your services externally. So for our conversation today, and I think about this as a conversation, even though I'll ask you to do questions and answers afterwards and find us afterwards, because I do not want to stop you from the party going on upstairs, let's think about a typical service that you might be running in your Kubernetes cluster. You have your external customers or your clients. They send a request to a network load balancer, for example. And then that goes through kube proxy, which then communicates to the node port service, which then communicates to the cluster IP service, which then load balances those pods across or load balances that traffic across different pods. So for this front end pods service, we have three pods. Now, what you might not be aware, and it depends on the architecture, maybe not, there we go, is these different front end pods are in different AZs. And so there are some considerations here with respect to network topology, performance, and cost in this load balancing between AZs. So for example, that kube proxy service is at ADCA. Did you know that? I don't know. And it's load balancing across these two AZs. So already, with a very simple service, we have cross AZ network traffic or opportunities where traffic are going from one node to another within your cluster crossing those AZ boundaries. Are you aware of where that traffic is going? How do you know if that's important or not for your resiliency design? Now, that front end pod, most of our services aren't just one pod. That would be amazing. Most of them are complex. So that front end pod now has to reach out to a back end service. And that back end service is on the same cluster that goes through cluster IP that's running in some kind of AZ. And we're a small company. This service is very lightweight. And we just need one back end pod. And it's just going to the same AZ. Awesome. But all of a sudden, it gets really popular. I put Gen AI into my application name. And all of a sudden, the traffic goes through the roof, right? Oh, man, what am I going to do? So I go to the back end deployment replica set. And I set it from one to three. And what happens? Tell me what happens. We get more pods, right? So now new pods show up. Those back end pods are in three different AZs. Now, I didn't know that. Maybe I'm just an application developer. All I did was put Gen AI into the title of my application. And all of a sudden, I got to scale up my service to thousands of pods. And this is a very simple example. This is about as simple of an application as I can think of. And all of a sudden, we have new things to consider, hidden trade-offs that I did not know about and that you might not know about. So first of all, we have service complexity, right? Just this front end and this back end. It's just three pods each. And we now have N squared traffic configurations that can coexist at any given moment in time in my cluster. And this is just one application on one cluster. And it starts to scale complexity-wise very rapidly. Then we've got cost considerations. That front end pod is in AZA. And now it's load balancing to AZA, AZB, AZC. And there's cost implications in terms of network traffic and resources that I might not know about. Maybe I wanted all that traffic to only go to AZB. Don't know. And then there's performance and reliability considerations. So these are just three considerations in terms of the performance. Maybe I wanted that traffic to only go to the same AZ. And the data on that back end service is better in AZA. And so, I meant AZA, AZA to AZA. And so these are all the considerations and hidden trade-offs that I need visibility into to make a better resiliency decision. So gaining visibility for resiliency decisions, we wanna make the best decision on resiliency trade-offs as possible, right? I'm an engineer. I gotta respond to this architecture. I'm on call. I wanna make sure that I'm making the best architectural decision at any given moment in time. So we need visibility into what services are talking to each other, where those services are running, the metrics that matter to those services, right? So it could be latency, it could be cost, it could be CPU usage, it could be pod-level networking. It could be all kinds of things. And then the telemetry has to be correlated to the Kubernetes resources so that I know what is talking to what at the Kubernetes context, right? With Kubernetes information, resources, and metadata. So what do I go to first to get this? Prometheus, not bad. I can get metrics for the pods, the containers, and other services, the node, but it doesn't give me where that traffic is going to from one AZ to another. And it doesn't necessarily give me information about the performance between those services. So then I start using open telemetry. Who here is using open telemetry? Awesome. So I can start tracing, and that gives me some dependency map and understand what services talking to what. But again, that doesn't have all the information at the AZ level that I might need. So I take a look at VPC flow logs, right? But this is awesome. I get a good understanding of what packets are flying, what transactions are flying through the network. But VPC flow logs don't have anything to do with Kubernetes. I don't know what that IP address is associated with, the front-end service or the back-end service, don't know. I can look at ENI metrics, but that's mostly around IP address allocation and what's the IPAM service is looking like if I'm gonna run out of IP addresses. It kinda gets me a little bit of information, but not what I really need.  That's great. Those transactions were going through a load balancer first. And I need to make sure that I understand where that's going to in those different AZs at any given moment. But that's a separate system and it has no idea what Kubernetes pods are running, what namespace, what service, et cetera. So this gets me some of the way. It gets me some of the good data, but I think we can do better. And so I'm gonna go over to Shahar and see how we can do better. There we go. Wrong thing. Well, thank you for setting the stage in your while. So we all got kind of the ground stated together of AZs being important, right? We have to have this resiliency. Most of you are probably using it in some form. But getting insights of how this actually works and how to actually manage this specific trade-off that AZs represent, that's still kind of hard with all the tools that Nirmal just kind of went through. So before setting up into building a new land and kind of figuring out how EVPF can help us, let's figure out what we're trying to improve, right? With the current state of tools you guys all use in your current cloud provider. So the first thing is service identity. We're using Kubernetes. This is a Kubernetes conference. You guys are using the Kubernetes infrastructure. We have to relate what we're seeing in things like VPC flow logs and all the tools we have to the actual Kubernetes entity, right? And it gets even worse if we're looking at VPC flow logs. You see IPs and ports, that's great, but that's only relevant for now. What happens a few hours later where pods get replaced? That IP is no longer relevant. You can't even use it to figure out how to troubleshoot your Kubernetes environment even if you had the ability to do so. And the second thing that we usually overlook is the carnality of the problem. Where you're looking at things specifically like VPC flow logs, these things represent millions of events just flowing in, basically saying how much traffic has been transmitted between different IPs inside your environment. But we want to use metrics. We want to measure trends. We want to figure out what's going on. Even if we could attach some entities from Kubernetes into these VPC flow logs and say, this IP is actually this pod and this deployment, even if we could have done that, how are we going to aggregate all this stuff into usable stuff that we can actually take decisions by, right? Knowing that a specific pod at a specific time did something and transmitted something, it might not be the best thing to make a decision of whether I need cross-AZ communication or not for my system. And the third part is lack of action and ability. Even if we know something about what's going on, there's so much information and so many pods running in your Kubernetes cluster that making decisions by it, we're going to have to get some more information, like what API is actually carrying these cross-availabilities on communication? Did I intend to do that? Or is it just a random API that I know that isn't something that I plan for my resiliency? So before we dive into what we want to achieve, let's just name it. We want a Kubernetes-aware network sensor, right? That's what we want to achieve. We want something to be aware of the infrastructure that's going to help us make decisions about whether this cross-AZ communication is something that we intend it to do, like you do in everything, even in setting your request to limits in your pods, right? You intend it to do so. So between AZA and AZC and these drawings, there's a lot of different network streams. The first thing we want to do is make sure that we tightly link that to the Kubernetes infrastructure. We want to name the pods on both ends on each of the streams. That's kind of intuitive, right? The second thing we want to do is aggregate it to some level that makes sense, the carnality you can work with. And the first thing that comes to mind is the carnality of the Kubernetes deployment, right? Do I actually want to measure the communication between each and every pod and each and every pod at the other end? Or I want to say something that describes the phenomena of two different deployments communicated cross-availability zones. And the final thing that we are going to try to achieve with EVPF in this talk is pinning down something that's going to help you reach the root cause of this cross-availability zone traffic and, again, figure out if it's important to you. And, for example, knowing that API search, which is an HTTP API, is carrying this traffic might help you make a decision of whether to address the issue or whether you intend that your platform will be built like that. So a good idea comes to mind, right? EVPF is a strong buzz these days, and it can probably help us out. And to those of you that don't know what EVPF is, EVPF is a revolutionary technology that allows us to run programs in the context of the Linux kernel itself, and in Kubernetes. It means in the context of the actual Kubernetes node, the actual Kubernetes worker node itself, without doing any scary stuff for charging kernel code or anything like that. But these EVPF programs have more power than that. They can observe what our containers are doing without intervening with the application code itself. Basically means that we can see what containers are sending and receiving across the entire cluster just by sending a simple EVPF program into the kernel of each of these nodes. Now, it sounds like it should be pretty easy, right? EVPF was built to observe network traffic. It's an event-driven system built to observe situations like network, receive, and send. And it also runs directly on the Kubernetes deployment. We wanted the Kubernetes Aware Sensor. That's what it is. It will run it as a deployment on your Kubernetes cluster aware of the Kubernetes infrastructure. And the last bit of EVPF program, that sounds like we can punch a few stuff in there, right? Like a logic for our aggregation or whatever you want to achieve. So that sounds like a magical solution to every problem we wanted to solve with VPC flow logs or things that come from our cloud metrics. As we all know, there's a bit of execution behind any great idea. So thanks, C, for that. So let's dive a bit into the details of how we can actually pull it off. So the first thing we're going to do is collect network metrics. Now, this is EVPF's moment to shine, because EVPF was built to probe simple operations in the kernel and user space like socketry and write. We can easily build counters that count the bytes that pass and that are sent and received on each of these socket pairs and start creating metrics from the infrastructure itself on things like IP and port from the client side, IP and port from the server side, and count these metrics over time, building these throughput metrics eventually that we can use. Now, this is already a good start compared to things that we have in event-driven systems like VPC flow logs. But eventually, we do end up with this kind of four tuple of IP and port on both ends and drop right into the first two problems that are clear. The first thing is that the client port is usually random. It has nothing to do with the logical aspect of the connection itself. It tells us nothing but the port being selected at the initiation of the connection itself, and it creates a lot of kernelality to whatever we're trying to describe. If we're going to build a metric with this label, we should think about it heavily because that's going to be a very high kernelality metric. And the second thing is, as Nirmal just told us, we're in Kubernetes, a server IP. That's virtual in most cases. It's going to be a Kubernetes service that behind the scenes basically communicates to a lot of different pods. How can we use a virtual IP to figure out what's going on? So we're going to address the problem straight on at the beginning. By dropping the client port, we don't really need it to figure out what's going on and make decisions on the logical aspect of the connection. And we're going to translate the service IP with some EVPF magic. Now, without diving too deep into that, EVPF is situated in the best junction possible at observing kernel operations like the services that the kernel provides to translate, not translation, and basically make decisions that Kubernetes uses about what the server IP actually represents and translating it to an actual pod IP behind the scenes. So we end up with a tree tuple, a new tree tuple, a pod IP on both ends, which is a physical IP we can actually use to understand, and a server port, which we're going to continue to take with us for the meanwhile. Now, the next thing we're going to do is tie that back to the Kubernetes infrastructure. We're going to use the Kubernetes API. That's very intuitive to do. The Kubernetes API holds all the Kubernetes hierarchy in one place. We can listen in on events that change this hierarchy and make sure that we stay up to date. All the pods, all the nodes that host them, all these manifests are being described in the Kubernetes API server. So we can start to do three things. First, we're going to turn all these pod IPs into pod names. IP is transient. We want to make sure that we hang on to a pod and a deployment name that represents something that you guys wrote or understand rather than an IP. And we're going to retrieve the availability zone value from the node manifest. We have all these nodes running in the cluster. Their manifest basically tells us what availability zone they belong to. And then we're going to tie that back to the pod. We know each pod, who's the node that hosts it, and now we have the AZ of the actual pod itself. And that's it. Basically, we have the full context. We have front end pod on one end, communicating to a back end pod on one end. On the other end, both of them belong to a specific deployment called front end or back end. And we know the node they're running on, and therefore, the AZ they're running on. So we just moved to a description which is much more suitable to what we tried to do, measuring a counter byte metric of communication between client on pod name and AZ on one end to a server with pod name, port and AZ on the other. Now, that's a good time to stop for a second and figure out what do we want to measure, right? Because eventually, just creating all these metrics without the ability to make a decision with them, it's something that we all know from observability and a lot of different aspects. Too much data isn't necessarily a good choice. We did have to go all the way to the pod granularity to get the AZ, right? Without knowing the pod and figuring out which node hosts it, we would never get to the AZ level, which is our intention at the beginning. But do we really want to say a specific front end pod is communicating with this and this volume to a specific back end pod? Because that could be tremendously wasteful. Imagine the situation of 100 pods on each end, as Nirmal just described. That's 100 times 100 possible connections. Does it really give us anything to measure any intricate connection between all these different pods? In most cases, what we really wanted to say was front end is communicated to back end, at this at this velocity, and some of this traffic is crossing AZs. So we can make decisions by that. And so we aggregate all the metrics that we're going to show from now on into this kind of new description, new labels of a Kubernetes workload name, like a deployment or anything that represents this group of pods on the client side, which is with its relevant AZ, and a workload and server port and AZ on the server side. So now it's much more descriptive and much more aggregated to things that we understand as a logical aspect of Kubernetes. Now, these are a lot of thoughts and a lot of theory. We wanted to show you how it might look like in an actual system that is very Kubernetes aware and measures these metrics. So we're going to dive deep into an example of GroundCover, showing all the different deployments right now in the Kubernetes cluster in a specific namespace. And we're going to focus on checkout service, which is a specific deployment. We see that it has one pod, and it's running healthy. And we see that it communicates to a few different other workloads in the same Kubernetes cluster. These six different workloads represent six different deployments that this workload communicates with. Now, if we look at the network metrics that we just described, we see two things. One is that about 500 bytes per second are being sent from checkout service to the other deployments. And about half of this is crossing availability zones. Now, it could have stopped here. But now we also know the four out of the six that actually partner on the other end of this cross availability zone network, network traffic. Now, this is super powerful, right? Because we're not just looking at six random connections, which we might have known from just knowing how the system is built. We know the exact four that cross availability zones. So it might be a wrap up, right? We know what is crossing AZs, and now you can make a decision of whether you intended to do so or not. But is there a way to make it a bit more actionable, even more? We know that EVPF is a very strong tool, right? It can observe socket reading right and kind of measure bytes being transferred at the lowest level like we just described. But it can also capture L7 traces, like application level traces, right? It can measure API throughputs and see through the application and user space itself with no cone changes as well to the containers you're running. A lot of different solutions out there from open source to things like ground cover utilize this exact capability. So that's a great and interesting idea. And also traces can be linked back to the infrastructure in the exact same way. We can know the pods on both ends. We can know the relevant nodes. We can know their AZs in the exact same way we did so far. So why don't use that? Because traces have so much more information like is the traffic encrypted? What's the protocol being transmitted at the application level between these two different pods across the AZ? And so we do a couple of things that we wanna show you that are interesting to kind of crank it up a notch. One is that we enrich those metrics into something that is usable even more. We're gonna replace the port label which is interesting on its own with a realistic enrichment of basically saying we know that this traffic represents HTTPS, for example. So this metric suddenly became even more interesting. But we're not gonna stop there because what if we get attached across AZ label to any singular trace that has been transmitted inside the cluster, right? Looking at metrics, looking at trends, making decisions by a volume of bytes being transmitted between two specific workloads and a specific API over time, that's great. But why don't see an example, right? Why don't see a specific span being set between two pods and label that span as crossing the availability zone? So we're gonna do just that in this demo. We're gonna walk in the traces screen on ground cover and we're gonna filter the workload called checkout service that we saw before, communicating with these four different other workloads over availability zones. We see the cross AZ label at the top mentioning that this span just crossed AZ and we know this is a GRPC span. And we're not gonna stop there, we're gonna filter all the cross availability zone spans and we get a list and volume over time of actual spans and examples with their payloads being sent and crossing availability zones. So we can take these examples and dive deeper with the developers, with the DevOps team which whatever is possible for the deployment that made a decision of whether it actually is something we intended to do. Now what did we end up with? We had on one network metrics, these metrics translate directly into cost, into performance of your application. You might see a specific workload representing a lot of cross AZ communication and you might wanna treat that just by looking at these metrics. But we also got deep, deep contacts with traces. So now we know who to blame, we know where to focus, we know how to maybe solve the issue and maybe take decisions on our architecture based on that. To show you that this can happen in real life, this is actually the story of Groundcover of us finding this exact situation that we just described and basically eating our own dog food which is always a good example of things being interesting. This is a very rough description clearly of the Groundcover metric ingestion pipeline. We're a built company, as part of that we store a lot of metrics. So our production was built on top of an ingestion pipeline with a front end based on Kong and a metric ingestion pipeline built on Victoria Metrics which eventually represented the entire pipeline we wanted to make sure it's resilient, right? So we created multiple availability zones that was a clear decision. If AZA drops, we wanna make sure that ingesting the metrics continues. So we deployed both Khan and Victoria Metrics on these multiple AZs and we were good to go, right? We're resilient if something happens to one of these AZs, our application is gonna keep on functioning. Well, what we found a few months later is that the original network cost which is basically describing these cross AZ communication network costs was higher than the compute of the cluster itself which in this case stores all our metrics. So for us that wasn't logical enough to make a decision but I think what's more interesting is what did we actually intended to even do, right? We intended that Kong and Victoria Metrics would both run on AZA and AZB. We wanted to make sure that if AZA drops dead that AZB is gonna be there to back us up. But did we really intend for a Kong from AZA to communicate with a Victoria Metrics ingestion pipeline from AZB? Not necessarily. We just didn't know exactly what we were doing and exactly what we were causing with this. So I really appreciate that story because I think this is where I see a lot of customers that they think they know how they design their architecture and they think they know, oh yeah, I've deployed this, I've put some rules or I have this traffic going here and I've set up the load balancing, I'm resilient. I'm okay, I know when an AZ fails I know where traffic's gonna go. But when you really dig in, you find out that, oh, I didn't know this service was talking to this. I didn't know this was configured from AZA to AZC or AZA to AZA even, right? So they thought they were building something with resiliency in mind but really they were just sending the traffic to the same zone and if that zone went down then there was no resiliency. So think about your own architecture and it's awesome and what your assumptions are about that but you need to have something there to validate whether those assumptions about your architecture cross AZ are actually true. So the takeaways for this are resiliency decisions are based on balancing these competing values, right? So you have different needs like availability, performance and cost that all driving and balancing the decision that you need to make. So sometimes a high cost and multi AZ and having network traffic going across AZ is exactly what you want and that's the intended design. But maybe you want to make sure that this service is always talking to a service that's in the same AZ and having that resiliency architectural trade-off decision data is important. Utilize EBPF to get that data. It gives you that granular level metrics and information and traces and telemetry and then you can connect it to the Kubernetes metadata to understand what services are talking and what services enriched with the AZs that those services are sitting on. And then you can take action. So once you know what the actual state of your services are you can change the architecture by implementing topology aware routing or something like a service or ambient mesh that has smart request routing or and think about where those nodes are being spun up the compute that you're using is being spun up to support those resources. So you can utilize something like carpenter to make sure that you're spinning up the nodes in the right AZ to support those workloads as you're scaling up. So the next time you have your awesome Gen AI application you know that it's resilient, it's cost effective and it's running really, really well. So get your phones out. We have some resources that you can explore more while you're grabbing your drink upstairs, for sure. So we have some resources, best practices guys. We have a blog post that covers all the different types of EBPF technologies at the end of last year, what it is, how it works, different open source projects around that. We have some details on how ground cover works under the hood that utilizes EBPF. And we have some best practices around resiliency and observability that me and my colleagues wrote from experience with talking with thousands of customers, our best practices guidance on making sure that you're resilient across different infrastructure layers. And last, but not least, please take a survey. I hope you realize I gave you three minutes back. Please fill out the survey. I'm gonna put this up real quick and then I'm gonna go back to the previous slide with all the links, all right? Cool. Thank you so much. Thank you guys.


So in that situation now, what are these recommendations you have for companies around the verification to stop the ruse? Well, look, the first thing is, is if you don't know the person well, so if it's like we talked about before, if it's an electronic issue, you have to, you know, put the device down, back up from your computer, take your hands away from the keyboard and ask somebody, you know, ask your booth mate, you know, your cubicle mate, the person in the office next to you, your boss, your assistant, somebody else to look at it before you do anything, you know, because usually once you get a second person involved, they're going to confirm what your instincts are, and then you know it's a scam, right? So that's that's how I advise with the with the technology.  And in terms of the phone call, I think that's the area that corporations have really fallen asleep is that they think phone calls don't happen anymore, that everything is done, right? I mean, we are of an age where we use the phone a lot. But younger people don't use the phone in the same way we did in terms of the voice call, right? And so corporations have kind of forgotten that there are people that are still making voice calls. I have all kinds of tricks that I use to get you to pick up your phone, because a lot of times people don't pick up the phone. But when I call you, you will pick up that phone, one very simple one that nobody thinks about it. So I'm going to call you, you're not going to recognize the number. Maybe it says anonymous, maybe it says a number you don't know. So you're not going to answer it. As soon as that call goes to voicemail, I dial your number immediately again. Now it's come to a second time. Now you're like, okay, something's going on. Again, maybe there's a problem. Maybe this is my kid's school and this is a teacher whose number I don't know. Maybe my mother, something happened and I don't know. So you know what? I got to answer this call because this could be important. I'm telling you, nine times out of 10, that second phone call, the person picks up the phone. If they don't, then I resort to, there's a thing called call spoofing, where you can get your number to show up as someone else's number, someone that they know. You can get your number to show up as some sort of authority number. I could have it show up as compliance. I could have it show up as the regulatory agency, whatever I want to do to make that. And we get these calls at home now, too, all the time. I got a phone call the other day from the actor, Sam Elliott. Sam Elliott, okay? We know Sam Elliott from Big Lebowski and all that stuff. Well, I happened to know Sam and Sam has been a big supporter of mine and he has done a lot of cool stuff for me. So I have his number in my phone and somehow some agency figured that out. And so all of a sudden I'm getting this call from Sam Elliott and I see the call come in and I think to myself, well, Sam Elliott has never called me. I mean, he's been a big supporter, but he's not calling me to hang out. And I realized that it was a call spoof and that somebody had used a relationship I had to try to get me to pick up the phone.


I welcome members to the 22nd meeting in 2015 of the Delegated Powers and Law Reform Committee. I ask members to switch off mobile devices, please. Agender item 1 is a decision on taking business in private. It's proposed that we take item 6 in private. This will allow the committee to consider its approach to the scrutiny of the succession Scotland Bill at stage 1 in the event that the bill is formally referred to the committee by the Parliament later this week. Does the committee agree to take this item in private, please? Yes. Thank you. Agender item 2, instrument subject to affirmative procedure. No points have been raised by our legal advisers on the legal aid and advice assistance miscellaneous amendments Scotland regulations 2015 draft, nor on the Courts Reform Scotland Act 2014, consequential provisions number 2, order 2015 draft. Is the committee content with these instruments, please? Yes. Keep. Agender item 3 then is instrument subject to negative procedure. The Scheduled Monuments Appeals Scotland Regulations 2015, SSI 2015, 231. Our legal advisers have identified three minor drafting errors with this instrument. These errors are firstly that regulation 6.4 contains an incorrect cross-reference to paragraph 4 of regulation 6. This should instead be a reference to paragraph 3 of regulation 6. Secondly that regulation 16.4C refers to documents which were sent with the planning authorities response. This should instead refer to documents which were sent with Historic Environment Scotland's response. And thirdly that regulation 17.1 contains an incorrect cross-reference to regulation 15. This should instead be a reference to regulation 16. Scottish Government intends to bring forward an amending instrument to correct these errors. Does the committee agree to draw this instrument to the attention of the Parliament on the general reporting ground as it contains minor drafting errors? Yes. I would also welcome the fact that the Government is going to bring forward an amending instrument. Thank you. The planning listed building consent and conservation area consent procedure Scotland Regulations 2015, SSI 2015, 243. This instrument also contains a drafting error. Regulation 19.1 provides that subject to paragraph 2. The provisions specified in paragraph 2 are revoked. The first reference to paragraph 2 should be to paragraph 3. Scottish Government agrees that this is an error, but does not plan to amend the regulations at this time? Does the committee agree to draw this instrument to the attention of the Parliament on the general reporting ground as it contains a drafting error? Yes. Does the committee also agree to call on the Scottish Government to amend this error at a suitable opportunity in the future? Yes. Thank you. St Mary's Music School, AD places Scotland Regulations 2015, SSI 2015, 248. This instrument has breached the 28-day rule. It was laid before Parliament on 5 June 2015 and will come into force on 1 August, meaning that the requirements leave a minimum of 28 days discounting recess periods between laying and coming into force has not been complied with. Does the committee agree to draw the instrument to the attention of the Parliament on reporting ground J as there has been a failure to observe the requirements of section 28.2 of the Interpretation and Legislative Reform Act 2010? Yes. Does the committee agree to accept the Scottish Government's explanation as to why the instrument could not have been laid earlier than on 5 June and to agree to accept the explanation as to why the commencement date on 1 August was chosen in light of the start of the academic year? Yes. No points have been raised by our legal advisers on the schedule, monuments, notifications and publications Scotland Regulations 2015, SSI 2015, 230. Nor on the schedule, monuments, determination of appeals by appointed persons to prescribed classes Scotland Regulations 2015, SSI 2015, 232. Nor on the Townland Country Planning Miscellaneous Amendment Scotland Regulations 2015, SSI 2015, 249. Is the committee content with these, please? Yes. Thank you. Gender item 4, instruments not subject to any parliamentary procedure. The act of Soderent Rules of the Court of Session 1994 and Sheriff Court rules amendment number 2, Personal Injury and Remits 2015, SSI 2015, 227. This instrument contains a minor drafting error. Paragraph 8.5 inserts a new chapter 15A of the rules of court of session 1994, motions intimated and lodged by email. Rule 15A has two paragraphs, both numbered 2. The Lord President's private office has undertaken to lay an amending instrument to correct this error. Does the committee agree to draw this instrument to the attention of the Parliament on the general reporting ground as it contains a minor drafting error? Yes. The act of Soderent Rules of the Court of Session 1994 amendment number 3, Courts Reform Scotland Act 2014, 2015, SSI 2015, 228. This instrument contains two minor drafting errors. Firstly, there is an error in the new rule 5815 of the rules of court of session 1994, which is inserted by paragraph 3.3 of the instrument. Paragraph numbering within the rule is 145. Secondly, in the form of petition for judicial review in schedule 1, the heading with the new numbering of form 583 is omitted. The new rule 5833 refers to a petition for judicial review to be made in form 583, but the form in schedule 1 is not so numbered. The Lord President's private office has undertaken to lay an amending instrument to correct these errors, and an error identified in the aforementioned rules of the court of session number 2, personal injury remits above. The amendment is intended to come into force on 22 September as this is the commencement date of the instrument. Does the committee agree to draw this instrument to the attention of the Parliament as it contains a couple of minor drafting errors? Yes. No points have been raised by illegal advisers on the act of Soderent Rules of the Court of Session 1994 and fees of solicitors in the Sheriff Court amendment. Courts Reform Scotland Act 2014-2015, SSI 2015-246. Nor on the Courts Reform Scotland Act 2014, commencement number 3, transitional and saving provisions Order 2015, SSI 2015-247. Is the committee content with those, please? Yes. Thank you. Agender item number 5, the Prisoners' Control of Release Scotland Bill. This item of business is for the committee to consider the delegated powers provisions in the bill as amended at stage 2. Committee's conclusions will form the basis of a report ahead of today's schedule 3 debate. The committee therefore needs to draw its conclusions now. Members will have seen the Scottish Government has provided a supplementary delegated powers memorandum and will have seen the briefing paper for the committee. As you will recall at stage 1, the bill of the bill, the committee was particularly concerned about the fact that transitional, transitory and saving provisions may be required in a commencement order subject to no procedure under the bill. As the use of these provisions could be potentially significantly effected, sorry, could have potentially a significant effect on certain persons affected by the bill, such as long-term prisoners. The ability to make transitional, transitory and saving provision at stage 2 has been removed from the bill. Instead, the saving provision required in relation to automatic early release of certain prisoners has been put on the face of the bill. The commencement provisions also introduce a limited delegated power in section 3.4 beyond the power to commence sections 1 and 2 of the bill by order in the usual way. The new section 3.4 of the bill allows the commencement order to amend section 1.1a of the Prisoners and Criminal Proceedings Scotland Act 1993. New section 1.1a is inserted by section 1.2 of the bill to provide the saving provision which defines which long-term prisoners the new early release rules do and do not apply to. The new rules only apply in cases of prisoners serving sentences opposed on or after the day that section 1 of the bill comes into force. Accordingly, once a commencement order has been made, anyone reading the amended version of section 1.1a will be able to see immediately whether the new or old early release rules apply to a prisoner sentenced on a particular day. A commencement order would be laid before Parliament, but not subject to further procedure. Is the committee content with commencement orders, powers and section 3 as amended at stage 2 and that a commencement order would be laid before Parliament but not subject to further procedure? Yes. Does the committee agree to welcome the amendments made to sections 1 and 3 of the bill as these have taken into account the committee's recommendation at stage 1 to enhance parliamentary scrutiny on the provisions? Yes. With that, I move the meeting into private for item 6. Thank you.


Ladies and gentlemen we back with some jiu-jitsu kaisen only three episodes left very excited getting to the tail end of it What's going on guys my name is Jack the bus you can call me I should have been back to a brand new video today We have episode 22 of our jiu-jitsu kaisen watching named the origin of blind obedience very interesting title So I'm assuming they're gonna sort of start setting up for the future of the show Like I said, especially since we are getting to the tail end of things. They can't start off a ton of stuff I imagine we'll get into some minor plot points So I'm very interested to see kind of what they tease for the future Especially considering they can go so many ways with it last episode of course was the sort of conclusion episode to the group battle event and I Guess all the curses invading it kind of just wrapped all that up and now I'm excited to see where we go next If you're new to channel drop a sub hit that big boy bell so miss any future episodes So if I like on this one, let's just hop right into it We know flashing lights basically means curse coming in hot Hey, you dead or you're very dead Okay, well very interesting start Oh they all dead It's a new case It's interesting that they always start off as like it seems like the police cases in a way So the property managers might be involved It's only when they complain Oh Yeah, the camera that was on it But why we're just getting like right into a new sort of mission But there's a pretty good chance it's the same one for the same cases Maybe it's a past student that they went to school with like the curse is like being kind of Like it's being manifested Yeah, in the middle school Detectives I am the smartest out of us three I think she is probably the smartest because she goes probably close second is a dory. He struggles sometimes. We still love them though Oh This is literally like a detective case. It's very interesting Cold case So long as you don't take more than 48 hours, but she says it's been a minute. So The lead might be dead dead Obvious bugs is it the haircut the cigarettes? Yeah, actually just setting them straight They're probably talking about the the woman with them. Oh, oh Fushikura knows them. Oh Oh, wait, that's a big deal. Why did he not say anything? What was he like?  Don't get twisted Might like regret his past or not want to revisit it. No wonder he was colder than usual And they're straight Then this show just hops right back in the stuff. I guess to the pacing is immaculate So they're very strict about guests even he recognizes Yeah, it's like I don't have to do anything, you know your way around What was their connection? Yeah, I mean how much could he really tell Some presses I can remember those students That'd be so weird to work at like a school see people just grow up so much Oh Hey, they could be of help Of course it was Love it Oh They didn't jump That's spooky dude my goodness Of course not yeah, I was gonna say that's pie a super cursed area He's still he has a tear in his eye from Fushikura hitting him Yeah See that's what they stole from the school too Alongside the Sukuna finger. Oh my god It is beyond money at this point my man Guys bleeding from his eyes any time Mahito's on screen, bro I just got to prep myself mentally so they're probably involved gonna be honest. Hey, so there's three I don't understand those what do they call them paintings last episode. They said still three. What do you call them?  I like her Yeah, um, that's what I'm saying. Oh his sister That's interesting that we're gonna find out a little bit about his family relationship They asked if she was okay, or if she's doing okay, and he said yes But in a way that like I don't know if he's like disconnected from her or doesn't talk to her or what this is all so spooky, dude Practice bad boy wide open So quickly We know much about his family. I don't know maybe I'm misremembering I Guess it could be anyone that she went with so they're Their squad is kind of stacked inherently He knows if they do she dies Right, oh, I guess he's saying if he leaves they have a better a worse chance of making sure she lives Cuz they're doomed She's fine right now So it's like a ticking time bomb He's taking a lot raw a lot of responsibility onto his shoulders in this case This is going alone, dude got to come out eventually They wait did they follow him Yeah, oh my gosh, they popped out of nowhere.   That's the one This thing's crazy. Oh wait, that's that's the thing my domain. He made it like probably to protect this other one I'm pretty sure that's it. Yeah, he's send it out. Oh Shoot Yo, my boy into door. He's cracked now though He learned quite a bit from Toto That's a dude's face. Oh my gosh. How did they just pull these insane scenarios out in one episode? I said I thought these last three were gonna kind of wrap it up and just world-build a little bit more But he's just throwing us more into some action Ain't no problem Oh Daimless How's this juju strong I knew there was kids gonna take some with Like yeah, I didn't know about that. Okay, so a huge episode in terms of development I think setting up a little bit more action before the show ends at least for the season But hey man, I'm 100% down with it Especially if it fleshes out fushiguro's character even more we're learning about his sister and what what she's had to go through So I guess he's had this on his mind the whole time that she's been in this state and could die any moment and that he's 100% going to go on this mission, but didn't inherently want to endanger into Dorian nobita I guess at least that's what I took from it and that now he has this opportunity to free both his sister and any other people From ever having this basically ticking time bomb put in them from this curse There's gonna be a lot of passion a lot of personal flame from fushiguro in this fight guys That has been it for episode 22 of our jiu-jitsu kaisen watch through let me know Episode down in comments below let me know if I missed anything especially because there was a lot in that one Just always I hope you guys have a wonderful rest of the day as per usual and I'll catch you in the next one his face


I'm deafed in for a long time. It just didn't make sense. When you think about the idea of a record company, they basically, they give you the loan, and they front the distribution to make your CDs. And basically charge you triple with that? Yeah, but you don't, there are no f***ing CDs. Nothing is f***ing with us, you do not exist no more. And then we still kind of get tricked a little bit, because like, we still kind of follow for the same tricks.  The homie just sold 150,000 albums, right? He didn't sell 150,000 albums. She had billions of strings. Yeah, millions, yeah, yeah. But they're telling him he sold 130,000. Because they not finna tell these f***ing, oh man, you had millions and billions of people listening to you in three days. They not gonna take that, because then you're gonna be like, damn, if I'm able to do that, without, I don't need them. You feel what I'm saying?


Hello, you're watching the International Daily Roundup by People's Dispatch, where we bring you some of the major stories from around the world. Let's take a look at the headlines. Israeli forces killed three Palestinians in Nablus raid, Muslim students faced restrictions in entering colleges in Indian state, Minnesota students demand justice for Amir lock, and millions faced severe hunger in Horn of Africa. In our first story, Israeli forces killed three Palestinians during a raid in the occupied West Bank on February 8th. Three men were travelling in a car in the city of Nablus when they were shot. According to WAFA News, they have been identified as Ashtaf Mubaslath, Adam Mabruka, and Mohammed Dahil. An Israeli special forces unit entered the Al-Makfiyya locality in a civilian vehicle on Tuesday. Images from Tuesday's attack showed the Palestinians' car riddled with bullets. Israelis claimed that the men had been responsible for a series of shootings in the area. Activists and rights groups have condemned the killings as an extrajudicial execution. The three were members of the largely defunct Al-Aqsa Martial's Brigade. The resistance group is associated with the Fateh Party, which is part of the Palestinian Liberation Organization. Thousands of people gathered for the three men's funeral later on Tuesday. Palestinians in the village of Betan near Nablus and Qalandiyah in Jerusalem held protests late at night. A one-day general strike was also observed across the occupied West Bank on February 9th, in solidarity with the men killed. Israel is known to deploy excessive and disproportionate force in clear violation of due process rights. It has also recently amended its open fire rules, expanding what has already been called a shoot-to-kill policy. We now go to the state of Karnataka in India, where Muslim students are facing increasing harassment. Hijab wearing students have been barred from education institutions in several parts of the state. The issue first came to light at a government college in the Udupi district in late December. Six Muslim students have been protesting for over a month after being told that they would not be allowed inside the classroom with a headscarf. The college claimed that the government violated the arrest code and that the students had given commitments regarding this earlier. After two days of hearings, the Karnataka High Court had referred the students' petitions to a larger bench. The freedom to practice once religion is enshrined is a fundamental right to the Indian constitution. There is a precedent in India where courts have ruled that the right to wear a hijab does fall under constitutional guarantees. On February 3rd, 28 hijab-bearing students were denied entry into a junior college in Kundapur. On February 7th, the government college in Udupi allowed the protesting students to enter the campus, however they were made to sit in a separate section. Students and protestors wearing saffron-colored shawls associated with the Hindu right have also confronted the Muslim students in several places. The BJP-led state government has shut down high schools and colleges for three days. Protest and gatherings within a 200 meter radius of all education institutions have also been banned for two weeks in the state capital. The situation in Karnataka has been condemned as part of the growing sectarian threats and violence under the right-wing BJP government. Next we go to the United States where students in Minnesota held a state while schooled walkout on February 8th. The protests were organized by the Minnesota Teen Activist Group to demand justice for Ahmed Lok. The 22-year-old was shot and killed by Minneapolis Police Department officers in February 2nd. Police entered the apartment where he was sleeping and by executing a no-knock warrant. Officer Mark Hanman then shot him three times within 10 seconds. Body camera footage showed Lok just waking up and reaching for a gun with his hand on the trigger. Police claimed that he had pointed the gun towards them and they had repeatedly announced police search warrant before entering the apartment. Body camera footage proves both these claims to be false. Several protests have been organized in Minnesota since last week. Nearly 1,000 people marched to the first police precinct in Minneapolis on February 5th. On Friday, Mayor Jacob Frey announced a moratorium on no-knock warrants. However, many have pointed out that he had already claimed to have banned the practice in late 2020. According to University of St. Thomas professor Rachel Moran, Minneapolis Police have requested at least 90 such warrants since then. Students marched to the Minnesota governor's mansion on Tuesday demanding a proper ban on no-knock warrants. They also demanded a demilitarization of the police and the resignation of the Minneapolis mayor and police chief. And for our final story, the world food program has stated that around 13 million people in the horn of Africa are facing severe hunger. Pastoral and farming communities in large parts of Ethiopia, Kenya and Somalia have been affected by drought. Forecasts have predicted lower than average rainfall in the coming month which could make conditions even worse. The region has witnessed three consecutive failed rainy seasons, causing a shortage of water and pasture. This has ruined harvest and led to abnormally high rates of livestock deaths. Access and affordability have also been impacted by rising food prices, inflation and the low demand for agricultural labor. The crisis also forced families to flee their homes. An estimated 5.5 million children in the region are at risk of acute malnutrition. Another 1.4 million are facing severe acute malnutrition. The UN has warned that the number could rise by another 50% if the rains do not arrive within the next three months. The conditions in the region are also increasingly vulnerable to climate change. The UN had warned last year that over 100 million extremely poor people across Africa were being threatened by the accelerating crisis. The continent is warming at a faster rate than the world average, despite accounting for less than 4% of greenhouse emissions. And that's all for today's episode. For more such stories, visit our website peoplesdispatch.org and follow us on Facebook, Twitter and Instagram.


What up what up? What's going down? Everybody I started to stream a little bit earlier Didn't schedule Waiting for things to set up Yeah, I started a little bit early off. I had to man. I'm doing good Doing good doing good Let's see what they added some multiplayer They got the FFA tactical player team player cool I'll get back into that after I finish this campaign, but we're gonna hop right into the campaign As you can see, I am 24% done with the game So put eight hours in so far. So we're gonna continue this up I'm probably not gonna be able to stream as long as normal because I gotta take care of some stuff My day's been good Y'all can hear me good. Audio's good. I'm a little congested. I'm stopped up right now. So I've been taking meds and stuff Yeah, I heard almost turned this back on AJ. We knew that was coming. No, I'm not 40% at all All right, let's get into this man All right Let's do this Start right where we left off So make sure my mic still seep up properly auditorium. Yep. It's not. Oh, no. What is it? What's wrong? Dc I've been here before This is where I locked her down This is where Cortana died Nice. I've seen it should be good now Oh Yeah, I just gotta make sure My camera is in sync with my audio Everything look good on y'all in. There's my does my voice seem like it's in sync with the visual with the webcam All right, cool. Cool. Cool. All right Let's get into this man. Sorry took out great value Thanos We'll be in touch You got it. I'll be waiting for the call. Whoa, whoa, whoa, whoa Get wrecked get bean.  All right. Cool. Cool. Cool.   Get rid of him. Got him. Oh my god. Oh No, Jesus, I gotta get to this thing right here. I've been good Come on. Come on Come on already.  Who we bro Jesus It's so many.    I Wouldn't even try to hijack.  I gotta get you Get out.  Just annoying Gee. All right, let's continue this Comparative, you know what can I want?    Hey, congrats on you getting the PS5 bro. Hope you enjoy it So, baby, take me out to dinner Hey, that's good man, but it didn't affect you too bad Yeah, my sizes are kicking my butt right now What's the plan take me back to the infinity for deletion Oh Helen I will block you bro. That's just not funny. I don't have COVID. Oh Boy, that's just not funny, bro All right, y'all prepare myself Can y'all tell me why does it do that in these these little pools to get some type of damage over?  I know I have a sword in my back pocket, but I I'm just trying to say really right around here. It's just a state of giving Honestly, I may need to try to get She'll right here got the shield right here. What's up pussy? Oh, okay?  Oh my god. I'm getting irritated At least to save my progress are you thank you? Oh my Jesus.  I bet She was expecting you but atriox got to her first You meant so much to each other It can't be easy Can y'all hear the game audio good? The disrespect was real, but see it did it again.   Let's do it over here. This is me y'all Oh, you want a sword battle?   Okay? I need some ammo Probably go back with the sword. Oh, it's not trying to pick up this guy Actually, I'm gonna fight.  Oh, that's cold blooded.  Well, maybe the sense will be Nope, there we go. That's my baby. He said I'll take you on myself.  Is there some more ammo down here? I think there is I don't know if I'm gonna walk all the way down here. I think I'll just stick with this See what's about to happen now It's more precise more complete getting closer to where she died But I was going to say deliberate like she wanted us to know something Should I got get rid of this down eat it.   He takes a lot of damage Damn, I just erased Get erased by Oh There's a reason why these are here pick this up. Thank you There's a reason why that's there.  I could do that for you could turn up. What's up? I'm supposed to go that way They all got rinsed. Oh, it's getting real y'all Oh Now you need my help Starting good point I'm dead had a back Now you would come up forgive me. Thanks, baby Really There's not much time He has the ring a weapon pointed into the universe There's a moment John will make it work he needs help of course Was this your plan all of all palsy Or is it mine? It doesn't matter Nothing else matters He can't do it on his own he needs me he needs her Score it all here get a lot of story now. Thank you Do you help to me you really did would you humor me through how you were going to die? Would you live your life differently? Perfect. Thank you What's she in the building it was her She destroyed the ring stopped my deletion Why oh Oh, I feel like I'm about to fight somebody big We get to the nitty-gritty baby. Is that you this is where Cortana Sacrificed herself baby. I'm here. I'm here Obviously it appears to be What is it? it's a courtroom a prison a place of execution All these things together Why? To call their sins we stood signable Unable to speak as they passed judgment We could not defend ourselves We would not reason with them Something's sending a signal before you ask I'm already tracking it here this Your Today we return that's the that's the master boss Oh Shit, so this is the master boss. I guess On the percentage when it shows like how much you completed that mean I guess that's probably like the open world stuff But the storyline stuff. I think this may be the end right here.  She's trying to open a connection between here and somewhere else on the ring where You deal with her and I'll find out I can't I can't go in there Okay, okay, okay, okay, you guys a major point hold on. Oh, my god He's just bold. They need my armor. I know this this fight was probably tough and legendary All right, let's go. Okay. Okay. Okay Okay, okay, she can instant she can Bro she got instant trans. Oh my god. She got instant transmission, bro. It's not fair Oh, go go go go. No, okay. Get on it. Go. What the okay? Okay? Okay? Okay? Holy shit, I got to take some water man. She can instant transmission. That's she crazy What's up water? I need Gatorade man. Is it is it in you? You know, I'm not sponsored by Gatorade Now I ain't trying to rage, bro. I just got to be strategic It's probably gonna be another wave of it What's about to happen yep, she's gonna send another way switch transmitters Rewriting the power through that one. Good. The connection is sentient. It's searching for something Yep, I knew it. Oh, there's swords and stuff over here. I just don't want to die.    All right. Okay, next one's down.  This is like the best weapon to get Switched again, it's found something no idea, but I doubt it's good. Wait, there's something else here Something's helping me Cortana, I gotta get rid of him first. I'm out. I'm out. I'm out. I'm out. I'm out.  All right, we're gonna no more.  Get over here. I had to get my favorite good here. Get out of here. All right thing. I did it y'all I think that's it The end Decrypted in time, it's okay You'll figure something out. Of course. I will I'm they'll pair you with another AI Maybe even another Cortana model if Halsey lets them it won't be me But you know that right?  I just had a Feeling that's what she would say. Oh wow DC what I see So much potential. I'm sorry. I didn't have long to plan this A few milliseconds really I hope it worked out Look at us. We just keep saying goodbye. Don't we? But this isn't an end it's a chance to make amends to rectify mistakes and It starts here. I was wrong. I thought that I could do this on my own But I forgot that the whole point of all of this The entire reason that I chose you in the first place was that we were supposed to be a team Perfectly suited perfectly matched perfectly Perfect in these final moments. I know what my last mission is I need to make sure you to learn from my mistakes Become stronger because of her last message. I chose well master chief. I really did It's up to you Are you all right? I don't know what to say Options I'm thinking was that you wouldn't help if I said yes, probably but we don't know where it's going Or even if it's going anywhere and the other suggestions. No, but he was like crazy Let's not do that again.  I think the better question is when are we know how for days Three days to be precise Do you this ring is different than the others banished in the harbinger We're looking for something that was never found. Why would the forerunners hide something and throw away the key? Doesn't that scare you no Of course not He is tall as hell really happy so What do we do now? We've finished the fight Yes, sir They banished still control the rest of the ring Wait, this is weird given all that's happened, but what what is it? We still don't know your name. We can't keep calling you echo 216 No, you can't Esparza Fernando Esparza. It's nice to meet you Esparza Fernando Esparza good work soldier And what about you? What about me? What do I call you any ideas? You think it would be okay? You're sure You get to choose your name Then I think I Think I might have the perfect one All right Here we go. Well, I guess that's the end of the story mode. It's the main campaign. There's still plenty of stuff For me to do on the actual world completely like 20 some percent of it So the rest of the open world, I gotta I guess finish up So if you guys want me to do that finish up the rest, you know Complete it all the way through go through all the side missions and stuff. Let me know But yeah, I'm you know, this was Convicted Only because it was like I was enjoying it I know they're sending up obviously That's my personal Bigger finish I was really I was trying to figure out what the hell they was trying to get Bring back to life apparently, but we never really find out so they found out in the next game Or whatever the forerunners that we're trying to hide or what I know that I was expected That's my way. It's about to go down, right?  I'm about to fight her This is halo influence campaign The storyline part Definitely probably check out like some of the side missions and stuff like that go through but it was enjoyable I will say that I Thoroughly enjoyed it for what it was Had a good time, and I hopefully you guys had a good time, too Hope you guys enjoyed the stream and I'll probably try to stream again tomorrow I'll probably do some multiplayer. I haven't played any multiplayer quite some time I'll probably do it The cranes are about to be 30 minutes, bro. Is there anything at the end? Let me see Cuz there's none that in I'm not about to be sitting here There is you can just skip all I can just skip all right cool, but it is that Is that a tree ox? Can I thought he was killed? Is that that is him That's a choice right or is that somebody else I couldn't really tell was that help.  Who was that? No, that's a tree ox That look like you also that was him without the face paint cuz that's the guy hold on Cuz that's the guy that beat master chief at the beginning of the game.  I'm checking stuff right now In this free Okay Yeah, so base Looking at the sorrow the post-credits he seems to indicate that H york survived car Thomas attack that appears as though He's free the endless and doesn't look any worse for aware It's likely that he'll be the antagonist when new missions are released sometime in the future Also, there'll be updating new missions and stuff like that. So hey, I'm looking forward to it Definitely will continue to keep playing this game or whatnot, but appreciate everyone's showing the love and support Thank y'all so much for Just you know joining in and and doing this journey with me, but uh, I will catch you guys probably uh thursday Most likely thursday i'll try to stream. So appreciate you guys. Love you guys, and I'll catch you guys later Also, you're saying that's not that's not a tree ox Oh, i'm not sure. I'm about to look it up, but catch you guys later