good to go. Alright, everyone. This is the real, this is the first thing you're waiting for here today. Just really going to be a very nice discussion session here. Hey, have a seat. In the right room. This is the place to be. You can tell the friends about it afterwards. Okay, so, I think, so before we start, I guess we have a couple of things to clarify here. Maybe first of all, I'm a Skype. My name's Eric. Eric. And we're from Steps. We work on Embark. Excuse me. And you probably noticed already that the title of this talk here, Building EWars and Depths with Embark V5, is a little bit different from what you see in your little DevCon application. This is due to some reasons. So basically, the description of the talk doesn't entirely match what we do here today because we have to change a little bit based on some time constraints. So basically, we were a two-hour talk workshop and then we got cut down to 40 minutes. We had to shuffle some things around. So out of the 10 points that we listed in the description, you might get maybe one or two. And also that at the same time also changed the format a little bit.  It's more going to be like a little bit of a theory session. And then afterwards, we can demo some stuff and maybe walk you through some code and maybe have some questions and then hopefully we get some answers. But just, yeah, just also clarify. Our goal for this wasn't to be an expert on EWars. If you have any EWars questions, Sean will probably answer them hopefully. He tries best. Our goal for this was to integrate the EWars contract into EWars. So just to help developers build contracts using EWars essentially. And before they're using EWars. So that's what we expected. Okay. Any questions at this point? Okay. So then maybe like, yeah. First up, was anybody at the EWars talk yesterday? Was it yesterday? Yeah. So we've been to that talk and it actually turned out that, you know, there's a lot of things still in the making. And so what we're going to show you today is, you know, stuff that works for the demo purposes, but it's probably not like in a production ready state. So just keep that in mind. It's more like exploration of what we can do with a mark. And then, you know, flexibility of the guys and so on and so forth. The main point there is that we want to show you how you can extend a mark to do just about anything you want, including some very, very experimental stuff like EWars stuff. All right.  So we talked about EWars, just a little bit. Then we're going to talk about the NIM programming language. Anybody have about NIM before? Okay. That's what we're talking about. That's awesome. Everybody here is going to learn something new today. And then there is a very mysterious project called NIM Play, which actually enables us to write smart contracts in NIM. And then we will show you a demo of how that works. And then this is actually what's going to use EWars momentarily. All right. So let's start off with, if you're WebAssembly more, you wasn't enjoyed. I mean, you probably have heard about EWars before in some way, at least like the acronym, right? So EWars was a restricted subset of WebAssembly to be used for smart contracts in Ethereum. And now if you're like new to this stuff, or more experts or whatever, like we are, then you might be wondering, what is WebAssembly actually in the first place? So WebAssembly, for those of you who don't know, is a binary structure format for the stick-based VM. So it's actually an open standard for the web that aims to provide developers an API in a way to run very fast programs and nearly native speakers. It's very portable as well. So basically you need to imagine, you can write programs in any language that transpile to WebAssembly, so you will never write WebAssembly yourself. It's an assembly language after all. And then computers are really good at translating that WebAssembly code to CPU instructions, which is why it turns out to be very fast. Yeah, so that, in general, about WebAssembly, there's actually a couple of browsers that already ship that. I believe that Firefox already has WebAssembly VM integrated so we can run stuff in WebAssembly in the browser today. So this is basically the web thing. So what that means in practice, you have your Swiss code turned into a wasm code in some way. There must be some sort of transmitter or compiler for it. And then ideally, since you have this wasm code, you can run on different CPU architectures because they can translate that code easily, which also means that that code is very portable. That's a good thing, obviously. There's generally a textual format and a binary format, so the textual format is like the assembly code that you can actually read as a human being. Again, this is not the code that you would actually write. It's the code that you can, the code that you can actually inspect and that you'll put in which you read. And then this is the binary version of that. So you can execute it. You could write it if you wanted to. Yeah. And yeah, so coming back to, it wasn't so doubtful that we know, like, a rough idea of what WebAssembly is. So E-wasm is a restricted subset of WebAssembly. So I'm not actually sure if the wording is quite correct. Maybe, maybe, Jarkis, so I might see if that's fine. Yeah. So essentially what that would mean is that if you write E-wasm code, it's automatically also valid. I want some code because it's a subset. But, you know, what does it mean, a restricted subset? So there's obviously, there's some very specific semantics to E-wasm that make E-wasm what it is compared to WebAssembly. And there are a couple of things. So we have, actually, maybe, can I open this here? It looks good. So there, the E-wasm VM kind of like, comes with like certain, yeah, semantics specific for Ethereum. I mean, we don't have to read this here, but there's this E-wasm website with all sorts of resources about E-wasm. So basically what makes E-wasm code, E-wasm code, is the environment that runs it eventually because it comes with certain semantics. That also includes things like a E-wasm contract interface. Basically an interface that allows you to have an E-wasm code that knows how to talk to contracts, smart contract APIs. And a couple of other things. Oh, sorry, there you go. There's also built-in system contracts. If you look at that, it's quite interesting. I'm not sure how hot today that still is, but there's like a central contract, EVM-transcom pilot contract. So like different addresses that are already available in that environment that your code runs in and that could also mean that, for example, you know, you have like certain functions like hash fonts and functions and stuff, as contracts, that's how I understand that you can call them from your own contracts within that environment again, right? So this is obviously stuff that would not be in plain WebAssembly available. You have that in your E-wasm environment. Coming back to the semantics. Non-deterministic behavior, basically, you know, removing floating points from that environment. And then there's this metering system which is kind of like the new gas.  Does that make sense? Yeah. Nice. You can ask John. Also please feel free, I guess, to ask questions. Yeah, yeah. We're very open, you know, format. There's the question. Oh, there. If the performance of WebAssembly is close to native, what's the point of using system contracts that are part coded by the pre-composed? So the reason for it this time is basically the E-wasm team wasn't able to make it as fast and also because of gas costs, they're mispriced at the moment. So if you go and look at how much a SHA-256 or a SHA-3 costs you and you had to implement it in WebAssembly raw, it would be mispriced. So you'd suddenly be spending, like, 10 times more gas. So that was kind of what, just to add to that, what the talk was about, as well as referring to is basically using pre-compiled and using the optimized interpreter. Basically, Ethereum 1 is just as fast as E-wasm. That's a non-optimized E-wasm. That's how I understood it. So at this point in time, they're using pre-compiled and optimized interpreters to get really fast speeds, but E-wasm will be faster. So what I understood right now that when we write a smart contract, we compile it. Byte code, let's say, byline code, not byline code. It's in between. The EDM is going to interpret that code. However, the E-wasm is an embedded code that's going to be compiled to be native code. It means to me that there is a hacking to the virtual machine itself that should run that code, which means that when it reaches the area of the native code, it's going to start executing it. Is this correct? So at this time it's not a compiled. It's still interpreted. Is that also what they're talking about? So that's what they were talking about from the talk yesterday. There are certain problems with using a compiled VM, especially security concerns with a jet bomb if it's a jet based one. Actually, could we bring this up so that the next slide is visualizing this a little bit? So from a classical standpoint of view, the way we build dApps today with solidity and stuff, for example, we run it through a solidity compiler, and then you get an ABI and a Byte code, and then eventually the Byte code is what ends up in the VM. That's how I look at the chain that lets you talk to your contract instance. Actually, very similar, is what happens with E-wasn't as well. Instead of writing your code, all of them you can write in solidity too. It doesn't really matter as long as it transpiles E-wasn't eventually. So you have your code, at this point you can use C, C++, Rust, or NIM, which we touch on in a second. You get your E-wasn't code out of that, and then that's going to get run inside of that E-wasn't environment. You still get an ABI code as well, so it's not in the graphic right now, but you get the idea. From a flow point of view, it's still the same process. You're just dealing with a different language and a different format. It wasn't itself directly in the EBM. So it will be dual stack, so at the point that they visualized this, it would be that you have a mark over when you deploy, and it will know it's E-wasn't, and you'll stack the E-switch between them. I'm not talking about deployment, I'm talking about compilation. So E-wasn't should be compiled to be understood by the EBM. Yes. Well, but... Yeah, so that it's... Yeah, like so... It's just actually an otherwise run time, if that makes sense. Okay, so from C to E-wasn't, some sorts of compilation. Yes. That's going to generate a code that could be understood by the EBM. Well, it's still a wasm run time that has EBM hooks as functions. I can show you later as well. We'll do it all down for you. Thank you. Good answers as well. So in continuation to that, in a different perspective, can we call that in a web-asm-plea-native run time, we have a metering library or something that... talks to completely in a different perspective? Yes. Because that is the missing piece, right? Yeah, if you look earlier at the slide, there was about... the metering currently gets injected, but you could still do the metering inside the servers as well, which is what I would prefer, but I decided to inject the metering. So it could be still treated as a package of a library that can transform the... Yes. Sure. All right, so eventually what that means, given what we've just seen, the benefits of using E-wasn't would be, first of all, you can actually write your smart contracts in any language. Anything that transpiles or compiles E-wasn't, which is kind of cool, but then you don't necessarily just tie to Solidity or Viper or whatever. So, originally, it's going to be a fast execution. There's also better library support, because, you know, since you can use any language, you probably can take advantage of a very big ecosystem of libraries and plugins that your language supports. And then, after all, there's also a community that E-wasn't is an open standard, so we have a lot of people who talk to about this stuff, but I can help you as well. All right, so, given that, we will touch a little bit on one language called NIM. That's the thing that nobody has heard about in the industry. And also, there's another expert here in that language. And so NIM is just yet another language that can compile or compile to E-wasn't. So, it's one potential candidate for you to write your smart contracts in the future. So, what is it? NIM is a Steadily Type Compile Systems Programming Language. If you look at the language and we'll see some code in a minute, it looks a little bit like a mix of, I would say, like JavaScript, Python. You, like, smash it together, and then maybe a little bit of touch within there as well. So, the idea is that NIM, it aims to be very expressive and elegant and, you know, have a very intuitive syntax. And it aims for native performance as well. So, if you look at the website, the official website here, there's this features section, and you also see already some code there. But basically, it, you know, it claims that it has native performance with the state of the optimization. So, the point here is that NIM actually also compiles to, like, C code, which means, you know, you can put the C code through a C compiler, and, you know, those are really optimized these days because there's, like, four weeks of experience going in there. And so, yeah, that's a pretty good thing, I guess. So, yeah, that's why we have here, you know, translation targets, like possible ones, or Cs2++, JavaScript, if it wasn't. Even JavaScript, so that's also pretty cool. Like, if you like to build web applications but you don't like JavaScript or TypeScript, whatever, you could use NIM, you know, that's your jam. And what's also really cool about the language itself, which is kind of like a key point here of this whole thing is that it supports data programming using generics and macros. Now, why is that interesting? So, first of all, some NIM code just to get a general idea what the language looks like, right, Python, JavaScript, smash it together. It looks kind of like that but it's just some weird indentation syntax as well, I think. If you're not used to that, it looks good first, but I think, you know, it's just a matter of getting used to it. So, you see there's like different things like iterators and you can create your own types and object structures. There's important statements as well, you know, if you've used any other language, you should probably get an idea of what this stuff is. So now, but macros, you know, being one feature of that language, has anybody used macros before in any other language, you know, from all the time? Okay, so for those who don't know, special functions that execute at compile time, so you can basically define functions that expand to the language that you're using and that expansion happens at compile time. And that essentially enables you to create custom domain-specific languages, which is a very, very powerful thing. And, yeah, so here's, I'm probably not the best example. You don't have to read and understand this code. I really just took it from the website just to give an example of what a macro could look like. And then, this is a debug macro. You see, like, you define it with a macro keyword and then, you know, you give it some, some logic and tell it what to do.  So you can find an array here, a string, and then we pass it to that function. So it looks like a normal function at this point. So you might wonder, like, what's the point really? You can just use all functions over there. But then, it turns out, you can actually go, go way beyond that. Again, like, if we, if we come back to the, the idea of creating a DSL, you can have some language that would, you know, with its own semantics that gets very powerful. And there's, there's this project that this guy is working on. It's called NIMPlay. NIMPlay is exactly that, right? It takes the power of macros and creates a DSL for smart contracts. Again, keep in mind, like, NIM transpiles to EOSP as well. So you basically get smart contracts in NIM that you can transpile to EOSP and then, essentially. So, right, NIMPlay is a domain-specific language for running smart contracts using NIM macros. Again, given what we've learned before. Essentially, that means NIMPlay is just a set of macros and, yeah, it takes care of, like, expanding it to NIM code. All right, so, another cool visualization. So, you write your NIMPlay contracts. They get expended to NIM code. So you, actually, you write NIM but you use the macros syntax. You expend it to the actual NIM code. Again, the compile time macros are executed at compile time. That code, that's sort of maybe in your contract code, right? It's going to look more familiar to you and easier to write your contracts in NIMPlay. It would be to write them in NIM by itself. So, it's kind of like a convenience feature. Yeah, right. So, once we expended that to NIMP, again, the whole process starts to oversee transpalting. It wasn't from there. It ends up purchasing. And, again, just to stress it once more, essentially, this could work with any language that transpalting wasn't. Ideally, it supports something like macros, like Rust, for example, is the same thing. And here's the sample code. This is our go-to example for a very simple smart contract that simply stores, you know, simple storage, like sets and gets a value. This is a simple storage contract written in NIMPlay, essentially. So, just that you get an idea. There are probably some things here that, you know, don't really... I think the main functions of construct is not really supported at this point. So, you get, like, an hour demo that little children are not going to be there, but just to get an idea. Take some pictures. It's good. But really, the important thing to look at are the first two methods, the two procs, set and get.  So, imagine this is a contract employee and, you know, in Ethereum, you'd be just calling the set method to set the value of the contract and going to get... So, you'd be sending a set transaction and calling the get to get your value up. It's very simple. I'm going to show you this. Is the main here representing the constructor? Well, we don't have... I haven't done the constructor project. It requires a different transaction to be bolted. So, the main is usually in... The actual entry point is usually just like salinity, or, I know, you would just have a... It'll probably change the syntax that you say is just a constructor. It still works that way. Because, like, main is a bad word to use for that structure. So, top-end of the transaction. Yeah, and in salinity, we don't have entry point. Uh, except... Yes, we don't. In salinity, we don't have the entry point because of the way the language works that it just starts executing from the beginning. But in wasm, we have an entry point which is usually the main function. Yeah, like a main exported function. Any other questions? Okay, cool. So, there's this thing. Uh... Small problem. Small problem. Spoiler alert. So, if you take a little bit of the installation instructions and if you happen to run other machines than Macbooks, for example, uh... Installation of NIP play can be... can be a little bit hard. So, there's, like, this whole process that you have to go through. And, um, now, to kind of, like, draw the line back to NABARC, you know, the tool that we work at, who's used NABARC before? Who's heard about NABARC before? Wow, okay, that's really cool. Check out NABARC. Yeah, I mean, I think this is really good for you to be here. By the way, you have 10 minutes left. You have 10 minutes left? Okay, then you really do get going. All right, so, um... So, basically, what we want to do is 15 minutes. Okay, I want to slow down a little bit. So, since this setup is this kind of hard to do, um, we want to help with NABARC, which, we're going to dive into it in a second, um, it's basically a tool that helps you build decentralized applications.  So, if you want, that gives you, like, all of the different features that you need to make the process very easy. And one thing that comes with it is basically a plug-in ecosystem and a plug-in API that enables you and us, but also you, um, to extend NABARC and its features. And so, you can basically also create a plug-in in that, you know, a key system, right? So, to give you a little bit of an idea of what NABARC looks like, it's a command line tool. You can run it on your command line. In the NABARC project, you get, like, this dashboard that tells you who are the contracts that we're compiling and deploying. You get, like, logging outputs, you know, transaction hashes, gas costs and everything.  Yeah, what? Yes. What are the contracts through that interface? You can top-level it as well, which is pretty nice. Oh. Oh, by the way, this is Michael over there. Sorry, I took the wrong train. Or the train going in the opposite direction. We have the father of NABARC here as well. You, Ray, and Richard, and other team members. So, you can talk to all of us. Speaking of cockpit, there's also web interface that comes with NABARC. With NABARC, you can basically it spins up for you a web server with cockpit, which is all one flight. Basically, that's your intent in the same way, but in a bit more rich way, I would say. You still have the rebel there. Yes. It's kind of like what you get at the CLI just on steroids. All right, so, and then, again, there's plugins. Like NABARC has tons of plugins. People can build plugins. There's an API. So, you have plugins for remakes, ethos, scans, sellers, snarks. With X. Yeah, with X. There's like tons of stuff. Again, you can build your own. We have docs here. So, in case you haven't heard about NABARC before, so go to NABARC.status.im and then there's like, you know, we put a lot of time making our documentation as good as possible. So, there's lots of docs about how to do things like creating plugins and stuff. And so, yeah. How cool would it be if we could use NABARC and new play and create a plugin that makes this whole process easy so that you can actually go ahead and write your smart contracts in a language like NABARC. Ideally, it would look something like this, right? So, like step one, you would install packages. You wouldn't install NABARC. You create a new project with it. There's a new command, right? You would CD it to it. You would install a plugin, something like NABARC new compiler for example. Configure it and then you're done in an ideal world. And I'm very happy to tell you that Eric is going to present you that. By the way, this is like what the plugin configuration could look like. There's an NABARC JSON file coming with every NABARC project. If you have other plugins, usually they come with their own custom properties that you can configure them. In this case, we don't even need to configure any configuration here. And, yeah, we go over to Eric, to the right corner. So, I am going to show you a demo first. I'm going to show you the demo first. And then, with the remaining title, kind of digging into some of the turtles, but and then there are any questions as we go. One thing I forgot to do before this, some of this is going to take a little while, so I've got my elevator music on cue. All right, so okay, so what we're going to do is we're going to do some before there was an embark CLI command. So we're going to run, we're going to do a embark run. That's actually going to spin up our dev, so I'm just going to do a embark run. Oh, yeah. Is that maybe too much? So, what this is going to do is it basically spins up all the services that we need to run our dev. So, so you can see like Pascal showed in the slides. Here's our dashboard. And this is basically starting up it's starting up a node for us, a local node. It's starting up any storage services that we might need, which we don't need. We don't need communication services like Pittsburgh, which we don't need. E&S services as well. Again, we don't need that for this demo, but it'll do that on all fours based on our configuration with that. So, as you can see, what it's also done after starting up the node is it's deployed our contract models. Well, it's if you look at the top here, it's deployed the simple storage one. This is our solidity contract to the top one. Now, the one underneath it is the exact same thing written in. Okay, so the code that we saw before, the simple storage written in, that's this guy. And it's taking a little while to deploy because it's on Testnet. We are connected to our own node project thing. No, I'm pretty sure it's the Wi-Fi. It's gone into the Wi-Fi. I mean, it has to be the Wi-Fi, right? You can try it once again, otherwise it's pretty short. You can try it once again, then otherwise it gets pretty short. So that you also test that currently it's very small. There's not a lot of nodes. Things can go wrong. It's one of the downsides of this right now. And a lot of it has to do with the fact that EWASM is undergoing a lot of changes. Anybody go to the EWASM workshop yesterday? No. Did you guys already talk about that? That's what happens when you take a late train, man. I took the wrong train. That was a problem. Thank you. It's important to know if our contracts are on the track. And we can wait for this. Can you open this to show the contract? Yes. All right. Show the code. Up, up, deploying, come on. Show the code. It starts with the receipt. Okay, so just to quickly show you the file system of our DAP. This is actually not a DAP. Just give me a second. I want to let this deploy so I don't mess this up. All right, fine, fine, fine. It does, like, work. Fantastic. I'm running that most of it. Hey, what? Hey, you're right. All right, so let's check it out. So basically, you can see here we've got a web server that's spun up. This is for our front end. This is for the DAP. And also we have a web server server for company. That was the screenshot I was going to show you before. I think these are working like all the services are working. You can do that using this link, but we're not going to do that today. We're just going to look at the front end of our demo, which is a really, really small React demo. I've got a few from open already. So, green lights. Hey. All right, all right, all right. Okay, so it's slow on just that. Can you see? Oh, yes. So we have two tabs here. One is for the solidity contract, which is this one that's showing right now. And then we have the NIM contract. So we're just interacting with two different contracts. This is all using what embark does in the background as it co-generates an object for us, like a contract object that we can then call methods inside of the contract. So for example, we get a value that's stored. If you guys remember what the contract looks like, just getting a value that's stored in the contract. The value is 100. So if we then change that to 53, set, that will eventually get set. It's just a bit slow because it's untested. So, at some point it's going to change. So I have a question. Yes. Is it because you're using the block here, I need to go back and sign transactions? Yeah, this is a good question. So the question is like, and the way embark works right now is you can configure wallet accounts inside of your configuration for your debt. So when you want to go create a transaction on the front end, instead of signing a transaction using metamask, embark will actually send a transaction through embark's proxy. And embark will pick it up and say, hey, you're trying to send this transaction. Is this from an account that embark controls the wallet? If it is, of course we have access to the private key, we can sign the transaction. In development. Very important. I mean, embark becomes your wallet at that point. So this was working. I promise. This isn't so difficult. You can imagine that the value usually is set and you can call and you can send it in one way. Let's try this in one way. This is not just mining. Nope. Nope. I'm trying to help you. I'll show the code while he's setting this up. So, basically this is, I'm sorry, you know what I need to do. So this is the contract that we're looking at, but I'm going to show you the file system a little bit first. So if you look at the top level of our file system, there's a few components here. The front end stuff is under app. We've got our configuration files under config, contracts under contracts, a disk, obviously. There's no front end. The only thing you need to really see here is the marketing system. So, what's cool about this is that you can see where our plugin just set up. Okay, so we've got this plugin here. This option is, we don't actually need it, but again, as Pascal was mentioning, you need custom options for your custom plugins here. So, don't worry about that one for now, but you can just see that we have the compiler plugins set up. That's how you install it. So once you have them installed into your app, you just enable it using as an object of plugins. So, in our contracts, we've got our simple storage solidity contract. So, we can set up the value, and set stored data to that value, and then we can also do the same thing that's set, so we can actually set the stored data value to where we pass in, and then to get, just pull it up. I think crazy. And looking at NIM, it's exactly the same thing. So, we can set a value using this set function, get the value using the get function. Quickly looking at config, there's configuration for blockchain. So, how you want to configure your node, and any of those accounts, like those walled accounts we were talking about earlier. So, you can basically add a mnemonic, and sign transactions that way. Communications for things like whisper, if you want to add a whisper to your three, it's left. I'm good, I'm good. How are you doing? It's good to be pleased, man. I'm pleased. All right. So, to look at in these, I don't want to get into these, but once you start looking at it, it's a lot to see. Any burning questions? Yeah. Well, I was just wondering, is it possible currently for this simple storage NIM contract to read? They don't like this sort of simplicity, that storage out of the solidity ring one? Like, how do these two be? So, currently it doesn't do a stack? No, no, okay, currently. But I think the idea, well, at the point when they made it was that you can switch and then, yes, you'll be able to read the same story. Especially with you, when you think about, like, you're going to have to hard fork at some points and then you'd have to run for a few years. So, you'd have to. That sounds hard. Great. Sorry, and I was going to show you just quickly in the last few minutes we have, and this is just full of NIM works. What did you say? Because there's, like, one thing that you might be interested in. You're going to stay here. All right, you can see this. Wonderful. So, you see there's this message of value set to 100. I did not just code it in there right now. I actually set the value. So this is the NIM contract right now. I set the value to 100. I'm going to call getValue. Can we change it? Can we change it? Yeah, let's do that. Well, should we get a number from the audience? Yeah, yeah. Let's pick a number. Any number. There was no clue. There we go. Any other numbers? No, no, no. Get the number. Let's get another number. Yeah. Thanks for warming them up. Okay. Yeah, well, you see this works. So what is the version of NIM? Good point. This is a custom development version that you don't have right now. Now, if you install, like, at this point, it's a version that's, like, latest master running on. Yeah, you can see a little bit of the program.  And you guys have tested it? You see it. And then the two set functions that you called one earlier when you were looking, and then you called the 100 actually. So yeah, it was 100 and 101 probably. Yeah, and then going to go into the transaction and then forwarding on the contract. It's quite cool. You can pay, you can even browse the data. You will hold on the contract to the two. The two. And then 0x49. 0x49. And then your storage tab. Cool. Yeah, so this is actually cool because we can, some of the things that we've discussed before. So here you can see setting the value. And then it does 0 because it's the first variable in the contract. So you just ping them into that. And then if you check the last code where I can share someone asked about the gas injection, and we'll see this is the calls in the current field of how the injection was. So they do a single pause and they make JP's.  Any other questions? Okay, well then I have a question. Yes, because you don't want to write your own interpreter? So it was, I don't know why they did it specifically, but I think it's because they wanted to test all the interfaces and compile time available. And not all of them exposed the interpreter to do for the county. So doing it this way allowed them to test all of them. You found the star.


Here is a method to get anything done to overcome procrastination and make progress on your dreams. The method is called act ACT Attitude Chunking and timing So here's how it goes When it comes to anything on your calendar that you need to do anything in your schedule I need to do item Okay, just if you if you feel yourself having some resistance towards it some procrastination Just bring in this idea of act Attitude chunking and timing so so a for attitude. What does that mean? It means to do whatever you whatever practice you need to do to bring yourself back to a positive mental attitude about the task at hand about the dream that you can do this that Everything can be approached with experimentation That you are taken care of forever by a higher power and that this is that you're truly going to be okay and That whatever you set your mind to and you and you take step by step you can absolutely accomplish Okay, and that brings us to the C in act a for attitude C for chunking chunking means to put your The the project or the task Write down the smaller steps for that task or that project so that every step feels very doable for you Chunk down this large project into smaller smaller bits so for example if I'm writing a blog post and I feeling intimidated I'm like seeing this blank screen and I'm like How can I possibly write a blog post? Then I write down what the smaller steps for writing a blog post are for example. I'm gonna write down Okay, quickly jot down three ideas That I might want to write in this blog post step two Quickly write an imperfect first draft step three take a break step four Come back and edit the draft into something readable So that's chunking down even writing a blog post You can chunk down building an entire business into smaller smaller steps that you can you feel doable for for any step If it feels still feels too intimidating too big you can chunk it down even further Write down those small steps. Okay, and then finally the T stands for timing Timing means to put some kind of time boundaries on whatever it is You're working on on those small steps so that you don't spend too long doing it so that you can actually approach it for me I actually set a timer For each step so for example if I were to say quickly jot down three ideas I might say well, I'll do it in five minutes just quickly jot down five at three ideas in five minutes So I'll set a timer for five minutes, and I'll go okay. Okay, great Let's play this game of jotting down three ideas, and I'll approach it with playfulness with experimentation with adventure Just to quickly jot down those ideas So that's what timing means to set some time boundaries around each step so that you don't spend too long doing it And that you can bring more of your your energy and your your playful attitude to it now Setting a timer doesn't work for you then then don't worry about that You can use timing just to put things into your schedule so that you're more likely to do it put those smaller steps Into your schedule when are you going to do this step when they're going to do the next step? Approximately so that you'll at least be more likely to do it if you put some time boundaries around that So I hope that this is helpful You can use this method of act attitude Chunking and timing whether it's a large project or a large dream or there was a small project that you feel Some resistance to some procrastination for so I hope you'll give this a try and Feel free to let me know if you have any thoughts on it any experience with it or any questions about it I hope this helps take care


Hello, number one, happy new year, get back safe. And the reason y'all are doing what you're doing is allowing us to live the way we live. So we wouldn't be able to do what we do without your service, so thank you. I mean, I hope that if you do get a chance to see this movie that you'll relate to it, you'll think there's some truth and then hopefully that others, you know, I mean, we do live in an age where movies, for better or for worse, can have a huge impact. And if some people can understand the sacrifice of a warrior, of someone who decides to give up their life for their country, what that actually means on a day-to-day level, not only for them but for their families. Well, you know, it was an interesting road. I mean, when I first was interested in the project, it didn't hand him with Chris Kyle. He was alive, very much alive, and he had written an autobiography called American Sniper, and I loved that war genre. Ever since I was a kid, sort of obsessed with it, and I thought I hadn't really seen a character study lately within that genre, and I thought he was such a dynamic, charismatic individual ripe for cinema as is Kyle. Clint and I just decided that we wanted to make this a pure character study, and if we got it right to any degree, hopefully it could serve two purposes. One would be that those men and women who serve can relate to it and maybe not feel so alone by their plight, and the other would be the 99% of America that have no idea what it's like or know anybody in the military would say, wow, maybe the person that passed me in the airport I'm going to stop and not just say thank you for your service, which does mean a lot, but take it a step further because our vets are coming home in a greater number than ever before. Thank you for your service, and again, you know, what you do is something that I don't think many people even can fathom, and we owe our freedom and our liberty to you. So thank you.


Hello, my name is Tama Munt and I would like to present something about databases, but let me introduce myself first. I started to work on libraries around some years ago, with a really clever database management systems driver for libraries. After that, I started to work with Kolomotor, with lots of things which are not related to databases, or databases of the group. But after that, I worked, and it was in the winter, I worked on the database foundation part, which I want to talk about. First, let me ask a question. Do you know what your database is? I think I've already used it. Hands-on group. Yes, thanks. That's half of the group, which is positive, because the other half just made me just lazy to put the hands-on. Thank you very much. Then I would like to talk about what are the main topics in my presentation. I would like to talk about the continuation of them. I will go into detail of the development process. Then I would like to suggest further development, opportunities after that, if I have time, that I will make a demo of the migration thing. What is it all about? We have this database, which is the run-hand of several database management systems. We had the opportunity to store our databases embedded into the ODB farm, which in this case, we can use SQLDB or Fireworks as a backup. There was this idea that not SQLDB should be default database management systems, but Fireworks, which is good for several reasons. For example, we want to get rid of the Java code in the Office Store, because it's a big dependency, and we don't want to shift that into the graphics art. We don't want to use it to configure such things. Another, more complicated, is the developers, because SQLDB is a Java case, and because of that, we need to use Java from C++, that means through Java native with API, and because of that, it's hard to move back. For example, if you press backtricks from GDB, you can't see the actual SQLDB code, just the mapping to the Java code. Another thing, I think this is for the priority, but it's just my opinion. It must be my own performance, and that means that C++ native code should be faster than Java code. And I found the question which is interesting. We use SQL and the answer would be for that, in my opinion, that SQLite is a feature of each SQL Fireworks, and my opinion from SQLDB to SQLite would mean that we lose some features. Okay, so now we come to the tender. GDF has probably done a lot of this migration thing. When we want to migrate to Fireworks, we have to make a bit able to look at points on database files even if there are no Java points that we use, which we use to promote this database. But before that, the Fireworks driver will be less likely to lose some features or that it cannot be... If you can't notice the migration, that's not just possible. Before that, I implanted that we finish the migration of some types in the Fireworks driver, which we did for the migration, and there was also another part which was about popping integer values from Firebase. It was quite interesting that I wouldn't have to go into detail there. Before I present my solution for this migration thing, I would like to introduce the form of SQL Database. Can we look at the ODB files and see if it's actually... You can find it in the folder on the database, and there are two files. One is the text file on script, and there is a data file. The script file contains the Schickman definition as in a form of a student, that means a great table, my table, and so on. And some other information, for example, it shows us that it should be in the data file. That means, for example, if I have a table on my table, I got a form from the script file, and the data from my table is located at this position in the data file. If you can see that, but it's not that important, that's the script file. The script file contains SQL, and I want it to highlight one row, which you see about it, probably, as I told you. Whatever, so this is the position in the binary file where you can find the data of the table. We actually have to look into all this in the Schickman definition, where we migrate the data, and we have to write it among the other database. Again, the other part of the course is to be entirely binary file. This is the figure of AVL3, that's a balanced binary picture, and I got to know that the SQL database stores its data in that format. It was about logging the source code, it wasn't much documented, but the source code was really understandable. I wouldn't have to go into much into how it works, but when we had the Schickman information from the script file, we could look at the binary data, and the migration tool, which is interesting from here, might be that this browser is the main class, the only class in Schickman that's outside of this migration tool, and you can call this SQL database to make the migration process, and it needs two fields, the storage which, which tells us with which we can access the internal files, so the script file and the data, and this connection is part of the SDBC driver, which is the abstraction, we learned the base connection, and we need that in order to execute the commands which we had found the script file, and we can set the data through this connection. And there are two main parts of the migration tool, the Schickman constant, which is under that, it's a great response because of all the read again, and then the definition, and this, this is a response, a part of the response in both words, reading the binary file. Okay, now I would like to highlight the interesting challenges from that. The first one, a lot of, reading of the watch, if not that interesting, but it's an example, if I look into the pattern structure, so the data file, let's say that one's in different, and say it's x down to the files of the diagram, so it's internal structure, and I can see the four bytes, which are the size of the watch, and that's the thing that's, I think, complicated. I had some trouble with the numeric, dancing one, and the types, because it was representative in the binary files, the big Java ones, which is an integer format. It's something like an integer, but it can be, if it's longer, longer than an integer, and I had to convert it to string, because the representation of the string, because as it is, it uses that for communicating the decimal numbers, and I, first, I tried to make a binary algorithm, and that was, that was, that was, so I was happy with that, but then I would make an internal and then I would convert it into an algorithm, and work that, and it works just fine. I thought that stuff, that I had to do, was the migration of the time, and so, that's interesting, because there are three different representation, the ethnography, the history, the history, as the time from 1970, as the history starts from zero, and fireworks start the test time from nine, from 100, 100, 1,000, 100. So, I had to convert each one of these tasks, I made some tests, I think that's that interesting, and yeah, another program, with the time, the migration of time, in Turkey, it's the values, as an operation system, time zone, dependent format, that means that, if you run legal office base, not the user way, you update your date in time, before you issue the comment, for example, the time zone, then you realize that the date is changed, and I think most of the discrepancy would surprise about that fact, although fireworks knows time zone westerns, there is a lot of people who may come in version, but yet it's not happening, and it's possible to create a pop-up window, which, as the user, demands, is that, as the user, it's not happening.


Hi, I'm Nick Gillespie, an editor-at-large at Reason, your source since 1968 for everything related to free minds and free markets. We're in the middle of Reason's annual webathon. The one time each year we ask our online readers, viewers, and listeners to support our principal libertarian journalism. We're trying to pull in $400,000 in new donations, your gifts are tax deductible and go directly to funding our print journalism, our video productions, and our podcasts. What's more, they're being matched, so every dollar you give goes twice as far. If you like what we've been doing and what we're going to keep doing, please give now. Go to Reason.com slash donate for giving levels and associated swag, some of it's pretty great. And from all of my colleagues, thanks.


Hey guys, welcome back to my YouTube channel. This is Daniel Rossell. Today's video is going to be a quick one about how to create a banner image in YouTube before your YouTube channel using the GIMP open source photo editor available for Linux Ubuntu and other distros really really amazing tool. So basically this is going to be just the really really simple part of it. There are other videos I've seen about using GIMP for this purpose. They show some more features I'm going to show less in the way of advanced stuff and actual logo creation I'm just going to show the kind of how to get going with it parts of this. So basically Your YouTube dimensions are currently as follows. They are 2560 by 1440 pixels, right? So what you want to do in the first instance is create a banner for yourself in those dimensions And I've gone ahead and just filled it with white. So it's just white color there and with those dimensions Now the thing about YouTube is that if you put stuff here or here, it's not necessarily going to make it into It's not going to render on all devices. So, you know, if someone's looking at it from a phone or looking at it from a tablet It's not guaranteed But YouTube does give you at the time of recording and I say that because the dimensions tend to change over time. At the time of recording the text and logo safe area is a 1546 by 423 pixel Rectangle that is centered on the on the horizontal and vertical axes on the X and Y So all you really need to do to make sure that you're the logo you're designing in a GIMP You want to basically keep your artwork and your logo within this area and so that it's it renders basically, okay? So here's what here's the method. I have been employing to do this So I create a new layer and I call this layer the safe text area guide now firstly put plop in those dimensions, which are going to be here 1546 and 423 now if you want to be smart, there is a way to be smart. You can subtract 2560 Minus 1546 that's going to give you a number. Sorry. I can't remember what number that is divide that number by two And that's going to be your Y. Sorry. That's going to be your X offset The division by two is going to make it equal on the equal on both sides and then you can do 5th sorry 1440 minus 423 and then divide the Divide that number by two and that'll give you a that'll center the image on the Y axis Okay, that'll make this and this equal and this and this equal But you don't even need to do that But that's what these that's that's if you want to use these offset X and Y and save yourself a step You can do that. I'm going to give the four. I'm going to fill that up with the foreground color so it stands out now click okay, and what you're going to get is the guiding rectangle if you will But the problem is that it's not in the right place. It's just stuck there on the left So fortunately there is a tool in GIMP. It's called the align tool and it's pretty now So I use the legacy icon set most people clearly do not there was the the most recent one But if you have the legacy set, it's the alignment logo is this one It's pretty logical because it's got four little arrows left right top down and the rectangles in the bottom So click on to this guy and then click the layer you want to align. That's important You need to actually click on the layer in this case this box, right? So when I did you got these four little Grabby things on the side of it. Sorry. I don't I don't know the correct name for those Then I go out of your layer option tab and click into the tool options tab Now I want to align even though it doesn't make a difference in this case Just just as a best practice we're lying it relative to the image So we're centering it on the entirety of the canvas and not anything else And then it's really easy. You just need to do two clicks. This is going to be a line in the center So now you can see it is perfectly aligned There and if we were to measure this area in pixels and this area in pixels We would get the same as if we subtracted two five sixty from fifteen forty six and divided in two And then we need to do it like this and now we are good You can just see visually that's right slap bang in the center of our canvas. So this is all good So now what I do is I just kind of create a new layer And I just kind of you know, I'm gonna actually build Into this layer and I let's say want to put a bit of so I just feel that was the background color Text goes here Now that box we're seeing is the safe text area So you wouldn't want to necessarily want to fill it all the way up as text But just in case we did for whatever reason So long as it's with anywhere within this rectangle, you're good to go So that's why I give it a different color other people do that alpha two selection and do other tricks This is my methodology now You might be wondering well Is that ugly rectangle going to render in this ugly logo? The answer is no all you need to do is get your logo as you like it get everything good Make sure everything's in the box and then before you export simply Make the guidance box invisible and what you can do is save this as a file and you know When if you want to work on the logo of the artwork a bit more You can just turn the guidance box back on turn it off and then export when you're actually rendering your artwork For YouTube and that is it That's the quick and dirty method for creating a YouTube cover image artwork using the GIMP open source photo editor


Hi everyone, Joe from jaskiescasebreaks.com, coming at you with brand new release, 2020 Panini Legacy Football 6 Box, half case number 2, random team break number 2. Let's hydrate the vocal cords a little bit there. Alright, big thanks to these folks for getting into the action, really appreciate it. There are all the teams right there. Let's roll it, let's randomize it, 3 and a 1, 4 times for each list. 1, 2, 3 and 4th and final time. After 4 we've got Thomas down to Mike, 3 and a 1, 4 times for the teams, 1, 2, 3 and 4. After 4 times we've got the Los Angeles Charters down to the Falcons.  That's right Robert Tucker, go Raiders. Let's sort by Column B, hopefully this will be a big step forward for the team. Alright Sub-Rex, alright so remember in the previous break I marked these boxes 2 so you know that they're from the same inner case. Bricks 3 and 4 are in that inner case, actually you can see it a little bit better on the top so only you can see it on both screens. There it is right there. That's 3 and 4 are there and that's on the site right now. I'm going to pause the video and when we come back we're going to see if there's any trades and then we'll have the break, stick around. Alright welcome back folks, there was really not that much trade chatter. So here we go with the break, thanks for hanging out with me on a Friday ladies and gentlemen. The final print out to make it official, appreciate everybody getting in, remember in break number one marked these boxes with the 2 right here so you know that they're from the same inner case. The next inner case, next half case inner case break is in the store right now, jaspyscasebreaks.com if you're watching live and we can do some more tonight. And I think there was a checklist in the chat, we'll be going by that checklist for the rookie autos, they're still in their college gear in this set. I'm not sure when the first pro gear product is going to come out soon, maybe in a couple months. There we go, box one of six, good luck everybody. So we'll go through this a little bit more quickly this time now that we've got a good first look at it in the previous break. There's Leviska Chanalt Jr., people seem to really like as a receiver. That goes to Jacksonville, that'll be for Connor, Jaguar's on the board. There's George Kittle of 25, there's Harrison Bryant to 150, all of those will be sleeved and top loaded before they get sorted and shipped out. There's Minis in here too, there's Peyton Manning, you've got Tyler Johnson, Cracked Ice, one out of ten, nice low number on that. Tyler Johnson is a buccaneer, that'll be Leonard in Tampa Bay. And we've got Desmond Patman, kind of as a cool autograph. That'll be for the Blue Horseshoe, Denny Annapolis, that'll be Ron Colts. There's Boomer of Science in the 199, there's Tyler Lockett 75, another little mini, Tom Brady. Next box, box two. Alright, let's roll. Got Peyton Manning to 299, got Alvin Camarita 150. And there's Cam Akers, rookie autograph, I think he is a Ram. He is. Los Angeles Rams, that'll be for Matt Buckler. Nice. Some good headmanship I feel like in this rookie class. In a broad sense, relative to the last couple years. I feel like the overall grade, the average grade, will be better than last year's average grade. Even the guys that just sign with two letters, I think, still have a little, there's still a little flair to the two letter autographs as well. So that's always appreciated. Alright, there's Desmond Patten again to 100, and we've got Hunter O'Brien from Washington. I learned last break where he went, and I've now forgotten, that's Harrison Smith, I know where he is. Cleveland Brown, that's right. Cleveland, that will be for Kyle and the Browns. I'm still in early season workouts, preseason workouts on learning all those names. There's Tyler Higbee for the Rams, we've got a mini Drew Brees, 71 out of 75. And we've got Tarell Davis to 100, timeless talents for the Broncos, my rivals. I like this under the lights car too, for the Chargers, Justin Herbert, all of these rookie car dealership, of course. Next to one, Hunter Bryant, what did I say? Oh Harrison Bryant is Browns, Hunter Bryant, Lions, correct. Nice Mike Tower, saving me from disaster. That goes to Mike G instead, dodged a bullet. Yeah, there's a little bit of a Ginterish vibe in here, Mr. Mike's eyes, for sure. What's going on? There's also Tare cards in here, just like a Ginter Ripp card. Two would be nice, Dan, full disclosure that we did pull one in the first half of this break, in random team number one, but who knows, you know how Colation B sometimes, could be another one. First one was a patch auto, second one could be another just regular auto, not non-patch. There's Kennedy McCoy to 100. And the Tare cards, the Dare to Tare cards are one per case, according to Adam S. There's Joe Burrow to 25, nice. I'll go to the bangles, that'll be for Derek Bratton. One per inner case or one per master case? There's Grant Delpit. Grant Delpit is a Cleveland Brown. So there's the Brown for Kyle. I don't think there's any other Delpits in the league. I won't confuse that one. All right, to 150 DK Metcalf. So Adam thinks maybe he thinks one per inner. I guess we'll find out in a second, because we didn't see a Tare card in the first half. So maybe a Tare card in this half. Henry Ruggs for my Raiders. And Shimala Adams right there. Raiders could use a, well, I've been a lot of teams could use a Shimala Adams, but Raiders could use a Shimala Adams. Raiders defense needs a little work, a lot of work. Shimala Adams would be nice. All right, there's Jalen Ragoire. Matalio, what's going on? Yeah, it is indeed Friday. Happy Friday, everybody. Although this is my Thursday. My Friday is until tomorrow. But for the rest of you, today is Friday. So happy Friday. And we've got a hit. We've got Brandon Ayak. I think is a niner, if I remember from the last break. Yeah, San Francisco 49ers. We had one in the first half of this inner case. That'll be for San Francisco Scott Corwin. All right, Matalio's Monday started Sunday. And Adam S. just finished office weekend. I mean, in the time of COVID, does do days matter anymore? I feel like they're all just mixed up for everybody. All right, there's Vaughn Miller, Broncos, Tom Brady. Just apparently he thinks COVID won't affect him. Just running around. That's Joe Thomas. He is a legend. Three boxes to go. Oh, that's right, Adam works at a supermarket. Be careful, Adam. So yeah, so for him, it's kind of normal. For Kurt, it's been like Groundhog Day for the last three months. Matt had to drive from New York to Virginia forward, then drove back from Virginia to PA where you live yesterday. Ooh, it's a lot of driving. Although less traffic than normal, I felt traffic in LA has crept up a little bit. But it's still a lot better than pre-COVID.  We've gotten a little bit of relief out here. And Ryan's driving around a lot too. Here we go. That's out of 25 on us. I haven't seen this. Oh, that's the dare to tear card. I was like, it's a little thicker. There you go, Cowboys. Eight out of 25. That's Thomas Riffle. It's up to him if he dares to tear. Well, we haven't done the other inner yet. So if it doesn't show up in the other inner, then we know it's one per master case. But so far, one per inner. Matt and Dan want you to rip it, Thomas. That's up to him. Or tear it, I guess, rips the other company. Panini's calling it tear cars. Dare to tear. He has until up until the time I click end recording. He has to decide. Tyler, Higbee to 50. What's supposed to be inside? This is a retired dare to tear. I don't even know how I would tear this open. It looks so difficult. I'd have to push. I guess those minis are supposed to be inside. Yeah, oh, mini-cards supposed to be inside. That's what Dan's saying. That's what I assumed. I mean, what are the mini-possibly? Do we know what the mini-possibilities are inside those tear cards? Besides, yeah, they're maybe short printed, if you're lucky. Are there any autographed minis? There's CD-LAM. Nice CD-LAM, Cowboys, I think. Yeah, Dallas Cowboys. That'll be for Thomas Riffle, another cowboy. It's out of 49. There you go, CD-LAM. Dan says, what, auto-short print, one of ones are possibilities. Brad L saying one inner, oh, it's one per inner case. Brad saying, according to him, features exclusive emerald mini-parallels. Interesting. Oh, Mr. Mike say, what's a Star Wars set? No, I've not heard about any Star Wars set. None that we have on for group breaks. Maybe it's on the Personals channel. With Ted, at Gatsby's Rakes on Instagram is our Personals channel, Instagram Live Only. So V's and Emerald, huh? CD-LAM again, Matt DeLeo saying no CD playoffs for the Cowboys. Is that the word around the NFCEs? Is that what they're saying? And there's Lynn Bowden Jr. For the Radas. One of the, we got him, Henry Rugs, Brian Edwards, few playmakers for Derek Carr. It'd be interesting to see how all these guys are deployed, how they'll adjust to the NFL, the speed of the NFL, so on and so forth, hopefully sooner rather than later. We gotta get the team used to seeing LV Radars. All right, and that'll be, there you go, Robert Tucker, you're welcome, man. I feel like Kentucky fans have reached out to me and been like, hey, you got a great player. He's exciting. I think the Radars are actually gonna use him as a sort of running back to RV2 from what I've been reading. I think that could change once things get going, but I feel like they might just kind of ease him in as a sort of special teamsy guy in RV2 to kind of give Josh Jacobs a little bit of rest, and maybe Lynn Bowden Jr. can do some exciting things here and there. So I think that's what they're gonna kind of use him as, which I think would be great, you know? And then I think they can use, when they got some speed, they can stretch the field with Henry Rugs. They've got kind of a bigger, sizable receiver with Brian Edwards, I think. They still have, they still have some, they've got Tyrell Williams, a healthy Tyrell Williams. I still like a lot, especially if he has room to operate, like he did when both Keenan Allen and Tyrell Williams, when they were both healthy and rocking for the Chargers. So that was pretty exciting. So Tyrell Williams still has some great value. I think Zay Jones is still in the mix too. People still like the Zay Jones. And then of course, Darren Waller. A couple other pass-catching tight ends there too. And the Raiders have a solid offensive line. So this is really a kind of a put-up or shut-up kind of year or two, I think, for Derek Carr. He's been doing fine. But this is definitely the year where I think he's now expected to take this offense to another level, and maybe determine whether he gets another contract with the Raiders or not. He still has three or four years left on his extension deal. There he is again, Lynn Bowden, Jr. Lynn Bowden, Jr. apparently he can throw too. So there could be some trick plays. There's Cole, Comet. You know what? I have no idea, Robert. I'll have to ask Nick about those combo teams. All right, Cole will go to Duh Bears. That'll be for SKS. About James Winston. Five out of 10, nice low number there. That's still Buccaneers' edition of James Winston. And that's gonna go to Leonard. And we've got to Sean Watson, 43 out of 75. Is this live? NBA schedule release is coming up soon? Yeah, it's those Boomer bust packs, Ryan Herald. That sold out actually a lot faster than I thought it would. Nice, we might have some on the personal side. Check it out. Ooh, this is a nice dual relic and autograph. What's that pattern there? It looks like an anchor. That's pretty cool. Nice. Kishan Vaughn. 248 out of 299. That's a Tampa Bay Buccaneer. So that'll be for Leonard and the Bucs. Nice. Is that what they say? The Commodore of Vandy Anchor down? I think that's the fur, I mean, I don't follow college sports too closely, but I think that's the first time I've ever heard that. Josh Zetz Vaughn is from my hometown of Youngstown, Ohio. He's a legit athlete, can do anything asked of him. That's good to hear. Guess what, Josh Zetz? Trivia, I don't know if we've talked about this before, but I was born and worn in Ohio. But I can't really claim Ohio. My parents moved out west maybe a year or two after I was born, so. But yeah, I'm excited. Excited about Lynn Vaughn Jr. I think he can even throw the ball a little bit too, so. Maybe some trick plays could be. I could see it's some sort of sweep and he gets the ball handed off to him and maybe he throws a bomb to Henry Ruggs flying down the line or Tyrell Williams. Something like that. So I think John Gruden's gonna have a lot of fun coming up with plays for him. These cards are out. Sorry about that. All right, oh, this is the last box. Good luck, everybody. This is a random team two. And break three and four is in the shop right now, jaspyscasebreaks.com, if you wanna run back that second inner case. So we got a brand new release there to work on, ladies and gentlemen. One of the lights, Josh Jacobs, nice. What do you number? You are, that's to 50. We'll sleeve that up and shift that out to the Raiders. We've got Yerter Gross Matos from Penn State and he is a Carolina panther. From a lion to a panther, this'll be Jake with Carolina. Dan Nelson, do we have a lot of backyard fires using all these base cards? No, we don't. Dan, guess what we do with the veteran commons? We gather them into 500 count boxes, right? A little fold over 500 count boxes by sport. And then we sell them in the shop and all the money from that goes to various charities. Children's Hospital LA. LA's best in after school program and a couple other charities that we like to support. Well, I burned them when we can sell them and help people. 29S75 Devon Durer-Nay. Eventually we'll have some of those being able to sell, well, eventually we'll be able to sell those on jasps.com on our retail website. Yeah, Jason Butcher, yeah, Warren, Ohio. There's pictures of me to prove it. I think in the family photo albums. Jersey Autograph Jacob Eason at a 149 right there. I think I have some pictures of me sitting in some nice field, a lot of open space. Colt for Jacob Eason and my Oshkosh Bagosh overalls. My Cam Acres, Jordan Loved, $2.99. And that, my friends, is that. Slide these base cards over here. All right, so no word from Thomas on the Dare to Tear card, so it's gonna stay like that. And we got a pretty solid break out of here, I wanna say. Love that anchor pattern in the background there. Nice Lin Bowden Jr. CD-Lam. Some good stuff. Thanks, that was an out of 10 Joe Burrow, Cam Acres, some Cracked Ice, and LaVisca Chanel Jr. right there. And there you go, boys and girls. I'm Joe for Jasper's casebreaks.com. I'll see you next time for the next break. Bye bye.


One of the biggest problems we face is that the anti-vaccine movement has done a fabulous job branding their message and creating this media machine. And one of the things I find with our community is that we end up, the scientific, the medical, the skeptical communities, is that we end up speaking in an echo chamber, just speaking to ourselves. And is there any body or organization moving towards branding our message, creating a media-friendly message, if you will, that people can understand, that doesn't sound like it's coming from, you know, eggheads, and that can counter, can effectively counter the message that these celebrities are putting out there. I'm willing to show my tits. So, now, as an interesting segue to that, there is a new website that hit a few weeks back, Rethinking Autism. And there have been several other efforts. So, professionally, yes, there are. There's every child by two, which is the same with the AAP. They tried to counter Jane McCarthy with Amanda Pete. There are several other professional organizations, both state and federal, which are trying to do the same thing. Again, synthesizing information, putting it all in one place. They've all been inadequate to this point. And frankly, I think we need to be fighting this on every single front that they are fighting, and with just as much enthusiasm. So as much as Rethinking Autism may not reach everyone, I think it probably is going to be able to reach at least a small fraction of people that wouldn't have had access to this information before. And as long as they're getting accurate information, as long as they are trying to help the families and reunify the medical culture with the parents who absolutely, even if they are firmly anti-vaccination, we still need to be working with them. If we don't, we're sacrificing the health of the children. We cannot sacrifice the medical care delivered to these children, no matter what family they're in.


This 2018 Chevy Suburban 1LT is stock number 12264Z. We're here at Summit Automotive in Fond du Lac, Wisconsin. You're new and used SUV headquarters. This 2018 Chevy Suburban has the 5.3 liter V8 engine. This vehicle has been fully-safetyed and inspected by our service shop, has a fresh oil and filter change. All the fluids have been checked and topped off. And this Suburban is 100% ready to go. It's got really new tires on it. Iridescent Pearl Tri-coat is the color. We shoot all of our videos in 1080p, 60 frames per second. So if you have HD capabilities on your computer, tablet, smartphone, or television, I highly recommend turning them on right now because it is your best way to check out the quality, condition, and options of the vehicle before seeing it in person. And if you like the video and want to subscribe to our YouTube channel to see all the videos we do each and every day of our new and used inventory, in the upper right-hand part of the screen is a subscribe button. Click that and then click the bell notifications and you'll get updates every time we do a video here at Summit Auto. This one comes with the factory 22-inch chromed alloy rims in there in excellent condition. This one's absolutely perfect. It's good to your Eagle Touring 285-45R 22 tires and I'd say probably about 80, 85% of the tread left on those tires. They are pretty new tires on here. Front fender is absolutely perfect. No dents or dings on that. It does come with the projector lamp headlamps, LED running lights, and those headlight lenses are nice and clear. Factory fog lights, front bumper and lower valance are in very nice condition. You can see any dents, dings or cracks on it and the grille is in really nice condition as well. No cracks or anything on there. The hood is in excellent shape but I didn't see any dents or dings or imperfections on that and coming around to this passenger side front rim, absolutely perfect. No scuffs or scrapes on there. As you go down this side of the vehicle, take note of how clean the body is, how reflective and mirror-like that paint is. We take these HD videos so if you are far away or even if you're close by, just cannot make the trip down but you're still interested in purchasing the vehicle. You can see this vehicle, hear the vehicle and have confidence in what you're looking at before you even get here. So when you do get here, there's absolutely no surprises and you can make a smart and informed buying decision from wherever you're at. And if this video helps you make a buying decision, let your salesman know that you saw the video and that Brett sent you. Back rim is in excellent condition and the back tires have just as much tread as the front tires. You can see just how nice that wheel well is. I didn't see any corrosion on there and this back rim is just about perfect. Four-wheel disc brakes on here, coming around to the back. Rear bumpers in pretty nice shape. I didn't see any major dents or cracks back here. Comes with full towing package which includes receiver hitch and seven pin wiring. Does have a power lift gate. Back storage area is very nice and clean. Those third row seats do power fold down. You do it with these buttons right here. Watch how fast these things go down. Very quick and then they always come up really quick as well. So really nice there. Do get a little bit of storage underneath there. And to get this gate down, you just press this button right here and it'll come on down for you. It does have the flipper glass as well. Rear gate is in nice shape as well. Coming around to the driver's side just as clean as that passenger's side. Rear quarter, I didn't see any dents or dings on there. Looks really good. And for full disclosure, this back rim is in excellent shape as well. Does have the capitalist fuel fill which is a really nice feature. And coming around the rest of the side of the Suburban looks really good. Doors are really nice. It has the power mirrors, directional signals, blind spot monitoring, and they're heated. Inside the 1LT package gives you the tan leather interior. No rips or tears on the seats. They're pretty nice. Both of these front seats are heated. You have factory floor mats throughout. Auto headlamps, turned out four-wheel drive. Power pedals, lane departure warning stability control has the power tilt and telescopic steering wheel. That's a really nice feature. Power windows, power locks, power mirrors. These mirrors do power fold in. I always like showing both sides so that you know that all the features are working on your vehicle. Memory driver's seat, Bose sound system will hop inside, turn the ignition on so you can check out the miles and the radio and everything that this vehicle has to offer. 36,734 miles. You do get a digital speedometer. Compass display as well. Let's see here if we can see a little info. You got to start the engine to get that digital display to come up. It has the heated leather-wrapped steering wheel. Bluetooth and information center controls on the right. Cruise controls, forward collision warning, and heated steering wheel controls on the left. Six-speed automatic transmission with the optional tap shift. This one comes with the AM, FM, and serious satellite radio capabilities on here. And it does have your projection where you can project your cell phone to the screen. So while it doesn't have a navigation system from the factory on it, it does have the capabilities for you to project your cell phone to the screen from your phone. So if you've got a nav system on there, put it right up on the screen. It's like you have nav on the screen.  There is a storage bin behind there, which is nice, and it has a USB jack for charging cell phone and stuff. Passner side format and seat are an excellent conditional rips or tears on there. Smells very clean inside this suburban. It does have the power sunroof. Up here you have your sunroof controls, your rear gate controls, and home link buttons for your garage door security systems and lighting systems on Star and SOS buttons in the rear view mirror. We'll take a quick look at the back seats and then we'll start it up and take a look under the hood. The back seats are just as clean as the front seats. You can see that these seats fold down like so. Back carpeting is very nice. Third row seats are in excellent shape, no rips or tears back there. You do get the second row quad seating. These second row seats are heated. You do get the latch child safety system for any child car seats that you want to put back here. And you can see that those seats are in really nice condition. It does come with a all-weather floor mat back here. You get a 110 volt, 150 watt plug-in, rear air controls, and a 12 volt power point. So really nice and clean back here. And the inside of the doors all look really good as well. The bottoms of the doors, I didn't see any corrosion on them. They look really good. We'll start it up and take a quick look under the hood. There's your digital spinometer. Also wanted to show you that backup camera is working nicely. You can see that it's no-check engine lights or anything like that. So that's good. We'll take a quick look under the hood. I would personally like to thank you for checking out the video today. And hopefully from this HD video, you'll been able to verify the quality and condition of this Suburban all the way around inside and out under the hood. We have the 5.3 liter V8 engine. Engine bay is very clean, runs very smooth. Once again, this Suburban has been fully safety and inspected by our service shop as a fresh oil and filter change. All the fluids have been checked and topped off. There's your mission sticker. And this one is 100% ready to go. I would highly recommend this Suburban from a quality and condition standpoint. And to see more pictures of this one, or one of our other 450 new and used cars, trucks, SUVs, minivans, Wranglers, halftones, three-quarter-tons, one-tons, you name it, we got to go to that website right there, www.SummitAuto.com. Full pictures and descriptions of every single vehicle from two locations all at SummitAuto.com. And if you'd like to check out more HD videos, you can go to YouTube.com.com.com. Remember to like, subscribe, and share on this video and all the videos that you see there. Click those bell notifications. You'll get updates on the videos we do each and every day here at Summit Auto. And if you'd like to check out more HD videos in the upper left-hand part of the screen, there's a link to subscribe to our YouTube channel. A link to more Suburban videos like this one in the upper right. A link to this vehicle on our website in the lower left. And a link to one of our latest YouTube videos in the lower right. Click those. Check us out. We're super excited to help you with this Ultra Clean 2018 Chevy Suburban LT1 in Iridescent Pearl Tri-Coat. Thanks again for checking out the video. Remember to like, subscribe, and share.