Can Pedersen do it again from the start line? No! And a little mix there, Nicky Pedersen. Now, it's Freddie Lindgren who has the lead. Watch out for Woffendon up the inside, but Lindgren's got the chance! Oh, my goodness me! Oh, Pedersen up the inside! Lindgren up the inside of Pedersen! Woffendon trying to stay out of trouble. Oh, Lindgren and Pedersen trying to beat each other up here. Goodness me, Woffendon is third, but Lindgren has that lead superbly. Wow, Pedersen just moved a little bit there. Freddie got the start. Real tough opening lap of Speedway. Still something to go here. Pedersen really coming on strong in second place. Keep your eyes on Woffendon. Here comes Woffendon. Blast off the safe defence. Here we go again. Yep, as Woffendon got the drive, he's out in the dirt. We're going into the last lap. It looks like Woffendon is going to miss out. And because the lead is with Lindgren, but Woffendon's gaining ground now. Down the back straight, tie Woffendon. Pedersen's going to close. That was proper Speedway there. Woffendon not happy with that. Oh, there's a bit of controversy here. Woffendon and Pedersen going head to head. Oh, we can't see it. Woffendon and Pedersen head to head. Tough Speedway. Really tough. Pedersen holds onto second place, and it's still going on. Yeah. It's still going on. Woffendon still having words here with Nicky. Great rivals. Both world champions. Emotions running high now. Certainly not happy with the move coming out in the last corner. Well, well, well. Pedersen's through. Great ride from Freddie Lindgren. Everybody getting involved. This is unnecessary now. Wow. There you go. It was a tough move. This is World Championship Speedway. It's tough. World Championship Speedway is tough. And... But a drive-up. It's on here. Well, there you go. It's getting lively now. Wow. But a win for Freddie Lindgren. We didn't talk about that much before that. Bit of a sideshow. Brilliant ride from Freddie. Certainly he made a great start. Best start. He hasn't made any starts, and really comes up with a smashing ride in semi-final number one. Nicky Pedersen through to the final, and Woffendon just misses out. Well, just a little bit of controversy towards the end of the evening. Don't mind that. Freddie missed it all. He's won the rerun. You see it here. Great start from Freddie from Gate 3. And Nicky doesn't quite get there, but he's in second place. Here comes Freddie now. Oh! Yeah, slams the door shut. Dear me. Well, that's what you get with Nicky. He's a tough customer. You know it's coming. Now he's in second place. Woffendon, wow. He gave it everything round the outside. Pedersen's aware of it. He's got into second place now, but he just runs a little wide. Pedersen up the inside. Slams the door shut again. Well, Woffendon clearly not happy with that. And, well, kind of understand that a bit, but that's what you get. You know, Nicky's a tough customer. Always has been, always will be.


what is going on guys welcome back to the channel and I appreciate you being here today I bring you another Destiny 2 video and today I'll showcase how you can start to unlock the mysterious box a new Exhaustic quest line with the black arm with DLC but before we go any further guys if you do enjoy the video and would like to show you support you can by hitting that like button if you are new around here and enjoy daily Destiny 2 videos be sure to subscribe okay so yesterday I uploaded a video where you could actually locate this Exhaustic quest if you are unaware of what I am talking about let me do a little recap for you the new Forge area on the EDZ located within this Forge area within a hidden cave off to the left of the entrance is an Exhaustic quest you can grab via this hidden loot crate the quest requires you to obtain four keys as you can see on the screen now until today we didn't know what these keys were or how they were obtained but it seems as though they are hidden within the universe and acquired via doing certain things at certain times today I'll be in your guide on how you can get the first key called the fish hook key so you want to go ahead and start the Forge you need to clear the first wave of enemies banking or dunking or even throwing 20 components at the Forge which are obtained via killing the blue shielded enemies which spawn across the arena so throw 20 at the Forge and then the first wave is completed then what you need to do is go off to the left-hand side of the arena like I do on screen now and out on this little rocky island you will see a drone spawn in you need to shoot and destroy this drone which you have done that in the first drone will spawn under the rocks on the right-hand side as you can see on the screen now here guys you again have to shoot and destroy this drone once that is done you then have to clear this second wave and get to the third stage which is the boss stage now this is where I experimented as I saw many people state you actually have to kill the boss to get this chest or loot crate to spawn in which rewards you the key I saw some people state you don't have to kill the boss well a pal of mine killed the boss and a chest spawning as you would think so I ran it and I didn't kill the boss and as you can see on screen now the chest or the loot crate it still spawned in for us to grab this key from so proving today within this video people you don't have to kill the boss to get this crate to spawn in I do however still believe you actually have to make it to the third boss stage though so yeah kill or don't kill the boss the loot crate spawns in open it and receive your key then go into your inventory and use it you will then see that you have completed the one step of zig-zag quest now if other keys are hidden in the game I don't know I honestly think we'll probably get one key with every forge and maybe another one a different way but whatever happens is we are rewarded an exotic weapon for it now what this weapon is we don't know speculations been thrown out there but we honestly don't know what it is at this time but no doubt it will be one of the new exotics we have seen so far so we will see people we will see if any new evil drops I will have you covered here on my channel so make sure you subscribe if you're new around here but yeah guys this is how you get their fish hook key for the mysterious barks exotic quest enjoy on that note guys we have come to the end of the video if you enjoyed it leaving a like really helps out if you're new around here and enjoy daily destiny 2 videos be sure to subscribe and if you never want to miss a video I upload turn the notifications on by hitting that bell button but thanks as always for stopping by people and hopefully I will see you on that next one


A lot of people daydream about being rich but when the wealth comes, they find it challenging to handle the changes that may follow as well. Money indeed makes life more comfortable, however, adapting to your new status may be a difficult thing to do. In this video, I will share with you 13 things that change once you are rich. 1. Your Friends In a YouTube video titled The Truth About Friendship, Mel Robbins explained that friends are classified into three. Friends for a reason, friends for a season and friends for a lifetime. At every season of any individual's life, there is financial upgrade inclusive, a change in association. Even if you manage to maintain a few of them, there will be a gap in communication, especially when they are not wealthy or making efforts to be productive. Once you are on a different page with someone, it is challenging to continue conversing, whereas if it is for someone on the same phase with you, there is a tremendous amount of respect for them and you will find opportunities to be with them. 2.  Poverty limits your scope of delicacies and even if you see beyond your tuna and ramen noodles meal range, you will have to look away because you cannot afford it.  Being wealthy brings to your realization that a balanced diet is a thing that exists. Thus, you may go into dieting and even employ the service of a meal planner. At first, you may want to run through all the junk that you desired but could not afford. In a short while, you would opt for homemade, healthy and well-garnished meals and even try out new delicacies. 3. Health Becomes a Priority When you are rich, you understand a statement, health is wealth. Unlike before, a doctor's appointment is no longer a waste of money. You only need to fix it into your schedule. When a poor man is ill, he checks for the nearest medication but the rich man would instead go through the process of seeing a physician and run in all necessary laboratory tests.  The realization that without sound health, you won't make good money will hit you hard when you are mass-wealth. So even though you might have to work more, more attention will be given to your health. 4. Goals For every phase in your life, your goals change. Wealth is not an exception. You definitely won't have a target of making a few bucks that can sustain you throughout the week. What you used to consider as success will no longer look like an accomplishment to you. A million dollars may have seemed like a massive sum to you previously but once you have it, you realize it does not go that far and is more of a starting point. In many cases, your goal will shift from money totally and will point in the direction of influence and significance. Your brain is automatically wired to think about the future, increasing your earning potential, becoming a billionaire, being listed on Forbes, building a legacy for your family, etc. 5. What makes you happy?  Now that you are rich, you will realize that those things do not matter anymore. The newfound wealth will give you a sense of freedom and accomplishment. Still, you will gradually begin to understand what is meant by, money cannot buy happiness. With time, dinner in a 5-star restaurant becomes a common thing to you and does not freak you anymore. The thing that will mean much to you at this point in your life are those things you probably took for granted while you were weak. Things like spending time with family, eating homemade meals, paying attention to your health, seeking authentic relationships, etc. 6. Taxes As an employee, your taxes were probably minute and deducted before you got your paycheck. Throughout the year, you are up to date with your tax payments and you may even get a refund of all your taxes. But when wealth comes, the tax becomes a big deal for you. All of a sudden, you will start to pay close attention to your payments as the amounts become so huge. Hence, you will seek a financial advisor and find mediums to reduce your tax-budding. 7. Your looks One aspect that is hugely affected by a change in financial status is your appearance.  Skin, hair, clothing, etc. Even the usual aspects of agent, like hair falling, can be fixed with hair transplant, teeth damage and decay can also be sorted. There are also stem cell injections that prolong your youthful appearance for a much longer time. Apart from these facial measures when you are wealthy, you can afford to take care of your body with expensive organic products, vegan meals, and other healthy food. Getting a personal trainer is not an issue for you, so you can get the body size of your dreams if you desire. 8. You can say no more often With more comes respect from others. This new respect allows you to state your options and make your own rules. You don't have to say yes to whatever makes you uncomfortable. For instance, maybe your boss used to make you work overtime or use abusive words on you. You can choose to say enough is enough and quit that job. Although you can discipline yourself to say no to unpleasant situations when you are not wealthy, it becomes much easier when you have affluence. 9. Security becomes important to you According to David Forbes, private office at Estet Agent Savals, there was a time when people flaunted their wealth, but now they don't. Because priorities have changed and security is on the top of the list. Many rich people, even celebrities, choose to remain low-key because they realize that they will become a target. Reports showed that after being robbed of more than $10 million in jewelry at gunpoint in 2016, Kim Kardashian West, who always flunted her diamonds on Instagram on the show keeping up with the Kardashians, toned down her social media photos and no longer wore diamonds in public and always had 24-hour security. If for adventure you flaunt your new status to the public, after a while you might prefer to live like a pauper if it would make people live you alone. 10. Places you go to Certainly the gathering of the poor differs from that of the rich. Top conferences, fancy parties, exquisite hotels and restaurants are all added to your portfolio of places to go when you are rich. When you are rich, you will realize that there is a vast world waiting for you to explore. Instead of vacationing somewhere near home, you can now go anywhere. You can fly first class in and out of the city and country wherever you desire, lodge in a five-star hotel and order for room service. In the words of American anchor Nicole Williams, the world becomes your playground. You only need to make out time to play. 11. Less social media time Many people spend so much time posing for and editing photos so that they can get many likes on social media. Some individuals derive a sense of satisfaction only from the number of likes and comments they have on media platforms. Thus, they put in a lot of efforts to post flattering photos of themselves and the things they do on a day-to-day basis. However, once you are rich, you no longer have anything to prove. You only get on social media to relax or network with other influential individuals. More so, when you are rich, you will observe that many people who like or comment on your post are just faking it. If you check your DM, you will see that these same people are there begging for one thing or the other. 12. Value for your reputation Middle-class individuals may not think twice before posting a photo of themselves getting drunk with friends on social media or stepping into specific environments. They might care a little about what other people will think, but they also want to show that at least they are having a good time and they may think, besides, I have nothing to lose.  Wealthy people understand that if they reveal too much of the wrong side, they might lose clients and money. 13. Education for your kids The rich are known for spending more on their children's education.  However, one common aspect that changes downwards about many people becoming wealthy is equipping the kids with moral education. While the children of the poor have inadequate professional training and high moral teaching, many kids from wealthy parents usually get the best of formal education yet lack the knowledge of how to cope with the outside world. They become so used to money doing things for them that they do not learn to be self-sufficient. Being rich comes with changes, so when you begin to experience them like having to change your friends, getting bothered about taxation and so on, do not get overwhelmed. These changes are the result of your present phase in life.


Hold John Brown. It's really fun to have Lamar Jackson under center and to watch that offense with him Just running the football over and over again, but it's also really bad for Raven's pass catchers They naturally went with a run-heavy approach on Sunday against the Bengals and they threw it just 19 times So even if a wide receiver had a 50% target share in that offense that wide receiver still wouldn't have hit 10 targets And remember those targets are coming from a quarterback Lamar Jackson. Who's a raw rookie? He's got to develop a lot as a passer still the thing is though You can't just go sell John Brown right now No one's gonna buy John Brown in fantasy football But I do think that dropping him might be a little bit premature Because there's still a chance that we see Joe Flacco this year and the Ravens do have a really nice upcoming schedule They get the Raiders Falcons chiefs and buccaneers and you never know Lamar Jackson could also improve as a passer as well So don't get rid of John Brown just yet Don't drop John Brown, but I will say that having Lamar Jackson under center is a definite downgrade for all of these Baltimore pass catchers


Welcome to the 11-20 talk by Herschel and Andrew. They are graduates of the Westford High School and they're going to call it soon this week. So take it away. All right. Hi. Our talk will be SCUA, Extending Distributed Tracing Vertically Until the Next Colonel. I'm Andrew. And I'm Herschel. Yeah. We did this as part of the MIT Primes Research Program for high school students. So first let's talk about distributed systems. So nowadays applications are getting more and more complex and they are no longer monolithic. So they're now written as distributed systems. The advantage of that is that you have modular development, continuous deployment, and better scaling. However, well, you can see them increasingly in large companies like Twitter, 2013. The problem with them is that they're hard to debug since there are many small services that operate, that depend on each other. So let's look at an example distributed system for, say, something like web search. So the user first makes a request to the front-end service and then that front-end makes a request to the web result service, which then contacts the page rank service. And then it returns results to the web results and then the web results are returned back to the front-end. Then it gets the images, which uses visual rank and so forth. Now suppose that a user is unhappy about search results being returned to slowly. How do you tell where the problem is? And this is where distributed tracing comes in. So distributed tracing lets you monitor and troubleshoot these distributed systems. So it helps you discover latency issues and it helps you find out what services depend on each other and helps you find where the issues are recurring. It traces specific requests as it propagates through the entire distributed system. However, distributed tracing tools nowadays miss a lot of things because there's more to performance than meets the distributed tracing tool. So there might be other services running on the same server and there might be kernel bugs that cause performance issues and even security patches like Spectrum Meltdown can have pretty significant performance impacts. So the question is, can we gain visibility regarding these issues via kernel? And that's our goal. So how did we approach this issue? We started with the Yeager distributed tracing framework. It's a tracing framework built by Uber, released to the open source community, I believe very recently. And it's a fairly mature system. It's actually used in production by Uber to as their own tracing infrastructure. To this we added LTTNG, which is a Linux kernel trace toolkit that is built to gain visibility into the sys calls and the kernel events that are generated while an application is running. When we combine these two, we get scuba. So now let's back up and talk a little bit more in depth about how tracing actually works. So as Andrew said, the goal is to follow an individual request as it propagates through the entire distributed system. So you start with a front-end request. And now with the front-end, the first step that it does is generate a context for this request. That includes a trace ID, a parent ID, a span ID, and whether or not this is sampled. The trace ID identifies this individual request throughout the entire system. It's a unique identifier for this request. The parent and span ID together are used to construct the causal relationship between a bunch of different services. So in this example, you can see the front-end request has no parent ID, and it generates a random span ID. Then when it contacts the web results service, the span ID of the front-end becomes the parent ID of the web results. And so forth with the page rank. And then when the front-end makes an additional request to the image of service and the visual rank service, then the parent IDs and span IDs are set accordingly. The span IDs are randomly generated and the parent IDs identify the parent span of that individual thing. So what exactly does this span entail? A span usually identifies a specific amount of work that is being done by an individual service and it's marked by a start and end time. Additionally, the user space application can attach logs and different events to the span so that they can gain visibility into what that individual request or that span was operating on at the time that that span was generated. Now, in addition, the front-end, when it gets this request, it actually usually does a, generates a random number and decides whether or not to sample that individual request based on that number. The reason behind this is if you tried to collect the span, all of the trace data for every single request that came in, the volume of data would simply be too large. And so while it is possible to do this in development for testing purposes, in production, usually a sampling rate of say one in a thousand is used. Now, if this entire trace is supposed to be sampled, then all of the different services will report the spans that they generate to a central service, some span aggregation service. This in Yeager is used as the collector service and that then stores it in a database which can then be queried through a web front-end. Speaking of that web front-end, this is what it looks like. So you can see the top-level request and then the length of that bar is the duration that that individual span took. And then you can see the causal relationship between each of these based on the indentation of all of these services. And you can also look at how different services are operating concurrently and when they start and end, how long each one takes. So it's fairly easy to identify a bottleneck in terms of let's say something's taking too long. You can simply look at the length of the bar if it's too long for what you expect, then you can identify that as your bottleneck and that was what causes your top-level request to take too long. So a little bit more detail on how SCUWA works. So already a user space application is running. We attach a Yeager client to that which collects these spans and then reports them to the Yeager framework. So this is already built as part of Yeager. So we didn't actually have to do too much specifically in the Yeager framework to anything to change that to make it work with our system. Now the Yeager client, we did have to modify which I'll talk about in a little bit. Now when the user application is running, it's gonna be making a bunch of different syscalls into the Linux kernel.  For example, a kernel event could be a scheduler event switching that process off of the CPU and putting another one on. And that usually happens immediately after a blocking syscall is made. LTTNG already allows us to collect these syscalls and kernel events and collect them using a set of kernel modules that LTTNG provides. So we needed a way to propagate that Yeager context for the trace into the kernel. And so we did that by using PROCFS with our own custom kernel module. We stored that data in the task structure which is the thread specific data structure that the kernel uses to identify each individual thread. You can think of it as thread local storage in the kernel. Now, what we did is combine the data from the task struct which contains the context and we attach that to all of the syscalls and kernel events that LTTNG is generating as part of its kernel modules. We propagate that information back into user space using an LTTNG adapter that we built and then report those into the Yeager framework using the conventional methods of reporting different spans. So to recap, first the Yeager client propagates its context into the kernel, then it stores that information in the task struct. When the user application generates syscalls or kernel events, LTTNG modules reads the data out of the task struct, pairs that information with the events that are generated and then eventually those events are then propagated back up into user space through the LTTNG adapter and then the Yeager client as well as our adapter both report to the Yeager framework. So the Yeager C++ client that sends its context into the kernel that took around 25 lines of modification to the existing Yeager client library in C++. We treat each Linux kernel event as the next level in the span hierarchy. So let's say there was a single span that was running for the visual rank service. Each syscall that the visual rank service makes appears as another span beneath the visual rank service and then all of the kernel events that are generated. So like RCU events, scheduler switches, allocations and freeze of different kernel memory. Each of those becomes an event in the logs of that span, of the kernel span that it's under. And our modifications to the LTTNG kernel modules in order to tag each span with the associated context information took around 80 lines of code and our LTTNG adapter took around 250 lines of code. So now we wrote several programs to help evaluate how well we did with this. So first we wrote a correctness tester. We wrote a small C++ program that just creates a bunch of threads and makes about 10 different syscalls. So this is just to make sure SKU is actually recording the syscalls as expected. So we found that they were and it appears that LTTNG actually does not instrument a few of syscalls that are called very often like get time of day. And the events that happened during these syscalls were properly recorded as logs. We also evaluated the performance using two different benchmarks. So they're both running on the same machine with a sampling rate of 0.1%. And for each scenario, so we have no tracing so we just turn everything off with unmodified Yeager. So we just included the normal Yeager client with the normal span creation. And we also, the next one is where we used our modified Yeager client. So this is the Yeager client that's modified to report the context into the kernel whenever spans are created. And the next one is LTTNG without Yeager. And that's just to see the overhead that LTTNG imposes. And then finally, we have scua where we combine both the modified Yeager client and LTTNG recording the syscalls and events. So the first such program was a small HTTP server written in C++. We used AutoCannon as our benchmarking tool. So we send a million requests over 10 connections as quickly as possible. And then we measured the latency and throughput under each of those scenarios. So here are our two graphs. So you have each of the benchmarking scenarios on the bottom axis and then the throughput or latency on the y-axis. So the first, this is our baseline performance. This is our unmodified Yeager which introduces a little bit of latency but nothing on throughput. We also have Yeager plus PROC FS. So in this benchmark, it decreased throughput and increased latency by quite a bit. LTTNG alone also has moderate amount of overhead with throughput especially. And then with scua, we combine all of those. So in the end, we have a 12% throughput decrease and about 200 microseconds of extra latency per request. So the next benchmark we used was Fortunes. So we borrowed our code from the tech and power web frameworks benchmark. What this basically does is queries for Fortunes from a database. In this case, it was Postgres. And this is intended to be a real world application to simulate a real workload that someone would do instead of the hello world example. We used a similar benchmarking process but we ran AutoCannon twice because Java and we did it with 100 connections to exercise Spring's threading model. This is what it looks like after we run their benchmark. So you can see each sys call appears below. For example, the Postgres query. So you see it's doing a send to and a receive from which is expected. And you can see each of those logs that happened during the receive sys call. Like for example, you can see it did a context switch and it did some RCU and datagram copying and whatnot. Again, here are graphs. So that's our baseline performance and when we add Yeager and even our modified Yeager doesn't do anything to performance and LTTNG decreases throughput a tiny bit and SCUA ends up with a about 6% performance decrease in terms of throughput and a little bit of extra latency on average. So we discussed our performance overhead. So the unmodified Yeager is negligible. LTTNG decreases throughput and increases latency since it's recording all of that data. We could improve this by only enabling some of the instrumentation points because for these benchmarks, we enabled everything. All sys calls, all events. Our modifications to Yeager cause additional latency depending on the benchmark since each Yeager library is written differently. Performing sys calls is quite expensive even when you're only doing it for every 1000 requests and LTTNG and our adapter ingesting the kernel events also perform more work. So that performance degradation is expected. A note about the tiny HTTP benchmark. Each transaction is less than a millisecond. So the latency impact appeared to be extremely large even though it wasn't that bad. All right, so looking forward, one of the things we hope to do is improve our performance even more. So currently with the fortunes benchmark we had around a 6% decrease in throughput and a very small increase in latency as well. However, we think we can get that down even further and we, Andrew outlined a couple of the ways we plan to do that on the previous slide. Another thing is simplify the installation process of this entire system. So currently we require modifications to the Linux kernel. So you have to recompile a custom kernel. We have a modified version of LTTNG modules. So those are the kernel modules that are part of LTTNG. Those need to be, those are custom as well. So you need to recompile those from source and install those properly. And then there's other modifications we did to the Yeager clients as well. And so basically putting all of these together to make the installation process and the usage process a little bit simpler would be nice. One of the other things we were looking into is adaptive sampling reconfiguration. So a talk that Lily gave earlier at DEF CON was talking about how you can modify the tracing parameters in real time to adaptively add different instrumentation points and logging as you detect that you need it. So if there's a specific service that seems to be taken too long or is too slow, then you can add additional tracing to that specific service in order to get better insight into that specific thing. So we were thinking you could also do a similar thing to decide whether or not to enable SCUBA. So you only would enable SCUBA if you detect that a specific service is taking too long and then you can gain insight into the kernel level on goings of that service in addition to the user space application itself. Another thing we were looking into is attempting to trace SCUBA with SCUBA. So Manio was doing some great work on replacing the existing SCUBA tracing framework with Yeager. And we were thinking about if we could integrate SCUBA into SCUBA basically to show another example that SCUBA can actually trace real world applications and additionally to measure how much of a performance impact it has when doing so. So in conclusion, we can distribute, we can use distributed tracing to monitor and debug all of these complex distributed tracing, distributed systems. However, current distributed, distributed tracing frameworks miss kernel information. And so we developed SCUBA to integrate the kernel level data from LTT and G with the information that Yeager is already collecting. And SCUBA has some impact on throughput and latency while it's not that bad and it could be used for some applications. It may be too large for other applications. So it depends as of now on whether or not it's applicable to production systems. Our code is open source. You can access it there. Really quickly we'd like to acknowledge Raja who mentored us through this process and the MIT Primes program. Hello. All right, here we go. Okay. So with that, we'd like to take some questions. Here's the microphone, it's over there. Thanks for presenting that, that was really cool. Do you have any plans for contributing any of that work back upstream to Yeager? Right, so our modifications to Yeager are fairly minimal. The thing is that they actually do have a fairly significant performance impact as of now. Or they have, they cause the differences that they have forced the Yeager client itself to propagate its entire context information into the kernel for every sampled request. So I don't think it would be, I don't think we should directly contribute back to the Yeager client, but I think it would be worthwhile to maintain like a set of patch files, say, that can be applied to the Yeager client to enable the skewer tracing integration. So while I don't think we should directly contribute back, we can still build off of whatever they're working on. Oh, I would encourage you to reach out to them and discuss it because I think they'll be very interested. Okay. Any more questions? Oh yeah, that was a great talk, thanks so much. So you're doing service calls into the kernel, so a service writer typically wouldn't necessarily know what the meaning of those system calls are, so have you got any tools to help you break out whether it's like networking stack it's entered or whether it's like scheduling, accessing file system, et cetera, to help those kind of users? So we could do some sort of thing where we group different syscalls to say networking or file system or a set of categories such that you can see all of your networking syscalls together and then all of your file system calls together and so forth. So we could do that. As of now we're just pulling the syscall name or the kernel that name directly from LTTNG and we're not actually doing any analysis on it and we're just sending it up to the Yeager client or to the Yeager framework. So right now we're not doing any introspection but we absolutely could. Okay, thank you very much. As others said, thanks for the cool talk. I had one question about LTTNG versus EBPF. Did you look at all that modification or what would be needed to work with EBPF instead of LTTNG and are there kind of pros and cons or shortcomings or reasons that you picked one versus the other? You did. So we looked at EBPF briefly. The thing with EBPF is that as I understand it it's mostly used for networking related. So you could absolutely capture syscalls and different sorts of things that are networking related using EBPF. However, in order to capture a grand picture of all of the different events that are going on in the kernel, we opted for LTTNG. Now we were actually considering using EBPF to propagate those spans, the span context between kernel to kernel. So the user space application wouldn't actually have to send its trace context with its request. We could actually do that from kernel to kernel using like an extension to TCP or something like that. However, it just seemed like it would be a little too complicated and then it would be difficult to represent the causal relationship between those two kernels properly using the current Yeager framework. So we looked into it. I'm not sure it's exactly right for what we were trying to do though. Cool, got it, thanks. Do we have left? All right, thank you. Can I see a little bit? That was a great talk. That was a great talk. Great, thanks. So I just got straight to that. Thanks. I'm sorry. I'm sorry. I'm sorry. I'm sorry. It's okay. You're doing great. You're doing great, actually. I don't know how to do this, but a lot of time it all just starts to take up a little bit. You can see it was small It's a jail connection. You know, it's totally normal. Okay, good. Also really important, I'd love to start with this book. Sure. And I'm pretty familiar with it, just to be aware of that. And I think this book is very cool. Yeah. So, one of the... How much does Dan? So, he did a good shoot. Oh. I don't know if that was good for you. Good for you. That's awesome. What company? You go out there? Oh, thank you. Your books? Your physical books? Yeah. Go on. Welcome back. Can you use this one? Yeah. Can I use this one? Sure. Do you like this? And you're calling... Oh, you're very used to it. So, since you have some time, it's good if you just take this open set this inside so that it's like nice and proper. Yeah, so, put this in your pocket and then just get this from underneath your coat and fix this. Okay. Okay. Oh, that's my phone. It's the office. Good question. All right, good. And, yeah. How's the audio on the back? It's good. Could I try? No, more. Okay. Okay. That needs control from there. Okay.


What's going on everyone? Sam here with late in sports cards. We're ripping 2022 Bowman Chrome Baseball light eight box break number two Random team style. Here's a look again at your random results As always you can find these on the website under the results tab as well as the link that's in chat Good luck here everyone. Let's pull some more color man. They're loaded with color last break So see what comes out of here our phone cube Make it present felt as always you got a purple to start it's Garrett Mitchell for the brew crew to 250 Nice one there Milwaukee Congrats on that brewers Volpe and Willie Fannis in Victor Nelson Velazquez Cubs self-relic and first junior Perez going to the A's there you go Bowie for the mini diamonds. What are we doing man? Throwing packs of top loaders all over the place here White speckle Manny Machado to 199 Padres nice one there San Diego James Triantos and Rossman for do go on the first mini diamonds Congrats again Padres Couple of cards in that pack for you guys Royce Lewis Ryan Acunha first Eric Hernandez first Well young studs right there in the AL central that is Yendri Rojas mini diamond for the Padres Gold of Adrian Polencia going to the Angels Congrats on that LA crispy 50 of 50 on the true gold Adrian Polencia nice one there congrats Chris came to the league Jackson Job Josh Lowe shades of greatness rookie mini diamonds Michael Hernandez for the Orioles up Dan How you doing buddy Samuel Munoz Alexis Hernandez 17 to go on the next one guys breaking next that's warming Bernabelle on the refractor to 499 Rockies 17 to go on the next one Ryan Wreckley mini diamonds Tired bud, but making it there you go Dan. I feel that All right $50 a spot on it as well Loaded with color in this product You're looking for five Exclusive black and white mini diamond parallels per box Exclusive only to Bowman chrome light you will not get them in hobby or in choice Almost lost the pack in there as well. You will not get those in hobby You will not get those in choice. You will only get them in light As well then sir Guzman going to the Angels black and white mini diamond there's speckle Jose Miranda did 199 rookie for the twins congrats Minnesota crispy again When's doing well O'Neill cruise rookie for the Pirates Jackson Merrill shades of greatness. There's mini diamonds Colson Montgomery white socks on the second second product prospect card George Valera came to the league a couple of firsts on the back there Oscar Colas being one of them There's white speckle trade Sweeney to 199 Yanks nice one there New York Curtis Mead and West calf on the mini diamond Congrats on that. Oh nice.  Thank you there Sean Sean. Just drop you guys that link Breaking next eight boxes There's yeast and more belt for the Rangers 16 to go on the next one There's a J rod rookie got white speckle Corey seager to 299 note 199 for the Rangers Polencia and Vasquez Wilford Varys for the white socks nice one there a white socks Pedro Pineda and base All right next box block here again everybody See what we've got There's then your quaver first for the Rangers on the mini diamond Black and white mini diamond Jeremy Pena rookie got a shimmer coming up. That's warming Bernabelle cold and freezing alarm Purple coming up here Alexis Hernandez on the first the 250 going to SG with the Cubs Congrats SG nice one there, buddy Cubs hit Eddie's Leonard and Jordan Walker black and white mini diamonds for the Cardinals. That's one Cardinals Jason Dominguez came to the lead. There's mini diamonds Louis on Hella Cunha for the Rangers One yep as refracted a 499 Cardinals Peace There's blaze Jordan for the Red Sox cool one there Congrats on that Red Sox Wonbin show blue Denzer Guzman right on top true blue to 150 nice one there angels Lonnie White on the Invicta Max Muncie and Robert Hassell going to the Padres on the mini diamonds Sean's dropping guys the link again. I believe we're still at 16 to go 49 99 a spot Get you a random team and an eight boxer of Bowman Chrome light white sparkle Lurad to two or two one ninety nine Dodgers and Edie Cappy for the Marlins nice one there Marlins more Spots and break little it breaks later on are coming in. Thank you guys for that one as well Frankie and Charlie base Eric are picking up a bunch of teams. Thank you Eric appreciate you appreciate you Neil Cruz shades of greatness There's Nick York again for the Red Sox on the mini diamond prospect guard Refractor Alexis Hernandez going to the Cubs again to two or four ninety nine Nice one there congrats SG any diamonds Ricardo Cabrera first for the Reds Royce Mark and Tom Refractor Jaren Duran on the word on the variation the home run cart Congrats on that Red Sox. That's actually pretty cool Steve G. That's a cool card. That's an awesome card Congrats Steve The four ninety nine on the Jaren Duran awesome one there And many diamonds Caesar Prieto, I don't hate that card. I really don't base there Mini diamonds Simon Juan is the wall For the Mets And white speckle Pete Alonzo for the Mets as well. That's gonna be number two at one ninety nine Congrats Mets on the polar Pete the Jesus and Jason Chorio base a bunch more Dual case pots coming in too. Thank you guys Get those rocking and rolling. Those are fun, man. Did you wow good stuff on to the next one? Good luck, everybody Mini diamonds Marco Luciano Shimmer Zach Vene nice one there for the Rockies cool card Willy Vasquez We've got Anthony Rizzo to one ninety nine white speckle for the inks Joey Weimer first and a Pedro Pineda for the A's on the white speckle or black and white mini diamonds Any diamonds James Wood for the Padres? He's a beast 15 to go. Thank you guys Yasser Mercedes the 499 for the twins Chris B. Congrats, man Nice one there. Nick Gonzalez Jose Rodriguez Wander Franco shades of greatness and Brian Acuna black and white mini diamond again for the twins Chris back-to-back good cards back-to-back packs Nice one there, man. Pink say a Suzuki to 299 Congrats Cubs That's going to SG Congrats, man. Nice. Say ah Rekelvin to Castro blue Jace And Eric Hernandez on the first black and white mini diamonds kind of a color match with the white socks there and base All right, we're on to box number Six three Detmer's the 75 61 out of 75 congrats on that angels Angels is Crispy congrats Chris killing it right now, man. Any diamonds Lurad Dodgers base their bergola one been show refractor Nick York. That's going to the Red Sox Nice one there Boston the 499 and You're about on helice mini diamonds for the A's Jeremy Pena and very badly damaged unfortunately. It is just a base. I'm sorry about that Astros Lexus Hernandez for the Cubs There shouldn't be out of there. I think they're just very rare shady Noel V Marte for the Mariners to 199 on the white speckle Yeah, they're just much rarer obviously than they are and like hobby and choice They're like case hits They're Samuel Munoz for the Dodgers on the first mini diamonds base and last one here white speckle is Randy Rosarana Yeah, Joshua. Do you have the stats on that Victor Acosta on the black and white mini diamonds? Joshua's always got our odds for us For autos in this I hope you two you are too shady. Thanks, buddy Appreciate you a bunch of orders came in see what we got here Down to 13 to go now sold out on our first hobby case as well. Thank you guys 13 to go now on One in 40 cases. All right. They are not case. It's then Yeah, but they're the the speckle autos. I want to say to the black and white mini diamonds autos I didn't know how I was just kind of assuming it was the same as what's called as topscrome Platinum that's kind of where I got that number from in my head, but yeah, it makes sense that it's a lot Rarer than that. But yeah, they're significantly more expensive than the the regular autos. Yeah, they're the mini diamond ones. Yeah They're nice. Yeah, I have to imagine what the becaro goes for the the trip the passion pulling adjacent choreo of that Oh my god That'd be insanity dude Mini diamonds warming burnabelle Holding freeze and alarm. There's purple Matt Chapman to 250 for the blue jays nice one there Toronto Willford Barris many diamonds Trace weenie for the inks Nice one there New York Had Bert Perez it came to the league Green George Kirby. Wow Graham Ashcraft speaking of mini diamond auto boom Not numbered go into the reds Congrats since he Gunner each Congrats Gunner will mag this one for a my man. That is awesome. Super rare card Wow Let's go man. Literally spoke that one into existence Holy cow That's insane. Then our green George Kirby to 99 nice one there for Davis mini diamonds The Pirates was a crazy pack crook. I agree with that one.  That's yearling confidant To 199 there you go again reds.  No, you agree. It's disturbing warming holding freeze and alarm on the Invicta Jason choreo nice one there for the guardians on the mini diamond Daniel or I know when we hit it 10 packs later Honestly kind of insane right there. There's a Jason choreo base on the back as well And this is a look at the stack of color. We got rocking over here. That's insane man Dude, there's so much color in this Alright, see what we got next. Good luck here everybody. Let's go Dolphins Often stink Harry Ford for the Mariners mini diamonds My dropping that link again strong I'm gonna chop you the link for the next one. We got a true blue coming up of Jared Kelnick. It's a 150 94 out of 150 nice one there Gutierrez, Roger Carayas nice run on those two 13 to go guys break it next is our third eight box break of this Mike trout refracted a 499. There you go angels mini diamonds Royce Marcantana mini diamonds George Valera for the guardians Amic Luis on Hella Cunha at a 150 nice one there shades of greatness for the Rangers Cole Henry base The over-pecuero mini-diamond. There's a red Victor Acosta One out of five go into the Padres on the Invicta boom Congrats San Diego man. What a break. This has been Eric B on the one spotter Picking up the Victor Acosta red Let's go dude Betside I have to imagine it's basically the same There's a wander rookie in there Plus a Joey Vado to 199 It's basically the same as regular chrome would be my guess Zack Dean and base. All right. Let's do a quick recap here. So there's color recap. We've got Jairan Durand red socks say a Suzuki Cubs Matt Chapman blue jays Alexis Hernandez Cubs Garrett Mitchell Brewers Noel B. Marte Mariners yearling confidant for the Reds Joey Vado Reds Randy Rosarano Rays Anthony Rizzo Yankees Pete Alonzo Mets Luis Rodriguez Dodgers Corey seager Rangers Trey Sweeney Yankees Jose Miranda Twins, that's my name a shadow for the Padres Jared Kellnick blue for the Mariners Denzer Guzman Angels Luis on jalicunia to 150 atomic Rangers George Kirby Mariners Reed Depmers Angels we had a Adrian Palencia Angels Victor Acosta red Invicta to five and Graham Ashcraft mini diamond auto going to the Reds. I'll do it for the break guys Thanks again for the fill and next up another one of these


Welcome to All Hands Update, I'm Petty Officer Jen Blake. Naval Education and Training Command, or NETC, announced the 2014 Health, Safety and Fitness Flagship Award winners. The award is given to commands that have the best programs encouraging health and fitness among service members and the civilian community. The Health, Safety and Fitness projects are part of the Navy Community Service Program, or NCSP. NCSP promotes volunteerism and community service to help empower youth in their communities. Eight commands were recognized this year for their outstanding community service. Award winners and honorable mentions will receive certificates from NETC in recognition of their exceptional accomplishments. For a complete list of this year's winners, visit the NETC website.


Local reality in Tizca was now an open wound, a rent in space-time from whence the powers of the warp spewed and festered, worming their eldritch tendrils into the fabric of creation to pervert and corrupt. Linear chronology ceased to function in any meaningful capacity. All chronometric marks from this point on are useless, as two timepieces held side-by-side would record completely conflicting time streams. From the ships of the Sancir host still in orbit, it appeared for all the world that the city of light had been swallowed by a roiling contusion on the face of the planet, a sickly haze of clouds the color of things that simply should not be. All within this pocket of nightmares appeared from without to be hazy, incoherent, almost dreamlike in aspect, and any who entered were either not seen from again or emerged with hours or seemingly days having passed in the minutes since they departed. No reports can be trusted entirely, if any could have even been made. All communication, be it mundane or arcane, from within or without had been completely severed. Logisticans and stratagoi positioned above in the void were helpless, sundered from all contact with the senior commanders of the host and unable to even assess the progress that was being made. Their astro-pats were all screaming, or at least those from whom the shock of the Wharf rifts emergence had not proved to be their doom. Many officers assumed that this was some sort of doomsday weapon unleashed by the 15th Legion, the final spite of Magnus the Red in the face of Imperial Sancir, however they had all watched from afar the sheer fury with which the Thousand Sons had met the wolves and the talons of the Emperor with. All that could be done, however, was to log timestamps and await any word from the Wolf King or the Captain General. None would countenance their deaths. For the Lord of the Custodes to fall was unthinkable enough, but that a Primarch should die. Such a thing was surely impossible, although it seemed that the impossible was becoming ever more dreadfully possible upon the damned world of Prospero. A large part of Tizca was, albeit difficult to ascertain from orbit, not affected by the Warp Storm, only obscured from the void by its visual and awe-specs interference. What Imperial elements remained in infrequent contact with the vessels above were issued perfunctory orders to continue with their previously assigned missions, and were assured, albeit with little confidence, that the Sancir host was still very much in control of the situation. Whether these instructions were followed or not depended entirely on the ears of those they reached. The Black Cull, for instance, did not precisely heed the words of the orbiting stratagoi, but followed their previous mission out of sheer, bloody-minded battle lust, continuing the sack of the temple-archology of the Raptora Cult, bathing the Pyramid and its surrounding areas in torrents of phosphics. The Twelfth Great Company, however, seemingly disregarded their orders and immediately plunged into the storm to seek their Primarch. The Sons of Horus continued with their purgation operation completely unopposed, either by the forces of the host or the Thousand Sons. At the Valparine Bastion, the resistance of the Thousand Sons had collapsed after the change wave triggered by failed Toron had hit. The Magisters within the Bastion were now having to fight there once brethren, those changed in flesh, as much as any Imperial elements without. The Carinid Sentinels and the Wolves both, seeing their opening, renewed their barrages, now unmitigated by the Kinney Shields of the Thousand Sons. They reduced what remained of the Bastion to dust in short order, burying the raging Fifteenth Legion Astartes beneath hundreds of tons of ferrocrete-reinforced marble. As resistance from the Thousand Sons' pockets yet without from the storm crumbled, the Sixth Legion elements within mechanized transports, as well as the swift-moving Custodes grav tanks and jet bikes, sought to run down whatever Magisters they could find, to free up all possible censure-host forces that they may surround the Warp Rift, or even enter it, and lend aid to their Captain General and the Wolf King. Before one relates what will no doubt be the climax of this most terrible of Chronicles, one must elaborate on the means of tracking precisely what occurred within the storm. In point of fact, I cannot use the word precisely. For such a thing simply cannot apply to such an event. All that we are able to establish has been reconstituted from as many sources as are available, but all are fallible in the extreme, especially when faced with the sheer power of the Immaterium in the manner seen upon Prospero. One need not remind Acolytes of the unreliability of personal accounts, either from those who had vested interests in representing a certain perspective, such as the Wolves, or those for whom certain concepts simply do not enter into the framework of their constructed thoughts, such as the Legio Custodes. Just yet, there are translation errors, such as the inherent difficulty in rendering silent sisterhood thought-mark into high or low Gothic. Beyond that, Vox's screeds are almost incomprehensible, even those logged in high-gain field apparatuses carried by certain legionaries. What has been recovered often contains cascades of static, fragmentary orders, in some cases orders that were only issued hours after their transmission had been recorded, and in a lot of cases, screaming. Screaming that is disturbing the human, and at the same time, not. Orbital tracking of the battle, as mentioned, was either conducted visually or by all specs pings of ident tags, but was completely futile. All sensorium data, where it could even be logged, made utterly no sense at any given time. Even neurocortical interrogations of captured prisoners, or volunteers from the censure host itself, only ever revealed glimpses, and often ones that directly contradicted all other information I have previously mentioned, or even each other. There are independently verifiable accounts from many sources that speak of heroic battlefield actions performed by warriors that had previously perished earlier in the conflict, or accounts that assure that certain individuals had perished, despite it being beyond doubt that they survived this final stage of the battle. Insummation. All is confusion. This truly was the impossible battle. All the facts surrounding it defy all attempts at logic, for such is the nature of the immaterium. It undermines the means by which reality itself functions. What hope do we have of sanely structuring accounts of anything that is involved with it?  What work you will hear may contradict what you have previously known. I can only say that this work is done with the best of scholarly attention and ability, and represents all a humble chronicler may do in the face of the terror of this lunatic universe. At best estimates, the vortex caused by the death of the warlord Canis Vertex and its erstwhile master, Calophis, had swallowed the core of the censor host, containing the Primarch Leman Rus at the head of some 12,000 of his wolves, Constantine Valdor and around 400 custodians, and approximately 1,500 null maidens of the Silent Sisterhood, as well as two cohorts of the Tyrion Exo Guard Auxilia Regiment. Ranged against them were some 7,000 of the Thousand Sons, as well as Spire Guard divisions of disparate size. The 15th Legion was now commanded in its near entirety by 3rd Fellowship Captain Hathor Mott and 1st Librarian Azhik Ariman, all of whom had fallen back to a new defence cordon set between the archaeologies of the Athenean and Pavani cults. The greatest concentration of these forces was around the Pyramid of Photep, to which thousands of civilians and routed Spire Guard still sought to retreat as the final bastion available to them. The establishment of this cordon had largely been aided in the chaos that was caused by the emergence of the Vortex, as well as the appearance of seemingly thousands of mutates within the reaches of the city. All of this, however, merely slowed the advance of the censor host. It did not stymie it. The 6th Legion had faced down the worst horrors of the galaxy in their two centuries of campaigning, and the Geno-engineered Ligio Custodes were literally constructed to pay such things no heed. Russ and Valdor knew that momentum could not be spent. Both constituted whatever forces they could under their direct command, in the face of total communications blackouts, knowing that all other elements were moving to the same objective they were. Naturally, many censor host units were simply unable to link up with the main bodies of Russ and Valdor. Some were lost to the unnatural eddies of reality that the Vortex tossed around like churning water, cursed to wander aimlessly through fractally repeating ruins until the warped squall blew out. Others were yet engaged with disparate units of thousand sons, forced to fight vicious, unrecorded miniature wars as creation was cracking around them. Some records noted, larger bodies of troops caught in the eddies were often forced to fight the remnants of these petty wars, for such was the fury of some engagements that those who survived it found it impossible to ward off the coming of the flesh change. Many hundreds, indeed likely thousands, were debased creatures roamed the ruins of Warpachote Tizca, horrifying amalgams of tumourous flesh or feral beasts in the shapes of wolves. Their origins are known, no longer mattering. The one aspect that slowed the censor host advance was the wariness of what psychic assaults they may face once they threw themselves at the thousand sons once more. Consequently, Russ and Valdor attempted where possible to organize their forces into columns, at the core of which stood cadres of silent sisters. Such maneuvering, under total lack of communications, was laborious in the extreme, granting the 15th Legion even more time to shore up what defenses they could around the Pyramid of Photeb. Such precision care was, for the host ultimately unnecessary. When the battle was joined, when the fury of the censor host was brought to the lines of the thousand sons, they were answered with entirely mundane bolter fire, as opposed to the eldritch howling of warp fire and arcane lightning. The 15th Legion seemed to be eschewing their powers, and one must only assume that the terror of the flesh change stayed their hands in that regard. Initially, it appeared that this final battle would be fought as of old, with bolter and a blade and raw transhuman rage, but as the heavy transports of the wolves crashed through their lines as the siege artillery of the host annihilated their readouts, many of the magistres of Prospero abandoned their restraint and their lives. Loosing the power of the warp through their bodies, their powers heightened now to undreamed of levels.  The thousand sons that did died, hacked to ruin by their once brothers, once their sentience had fled and their minds became as broken and corrupted as their bodies. Yet in these sacrifices time was bought and vengeance was reaped. Three times did the censor host throw itself at the lines of the thousand sons, and three times were such attacks repelled. Yet the numbers of the 15th Legion thinned with each assault, 7000 dwindling to 5000, the bodies of their fallen mixing with grey armoured woolen dead to form barricades of ceramite encased flesh, behind which the defenders prepared for yet another offensive. Cohesion was lost, units scattered, circles and fellowships mingling with no heed to any sort of formation. A scarab occult terminator would stand shoulder to shoulder with the 15th Legion line astarties, both covered by a spire-guard human with a heavy weapon, a grim equanimity found at the edge of oblivion. It was then, as the silence had fallen, as a breath was drawn before the plunge, that he came at last. The crimson king, Magnus the Red, had any words been exchanged between the brothers. One confined no accurate record of it. Genesha Kroll, knight-commander of the silent sisterhood, who witnessed the eventual conflict between primarchs, stated that Russ and Magnus did indeed speak, briefly, but as to what was said she knew not. Others who beheld the arrival of the crimson king disagreed with the soulless queen's account, stating that the two primarchs immediately flew into combat, with nothing but the wolf king's howl to announce it. This is just the beginning of the disparity between accounts of this confrontation. All appear to have been warped in some manner, both through the mythic aspect such a fight between demigod sons of the emperor will seemingly inevitably take on, and through the reality-shredding tempest that surrounded the pyramid of Photep. One focal point of agreement, however, is that the clash began with a howl of the purest rage from the heart of Liman-Rus. Beyond that we once again return to incoherency, although this is partly due to the sheer unparalleled speed at which primarchs are capable of engaging each other at. Of those present, it is likely only the Ligio Custodis, perhaps even only Constantine Valdor, who possessed any biological capacity to follow and process the sheer speed of their bodily movements. Liman-Ax met Silverblade with a fury that shattered sky and air. The cold rage of the lord of the rusts meeting the psycho-kinetic mastery of the crimson king. Nothing survived contact with their combat, not the architecture of Tizca, not the hulls of tanks, not the plate armor of Astartes. Any of the latter that somehow sought to intervene to aid their gene-father to protect them were simply annihilated before the combatants were even aware that an attempt had been made. The full force of Rus' martial skills were being levelled directly against every iota of Magnus' psychic might. Neither gave a hint of quarter, but even given all that was being brought to bear, to bring him low, even given the titanic capacity for etheric destruction made possible by two centuries of his brother's arcane learning. It is unlikely if there could ever have been any victor other than Liman-Rus. It is a general hypothesis that the Primarchs were built to fulfill a specific role that the Emperor had in mind. While Magnus' may only have been known to his father, Rus, perhaps more so than any of his brothers saved the lion and angron, was clearly a weapon designed for destruction. And the hell that had come to Prospero, in the etheric tempest that was tearing at the roots of all things, perhaps none but him could have so thrived. Though the Crimson King tore at his brother, wounding him on planes material and immaterial both, it was to Rus' that the final blow fell. Some related it as the plunging of his sword into Magnus' torso, but the prevailing account holds that the Wolf King bodily heaved his brother aloft and cast him down across a brutally armoured knee, sundering the back of Magnus the Red and defeating the Cyclops of Prospero utterly. At this moment, this instant played across a billion instances. It is related that a light suffused the entire pyramid of Photep, bringing illumination to an area that had until that moment appeared perched upon the precipice of a night eternal. It had no source, seemingly filling the air itself with an incandescence that was indescribable. Many presumed it a final trick of Magnus, but the sorcerer King appeared utterly unconscious, maybe even dead, and was in no state to be casting some form of esoteric incantation. If it could be said to emanate from anywhere, the sanctum of the Crimson King appeared the origin, but such identification proved impossible as the light reached a blinding intensity that forced all who beheld it to turn their eyes away, to dull armour auto-senses lest it burn their retinas in its brilliance. The storm, however, did not simply end, but now appeared to have a new locus. Howling winds began to form a vortex centred on the pyramid of Photep, tearing gales shearing away rubble and masonry and even toppling armoured tanks. Many relate that it was at this moment their Vox networks, previously silent or static, were invaded by a cacophonous choir of whispers, while others claim they heard not but booming wicked laughter. Yet others say that upon the winds was born the death howl of the world itself, the pain of a planet condemned to oblivion, and that cracks in the sky of creation began to rend themselves apart, ghostly fingers of things abominable intruding upon reality from the unknowable beyond. Shards of existence splintered, dimensions fracturing and inverting, slicing at minds and flesh as knives. To many it must have no doubt seemed that the Crimson King in his passing had broken the rules of all that was and is Chaos, but it would not last. The light snapped out of being, the storm bereft now of its locus faded, as if a flame had been put out, local reality reasserted itself. The bleeding of physical laws staunched. The Vox now exploded with frantic activity, ships in orbit and censor host formations across the city hailing their commanders with urgent requests for information. Those commanders, and those of the host yet alive within the former eye of the storm, surveyed the ruination around them. Of Magnus the Red, of his thousand sons, there was not a single sign. In the aftermath of this clash titanic, little was clear. Constantin Valdor immediately ordered a full sweep of the ruined Pyramid of Photep with all available resources, Imperial and Mechanicum both, to attempt to determine what had occurred. The area of the city had contained over 3,000 surviving thousand sons, and an approximate number of elite and veterans by our guard, Auxilia. There had also been as many as 10,000 civilians cowering in subterranean fiends and catacombs. In total, some 20,000 humans and transhumans had at one moment been present, and now simply were not. This was not merely that they were dead, there was literally no trace that they had existed in the first place. There were no bodies, no scraps of clothes or armor, nothing. Even weaponry capable of disintegrating a body in an instant, such as thermite armaments, could leave scorch marks. Radfages and viral cascades typically left an organic residue or slurry in their wake. Adepts of the attended Mechanicum Tagmata, well versed as they are in the arts of annihilation, as well as those of the Sixth Legion's Black Kull, were completely baffled, able to draw no conclusions as to what weapon or device the thousand sons or their Primarch had employed at the end of all things. Most conclusions that could be drawn at the time were only able to posit that the arcane was at play here, as it had been throughout those catatlysmic final hours. But as to how, nothing could be said with anything even remotely resembling confidence. At 1917, at local time, on the 734004M31, the censor host's ground forces succeeded in making contact with their ships in orbit.  Conflict, however, still continued in the devastation of Tizca. Not every thousand son had vanished. Isolated bands yet persisted, fighting hopeless retreats to some indeterminable, perhaps even imaginary, fallback location. Bands of mutates continued to attack all they encountered. While Russ gathered his wolves into hunter-seeker units, fresh reinforcements in the form of knights from House Malanax took to the field, the powerful war suits proving more than a match for the gibbering horror things that flung themselves at anything that moved. As many as 2,000 of the 15th legions still remained within the Argent Bastion at the eastern end of Tizca's walls, all that remained of the Eighth Fellowship, as well as a significant number of Psi Automata of the Castellex Achaomarch. The resistance lasted for maybe an hour after the fall of Magnus the Red, before they withdrew to the Bastion's lower reaches, affecting a hit-and-run retreat in face of a punitive offensive of Varragir Terminators and Ligio Custode's sodalities. Everything was only ended when a blank-eyed Leman Russ, operating it seemed on more rote than actual drive, took to the tunnels, butchering every single astartes he could find, with the dispassionate ease that would have been contemptuous if it had any emotion behind it whatsoever. From the records of some of the Custodians present, had the Wolf King been any other than a son of the Emperor, his behavior may have pointed to severe trauma. But of course, such a thing was not possible. Elsewhere, in the ruins of the Valparine Bastion, a division of Thousand Sons had emerged, having protected themselves from the Citadel's collapse through a superlative series of overlapping kinetic shields. Instead of bothering to engage any wolves or Custodes within the area, these astartes, now under the command of the line officer named Sul Contep, took to the Citadel's airfields to make flight-worthy whatever aircraft they could. When their presence was eventually discovered, and since your host forces dispatched to their location, the Magisters had managed to evacuate in their totality, packing what ships they could with civilians that remained alive within the area. Departing out over the Valparine Sea, they utilized the ash and steam clouds present to mask their exits. While some were taken down by Ligio Custode's equinox interceptors, great many disappeared from Imperial Aspects entirely. Sons of Horus Division of the host, having been entirely absent from the Vortex in Central Tizca, had now turned their operations to total purgation. Any who were not of the censor host were put to an unceremonious death. Their corpses left rot where they fell as green-armored astartes spread out through what remained of the city. In the Northern District, in the ruins of the Prosperine Air Guard's base of operations, the 16th Legion, and several knights of House Malinax, encountered survivors of the Spire Guard, and a significant quantity of civilians under the leadership of Seneshal Prime Lucretia Illuniri, who had been attempting to affect rescue operations as best she could manage as her world fell around her. During her rank would grant her some means of parlay, she voxed a demand to the commanders, Boros Kern of the Sons of Horus, and Anrak Hadratha of the Space Wolves' Black Cull. She demanded the proper treatment of civilians and non-combatants under the Lex Imperialis, and for the surrender of her soldiers once they had thrown down their arms.  The pitiless slaughter of every single civilian that remained within Tizca would continue for three days local time, including in its scope operations dispatched to investigate any potential thousand son's presence elsewhere upon the planet. What pockets at this point remained, usually handfuls of individuals, were treated to the same immediate butchery. At the time the sun sank along the smoke and ash choked skies of prosperous only city. Wolf King yet lived within its ruins, no plant, no animal, no human, no astartes, no mutant. Valdor at this point ordered the evacuation of sensor host forces, seeing no reason to remain, although Russ in typical fashion did not heed them. The Wolf King had resolved that his men would be the last to leave the planet. It was at this point, at the tail end of the evacuation, that the thousand sons that had fled across the Valparine Sea reemerged, making directly for the final Imperial transport arcs. Easily overwhelming the auxiliary present, and completely unbeknownst at this point to the wolves, the arcs made orbit, slipping past the Imperial ships in the prosperous skies, most of which had been dispersed into a second bombardment formation. Most destroyers dispatched to intercept annihilated one of the barks, but not before the remaining two killed all drive and power functions. Their signals now becoming lost in the orbital debris that had spread out from the remains of Prospero's wrecked, near-planetary void infrastructure. While sensor sweeps persisted for hours, no trace of the vessels could be found. It was eventually ruled that, as they lacked warp capabilities, those aboard would be rendered too helpless to affect anything of note, so they were simply presumed dead. Lehman Russ was the final set of boots to leave the ground. He storm-birded, dusting off from a shattered and ruined hellscape. As a final punitive act, a second orbital bombardment was conducted, incinerating anything remaining that could burn, ensuring that any of those who had somehow managed to escape the Emperor's censure would not live to celebrate their already completely hollow victory. As the ships of the censure host slipped anchor, Vox Beacons were ceded throughout Prosperine approaches, broadcasting the unmistakable Perditus Maximus single. The Lex Imperialis had ruled this planet utterly forbidden, and may approach under pain of death. This was Prospero abandoned, a world corpse, a planet of ash and departed pain, a choked orb hanging dead in the void where no sound ruled saved for the wind through burned bones. At best historical estimate, the cost of bringing the Emperor's writ of censure to Prospero was 30 million lives, of which the overwhelming majority were Imperial civilians simply present on the planet at the moment of the censure host's arrival. Data logged within the Administratum placed the number of civilian survivors at a net zero. The official line would forever be that the Prosperine branch of humanity, which had survived the turning of millennia, the terrors of old night and the renewal of the Great Crusade, had been annihilated in its totality thanks to the follies of Magnus the Red. The same was said for the 15th Legion, Thousand Sons. From 004 until a decade later, upon terror, as the walls fell in 014 M31, the Legion was officially declared extinct. The truth, of course, is that neither the humans of Prospero, nor its Astartes were all wiped out in one fell stroke. Notwithstanding the Astartes and civilians that had disappeared with Magnus the Red, there remained many thousands of both who had, through the vagaries of fate, been abroad across the galaxy when the Doom of Tisca was wrought. Many were simply put to death by Imperial forces they were serving alongside, usually before news of the censure of their Primarch, or indeed his fall, had even reached them. In one prominent example, 2000 Astartes of the 9th Fellowship under Centaur Rame were gunned down by the Ultramarines they served alongside. Similar justice was conducted by the Imperial Fists and the Salamanders, 2000 Sons forces they had previously counted as allies, but had been explicitly instructed to slaughter. It is perhaps noteworthy that at no point did any of the Astartes committing this fratricide attempt to aid the doomed and unaware thousand sons in question. Some naturally escaped by their own devices, the prognosticators amongst them becoming aware of their doom before it struck, and for these few, awaited a life, at best, of fleeing from the jaws of Imperial retribution. The largest of these contingents, independently verifiable to history, were 5000 Astartes of the 4th Fellowship, constituting its majority, who immediately ceased their great crusade assignment and fled to the stars upon news of Prospero's demise reaching its expeditionary fleet. Elsewhere, several thousand sons of Magnus stationed on Prospero's client forgeworld of Shauak had, similarly fled. Of the fates of these thousand sons, nothing can currently be said. In the chaos of the years to come, the threads of their stories are utterly lost. It is quite possible they may have reunited with their Primarch and their Legion before the siege had even begun, but it is equally likely many simply turned to a life of the renegade during the conflagration of the Horus Heresy. Perhaps siding with neither traitor nor loyalist. Perhaps they became black shields, or perhaps they simply chose to survive as best they could in a world consumed by madness. In total, the censor host had suffered significant losses in its prosecution of the battle. Some 49,000 in total and a massive quantity of armaments either lost or abandoned in necessity in the tomb of Prospero. This included several Titan god machines, much to the fury of the Mechanicum. Naturally, the majority of these losses were incurred by the Vilka Fenrica, some 25,000 confirmed killed in combat, as well as the entirety of its 13th grade company simply declared lost in the collapse of the Warp Vortex. This was a significant amount of the Sixth Legion's strength at a crucial time. The heresy would rupture into dreadful reality mere months later, offering the Legion no time to recover in any meaningful capacity from these losses. The casualties for the Talons of the Emperor, the Silent Sisterhood and the Ligio Custodes, were relatively small and somewhat unverifiable, but when we consider the scale of their commitment to the host, and their rarity and specialities, their losses can still be considered severe by any measurable metric. Some historians have even waxed lyrical on the loss for the latter formations, altogether less mundane, the status of custodian invincibility. Never before had such a large quantity of the Emperor's own life wards been committed to a single action, and even in instances where they had taken to the battlefield alongside the Master of Mankind, rarely had more than a few fallen in pursuit of their goals. Studies that had observed them in action, be they Thousand Son, Wolf of Russ, or Son of Horus, learned many a lesson from that day about just how the Custodes prosecuted their war-making, and notes were taken about precisely how they had fallen and when they did. On the loyalist side, darker rumors fastered, particularly around the ease and apparent experience by which the Oric champions of the Emperor had dispatched astarties so contemptuously. Some indeed wondered aloud if this had been a purpose they had been crafted for, although such opinions, when expressed, were rarely done so to ears untrusted. The ripples of the destruction of Prospero spread outwards from it, some discernable, others less so. Though seismic an event, an Imperial history could not simply go unnoted by the many, even if the Imperium's military regime did much to downplay its significance. A triumphant parade was held perfunctorily upon the censure host's return to Terra, one which Russ declined to attend, leading his wolves elsewhere. Val'dor's own journal notes that, according to the Wolf King, a king does not invite his blood-steamed headsman to a victory feast, although to call it the latter was quite a misnomer. The Emperor was deeply concerned with the loss of Magnus, it is supposedly said, and what it represented for his unknowable goals, declining in his personage to attend any victory celebrations such as they were. The triumph ended on a muted note, with the courts of the Imperium moving rapidly to declare the Thousand Sons as Perdicia, all records of them to be expunged, all their property seized, all treaties they were privy to, rendered defunct. Many worlds brought into compliance by the Legion, especially one's Magnus had sought to shape into visions of his ideal future, made strident objections in court to the Legion's destruction and subsequent expurgation. The representatives of these worlds made little headway, and, returning home, found that there were significant increases in Imperial auxilia presences that was the only response they were ever to receive. Michaud Arcad, the Forge world long considered bound to Prospero and its Legion, had long been on the boundaries of both Imperial and Mechanicum politics, conducting relations cordially but rarely with both. In the wake of the censure, the world ceased all communication with both empires, bringing it within what most would consider to be a fraction of actual secession. Accusations flew between the Imperium and the Mechanicum of what exactly should be done with the Recalcitrant Forge world, and it is likely only that the outbreak of the heresy prevented a full military expedition from being mounted to bring them once more into full compliance. Of the Warmaster, Horus Lupacal, little could be said about his reaction had he made any form of response. Prosperine Fair had ultimately been one organized at the behest of the Emperor himself, despite the Warmaster's later opportune intervention. Raising of the censure host and its goals were done without any consultation with Horus, but the Primarch being, supposedly, the ultimate military authority within the Imperium. Some academics have declared that Prospero and the Emperor's bullish ignoring of his son in its devastation was a contributing factor to the Warmaster's resentment and ultimate rebellion. Such accusations honestly seemed facetious to yours truly, merely for consideration with the benefit of hindsight of the events that were already in motion. Horus' fall was the cause of Magnus' actions that led to his censure. The Warmaster, made aware of this by his new allies, sought to capitalize. The mind of Lupacal, his die that they had already been cast when the Cyclops fell. Perhaps the most profound impact of the destruction of Prospero, besides those already recounted, was that the impossible had been rendered hideously possible. The starties had killed the starties. While two legions had already been struck from Imperial record, their loss is altogether another topic, and the circumstances by which they occurred are clouded with mysteries impenetrable. Prospero, however, was seemingly impossible to hide, a catatlysm in full view of those who had the power to see it. For all the detractors of Magnus claimed his was a circumstance unprecedented, what remained was the simple fact that, in later cases, the circumstance would be entirely precedentant. Anyone of the remaining 17 loyal legions could suffer the same fate, an existential shock that brought no small amount of disunity to an already fractious brotherhood. The wolves, for their part, drew the anger of many, as shatterers of this covenant of brotherhood, and unrepentant ones at that, they only succeeded in forcing themselves into further isolation. A pariah status they infuriatingly seemed to revel in, wallowing in a bleak reputation that seemed to grant them some measure of comfort as they processed their blackest of deeds. No matter that it had apparently been on the orders of the emperor himself, the wolves of Russ were now the only legion who had direct combat experience fighting the legion as a starties. The wolf king was the only primarch to have ever fought one of his brothers to the death. Some would dub him kinslayer. Had he cared, he gave no hint. The wolves, however, went one step further than merely garnering their experience. They actually codified it. Rendered from sagas and first-hand accounts, legion serfs compiled the Codex Omega, a treatise designed to be the tactical and strategic reference should the emperor decree the destruction in force of another starties legion. This was, of course, a direct and plain thread to the legion as a starties by the sixth legion, and one whose contents were shared only with Horus Lupacal and his own legion as warmaster. An error so unspeakably grave that Russ was later said to admit it was one of his greatest regrets. Almost every legion released immediate missives to the emperor, calling for the destruction of the Codex Omega, save for three. The Iron Hands, the Night Lords, and the Alpha legion, all called instead for every legion to be given a copy. Certainly, the awareness of such a work caused significant discord among the legiones. Many shored up inter-legion treaties with those they were closer to. Many worked to stockpile arms and armaments, or shifted around garrison forces in what could have been almost nervous agitation were they not a starties. The victor in this, as with almost all things concerning the Prosperine Incident, was Horus Lupacal. The legions distrustful of each other, the executioners of the emperor maimed and isolated, an unpredictable sorcerer king betrayed, wounded, and cast into oblivion, seeds of doubt in the emperor's motives sewn into the galaxy, all of this played into the war master's hands. A Prospero meant to stand as a noble upholding of the law of the Imperium, it instead was now forever to be remembered as a triumph of the traitor Horus, his first act, his first victory, even before blood had been spilled on the soils of Istvan. But finally, of the fate of Magnus the Red, and his thousand sons, all at the time believed him either to be dead, or in a self-imposed exile of sorts. As his body was never recovered, nor any trace of his death identified, this was all that could be surmised. That was of course until the Siege of Terra, when his sundering of the outer walls and his gambit within the imperial dungeon played out in all its dramatic tragedy. Magnus had survived Prospero, and yet persists to this day, even now, in corrupted damnation. How he accomplished such a feat is known only thanks to later, darker revelations about the fifteenth son's fall. His final sorcery on his homeworld was a wholesale transportation of himself, his library, and all of the surviving thousand sons, Spiregard and Prosperine civilians in the Pyramid of Photep to another planet entirely, Sorterius, the so-called planet of the Sorcerers, a damned world located deep in the festering reaches of the Ocularis Teriblus, the Eye of Terror. Had such an act been possible for Magnus himself, it would have represented a feat of psychic mastery that surpassed anything any human, baseline, Astartes, Primarch, or even the Emperor himself, had ever accomplished, or could ever have accomplished. Divisio Telepathica Investigations, commissioned in the aftermath of the Tatlism in secret, projected that, even if Magnus had sacrificed to some total of every Psyker at his beck and call, the resulting psychometric energy would only have been sufficient to transport a handful of individuals, not thousands. Early studies into this were curtailed by post-scouring imperial suppression. No one was apparently concerned with how Magnus had survived, and it is only thanks to inquisitive minds of later millennia that one has any body of scholarship upon which to build. Those long thousands of years taught humanity the pain of the primordial annihilator, the so-called gods of chaos, those eldritch intelligences that dwell in the deepest reaches of the Immaterium. Many now believe that, as Magnus could not have accomplished his feat alone, at the moment of his death he opened his hearts to the presence of a force altogether beyond. That in that darkest of moments, he embraced damnation that he might save his sons, and himself from certain death. Should this indeed be the case? That power responded in kind, spiriting the Primarch and his Legion away, to remain until this day under its thrall. Certainly the Thousand Sons have over ten thousand years been under the many, many eyes of the Changer of the Ways, as Magnus himself has, recently renewed in aspect and apparently vigour as he is in this darkest of millennia. The boons of such a patron would go long ways to explaining how, a mere ten years later, three thousand Thousand Son survivors became the approximately ten thousand accounted for upon Terra during the siege, although one author posits an altogether different theoretical. According to the theory of the first of the fifteenth, the power offered by the shifting many at the moment was one whose price was unforeseen. Magnus may have desired himself and his son saved, but the Changer did so by means rather different. It selected one amongst his Legion, saving this individual, consuming all others, including maybe even Magnus, as fuel for this act. The Thousand Sons thus seen upon Terra, and laterally throughout the millennia, are merely duplicates, pale copies of those devoured by the shifting many in the final moments of Prospero, aether stuff becoming part of its great games to be played out for unknown abominably Machiavellian ends. There is of course but one who could possibly have been saved, and given all this individual has wrought over the years since, one cannot help but consider that this potentially insane-sounding theory may hold some merit. That individual, of course, is Azek, Ariman. Maybe I consider this fancy only because the reality is so horrifying, that one of the greater intelligences intervened on the express wish of so far fallen a son of the Emperor himself. Magnus was a shining beacon of progress in a universe that so despised a concept. Consumed by his ego, consumed by his follies, consumed by his arrogance, the price he paid would see the soul his father had forged for him consigned to a damnation eternal, and us, our humanity, alongside him. This van was the birth of the heresy, yes, but upon Prospero, it can truly said to have been begun, Emperor preserve us all that we have lived to see its aftermath. Mave imperator, Gloria in excelsis terra. This video and this channel were made possible thanks to the very kind donations and support from my Patreon subscribers. If you'd like to help support the channel, head on over to patreon.com. If you'd like to receive more updates about the channel and any future videos, you can contact me or follow me on Twitter at oculusimperia. Otherwise, please like, subscribe, comment, let me know your feedback, and as ever, thank you very much for watching.