Yeah, I'm going to be talking today about supply chain security, specifically JavaScript supply chain security. This conference actually has the open SSF added and a bunch of other tracks that I'm sure if you've gone to, you've heard about this topic quite a lot. And in the last year or two, you've probably heard about this topic quite a lot. And yeah, if you want to, I think that link works. You can follow along the slides or go get them yourself. There's lots of links, lots of content in here. Feel free to follow along. And yeah, so a little bit about me. I see a lot of familiar faces, but I'm sure there's some folks that don't know who I am. My name is Darcy Clark. I've been an engineer or in software development for over 20 years. I was the former staff engineering manager for the NPM CLI for the last three and a half, almost four years. Left GitHub in December. Also built a company called Themeify. It was like a commercial WordPress theme company. Did lots of consulting with all those big brands that you see there. If you want to follow me on Twitter, if you're still on Twitter or not, I'm at Darcy on Twitter. So cool. Most notably, I said I worked on NPM, the NPM CLI team for three and a half years. It was part of the acquisition in 2020 by GitHub. So a lot of my experience comes from, obviously, managing a team that supported a portfolio of over 100 or almost 100 packages with billions of installs monthly. Likely, who's run NPM install in the last month? Awesome. Cool. So I'm hiding your dev dependencies somewhere. I'm sure. I didn't write a ton of code.  So blame them for any problems you have with NPM. Specifically, Luke, who still is on the team right now, if you need. Exactly. And yes, please go to Luke's talk tomorrow. He's going to talk all about how we orchestrate releases and everything with those hundreds of projects. But yeah, so significant impact, roughly 2% of that portfolio, or 2% of all traffic that we saw on the registry was for that portfolio of projects. And if you can imagine, and some of these maintainers, this might not surprise you that I see in this audience, the small team of about four or five supported 2% of the entire registry traffic. So when you're talking about supply chain security, you're talking about the packages you depend on all day, every day. There's just a very small minority of folks that are really doing a lion's share of the work to make sure that we have a secure infrastructure and secure supply chain. So I see Jordan in the back there, too. We'll bubble wrap you later.  Let's hope there's not asteroid that comes crushing down here, so. Cool, so when we talk about this area, when we talk about supply chain security, what are we talking about? And why do we even care about supply chain security? Well, it's really open sources taken over. We used to have 89% of the software we were shipping was closed source, and now we've totally shifted that to 89% of the software that you own in production is actually open source. And really, securing the open source supply chain means we are securing our own products supply chain as well. So it's critical to get this right in the open source so that we can have safe, closed source software as well. And what are we talking about when we talk about supply chain, what are we talking about trust? So let's take a look at the current ecosystem, and this is going to help shape what I'm talking about, especially because different talks, I'm sure, can go into different parts of supply chain security. Specifically within JavaScript, there's a whole bunch of tools. And the landscape has different players in it, different open source projects. There's the runtimes and engines. There's the package managers, the transpilers, and then a whole bunch of other packages as well. And really, this is the layer that you see in MPM. All these categories of projects are the ones that are actually in the registry that we usually consider to be the ones that we actually can interface with and download, install. And today, I'm going to focus primarily on package managers because that's why I know. No big surprise. But we're going to talk about essentially why package managers are so important and essentially what we can do to have more secure package management. So of course, what does supply chain security look like in practice? Well, it's the fancies you have, right? And of course, JavaScript has a lot of dependencies. It is the largest software registry. MPM is the largest software registry in the world. We see over 3 million packages. I'm sure. Does everybody here have a package in MPM? Hopefully, most of you, some of you. And of course, we see a ton of downloads, right? We see 219 billion downloads a month. And of course, you've seen the memes, right? This is the stuff that gets a lot of likes on Twitter. People are sharing this concept that we are a very greedy ecosystem. And obviously, we just consume open source on mass. And I actually look at these. And I'm sad because it seems like it's a failure that we don't really have good observability, right? Like I think a lot of people look at, there are no modules folder in the think that's a black box. And I think that's a bit of a failure on the tooling side of things. And I'll take a bit of a responsibility for that. Of course, a large portion of those dependencies aren't actually things that you've included yourself. They aren't the direct dependencies. I know for us, you've talked about this all the time. In your talks, and it's actually being documented quite widely, the Octaverse report on this back in 2020, it's an average of 683 transitive dependencies and JavaScript projects today. That's crazy compared to the fact that there's only, I think on average, it was like 10 direct dependencies in the projects. So that's compared to all the other ecosystems. It just looks insane how many transitive dependencies we actually see. And if you don't know what transitive dependency is, this little diagram helps you. If this is a new term for you, it's essentially something that you haven't included directly. It's coming into your project because it is a dependency of direct dependency or even deeper in the graph. Of course, the fun stuff comes up with the fact that the fun insights are that these types of dependencies are actually the ones that are found to have the most vulnerabilities or be representative of having the most vulnerabilities is those deeply nested dependencies that you didn't even include yourself have the most vulnerabilities. So roughly same 5% of volums are living there. And you would have seen, I think this stat was used in one of the keynotes as well. It's from Sonotype State of Software Supply Chain from 2022. So we've seen like an increase of over 742% in attacks on the supply chain or open source supply chain. This is what this looks like on a graph. Graphs, yay. It's kind of scary when you think that attackers and people that actually want to disrupt our ecosystem, not just sort of benign vulnerabilities. This is increasing, right? And the JavaScript ecosystem being the largest is sort of ripe for disruption and it sort of has a lot of low hanging fruit in terms of the API surface area that we support. So I don't want to know what this looks like next year, but I'll see you next year and hopefully we're all still here. Hopefully we're all still here. Everybody in this room probably will have a job next year if you take this back to your companies and they're like, I know more about security. And you'll have a job for a long period of time, right? So this is great. Everybody here is gonna switch to be security experts. In terms of GitHub, because I know the Seca system, while I used to work at GitHub, GitHub's own advisory database for the MPM ecosystem was like 2,900 advisories. A lot of those had actually been migrated from the MPM advisory database. And roughly 80% of all dependabot alerts are actually for the JavaScript ecosystem, which is kind of crazy. So we're talking about a lot of compute that GitHub actually gives away for free with that tool. And actually there's roughly 8,000 malware takedowns that now are represented in the advisory database. It's kind of hard to find if you want to know how to actually see those. Let me know. And that doesn't actually represent all the malware takedowns. I know some companies and representatives here know that that's the case, that not all malware takedowns are actually in advisories, which is unfortunate, but this is a pretty large sample size of what we're dealing with. So who feels like this is true? This stat is true. Feel free to raise your hand. Wow, okay. We got some, a lot of ICs in the room. It's true. You feel like it's low. This was the last data point that I could find. It's actually a couple of years old. So you're probably right. It's probably a lot larger than this. And you get a sense that it's becoming unmanageable actually dealing with dependency updates and the fact that you're getting hit with an advisory. It feels overwhelming. And I have some examples of this actually down the line here. But yeah, so 59% chance in the next year, you're gonna get an advisory.  So what are the actual threats when we're talking about supply chain security? I'll try to move quickly through these because many of these are known, that they get reiterated, rehashed. Vulnerabilities are sort of the easiest thing.  People are actively trying to write software that is malicious. Typosquadding is fat fingering something and sort of getting socially engineered to download something that you didn't mean to. Dependency Confusion is sort of a very unique type of attack that is seen or an exploit that can be used where essentially the infrastructure that has been created for enterprise, enterprises and corporations to proxy the NPM registry has created this sort of situation where you can potentially download and be socially engineered to download software you didn't mean to in your company. And then there's registry compromised. This is like very unlikely. Does anybody know if the NPM registry has ever been compromised? That you know about? No, no and the funny thing here is that most of you all have essentially a cached version of most packages with integrity checks and can basically tell whether or not a package might have been modified in some weird way. That's why lock files exist. This is why folks that are mirroring the registry can also, you know, if you're writing registry follower, the NPM registry follower, then you can also sort of flag to the ecosystem. We would long hear that, you know, Tarball is being compromised before I think it would ever reach your front door. And then the worst case scenario is account takeovers. So somebody like, I don't know, offers you a beer and then starts publishing packages from your laptop or is able to do some sort of session spoofing or something like that. They're able to actually get your credentials published as if they were you. How can we mitigate some of these? So GitHub and NPM have been trying to do a lot of work here. I can't speak to any initiatives in the last four months since I quit in December. But there was definitely a focus on doing more active scanning. I know a lot of companies in the ecosystem have been doing active registry scanning for malware and helping to report it back to the NPM registry. There's also new sort of technologies in terms of the AI models and behaviors that they're seeing within the package contents. The key here is like focusing on package contents for malware. It truly is like the source code doesn't matter as much as the actual thing you're about to download. So focus on contents is key here. And of course, like surfacing this back to the canonical registries is important. Typosquadding, the ways we can mitigate that is definitely through heuristics. So known patterns or dark patterns to sort of socially engineer, you can imagine pluralization or prefixing or suffixing. Package names is an easy way to essentially socially engineer packages that can be downloaded by accident. And then so finding those patterns, creating sort of heuristics also based on potentially downloads or package authors, having good sort of heuristics around this can create tools that we can help prevent typosquadding attacks. Of course, policies and enforcement, just how do you configure the tool that's installing the thing to make sure it's not actually downloading a typosquadded tool. In terms of how we mitigate dependency confusion attacks, it's really tough. The key here is own a scope. That's what we've told people for years. Own the public scope in the MPM registry if you're going to have private packages that you're publishing to an artifact three or Nexus instance, you should always own the scope so that you don't get exploited and always make sure your MPM RC file has to config for that scope to be proxied through. In terms of registry compromise, we already have the tools to essentially check this. If you're not using lock files for some reason, I don't, I'm sorry, like I don't know why you're doing that. But that's the key here is we store that information about packages into tar balls, or sorry, packages into lock files about the tar balls. And we do integrity checks today that should prevent any kind of like registry compromised asset. And account takeovers MPM did a ton of work here enforcing mandatory 2FA. A lot of folks are not happy about that, but it does sort of raise the bar in terms of potential account takeovers. Also improved sort of login experience with modern sort of web off end. Login was implemented into the MPM CLI itself. So if you ever type MPM login as a V9 and beyond, we've defaulted to that web off experience. So now you can get thrown to the website, put in your credentials or use a yeah, like a web off end experience in the browser to essentially log in or publish when you're publishing as well to authenticate. So those are sort of the known sort of attack vectors. I'm sure you've even heard like many times over the five or six categories of exploits that I talked about there just now.  Specifically the noise within supply chain tooling is a huge problem today. There's a lot of confusion as well about how dependency graphs should be represented. There's some obfuscation around APIs as well. And just generally there's a real lack of tooling to help you deal with advisories, to help you deal with updates. And in terms of standardization, there's also a pretty huge lack of standardization around package management. And the very last one actually, there's a ton of immutability when we're talking about installing software within JavaScript and it's a huge problem. Gonna take some water. So this area, essentially immutability and non-determinism, it's something that, I'm not sure if a lot of folks in this room have dealt with, but it's likely that you've installed a package which has a lifecycle script, a post install script that executes and modifies files on your system in some way, which is different than the artifact itself that they existed. Might even reach out to the network to fetch something and it is inherently not the same thing that was published that is now living on your system. So I thought I would share a quick example of just sort of immutability and non-determinism within the ecosystem. Who's ever used Create React App? It's okay. It's okay if you're not a friend and developer. You can. And not to pick on Create React App, like great project. This is after initialization of, I think I ran MPX Create React App. This is what your dependencies will look like in your package JSON. So you get seven direct dependencies added to your project when you're starting a new React project. And so you're like, okay, great, that's awesome. So what happens if I decide to use one package as manager or another? Well, to actually install those seven direct dependencies with Yarn, I actually get 1200 dependencies in my graph. So you go from seven direct dependencies now to an inflated number of transitive dependencies to fully realize the dependency tree there. And also you start to see this crazy pattern, which is none of these numbers are the same across all these package managers, right? So this is a huge problem. The representation of that project, the package JSON, to PMPM is different than Yarn. It's different to MPM. It's different to BUN and Deno, these new projects that are also doing sort of seamless no install experiences. And so there's a difference of almost 850 dependencies between these package managers. It's pretty insane, right? So this is where the lack of standardization about how we resolve your dependencies is a huge problem and probably a bigger problem to supply chain security than folks might realize. So you're probably like, wait, what the heck is going on here, right? And I actually shared this insight on Twitter. And I'll show you the responses there in a second. But what's actually going on here is that each package manager has a very different understanding and different capabilities about resolving your project, your dependencies in package JSON. So it depends on whether or not they're going to install, like the context is key, but also their understanding of development dependencies, optional dependencies, peer depths, any overrides or resolution features that your package manager might have. Life cycle scripts as well is going to create some immutability and potentially change the number of dependencies installed. So this is a lot of, these are a lot of features that each package manager can take a different stance on any one of these and create a different representation than one or another. So any kind of like security tooling or anything that's using one representation may be false or invalidated if you decide to use a different package manager tool the next time you install your project. And so I said, I posted this on Twitter and some people are like, what the heck? I think ZB was kind of like, okay, but are they fast? You know, like it doesn't matter as long as bun is like blazingly fast, it doesn't matter which packages I get on my system, right? I know Wes is in this room. Okay, but some of the people are in this room so I'll let them take a picture. So some of the responses were really funny, like to be like, oh, like what the heck is happening here? I think Jordan, I didn't put your response, but you know, he was digging into how I got that, this data and it was a bit of manual work to actually get the out of the caches for Deno and bun I had to go into the caches to go get those results. But yeah, this is pretty interesting. I think Wes has come in specifically, so Wes sitting over there is super interesting. You know, he's saying, and I think very sarcastically, because you know the answer to this, right? But not everybody here might know. Well, what would happen if I ran that same package manager again on the same package JSON? What would happen? It would be pretty funny. Well, there's actually this like, statement. And of course, when we talk about supply chain security, there's been a lot of talks about reproducible builds, probably hermetic environments, hermetic builds, and they actually, that comes back from this Heraclitus of Eusephorus, I think. The Greek philosopher said, like no man ever steps in the same river twice. I like to say that no package JSON installs the same river twice, and that's a hipster from San Francisco. It's specifically full stack. Probably using Versailles. But it's true, it's an unfortunate fact that MPM install is not consistent. It's not reproducible. And part of it has to deal with time, and it's very philosophical. Are you the same person you were today that you were yesterday? It's a bit philosophical, but also at the same time, there's real world problems with these tools. So how can we avoid that worst case scenario that as you continue using the same tool, you're actually getting different results over time? So MPM install, if I use it twice in a row, like how do I ensure that's the same thing always? So the key here is, at least with your dependencies, you should be avoiding sort of mutable references. And so this isn't very well documented, but things like distribution tags, so that specifier like at latest or at like a pre-release or something, where there's a distribution tag that lives within the MPM registry, that's kind of considered like a release channel. And that thing can update all the time, right? It's not a specific version that you're sort of opting into. Same with remote tarball URLs. You can actually specify a package as if it's an individual file. And that thing has no kind of registry integrity value that is being stored back in the registry. So this thing can change over time. And same with Git repositories, obviously the references there aren't sort of locked in time. And in fact, we don't store back an integrity value at all for Git repositories. Specifically, we don't store back integrity, sorry, value for repository dependencies in your lock file. So key here is just be mindful that like these references are mutable. And actually this morning is that not all the package-mended data in the registry has been validated. So how can we sort of get rid of this mutability or avoid it? Use lock files, plain and simple. Understand what's in those lock files. So know what those values are, what can and can't be checked for integrity, like I just said with Git repositories. And then you can actually use time travel, which is pretty cool. For any registry dependency that exists, you can actually lock in time the manifests that you'll fetch and the versions that you'll fetch from the registry that you're configured to. So this is a feature that's in the NPM CLI and it essentially creates a way to have a subset of the versions available. This kind of gives you a way to sort of lock things in time unless the NPM team has like removed that dependency for like malware or something like that. This should be a pretty foolproof way of making sure you sort of get almost a reproducible build. And of course, if you're a robot, just cash and bundle everything. Basically, once you fetch it once, just hold on to it. Yeah, yeah, this is a little robot that's coming back from the future to tell us what we should be doing. And it's still running .NET in 23. So I only have about 10 minutes left, but I want to also quickly look at some of that current tooling and the state of that tooling. Because I know that it's not super easy to understand what's going on. And yeah, sometimes you can be afraid, you might be afraid to ask me how to do certain things. You might be afraid because of this. So here's another example. I'm again using create react up again, no shade, but this is a fresh install of create react up and I already have six high security vulnerabilities. I generated this today. So anybody starting a project with the tool, unfortunately they're starting off with some vulnerabilities already in the project and that's unfortunate. But it's great. NPM has just showed me post installation and actually I ran audit again just to make sure I wasn't going crazy. But I ran audit on the project and it showed me that there were six high security vulnerabilities and it told me how I can fix them, right? So it says here we go, run NPM audit, fix force. So I'm like, sweet, I'm about to do that. Luke, what's gonna happen? Say it again? Okay, and we got 84 vulnerabilities. So this is really unfortunate, right? So we have this tool, it tells you that there's some problems. We say you can go fix it running this command and then you end up with what? What's the factor? Does anybody, quick mask? What's the factor you go for? Oh yeah, we've got all kinds of new dependents, new problems, right? So, and what's even more probably furious for end users is we tell you to run NPM audit, fix again. Right?  No, like I want the old set, right? Right, so this is really frustrating. We got people constantly complaining about this. And this is the state, as of today, of this project and these tools. I like that everybody in here is laughing because I know that you all experience this and it's actually, it's sad, it's not a good situation. There's some companies really trying to do great work in this space though. They're trying to innovate. GitHub obviously has, dependabot, men has renovates, sockets, as for us as in here is trying to do great work in here. Trying to obviously improve the state of security insights, these advisory tools. But I do want to note some red herrings and sort of issues obviously. Red herrings in terms of the NPM audit tool, that's a great example. Oh my gosh, like I do this thing, I get another thing. Some of the advisory tools obviously, like NPM audit is a good example, are giving false positives. They're creating noise and we're doing all this work, we're creating all this noise in the guise of, well, a false negative would be worse, right? Like that's the, we want to tell you about everything and even if we're wrong, it's better than if we happen to not tell you about something. Like Sbombs is, I'm sure you've heard the term, software build materials are in the JS ecosystem, we've had lock files for a long period of time. Just be mindful that some of the standards don't map one to one with our ecosystem. I've been able to generate Sbombs from GitHub's new tool that don't actually match reality, which is unfortunate, so these are things that might, may or may not provide value to you, but you already today sort of have a ledger of the software that at least within JavaScript's ecosystem for your project, you should have a ledger and an index of the packages that you have in your project. This is another one that's a bit concerning, there's a lot of work that goes and a lot of focus that's gone around sort of artifact signatures and it's like you really care about the package contents more than anything else and I know that people care very dearly about provenance, but yeah, MPM did ship a feature here if you wanna validate the integrity of the signatures, you can do that with MPM audit now, so there is a tool if you do care about these things, I think the focus is a little bit misplaced. In terms of scorecards, brands badging, this is something that every organ needs to, I think way against the policies and sort of be concerned about the biases, definitely have a zero trust mentality when it comes to security, don't trust me, don't like validate everything I say, don't trust like the big orgs, definitely look into these things yourselves. And just in general, like watch out for pancias, like there's a lot of companies that are telling you they fix all your problems, S-bombs are gonna save us, it's not true, there's not one like silver bullet here, there's a lot of different tools, a lot of different things we have to fix.  Don't worry, there's hope. So insights, I mentioned before, there's companies that are actually doing some great work in terms of bubbling up what's inside the contents of packages, creating great metadata that we can use, that's something we've been missing from basically the dependency graph today to be able to build great tooling around great data and insights about packages. Of course we're also, I think as an ecosystem, we are really needing reproducible installations. And the only way we can get there is by removing our need or sort of crux on the mutable sort of installation process with post-install scripts. And so we definitely need first class, what I've been pushing for is first class support for package distributions. It's an idea that has been around for a while, it's something that there's been some support for or pushes for with yarn. At NPM I put together an RFC for this. This is theoretical again, this is just a spec that we've been putting together, but this would create a blessed way to have essentially per environment or sort of per condition sort of variants of packages. There's also been some great work in terms of runtime isolation with the experimental permission work that went into Node. I think, when did, do you know when it landed? Okay, so it's been around for a while and then same with the experimental policy API which Bradley unfortunately isn't here did a lot of great work there a while back. And so we have these two great features within Node today that you can go try out and see what it looks like. This is very similar to what Tenno has implemented with sort of policy enforcement of the runtime. NPM has an RFC open for permissions and I would love to see per package permissions. I have a screenshot here of, has anybody ever written a web extension? Yeah, couple. Web extensions in the web manifest file actually has like permissions and scopes like baked into their web manifest format. I would love to see us eventually adopt something like that to make it easy to sort of provision at the package level. And so that's what I think we're trending towards and I hope we get to. The last thing I wanted to sort of talk to John, I don't know only have like one minute or almost over is sort of introspection. Last year we did something really cool. I put together this spec for what is called like the dependency selector syntax. It's basically lifted CSS syntax that makes it super expressive to write queries against your dependency graph. This is a set of examples of what that looks like. If you've ever written CSS, you're probably like, holy cow, like I know how to find all the react versions easily, you know, you can also do really interesting things like finding your peer devs, whatever that is. The attribute selection is especially interesting because you can essentially query for any kind of attribute that lives on in your package JSON. So you can see how with more information into the dependency graph, we could actually do really cool queries. And this landed, here's some more examples of exactly what you can do with this syntax, but this landed back in MPMV 816. And big, I should say big applause to Roy and Luke for work on the MPM CLI that got this done. So here the very last example is a query for all the life cycle scripts. Programmatic, you can actually use this today. Like if you want to go write some interesting queries, you can actually query it just like you would in the DOM, right? Like in, you want to write some JavaScript to query your HTML documents, you can actually query your dependency graph with the query selector all, which is really cool. And if you want to, you can use the command line MPM query. So this takes your node modules folder and sort of says, let's stop letting this be a black box and do some investigative work. Noble selectors, you can do some interesting things with Sember, we've created like some pseudo selectors that are really cool, not yet implemented, but that were specced out are things for CVEs and CWE selectors. Also, our seed today is a query support for MPM audits. So that crazy noise that you see today which might not be relevant to you could go away very quickly by filtering out sort of the things that you need. And lastly, with validation or sort of with the query selector, you can write really expressive policies, right? So imagine ESLint for enforcing installation policies of your dependencies. So key, imagine a world where we eventually standardized package resolution, similar to the browsers did with HTML5. Imagine we can have an amazing query syntax that allows you to expressively write and traverse dependency graph. You would not feel like you're in the dark but actually like you could find the things you need. And so I really truly think that that's the way forward. Obviously this talk is a lot about the accuracy of our dependency graphs and securing them. We definitely need more standards. If you stay with a zero trust mindset you're gonna be a lot safer than you were coming into this. Please share any discoveries that you find. If you're gonna use the package manager today please use MPM as far as I know, the most accurate. But yeah, that's it. Thank you. I think I have mad time so I don't know if we have time for Q&A. But yeah, I can talk to you guys. Any immediate questions I guess? We might have like five, 10 minutes. Okay. Does Arborst have a method? You showed the query selector all. Does it have a matches where you could give it and as, yeah go back. Wait, no, Arborst API specifically. Like you see tree query selector all? I'd be interested if there was like a, you have a reference to a node in an Arborst tree that you could say does this match my query selector? Does that API exist? If we standardize it can exist. Yeah, we can definitely do that. Yeah, the hope towards the end here with the talk of standardization is that over the next year I would love to bring a lot of this work and like tooling to the OpenJS and to standards. Anything else? Any other questions? Yeah. Did you try to fix React after another time? Did I what? Did you try to run npmod to fix-4? Yes. Do you know the result? No, it's- You go back to the first one. Yeah. Yes. No, no, it's actually intermittent. We actually, I think there's potentially a race condition as well. Yeah. Yeah, so that's another issue, truly. Like no package install is the same place or no npm install is the same place. Anything else? Cool, thank you so much for coming.


Thanks Tracy, so Don Bubar believe it or not I've been running Avalon as a publicly traded company in this specialty metals and mineral space for over 20 years now actually and have seen quite an evolution in the space from when it first started with our lithium project where these were basically little known, little appreciated and very poorly understood emerging commodities to where we are now or this is becoming quite an important sub-sector of the mineral industry particularly with this whole evolution of the battery industry energy storage technology electric vehicles is creating this whole new demand that we never saw or could perhaps see coming in the distant future 20 years ago but it's definitely upon us now and it's a change to game in some very dramatic ways so I think it's time that this sub-sector of the mineral industry really look at how it wants to brand itself because it is such a different sector the mineral industry we've referred to these as commodities but they're really not commodities in the traditional sense of the term they don't trade on commodity exchanges they're really highly refined chemical products that you need to produce for specific applications in the in the marketplace and so there's a lot of new terminology starting to emerge on this I know an investor Intel has used the technology metals I hear energy metals being used quite a bit now advanced materials clean tech materials that's one that I kind of like but I think we should all think about how we want a brand this industry to really differentiate it from the traditional mining industry which is very very different in terms of the risk factors and so that we don't confuse investors about what those risks in the business are let's face it most traditional mining investors just their commodity price speculators at at the end of the day whereas in this industry it's more about the growth opportunities that these emerging commodities are presenting to investors and so I say now that I'm hearing the blockchain developers and Bitcoin developers adopting the word mining I say they can have it they're the miners now we're going to be clean tech producers clean tech materials producers there's your reminder of forward-looking information so as I said we've been around for over 20 years now and I'm a veteran of this technology metals space and as a result of that we've done many many equity financings over the years so we have some 20 to 25,000 shareholders all over and since the rare earth bubble burst there a few years ago we've seen a big turnover in our shareholder base which has kind of depressed our valuation but on the other hand we do have a very large audience out there to follow us around the world and once we get some traction on one of these projects we're working on and we should be able to really build on that solid base and another thing that differentiates Avalon and in addition to the commodities we focus on over the years is we embrace sustainability as core to our business early on recognizing if you're going to try to produce materials for clean technology makes sense to try to do that in a sustainable clean way embracing the principles and environmental social responsibility we did that we built it into the culture of the company we've been producing a GRI compliance sustainability report for six years now and continue to get recognition for that actually actually just got recognized for the third time by corporate night magazine as one of their future 40 responsible corporate leaders in Canada so in terms of our overall sustainable development strategy what is a sustainable development strategy in this space well we had to find it by focusing on those materials that are relevant to clean technology as kind of number one and then think about how to design that operation to minimize the overall environmental impacts that you're going to have on the environment and start planning even before you started how you're going to make productive use out of that land post closure any money companies don't even think about that till they're getting near the end you really should think about it even before you start to work on that new mineral deposit and then focus on process efficiency how can you process that material to minimize the amount of waste you generate and maximize the amount of valuable material you can extract from that that rock you're taking out of the ground and do it in a way that meets your customers expectations on product quality another thing we're applying is that's different from the traditional mining industry miners always want to make the next mine the biggest they possibly can biggest richest mineral deposit but it doesn't really have to be that way and the traditionally in the mining industry you would start small follow the vein and get bigger over time as as you understood the resource and saw the opportunities actually by applying that sort of stage development approach starting small and building scalability in the project you can actually manage a lot of the risks inherent in the business in terms of environmental impacts and as well as investment risks started a modest scale understand what you're doing build some scalability into it but in something goes wrong at the start in terms of perhaps the chemistry of your discharge water and you can fix it before it causes a huge environmental disaster at the end of the day so I think there's a component of the stage development approach and environmental responsibility as well as managing investment risk by not overbuilding it too quickly and then finding maybe your product is not going to be accepted in the marketplace at the end of the day and lastly if you're working in Canada and anywhere in northern Canada you really have to work with the local indigenous peoples our principle has always been and still is engage early and often and try to find ways to collaborate on opportunities to share in the rewards of the business and create opportunities for partnerships as well as job creation and training so as I said we've been a diversified player in the space for some time that's been really part of our strategy is accumulate a portfolio of assets that give us exposure to a broad range of these technology metals and have ourselves positioned to move a project forward in production when the opportunities created by new technology creating that that demand a few years ago we thought it was going to be rarest and got awfully close with our Nechilacho project right now we've been focusing more on our separation rap is lithium project for obvious reasons but it's interestingly enough we're now seeing opportunities to advance all three of them at the same time because of new circumstances with rare earth and and tin nice problem to have but it's creating quite a bit of work for our team these days so I'd like to give you a little bit of a snapshot on each of these projects and try and do that in the time I have available here so starting off with separation rap is lithium this was our first foray into the wonderful world of these clean tech materials new discovery back in 1996 started working on it in the late nineties initially as a an opportunity to serve the glass industry this was an unusual lithium pegmatite enriched in the mineral petalite not a common lithium mineral but a valued industrial mineral in the glass sector and still is actually and we nearly got it going then except for a change in the marketplace there that frustrated that opportunity that at that time but we've hung on to it knew it would have another day could see that probably a lithium battery would become something bigger even back in the late nineties and sure enough that's what we're seeing now and provided an opportunity reactivated a few years in the meantime we've kept our tenure in place made it more secure and a reminding lease maintained our community relationships there we've got good access and a 10 million ton open pitable resource that's ready to mine when the opportunity arises which perhaps is just arriving now as two minerals in the resource petalite and lipidolite and lipidolite is another opportunity for us we didn't even recognize early on it's now starting to be used more as an input for making lithium battery materials from and in fact we now are talking about collaborating with our good friends at Lepidico I don't know if Joe Walsh is here today but Lepidico are planning to build their phase one demonstration plant for their process to make lithium carbonate from lipidolite and Sudbury and we hope to be their supplier of their initial lipidolite needs for that that plant and that would be an important byproduct for us but petalite is still the dominant mineral in the resource that's creating the opportunity and so we know what I've ever made a battery material from it before so the last couple years that's what we focused on was how do you make a battery material actually innovated our own process to make lithium hydroxide from petalite made and fine products been proven in the NMC cathode chemistry already by the NRC and we know we can do it at low cost we think we can improve on that but that's definitely a path that we can follow here now but it's also got potential as an industrial mineral and glass and we're still looking at that too so we've got a number of options open to us including producing lipidolite as a byproduct for Lepidico and other users of that the glass industry though is is a very interesting opportunity for us nobody's talking about it everybody's talking about lithium batteries but the glass industry is still a very big consumer of lithium and these high strength glass products that are becoming more popular now things like gorilla gorilla glass made by Corning the critical ingredient in all of them is lithium and there is no substitute and what's happening now is there's now struggling to find adequate supplies of lithium and that's kind of open the door again for an emerging producer like us with the ideal form of lithium for the glass applications to serve that market and we've actually done some more work on how to create a product for them that meets their quality requirements and we've come up with something that my colleague Pierre has branded super petalite because it's super clean in its quality and that's really important to the end users and creating a good opportunity for us to serve that market so based on that understanding and having a multiple kind of market opportunities we're going to take the staged approach and what we want to do is start by at a modest scale get in a production produce the industrial minerals products which we think we can do for in the order of 50 million dollars start making money on that and then on the back of that have a pilot plant to prove up our battery material product see where we can fit into that market best in terms of the different forms that are being used now and then have another scale up on the back of that production initial production of the industrial minerals products to serve that industry going forward we think that's the most logical and lowest risk way to get initiated in this lithium business especially considering how dynamic an industry it is as Dan explained earlier with the types of chemistry is being used in batteries changing all the time and inevitably the material inputs as well and quickly this another thing about this resource if you want to be sustainable there's these are great deposits to work on there's nothing poisonous in them that can that represents an issue from for the environment on to tin quickly and this is a slide that was shared by the International Tin Association with its members from a presentation done by Rio Tinto on a study they commissioned at MIT so a very credible source that ranked the metals in terms of their being impacted by new technology and guess what number one on the list was tin who to thunk a out ranks lithium and cobalt in fact and I think this is just a reflection of the fact that tin has a lot of potential in many of these emerging clean technologies and maybe they haven't been fully realized yet but there's a lot of work being done to see how they can contribute in positive ways to many of these technologies and there's huge growth potential there and that's great news for us because we've been working on a tin project for over ten years now looking at trying to redevelop the old East Kentville tin mine which closed in 1992 when the price of tin dropped very dramatically and it's been basically on a closed mine site ever since but lots of resources left in the ground and we see an opportunity there now that we're working on actually redevelop it by taking advantage of the factors a whole block a lot of waste that was left on surface that with using taking advantage of current prices and new technology we can recover a tin concentrate make money while we clean up the site so we've created a whole concept around that six million tons of previously mined ore sitting there oxidizing you see the orange color generating acid mine drainage and creating a problem for the environment that we can clean up make money while we do it so we're going to try to develop a plan around that and it's again a relatively low capex for something like thirty million dollars now we can put this in production in less than a year start making money not a huge amount of money but for a company with no revenue any amount of money is welcome and get ourselves into small scale production with the potential to scale it up by going forward and clean up the acid mine drainage issue there and if I can get two more minutes Tracy I'll just touch on first well it's used now as in solders for electronics so it's in every electronic product now on the circuit board for the solders so it has those conductive properties that give it application in a broader range of things now and it's being talked about in some new types of lithium ion battery cathode chemistries it's already being used in renewable energies and solar panels indium tin oxide is as part of that chemistry and there's a whole bunch more that we're just learning about ourselves actually there on the on the radar screen yeah so TIN is a fascinating opportunity if I have two more minutes just touch on on Thorlake and Nechilacho that was our rare earth project we had to put it on hold about four years ago when the rare earth bubble burst and all the interest evaporated and with the mollycore fiasco in the in the US investors have just lost interest in rare earth totally in fact it's almost like rare earth or a dirty word with investors south of the border now they don't even want to hear about a little investment but as you heard earlier yesterday from from Gavin and Nick rare earths are coming back has no doubt about it they're vital in electric vehicle technology now to as you heard them talk about and so there's a couple of opportunities or reasons now for us to look at reactivating Nechilacho not interested in rare earths as one but also Northwest Territories is looking at alternatives on improving infrastructure there one of the things they're focusing on is is how they can bring clean energy to the north the north side of the lake here around Yellow Knife that does not have enough access to hydro power to service needs so they're relying on fossil fuels and there's a plan now to bring hydro power from this dam north north of the lake and the route they're looking at would bring it right by us at Thorlake here and give us access to hydro power greatly reduce our energy costs and actually we're perhaps part of the justification for that route of being a potential customer for the product and they're also talking about extending this road out to the shore here to a long less transmission line which provide access to this new proposed park out here in the community of Lucille case so we might actually be able to take advantage of this and with much improved infrastructure and then of course we've heard yesterday about how there's a soaring demand for neodymium-praziodymium with electric motors and electric vehicles requiring this now and while we looked at a model based mostly on the heavy rare earth potential at Natchalacho there are some discrete zones there that are very very rich in neodymium- praziodymium that we think we have an opportunity on plus there's a whole lot of lithium there that we haven't even really begin to look at including Lepidolite that'll make Joe Walsh happy there at Lepidico so what are we doing is we're going now to sort of take advantage of this this year start studying the possibilities but again looking at a small scale development model see if we can take advantage of these small very rich resources easy to access and get in production in the near term and bring a supply of neodymium- praziodymium concentrates to serve this rapidly growing market electric vehicles and maybe I'll leave it there thanks for giving me some extra time


Those are medieval robots. In the internet community centered on the bustling town of Bikini Bottom, where colorful characters dwelled beneath the waves, there existed a lost tale that only a few fortunate souls witnessed, a story shrouded in mystery and intrigue. It was an episode of SpongeBob SquarePants that vanished from the annals of television history, known only as The Black Hole. Legend had it that those who watched it saw a title card that was an empty black void, with purple text reading, The Black Hole. As the episode begins, the screen flickers to life, revealing SpongeBob eagerly introducing his latest invention to the viewers, a highly advanced particle accelerator. With boundless enthusiasm, he explains its purpose, to unlock the secrets of the universe and push the boundaries of scientific discovery. Excitement fills the air as SpongeBob powers up the accelerator, his friends gathered around to witness the historic moment. As the machine hums to life, it creates particles accelerating and colliding into each other. But as it did, something goes terribly wrong. A vortex forms within the accelerator, growing larger and more ominous with each passing second. Panicked, SpongeBob and his friends scramble to contain the chaos they've unleashed. But their efforts prove futile as The Black Hole continues to expand, threatening to engulf Bikini Bottom and everything in its path. In a desperate bid to save their home, SpongeBob and his friends embark on a daring mission to stop The Black Hole before it's too late. With courage and ingenuity, they devise a plan to reverse the accelerator's effects and close the rift in space-time. Amidst swirling chaos and heart-pounding action, SpongeBob and his friends face their greatest challenge yet. With teamwork and determination, they activate the accelerator once more, using its power to disrupt The Black Hole's gravitational pull. In a blinding flash of light, The Black Hole collapses upon itself, vanishing into oblivion. Bikini Bottom is saved, and order is restored to the underwater world. As the dust settles, SpongeBob and his friends share a moment of relief and triumph. Though their adventure was fraught with danger, they emerged victorious, proving that even the most daunting challenges can be overcome with courage and friendship. And so, The Black Hole fades into legend, a lost episode of SpongeBob SquarePants that reminds us all of the power of resilience in the face of adversity, and mostly, nothing creepy or unsettling seemed to happen in this episode. Though its tale may be forgotten by many, its message inders, echoing through the depths of the sea for generations to come.


When I came to Congress in the early 1990s, I didn't need a PhD to understand that these trade policies were written by corporate America for one very simple purpose. And that purpose was to not have to pay workers in this country a living wage. The purpose of these trade agreements was to enable them to shut down factories in Pennsylvania in Vermont and all over this country and move to low-wage countries where they pay people pennies an hour and don't have to deal with unions or obey environmental regulations. That was the purpose of those trade agreements and that is exactly what has happened over the last 30 years. We have lost since 2001 almost 60,000 factories in this country and millions of decent-paying jobs. There was once a time when people could get a job in manufacturing, earn good wages, good health care, decent pensions. Those jobs increasingly are gone and the new jobs are McDonald's and Burger King. Let me just give you a very few, very few examples of how our disastrous trade policies have impacted the people of Pennsylvania. 2013, General Electric announced that it would be eliminating 950 jobs at its Pennsylvania locomotive plant in Erie, moving many of those jobs to Mexico. Last year, Allegheny Technologies shut down two steel plants in western Pennsylvania, laying off 600 workers moving to China. 2009, Hershey shut down its York Peppermint Patties plant in Redding, destroying 300 jobs and moved that plant to Monterey, Mexico, where workers are paid a fraction of the wages that workers here were paid. In 2008, Sony closed the last TV manufacturing plant in America in Westmoreland, destroying 560 jobs and moved that plant to Baja, Mexico. And on and on it goes. I have opposed from day one in Congress every one of these disastrous trade agreements. Secretary Clinton has supported virtually every one of these disastrous trade agreements. Now my message to corporate America is your greed is going to end. You are not going to continue to deindustrialize the United States of America. You are not going to continue to shut down plants here and move to cheap labor abroad. You are not going to cut the wages and benefits of American workers and give CEOs huge compensation packages. Together, we are going to create an economy that works for all of us, not just the 1%.


today we're going to talk about the canteen spirits vodka soda product there's one thing going for it and it's zero sugar and zero carbs other than that don't know hey there njwho22.com here with a booze vlog this isn't sponsored i bought this product myself it just we found it at shop right liquors the other day it's called canteen spirits vodka soda and we were you know you know kind of interested in it because it's zero sugar and zero carbs that to me is great it's five percent alcohol so let me try it it's 15 bucks for a six pack which is ridiculously costly and we we drank this six pack and i'll tell you the the net result was the next day i felt uh this morning i had a pounding headache and i didn't feel great and guess what the buzz for this wasn't really all that good either i didn't even really feel like i had a buzz i felt fine all night when i was drinking them and i don't know why i woke up feeling like crap but um and one other thing that bugs me about this i don't really know much about the brand but i went on their website to see if there's any nutrition facts i want to know exactly what's in here what kind of water that they use what kind of flavoring makes this thing taste like black cherry um and nowhere on their website or on the package that it was i able to find nutrition facts because they say zero sugar zero carbs and i can't tell if it has some sort of bad sweetener in it now this wasn't a very it had a very subtle flavor um it wasn't really anything all that great so i don't think they added uh anything but they did say in the box here vodka with natural flavors added so i have no idea what that means i can't stand companies that aren't transparent like this that other company the long finished drink or whatever they had to go digging through their social media feed until i found their answer for the ingredient this one i'm not going to bother going through their social media because i don't care so your better bet is to buy like polar cans of black cherry seltzer and put an ounce and a half of vodka in each can and you'll get the same drink and you probably instead of getting six for 15 bucks 15 bucks worth of you know halfway decent vodka plus seltzer will probably get you 12 18 or even 24 cans of the same exact drink and probably taste better um so that's it i don't recommend this i'm not going to buy it again it's overpriced didn't feel good and they're not transparent with their ingredients so that's it see you later canteen have a nice day if you like our video please hit like and subscribe and i'll see you next time


Everybody forest here ripping 2022 honors first off the line immaculate first off the line Obsidian and prism six box mission number 17 results on screen can be found anytime at late in sports cards comm Let's get into it So it's too obsidian hobby to prism hobby and immaculate first off the line and an honors first off the line We'll do the prisms first purple power rookie Saints Alante Taylor to 49 Ferguson is in your white purple J. Alexander Packers. That one's out of 125 Karee Quildon Carson strong got a silver. No offense Seahawks followed by a Rams Isaac Bruce Silverado David Belgica on brisker Awesome Silver Mondrey Stevenson Pats blue ice Carson Wentz Commanders to 99 Isaac Bruce Torrey Holt orange rookie Treson Abner bears the 249 Calvin Austin the third Brock Hardy rookie base Silver brilliance Josh Allen bills orange Kyler to 249 Cardinals Spiller and Logan Hall And guys Matt's live at 10 a.m. Eastern with baseball breaks Basketball breaks and football breaks silver Miles Garrett Browns followed by a Kenneth Walker the third rookie Otto Seahawks the 149 on the red wave nice card Seahawks got Damian Pierce and Daxon Hill Traylon Burks orange CJ 2k Titans at 249 Chris Johnson, Sam Howell rookie commanders Prism flashback Garrett Wilson Jets hyper rookie Jalen Tolbert Cowboys to 175 Fetherian Mathis and Tide Chandler Silver rookie sauce gardener Jets purple ice commanders Logan Thomas 225 Devon Lloyd and Jalen Tolbert blue wave dick but just bears the 199 Troy Anderson, I Isaiah Pacheco Checo, I'm sure Last pack of box one Silver and new recruits Kenny Pickett Steelers Hyper Stefan Gilmore Colts to 175 Scene Romeo Dobbs, I did a better second box prison here. Come on red wave Jamo or Javante Sorry, Javante Williams to 149 Broncos Duffy and George Pickens Steelers rookie silver lockdown is Michael Parsons Cowboys green scope Dan Marino Dolphins to 75 Phillips of Wendell Robinson Yeah, but yeah, but go pass Silver rookie is Kairi Elam bills Navy camo Anthony Munoz Bengals Number 16 of 25 Dude was a beast. I'm called to old serious final tomorrow 7 7 Eastern Blue wave rookie bills Kairi Elam to 199 Ruckert and cook Silver brilliance Najee Harris Steelers orange to 249 bills Jordan Poyer Well, they quill this rookie Blue ice Ray Lewis to 99 Ravens See what happens tomorrow, man Orange to 249 Browns Nick Chubb Taekwondo and Kyler Gordon Silver Devon McCordy Patriots if they Gus Ferrata auto to 99 Commanders Christian Watson rookie base I don't remember that no silver Matt Ryan Colts purple ice to 225 is quandary dig Seahawks Just Rookie orange boy I'm off a Seahawks to 249 Ketsey a sauce gardener Silver prison break rookie Olave Saints blue wave Kenny Clark Packers to 199 Desmond Rader rookie silver MG3 Broncos followed by a Tyler Algear that is a gold rookie auto, but it has a big peeling on the back Solid hit for the Falcons gold rookie auto Tyler Algear, but you're gonna have to get it replaced Mafe and Tyler Algear Get a box wrapper out to you Falcons city and now two boxes Karloft is chiefs rookie to 25 on the yellow furious George Tunnel vision AJ Brown Eagles to 25. That's a green accent there. It's a burrow base Lions to 125 trifecta material Deandre Swift in the triple jersey Rookie eruption patch car Jersey card Bailey zappy Pats to 100 Eagles rookie autos Jordan Davis here To 199 Part of the Philadelphia Bulldogs and a 175 rookie dual Jersey auto for the Texans is John Michi the third One more obsidian then iMac and honors Maybe we'll pull a Brady or Mahomes on The honors rookie purple pier strong junior Pats number to 100 Got rookie Charlie color out of 25 for the Ravens Got Ryan Tannehill tights. It's a 50 Ravens Kyle Hamilton on the four color rookie patch on breakable Seahawks Kenneth Walker the third rookie jersey to 100 That happens Jose we all get busy The list Jones jr. Rookie audit to 199 for the Bears Jets breeze hall ricketers you ought to 175. All right. Let's see some monsters here Okay, break so far. We know we didn't make it a great one It's kind of thick. All right. What's going on here. This card is coming out of the box. Whoa.  Look at the middle. Whoa That dude Good like eight cards together, I guess That's green to 23 Dishon Watson first off the line for the Browns We're about to find out Rookie jumbo patch to 10 Wanda Robinson Giants. Oh, that's what it is Look at this thing. Yeah, it is a soul relic Tyrion Davis price. Is this even a card? Does this count as a card? Tyrion Davis price Niners rookie soul relic. So cleat relic here Yeah, we pulled it we pulled them a Holmes honors auto Few months ago No, not at all. No chance You got numbers auto jets mark gas the note to 99 10 on the edges. Oh There's so much edge there Dude, that's way more than a 130. Yeah 130 is this this is 130. This is probably 120 ish. It's pretty well inside the 130's Probably go. Oh, yeah, that's probably like a that's bigger than a 380 or 360. Oh, yeah We have 360 mags like silver bars from like a packable nose fit perfectly and some of the things that I hear fit well in there, too But I don't know what that is. I don't know what that's a big end. Oh This is sick. I like this a lot Patriots clutch time inks at 49 Adam Vinitieri Heck yeah You go Pat's and a green first off the line prime Patrick you auto to 18 Jameson Williams Lyons Awesome hit Lyons pretty good box there. All right. Here we go honors photo 2022 Sunday funding next y'all stick around for that one. So we got purple Auto that's lower numbered purple Base that's lower numbered and a one-of-one recollection collection in this box We're gonna start with a Justin Jefferson for the Vikings to 99 The purple is a Jalen Hertz three of 12 There we go birds nice little numbered Hertz There is like a line across the back here. I don't know if you guys can see it Goes from like the number over to like where my thumb is Come on there it is you can kind of see the white you can see we're on his pant leg There it is goes between the 12th all the way across And might I think it's the print line. It doesn't it's not a scratch It's not a physical scratch, but we'll send a box of wrappers. You can get that one replaced Very low nice low number it hurts though. I want that to be perfect either way. I think that's a print line But I again, I don't know how that would Fair if you sent it to grade. All right. Here we go first off the line Purple rookie signatures George Pickens Steelers again, that's a 15 or less Steelers George Pickens It's a Tony Hawk 900. Yeah, and it really is chicken. It is a 900 nice Pickens and Recollection collection Cowboys Tony Romo on the one of one There's a flawless design card here. You get the recollection collection stamp right where he's holding the ball There you go 2018 flawless design here Congrats to the Cowboys All right, y'all that'll do it. Let's do a quick recap here We got Sunday fun day. I'm next Wanda Robinson Kenneth Walker the third Kyle Hamilton Bailey Zappie Deandre Swift autos of Vinitieri Mark Gaston oh Breeze Hall Yulis Jones jr. John Miche the third Jordan Davis gold Tyler Algier did have some unfortunate peeling on the back Valgans was sending a boxer rapper out to you so you can try to get it replaced Gus Farrott Kenneth Walker the third and then Isaac Bruce In one of one recollection collection Tony Romo for the Cowboys Nice Romo Pickens Purple Redemption Steelers honors Ricky signatures RPA or prime patch. Yeah prime patch rookie auto is James Williams green 18 first off the line Lions and then the Soul rally barely if it's in the slider box Davis price nine errors to three that is the car. That is nothing else But the card. Yeah, I think it's Gummy thick.  That'll do it on a Sunday funny


Who is the most important X-factor player that needs to step up for Raven's playoff win? We jumping straight into it with this first question from my guy, Joshua. He said, what's up in Graven, great job on another season covering the Ravens meticulously. I know you'll say you're not, but you are the man. No, I am a man, but definitely not the man. But I appreciate you, I appreciate the questions that you done sending this year because you've been bringing it. And you don't pull no punches or nothing. So I always appreciate that. Anyway, he said, believe it or not, I actually have faith about a Ravens win this weekend. Oh, me too! We on the same boat, but anyway, let's keep going. I'm not blind, the Bengals are clearly the better team, but their tendency to get away from the run game can shoot them in the foot, especially if the Ravens can find a way to hog time and possession and force enough three announced to keep them under 24 points. If our defense and special team keeps the game in arms reach, who do you think on offense besides whoever's at quarterback needs to have the biggest X-factor game of their career for this win against all odds? If I got to go on offense, I would say specifically JK Dobbins. I would say JK Dobbins because if he can have a game, like have a game, then the Ravens can control the game. And if the defense can do what they've, they've been doing pretty good overall against Joe Burrow this year. They should have Marcus Peters back so that'll be nice. Daryl Warley like played out of his mind and obviously got Marlon Humphrey. Kyle Hamilton been coming along strong. You got Marcus Williams and this will be a Bengals game that he finishes. I mean, he finished the last one too. Roquan Smith, this will be his second Bengals game. But I would say JK Dobbins because if he's going off then and they scoring in the red zone too, that's so important. But if he's going off then the Ravens they're not only controlling the clock, but they're converting, they're getting first downs. They're keeping drives alive. The clock is moving. So they're holding the ball like you mentioned time and possession. So I would say him. And then, I mean, we brought up so many people on defense already. But yeah, if I had, if I could go for a unit, like say a unit that would be the X factor, I would say the offensive line. Because the off, and I know it sounds so often to line that's such a boring answer, but it's true because the offensive line can set the tone and keep the tone for the game.  If they do great pass blocking, that's the one right there where it's like, eugh, they can be great pass blockers. Then that'll give Anthony Brown or Tyler Huntley, but it'll give Anthony Brown a whole lot of time for his receivers to drop passes. Next question is, I was just playing, well, I was playing, but I wasn't playing but anyway, I'm just playing, I'm just messing around. But anyway, next question came from Lynetta. She said, hey, engraving, how are you in the family? Hey, we doing really good Lynetta, I appreciate it. She said, I have a question, will Lamar posting about his injury? Do you think the players will try to win it all for Lamar, or is this wishful thinking? I'm just wondering, what do you think? Thank you for all that you do, and I appreciate you. Hey, no, I appreciate you. Now, yeah, I can see that they're of course trying to win it for Lamar, but they just trying to win it for themselves. They just trying to win it, period. I think with Lamar just talking about his injury status and whatnot, him putting it out there, that I think it's something that they probably knew already, but it just makes it official to the world now. Like, okay, yeah, Lamar's done. But it does put even more pressure on them since they don't have their superman at quarterback. It puts pressure on all the next men up because Lamar, when he was there, he nine times out of 10, he alleviated pressure off people. There will be some games where he put more pressure on people. He was having a rough game, but nine times out of 10, he's alleviating a lot of pressure off a lot of people. And he does, because he does so much. He does so much. So yeah, I think, yeah, they gonna try to win it for Lamar, but they gonna try to win it for themselves, too.  You don't always get an opportunity. Like Playoffs is, for some players in their careers, it's worked out what they've been to the Playoffs a lot of times. Other players, it's like, ooh, Playoffs came falling for you. Clay is Campbell, like who knows if this could be it for him. Justin Houston, this could be it for him. And it's other guys that are pending free agents, don't know where their careers headed. Some guys may be thinking about retirement right now. They may not have just come out with it or whatnot, but you gotta take every opportunity. So yeah, I think they all gonna try to do it for Lamar, but I think even more than that, they trying to do it for themselves. Next question came from Lamar. He said, man, that tweet from Legote was a breath of fresh air. Even though he isn't playing in quiet's down trade rumors for now, what do you think, my guy? I don't think that quiet's down trade rumors at all, like not one bit. I didn't get that from Lamar telling everybody about his injury that it quieted down trade rumors. I think the only thing that will quiet down trade rumors is if Lamar signed a contract with the Baltimore Ravens. Next question came from my guy, Kevin. He said, are we over hyping Lamar? And Graven, happy new year. Thank you for the channel. I'm a new subscriber. Only found you a few weeks ago and you're my primary source for news about the Ravens. I appreciate it, Kevin. Thank you, man.  Looking at the season, the stat of no passing touchdowns for 13 weeks points out a glaring weakness in Lamar's game, especially in clutch situations. Ooh, yeah, as far as the title question, are we over hyping Lamar? No, then as far as where you broke it down about the whole no passing touchdowns for 13 weeks. No, I wasn't at no passing touchdowns to a wide receiver. I think that's what it was. No passing touchdowns to a wide receiver, something like that. But you look at what Lamar and the Ravens have accomplished with what they have on offense. Look at how much they've won with what they've, or really actually what they haven't had on offense. That's a better way I should put it. Just a lot of lackluster talent there at skilled positions. I mean, there are really every position on, in football is a skilled position, because you gotta have skill to play those positions. But you look at how successful they've been. And then you look at other teams around the league. I know a lot of people like to point out, oh man, if we got a wide receiver, we could end up being like the Raiders or like the Cardinals or some other teams that have nice wide receivers, but they still haven't done good. Well, you get what I'm saying, a lot of people bring that up. So then you could flip that around and be like, well, look at what the Ravens have done and the successes they've had without those guys at that position. And it speaks volumes to Lamar Jackson. It speaks volumes. So that's why I just, I really been hoping that you can see him in a situation where he does have it. But again, not the conversation for another day. So no, we are not over hyping Lamar. Lamar will sign the non-exclusive franchise tag. Next question came from my guy, Maddy said, and Graven, thanks for the constant streaming Ravens content. Nah, I appreciate you watching it. He said, the only way the Ravens will find their way out of the Lamar Jackson contract situation unscathed is by tagging him with the non-exclusive tag this year, not next. If we exclusively tag Lamar, he may just sit and the Ravens end up in a Kirk Cousins 2.0 scenario after the tag. Here's why the Ravens will only put the non-exclusive tag on Lamar. This would let Lamar shop and find that guaranteed deal maybe, but Shadi doesn't want to do a Deshaun structured deal, but if another team office it, well, he would have to do the deal, I hope. He's not going to lose Lamar. But anyway, he said, optics shift away from the Ravens furthering the fully guaranteed contract shift for quarterbacks and instead shifts the focus to the team that forced our hand. Since two first round picks would also be due, Lamar may not get a guaranteed contract which may help EDC negotiate a more team-friendly deal. I see what you're saying, it's like if he's talking to another team, that puts depression on Steven and EDC in them, but I just, I don't think, I just don't think it's going to happen right now. We'll see though, but anyway, he said essentially this puts all the cards on the table. The only card still hidden would be how much Lamar could get as a free agent without two first round picks or any trade capital tied to him, which given his contract situation, Ravens would never let be shown. What do you think? I'm not hearing anyone talk about the strategy around the non-exclusive tag and how it could be leveraged in this unique situation. I love Lamar, I love the Ravens, everyone loves him. No, trust me, no they don't. And that's okay. He said, I love Lamar, I love the Ravens, everyone loves engraving. No, no. But again, like I said, well that's okay. I hope the two parties can come to a business agreement that works for both. So, hey, we'll see. I just don't see it going down though, but it's time, it's time so anything can turn around, right? Steve, next question came from my guy, Thomas said, I appreciate you and the kindness of your family. I appreciate that, thank you. The years before Steve began to be the main owner of the Ravens, the postal service used to buy hundreds of tickets and take Baltimore City School kids to the games. Once he took over, he was not interested in group tickets, but only season ticket holders to purchase extra seats. This showed me that he wasn't a team player, but I got mine, you have yours to get type of attitude. Ever since then, it's as you say, as long as I can make money, I'm good. This gives me the impression that Harbaugh is in on it and is also a puppet on a string too, as I say, and lay low for your under the table bonus. There comes a time when you have to stop crossing oceans for people when they won't even jump puddles for you. Hey, I mean, he's the owner. So that's what he's in it to do, make money. That's what owners are in it to do, make money.  So yeah, Harbaugh just gonna run with whatever Steve said, cause that's the one that's cutting the check. Next question came from my guy Emerson. He said, I have a beautiful, dark, twisted fantasy in the event Lamar walks via free agency, or he ain't walking via free agency. You know that ain't happening. But he said, or if he is tagged and traded. Okay, there's another one. Although I hope Lamar is in the longterm plans, it seems increasingly unlikely. The Ravens will be set up with a strong run game and a strong defense regardless of what happens this off season, but what we'll be lacking if Lamar is gone is any sense of a pass game. First off, Greg Roman needs to be gone, but even in that case, receivers still aren't going to want to come to Baltimore. That is very true, that's very true. And I think that would be the case if Greg, obviously if Greg Roman stays, but even if Greg Roman leaves and they bring in another offensive coordinator, I still think if in order for Ravens to get a receiver, they would have to sort of overpay, so to speak. And simply because they will need to prove that their passing game can be real. And that's gonna take at least a year to do because you gotta show people on the outside a level of consistency. You gotta show them that okay, their offense just ain't the silly stuff no more. Okay, cool. But anyway, he said there is a solution for that, however. That being in bringing in a 46 year old quarterback who is said to be a free agent this off season, it sounds crazy, but the man has historically succeeded with a strong run game, a strong defense and an elite tight end. All of those things are given in Baltimore next year. Trade for Mike Evans or some elite guy in the event Lamar is traded, used those picks to beef up the secondary and then the old line. And the only flaw it seems is they drafted a center built for a mobile quarterback in a run for his offense. That being said, I don't think it's a deal breaker. If we can't keep it more long-term, at least get us a Superbowl before the inevitable years of mediocrity. Sorry for the long question, thank you. So he is talking about Tom Brady to the Ravens. That would be wild. That would be crazy. But if Tom Brady went to the Baltimore Ravens, then all the calls that the Ravens don't get right now, oh, they would get them all, all of them. They would get just as many primetime games, if not more, because if Brady to the right, that would be insane. Brady would, he would be like, he would be a quarterback, but also an assistant head coach. Cause you know, he would run the show. Like he would run the show, but it's like, that's crazy, man, that's crazy. Didn't Grant go probably want to come at our time and be like, okay, I'll play now. But that, yeah, I've never like even thought of anything like this before. This is a very unique question. On a lighter note, next question came from Griffin. He said, I know that there's a lot of things to be down on about us as of right now. Sending this before we lose to the Bengals, by the way. Hold up there, buddy! Who said we losing? But anyway, but how about we talk about something a little more lighthearted? Why don't we have red and black Ravens jersey?  I mean, that the practice, those practice jerseys, those black and purple practice jerseys. Ooh! But anyway, that would be awesome, especially because in a logo, there's a hint of red. Just a fun little thing to think about amongst all this chaos. As usual, stay safe and hashtag taking clean. I appreciate it, man. But yeah, before they even stepped to a red and black jersey, they need to drop those black and purple practice jerseys. Next question came from Kingston. He said, there's still a chance. I know everybody is talking about the Ravens having no chance to win against the Bengals, but I think there's still a chance, even without Lamar. I agree. I'm right there with you, man. But let's keep going. He said, here's my opinion. The Ravens defense played well against the Bengals. Joe Burrow threw 25 for 42, 215 yards and one touchdown. That is not the Joe Burrow we know. Now, of course, newly paid real qualifier has 16 tackles and four assists. I also saw Kyle Hamilton make some plays along with David Ajarbo having a strip sack. That's just the defense. The problem was the offense. His way it gets complicated. Of course, we had to start rookie Anthony Brown and Harvard side of the system starters, but there is still problems. We had four turnovers, four. And one of them resulted in a touchdown. You cut that touchdown, the story is different. I think it was five turnovers, right? He said, of course, Pro Bowl Tyler Hunley is gonna have the chance if Lamar doesn't play. I think Snoop played his best half versus Steelers in the first half, but the same problem lost us the game. Mistakes. Yeah, mistakes. Real quick, let me try to remember. Sammy Watkins, he had the fumble. Anthony Brown, he had the fumble. Anthony Brown, there was the pick, the really bad pick that he threw. There was also the pick that he threw. I mean, the Marcus Robinson dropped it. So that was four turnovers. I really thought there was another one. I feel like I'm missing one. Next question came from my guy, Brendan. He said, I ain't graven. Been watching for a while and always wanted to say something. I've heard around Twitter that Lamar has not been helping himself off the field. As he may go to physical therapy, but he is resisting Dias and keeping himself in good shape. So in my opinion, he will be franchise tag, but not exclusively. If a team would want to pick up his contract for two first round picks, they will trade him before the draft for players in picks. Love the flock. Let's go Ravens, love the channel and hope your fame is doing well. Appreciate that, Brendan. And yeah, I mean, if they, I don't know if that's true or not. That's all I can say. But yeah, if he did get traded, it would definitely be before the draft because Raven's not, they wouldn't trade him for only future picks for like two years down the road. No, they would trade him for picks right here right now. Next question came from my guy, BGMethod. He said, I ain't graven. This is the first time going in on a question from Subb. I got a few questions and comments. Not that you asked what I'm from B-more. I've been a Ravens fan since 98. I didn't immediately fall in love with him. I'm an active duty Army vet and the young football player from Merville High School and B-more that passed back in 2021 was my cousin. Oh, I'm sorry about that, man. I always appreciate Hollywood for repping him at the game. I also sent these questions to Ravens vault. I think Ro and Williams are new Wave, Lewis and Reed are great cornerstones going forward. Yeah, I agree, I agree. Cause they both, they both bring it. They both have their hiccups along the way, but nobody's going to play perfect every single week. He said, I do believe EDC is going to work on the wide receiver problem more diligently this off season. We'll see, we'll see how it goes. It's obvious to everyone that is going to hold us back if they don't. He's only going to go so far though. So I think it rules out the Andre Hopkins. I'm 85% sure that. So hey, we'll see what that 15% could do. We need a strong offensive coordinator that takes more advantage of Lamar Jackson's arm talent. If Lamar Jackson's arm talent is still here next year. So that's to be determined. He said, with all that said, here's my questions. A way in a job, oh, who has a better chance of becoming the sucks type of guy? Oh, man. Adafi Way started off strong last year, then this year just, I don't know what it's been.  He like, he got a slow take off. And that's like holding him back. And then the same guy said that a job makes it look easy. And I was like, well, he didn't even play that much, but he did his thing last game. So I don't know. I think it's too early to tell. Obviously, Adafi Way, he got to build up consistency. And David Ajabo got to just build up because he was only played in a game in a play, or a game in like four play. Cause I think he was on special teams that first game that he played, but he only played one defensive snap that first game. So I think, for me, it's too early to tell cause we don't even know. We don't know Adafi Way yet.  He said, I don't think it's too late for a way. There's flashes. Remember how long it took Paul Kruger and Adelias Thomas? Oh boy. Where do we get that wide receiver? Who are you looking at? Can we draft him with only five picks this year? I like Harrison Junior, but I don't think he's coming out. No, he not eligible yet. We would have to trade a bunch of assets to get in position for him, like Atlanta Deer for Julio. As far as wide receiver, I, in my opinion, what I think they should do, I think you should draft somebody who's NFL ready. The first round early second, I know they ain't got that many picks right now. They're going to get more picks. You know they already, Raven's going into a draft with five picks, never. They were never, they would something, but they ain't doing it this year. But I would say to draft a high receiver, draft the NFL ready receiver and also trade for somebody who's nice now to whether it be Deandre Hopkins. I know Mike Evans, Mike Evans will cost more than Deandre Hopkins to trade for. So if it's Deandre Hopkins, okay, cool. Mike Evans, oh, okay, cool. And I think somebody like Lazard, that wouldn't be my first choice, but I'd be like, okay. But so I would double down at the position. I know Rashad Bateman's supposed to come back. Devon Duvenay's supposed to come back, but I'm not going into this season being like, all right, Rashad Bateman and this other guy, the veteran, whoever we get, y'all are it. No, I'm loading up, man. I feel like they should have been loaded up, but I'm loading up for whoever the quarterback ends up being so heavy even more. He said, lastly, who could be the next offensive coordinator and why doesn't anyone seem to think T. Martin is a possibility? I heard a lot of people talk about T. Martin before, but I haven't heard as many people saying it recently. He said he didn't run a G-Dro type offense in college. He now has experience with those run concepts. Maybe he can merge it with some creative passing concepts to create a hybrid version. I really believe that's why they hired him. Harps doesn't like guys he doesn't know in coordinated positions. So you're right, he don't like guys he don't know in any positions for you. He knows T now. Let's unlock Lamar Jackson. We can hope that Lamar Jackson will be unlocked. We really can. I really hope so. But with this team, the way that they operate, the way that they think, the way that they move, I just don't see it ever happening. I don't, they would have to change a lot of stuff to really just get LJ potential reached. I just can't see it right now though. I can't, I would love so much to be wrong about that. But the way that they've operated, I just can't see it happening right now. He said, I appreciate your platform and I love how you carry it. Just like everyone else that gets long-winded in questions themselves, forgive me team, keep it clean. I hope you forward know in the vault get some more work together in. Oh yeah, yeah, yeah. Shout out to them, man. Glenn and James. Those my guys, man. I remember when I first met them, they had me on, but before they jumped into YouTube, they had me on their podcast. It's just audio podcast. It was in 2019, it was the, I wanna say the Thursday, or maybe the, yeah, I think it was a Tuesday or Thursday before the Ravens and Patriots game in 2019. I'll never forget because I think Glenn said that it was actually his nephew or little cousin that had put him onto our channel. And then, yeah, the rest been history. They've been on here plenty of times. We've been on there plenty of times. They, they, they cool people, man. And then with the vault, that's with Bobby B, Bobby Baltimore, Bobby T. He got so many different names though. So shout out to him. He been doing this thing over there. And then he with the vault with Sarah. Shout out to Sarah. Sarah, she like super cool, man. She, she, she, she's super cool. I gotta have her back on. I gotta actually have both of them back on. Really all four of them back on. But I remember when Sarah first came on, Sarah Ellison, I was a little nervous. I was a little nervous because I'm like, man, this is somebody who used to like work for the Ravens and she coming on my channel. Like, oh man, I, but she was super, super cool, man. And she, she's, she's really good. She comes in, she brings the stuff, she bring good energy. She, she, she's super cool. So shout out to Sarah Ellison, man. But anyway, he said, go Ravens, Morgan State stand up. Shout out to Elijah Gorham, my little cousin. Rest in peace.  Hey, I appreciate you a lot, man. Next question came from my guy Gavin. He said, ain't Raven, hope you and your family are doing well. I'm curious where your confidence level is with Lamar not likely to play on Sunday. If honey starts, I feel he can manage the game well enough to allow JK and Gus to have a big game. The defense will do their thing like we saw last week. So I think if the offense can put up 17 or 20 and not turn the ball over, they could hold the bingles and maybe squeak this one out. This one will be more on coaching than ever. Oh man. I thank you for that reminder. Cause it will be because when, when you're back, I mean, excuse me, when your star quarterback is out, there's a lot more pressure that gets put on you as a coaching staff.  I do think the Ravens, they seriously have a chance, but yeah, they got to outplay their scheme. They, it's so important like that Greg Roman and the offense, the game, he calls a game out of his mind. It has to be like out of his mind type of great. Like there ain't no room for the silly stuff. It's really not no room for the silly stuff. And that's on Hobbs, Greg Roman, Mike McDonald, everybody. The players as well too. They got to help each other out. Coaching got to help the players out. Players got to help the coaching out. Players got to help each other out. Coaches got to help each other out. They got to help each other out. And really have each other's back. Cause if they don't, then they gonna be on their backs, chilling on the couch, soon relax. Next question came from my guy Brandon G. He said, hope all is well with you and the family. My questions are as follows. Number one, what is your take if Lamar sits out Sunday night? Well, he said that he's hurt. So there's that. But number two, he said, do you believe the knee injury is to the extent that wouldn't allow him to play? Oh man, yeah, he sent this before, he sent this on January 11th. So it was the day before Lamar sent out the tweet that he sent out today. And then number three, he said, do you think Lamar is using this injury to sit out so he can ensure the contract he wants and deserves? Now that part, now would he play if he had a contract? If the knee injury is as bad as it seems, I don't think so, I don't think so. Cause I mean, yeah, obviously with a contract, things are different. But then you still gotta think long term. Cause like if you injured and you injured like that, then you could not only mess up stuff for right here, but you can mess up stuff for down the road too. And then he said, number four, if the worst case scenario occurs and he does demand a trade, who would you prefer takes over? Sorry for all the questions. I'm sure a lot of Ravens fans pondering these questions as well. Appreciate the content and keep it off of the exceptional work. I appreciate you, Brandon. Who would I prefer take over? I wouldn't even know, man, because I like, it would be so weird. Like Raven's life without Lamar. It would be very weird, especially for how it's been over these past five years. I wouldn't want, I love Tyler Huntley. I wouldn't want it to be him though. Anthony Brown, I wouldn't want it to be him either. But I just, I don't know who would be out there. There's, I mean, possible quarterbacks that are out there. No, my God mentioned earlier, Tom Brady. There's, and Rodgers could be a possibility there's Derek Carr. He could possibly be out there. And there's, of course, the draft too. And I'm sure I'm probably forgetting some people too, but I just can't even answer that right now because I just really don't know. Next question came from T-Dubb. He said, Super Bowl one in 2013. This is my first time shooting your question. I hope you and the family are happy, happy, healthy, and doing awesome. Hey, we all, I appreciate it. He says, so I heard on the lounge podcast that the Ravens fired their offensive coordinator after losing very bad before going into the playoffs. This sounds exactly what the brass should do. We need some kind of change to put a spark in the player's morale. Now, he didn't, I mean, after the Broncos game, I said, if they don't fire Greg Roman after the Broncos game, then he ain't getting fired. And he didn't. Now, he sent this question on January 7th. Now, because he asked, do you think if we lose to the Bengals, then Greg Roman could be fired? No, I wouldn't have thought that. Because again, the Broncos game, once they didn't fire him after the Broncos game, after that, then he was safe for the rest of the year. Said, I love Team Cuban Clean. Thanks for all your hard work and dedication to the channel. I bleed purple and I'm always a Raven fan for life. Honestly, I think Ravens fans are one of the most passionate dedicated fans in the NFL. Oh yeah, Ravens fans, they certainly a lot of fun, man. I appreciate you. Next question came from my god, Jarvis. He said, great job resigning Roquon for the next five years. So next up is LJ.  A few questions for you though. Can a player refuse the franchise tag? For example, Lamar Jackson, and if we do resign him, who's a realistic wide receiver, you think we can get to help this offense? No more wide receivers who've been on the couch. I personally wouldn't mind getting DK. DK Metcalf? I mean, he ain't going nowhere, but yeah, I wouldn't mind DK Metcalf either. But I think, the ones we mentioned earlier, Deandre Hopkins, I think that is a realistic option especially since the card, it's already put out there publicly that the Cardinals are either gonna trade him or it's put out there publicly that they trying to release him. I mean, they trying to get rid of him, excuse me. So he'll either get traded or he'll get released and he can pick wherever he wants to go. Raven's best bet is if they could trade for him. That's their best bet. Because if he becomes a free agent, there are plenty of teams that's gonna pay more money than you. So your best bet is to trade for him if you really want him. So we'll see how that goes. Now, as far as the franchise tag part, can a player refuse the franchise tag? Yeah, they can. They can refuse to sign it and then they could wait, just wait it out, wait it out. And either the team could be like, no, we're not budging and the player could come back. I think they will need to have at least, I wanna say, how many games is it? I think they will need to have at least like seven or eight games that they were active in a year to have an accrued season for the season that they're into count on their contract and toward their overall years played in NFL. Because if they set out the whole year, then the season just wouldn't count to the amount of years that they would have played in the NFL. Therefore, it wouldn't count towards a contract. Therefore, if they set out the whole year, they will be in the same exact position the following year that they were in this year. So nothing would change. So yeah, a player can refuse to franchise tag. Long story short. Next question came from my guy, DeAndre. He said, I ain't graven, hope all is well. My question for you is that since the Browns, Texans and Cardinals have made moves now that their season is over regarding coaching and coordinators, does that give you hope that whenever we finish, hopefully with a Super Bowl this year, hey hopefully, does that give you hope that we will definitely be making our own moves as far as the Ravens staff that so desperately needs to be focused on? That's a really good question. For Ravens not really, I could see them. The most thing I see, Mike McDonald ain't going nowhere, Harbaugh ain't going nowhere. Biggest change I could see happening is Greg Roman. But I just don't feel like much would change even if Greg Roman, his contract ran out and they were like, okay, we decided to mutually part ways, do-do-do, wish them well in the future, endeavors, do-do-do, whatever. I just, I don't think much would change as long as Ravens still had the same mindset. Now last question on this episode came from my guy, Howard. He said, what's happening in Raven? I know it's playoff time and I'm ready, but I've been thinking lately about the situation of play-calling and many of the things that be making us fans shake our head with this Ravens offense and it hit me. Greg Roman basically told us how he operates and coordinates in his very first press conference when he was introduced as offensive coordinator. A reporter asked him his play-calling style and he said, I don't like to leave breadcrumbs behind. At that time, I don't believe the media and us fans really got that analogy to his truest form. I'm about to explain it so it makes sense. What he meant was when he calls certain players that works, don't expect to see them again. Basically the approach is trying very hard to outsmart the opposition, but in reality he's outspotting and outcoaching himself with that approach and it be costing us. And Graven, I've been rocking with this channel for the last couple of seasons and it's been plenty of times on your videos when you said the Ravens do incredible things in one game and then we just don't see it anymore. That's the reason. And I've said in the comment section as well as questions from subscribers at Hardball, Roman and Wink were too stubborn to change. They fired Wink, but that was only a third of the problem when it pertains to the coaching situation. Two thirds of the problem are still here. Hardball and Roman. I can get much deeper on this topic, but I wrote enough in his email that Team Keep It Clean understands where I'm coming from, your thoughts. Oh yeah, they, you said it, outsmarting themselves. Outsmarting themselves is just a perfect explanation for it and then just really overthinking things and overcomplicating a lot of stuff too.  And you know just what I mean. You two team keep it clean. You see my boy, he like automated. Well, that's my homie, ain't that right in Raven? Right in Raven. Right in Raven. Shout out to Raven. Right in Raven. Right in Raven. Right in Raven.