I want to welcome everybody to five points. Of course, it's five points with the fountain behind us. City Council today took some steps to clarify a lot of questions that we were getting from our residents about the appropriateness of timing and location for wearing masks. Simply put, it's important to wear masks when you can't properly social distance. So we know the three inputs the CDC says to follow. Wash your hands, wear a mask and socially distance. So we want to focus on the mask and social distance, not just here in five points, but in all of our hospitality and retail areas throughout the city. So we're here today to talk about that. We are a unique city that we are a state capital. We are a university town with many wonderful universities and colleges. And with that, we see we have very vibrant hospitality districts. And so the optics that people have been seeing the lack of social distancing in some of these areas is something that we take serious and that we are going to make a special effort of push as we move forward. It is a football weekend. We are very fortunate to have the fighting game cox playing at home this weekend. So it's a great weekend for us to put these initiatives into place. Can't thank our ambassadors are our Columbia Fire Department enough for everything they are doing for us educating, getting getting the masks out. And so we're here today to talk more about that. Chief Jenkins is gonna come up in a minute and tell you about our initiative moving forward. What we've done in the past, how the small businesses in our hospitality districts are helping out with this issue. But first and foremost, I want to thank the University of South Carolina. James Smith is here from USC. They made a wonderful mask donation to the city's efforts. We've got the first donation behind us in a nice brown box. But I wanted to invite James up Mr. Mr Smith from the University of South Carolina to talk about this partnership that we've we've been forging with the university as we as we all as we all move forward together in this. So Mr. Smith, thank you so much, Councilman Brennan. It is wonderful to be here today. I'm privileged to be here on behalf of President Bob Caslin and the University of South Carolina. And to continue what has been a very strong partnership between the members of city council who are here and others who are not present also the mayor and working together to pass ordinances and help us limit and not allow the spread of COVID-19. It is a partnership. And we're all in this together. And key to that partnership has been the ordinances have been have been passed. We are very supportive of what the city did today to extend the face covering ordinance and to raise the fine. We appreciate so much the work of Chief Jenkins and he's done to help enforce those ordinances. We appreciate the work of the local businesses here in five points and others who are helping to reinforce that and their efforts. We all are in this together and we win when we work together to make sure that we protect public health and continue to ensure a good quality of life for the citizens and the one being for our students, faculty and staff. So we're we're proud to be a part of this to partner with Chief Jenkins and to making sure that that everyone covers up. And it's a simple step, but it shows the care and consideration that you have for others. It shows a commitment that we're going to look out for our fellow Gamecocks. So thank you very much. It's a privilege to be with you today. Well, thank you all for being here today. Certainly where I have because we want to keep everybody safe. We want to thank all council members for passing this ordinance and also allowing us to get out here and enforce it. Thank you to the university for this partnership. We also couldn't do our work without all said, imagine Mr. Wilson, so we thank her as well. But we also want to thank all our firefighters and especially our fire marshals who are out here beating ground every day to try to make sure that this ordinance is it works and in effect. Basically what we'll be doing is we'll be going around to some businesses. We're gonna be educating them on the new ordinance. We're also gonna be passing out mass free mass that were donated by USC. And I tell you it's a great partnership because the key to it is not so much the punitive part the key to it just keep everybody safe. And that's what we're gonna be doing. We're gonna be educating people want people to stay safe. All of our young folks are our future. Our old folks is our future as well. So we want to make sure that everybody stays safe and we don't want you to go anyplace and catch it. Take it home to you to your relatives. It's not this is not just a five points effort. This is a whole city effort. I do also want to thank the businesses down in some of them. They have really partnered with us to make sure that folks that are in the line. They remind them to keep your mask on, keep your mask on. And that's the the posture that we're gonna be preaching here on out. But you know, smoky bear teach you about keeping your forest fires down. That's what you preach about. Sparky talks about fires, but Sparky gonna be fulfilling a new role now. So what are we doing? Even sparky wants to get the message out. So we're gonna be using using sparky to educate people on getting mad showcasing him. Let him walk around. Let people see even sparky don't have a mask on. So he's parking you do it. So can you. So again, this is what we're gonna be doing. And we appreciate you all coming out. And we'll walk around and start giving some mass up.


He's going to spark here. Why? The most incorrect read I've ever made in my life. The most incorrect read. How's it going everybody? Dato Doi here with our first ever DLC ranked matches for Cooler and 17. Obviously this is going to kick off our week to ranked matches with these guys. We got Android 17 up front because of those mix ups. Cooler's in the middle just because I didn't know where else to put them. And of course we got Yamcha backing them up. Unfortunately for us, it doesn't look like our opponent is here to play DLC characters. And we're very close to getting demoted, so there is definitely something on the line here. From my experience, limited as it may be with Android 17, his hardest part of the game is, I tried to, I knew that was coming. But anyway, the hardest thing with Android 17 is getting in on that opponent. So it does suck that I don't have a beam assist, but we're going to try to make up with that by just running in. Oh, let's go. We're in. All right, so we do get a basic mid-screen combo here. I'm not going to go for anything too fancy. As always, if you have any tech, by the way, hit me up. No, wrong combo. No, I, ah. Yep, that was my turn. All right, watch this pose, watch this pose. Ah, ah, glare at him. Take a little look at him. Let's take a little look at him, 17. God, I love that, that little pose. All right, we're going to be switching out here pretty soon. Okay, I couldn't cheese my way into that one. All right, and that's a free switch in for Yamcha, who will provide us with the sliding. Promise I will get cooler. Oh, okay, deflect me, will you? And sorry if this has been more analytical than, then, oh no, our usual right matches. But you know, the first one of the week is usually always just me talking ideas with you guys. Cooler time. All right, cooler is menacing in this corner. Oh, it's a shame. I would have loved to stay in it longer. Look at the absolute range on cooler, by the way.  Like I know Broly in 16, obviously, but just in terms of range, cooler feels so much bigger than these dudes. It's insane, like look at the size difference. That was already a vanish combo. Ah, ah, ah, no sliding. This guy is saving a lot of bar. I actually thought that was a vanish. Okay, we're gonna be blocking here for a little. Backdash on that? No backdash, wow, that was jailed. Ah, I couldn't get out of there. Okay, that was very good. I'm surprised that jailed me. Also, this is a very good connection. I'm glad we got a good connection for the first one. We not dying though. Oh, never mind, I forgot Android 16 was out. For some reason, I thought that was the opposite, but yeah, we're dying. Go tank 16, that's too crazy, bro. What am I supposed to do about that? Superdash me. That's the best you got, a little mix-up.  I didn't even consider him going low on that one. All right, level three, we are gonna spark here. Let's hope our opponent isn't wire tapped into our brain because we're definitely sparking. Got him. Oh no, I didn't mean to click that button. We live. All right, we're gonna get Cooler in. Oh wait, no, this is gonna switch sides. Never mind, not doing that. Cooler, Cooler, bro. Cooler, Cooler, Cooler, not in the first game, dude. Not like this. All right, but I have faith, I have faith. Come on. Superdash didn't go through. That's unfortunate as well. Don't ever touch me in my counter state. Android 16, you're being erased. Boom. Oh, that is a satisfying super. The counter state on that is too good. Oh, yes, don't touch Cooler. Watch me hit this. Look at the range. This character is wild. I saw somebody say he was low tier. Get that out. Wow, remember when I said this was good connection?  Cooler, I'm gonna try to save up three bars because he won't be able to touch me. Never mind. Pick him up like a baby Cooler. I'm gonna try to cheese him out with a low here. No, I can't believe that didn't hit. I can't believe it. If that would have hit, that would have been so good. I can really see Cooler being super good, by the way. No, I tried changing sides with the change. Ah, I shouldn't have done that, but that was a really good game. Really good first game. Obviously we have some defensive work to do, but for the first game with those characters, I'm jazzed to get into it already. I can't believe it. Personally, can't believe a lot of what's going on here. He's saving up those assists to try to go in. So we gotta, how did, huh? What?  Oh, low. Oh, he didn't go for a direct attack after that. Okay, messed up the confirmation off of 17. That's fine though, we did get the low off. We're free. On the back. Okay, good. I get, super dash doesn't go through that. I gotta remember, I keep trying to cheese it like a Vegeta assist. That's, oh thank the Lord that worked. Okay, okay. Oh, it didn't go high enough. That was something I wanted to try. I think he wants to switch. Oh, maybe not. Oh no, that hit me, okay. Switching, okay. That's something we had to do there. Oh, beautiful, we're just gonna switch him right away. Beautiful, we're switching him right away. Oh, beautiful. That was exactly what you wanna see there. In that situation, that's exactly what you wanna see. Oh, I'm loving these characters together, dude. Like I was playing a lot of 17 on Switch, but I guess I never considered like how much I'd like him on my normal setup. Wow, I could not get normal out there. Oh, why do I back dash instead of downhaving these things? All right, 17 is looking hella sick. Oh, this was a bad decision. That's not gonna hard knock down. Kinda forgot what we were doing here. Cheesy level one. Oh, he knows. Oh, he knows. Okay. Oh, beautiful downhaving. Is it gonna switch out? Okay, I honestly don't mind that too much. Mm, 17's gonna get this knockout. Yeah, please knockout. I don't know how much damage it does. No pose. Oh, what are you doing?  Oh, too much bar, too much bar. I hit heavy too many times. I tend to do that when I get excited. I wanted the heavy EX roll into a high. That was the plan anyway. But the plan obviously failed. Cooler, satisfying. Oh, you don't get it like that, boys. Oh, cooler, too good. I tried to downhave that. Didn't really work out. We should be able to get a clean win here. I tried to downhave that too. All right, cooler. If you could live, buddy, that would be greatly appreciated. Oh, just an elbow. I wanted to finish that with a little something flashier, but all right, we take it. Cooler gets his first win in rank for me. 17 did put in a lot more work though. That's fine, I put in more time with 17. Let's see what cooler can do up front. Oh, look at this, look at this range. I'm saying that a lot, but just look at it.   No, miss. Oh, why did I EX? That was not the right move. Please excuse me as I work through my trying difficulties of trying to overcome my stupidity. Oh, but man, cooler, cooler's a lot of fun. My turn. We're going to the corner. Going back to the corner. Oh, that combo'd. Yo, was that gonna kill? Oh, it doesn't, but. Oh, cooler, if y'all thought cooler was low tier, you must be thinking wrong. Look at the range he commands so much space. Cooler's not low tier, there's no way. I refuse to believe it, watch this. Okay, I thought he was gonna be a Bardock player there, but clearly this guy failed the entry exam at the school of Bardock. What are you doing? What are you doing at the school of Bardock if you can't pass the entry exam? That's not gonna work. Ah, I haven't even been mixing in dragon rushes. I'll do that starting now. Cooler just somehow became cool to me. What are you doing? Let's not do that again. Hit me, bro. Okay. Look at this.  All right, cooler's leaving us now, but let's be honest. That entire game was cooler. Cooler might have to go up front. Ah, I tried to block that. Okay, he didn't go for the overhead there. Okay, there we go. Ah, vanish didn't come out in time. That was a big part of my plan there that just got soiled. Okay, I was so worried about the grab that I didn't ever go on offense against that Bardock. I'll try not to do that again. We're gonna spark here. Damn, I tried to keep forgetting you can't do that. Oh, you thought I was staying in with 17? Ah, what are you doing? Be patient. That's what I do, your resets. All right, let's see if we can't mix this man up.  Boom, 17 with the behind the back claw. Loving it, dude. Ah, no outro, I love this man's outro. But we still pose and looking mad, mad fabulous. All right, let's go. Oh, that was supposed to be my turn. Looking for that grab. He doesn't seem to want to throw it out. So now we're going to look to get aggressive here. Okay, we can block everything this guy wants to throw it. That's no problem. And then we tech the grab, we're out. We just played perfect defense there. We earned our right to be free and I missed the down heavy. And we're in jail again. You said, I've been practicing defense though. I mean, that guy's, it's not like he was hitting me with any assist, but I have been practicing. Also, it does help that it's only two frames. Mm, saw it coming. And yeah, 17 is a little low. That's as a matter because we're going behind and then we're also going in front. So you can have that back. Mm, unfortunate for, unfortunate for me. I was going to say unfortunate for that. Oh, no. Ah, no tail. Ah, I'm not hitting the ground fast enough. I think keep thinking if I hit the ground, I got it. Oh, lag. Okay, we were too high up to do anything. So we're just going to bring back in Bardock. Ah, I went with the light low option. Not good, not good. I'm surprised he didn't do anything about that. That was not the correct call. Okay, we're just going to get Gotenks back in. That's about as much damage as we're doing to this guy. Dragon rush. I did this because I do believe we can, didn't expect to do that. I held forward for some reason. Undeniably unbelievable. Okay. Okay, we don't want 16 in here. We want Gotenks. Oh, I might, no, Gotenks level three doesn't do that much. So we're probably alive. Very injured, but probably alive. Really? How did he sneak that in there? I hit Bardock. Let me live, please. Please let me live. Oh no. Ah. Oh, cooler. I thought you hit him, buddy. Or at least scared him. Cooler, you disappointed me there. Also, I disappointed me there. Okay, again, we do not want 16 out here. Huh? I didn't know it had that kind of effect. It stomped me? I didn't know that was a thing. Also, I'm just glad that happened. The way it did, I'm just glad that happened. All right, we should probably get Cooler out here. He could use the assist, honestly. No super dash. Oh, I'd like to record the show that I have not blocked one of those. Oh, that was sick. Oh my God, cooler. Okay. I'll back down, I'll back down for now. My turn. Oh, not my turn. It was a little, you know, I couldn't tell. Okay. I wanted to hit him with that so I could switch in and, you know, catch him by surprise. That's fine. We'll recover most of this. He'll probably go for the hard knockdown. I agree with this call. He's got to get the mix up in. But I think I've shown, I've been doing pretty good defense today. So my confidence is higher than usual. Especially when that was not even close to a mix up. Just kind of jumped in the air in super dash. Not the brightest, not the best, but. Wow, we've gained so many points. Okay. I'm kind of expecting just a random area. Okay. A little off base. Okay, we got to defend again. If he jumps again. Oh, no super dash, that's right. I thought he was going to super dash after that whiff down, have you? Okay. We want to bring in his go tanks because that's the assist that's really getting us more. Oh, nice tech he saw. Keyblast hit me. Oh, why would I vanish there? Is that a level one death? I don't think so. Well, we have a lot of defending to do. Ah, oh. All right, very lucky for us. Very lucky here. We are going to get in cooler. Oh, if that would have reached. This guy would have been in for a world of trouble. Ow, my thumb. I heard my thumb there trying to block. That's something I noticed with the Nintendo Switch version as well. Oh yeah, I used my jumps. No, no, no. Ah, it only eats one hit. I forgot, I forgot that was risky. That was risky. I thought I could cheese it. I thought I could. No, 17. No, no. Oh, 17 lived. Oh, come on. Was that a mix up? Okay, I hit a button there. In fact, I hit a pretty bad button. I was going to try to down heavy. Not a reaction, just a guess. Coolers taking massive damage here. Oh, we're dead. Yep, that's a lot of damage. We were dead there if he wanted us dead there. More love of the story. Whoops. Oh, Reed. Oh, don't try to avoid it, dude. Is that going to hit? I hope that goes low enough. Ah, so risky. I'm still working to see what I can get away with on that level three. Please hit. Mm, ha, yeah. Love that animation. You could, I wish he screamed during it. Why is there no scream? Ah, ah, cross up. I didn't expect it. Even though 17 stood up and looked the other direction. Ah, all right, well, in our cooler 17 video, it comes down to a Yamcha comeback, which has been happening a lot on this channel lately. We will mix up the assist, by the way. It won't just be Yamcha. Maybe for the first two videos, we'll use Yamcha, because he's my boy. But we'll mix it up. Okay. Ah, that was so bad of me. Wow, he hit me. Does he have a jump? He does. Interesting. Level three mix up. This is gonna be a rough one. Ooh, okay. This is gonna be a rough thing to block, is what I'm saying. Yep, okay. Ah, of course he would. Why wouldn't he do that? Okay. This is super bad for us here, but we gotta focus on the positives.  And he is going to spark in here. There's no way he's not, right? Because you want your two characters alive. You wanna be able to have the assist. I probably should just click buttons after that. Why didn't I press my agenda? Okay, we're still here. Why, I've never seen that stomping effect before. How have I never noticed that? That seems really good. Is that the new effect they added in the way back patch? That's so good.  I mean, honestly, both very good. They're both a viable option. That's a poor Yamcha assist. Ah, he caught me. There we go. That's what I wanna see. Okay, now it's our turn. Mm, I see, I've been stunning him. I've seen that he likes to reflect there. Oh, hope you guys watch my video because you're about to see it live. Sparks, wow, he's seen the video. Oh, beautiful down heavy. Every time I see it down heavy in the air like that, you gotta appreciate it. Um, I think in the interest of keeping this game equal, I should spark here and not let the momentum build. 17. Oh, I was about to say that didn't kill. I forgot it plays that little animation. I was like, what? Grabbed my controller nervously. Spamming cooler assist here. Yup. Ah, I tried to jump back. Ah, I couldn't escape. Ha ha. Ah, I caught the Super Dash. Oh, we're alive. Only because he wanted us to be, but not sure why that didn't hit me, but I'll take it. Ha ha ha, I'll definitely take that all the way to the back. Mm, just gonna go standard route here. I'm back. No, that was, no, that was supposed to be a level one, but I guess it doesn't matter, but that was supposed to be a level one into somebody else's level one. Didn't really matter who, but yeah, super unfortunate that this has happened. Let's get cooler back out here. Huh? Throw him. Trash this guy. Why we deflected that?  Ah, man, he's been avoiding that move pretty good. I've been throwing it out a lot.  Cooler laughed because he knew that she was. He tripped him from below and vanished and that killed him. Super good in the clutch. All right guys, well that's gonna do it for our first cooler and 17 video. Sorry if I wasn't as talkative. Give me a little while. I think I'm getting these two characters down in real ma- Huh?  This video is gonna be so long. They got rid of the, it's just death matches now. Why? Why Bandai? I'm trying to run a YouTube channel here. I, ah, Mike's, Mike's, my excuse has always been, well that's the set, I'll call it. But now I'm just stuck here for eternity. No, Bandai. All right, well this is the last game. This is the one hour Datodoya special. People are gonna be like, oh, why is this video so long? Overhead. Overhead. Nope. Ah, he just did a good job blocking there. He just deserved it. Oh, why is this video so long? It gets to the end. All right guys, well that's gonna be it for me. I'm done. What? Oh man, okay. Well, let's try to win. Like obviously I'm not gonna. Ah! Ah! That much foundation is shook, dude. Death matches and dragon ball? Why? Wow, I need to switch out. Wow, he expected a hit there. What? Wow, it's a whole new game, dragon ball fighters. I'm shook to the core. Well, how are we gonna handle ranked matches now? Cause we've always done it that way. We used to do two matches when it only went up to three. Man, this is crazy. Welcome to a new age of fighters, everybody. Let's see if season two comes along. He's gonna spark here. Ha ha! The most incorrect read I've ever made in my life. The most incorrect read. I tried hitting buttons. I'm like, everything I've done this match has been wrong. And tried to end the video, incorrect. I thought that was just gonna be a switch thing or maybe they just didn't implement it yet. Cause I did see that on the switch, but that's real. This is the life now. Bandai Namco has locked me in forever. Is he gonna, I want him to block one of these. Ah, speaking of blocking, perhaps I should have been doing the blocking. All right, drop me down. That's not gonna hit. Please, ah! Now we gotta find a way to switch it out. Or maybe since he's doing wake up level threes, maybe that's an invitation for the boy to do one. Nope, no it wasn't. That was a stone cold nay. All right, we need to get go tanks back out if we even want a chance of winning this game. But I think it has to be cooler. Okay, he caught me slipping. I tried to stick out a tail. No, let the record show that I do not deserve this cruel treatment. All right, knock me down. I was like, oh, not this knock down. I just wanted to be knocked down. Not hard knocked out, okay. Let's see if we can't try to find a, hit me. Oh, he knew. Wait, we still have a chance. Oh, I forgot three heavy is a move for cooler. Well, I'm gonna call it there.  No, I'm gonna click no rematch there. Thank you. Okay, well, how you guys enjoying the update, by the way? Let me know down in the comments below. I'm enjoying it. I did not know about that new feature, but here we are 30 minutes later. So as always, let me know your favorite moment of the rank session down below in the comments. I'll be down there as always. While you're down there, if you like these videos and wanna support the channel, make sure to hit the like button and subscribe. And hey, also just a bonus one. I should have said this before, but who you enjoying more, Android 17 or cooler, they're finally here and so brings season one to a close. It's a very different environment, as you can tell by Beerus and Goku. But yeah, I'm Blatidoya. I'll see you in the next video.


Hey, what's up dudes and dudettes drew here. It is Monday, February 3rd, 2020 And I'm gonna do something a little bit different for just a couple of minutes. This is a book update Because I want to clarify some things. It's getting a little bit confusing And I think you guys need to hear this news so you know exactly what's going on So what you see on my screen right now clearly is a book cover This is the book that I've been talking about for the last seven months and writing for the last seven months This book is tentatively titled the anxious truth and as you can see a step-by-step guide to overcoming and understanding Anxiety panic and agoraphobia. This is a giant 70,000 word comprehensive recovery guide. This is what you guys have been, you know, so enthusiastic about which by the way I really really appreciate everybody's been so positive and encouraging and supportive and excited about the project that It's definitely helped to motivate me and I appreciate all that support So this is the book that everybody's been talking about it's now been written I finished writing it this past weekend and it's now going to go into the editing and production phase And it'll probably get released somewhere in about 90 days from now, right? So that's what's going on with this book and I'm calling this one of the gray book because it's got the gray cover When I was writing this book and starting to finish it up I knew I wanted to put my story my personal recovery story in the book as an introduction So I started writing that Maybe about a week and a half ago and as I wrote and I tried to incorporate all the questions that people have asked me Over the years about my particular story I wanted to get as detailed as I could that introduction just started getting bigger and bigger and bigger And it soon became pretty apparent that it was way too big just to be the introduction to this book This book is already 70,000 words So I couldn't really write a giant introduction and just tack it onto the front of this doesn't make any sense So in the last seven days, I actually wrote a completely new book this book So I'm calling this one the white book because of the colors and you can see this one is the anxious truth and anxiety story This is my recovery from panic anxiety and agoraphobia This book did not exist 10 days ago and I wrote this entire book in the span of about five days last week So I've been pretty busy And to be honest with it, I'm tired and I probably look it So this book is done It is my personal story that so many people have asked about and it serves as a bit of a prologue I really want to make sure that people that are reading understand what I lived like I'm not just making this stuff up I live this just like you are living it now and That that's the object of the game So this will be released on february 18th and it will be free Like I'm not going to make anybody buy this book that would seem ridiculous to me So it will be free in a bunch of different places. It will be on amazon, but it can't be free on amazon It's got to be 99 cents. That's the minimum price of a book that amazon will let me sell So I can't make it free there But if you get it from google play or apple ibooks or on smashwords.com or maybe from my own website I'm not sure yet. It will be free. You just download it and it's fine But at amazon, it's got to be 99 cents. It will be an e-book So it's not going to be printed. I mean unless a lot of people really asked for a print version of it Then I'll consider that but otherwise it'll be just an e-book and I will probably also read it So it'll be an audiobook, but that's that's going to take another month or so for me to get that together So I just wanted to let you know this book is free This is my personal story and this will be released on february 18th And I will make an announcement about that And this book the gray book is the recovery guide that everybody has been waiting for and been so encouraging about me writing This will be in about 90 days roughly So there are now two books and that's why I think things were getting a little bit confusing That the fact that there are now two books So there's the regular book that's coming out later and then there's this book Which is the free e-book and that will be out in about 15 days from now So what i'm going to ask is that if you've not already done this and you want to stay abreast of this I mean i'll post on facebook and instagram and all that stuff like I usually do But get on my mailing list. So go to the anxious truth.com And you'll see a link to to the books book updates Just get on the mailing list on that page and I'll let everybody know via email You know what's going on with this book where you can get it where it's going to be free and then amazon is 99 cents And then I'll keep everybody posted as to the other book the gray book the recovery guide as we're going through that process also So we're getting there and again. Thank you so much for all the support and encouragement But yeah, grab this one first. It's free. You can share it. You can do whatever you want All I'm going to ask in return is if you get this book and you like it and you think it was worthwhile reading And it's helping you or motivating you or whatever wherever you got it just go and rate it and review it That's that's all I'm going to ask and then pass it on to somebody else. Maybe that'll it'll help them I don't know but yeah, that's the story two books didn't expect that to happen and Guys like I can't even believe that everybody's so like psyched about this project. It's it's amazing I never expected that I thank you all very very much and I will see you soon


Grab a fresh pair of pants.  You requested it. You got it Ethan I'm apparently still in movies. Hawk is the lead in Sinister He's the typical horror film dad who's a writer with little time for his family. The guy's not likable in the slightest I'm not sure if that was the intention or not Seriously, this guy's not dad of the year. He moved his family into a house that's had multiple murders and missing victims He's really the main focus of the film and the wife and kids just get a handful of small scenes There's a little bit of comic relief from one of the police deputies and of course is the old cop on his way to retirement Once nothing to do with the writer. What are you doing in my town, son? Nothing for you here. Nothing but pain and sorrow.  That's gonna end up F***ing you up That was a spot-on impression of him and Sidious had the better cast for me And that's mainly because the people make logical decisions for the most part housewife slash Musician Raina Lambert is the focus here. Nothing really exciting about her character though But she is the central one She was still nice to watch though because she's actually very concerned about the odd shit taking place in the house And two, she's played by Rose Byron Byron Byron Byron, BYRNE, no idea how to say it. She's easy on the eyes. She's good to look at. She's attractive.  It's almost a requirement to have a creepy kid in a horror film And this one has Ty Simpkins as Rainy's son Dalton. That's actually unfair to say he never does go full creepy He's just in a coma. I just assumed he would and that's a testament to the script that he never does He doesn't fall into that trapping. The highlight for me is actress Lynn Shea's character the paranormal specialist It was really fun to watch her and her two colleagues ghostbuster around the house look for evidence of any paranormal activity But these are scary movies. It's all about the villain. It's all about the threat and here I think they're about Ty I think they're about even because although they started out scary enough by the end I wasn't crying in the corner with my teddy like I thought it would be. I was actually almost laughing Not a good sign. Insidious provides us with multiple astral projections But the main baddie is a red-faced demon who is extremely dangerous Unfortunately when we really get a good look at him later, he looks almost cartoonish in nature Sinister in my opinion has the scarier of the two villains and that's thanks to mr. Boogie's demented nature But that final shot where he pops out of the corner for a little peekaboo That was full on cheese Don't Sinister and insidious started very different from one another and I was scratching my head trying to figure out why the fans Wanted me to review them together that it turns out. They're actually very similar They're both about demons trying to escape their world by attaching a living host In order to carry out their dirty deeds Done dirt cheap I prefer the insidious approach though mainly because I didn't have to shout on my tv every five seconds For the dumbass protagonist to do something logical. In fact early in insidious the family moves out It's like a half hour in and they're already out of the house a couple crazy things happen. The wife's like no No, we're leaving I was like what? That's logical in a horror movie Sinister doesn't even bother with logic and it's very frustrating to watch Ethan hawk ignore the most obvious things ever He sees ghost hands pulling him into the floorboards on his computer. He sees this the evidence there He finds out later that this is in fact some sort of paranormal creature Who's eating children and killing families. He has a family and children.  I'm invested every time it went night I'm like, okay.  We get shadows in the corners We get empty shots of darkness But that final act when you see the creature it's over it gets it gets way too loony tunes These are both shot very well and it's rare to see a gimmicky camera angle. Yes There are some cliches like the boy coming out of the box looking like something out of the exorcist body all mangled Twisted up like two pretzels having sex I have no idea. I just say things jump scares are of course staple But you can't have a horror without those our villains are bad guys They're left to our imaginations and that can be the scariest place to go Even when it is obvious it still works really well Like in sinister when there's the laptop sitting up and you can see mr. Boogie's face there just Standing there and you know at any given moment He's gonna look and even when he does it boom It still gets you given it's a sinister in this category because I really liked all the disturbing imagery The party by the pool the home and garden scene the fire in the car. They're all very eerie. They're all very fun Music and scary movies go hand in hand. Usually they're an extension of the script. It's like a laugh track It's like a live audience telling you what you should be feeling in that moment You hear that loud jump you hear that loud pop in the music and you know, yeah It's all very par for the course and that's both good and bad because while I'm expecting it I wanted something a bit more impressive As I've told you before I have a bias towards the horror genre I have a distaste for them in general But these two weren't awful insidious was actually pretty good. I mean there's there's much better out there But between the two I'd go insidious every day of the week. This isn't my area to swim in I'm not familiar with this side of the pool. So why don't you guys you horror experts? It sounds like horror you horror experts as well Let me know where these films stand on your list. Are they even close to the top? Give me some recommendations too. I'll do some more feuds on the the scary franchises More than just reviews. This is movie feuds Jesus Christ


So, good afternoon everyone. I'm going to change a bit the subject. I'm going to talk about the full provisioning and management of food for the Roman city of Bracharagusta based on the anthropological analysis that I've made in one of the necropolis of the city. I've divided this presentation in three sections. First, a small introduction about some concepts, general concepts about this subject. Then I'm going to explain briefly the Robinville's qualitative model of full consumption for Pompeii, which will be the basis of our study for Bracharagusta in which I'm going to talk about the full provisioning areas, catchment areas for the city and general considerations about the wood necessary for the cremations. So, as it's obvious to everyone, for pre-industrial societies, wood was almost the only resource for several activities such as eating, cooking, cremating the dead and construction, and understanding how each of these, how societies collected, managed and used this flow is important for understanding each of these activities, but also in a broader sense to understand the territorial management, landscape use and the environmental impacts of these societies in the environment. Surprisingly, there is not a lot of information about this, both in classical history, classical economy and also in archivotomy, and when these subjects are addressed are only in broad general terms and not in quantifiable and qualitative terms backed up by architecture. One of the few exceptions to this trend is the research undertaken by Robinville for Pompeii and Rome, which I'm going to explain briefly. So, for Pompeii, this research, Robinville's research was based on the anthropological study in several sites in Pompeii. The main species that she identified was Fagosovatica among others, such as oak, ornbim and maple, and she also identified the main catchment areas of wool for the city, such as in the upper mountain slopes, midslopes and managed forests and also lower slopes. She then, she based their model in a series of assumptions such as that ethnographical epoxy data related to wood dependence for industrial societies. She assumed that all the fuel used in the city was of regional origin. There was no, not in the parts of wood, and she considered several variables such as population estimates, several estimations for the population, full consumption per person per year, the ratio of raw wood and charcoal used in the city, and charcoal productivity, which means the amount of charcoal, the amount of wood necessary for making one ton of charcoal, and for general forest productivity in the area. She compiled everything in a mathematical formula and then formulated this spreadsheet with the forest area required for each of these variables. I've tried to adapt something similar to Bracar Augusta. This city, this Roman city, was founded in the first third century as the capital of the Covetus Bracar Augusta in the province of Tarrakumis, it's not least in Liberia. The importance of the city grew in the following centuries, becoming the capital of the newly created province of Galicia, and then with the barbaric invasions it became the capital of the Suevi kingdom between the 5th and the 7th century. As any proper medium-sized provincial capital in the Roman Empire that all the necessary public buildings such as theaters, Roman baths and domes, several domes, and also obviously several necropolises. The largest one, the one underlined, the grapples of the road 17, was the largest so far found, was excavated during one and a half year, in 2008 and 2009, when more than two well, and 200 burial depositions were identified, mostly permission in deposits. It was located in the eastern outskirts of the city alongside this road connecting Bracar to Rasturica, and kept being continuously used for almost six centuries. During the excavation there were thousands of samples, something, a carbonyl sample, something made. In total, we've analyzed in the last couple of years almost 47,000 charcoal fragments in more than 180 permission deposits. We've identified almost 30 species, and the Citus Oak was by far the most frequently identified, and overall the total species identified almost three quarters were collected in climatic mixed oak forests. For this data, for this model, we've only used the data regarding to the first and second centuries AD, because they comprised almost all the decremation depositions, because afterwards there was the start of greening, animation practices, and the cremation deposits started to become fewer. Among the 30 identified species, the presence of Pinus subvertis and Fardus subatica was particularly interesting, because it does not occur naturally in the vicinity of the city, nowadays it only exists naturally in the Gerege mountain range, which is the areas highlighted, so it already implied a broad area of wood collection necessary to sustain the city. While applying the Robinville's model, we've based on the same variables that she chose, ethnographical proxy data, the full supply of wind of regional origin, and we only changed the population estimations according to what's currently known for the city. And we also compiled a similar table with the values of the actors necessary to supply the city. I've then picked three different scenarios, and placed the total area that would have been necessary to sustain the city according to these conservative scenarios. The first scenario relates to the lowest estimations of population and consumption, and the highest levels of productivity, and in this case it will only be necessary 700 actors of wood. I'm always talking about wood, and this also refers only to wood consumption per year. And more average scenario, combining the medium of all these variables, would require roughly 12,000 actors, and a more worst case scenario with high numbers of population and consumption, and lowest productivity, would require this enormous area. And these are only, these areas that I like only refer to, they are not exactly the points where we think the wood was being collected, but were just to give a broad sense of the area necessary to what I'm talking about. Of course, the city was not an island, there was previous occupations and contemporary occupations. This region is especially interesting because it had extensive density of occupations during the Iron Age, and also towards the Roman Age, with hundreds of known sites. And when we cross all this information, we suspect that the areas of Fuerwood provision would most likely fall in these great areas in which there are less, in which there are less known sites, psychological sites, and they are particularly interesting because they coincide with the areas of Pines and Silvestes and Fagos, which is this mountain range where they naturally occur. And this would be also a very suitable location for wood collection of the good transportation lines. Both these roads cross directly through these forests, and also there was a strong possibility based on the geographical examples of the region that some of this wood might be transporting downstream via rafts using the Omi River and the Cavador River, which go right beneath Merakarogusti. This region also is particularly interesting because it has one of the highest annual rainfall percentages in Europe, which would have increased regeneration, so there will be always, at least during the first centuries of the Roman period, would have had extensive forests. But as soon as the Romans settled, and especially in the area of Rakharogusti, the paleological data from this Gerez mountain range, from the lagoon placed here in this spot, showed a massive deforestation trend. So the woodlands would not be able to recuperate from the necessity to withstand all this population and all these needs. We've also made some other experiments with this model while to calculate the fuel necessary for the formation. Several ethnographic and experimental data point that would be necessary for 200 to 1000 kilograms of dried wood to perform a full cremation. The size and structure of the pyres are usually standard since prehistory, using a series of logs, large logs, or albs or quarters, arranged in this alternated pattern. So in order for the cremation, it would have been necessary to fell the trees, to cut off trees, entire trees. It could not be possible to make a pyre with dried wood collected randomly in the forest. So in this case we've used not hectares, but full oaks, since the oaks were the main species identified. And in the region, major oaks, about 30 meters high, could provide up to 15 tons of dried wood. So we've estimated for 169 cremations that we have identified in the first two centuries, how much wood regarding to this tree hypothesis, 250,000 wood per cremation, it would only require about 33.8 average oaks, waiting 5 tons each, or 13 in case of larger oaks. Because these are very meager results, at least we were respecting much more, we've made a crude estimation of the total deaths in the city between these two centuries, and then crossed the total values with the current density of oaks per actor in the region, and still, even in the worst case scenarios, when each cremation would require one ton of wood, that would be only, this 21,000 tons, would have been required only 2.2 hectares to be collected, so it's a very, very small number. So as a quick summary, these pedifiable models for full consumption have a huge potential to provide important insights on territorial management and environmental impacts. The more data we consider in these models, and the more accurate it is, the more accurate these models can be, and the more useful they can be to perceive the size of the city, the area outside the city that would have required for providing all these materials. Among the old and the wood necessary for this variety of activities, cremation would have only required a minimal amount, and we are now trying to improve, to fine-tune this model, to include the most variables possible to try to be as accurate as it can be. So thank you.


For nearly five decades, Historic Denver, Incorporated has been the leading preservation organization in the city of Denver. The organization was founded in 1970 as part of a significant public effort to save the home of Titanic survivor Margaret Molly Brown. The organization acquired and restored the property and today the Molly Brown House Museum serves 55,000 visitors each year through tours, educational programs, outreach, and exhibits. Working closely with the public and local officials to address the challenges of a developing city, Historic Denver has been the driving force behind many vital preservation wins throughout the city. The economic success following the designation of the Lower Downtown Historic District has become a catalyst for numerous additional residential and commercial districts in the area. Recently, the organization has worked to enhance Colorado's state tax credit and continues to lead efforts to protect Larimer Square, Denver's first historic district. Historic Denver is known to many as a resource for the community. Through technical assistance, funding, and educational tools, they empower the public to advocate for Denver's historic identity.


Felly we're passing on to you lot. I'm going to go over some of the consequences, and some of the approaches that we've used to mitigate the difficulties, and I'm hoping also that some of you here might have some useful suggestions either for the Zen packaging in Debian or for us as upstream. So now, let me show you an overview of a typical Zen system with the key components broken out. Don't worry, there's not going to be 46 slides like this one. So firstly, I have to make a note about terminology. We use the term DOMnaught to refer to the first privileged guest operating system, which in most systems does all the back-end work of managing the system and its real hardware. Many of you who won't, sorry, right, yes. Many of you, even if you're Zen users, probably won't be familiar with several of the boxes on this diagram. Particularly there's some internal pieces which are part of our Zen upstream code. And you'll see I've drawn this blue box around the code for which we're upstream, and it's a rather unfortunate shape, and that's where many of our difficulties come from. So the code for which we're upstream comes in two big pieces. The first is the Zen hypervisor itself right here at the bottom, which you will have all heard of. And the second is this collection of libraries, scripts, demons, supporting tools, et cetera, which allow the host to do the work of managing and supporting the system and all the guests. Upstream, we call this part the Zen tools. Unfortunately, this is a bit confusing because there's also the Debian Zen Tools package. I'm going to keep using the upstream terminology here, so you'll just have to bear with me on that. The Debian Zen Tools package is a little thing up here, which is a sort of provisioning utility, which uses all the Zen tools stack code. So together with these higher layers like Zen Tools package and OpenStack and whatever, Zappi maybe, we call everything above the hypervisor and the domino kernel, the tool stack. So as you can see from this diagram, there are some components of the system for which we're not upstream, and there are three really important parts of that. The first of these is the guest operating system. So obviously this is the whole point of the exercise, and so in some ways it's the most important, but it's also the easiest from a compatibility point of view, at least for a downstream like Debian. So the guest might be another install of the same Debian version as running in Domnord, or it might be some other free operating system, which has been specially adapted, paravirtualised, as we call it, for running in Zen, so we call that a PV guest, or it might be an unmodified operating system for which we're providing a full PC emulation, so like an HVM guest, and that might even be a proprietary system such as Windows. Now the point of Zen is to provide a reliable and stable platform, and to decouple guest operating systems from hardware and sport software, so I'm going all this stuff here in blue in the lower layers. And often the guest will be run by a different personal organisation to the host, either in some kind of cloud facility, or because you're hosting internal sysadmin providers are different to the guest admins. So we've traditionally had a very strong compatibility guarantee. Guests which are written against old versions of Zen, and work correctly there, are supposed to work on future versions of Zen. Currently upstream supports guests written to run on previous Zen versions going back to Zen 3.0, which was released in 2005. So that means we retain the ability to service all the old guest-facing hypercalls, all the IO facilities at memory management interfaces, even if they've been replaced by something newer, better, faster, less pain to support. And this compatibility guarantee goes even further. For guests and Zen versions which support live migration, we ain't support live migration of your guest from an old version of Zen to a newer one. So if everything's working properly, you should be able to upgrade your Zen host without even needing to reboot your guests. And this migration facility means if you have multiple hosts and enough spare capacity, you can do what Zappi calls a rolling upgrade, where you can upgrade your entire hosting platform one host at a time by migrating the guests off each host as it's to be upgraded, and then migrating them back again afterwards. So actually meeting this compatibility promise from upstream point of view in every detail is quite tough. And the most difficult part of it, or one of the most difficult parts, is we don't always know exactly how the old guests behave, and sadly not all of the interface documentation was always perfect. But almost all these guest interfaces have pretty good extension mechanisms, so there are spare fields in instructs, there's key value namespaces where we can add new keys, there's a fair amount of capability negotiation mechanisms. There's not always sufficient because guests may be buggy, and even quite subtle changes can expose new bugs in guests, but even when that happens, we try to cope. So for example, a particular common kind of guest bug is that it gets partial or broken support for a shiny new Zen feature. So it then works fine on the old versions of Zen without the feature, but when you upgrade your platform, the guest tries to use the new feature and stabs itself in the eyes. So we have knobs that Zen administrator can twiddle for each guest to say, well, just don't advertise that feature, so to work around that lets you sidestep those kind of guest bugs. So what this promise means in practice is that when we're doing upstream work, we give forward compatibility for guests a lot of attention, both in design implementation, and of course it means we treat compatibility bugs as regressions which deserve a fix and back ports and all those kind of things. Now there's one other difficulty with providing this guarantee which I'll be getting on to, which is particular to HVM guests, which causes pain for downstreams such as Debian, and I'll get on to that later. So the other big part of the system for which we're not upstream is the dominoct kernel. Most in installations use Linux. There are other platforms that support dominoct kernels, but certainly in Debian the kernel available is Linux. So for many years we maintained a fork of Linux, this is the Xeno Linux that Ian was talking about, which had intrusive changes to the memory management system in truck handling, hardware access and so forth, and this became quite unsustainable, as you might have predicted. So nowadays, since around Linux 3.0, all or almost all of this necessary code is in the Linux upstream tree. So now the interface between the dominoct kernel and the hypervisor here is much broader than that provides to guest kernels, and also the interface between the tool stack and the dominoct kernel is relatively broad. This means that dominoct needs to be able to support all the facilities for direct access to guests needed by the management tools, and it also needs to cooperate with Xen to manage all the hardware, but because of the way Linux is developed and the fact that users would constantly need new versions of the dominoct kernel for all sorts of reasons not really related to Xen, like running on new hardware or fixing security bugs, trying to maintain our own stable branch of Linux is a non-starter. So instead, we have a kind of reasonably loose coupling here between the dominoct kernel and the other components of the Xen system. So we expect Xen and its tools to work with a range of dominoct kernels. On the other hand, this does mean that life is a bit... on the other hand, life is a little bit easier because we don't try to be bug compatible with bugs in old dominoct kernels, that is. If a user is running a Xen system, we expect them to be willing to run a kernel which has Xen-related bug fixes, even for bugs which were exposed by a new version of Xen well after the kernel was released upstream. So obviously we don't expect users to roll these kernels themselves. We aimed to push the necessary changes between mainstream Linux stable branches and out-to-distros that way, but that does mean that you can rely on users getting backported kernel bug fixes. So this tolerably loose coupling and all the upstreaming of the mainstream Linux, the code into mainstream Linux, means you can use the same kernel for your Xen dominoct as will boot on bare metal, and as Ian was saying, in Debian nowadays, there's no longer any special Xen kernels. The standard 686 Big Mem or AMD64 kernel is good to use as a Xen dominoct or as a guest as you like. So another important component of the traditional Xen system for which we're not upstream is QMU here. When we run unmodified guest operating systems, we need to provide them with something that looks like a PC. In particular, we need to provide something that looks like a screen, a keyboard, ID, a network controller, a simulation of the underlying bus hardware, like PCI and so forth. For a long time, the QMU project has been trying to provide this same thing in a different context, so it was an obvious choice for reuse. But when Xen first wanted to do something like this job, the QMU project was quite difficult to contribute to, and the code base itself made a lot of assumptions about the architecture of what the whole system was going to be and what the purpose of the QMU code was. So the Xen developers at the time took a copy of the QMU source code into the Xen tree and just hacked it up until it did what they wanted. So that, as you can imagine, has been a bit of a problem. So over the subsequent years, that version of QMU, which we now know upstream as QMU Xen traditional, got important performance improvements, important bug fixes, security fixes were made directly to the Xen version since upstream didn't have a security response process, and I think they still don't. We merged from upstream a couple of times, and we did try to upstream some or all of the Xen changes, but the number of factors made that meant that this wasn't entirely successful. Inertia and unwillingness to expand the scope of the QMU project on QMU's part were factors. Poor communications really didn't help, and we had a lack of effort and thought there were more important things to do, so ultimately that didn't really come to very much, at least not until a few years ago. But things have changed now. The QMU project has been utterly revolutionised over the past few years and is incredibly fast-moving and dynamic nowadays, and we've been aggressively upstreaming the changes necessary for Xen. So QMU Xen traditional is now in the deep freeze, but why do we need it at all? Well, one reason is the new QMU Xen based on upstream is not quite ready. The Xen 4.2 release will still use QMU Xen traditional by default, but we do expect the new upstream-based QMU Xen to be the default in Xen 4.3. But a big of a reason is that we promised old guests would continue to run. The emulated PC provided by modern QMU Xen is quite a different beast to that provided by QMU Xen traditional. It's got different device IDs on many of the devices, the emulated chipset has been upgraded, the new upstream QMU can't read the save files generated by QMU Xen traditional, so guests can't be saved, restored or migrated to the new one. Even worse, many guest operating systems react very poorly to a complete motherboard and chassis swap, which is what it would look like if you just upgraded to the new QMU and reboot it during a reboot. Even if they don't mind that in theory, in practice the new setup might expose rafts of guest bugs, which would be very difficult to work around, especially given that we're now much more closely coupled to the upstream QMU codebase. And while in principle it might be theoretically possible for upstream-based QMU to emulate the old one with sufficient if-defs and run-time flags, the resulting code would be very ugly, very intrusive, and not at all suitable for upstreaming. It would be totally unsuitable for long-term maintenance. So we as the upstream intend to main QMU Xen traditional indefinitely. That means that there are two versions of QMU in the Xen system, the old one and the new one. It's even worse, because of the speed of development to the QMU project and the lack of Xen-focused QMU committers, getting important features and changes into upstream can be rather slow. So if I just give an example, PCI passed through an important Xen feature for many years in QMU Xen traditional, took six to eight months to get into QMU upstream. So we as the Xen upstream provide a version of well upstream QMU, which is actually an upstream QMU with a lot of Xen-related changes. We have a policy of not committing anything into QMU Xen, which we think wouldn't be suitable for upstream. So in theory QMU Xen, as we call it, would be entirely suitable for use as a replacement for QMU. But in practice we don't expect people to want to use our slightly funny branch. For one reason, we don't do any non-Xen-related testing on it, and it might be based on a different version of QMU than the one you'd use for other purposes. So the net result is that to get full Xen functionality, a distro like Debian needs to include two additional copies of QMU, besides the normal QMU, and perhaps a different version for KVM as well. And one of the versions used by Xen is ancient. This is of course not the kind of thing that makes the Debian security team happy. Of course, it's by far from the only occurrence of this kind of thing in the Debian archive. And at least in this case, Debian can work with an upstream who still supports all the versions that Debian needs to ship. We as upstream do security and stability patches and compatibility fixes, even for the solidly frozen QMU Xen traditional. So given all that, it's good to see there are some efforts being made to help Debian manage code duplication and forking more effectively. For example, by searching the archive for similar code to fer it out copies that we didn't know about. But ultimately, in this case, the real work of doing support, particularly security support, for multiple versions is necessary. There's no other way to avoid breaking those old, perhaps hard to modify, guest operating systems. So here we can see one of the key ways that we do with the problem of interfacing compatibility. Just provide both versions of the software and use whichever one is appropriate somehow. And in principle, this is the same approach as done in a more formal systematic way with any seed library with a reasonably stable API. We're all familiar with Debian's well-established and mature approach to this, shipping perhaps two or three versions of any library in one release. I think Debian could really benefit from better tools, not just for spotting embedded copies and packages which are forks, but also for cross-porting changes, tracking which embedded copies came from which versions of upstream, which had which essential security fixes and all that kind of thing. So enough about all that. There's one other difficulty which shows up in this diagram. The Zen project upstream doesn't promise that you can run one version of the hypervisor with different versions of the tools. That is the user-spacesport management software will only work with a corresponding hypervisor, and that's this thick version line all the way down there. We don't break compatibility within a stable release, but in general there's no compatibility from one release to the next. The reason for this is that the management interface of the hypervisor is complicated and closely dependent on the features available in a particular Zen release. This means that both we want to be able to add new interfaces, such as new management hypercalls, and we want to be able to discard old ones. This whole situation leads to a similar problem to the one with Linux and Udev. If you're upgrading, you want to upgrade the tools on disk in the file system and the hypervisor in slash boot. If you do this in the naive way, there will be a time when the two versions on disk don't match and the system won't be able to work if it's rebooted. Luckily this doesn't make the system completely unbootable and impede you fixing it, but it might well be unable to run guests at all or the guests might break. It also makes it difficult just to try out the new version. If the new version doesn't work, you have to fish out some old packages from somewhere and install them. So the Debian Zen maintainers have arranged to allow co-installation of different versions of the Zen tools. Now our upstream build system doesn't support this particularly well and I applaud the efforts of the Zen maintainers in Debian to sort this out. So the Debian packaging for Zen edits all the paths to contain the Zen version number and there's wrappers for all of the Zen entry points which version of the hypervisor was booted and run the right set of binaries. So this compatibility rule seems quite restrictive and you might say, well, we should be more relaxed about it. But even if we upstream spent more effort on this area, it's not clear how much would help. The most obvious improved compatibility guarantee would be using the tools from Zen version N with the hypervisor from Zen version N plus one. So relaxing this line here on the diagram. But I wouldn't do very much good because firstly, distro like Debian which releases less often than Zen upstream will still have the problem because versions of Zen in two subsequent Debian releases would often differ by more than one Zen release. And even for a distro which releases less more often than Zen or if we offer the longer compatibility period, there'd still be a complicated upgrade path. You'd have to make sure to install and boot the new hypervisor first before upgrading the tools. So in practice, Zen will probably anyway have to use the capability to co-install different tools versions and use the appropriate one. There's one other big transition which doesn't show up so clearly in this diagram. So the old Zendy demon here which formed the core of many of the old Zen tool stacks is being phased out. Mostly this is because it's a terrible mess internally to the point where not only does nobody understand it, but it's probably not even possible to understand while remaining sane. Also it implements in a non-reusable way a good deal of the functionality wanted by other tool stacks. So one particular such tool stack is Zappi over there, you can see, which is a sophisticated API forming the core of what's known as XCP, the Zen Cloud platform, which is the free software release of Citrix Zensource's Zen server product. And now in Debian as Project Kronos. Zappi's used by orchestration layers such as OpenStack and CloudStack. And it's going to be shipped in Weezy. Another intended user of... This isn't the wrong place. So we're replacing Zendy with a C library known as LibZenLight or LibXL. The command line tool which is used by many Zen users to manage domains XM is being replaced by a mostly compatible rewrite called XL. And the intent here you see is that users such as Debian's ZenTools package will find that XL and XM are suitably compatible. So this is coming along nicely in the upstream tree. We've got a preview of it in Zen 4.1 which is going to be in Weezy. And in Zen 4.2 LibXL will have an API which we intend to support in the future in a backwards compatible way. Sadly, ABI compatibility is still beyond us. So users of the Debian's ZenTools package and its utilities like ZenCreativeImage should find that the generated guest config files are all compatible with the new XL utility. And you can use XL pretty much like XM. So your ad hoc high-level machinery shouldn't need too much adjustment if any at all. And we spent considerable effort trying to figure out what ZenD does in reproducing its behaviour so far as it's comprehensible and reasonable. The results aren't perfect from a compatibility point of view but we hope that in any particular system the changes need to use XL rather than XL will be minor or hopefully completely absent. One exception to this is the ZenD Managed Domain's facility which you invoke by saying XM new rather than XM create. We don't think many Debian users are using this and need many users at all. The functionality like this is better provided for in other ways. The most obvious is the init script-based automatic starting setup which is shipped in Debian for some time. And if that's not sufficiently sophisticated we suggest using a more sophisticated management layer such as Zappi or OpenStack. So if you're a ZenD and XM user we'd really like to encourage you to take a look at the new XL tool stack in Weezy. If you use ZenD directly rather than via XM or use XM in some way which you think might be unusual you should check right now that LibXL and XL meet your needs. ZenD is pretty much dead now as far as development goes and we're probably going to remove it in Zen 4.3 or maybe 4.4 probably therefore it won't be in Weezy plus 1. So if there's important features missing from LibXL and XL we need to know about it really soon. So one of the other users of LibXL intended is LibVert which is a bit of a more complicated problem. I know LibVert isn't very big in Debian more of a Red Hat thing but I will talk about it here briefly. I'm not much of an expert in it so if anyone is do speak up. Anyway our intent is that the LibVert driver the ZenLibVert driver will be linked against LibXL so the LibVert demon itself will be linked transitively against a particular Zen version and we may need to provide multiple versions of that too. So to try to make all of this somewhat less painful we've been working quite hard to ensure that at least in the 4.2's release we've got API compatibility in LibXL and indeed the command line compatibility with XM. So I hope I've given a flavour of some of the difficulties we face where the upstream for quite a mature and sophisticated system and so we've had to take some different approaches for some of the interfaces and some of the layers. So if anybody's got any suggestions for how either Debian or upstream can do things better and make our or other people's lives easier please do speak up. So any questions? Or you're all brains imploded by my diagram? Anyone on IRC? OK, well thank you very much.


THE DIARY OF A MADMAN AND OTHER STORIES by Nikolai Gogol read by Nicholas Bolton for Naxos audiobooks Petersburg Tales Nefsky Prospect There is nothing finer than Nefsky Prospect, not in Petersburg, anyway. It is the making of the city. What splendour does it lack, that fairest of our city thoroughfares? I know that no one among the poor clerks that live there would exchange Nefsky Prospect for all the blessings of the world. Not only the young man of twenty-five summers with a fine moustache and a splendidly cut coat, but even the veteran with white hairs sprouting on his chin and a head as smooth as a silver dish is enthusiastic over Nefsky Prospect. And the ladies. Nefsky Prospect is even more attractive to the ladies, and indeed to whom is it not attractive? As soon as you step into Nefsky Prospect you are in an atmosphere of gaiety. Though you may have some necessary and urgent work to do, yet as soon as you are there you forget all about business. This is the one place where people put in an appearance without necessity, without being driven there by the needs and commercial interests that swallow up all Petersburg. A man met on Nefsky Prospect seems less of an egoist than on Morskaya, Gorchovaya, Lityeinaya, Mishchanskaya and other streets, where covetousness, self-interest and need are apparent in all those walking by or flying past in carriages and droshkies. Nefsky Prospect is the general channel of communication in Petersburg. The man who lives on the Petersburg, or Vyborgside, who hasn't seen his friend at Piesky or at the Moscow Gate for years, may reckon with certainty on meeting him in Nefsky Prospect. No directory list at an address inquiry office gives such accurate information as Nefsky Prospect. All-powerful Nefsky Prospect sold place of entertainment for the poor man in Petersburg. How cleanly swept are its pavements, and my God, how many feet leave their traces on it. The clumsy, dirty boots of the discharged soldier, under whose weight the very granite seems to crack, and the miniature, ethereal little shoes of the young lady, who turns her head towards the glittering shop windows as the sunflower to the sun, and the clanking sabre of the hopeful lieutenant which marks a sharp scratch along it. All print the scars of strength or weakness on it. What rapid transformation scenes pass over it in a single day? What changes it goes through between one dawn and the next?


Happy Monday, everybody. Hopefully, everybody had a great weekend. And happy Father's Day. Hopefully, everyone had a great Father's Day. This is for all my daddies out there. Good to see you, Mark. Good to see you, Nick. Dave, Mary, Mike, Mark, everybody. All right. So it is Monday, new week. Little cloudy here in New York, so I think everybody is gonna be ready to get back into trading because a lot of kids are starting. High school is pretty much over for a lot of kids here in the Northeast area. I know final start, so summer is only, what, a couple of days away now, I think? Oh, is it the 22nd? So we're gonna have a, I think we're gonna have a really fun summer. And listen, if today's any different than last week's Monday, I mean, last Monday, we literally just paid for itself. So as it was going on this morning, there's really not that much out there. But there are a couple of stocks. We're gonna check them out. But just give you a little heads up on upcoming events. Just keep in mind, traders talks coming up. Classes do start this week. And don't forget the trading summit that starts September 10th to September 12th here at Cybertrain University in New York. So hopefully you look to see you guys there.  The stock has been a great, great runner this morning. Had gorgeous Faustal flags. You're having great orders everywhere with that stock right there. And we're gonna come back and check it out. But before we do that, let's start off what happened on Friday. All right, let's see what some of you missed and go from there. First, let's start off with the MARX trade right there. That stock, I don't know what happened. It just came from nowhere going into the close. You could see at 230, thing just went from 610 all the way to 680. Great, great mover. Had a really quick pop early. Great Faustal flags right there, right after about 230. And then kind of like, did a little couple of nasty shakes in there. But not that, not terrible, but I know some of you guys did pretty well in there. The other big mover, which is shockingly, is LK, which is actually going into this morning's watch list too. But LK, I call this mini Starbucks right here. It's a copy Starbucks. It's a Chinese company right there that basically have a lot of stores out there. But stock just went public. We're from 25, tanked at 15. Shockingly, it's already at 19.  You could see, yes, on Friday. And she's kind of picking up that momentum. She closed right around the 1920. She almost at 1980 this morning in pre-market. So that one's going back on the watch list. Another one that's also going on the watch list this morning that is coming from Friday is Chewy. Now, if you have any kids, I mean kids, I'm sorry.  I mean, it's like a kid, right? So companies just went public on Friday. Chewy is a really good online store for buying pet food and stuff like that when public's actually doing pretty well. Scott's Momentum took a big, big hit on Friday. It opened up just a little too high in tank. Let me just fix the timeframe here so you can see what I'm talking about. It started right around 38. Shopped to 41, tanked to 34. Now, this is an IPO. Now, you guys know, gotta be careful with IPOs. You gotta be a little bit more of an advanced trader. Can't be trading something that really is not in your league because these things will really crush you. Remember, it's all about risk, not the reward. The money comes later. It's all about was the question you get in. And then we had this last one right here, the ARQL. A pre-market gapped up was a good short after the market opened up. So some of you guys did pretty well. So that's what you guys missed on Friday. Now let's talk about what's going on this morning. Now we got to Chewy on there. I told you about Chewy. And that stock had a really, really nice move. She's gapping up a little bit this morning. Now, some of the people that were asking me over the weekend, they say, hey, I heard Chewy in public. You think it's a good investment this net? Listen, I don't know what a good investment is until probably maybe three, four weeks from now and let the smoke clear. We see a lot of these IPOs. And shockingly, there's been a lot of them that came out this year. A lot more than we have seen in a while. A lot of companies been sitting back for a long time. But, you know, they've been fun and some of them are working out. Some of them haven't. So you've got to be just be very careful what you're putting your money in. And you've got to be an investor. You've got to let the smoke clear. Another one that's on that watch list, we talked about the CTRV. Let me get back to that one. So that one is gapping up really, really nicely. It's up about almost 70%, 68 to be exact. Stock took a huge hit. If you look at the long-term trade of last year, this thing was at $180. And when you look at it where it is today, you're like, wow, my God, feel bad for the people that own it back then. Well, listen, I don't know. We traded a few times already in the past. If you go back to your journals, which by the way is very, very critical that you do your journals every day. I don't know how much more we have to stress it to you guys, but how are you going to learn from the mistakes if you don't check your journals? We're going to be covering that a lot in class. And actually on the new courses, the fast track courses that we're going to be doing here at Cybertrain University is very important to you guys do that homework. But anyway, that stock, we traded it. We did pretty well. It backed off. I felt like it was a little bit more of a short squeeze. You can see it right here. Last, when we traded it back here, wasn't too long ago. When it went from like eight to almost like 20, something like that. Go back to journals, check it out, because we did trade it. Another one, you know, I keep hearing about this.  So, you know, you're hearing all the cryptocurrency, this and that. It was such a great story when it first came out. And, you know, now they all took hits. You know, it's up this morning. I would keep a close eye on it. Some people think it's still, you know, Bitcoin's going to 100,000. Some people say it's going to a million. You know, it's hovering at 10. You know, listen, there's a lot more stocks out there that we've traded here in the market that you can make a lot less, more money with a lot less risk. At least you have more control.  But listen, just be very careful of that. I don't know too much about it. And it's just, this gives you so much less risk, more reward. But if you want to see, you want to throw some poop on the wall and see if it sticks, just don't do a lot of it. Cause I know some people got crushed in it. C-A-L-A is another one that's popping up on our watch list.  I thought this will look pretty good this morning. It was gapped up pretty nice. It looked like it backed off. You know what? I'm going to scratch her out. And then the LK. I'm going to put that book on my watch list again. So it looks like a lot of stocks that, remember what we always taught you that to be a good swing trader and investor, you got to be a good day trader. And if you notice, some of these stocks that we've been day trading made now they became more of a swing trade, like maybe LK. You know, this is an example like I'm basically telling you. You saw the stock open up at 25. You bought at 15. You know, if you really liked it and worked out pretty well and held pretty strong, you probably, and you wanted to own as a swing trader, you probably should have had around $17, $18. So you're looking pretty good right here. Just like Uber, you know. I told you I'm swing trading that one. Let me put the typed in wrong window. You know, Uber gapped up pretty big. Looks like it's, you know, building a nice little Fausta flag. If you were here, everyone should probably had a, got it where I got it right around 39. There, I got like 39.50. So let me shop the 45. So, I mean, there are good swing trades out there, you gotta know what's happening over the course of the day. You wanna get a good price. All right, any other questions, guys? That's any questions that, any stocks I missed that I did not bring up? Any other questions?  Facebook is developing a coin. And you know what? If you know the whole story about why they're doing it, it's all about because they have the users. They're basically trying to run a community, you know, their own, you know, currency within their own company, which honestly, when you really think about it, that's what PayPal does, right? Isn't that what PayPal does? It's the same thing. Now they're just taking it to a different level. You buy with PayPal money, you know, there it is, different as PayPal is obviously related to the dollar. But now they've got their own community. They wanna make their own value and that's what they wanna do. But just, but listen, you know, let that stuff keep coming out because that just makes opportunities for us when it comes to trading. Just gotta trade the market. Who cares? Get away from the banks. Like I said, Jerry, don't take a personal, just look at it as an opportunity. That's why you have to look at it. Michael says the S-O-L-Y just got crushed. Yeah, well, it looks like I got crushed, but look, I just came back. So I don't know what that is all about. That must have been just the crazy print right there. Yeah, just a matter of time. You know, like I said, Jerry, listen, everybody's gonna try to jump on this bandwagon, but I mean, I even heard Jaguar, the car company was looking into it. So money's gonna be, I mean, if everybody started doing money's gonna be a big difference. But listen, that's a story itself. At the end of the day, what are we doing here? We here to capitalize on it, so let's trade on it. So anyway, guys, not a really big list here on a Monday. It's perfectly normal to be like that on a Monday, but we saw what happened, the market opened up. We only need one to make a really good day's pay. The array is one I forgot. Let me just bring this up to array, because I wanna kinda just talk about it. Stock was a buyout right here. We've been trading it the last couple of days, and if you caught on to it and you held on to it, it did pretty well. So for all those people that did pretty well on array, congratulations, you guys did great on that one. All right, so anyway, a lot of events going on this week, and just keep in mind, everybody, that with the classes going on this week, which is very important, you gotta be in class. Trading is not a full-time job. It's a part-time job.  It doesn't mean you log out, you wanna keep the text, so you know what happened, what you missed, but make sure you're in those classes because you gotta learn before you can earn, and let's all welcome all our new members that are starting on the first day here on Monday, which is basically what we do. All we could tell you guys is make sure you talk to Education Advisor, watch those sample videos that we gave you, so you know exactly what the code words that we use here in the room, and just look, listen, and learn. Because remember, I know everybody wants to trade, doesn't mean you should, and all you're gonna know it is seeing if all the people make money doing it. All right, so go look, everyone, happy trading, and we'll see you back in the afternoon. Let's go make some money with the market opened, right? Good luck, everyone.


country as ancient as it is modern, moving as history moves across the threshold of the past. For 5,000 years, wave after wave of the peoples of Asia have streamed across India's borders. Conquerors, immigrants, soldiers, holy men and scholars, pilgrims of many creeds and of many races have woven their customs, traditions and beliefs into a continuous and intricate pattern of civilization and of beauty. They have farmed and they have fought. They have loved and they have prayed. They have fought and they have played. They have built monuments and palaces and temples and cities. They have written poetry and they have sung songs for 5,000 years and they have moved as history moves into the contemporary world of today. Delhi has been called the city of seven capitals, the seat of power of seven ancient dynasties. New Delhi is now the seat of power of India's democratic republic. In February 1962, the world's largest democracy went to the polls for the third time in the history of the 12-year-old republic. Over 100 million voters cast their ballots in and for the democratic process, the process of free elections. March the 12th, 1962. A new session of parliament opens. Dr. Rajendra Prasad once more takes his place. The first democratically elected successor to India's past heads of state, India's first president. Also on this day, March the 12th, 1962, India, her people, and Prime Minister Jawaharlal Nehru expect a visitant. From a sister democracy 9,000 miles across oceans and continents, accompanied by the American ambassador Kenneth Galbraith, comes Mrs. Jacqueline Kennedy, wife of the 35th president of the United States and her sister, invited guests of the Prime Minister and of his daughter. Mrs. John F. Kennedy, a lover of the arts and the mother of two young children, brings to the people of India the greetings of the people of her own country, also a people of varied backgrounds and customs, of many faiths and races and beliefs. The United States Embassy in the center of New Delhi, combining modern architectural techniques and ancient Indian motifs, reflects the new world and the old, and the longstanding friendship between our countries, between the United States and India. Mrs. Kennedy has a special interest in the culture and traditions, old and new, of the world she is about to enter. This is India, 1962, kings and emperors and explorers of five centuries ago, new and treasured the silk of Banaras. Today, the ancient art of weaving joins the 20th century in a procession of silks, brocades and muslins for fashions that go around the world. The continuity of artistic tradition moves in an unbroken line from the variety and richness of the past to the living art of today. Art reaches across many barriers, makes many friends. In her own land, Jacqueline Kennedy has given a new place of importance to the American artist. Mrs. Kennedy finds in the young Indian artists who have come to meet her a welcome close to her heart. Mrs. Gandhi, my friends, it gives me great pleasure to present to you today the children's art carnival, a present to the children of India. I've often noticed the art of children is the same, the world over and so of course is our feeling for children. I think it is good in a world where there's quite enough to divide people that we should cherish a language and an emotion that unite us all. Thank you. It's from the Prime Minister's gardens in the center of modern New Delhi is measured not only in air miles to Jaipur, capital of the state of Rajasthan. It is also measured in years, taking the American visitor on the first step of her journey into India's past, to the land of the Rajputs, of Waria and Prince. Elephants and emperors have always been friends. The rocky road up the hill to the Umbair palace was once traveled on the lumbering backs of elephants by Raja Man Singh in the first and his retinue of court followers 350 years ago. Alexander the Great marched his armies out of India with 200 elephants. Tamur of Samarkand with nearly a thousand, a long time ago. Doubt from the terrace of the palace his fathers had built and saw the pleasant planes below. He decided it was time to come out of the fortified hills. In 1728 he built Jaipur, the pink city, one of the first planned cities of its day. Tumas of discontent if there were any would allow to reach this monarch's ears in the courtyards of the city palace or the corridors of the Hawa Mahal, the palace of the winds. Maharaja Sawaj I Singh was a scientist. He preferred to think about the shape of the earth, the universe and the stars. Mrs. Kennedy's journey continues back into time. Another city, another age, another monument. The year 1569. The city abandoned, the emperor long since gone, the monument remains. Marble and mother of pearl to honor the tomb of a saint. In Fatipur Sikri the saint Salim Chisti prophesied that the great emperor would have the son he dearly wanted. And so the story is told, Akbar the Great did have a son and his son had a son. The monuments of India's historical past do not however belong to the past. They belong to each new day and to the people who live it. To priests and to scholar, merchant and villager, to neighbor, to stranger, to friend. This is the monument the son of the son of the great Akbar built. A garden of cypress, a pool of still water and a dome of pure marble. Behind a pierced marble screen, emperor Shah Jahan entombed the body of his dead wife. Three centuries have gone by year by year, hour by hour. The sky of India touching to immortality the tomb of the emperor's work, the Taj Mahal. An emperor's monument to love and to death. Benares, a people's monument as ancient as the sacred Ganges that flows along its bank. A people's monument to the life of India itself. To the holy city of temples and of minarets. To the city of the sacred river and to nearby Sarnath. Where Lord Buddha preached his first sermon more than 2,000 years ago. Come millions of India's pilgrims, come India's friends. Immense and sprawling life of Benares is a reminder that the people of India form one sixth of the peoples of the world. Fittest in time and in space from the start of the American journey into India. The medieval city of Udaipur with the sunlight still falling on its ancient walls. Moving towards tomorrow, the white city is already a seat of learning. And India's five-year plan will bring further means of economic growth and modernization to its people. A window on Udaipur's lake Pachola opens. And as in many other parts of India, Mrs. Kennedy once more looks out on a changing day. On a day of legendary beauty. And its people, and this made my visit possible. At the end of every day, I could not decide which day was the best. Each day brought new experiences, new friends, and a new welcome. It was a wonderful surprise to meet our own American pioneers of the peace corps, so many miles from home. Going the unknown ways in my husband's words requires many gifts of character and a confident vision of the future. I believe that both the people in India and we in our own country share this vision. For the gentle man who went his way softly, no marble or ivory monument is needed. Strong in spirit as he was frail in body, Mahatma Gandhi's memorial is in the hearts of his people and in the thoughts of those everywhere who seek to maintain freedom and to secure peace. The unity of God, the oneness of the universe, the brotherhood of man, the age-old articles of faith of the people of Islam have begun to acquire new meaning today in the life of the young nation of Pakistan, a national homeland for the Muslim people. In heritages of a tradition and a culture whose roots go deep into the ancient past, Pakistanis look to their faith to guide their nation's future. The future of any nation, young or old, lies with their children.  Among the gifts she has brought from the United States to Jinnah Hospital, not the least is Mrs. Kennedy's own delight in making a new young friend. Never far from Pakistan's hope for the future are her memories of the past. Through the ancient streets of Peshawar gateway to Pakistan's northwest frontier, Mrs. Kennedy follows the route history followed. Kiseh Khani, the bizarre the storytellers, for centuries a meeting place of soldier and tribesmen of merchant and scholar on their way down a long stretch of perilous road from the mountain reaches of the Khyber Pass. Descendants of the tribesmen of old still guard the bleak approaches to the pass. The tribal Malik still welcome friends in the traditional way with the traditional gifts. The Khyber Rifles, historical defenders of the fertile valley of the Indus, of the land below the mountains. Century after century, friend and invader travel this road. Armies and caravans bound for the riches of the great subcontinent of Asia. Alexander of Macedonia, Genghis Khan, Timur of Samarkand, swept down across these mountains. Sun down at the governor's house in Peshawar. The drums of the Khyber tribesmen no longer sound for battle but revive for the American visitor in ancient ritual. The Kutaks dance. Celebrating a young tradition in the ancient city of Lahore. Pakistani national horse and cattle show. President Ayub's gift to Mrs. Kennedy. Sadah, descendant of an Ascot winner, traces his ancestry back to the fame stables of the Aga Khan. Cymbal of the warmth of the welcome the visitor from America received wherever she went. From the distant plains of Texas and the subways of New York are brought to Bashir, the camel driver, the good wishes of many Americans and the greetings of Mrs. Kennedy and her sister. Bashir has his own contribution to make to Mrs. Kennedy's visit to Pakistan. In the search for identity, for purpose and for a place in the 20th century, Pakistan has not forgotten man's need to dream. Three years ago, the Shalimar gardens brought repose to a Mughal emperor. Today, the gardens offer repose and delight to anyone who seeks it. I must say, I'm profoundly impressed by the reverence which you and Pakistan have for your art and for your culture and for the use which you make of it now. My own countrymen, too, have applied in their traditions. So I think as I stand in these gardens which were built long before my country was born, that that's one more thing that binds us together and which always will. I had always heard of Pakistan's proverbial hospitality and it was even more than I had expected. I hope that with my husband I will be able to return again soon to this vital and beautiful country.