Am I? You are! That's a surprise. What a nice surprise for Christmas! Is he on the nice list? I think he might be on the naughty list. Yeah, I agree. I swear, everywhere I go I have to unknown for something. So we had the luxury of going to Winterfest at Canada's Wonderland on its opening night and boy did it not disappoint. So in this video I'm going to give a complete overview of Winterfest at Canada's Wonderland and give you my recommendations to have the best visit possible and to describe everything you can do at Winterfest because there is a lot. Winterfest is honestly my new favorite time of year at Canada's Wonderland and I know a lot of enthusiasts are going to be triggered by that but I honestly just loved it. Honestly, Canada's Wonderland spent a fortune on this event and you can tell. It literally shows through everything they did. Everything is so beautiful. The actors are amazing. Everything about Winterfest is absolutely fantastic. The customized soundtracks, the customized entertainment is just pure bliss. It's amazing. I loved every minute of it, the songs, the singing, the entertainment, the shows. Literally letters to Santa. I'm a 20-something year old person and the letters to Santa was just so amazing. And Santa's workshop, so pictures with Santa are absolutely fantastic. The whole thing is amazing. But to start, the event either starts on Fridays at 5pm or at 3pm on Saturdays and Sundays and my honest advice to you is get there early. So arrive 30 minutes before then and go right to the skating rink if you want to get skating done because the line for skating gets big real quick. So if you want to do skating, do it right away. Right before the lighting ceremony and you will miss the light ceremony if you do the skating right away. So it's what you prefer. Do you prefer the light ceremony or skating? So I would do either that or you could do the light ceremony and then quickly run over to the skating and I think that you'll still be able to get on. Or you can just book your time slot online. So if you go to Canada's Wonderland.com and pay $10 you can book and confirm your time slot before you arrive. And honestly, it's worth it. They have these really, really, really adorable little things that for kids or anyone who doesn't know how to skate perfectly that you can hold on to. They're like little reindeer and seals. It's just absolutely cute. Other than that, the lighting ceremony is absolutely gorgeous. They light up the mountain with these lights that look like water flow. And then they the lights also project snowflakes and stuff to match the music and then international street with the lights is absolutely stunning. The 250 foot tall trees as well.  Everything's just beautiful. The merch stores are beautiful. The gingerbread stores, the treats, the desserts. It's just so fantastic. So outside of the lighting ceremony and the ice skating rink and the mountain being decked out. That alone is absolutely gorgeous. But you make a right or you go straight into Med Fair and the gates into Med Fair are absolutely amazing. The entertainment option inside the castle I heard. I didn't get to see it yesterday due to a technical difficulty. But I've heard it's absolutely amazing. I'm going today to check it out. So you got to check out the show in the castle. The shows have time slots on the park map or the little brochure at front gate or inside of where the show takes place. They have that information as well. But all the shows are worth it. The dancers and singers are absolutely amazing. I was honestly like this is Canada's Wonderland's first year and you know it's a theme park. So you don't expect Disney level entertainment. I'm promising you that Cedar Fair and Canada's Wonderland knocked it out of the park. The shows, the singers and the entertainment are very Disney level. I was absolutely in love with all the shows that I saw. The soundtracks, the singing, the voices, the acting. It's all amazing. You got to go. It's definitely worth it. And to let you guys know, Wonderland dropped the price from $35 before opening to $21.99 online. So if you don't have a gold pass, it's $21.99 online, which is a really good deal. Or you can buy a 2020 gold pass to Canada's Wonderland and it gets you into Winterfest this year, 2019. And all of next year, Spring, Summer, Fall and Winterfest at Canada's Wonderland in 2020 as well. So definitely worth the price. $101 for the gold pass is greatly worth it and add parking to that. Outside of that, you have cookie decorating. So for $20, you get four large cookies and you can decorate it. So a great price for families and the cookies are very large. And it's just a really fun family activity to decorate cookies. A lot of people are recommending it. We didn't quite get to do it that night. We're going to do it tonight. It looks absolutely amazing. And then the rides are open. So you have the Swinging Ship Rage. You have Nightmares, the Spinning Ride. Really awesome to ride rides in the cold. And just the fact that they have those two rides already puts them ahead of any other Winterfestival in Toronto. But that's not just it. You get bumper cars and clockworks on top of that. And then you get most of the kids' areas. The Planet Snoopy and the Kids Rides are open in Planet Snoopy. So that's awesome. And the event's just amazing. The lights. So KDK Lane in the Planet Snoopy Bridge into Planet Snoopy is absolutely amazing. You got to check it out. It's so cute. Everything's so cute. And they have live actors throughout the park that are just absolutely into their roles. And it's just so awesome. The elves walking around the park. We're absolutely amazing. The Prince and Princess of Winterfest. I don't know all their names off my heart. So correct me if I'm wrong. We're getting used to talking to them and getting their story and their name and all that. They're just amazing. Everyone's so awesome. All the employees were so friendly. It's just such a magical time of year at Canada's Wonderland. If you don't have the meal plan, the best food in the park is definitely at Marketplace. So Marketplace is in Med Fair across from the castle. They have a Christmas dinner stuffing turkey, breast or leg, whatever you prefer. Mashed potatoes and gravy and fresh vegetables, steamed vegetables. And it was amazing. It was my favorite food I've ever gotten at Canada's Wonderland. Definitely going to be getting that. And they have dessert. Amazing flavorful desserts for $3. $3 for dessert. Absolutely amazing. Like, and it was to die for. I got that gingerbread cheesecake that they were advertising. Loved it. Absolutely amazing. You got to try it. They have pumpkin pie that I'm going to try today as well. They have cheesecake in the market in the market behind Dragonfire. Dipped cheesecake. So you get like strawberry, candy cane, cheesecake dipped or chocolate. I heard it's really good. I didn't get to try it yesterday. I definitely want to. But yeah. And then for $12.99, you can get unlimited hot chocolates the day that you visit. And then $2 refills on any other day if you come back to Winterfest. That's worth it. We got those as well.  But I'm trying to think if I missed anything, there's so much to do. Hicks with St. Nick, as I said earlier, like such a beautiful setting on the inside. So Santa Claus went over the top with his pictures with him. And it's just beautiful. I will give you some advice. You're allowed to take your own photos. The pricing on the Santa Claus photos is a little steep. It's the only thing in the park that I'm going to tell you is overpriced. So that's really good for a theme park. Everyone knows that everything's usually overpriced. I'm telling you, everything at Wonderland is not overpriced. Nothing's overpriced except for your pictures with Santa. So it's $50 for two pictures with Santa Claus or $60 for the kit is what I think they're calling it. And you get the plastic holding for the pictures. And it is really nice. My sister got it, but $60 is a little pricey for pictures with Santa Claus. So we might see an adjustment on that hopefully. But right now that is the price. But you are allowed to take your own photos and it's free. Again, letters to Santa is free as well. And you get a response from Santa Claus if you put a return address on it. So Santa Claus will respond to your letters if you put your return address on your letter to Santa. That was free and worth it. Ice skating from what I understand is $10. But I'm hearing it's free if you don't book. But again, not booking will most likely lead you to not getting on the ice. Again, you just got to go check out this event. It's absolutely amazing. Wonderland really hit it out of the park. We were not expecting this level. We knew it was going to be amazing. We knew it was going to be awesome. We've seen other parks do it in the Cedar Fair chain, but Wonderland went over the top. They have their own soundtracks, own shows compared to the other Cedar Fair parks. They have awesome live elves from the North Pole, which are amazing. And just Santa Claus and everything about Winterfest is absolutely amazing. It's an Instagram worthy event.  It's definitely one of those events that you got to check out. Anyways, hopefully I didn't miss anything. The food is amazing. Again, the events are amazing. Sorry, not the events. The shows and entertainment and the little arts and crafts, cookie decorating. Pix with St. Nick, Letters to Santa. All that is absolutely amazing. So definitely go check it out. It's an event well worth it. So book your tickets online at Canada's Wonderland.com for $21.99. Or get your gold pass for $20.20 and get in this year and next year. And arrive early. Book that skating right away. Book it online if you can't go right away. Check out the lighting ceremony and watch all the shows. And walk around the park and ride the rides. It's absolutely amazing. You can eat at Marketplace in Med Fair for great food. Nonetheless, thank you for watching this video. Hopefully you go check out Winterfest and have an amazing time. Don't forget to hit that like button. Subscribe if you haven't and share this video for others to learn about Winterfest. Have a great holiday season, guys. Thanks so much for watching. Bye.


How's it going guys and welcome back to another J-Char review Today we're going to be looking at these Dragon Ball super chocolates that I got from Tokyo central If we zoom in on the packaging real quick. This is kind of why it Caught my eyes because the popping colors on the package. It's kind of look like crayola crowns to me though I'm kind of Wondering their design choice, but I'm hoping that chocolate is going to be really good as you can see we have Ultra instinct Goku here on the front and then super saiyan blue Vegeta Let's go ahead and turn this around if we go ahead and focus It says right here that we got eight grams of carbs and there's two servings per container We have 25 milligrams of sodium and then eight grams of sugar is pretty much equaling out the carb amount They have a little bit of a diagram of what's inside and then we have this official kind of I don't know if you can see that Let's focus in Kind of a shiny toy animation seal of approval, I guess and This is what the side looks like has all the same kind of logos Let's go ahead and zoom out and yeah, I think that this is a really nice packaging and I'm really excited to try this out. So without any further delay. Let's go ahead and open this and taste us these guys it's gonna go ahead and Put some scissors in here. There we go, and then we're just going to slide this little tray out of here and There we go, let's go ahead and bring this in and focus in on it. So right here. We have piccolo Goku we have two different hearts kind of reminds me of Valentine's Day Then we have Vegeta and Gohan So we're gonna go ahead and try the piccolo one and see what it's about I'm not sure if these are different flavors or not or there's something different in them But we're gonna go ahead and try it out. There we go. Oh They're flat, you know for some reason Let's focus in on it For some reason I thought that these guys were gonna be like circular like a crown like on both sides But for some reason they are flat. I Don't know. Maybe it's just because I thought it looked like a crown Says dragon ball super on the side The art wraps around the back a little bit And has a nice depiction of piccolo looks like he's gonna be using his What was it cannon? Attack or something like that Let's go ahead and open this up special beam cannon. That's what it was. There we go looks to be a milk chocolate Let's go ahead and try it out Now I would say that this is more on the lower quality end But I'd still say that it's better tasting than like a standard Hershey's bar that makes any sense Let's go ahead and open up the Goku one Let's focus in on it. I like the depiction of Ultra instinct Goku Maybe an unpopular opinion, but I feel like maybe when they introduced ultra instinct like if there's gonna be I think there's a Continuation that they're gonna be doing I feel like they should introduce this at the end because like Spoilers if you haven't you know seen it, but this is pretty OP And I'm thinking that maybe they should have saved like his super OP form for like later because like How can you really ascend to be onto that? I guess you could really say when he hits Super Saiyan 3 What could you do after that too? But looks as though we just got more milk chocolate in here So we're not gonna go ahead and try that because it's gonna be the same thing Gonna grab the heart real quick and bring it into focus So we have the heart right here I'm assuming it's the same chocolate, but we're gonna undo it just to see Looks as though it is the same chocolate and then I'm assuming these guys are too But I just want to kind of take a look at the packaging on these guys real quick Versus actually opening them up because I'll save them for later So has a nice depiction right here of Vegeta, which is interesting because you know you'll look at this and you see Vegeta But like if you look at the old Dragon Ball Z art they were like even The farthest back at the beginning of Dragon Ball Z and then mid, you know boo saga or you know the self saga I mean, it's just the difference in like the way he's drawn is so dramatic Some people don't like the way that he's drawn in super, but I don't mind Then we got Gohan right there And Gohan's alright not my favorite character, but not my least favorite I heard that originally they were thinking about trying to make Gohan the main character and kind of like snuffing out Goku But fans didn't like that and neither did The creator as well now that just might be an article I read But that's why Goku came back and why Gohan was so prominent in the boo saga And then he kind of ended up not being at least that's what I think But yeah a little bit of nerdy Dragon Ball Super slash Dragon Ball Z Information for you guys, but yeah, what do you guys think is this something that you could see yourself buying for yourself or Maybe for a friend or maybe even for the holidays. Let me know in the comments below a Huge shout out to my patreons. Thank you guys so much for your support You guys are awesome. If you enjoyed this video, don't forget to comment rate and subscribe and as always I'll see you in the next video


I bring you all the very warm felicitations of His Excellency President Mohamad-e-Buhari on this occasion of the Interdenominational Service to mark the 62nd Independence Anniversary of our Republic. Let me also congratulate His Eminence, Dr. Daniel C. O'Call, the new President of the Christian Association of Nigeria, and all the new members of the Executive of the Christian Association of Nigeria. I pray that your tenure will bring blessings, light, and encouragement to our nation in Jesus' name. In a few days, we will celebrate the 62nd Birthday of Nigeria, but Nigeria is not a natural person, it is made up of people, it is made up of men and women and children who are Nigerians. So when we say that we celebrate the birthday of Nigeria, we are in fact celebrating the birthdays of the Nigerian people wherever they may be in this great and vast nation. So every prayer and every blessing that we pronounce today on Nigeria, we also pronounce on every Nigeria and all of our friends. So this evening, I will pray for Nigeria and the Nigerian people. My favorite prayer for people on their birthdays is found in Deuteronomy 33-25, the second half of Deuteronomy 33 verse 25, as your days so shall your strength be. As your days so shall your strength be. What does this prayer mean? As your days so shall your strength be. It means that the older you become, the stronger you will be in various ways. The older you become, the stronger you will be. Your strength will increase as you grow older. So the first way in which your strength will increase is that you will become physically stronger and healthier as you grow older in Jesus' name. The Bible says in Deuteronomy 34 verse 7, Deuteronomy 34 verse 7, it says that Moses was 120 years old when he died and his eyes were not dim nor his natural vigor diminished. For the average person, as we grow older, we become slower and less fruitful and even barrel. But the word of God to Nigeria today is that it shall not be so with you. Even as you grow in age, you will be more fruitful. You will not be weaker with age. And for every Nigerian, you will be more fruitful as you grow in age and you will be stronger day by day in Jesus' name. The word of God says in Psalm 92 verse 13 to 14, Psalm 92 verse 13 to 14, it says those who are planted in the house of the Lord shall flourish in the courts of our God. They shall still bear fruit even in old age. They shall be fresh and flourishing and that shall be so for you and all who you hold dear in the mighty name of the Lord Jesus. Another implication of the blessing that as your days so shall your strength be is that every day God's promises will be renewed in your life. Every day God's promises will be renewed in your life. God said to Abraham in Genesis 12 verse 2 to 3, Genesis 12 verse 2 to 3, he said, I will make you a great nation.  Let me repeat those same blessings for Nigeria and for you who are here and for every Nigeria because God added in that promise that in Abraham all the nations of the earth will be blessed.  Yet another implication of the blessing as your days so shall your strength be is that every day, every month, every year you will be greater, you will be better, you will be happier, you will be more prosperous, more joyful than the previous one and concerning this nation the word of God says in Haggai 2 verse 9, Haggai 2 verse 9, it says the glory of this latter temple shall be greater than the former, says the Lord of hosts and in this place I will give peace, in this nation I will give peace, says the Lord of hosts. The future of Nigeria will be far more glorious, more peaceful than her past and so shall be for you too, every year you will be happier, every year will be more glorious, more prosperous and more peaceful in Jesus name. As your days so shall your strength be, another implication of that blessing is that your strength physically, mentally and spiritually and even financially will be sufficient and adequate for every new season, every new situation and every new challenge. You will have more than you need for every new season in your life in Jesus name. Brother and we stand at the gates of a new nation and we see its lights shining bright. The nation of God's promises, a nation of opportunities, of equity and justice, a secure and prosperous nation, a nation of laws and righteousness. Even if what we see today seems bleak and dark, we are confident that God who owns the heaven and the earth will fulfill his promises concerning this nation and indeed he says in Joshua 21 verse 45, Joshua 21 verse 45, he says not a word failed of any good thing which the Lord had spoken to the house of Israel all came to pass and we pronounce concerning this nation that not a word will fail regarding any good thing which the Lord has spoken to Nigeria all will come to pass in Jesus name. Finally to every citizen of this nation and every family that is represented here would declare that in the name of Jesus your best days are yet to come. Every promise that God has made to you will come to pass in Jesus mighty name. Happy 62nd anniversary.


Okay, this apparently starts now, I thought it started at 35, but I'll go ahead and get started. Welcome, everyone. This is Monsters, Ghosts, and Bugs. So quick poll of the room. Who here has built their own kernel before? Who here has crashed their own kernel before? Okay. Excellent. Okay. For a slightly more getting us into the mood of this talk, think of a system you have, any system, maybe your laptop, maybe a machine, and ask yourself what kernel is running on your system. Do you know what kernel is running on your system? And then ask yourself, if you know, why are you running that kernel? Did you make a deliberate choice to run that kernel? Or because perhaps you couldn't choose what kernel you are? Or did you just kind of use it because it came with your system? And I titled this talk Monsters, Ghosts, and Bugs because, okay, it was pretty catchy. But the idea behind this talk is to get you thinking about how different kernels are maintained and what impact that can have for you and what drives how these kernels are maintained. Kernels are always going to have bugs, obviously, like all software. And ultimately, you already need to have a plan about how to deal those as a consumer of kernels. Sometimes you're going to get spooky ghosts like Spectre and Meltdown. And you'll need to deal with those in a different way. And then I'm also going to spend some time talking about monster kernels that sometimes get a bad reputation, but do also have some good reasons for existing. The first thing I'm going to talk about is how the upstream kernel community releases a kernel, simply because it turns out that how the upstream kernel releases a kernel has an impact on how distributions may choose to release their own kernel. You've probably seen this in other talks, if you've seen Greg talk about it before. But this is my take on the entire thing. If you've ever seen a report from the Linux foundation or LWM, the usual line is, wow, there are so many people working on the kernel every version. And this is true. There are lots of new contributors and new patches each time. And the kernel is always released on a fairly regular schedule. This is the extent of my graphic skills. This is a rough diagram representing the kernel cycle that's happening right now. All the way in the left, you have the 5.2 kernel, which came out early July. And all the way in the right is 5.3. And each of these blocks represents a week of time. We're somewhere around RC5 right about now. And if all goes according to plan, 5.3 will be released after RC7, somewhere around the middle of September. How do we know this is a schedule? Mostly because this is what has happened to previous kernels, and there's no reason to believe this is going to change. Probably Linus Torvald still sets the release schedule. And this is the schedule he's chosen to pick. And the schedule is so predictable, you can probably guess when the next kernels are going to be released. This is a website that someone has put together that is a little bit tongue-in-cheek with the name. But it's really handy because it shows you when the past kernels release and also gives an estimate about when future kernels are going to be released. I always say rough idea when using schedule like this because things can change. The diagram I gave only had seven release candidates. These days we also seem to be getting a lot of more kernels that have an eighth release candidate. And then around the time Spectre and Meltdown happened, we ended up with a ninth release candidate. If you're trying to plan kernel releases down to the day, you're probably going to have a bad time. The kernel community isn't interested in guaranteeing releases on a particular date, but the releases do happen on a remarkably cyclic basis. So the first part of the kernel release cycle is the merge window. After one kernel is released, the merge window for the next kernel opens up. As the name implies, this is when everything is getting git merged together. This time period usually lasts about two weeks. This is a busy time for kernel maintainers. Kernel maintainers are going to be doing preparation of a git tree to be pulled by Linus and maybe also accepting pull requests themselves. Many maintainers don't actually submit to Linus directly. Their pull request will end up in his tree indirectly through someone else. But all the trees will eventually make it to Linus's branch even if indirectly. But this is an important point for two reasons. One that a kernel patch is not considered fully accepted until it's actually in Linus's tree. And two that all kernel releases are also happening off of Linus's master branch. Using this merge window, a lot of maintainers will not actually be reviewing patches. If you try and email Greg K.H. to patch this time, for example, he'll have an auto respond that says, please contact me after the merge window, simply because it's too much volume otherwise. Before a feature lands in Linus's tree, it's usually expected that developers have done some degree of testing, sometimes more than others. But once it gets pulled into the Linus's tree, it's going to get testing from a much wider audience simply because it's got a whole new set of hardware and new people to test on. And you're going to find that the merge window is where most of the bugs are going to occur or introduce simply because this is where most of the commits are coming in. The kernel is still mostly usable at this point. And it's still very important to continue to be testing and using it this time simply to continue to try and find and possibly fix bugs. Eventually all good things come to an end. And after two weeks, the merge window closes and Linus releases RC1 off of his master branch. The good news is at this point, things usually start slowing down a lot. New features are going to stop coming in except when maybe a feature does try and come in. Sometimes features can come in after RC1, but in general, the bigger the feature, the more unhappy Linus is going to be and the more likely is to reject a pull request. There's a schedule to the kernel and the schedule is that new features need to come in during the merge window. But in general, by this time, most of the new features are in because it's time to continue testing. I mentioned that bugs are often introduced and perhaps fixed during the merge window. These may be the simpler bugs because other bugs may have gone unsolved or just unnoticed simply because they hadn't gotten enough testing. And this is the point of the RC cycle, is to try and find and fix bugs. If you see patches that are being sent now, they are oftentimes patches for the current kernel. But the RC, especially later in the RC cycle, this is all for the time to start looking towards the next kernel. Maintainers will start to do more patch review after the merge window. But for patches that are sent now, unless they're fixing new or major regressions, patches will be queued up for the next kernel. So for example, a patch that's sent now will be queued up for 5.4. I've mentioned several times that Linus will often reject pull requests and maintainers will reject patches for the current window if you try and send them at the wrong time. And this is because trying to get a maintainer to take patches off cycle doesn't end well for anyone. Simply because if you try and get a maintainer to take something that's not ready, it's going to introduce possible stability regressions across the entire kernel. Greg gave a talk a few years ago called, I don't want your code, kind of a harsh tame. But he tells a good story about a time that he tried to take a patch before it was ready and the consequences of the calls. So there's a good reason for maintainers being pretty strict about when they take patches. Eventually a week passes and another RC happens. The procedure for each RC is the same for each week. But the expectation is that the number of patches going into each RC should be getting smaller since only bug fixes should be coming in. Sometimes it goes faster than others. Sometimes RCs get bigger, which nobody likes. Sometimes the time passes. And eventually Linus decides the kernel is stable enough and declares a release. And everyone is super excited once again. Okay, so a brand new kernel has come out. This means it's immediately time to go and start putting it on all your systems, right? Maybe not. Just because a major kernel has been released doesn't mean it's bug free. After a kernel has been released, it's going to get bug fixes for a period of time, typically until shortly after the next kernel version is released. So 5.3 is going to be released in the middle of September. And it's going to get stable updates 5.3.1, 5.3.2, 5.3.3. But they won't continue indefinitely. They'll eventually stop about the time 5.4 is released. I mentioned stable updates as receiving bug fixes. When I'm using the phrase stable update, I'm using a very particular term here that's defined for the kernel. The bug fixes that are going to stable updates are a very specific set of bug fixes. They are typically small self-contained fixes that are less than 100 lines. The issues that are fixed must be really issues that bother someone, no theoretical race conditions. And the fix must be in Linux's tree. All of these requirements are designed to hopefully improve the stability of the stable fixes. Because not all the fixes that are proposed out there are actually appropriate for stable, the way patches end up getting into stable is that the patches tag with cc stable in the commit message. Sometimes the submitter will add this, sometimes the maintainer will add this. But if a patch doesn't get added at commit time, it's okay. If you find that a patch is missing, you can email commit hash to the stable mailing list and it will be picked up. And when I say you here, I mean anyone, any kernel contributor can do this. If you found a patch and perhaps done a bisect and you notice that it's in Linux's tree but not in stables, you can email the stable maintainers and they'll pick it up. And then this is a page that gives a short description of the entire stable process if you want to know the entire details. So this is a screenshot I took of kernel.org. If you notice, there are multiple versions here that are marked long-term stable or LTS. These are stable versions that some kernel developer often Greg has decided to maintain for a period of time. Greg usually picks one kernel version a year to be the LTS version. Sometimes he announces it beforehand. Sometimes he doesn't want to because he's found the path that if he announces a particular version is going to be an LTS version, people will try and get patches in before they're actually ready and again causes more stability problems. But usually without fail, once a year you'll get a new LTS. And I actually had to update this slide right as I was working on these because Greg announced that 5.4 is going to be the next LTS version. So as you can see here, Greg maintains a lot of the stable versions. Ben Hutchings is a maintainer for Debian, great person, and he also maintains the 3.16 stable versions. But all these stable trees are not actually created equal. The way these are intended to be used is that you take the most recent LTS, use it for one year, and then update to the next unless you have other reasons. Older LTS releases are typically designed for perhaps hardware enablement or other very specific use cases where you can't update for logistical reasons. And in general what you're going to find is that the older LTS releases are getting bug fixes, but they're also going to trail off after a point so they're going to be getting just a core set of bug fixes. Okay, so that's the story of upstream and stables, but obviously people need to consume these trees in some form. And the question is, is that then your distribution, what kernel is your distribution actually running? I did some look online to see exactly what various distributions were running. This is where you can find information about the Ubuntu kernels. And it's kind of hard to capture in one slide, but from the very detailed schedule they have, they're using a mixture of LTS kernels and their own kernel versions. And this is a screenshot of Arch, and if you look here is that they're running things that are fairly close to the stable mainline kernels, updating on a regular cadence with the monthly stuff. Okay, and then when I say distributions, it's also important to think of distributions as things like Android, which also runs a kernel. And this is a screenshot from Wikipedia showing the kernel versions that were used all across the time with some of these slightly older versions up there. And I'll talk more about Android in a bit and their journey in figuring out the best way to maintain a kernel. And so naturally the question is, okay, we have a bunch of distributions, they're all running things differently. Why are they running these kernels the way they are? And it kind of ends up running down to a trade-off of stability versus features. If you're going to run in a single LTS version for the lifespan of the release, it's probably going to be fairly stable, but you aren't going to see a whole lot of new work since the only commits that are going into stable updates are supposed to be bug fixes, not new features. Okay. One of my full-time jobs is Fedora kernel maintainers. So I'm going to talk about how the Fedora kernel is maintained, just as an example about why a distribution would choose to run things in a particular way. And the Fedora kernel model is to rebase to new kernels as soon as they're released, similar to the arch model, so you get a release schedule that looks like that. And this ends up being the easiest for the Fedora workflow and also well-aligned, but the Fedora philosophy to be a leading edge distribution. With each new kernel version, you're going to be getting a lot of new things, new features. Okay. Everyone's, I need to drop some buzzwords here because they're mandatory containers. Each new kernel version, you're going to be getting new extensions to containers to help them run more securely and hopefully be better running. Another favorite buzzword, EBPF. EBPF is a feature that's been extended over the years to be able to do new tracing. Each kernel version, there's more ways to trace. You're going to get new hardware with each release. I can go on and on about the different things, but the point is that you're really getting the latest with each new kernel version. But this also comes at a cost. All these new features I mentioned sometimes don't work or even worse things that used to work stop working. A real life story from last December, it turns out there was a major regression in the block layer that was people reporting it as EXT-4 file system correction. And there was a lot of back and forth in terms of trying to figure out what the bug was. And eventually, the maintainer did eventually find the commit that fixed the problem. But of course, this was very frustrating for the users who were trying to narrow down the problem and figure out when their file systems were going to stop getting corrupted. Most issues you see aren't going to be that dramatic, but this is kind of the point about updating kernels, is that how much risk do you want to put on the users in terms of giving them no features but perhaps have them potentially have an issue. For something project like Fedora, our users expect that they may occasionally see a bug, hopefully not file system corruption, but some bugs and they'll have to work with us to report bugs to get them fixed. So again, this means that if you choose to run an LTS kernel and not update to a full new version, you're not going to see new graphics drivers or container features, but hopefully you're not going to see file system corruption either. And again, if your goal is deployment on a known set of hardware and you're not really touching it a whole lot, this is probably what you need. I spent some time talking about the upstream LTS kernels, but it turns out there are a lot of distributions out there that aren't going to use the LTS kernels and tend to do something that kind of looks like an LTS kernel but follows a different schedule. Hey, I am obligated to talk about my employer here, Red Hat. A lot of people sometimes like to talk about this is how Red Hat maintains the enterprise kernels for the Red Hat Enterprise Linux. And they've kind of given them this nickname of Franken kernels and because especially from the upstream community perspective, they really do look pretty scary. These kernels tend to pick up individual patches and backport specific features rather than, say, taking stable updates. And the reason they get a bad rep and get these bad reputations is because from the upstream perspective, you don't know exactly what's in these. The kernel version may be, say, 4.4, but you have no idea what's in them. There may be some bug fixes but not others. Yeah. Sometime last year, Red Hat announced that EBPF was going to be backported into its kernel which brought a lot of chuckles as an example of a feature being brought into a very older kernel. And another big objection to these kernels is the argument is that there's a security risk. And the argument goes by not taking all known fixes, you potentially have a security hole since all issues may be security issues. And I can't really dispute that if you don't have a particular patch or bug, you have an issue. But I'm flipping this around to get the suggestion I got from some people to not call these Franken kernels but well-curated kernels. The point here is that these kernels are maintained because there are enough people looking at them that they can usually figure out if something should or shouldn't be included and if it turns out maybe something was missed, they can add it fairly quickly. And this philosophy is that it's better to only take fixes that are known from a known specific set of commits versus taking everything simply because that's one possible way to reduce risk. It also turns out these kernels may offer other guarantees for say binary compatibility and taking stable updates that have other commits that haven't been validated can help possibly make that harder. So when you run one of these enterprise kernels, you should know exactly what you're getting because the people have selected exactly what goes into them. And part of the idea of only taking certain fixes is that sometimes regressions slip into the staple trees. There's a famous quote out there related to Linus' law which is that, given enough eyes, all bugs are shallow. And this is what the kernel community has focused on for many years. The focus has always been on code review to try and find these bugs before they get committed. But I think the stable trees are a good example of where we've seen the limits of this process. Patches for the stable trees get CC'd to the mailing list, as I explained before. And the patch is presumed to be accepted unless someone objects. And then one of the issues we've seen is that developers don't notice that they're supposed to, that they don't want the patch included, or that their dependencies have been missing and that there have been problems in the past with this. Obviously, nobody wants regressions. And I don't want anyone to think that this doesn't mean the stable trees aren't usable. They are a fantastic resource and everyone does a great job of working on them. But it goes back to figuring out how exactly you're maintaining these, and the stable community has had to figure out what are good ways to be able to maintain these trees to get the fixes while also reducing regressions. And the stable trees are, I'm not going to say a newer model, but if we go back to our big scary monster of an enterprise kernel, the people working on that have just decided that for their particular purposes, it's easier just to pick up individual fixes than to try and say, guess what's in the stable tree. Excuse me. And this does come down to needs. The people trying to ship one of these kernels have needs that don't quite match with the upstream LTS kernel, so they do their own thing. I want to talk about embedded and Android as a lesson learned in dealing with kernels and shipping features. The embedded Linux had kind of a reputation for many years of shipping very out of date kernels with patches that had never been reviewed upstream. And the reasons they did this weren't always because they say we're making the deliberate choice about this is how we want to deliver, but maybe they didn't see a better way to do this. And part of this had to do with what the embedded system was trying to do for shipping a product. I just presented the timeline about how the kernel is released and when patches are going to be sent. If you think about it from the other perspective, this means that if you want to get things included, you need to be thinking backwards. So let's say you want to release a product on date X. If you go back to the handy dandy chart I showed about when kernels are going to be released, that means something on date X is probably going to have a kernel Y, which means you need to be thinking about submitting it at kernel Y minus one or Y minus two. Kernel development takes time. Again, I talked about how maintainers don't want to take things off cycle because it turns out it will potentially cause regressions. But if you're a company who needs to ship a product, you can't always work with this. You can't really go and say, sorry, we're not meeting our holiday deadline this year because somebody didn't like our changes to the DNA layer. So ultimately this means that if you're a company who needs to ship something, you're just going to put whatever you have and ship it out. And that was what a lot of the embedded world looked like for many years, some out of tree patches on top of a very old kernel. Obviously in many respects it was successful because products were getting out, but it wasn't the best thing to work with as an engineer or as a consumer. And this is what Android did in the early days. The first versions of Android shipped a bunch of features which had never really been reviewed upstream. Google wakelock controversy if you ever want to see a very long thread about maintainers trying to figure out what they want to do with some of these Android features. And what Android chose to do in terms of shipping a lot of AdFu code was success, but it wasn't very sustainable from a kernel maintenance point of view. But fast forward to today and things look better for Android. Even to that a high level Android is still doing the same thing of shipping a kernel out of tree patches. But it turns out this is the secret of all distributions. Most distributions are maybe shipping a few out of tree patches, minor tweaks to be able to do what they want, even ones that are tracking LTS. But what's changed for the Android community is that they are much better at engaging with the upstream community. They think about their features and they try and propose them. Not every feature they want is necessarily accepted, but they continue to work with the communities and try and find solutions. I mentioned Android here as also a heavy consumer of the LTS trees. They've learned to use that as the basis for their trees so they can benefit from pulling the stable updates that come from upstream. And internally they're doing all their testing on the LTS trees and they're reporting that back to the upstream community so everybody is benefiting from their increased testing. And I mentioned Android as a success, but really today the embedded picture looks much better and embedded distributors have gotten better about working with the community and there are a lot of board support packages that are in fact running the mainline tree. And this is thanks to a lot of hard work and education by kernel developers explaining companies how exactly to contribute to the community. And this is really a key point to a successful kernel strategy. How are you engaging with the community? Maybe the community doesn't want your patch, but you ultimately need to figure out how to handle that. And this kind of leads to the next topic. People sometimes seem to want to run their own kernels off of kernel.org instead of running whatever the distribution provides. And this is certainly something you can do. And when I talk about this, I never wanted to discourage anyone from doing things for the sake of learning. The best way to learn about the kernel, I think, is to try something and break it. You'll get a good chance to learn about what hardware you have if you try and compile your own kernel and then say, miss something or try and apply new patches. You can learn about how things work by testing patches. If you want to try and run your own Raspberry Pi cluster on your own, go for it. But if we're thinking about projects or deployments and, say, that have real users, you really don't want to be running your own kernel. And I don't say this to try and keep myself in a job as a kernel maintainer. Being a kernel maintainer is not always the glamorous life that everyone thinks it is. It's oftentimes pretty tedious. But a big part of what kernel maintainers are doing is thinking not about just what today's kernel is, but tomorrow's kernel. Let's say you found this amazing patch set out there that improves your workload by 1,000%, but it's not going to be accepted upstream for any reason you can think of. So you decide you're going to keep running your own kernel with this patch set.  This is your periodic reminder that when you deploy your kernel, you are not done. Please make sure you are giving kernel updates. You are getting updates, especially for security fixes. So if you're running your own kernel, you are responsible for getting updates. And this is the piece of advice that is given out there. If you decide you want to maintain your own kernel, please make sure you track one of the LTS branches from kernel.org and just take those updates. I spent a lot of time talking about why the enterprise kernels may choose to not use an LTS bake and pick and choose individual patches, but this really only works because they hire enough kernel engineers who have enough experience to know exactly what they can and cannot pick. You do not want to be trying to maintain one of these kernels on your own or even as a small team. Android is an interesting case of this as well. I used to work on Android phones, and at the time, the kernels we used didn't track stable updates. This meant we were regularly hitting bugs that had been fixed upstream, and then we were scrambling to bring the patches in, usually at inconvenient times. And really, you will forever be playing catch-up if you're already running an LTS and trying to figure out what fixes you need to bring in. Upstream is doing a lot of work to try and maintain the stable trees upstream. Please take advantage of that. But even if you decide to keep using LTS like everyone recommends, there's a good chance you're still going to have to do some work to maintain your out-of-tree patch simply because you're eventually going to run into merge conflicts. And merge conflicts are why kernel maintainers will never be fully out of a job. There are certainly some tools out there to help maintain your out-of-tree patch sets, but ultimately, it's usually going to be humans who need to figure out how the code works. APIs get changed and removed, structures get added and removed, and things get moved around, and you need to know the code pretty well in order to try and do backports correctly. Another story for my Android days. I did a merge incorrectly when I was helping to work on a kernel update, and this introduced a subtle memory accounting bug that went unnoticed for months until there were fine enough reports of negative numbers of pages that I could help narrow down the problem. And if I had to go back and give myself some advice then, I really would have tried to get more people reviewing the backport I was doing to help maybe try and catch the bug. And again, the reason why a lot of these enterprise kernels actually work for doing backports is because they have enough people looking and reviewing the patches and who know the code well enough to know exactly why these problems occur. And again, I never wanted to discourage anyone from doing this work from learning because it turns out you can learn a lot from trying to do backports, but if you're thinking about kernels that are running on production systems, you really want to set yourself up for success. Then we have our favorite bugs exposed last year, Spectre and Meltdown, the ghosts from the title of this talk. I think there's been enough talk explained by people like Greg about how the disclosure of this was handled pretty terribly, and we've certainly learned since then about how later variants were handled. But we're never going to be completely done with security. And we'd like to believe everything is going to be handled perfectly next time, but I'm pessimistic here. So if you're running your own kernel and maintaining your own out-of-street patch set, what are your plans for when you wake up and read the headline about the latest zero-day or issue, you are the one responsible for applying the security fix your tree and getting it out. If you have a backport and the security fix doesn't apply to your tree, you're the one who's going to be responsible for trying to resolve that merge conflict. And how confident are you that you have actually fixed the bug and not accidentally reintroduced it? This is a real problem people have done in the past that major distributions have tried to apply security fixes, done something correctly, such that the security fix bug was still there. It's not only pretty embarrassing, it's not a good experience for anyone. So circling back again, I make it sound like if I'm trying to make it sound like distributions always get it right, they don't. That's a good example. They may give a lot of bugs. But the point here is that distributions are already making these mistakes. So try and take advantage of these mistakes before making your own. Okay. So wrapping things up here, the question of what kernel you pick ends up coming down to what's your focus. If you don't care about the newest features, it might make sense to run a kernel that just gets bugged versus fixes, say, on an LTS kernel. If you have particular stability requirements, binary requirements, maybe you want to run an enterprise kernel. Maybe you want to try and run your own kernel, but you really might want to think twice about it and have a good plan for dealing with things. But more than anything, I think I use the word think a lot, think about exactly what you want for a kernel and try and make your life easier. Okay. Thank you. I think we have a few minutes for questions here. Yes? Yes, that's a good point. The joke about fragment kernels is because they're stitched together, and that is a good metaphor about why they're why they're got together. Okay. Thank you for your questions. I'll be hanging out at the red hat booth after this, so you're welcome to come by and ask me more questions there. Thank you very much.


Interview Log, 1867-23 Interviewer, Dr. Adam Bernstein Interviewed, SCP-1867 Forward During a standard checkup interview with SCP-1867, the subject, at the request of Dr. Bernstein, was asked to elaborate on the nature of one of the items found in his collection, an ornate brass baton. The baton, while showing no avert anomalous properties, caught Dr. Bernstein's attention due to the amount of dried blood still covering it. SCP-1867 complied enthusiastically. Begin log Good afternoon, SCP-1867. Please good doctor, call me Theodore. Very well, Theodore. I would like to ask you a few questions about this, show's picture of the baton. Oh, Yuri Dresnick's command baton, haven't seen it in years, interesting story behind that one. Would you care to elaborate? Certainly, I do enjoy telling a good story, and this one is so very full of excitement. Please continue. Well, it was the year 1855, and the Russian war was raging across the Black Sea. The Tsar was trying to take control of the Bosphorus straight from the Ottomans, using some daft argument some priests had in the Holy Land as an excuse. Our brave lads, along with the froggies, were given the Russians a right thrashing, despite a few minor setbacks like that unfortunate business with the Earl of Cardigan's Light Brigade. Great man, terrible tactical sense. I remember having a heated discussion with him about Scipio-Africanica's vertical spear formation. Focus on the baton, please. Alright, it was, I believe, late July. I was visiting an acquaintance of mine in London, and we were just discussed in the preparation necessary for an expedition he was planning to the East Indies. When a knock was heard on the door, and the man-server proclaimed it was a messenger from Lord Palmerston himself, who wished to speak to me at once. I made by way of the Downing Street 10 post-haste. The Prime Minister was waiting for me in his office. Theodore, he said to me, the Empire once again requires your services. The war in the Black Sea is turning in our favor, but we need to stick one final nail on Alexander's coffin if we want the Russians out of the straits permanently. We pulled out a map and pointed at a spot, Sevastopol. We've been besieging the thrice-damned place for almost a year now. If we manage to take it from the Russians, it's only a matter of time until they surrender and accept our conditions. Does this have anything to do with the baton? I'm getting to it, I assure you. As I was saying, the Prime Minister confided in me that he was planning a joint attack with the French of Sevastopol in late August or early September, but there was a problem. The Russians were rumored to have recruited a thaumaturge of great skill, Yuri Dreschnik, and he dared not order the attack as long as Yuri was there to muck things up with his magic. He wanted me to get rid of him. Why did the Prime Minister need you to get rid of this wizard? Thaumaturge, doctor. They are not the same as wizards. He needed me because I had experienced. I led the Great Warlock hunt of Austria in 1833 and had numerous encounters with various shamans and witchdoctors throughout my travels. I was quite the authority figure in the field, if I may say so myself. Carry on. The Prime Minister needed Dreschnik gone before the attack, and he knew I was the right man for the job. As a patriot, I could not refuse, and I was scheduled to board HMS Gallant, leaving for Istanbul on the following day. The journey was uneventful, save for a minor pirate raid near the shores of Libya, which was easily repelled. I arrived at Istanbul safely, then boarded another smaller vessel for the remainder of the trip. I arrived at General McMahon's command ship on the last day of August. And I traced in McMahon with a solid gentleman, if there ever was one, even if he was French. Always good for a laugh and a quick shot of brandy. I first met him in Algeria when he commanded the foreign legion in the 1840s. The man could smoke a hookah like no other, and that's a promise. I remember sitting with him in the chic of, focus please, SCP-1867. Theodore. Right. The Thaumaturge. McMahon told me he'd received credible information that Dreschenik was hiding in the Malikov itself. This massive stone tower overlooking the port, preparing some sort of foul ritual, as Thaumaturges are bound to do. I was to assemble a team from the very finest the Allied armies had to offer, and make a raid on the tower at night, disposing of Dreschenik before he could raise some nastiness to hamper the war effort. And how did the raid go? Oh, quite splendidly. Well, mostly so. There was the small matter of our boat-sinking halfway to the port, and our sniper tripping on some slick stones and breaking his ankle, and half the team getting discovered and riddled with bullets, but other than that, everything went perfectly. We finally cornered Dreschenik in his ritual chamber after a long chase, as the man was surprisingly fast for a portly middle-aged gentleman in long robes, but he would not go down without a bite. He pulled out some strange apparatus he was hiding in his sleeve, and pointed it at Sergeant Monroe. Poor man never stood a chance. What did the device do to Sergeant Monroe? Turned his skin inside out. The screens were quite terrible, not to mention the smell. He managed to do the same to Corporal Turner before he shot the device out of his hands, along with a few fingers. He wasn't done, though. Screaming like an Indonesian howler sloth, he sprayed the blood from his severed fingers on the corpses of my fallen comrades. The two inside-out bodies jerked and came to life, attacking what little reminded of my crew. They ripped a random roux apart with superhuman strength before I took them down with my trusty machete. Now it was just me and Dreschenik, and he was all out of tricks. His grand ritual was left unfinished as I brained him with his own command baton. The battle took place a week later, and we gave those Russian ambassadors a beating they wouldn't soon forget. That's how the baton came to my possession. So the baton is just an ordinary command baton? Though it found meturgic power to it? Of course not. I burned down his ritual chamber along with all of its tools before making my escape and swimming back to safety. You'd have to be quite daft to keep a thumb at Turg's belongings. They always cursed at things. I lost a cousin to a curse like that. He was turned into an eel. Could you imagine that? Being an eel? Treadful. I would think so. End log.


Next question is from Andrew E. Burrell 21. What are the best mobility exercises for low bar squats? Oh, good low bar squats. Now, I guess the question I would have here is, is the question, because the low bar squats, the bar so low on your back, so shoulder mobility. So shoulder mobility is what I'm looking for, or we're talking about squats, and so are they asking that because the squat depth, they're lacking, and so that totally changes my direction. Well, let's look at the difference between a low bar and a high bar squat. High bar squat, you're going to be more upright. You're probably going to need more ankle mobility, right? Because your knees are going to travel forward a little bit more. Low bar squat, you're going to get more forward bend, less ankle mobility, but probably more hip, I would imagine, stability and strength. And then, of course, thoracic, right, in that upper back area, is what you typically would see with somebody that you'd have to work on. I think the biggest issue is what you guys said was the shoulder mobility, that shoulder and thoracic kind of mobility, to be able to support a bar way down on that part of your back and hold it with good chest out type of posture, because a lot of people aren't able to do that. So good exercise for that. I like the wall test that we have in zone one. Yeah, zone one in prime. I love, and I think I shared this on my story a couple of months ago, and I've just really been incorporating it in the last year, our suspension trainer W's. I love that to prime for exactly that, because literally think about where you're trying to, the actual movement of getting me, me getting under the bar for a low bar squat, this is what it looks like, right? And then we're wedging it down below. Like literally that is the W.  So I do face pulls as well. Yeah, face pulls, W's on the suspension trainer. Those, I mean, I used to do zone one. So zone one was like my go to, go to zone one, work on that intrinsically. And the reason why I think I like W, it's easier to get somebody to do a W than get them to cue the zone one. So if you don't own prime, it's harder for us to think to explain on a podcast like exactly what zone one is and how to do it to get the benefits. Where if you go YouTube or Google search what a suspension trainer W is, you could do it and emulate it and I think it'll get tremendous benefit from it. Yeah, prone cobra can kind of work. Yeah, work on that area well. And then hip mobility, right? What kind of things are good for hip mobility? You know, 90, 90 is always a great movement for that. Tube walking, lateral tube walking can help a little bit with that stability that you might need for a low bar squat. Generally speaking, I'd say people tend to run into mobility issues more with a high bar squat though. In my experience. Oh yeah. You see more issues with ankle mobility than you will with ankle. And just the high bar squats is taking me a long time to get to where I could actually do one really, really good. You have to have really good depth in order to be able to sit upright and keep that bar up really high. And if you're taller and longer, it's even harder. The longer the lever like that. So I had to low bar squat for a long time to get to hit depth because I had to let my body fold over a little bit because I didn't have the ankle mobility and shoulder mobility. Olympic lifters are probably your best example of high bar. Oh yeah, that's where you're going to see the best. They're nice and upright with that. You have to remember all the bases with wrists, elbows and shoulders you do our handcuffs for rotation. And that's just one of those that like it just places you in such a good position and really articulates each one of those joints because those are all essential in getting into that position lower on your back like you have to get everything in a nice functional position for that.


I'll put the labor unions behind you, George and his labor crowd ought to be there tomorrow morning trying to get people to read and write. I told Martin Luther King, I said, hell, I'm for voting, and we're going to get voting. That's not your problem. You're going to have a vote message in its nation that we can do. But the big thing, Dr. King, with you is a billion, 200 million for Nate Rose only.  It's the Negroes. Now, God, they can't work in a filling station, but water and radiate unless they can read and write. Because they've got to go and punch the cash register. They don't know which one to punch. And they've got to take a check. They don't know which one to cash. And they've got to take their credit card, and they can't pull the numbers. So you've got to teach them to read and write. And that's what cheap damn fellows better be working on. And if these Republicans want to be for the Negroes, I hope to do. Two-party system. I hope some Negroes vote for Republicans. But you make them go vote for education. And I think you ought to find out this group that's meeting with Ms. Green. And as Vice President of the United States, you ought to ask two of them to come to your home on Sunday afternoon. You ought to have two of them at breakfast with you on Monday morning. You ought to have two of them in your office in the afternoon and give them a card to the gallery and give them a picture of you and your wife and give them one of the president. And then tell them that this is the greatest thing, and their names are going to be built to be written and fire on every schoolhouse in the country that they've made the breakthrough.  And then the school board's got to give it to them, and that you're a Protestant. And that this is the best thing you've ever seen, because if you can't do more, no Lady Green.  I ought to have her. And as I, she's been a little younger, I might have picked her. Goodbye.


So my beautiful people, I am back with another Alder Ring video, a mage is out there, this one's for you. How's it going guys? My name's DPJ and if you do enjoy the video, leaving a like really helps out and if you like what you see and want to see more Alder Ring, be sure to subscribe. So what do this moonblade? An absolute amazing bit of kit that no doubt binds to your staff. Let's quickly read about it before I showcase it to you in action. It is absolutely amazing guys, as you can see right there, a duelist moonblade, sweeping slash followed by a cold blade projectile. Conjures a cold magic greatsword, then delivers a sweeping blow that launches a blade like projectile thrust. This sorcery can be cast repeatedly and yes it can. Now it does cast 39 focus points which is quite chunky. It requires a 32 in intelligence and that's it. That's it, just intelligence guys. So you bind your staff, so make sure you have a staff and we're going to check it out before I showcase you how you get this thing. Let me let me round all these guys up. Come on people. Come on people. Where's the guy with the horn? Where's the guy with the horn? He's normally standing here. Is that him there? There he is. Nope, he pulls out his sword. No, I forget his sword. I'm gonna pull out my horn. Come on. Is that all you got? Come on. Come on. Come for me. Come for me. Come for me. Come for me. Come on. All gather up. Let's see what this thing can do. You ready?  If you lock on one it's sent to like that. Man it takes them all out. Jesus. Oh it's beautiful. Oh it's incredible. It does some serious damage. It really does and in fact it can take out more as at the same time. Geez and I only myself guys. There's nothing really I've got on. Which helps my magic to be honest. I mean that doesn't do anything with this thing in the charge bar. Apart from my my Suruli number medallion. My armor. Nope, nothing. I mean my research glitz on stuff and it's the best in the game. It's the best in the game people. Oh yes this is absolutely incredible. So how did you get it? Well it's going to take you a mission if you haven't already completed Rani's quest line. Now Rani's quest line. You find Rani up here and Rani's rise to get here guys. You need to clear that carrier mana. Clear out Loretta.  She'll be at the top of this tower. Start a quest line. Simple as that. Now about 98% through it you'll come to this area here. You can only get to this area guys for you're doing Rani's quest line. So your first come at this grace point here. You'll come up there and you'll come up this grace point right here guys. Right here. So from here you need to come up to here. Activate this grace and go this way and you'll see it on screen now. There is a massive dragon there.   It is as simple as that. Now what we'll say is if you if you got here there's three dragons around. I'd say this area here. All they drop are the dragon hearts. They don't drop anything else. I've killed all three of them. I didn't get nothing for them. So yeah ignore them. Go for the dragon here. But in saying that I did kill all three of those dragons before I come up here and took out this dragon here.  You probably have to take out those three first or those three after. But I don't think you do that. So come here guys go to dragon and you'll get this incredible a duelist moonblade which I'm loving. I'm loving. It does consume though quite a bit of your fb points but you can count that with some talismans in the game no doubt. But there we have it guys. If you enjoyed the video leave a like really helps out. If you like what you see and want to see more I don't think be sure to subscribe and hopefully people I will see you when that next one


Okay, let's go. Let's let's get your thoughts because you guys were racking it up earlier with Tom of Midnight's Edge Chris Gore in regards to this. What's this gentleman's name Chris Stuckman? Criticize this What? What is your thoughts on on what this gentleman says because he's got a big platform? Yeah, he does and He's been at it. He's been at this game for a while from what I read Never fall. I don't know he is until this happened. I I fall I watch his reviews regularly. Okay it's just another data point in terms of Whether, you know, something might be good or not. I I don't think he is I Think he's a very even-handed reviewer He has a lot of Background he's done independent films, but he's also a real collector of films It's it's clear that he watches a lot of them and he's a fan of films He's not a he's not a dilettante in that regard.  That's an honest take That's an honest take what he you're from what you just told me So he just you know, he said if you want to I mean I'm paraphrasing you want to watch negative reviews of Madame Webb There's lots up the lots there already But I disagreed with his weepy Presentation in terms of you know movie making is hard It's arduous But it's exciting it's tiresome but energizing and You could be Collapsing on the ground in the evening, but when then you roll in the next day and you're in makeup You're just completely charged up. I mean, it's There's there's no your batteries are fully charged You're ready to go and you're gonna expend all that energy by the end of the day and I didn't understand so it's hard But it's not difficult. So I didn't understand his word His use of the word hard as if we're supposed to feel sorry for these people these people all of whom got paid Extremely handsomely. Yes, they have egos. None of them want to be in a stinker like that doesn't help your career although this movie You know apparently is is is so bad that people are actually feeling sorry for the actors So I don't think it's going to hurt anybody's career. This is not gonna bring anybody down Okay But I go ahead Good movies, you know, if you know the the solution to bad movies is make a good one so He's It's an honest take right as far as like hey, I'm just not gonna add to that's just mine like right I Get it and I've done that a few times, you know, it just is like, you know, what why am I gonna do a Whatever, you know, you know, why am I gonna do another Ziegler hate video? Um and then he you were saying that he says that filmmaking is is hard and he's a filmmaker, right? He he did an independent based on some independent movies.  You've got five days to shoot the film You've blocked it out. You've planned things. You've got your locations. You're just so involved in getting it done That's not sure the hard part hard part is getting it financed I'm gonna wait and talk to you about that Did he say it at any point? Hey, don't don't bash on the film. No He's just like this is just me. Yeah and he did say that Uh He did say that He he didn't have experience with doing big Hollywood movies Uh, it's a different type of freedom. It's a different type of process. Yeah, you know, it's a different thing We know from experience.  He you know all on his own that being said he's like I am so bogged down with with um with a Red tape of it. Just the red tape Uh That it's it's amazing that anything gets through to you know, because it's with a reputable Distribution company and then you're going to see his documentary on on amazon and apple Oh fantastic. Congrats pretty amazing pretty pretty incredible and and and he did it independently like it's already made But soon as you're dealing with studios and legal Forget it forget it. That's a that's a different that's a different monster. I I will say this just just personally right I pay for most If not like a super majority of the movies I go see I pay out of my own pocket Right. I am not I'm not a rich man. That's why when I say you're super chaps Super chats help they really help me So I can pay for my a-list I can pay for this when I when I do get early access or get invited I let the viewer know hey Chris go inviting me to this.  Yeah good writers. They can afford good writers Yeah, they can afford good directors. They can afford the best talent the best talent was great Well most the the female talent. I really liked yeah, you know It's but the it's the writing it's the directing it's a vision. It was like This this it wasn't even good bad like Morbius.  So And an independently produced movie looks independent. I mean they just have that Feeling to it now. Yeah, so my my thing was You guys were talking about it and Chris was saying that making movies is not hard I completely disagree I was you know, it is one of the most difficult things to do like you. Yes, you have to have discipline Discipline is not an easy Thing to practice every day You know, especially if you're creative if you're an artist if you're a producer with that with that with it with your Your different mentality to produce that's much different than being a creative You know creative people are often not very not not a Business savvy and don't know how to do not know how to work in teams Which gore also said, you know, you've got to make a movie. It's you gotta have a team It's like right then. How can you say this is easy? Nothing? What you just said is easy So so this is okay. So as I said in the in the show and right now Hard needs to be defined Because I've done this It's a challenge To find the right people Yeah, so is that hard and I've had a dop quit the day before shoot. Oh my god director photography everybody Yeah, so so the thing is now you're on the phone and you're trying to find someone and I'm a problem solver. I have never not failed to solve a problem. I have utter confidence in myself I'm like Radar in mash Where I need to get my favorite characters of all time So I need to get this thing.  Come on. Yeah. Yeah, I'm driven If I'm in the middle of no, you know, you could be driven and just still be on one side of your brain You're you're you have both your gear your gearhead and and also to a Creative comedic writer and I understand the finances And you understand the finances like I like I needed you like 40 years ago anyways And I can do something together now Yeah, let's do it. It's called uh, holy pablito chat chat chat slantinos Paul Paul and poly together orly Orly as we walk down some street bringing that up explosions behind us, you know because because gore was saying it's it it it it's We have to define hard because yeah, I for one believe this is one of the hardest businesses. Yep to just Compete in guys. I'm mind. I'm out. There's no just because you join sag. That doesn't mean employment doesn't actually it's actually Sometimes it's you lose a lot of them because you are sag if you understand that you know what I mean Um, so we can go back and forth back and forth, but this is a you know back to stuck man That's a great question though defining hard. I think he was a bit. I think he was a bit flip Well, you know, yeah, I mean Yeah, that's that's gore being gore and that's why I love you know getting in getting into it with him and because I think he does that too just to get more conversation going which I mean flogging a script for two years and not and and getting a no Every single time you have a meeting Does that is is that hard? Hmm It's crushing crushing very well, but what's funny is if you do it and Then that's just part of the journey. You don't you don't put it into the hard mentally the hard column If you succeed it's hard while you're not succeeding Did you just have what i'm talking about? I do because it this this is a That's why it's so psychotic this business. Yes Yes, exactly. You're exactly right. Yeah And that and see and and I listen god bless you all God bless you all that uh, are not that have not dabbled in this business and yet say Well, my boss does this and I have to deliver it. It's not the same. No, it's not the same Your example, it's true. It's true in in business world in that business world, right? But this is the most insecure Yes Business you can imagine and where it demands any creative To be insecure emotionally insecure to succeed In writing in right acting. It's just it's just Well, it's you've also got this Jekyll and Hyde thing where while you're defending your creative to executives You are absolutely certain of its quality and its successful Of possibilities, right then they go. Okay. I'm green lighting it. Here's some cash Now you are scared to death.