Now if you guys missed out on getting Merlin's Cloak in Hogwarts Legacy, while you do now have another chance today I will explain. Oh, how's it going guys? My name's DPJ and if you're doing a video or living a life that really helps out and if you like what you see and want to see more, be sure to subscribe. Okay so Merlin's Cloak looks absolutely incredible, by far the best cloak in the game, no one's going to argue with that, but there's only like limited times you can get this thing the first time, you had to watch them stream for a certain while, they've stopped that now but they're actually giving you guys one more chance to do this, so you want to do this while you have this chance. They tweeted this out which you can see on the screen now, this is by one of the games Avalanche by the way, another chance for the exclusive Merlin's Cloak Twitch Drop. Join Avalanche software on Twitch on Friday 24th February at 2pm PST, 5pm EST and I'll decelerate this in the world guys now, I'll show you on screen just to see if you guys ain't from America as I ain't so you could get a little confused at this. We'll be live for a few hours starting our studio playthrough of Hogwarts Legacy and a Twitch link to where they're going to be streaming this, you'll find also link down below. Now there are a few other things you need to know about actually getting this thing and that is your Twitch account, you have to have a Twitch account, it needs to be linked to your Warner Brothers games account, both are linked down below, these must be linked together, then guys you need to use the Twitch Loot Drop page or the Drops and Rewards page which I'll also link down below and you need to keep an eye on this while you're watching that stream because you will need to claim the rewards too, again that will be linked down below. Now when you actually have claimed the reward when you've watched the stream for a certain amount of time and you have that Merlin's Cloak appear in your Twitch and Loot Drops and Rewards imagery screen and you've claimed it there, you still need to do a little process, firstly make sure your Warner Brothers games account is linked to your playing game attack profile, whether that's Steam, whether that's PlayStation, whether that Xbox, make sure it's all linked together. Then guys you need to use this page right here, if you've got to Google and write Hogwarts Legacy, Twitch Drops it'll pop up, I'll link it in the video description too for you guys but this is the page you need to go to, then all you need to do is follow the steps it states on screen, so you'll need to sign into your Warner Brothers games account and then connect your Twitch, this may already be done for you, you'll then need to click tune in which you're seeing here but don't worry about that if you've already watched the stream for that certain amount of time you'll be fine here, again checking your Twitch inventory to track the progress of your claim, that's the page I already linked so you'll find there and then guys you'll just simply claim your rewards and it really is as simple as that guys and then you'll get Merlin's Cloak in-game, a lot of people are confused about this, I myself was as well and this solved it for me, so if you've watched the stream, you've linked all your accounts, you've claimed the reward but it ain't appearing in your game, use this website and you should be good and there we have it guys but yes I believe this is the last chance of you being able to get Merlin's Cloak so you want to do it while you can, guys if you enjoyed the video leaving a like really helps out if you like what you see and want to see more be sure to subscribe and hopefully guys I will see you on that next one


Welcome to the Network Engineering video blog. I am your host, Michael Crane. In today's video, we are going to create a single parent application that holds our TCP socket client and our SSH.NET client that we created in videos number 66 and number 69. We will still be using Visual Basic 2017, but instead of creating a Windows Form app, we are going to create a Windows Presentation Foundation WPF application. I'm referencing Microsoft's Visual Studio 2017 WPF overview and walk through my first WPF desktop application to get me started. I'll put the link to both articles in the video's description below. To keep this video from being three hours long, I will only cover the code related to our application. However, WPF creates several default files. If you're not familiar with WPF, I highly recommend reading the WPF overview and walk through. If you are familiar coding using Windows Forms, but new to WPF, I recommend checking out the Windows Forms Controls and equivalent WPF Controls page as well. That will really help you transition to WPF. The link for it is below as well. Mogwai is the name of the application we are creating today. Mogwai is an acronym for Muxall Automation GUI. You can download Mogwai code from the Muxall GitHub repo. If you are curious what the goals are for Mogwai, check out the readme file in the repo. The link to the repo is in the video's description below too. OK, so that's about it for the intro. Let's get started. OK, so to create a WPF app is pretty easy. Select new file, new project, and WPF app. But before you click on OK, make sure to give it a name because it is a pain to change it later on. So we're just going to call this test demo and click on OK. OK, and as you can see it will create several default files for your application. And I'm not going to go through all these with you. You can go through the WPF overview and the walkthrough, and they'll give you a lot more information about these guys. But the one we're mainly interested in is this main window, XAML. And this is going to be your GUI code. And if you're familiar with Windows Forms, you know it has a designer window and then the implementation code in another file. And this is kind of the same thing. And they call this code that's in this .vb file. They call this the code behind code in Microsoft. Some people call it implementation code. If you've ever done any HTML programming, this would be the equivalent of your JavaScript behind your... This would be like your HTML file, the XAML file, and the JavaScript would be all in this. And the code behind, OK? Or your implementation. All right. One of the things you'll notice is there is no multiple document interface for this window right here. But this main window is going to be our parent window. And another thing you're going to notice is it's not called a form. It's called a window. And if you go to this Windows Form Controls and Equivalent, you can kind of look at what the... If you're familiar with programming and using Windows Forms, you'll be able to find the WPF equivalent because they've changed some of the names and it can be a little confusing. You can see it went from form being a form to a window, all right? And it says window does not support child windows. OK, so WPF doesn't support child windows. Like when you're using Windows Forms, you have a parent, a multiple doc MDI, and you have children forms inside the parent. Well, WPF considers the window root. So you can't add to root... You can't have a root window controlling another root window. You can spawn another root window, but that's something different. So if you go up here, right-click on this, I add new item, and it's like filter on WPF. So this is your root window, so you can add pages. You can also add user controls and this other stuff. So we're not going to use page. We're going to be adding user controls later. So that's going to be our children are going to be the user controls. And we'll get to that here in a second. So anyway, this main window is going to be our parent window. And let's just take a look at the XML real quick. Well, let's look at our other app. Okay, so these are the items you're going to want to change. You want to change the title to whatever you want to call it. I called mine Muxall Automation GUI. And then we're going to add these... This is a menu. So when you...  I'll show you. This is so when you right-click on the background, you get this menu right here. All right. And you can see it lists these four items. And these are going to be the callback functions that's in the code behind. Right. And another thing, when you create this... Your first app is going to default to a layout of grid. And I changed mine to canvas. You might be able to get away using grid, but I think some of the functions that are at least in mine aren't going to work properly using grid. Just for the layout, canvas is more of a... You tell it exactly where you want it. And grids use like framing to get everything straight. Okay. I probably didn't explain that real well. You can go look up a grid means and the different layouts. There's a bunch of different ones. Okay. So when you change the grid to canvas, you want to give it a name. I called mine canvas main. So I know what it is and what I'm doing the code behind. And you want to add these list box items. And you can do this from this properties window right here. Let me see if I can remember how to do it. So if you go to properties and... If you just type in menu right here, it's a nice little search for finding items in this very long properties list. And then click on this context menu. And I think it's under item way down here. Items. Yeah. So if you click on this collection, you can start adding these buttons. And this will get you some of the basic setup or the basic layout of it. Right. You can come back. It'll populate all this in there for you, which is real nice. You don't have to remember how to code that. And then you just have to add what events you want. Okay. All right. And that's about it for this main window XAML. Or I'm just going to call it XML. I'm saying that A is kind of a tongue twister. All right. Let's go take a look at the code behind real quick. And this is the implementation. As you can see this, these menu items just call these different subroutines. There's four of them. And so we've got the add router, add switch, add test it, and add link. That's all that's in here. And we'll just look at one of these. You can go download this code from the, from the GitHub repository and take a look at the others if you want. They're all kind of identical. Or they're close to identical. You can download the code and look at the differences. But except for this right here, this doesn't really work. I was just playing around with it. So that'll be, we'll fix that in another video. But we're just going to, let's just look at this add router real quick. Okay. So we're going to come over here. And this is a class, this router node right here. So what it's going to do is it's going to say, I'm going to, I'm just going to create a new instance of class router node. Right. And I am going to add it to my canvas as a child. So it's just canvas dot children add router. Right. And then I just put in this little debug statement when I was testing these things. And, and the switch is basically the same. So let's, like I said, the, all this is the same. And actually most of the, the classes are the same. So let's go. We'll just start from the top. We'll look at the Cisco router node. And it just has a little picture of a router right there that he see where I defined that at. Oh, here it is. Here's where I defined it. That's the image source. We'll just look at the canvas right here. I changed it from grid to canvas again. I named my canvas UC canvas. Which stands for user control canvas. I gave it a default height and width. And, and then I, I'm creating a rectangle. I gave it a name. It's called a user control node. And I gave it a default height and width. And, and then it's got these mouse down and mouse move events. And that's so you can drag it around. And this render transform just says the, this, or we got a measure from the left-hand corner, right-hand corner. Since it's a circle, or at least the picture is a circle. We want to do it right from the middle. Yeah. So I'm just fill, I'm just using this rectangle fill. And I put a picture of that router in there. And here's another menu. So when you click on the route, right-click on the router, you get these commands, right? The subroutines it calls on the mouse up event. All right. Now we can go look at the code behind on it. Okay. So here's our, our constructor or here's our copy constructor. And this looks like it's got an error in it. And here's a send command. And this is kind of what we're looking for. The, the edit node and the delete node don't have anything, any implementation codes in there. So we're not going to look at those, but we'll look at this real quick. This send command going to create a new instance of the Cisco client class, right? I'm just going to call it router. And, and then it's going to show it. And this is interesting. So this Cisco client right here is the form that we created in the previous video. I had to recreate. I didn't have to, but I recreated the Cisco client. And the reason why is I was trying to add the windows form application and, and it's, it's doable. I can go in here and say add a new item and you can, you can add a windows form if you want to, right? I didn't want to create a windows form app in this. I wanted to copy the one I had already created, right? So I was, I was trying to do new and existing item. And I went looking around, trying to import that windows form into my new WPF app. And, and it just wasn't going to do it. Not cleanly anyway. And I said, okay, well that's fine. I mean, so here's the code behind for the Cisco client class, right? And, and as you can see, it's exactly that's exactly what we created in the previous video. So the only thing I really had to create was this client GUI. And as you know, this is, it's just a simple drag and drop all these text boxes and buttons on there. So just recreated the GUI and you can see, you can see that it's pretty ugly, right? Cause I just, I just dragged all this stuff on there and just moved it around to where I wanted it. And I didn't make anything real pretty. But it works, right? And I also even left a grid, right? So I didn't bother to change it to canvas. So, and that worked pretty good. So, I mean, this took a little bit to create. And I could show you, but it would make this video way too long. So we're doing add router, right? Click on, do a send command. And here's our GUI, right? And this is a separate, separate window. If this is a true MDI document, you would not be able to move this child window outside of this parent window, but this is a separate root window. So anyway, yeah, I had to do that for both the Cisco client and the Xena to set. Where'd that, where'd that go? Oh yeah, here it is, Xena client right down here. And that's the, the TCP socket that we did in video 66. The Cisco client we coded in Windows Forms, video 69. And then I basically just recreated the GUIs in WPF and then copied and pasted the code behind into this XAML.VB file. And of course, you know, I had to change some of the names around, but it didn't take very long. It was actually pretty easy. So, and now everything's in WPF. I don't have any Windows Forms and the old Windows Forms code to deal with, right? Okay, so to create these child classes like this Cisco router node class or the switch node classes, it's really pretty easy. You just go up here, highlight the project name, right click on it, say add a new item.  Make sure to give it a name of what you want and click on add. We can do that in our other one over here. So we'll just say, add new item. And I'm not sure why it doesn't default with just WPF as a filter, but anyway. So use control. We'll just leave the name default say add. And this is what it creates for you. Okay, so we added the Cisco router node class and it's also, it's a user control. It's just a canvas. It has a rectangle on it with a picture of router in it and a menu. And when you right click on the router, it instantiates like if you do a right click and do a send command. It instantiates an instance of the Cisco client that we created. All right, well, I hope that makes sense. Okay, so one of the things I wanted to show you was this code behind for moving like the rectangle around, okay? And the reason why is I could not find a decent example of how to do this anywhere. And I was beating my head trying to figure out how to make this work. I saw, I literally saw examples of people doing this, doing the same kind of thing with like two pages of code. And after some poking around and playing around and as you can see doing some debugging, I finally got it down to a couple subroutines. And they're event-driven, so when you get the mouse button event down, it populates this point origin variable with the X and Y location of the router. And then this translation point is a translate transform object. It's measuring how far away we are from these origin points. This is when you do the left click down it. It records this information, right? So then soon you start moving the mouse, you start getting mouse events where you're actually moving it. And then you can record the mouse location on the canvas. And you can see this is the user control canvas, not the parent canvas. So this is saying, okay, the mouse is moving. So it's going to get the location of where the mouse is moving. It's going to check to see if the left mouse button is pressed. So this one is, okay, I pressed on it and now the mouse is moving and it's double checking, okay, is the left mouse button still pressed? In other words, have you left clicked on it and are dragging it, right? And it's going to say, okay, I'm going to translate point X to mouse location minus the point origin dot X and translate point Y to mouse location point Y minus the point origin. And then I'm going to actually move it. So it's going to say, okay, move UC node, render the transformer, which means move it to the translation points that we just assigned right here, the X and Y points. And that's how you make it move around. This right here would probably be a good video on its own, just a little one-minute video on how to do a drag and drop with a control in WPF because this literally took me hours to figure out how to make it work. And why Microsoft doesn't have a built-in function for this is a head scratcher. If someone knows, I wish they would let me know why this isn't just something that's a library in WPF. Anyway, I digress. Okay, so it was a Cisco router node. I'm going to go ahead and show you a couple of other ones real quick. So we're back at our main. There's our main window. And okay, so we did Cisco. And that was a Cisco router. Now the Cisco switch node is, as you're going to see, is going to be pretty much identical. It's a rectangle. It has the exact same commands. It's got a different image, of course. And the code behind is pretty much identical, even has the same error in it. And this code is identical, too. So you can see we're getting a lot of duplication of code here. This can all be cleaned up in the future, but for right now, it doesn't really matter. A lot of this stuff will probably change. Now, we can just consolidate all this code into one class and then pull it in as we need it in our different nodes, right? But we'll do that later. Okay, so that was the switch node. And it actually, I think it calls up. Yeah, so it does call the switch. But it's still a Cisco client with a send command. So it's identical because they're both using SSH into the nodes. We can look at it real quick if you want. So we can right-click, say, add switch. And it gives us the box or the switch. And you just do the send command. And as you can see, it's the exact same Cisco client. And the only one that's going to be different, let's look at the test set real quick. So I don't really have a nice little picture for the Zena, so I just use their logo. Right-click on it, send command. And as you can see, the Zena client's a little different because it's not using SSH, right? Okay, so that was a switch. You can see it's identical. And let's take a look at the Zena real quick. But as you can see, as you'll see, it's identical. That's a Cisco client. And I did recreate this GUI as well. But it was very quick. You know, I just, like I said, I just dragged all this stuff in there and dropped it in there and made it look pretty much identical to what it was in Windows Forms. And then I just copied and pasted the code behind right from the code we did in Windows in video number 66. Oh, here, the Zena test node. Yeah, you'll see this is all identical. Same commands, different picture. Oh, I did add a drop shadow effect. And there's probably some other stuff in here. I'm forgetting, yeah, I added a favicon.   And if you Google that, you'll know what I'm talking about.  And yeah, you can add that little icon guy right here. All right, well, I hope all this made sense and I'm not going too fast. I don't know how much detail to give or not give. I try to keep these automation minutes under 20 minutes or at least around 20 minutes because a lot of times people are just looking for a quick answer. They don't want to hear me blabber on. But I do want to explain how this WPF works and how all these, how the main form, fires off its children forms and adds it to the canvas. And then how do you add the menus to the objects? How do you add the menu to that? I just wanted to cover all that but it takes a little while if you're not familiar with programming and WPF, it can be a little different. And especially this XML stuff, that's kind of different, trying to figure out where do you add the code to add it and XML, I mean, because you can add a bunch of this Windows code directly in the implementation right here. You could do almost all these commands in here. But I think we would be missing the point of the MVC architecture. So anyway, we'll do our best and keep plugging away at it, okay? Anyway, I hope you liked this video. If you do, give it a big thumbs up, that helps. Hit the subscribe button, that really helps. If you have any questions or comments, leave them in the comments of the video. I'll try to answer them the best I can. And if you want the code, that code is freely available on the Muxhall GitHub repository. And I'll see you next time.


Okay, this video is going to be, what's probably going to turn out to be a touchy subject, there's going to be a lot of flame wars going on down in the comments and that sort of stuff. But it's about antivirus software and what I personally think about it. And basically I think the whole concept of antivirus software is just a flawed concept. I think antivirus software is useless and again, just let me just talk about how it's going to work. Now, let me be very clear here. I'm not saying you don't need antivirus if you're on Linux. I'm saying you don't need antivirus, period. If you just follow a few simple rules. First thing we need to go over though is how do you get malicious software on your computer? There are two main ways. Main way one, you download and install it. Second way is through vulnerabilities on your system, zero day attacks. Now, also I want to point out that there is no such thing. I'm not saying you don't need antivirus and you're never going to get any malicious software on whatever operating system you have. That's not true. There's always going to be vulnerabilities. There's always going to be a chance for that. I'm just saying that antivirus software is not going to help you.  How do you prevent this? There are three simple things you can do. And again, nothing is perfect, but three simple things you can do. Only use software made by people you trust. For me, that means that it's got to be open source. That doesn't mean I trust every piece of open source software, but if it's not open source, I don't really trust it now. Am I perfect? Is everything on my system open source? No, I have some drivers on there and I will admit that I also use Google Chrome when I could be using Chromium. I'm not perfect. Thing is, I do trust Google, for example, to an extent. I trust that they're not going to destroy my computer. I trust that they're not going to steal my credit card number and go charge things up. Do I trust them not to be spying on me? No, that's something different. But as far as being destructive on my computer, I trust them, but that's just me, I would recommend not to use Google Chrome in that aspect. You're much better off going something with Firefox or Chromium, but not to get off too much on that. You get software from a person that you trust.  It's the only reason you can make up all the excuses you want.  I get it from someone I trust. It may not be the developer exactly, but from a source that I trust, a server that I trust, that I know that to the best of their abilities, this server is secure. Again, nothing's perfect. And three, you get it in a secure fashion. Security key, something to make sure there's no man in the middle attack. You follow those three things. It's the best thing you can do to prevent malicious software on your machine. In that aspect. Again, the second option, and so in that aspect, you don't need antivirus because you get all your software. For me, it means getting all my software from the Debian repositories. If there's anything else and there's very, very few things I might get outside of that, I still make sure. For example, I like to make sure that I have the newest version of Blender sometimes because they're coming out with new features. So I may not want to wait a couple of weeks for the new version of Blender to come out in the Debian repositories. So I get it from the Debian website. I trust the Debian website, or sorry, trust the Blender website. I'm sure it's secure. But even if I trust this guy and this guy and this guy, the more sources you get your software from, it's more chances for vulnerabilities. So you're best to go with one source that if there is a problem, it can quickly be patched. And since you're using a package manager, updates will fix things rather than having to worry about updating from multiple different places. So that's option one. You get your software from secure locations in a secure manner from people you trust. Okay? What's option two for getting a virus on your system? Zero day attacks, vulnerabilities. Antivirus is not going to help you with that. Well, it shouldn't because it should be fixed before it gets to the antivirus. If there's a vulnerability on your system and it's known, hopefully your operating system will patch those vulnerabilities as soon as possible. And then they won't be a problem. Thing is, antivirus isn't going to have them until we know about them. And then it's going to add it to its list of things to check. But your operating system should already take care of that. So here are the two things. Again, get your software from trusted places, trusted people, and in a trusted way, and keep your system up to date. And if your system, if you're using a good operating system, vulnerabilities should be patched. You shouldn't depend on your antivirus software to be looking for these patches for you. It's that simple. So again, a lot of you are hating me right now. You want to comment below.  Say some obnoxious things that just don't make any sense and aren't true. Because that's just how it is. Antivirus, the concept of it, is flawed from the beginning. And also, another thing, okay, so antivirus, you might say, well, even though we don't know about these vulnerabilities, we're just going to look for software doing malicious things, doing suspicious things. And that's another problem with antivirus software. One, it's running your background all the time, slowing down your system. But every system I've seen that has antivirus, it gives you more false positives than it does real positives. Because it's everything you do.  This program's trying to download a file from the internet. And it's going, is this okay? Is this okay? Well, yeah. I mean, I trust that program. That's why I installed it. If I didn't trust this program, then I wouldn't have installed it. Asking me, do you trust this thing is ridiculous. And that doesn't work anyway. I, for example, I've made scripts and programs for Windows systems that, you know, they're basically installers and they go out and they grab files to install whatever packages I need. And stuff I wrote myself. And I have found, written them certain ways. Antivirus is like, whoa, whoa, this program's trying to grab, you know, data from online. We're blocking it, you know? Or are you sure you want to run it? And then I just changed the way I do it. And basically I use Internet Explorer in the background. And Internet Explorer is trusted. So I'm doing the same thing. I'm downloading the same files. But because I'm doing it with a program that it trusts in the background, all of a sudden, it's okay. And another thing is, you can go online. There's websites. You can upload a file.  And so if you want to make malicious software, you test it on that site. If one of the programs catches it, you just recompile it and you encode it different and try again until it isn't detected. It's that simple. Antivirus just does not work. Comment below. Let me know what you think. I'm probably going to get a lot of thumbs down, but I'd like to get some thumbs up too. Comment below. Probably going to be a lot of fighting on this. I may not reply to a lot of comments because I just don't feel like arguing people. But as always, thank you for watching. And I hope that you have a great day.


Hi everyone, I'm Joe for jazby's case breaks calm. Happy Saturday coming at you with 2019 2020 Panini contenders optic hoops Pick your team two box pick your team number 75 big. Thanks to everyone for getting in on the action Appreciate it at the end if you bought at least two teams, you'll get a shot at a little bit of break credit top five We'll win $60 of break credit each We got Katie Okay, see addition all-star aspirations. We got Anthony Davis 20 rebounds playing the numbers game We got Markel Fultz poor Markel Fultz. I think Have to come back from an AC out. I thought he might have had a chance at being comeback player of the year Devonte Graham For Charlotte. All right, the autograph is gonna be. Oh nice for the Miami heat Dario with the heat Kendrick Nunn Rookie ticket autograph 004 out of 149 Nice, that's pretty sharp There's a Zach Levine right there for the Bulls. There's John Wall historic slams For Washington We got more historic slams Is that this play Griffin? Clippers and we got silver Jason Tatum for the C's and Brandon Ingram who was come back clear of the year last year Playing some good basketball this season to where does Andre drum and go Andre drum and reveals an RJ Barrett nice one Roy with the New York Knicks He's playing some of the Knicks are playing good basketball. Believe it or not It might sneak into a playoff spot this year. That'd be hashtag good for the hobby There you go And there you have it. There's Andre drum and right there for Cleveland Thanks, everyone. I'm Joe for jazby's case breaks calm. That was pick your team number 75 Now let's give away a little bit of money if you follow those instructions, you'll know that you have to buy at least two teams All right Dario bought three teams But to count still one entry Gretchen bought two teams. That's an entry. Thanks Gretchen Hovsev bought 19 teams 18 teams count for the for the purposes of the promo Right, so that'll be half of that is nine There's nine right there Jarell with two teams. That's an entry Roy two teams. That's an entry and Steve Moser two teams one entry All right, so 14 spots total on that so top five after Six good luck four and a two one two three four five and Six after six times. There's your top five Jarell Hovsev Hovsev Hovsev and Roy The break for Roy there. We have thanks everyone for giving this a shot. I'm Joe for jazby's case breaks calm I'll see you next time for the next one also If you happen to use multiple different email addresses for your for your orders here jazby's case breaks calm Check all your emails. I don't know where that I don't know what the main one is when we're doing gift card codes or break credit codes So just check all of them check your span folders except congrats again


How often do you find yourself engaging your team by offering them the benefit of the doubt? In today's data-driven environment, asking for data is a sound and helpful habit. Articulating assumptions that go into decisions is also necessary. Leading, while offering others the benefit of the doubt, imbues your trust in your team and is different from a lack of intellectual curiosity. Leading by giving others the benefit of the doubt cultivates safe spaces for candor and meaningful questions resulting in improved team performance. Reflecting our trust to others through our own integrity can lighten cognitive overload and self-doubt. Such two-way trust may also enhance expressions of inclusion, shifting the conversation toward intellectual creativity and mission accomplishment. As a leader, offer trust to your team by judiciously giving them the benefit of the doubt. Lead well this week.


Members of law enforcement gathered tonight in Bemidji to recognize and remember those who served and lost their lives in the line of duty. Positioned in the shadow of the Beltrami County Courthouse, community members and residents gathered for the Peace Officers Memorial service. This is the 19th year the ceremony has been held in Bemidji. The message at the ceremony highlighted the importance of remembering those who gave the ultimate sacrifice and the importance of showing gratitude towards law enforcement in our changing times. Probably more important than ever before because of the of our society and some of the things they have to deal with. And of course whether you're military or law enforcement we like to we want to honor them and they like to be remembered and they give an ultimate sacrifice and so very very important to to remember that. Law enforcement fatalities rose nationwide. In Minnesota one officer was killed in the line of duty during the past year.


Welcome. This is Melissa Armo and I'm reviewing the spy here tonight and it's very interesting because the market felt heavy heavy this morning. I felt that the market should be up higher this morning given the jobs number out. We did get up but I had felt that it was a big gap that was needed but you know what my take on the market was we were they're gonna stall today fall and then rally next week or take pretty much all day to get going and that is what the market did. Now I'm just gonna review this here because I'm I'm gonna you know I've been doing this a long time but I'm on a bazillion email lists I mean I'm I'm talking about going back like 11 years and I just have a separate email I get all this crap to and I got so many emails in the last 48 hours about people shorting this market excuse me and it's because the market to people has seen top in here in the last you know two days we gapped up here and fell didn't get over 295 and then fell this was the fed day the fed minutes came out dropped down here gap down this day so a lot of people shorted this market here shorting the top and and then there you see it and again remember resistance and support are areas so people were looking at this and saying well that's it that's the top of the market and then here's today so the market gapped up today and really quite frankly rallied into the clothes exactly as I expected we would do 519 here eastern time market up here after hours and anything can happen here next week between the next three days of Monday morning I don't know where we open but I will tell you that the market's definitely higher first of all if your strategy is shorting tops and buying bottoms you will consistently lose in the market over the long haul it doesn't mean that some days you won't make money it means that over the long haul you will lose money also you know a lot of people like I said not only shorted this market but exited their lungs when we didn't follow through let's go here three days ago or two days ago so you know I'm telling you that these numbers are real I mean the market mathematics if you've ever studied math you understand in the world these numbers are real the spy is headed to that 300 number it is going to get there I can't give you the exact time and second and date and moment and time that is going to but it will get there and the reality is that you should never short a top as a strategy so a nice call here I made in the market it was fairly early in the morning not not right out of the gate because I felt we were heavy this morning and we did drop and fall initially after the gap up but you know for the mark to get through this area the shorts are not blown on through yet because we didn't get over this level which was to 94 95 but I'm telling you that we will now some people watch price action like me but they don't read it like me they will take trades according to something called technical analysis and some people trade based on fundamental analysis I'm telling you the technical analysis gives you the right information to be able to know what to do next so the market is definitely definitely not a short and quite frankly anyone that is short in this market in my mind is an idiot okay but you know another nice call here today and again many people still probably have the hung on to the shorts over here from a couple of days ago thinking and believing wholeheartedly that the market might get a little bit over and then fall again are feeling that the market is extended this market is not extended and I could go into a very very very long lecture about why I'm not going to do that here tonight it's Friday night it's late but I will tell you though that I had a nice call here today in the day trading room to go along the market a nice option trade here to go long and I would follow this through for sure into the next week and we will see where we go again I don't find all fundamentals but there was a nice jobs number out this morning which created the gap up in the market I wanted to see it bigger but at the end of the day the market still did it there's still plenty of strength and plenty of momentum into the market and let's just see exactly where we are here yeah we're up we are up tonight 294 34 was a high here at 145 actually here at four o'clock we were up at 294 45 now 294 34 so we were over this here right into the close yeah we get over this after hours and then we follow through so I mean caution to the wind anyone that short this market I think it's a dumbest thing you could possibly do next to shorting Microsoft but you know this is again why it is very important to have a consistent strategy to trade a reason that you look at things it is not about supporting resistance if it was that easy quite frankly no one will lose money in the market and everyone you win and the amount of money they would make would be very very small so there's a very few people making a lot of money in the market and a lot of people losing and why is that because there is a few people that are very intelligent and smart and know what to do and understand what to do and then there's a lot of people that don't so if you want to put the answer in your favor my suggestion to you is learn what to do from the people that are at the top that's pretty much all that you have the only choice that you have if you are not one of those people at the top if you don't know the all the information already okay then you need to learn from someone like that and that's you know the best advice I can give you going into the weekend have a great weekend everyone Kentucky Derby's tomorrow night and if you're interested in learning what I know the next class for the golden gap is the 18th and 19th of May email me at Melissa at the stockswish.com