Hi, this is MXUX. This is MXUX. This is a Lordstown Week news video. It's about Lordstown Week. I'm going to go over how to find a live cast and watch it, camping world news, some insights on insider selling, the interim CEO and Ohio in general. And this is MXUX. So let's get to the video. Okay then, this is the first topic here. Lordstown Motors not part of Camping World's electric future. So this was the big announcement. In my last video I had mentioned that I think that I thought this was the problem and I thought the Otis here was gonna maybe come up with some money and get more deeply involved with Lordstown. They had mentioned joint venture partnership, all kind of different terms. But anyway, this I believe is what did Steve Burns, this was this agreement with the board and the top executive, Schmidt especially, and Darren Post both mentioned we are not going to build the camping world campers or whatever. We're not building campers. And this is the Otis. We are launching electric world with an amazing assortment from around the globe. Linoma said Lordstown Motors will not be part of that. So there you go. Lordstown Motors will not be part of that. So I suspected that this was, now this may be a branding thing. I mean if you look at the response to the camper add on for the Tesla pickup, I mean it's blowing up. I don't know. They got 100,000 orders. I forget.  So I don't know. I didn't, it didn't bother me personally. I thought it was, you know, made sense, synergy. But you know, there's branding people now that are in charge and they may have felt that this was going to damage the brand or take the brand off into a direction they didn't want to go. So anyway, that makes it formal. Here's the tweet we are launching without, you know, blah, blah, blah. Okay, announced a partnership, announced a partnership and they were going to provide service and maintenance and roadside assistance. Anyway, and they were going to build the shells to become EV campers. I think this is a good market. I think somebody's going to make hay with it. Maybe Lordstown will come back to this. But you know, with limited resources I imagine they wanted to focus. Who knows? I think it was a branding thing. I don't know. Anyway, I think that's what the wedge that separated Steve Burns from the board was this whole concept. So moving on to the next slide. Now I want to get into the Lordstown Motors, the insider selling, which has been such a big deal all over the internet.  And they're all foreign by the way, not that that's a thing I'm just saying. Anyway, this is a summary of the insider trading stock hut has gone over this. This is old news, but I just wanted to give you this here. The number of shares sold was a million, million and a half. The number bought was 46, 47 million by insiders. So what is that? 40 to one. Okay. And everybody was talking about the sales. All right. There you go. 40 to one. Now, let's just look at these sales. Darren post. And that was on 24. Okay. February four. Rodriguez, the CFO to four. Schmidt to three. One to two. Shane to two and Schmidt again on to two. Now I have written down here somewhere. I think I think it was about $25 a share at that time when they sold. And you can see here 20,000 70,000 170,000 190,000 and 290 and 350,000 something like that. All right. Here's the prices right here to strike prices. Okay. Now, everybody's saying, Well, that's before the before the bad news came out on the earnings call and all this. Well, I got another theory. I'm just going to put this out there by way of explanation. I think the key event that happened right around here was the award of the postal. And this was on 223. So this was about what two weeks later, a little less than that. And announced that Oshkosh got the US postal delivery vehicle contract, the entire contract. This, by the way, was an abomination. And this, I mean, I don't see how this can stand. They need to investigate the insider selling insider buying. You know, this head of the postal service needs to be investigated by the SEC and FBI. As far as I'm concerned, there was all kind of insider trading going on around this whole thing.  I mean, granted, workhorse, perhaps not the whole contract, but a portion of the contract. And I'm going to go over later why this is so critical to have this electric fleet on the road in the United States of America for the country and for the modernization of our grid and for the implementation of electric vehicles and for us to still be a leader in the world. You know, this is all very important to go backwards on this. And I mean, this is just an abomination. So anyway, this was February 23rd. I personally think that they may not have had the inside information, but they may have looked like it was going that way. I, and I'm sure a lot of these guys thought, and everybody was suspecting that if workhorse got this contract, Lordstown was going to build the trucks for and that or the trucks were going to be built on the Lordstown line, or the trucks were going to be assembled at Lordstown. And, you know, that's part of the panache of the company and, you know, the press and everything. And when they didn't get it, I think, and also the income, so certainly from that effort, early income, I think a lot of these guys sold out. That's my opinion. I don't know. That's a scenario. Okay. Again, these are all two four first week in February. This was the third week in February. So two weeks before this. And then just here's the the call was until May 21st. So that's, you know, I don't know, three months later. So I don't, I don't know. Going concern risk was on June 8th. That was even farther away. That was very much, you know, four or five months away. So I think I think actually the reason for this selling was the postal contract, my opinion, my scenario. What do you think? Tell me what you think. All right. Now, and this is the going concern announcement, which, by the way, this is a box they have to check on that form when they file it. And this is boilerplate. We all know what, you know, the cash situation is and so forth. And the debt situation is so they have to base that on current accounting. So you know, we all know what's going on with this, all the fans. Now I want to talk about this is this is very interesting. This is Angela Strand. She's an MBA out of Tennessee. She's the acting CEO now, I believe. Experienced with more fleets OEMs, utilities, financing, infrastructure, deploy electric trucks. She's a ride director since 2020 and lead independent director since 20 April 2021. And holder seven patents patents and manager director of strand strategy, blah, blah, blah. Anyway, the interesting thing about her that I don't I thought I read it on this website, but I can't seem to find it now. Angela strand is also a board member of a new V holding corporation. Now, if you haven't heard of new V, new V's a SPAC that came out. And here's the one month one month chart on on new V.  But it's doing pretty good here. And the last month, I actually own a bit of this stock. Anyway, the point is, see, it's a pre revenue the market cap, you know, it's a small market cap. However, they do have operations in Europe. They have operations in Denmark and a lot of the other European states. This is a company that does the vehicle to grid technology, and the vehicle integrated vehicle giv platform. Now, now the way this works is, and I'm just going to give you a hamfisted explanation.  That's kind of a sideways version of this. This is vehicle to grid. And this involves a bit of special hardware and inverter in the truck itself. And then the truck battery pack.  That's that's mounted on to a special technology circuit board or whatever the firmware that's in that as well. What this enables is they the truck can charge through that outlet. And it can also during peak demand, it can supply power to the grid seamlessly. And you can set up parameters as to when you want it to charge and when you don't want it to charge and so forth.  I believe these giant utilities like to run at 60 Hertz. I'm not sure you guys that are engineers have to tell me anyway. The point is, if they run below that, it's no good. If they run above that, it's no good. So when you have this vehicle to grid software and hardware implemented in your fleet, it's like having a giant yard full of Tesla Powerwalls basically. And you can customize it to power your facility or you can customize it to, you know, provide either storage space, basically supply storage space to the grid or to sell electricity back to the grid. You can actually make I think in Denmark right now, they're talking about $2,000 a year. It does cause a minor amount of battery degradation like 2% over a number of years. So it's not, it's not that it's not a big deal for the truck. But anyway, the point is, I mentioned the postal service earlier. If we had electric postal delivery vehicles, and we had this technology on those electric postal vehicles, can you imagine the size of the Powerwall we'd have in the United States of America? Do you think we'd have any blackouts? Do you think Texas would lose power?  I don't know how they got it set up down there. But the point is, this would have been, this would have put America right at the cutting edge, would have upgraded our utility infrastructure. I mean, you know, selling the workhorse vans made by Ride and then with this technology in them. And I'll tell you something else, and I'm working on a video on this. You know, the demand that the wide acceptance of electric vehicles is going to put on the grid.  I mean, there's going to be brownouts, there's going to be all kind of stuff going on. I read somewhere that an EV uses about the same load on a grid as three homes. So anyway, average size homes. So anyway, the point is, you know, having this, having this V2G resource of all those postal trucks, can you imagine how this would have upgraded our grid? Because everybody's talking about, well, how are we going to meet demand? How are we going to upgrade our grid?  So they need to store it somewhere. Where do you store it? Vehicle to grid. Okay. And you know, and again, you can program this a million different ways and they have statistics and so forth. This was actually developed back in the first iteration of electric vehicles. It was a concept by a university professor that has been taken up in modernized. But anyway, I wonder if Angela Strand, well, Angela Strand, I believe, is going to work with new V2G to implement this along with the endurance. I would imagine I do not know. But I think it would be a great system to have in place with the fleet operators. They provide the chargers and the technology and everything. And I think they have a management fee they charge or whatever. But the point is, I have a feeling, since she sits on the board of this company, that they're going to implement this in the fleet applications for Lordstown. And now this may have been part of the reason they wanted to get away from the Otis. And they want to, you know, they want to keep everything self-contained. They don't want to take any partnerships or anything on. Could be. I don't know. But anyway, I think it's a very interesting company, interesting technology. It's interesting that the acting CEO of Lordstown is on this board. And I think, and I have seen a presentation on the endurance that says they can be equipped as an option to do this. So the technology is there, execution, implementation. Anyway, pretty interesting. I did not know this before the other day. It's kind of hard to find out. I hope you guys like it. That's a scoop. And let's look at that chart again. Hey, hey, baby. Whoo. Look at that. All right. Anyway. All right. Now, this is another topic that's getting extremely difficult to find. And StockHut, I watched all StockHut. Hey, shout out to StockHut. I watched all StockHut's videos today. I had to get on, had to get on the YouTube and get this information out. Now here, this is difficult to find. It's not on their website. I saw a brief flash of it on YouTube as an announcement, but I could not find it again. It's kind of a waiting in queue for the live stream. Anyway, Lordstown Motors, and this is June 8th. Okay. All right. Lordstown Motors announces live from Lordstown Virtual Tour. Lordstown Motors announced this morning it would host a live from Lordstown Virtual Tour preview of the startup electric manufacturers operations on Friday, June 25th. It's going to cap off Lordstown Week as we prepare to open our doors. And so they're letting the investors and the fleet customers and analysts all go in first. And I think some locals as well. The virtual presentation will include a tour of the plant, a preview of Lordstown Motors vehicle lineup, and a ride along experience in a 21 Lordstown Adurance. The presentation will be followed by a live question and answer session with Lordstown Motors executives. So this is what we've all been asking for. And now here's the rug. Those interested in participating event can visit the company's website LordstownMotors.com on June 25th at 2 30 p.m. So they are saying here you got to visit the website at 2 30. Whether that's going to be streamed to YouTube, I don't it doesn't appear that it's going to be. It might be shown as a recorded video later. I think stock had mentioned that he was going to try to stream this. But in any case, this is how you can view it go to LordstownMotors.com June 25th at 2 30 p.m. And I guess that's local time. And so that's a four hour time difference. So for us, it would be the 10 a.m. Something like that, maybe for Pacific time. Anyway, and then I just wanted to say something about I've been watching the videos from I'm going to just show a short snippet of a video that's been taken at Lordstown Week.  They got this truck. The truck's running good. Did you see the moose test? I'm a big moose test guys, that thing is the moose testing it's not even fitted out yet or finished with the torque vectoring. That is a big deal.  Hey, puts his hat on backwards getting a truck driving through the mud in the field there. I'm brambling. The point is, compare that to Tesla, where they got the style Elon Musk is all styled. Who styled him? He's got his personal stylist. And then the guy that designs the cars, what's his name, Sven or whatever his name is. Again, looks like a Calvin Klein model styled. Yeah, Lordstown, real people making real trucks for real people. I like it. Anyway, that's just my two cents. You know, in California, it's Ohio. America. That's why I think these haters can't stand it. Because it's so American. You know, anyway, I don't want to get off on that tip again. Anyway, just for closing here, I'm just going to show you this is just a quick, I'm just going to show a snippet of this. I'm going to go to I'm going to play a little bit. I'm going to go to full screen here. Pass that. We're going to go into it. There you go. Then we'll do tight turn. And there's the interior of the truck. I think it looks great. I think it's great to finally see the inside of the truck. And I do like the interior. You know, it's normal. Have you guys done any? Anyway, personally, and they're talking about load testing here. And I just want to tell you, I was looking over the Ford stats today. Most of the people that bought the retail bought the highest price truck with the biggest battery. I was looking at their fleet and sales. There are so many gotchas on that thing. Well, if you want to have this tone, you got to get this battery pack, you got to get this supreme pack, you got to get this, you got to get that.  So anyway, you can look at these videos on on YouTube stock hot has links to them. I don't want to use too much of this video. I wanted to show the the I love that screen. I love the way that interior looks. I wanted to show the Moose test here where they're swerving in between these cones. I guess I didn't queue it up right. All right. Anyway, this is a look I love that dash. Anyway, all right. So I'm going to kill this now. And this is MX UX and I hope you liked this video. I'm going to do a close at the end and review. Thanks for watching. Okay, this is MX UX. This is a risk on stock. It's a pre revenue spec startup and it could result in catastrophic losses. Seek professional guidance. I'm not a financial advisor. Okay. Anyway, a lot of interesting stuff here. I thought I'd want to share with you, especially how to see the live stream there. I had a hard time finding that. Hope you guys liked the video. Just in closing, I'll just say, I think the endurance looks great. It's seeing a finished truck like that. It's riding great. I love it because it doesn't have any motor noise either. You know, it's a few squeaks there but they're going to work those out. No electric motor noise. Anyway, here's a bumper. The F 150 lightning planted a total remake in 2025. So they obviously didn't get it right. Thanks. Thanks for watching guys. MX UX.


Perfect, so I'm gonna go ahead and get started. So we're gonna be going over the time series tech stack for the IoT Edge, so really quick. My name is Zoe Steinkamp, I'm a developer advocate for Influx data. Before I became a developer advocate, I was a front end software engineer, mainly working in React. Some interest outside of coding and technology, it would be traveling, cycling, cooking, and gardening. You can ask me about any of these and I'd probably talk your ear off. So first things first, we're going to do a bit of a dive into the Influx DB platform, mainly because we need to explain how this works with Edge. Oh, there's someone washing the window. Sorry. First I thought a pigeon hit it. So what is time series data? So time series data is any data that is time stamped in some way, whether that be every hour, every minute, or every second. More specifically, time series data comes from many sources. This could be in a physical space like devices and sensors on possibly a factory floor or in a field or on a vehicle or even in space. From software applications, including VMs, containers, microservices, applications, storage and compute resources, et cetera. And from actual applications, be that crypto, financial, stock markets, agriculture, energy, it's very broad. Increasingly, it is the combination of multiple data sources that brings the intelligence to these applications. So when we normally describe Influx DB, we normally do describe it as a platform. Technically, most people know us for our database, but one thing to know is we have our API and tool set for real-time applications. We have our time series engine for real-time data workloads and finally our community and ecosystem. So when it comes to our platform, we normally break it out into these, as you can see, three architectures right here. The first one being our data sources. So that's going to be the actual devices that transmit time series data, as I just mentioned a few before. Then we have the actual core Influx DB platform. That includes Telegraph, which is our open source ingest agent. I'm going to talk a little bit more about that in a second. Our client libraries, which allow you to write in your preferred coding language to get your data up into Influx DB and then also native ecosystems as well. Finally, from there, you have the ability to start collecting, transforming, down-sampling, alerting off this data and that can go onward to be application workflows, infrastructure insights, and IoT actual actions. So as I just mentioned, we have our Telegraph plugin. It has over 300 plugins available and it's completely open source. We normally like to say that we're the caretakers of Telegraph. In fact, it's used by quite a few of our quote-unquote competitors. We'll use this, but pretty much every single plugin that we have is taken care of by its original owner, whether that be a company, a platform, et cetera. There's a few in here that we take care of ourselves, a few more fun ones like Minecraft or CSGO. Those were built by our engineers in-house who just really wanted to monitor their gaming. But for the most part, these are taken care of so they stay updated, et cetera. Flux, so when it comes to actually querying around your data in our platform, we have Flux, which you can imagine. Flux is to Influx DB, what SQL is to MySQL. It's the same thing, it's just a language for actually doing the work that you need to do on your data. Flux allows us to work more efficiently, specifically on time series data. It runs at the DB level as well, so it doesn't require any third party or client application tools to actually query this data. These are just a few examples of some of the things that you can do. The ones I normally highlight would be things like custom aggregation, which can allow you to change the window of time you're viewing for the data. You can also define custom functions yourself like running through tables. Some of you might actually recognize if you've done SQL development, those would be the joins, the map, and the pivot. And finally, more advanced features like covariance and smoothing, which is a little bit more useful with data science use cases. This is what I mentioned before, this is just the client libraries. These are the languages that we happen to support to help you upload your code and the language that you feel comfortable coding in. Task, so tasks are actually pretty important. I'm gonna really quick kinda go into what these are cause this is actually a big core part of edge to replication or at least it used to be. So with task, what this allows you to do is mainly clean up your data, as we like to call it. That means that maybe you wanna drop per, say, columns, you wanna drop information, you want to aggregate that information, specifically when it comes to aggregating, we normally call it down sampling when you archive historical data. When it comes to time series and IoT devices especially, you'll find that they send a lot of data, it's down to the milliseconds that exponentially gets quite large over the course of an hour, heaven forbid a day or multiple days. So what a lot of people will do is they will down sample their historical data for storage. They'll say, I don't want to know every microsecond detail, I just need to know roughly in an hour what this value was. And so for that, they'll go ahead and store that. Maybe a week later, they'll down sample it even further for better storage for a smaller data set. And sometimes they also just drop it all. They just say, drop everything that's 24 hours old, get rid of it. And that's also something that down sampling and tasks can do. So checks and alerts. So checks and alerts is exactly as it says here. This is the UI for it. It's a GUI that makes it easier. But basically you can check on things. Specifically you can do a threshold or a dead man. Dead man is as morbid as it is. It means that your data source is dead. It just literally is monitoring to make sure things are coming in. Thresholds are more what you guys would be familiar with which is things like, if your IoT sensor goes above or below a value threshold, please let me know. Set it to warning, critical, or maybe even just info. Maybe you just want to know about what's happening. From there you pick an endpoint. We offer pager duty, Slack, as well as HTTP, which obviously HTTP pretty much opens the door for any type of application. And from there you just set a rule, which basically just says, please alert me if it goes from info to warning or warning to critical. It's pretty straightforward overall. This is that exact same use case but with Flux. I just wanted to show that you could also do this in the non-UI basically. Now one thing to note about this is it does give you a lot more functionality obviously because you can, as I've mentioned before, use Flux to kind of clean up the data and do a few other analyzing and manipulating, et cetera. We also have a lot more endpoints when you do it this way. Dashboard creation, so this is gonna be visualization. For a lot of you guys it will probably kind of remind you of Grafana. That's a lot of people actually do use InfluxDB with Grafana. This just happens to be our in-house visualization. We also have dashboard creation. Again, this is probably gonna remind some of you guys of dashboards like when you're monitoring a server. It's a very similar thing except for the differences. We don't normally, we have a few out-of-the-box dashboards but for the most part it's custom built. A lot of people like that, especially if they're monitoring things that require custom dashboards. We also do have what we call the notebooks which are basically more interactive. A dashboard is something you would visit every day and you wanna see the same answer to the same question. You can think of notebooks as you are playing with the data and you want to answer different questions and you wanna kind of workflow through it. It's also a lot better if you have, you know, multiple coworkers and such. These are just some of the basic visualization types. Not gonna go super in-depth into this. They're pretty straightforward. And here's another visualization type that's a little bit more advanced that we offer. Things like maps and histograms. So let's go a little bit deeper into the actual tech stack for edge data into the cloud now that we have a brief overview of the platform. So really quick, some advantages from doing edge to cloud replication. The biggest edge advantages are going to be reducing bandwidth cost of sending high fidelity data to the cloud. And number two is going to be network resilience for intermittent failures and connectivity. Imagine, you know, if you're in a remote region or things only get uploaded every couple of, you know, hours, that's pretty much what we're talking about here. This hybrid solution provides the flexibility to also move some of those more mundane tasks such as down sampling to the edge. As I just mentioned before, this can be great if you don't want all of your data being stored and you actually already know that you wanna start cleaning it up, you could do it at the edge instead of doing that at the cloud and it could save you time, money, just makes it a little bit easier. So here are some stacks that you would find in the cloud. Some of these are gonna be things like Foglamp and EdgeX Foundry, which are IoT edge frameworks being built to help control running the devices as well as standardizing API and protocols. They also both have APIs for retrieving data and sending it northbound to a system like Inflex DB. Ditto creates digital twins in the cloud. You can use Inflex DB for data replay with this. It also includes running data simulations on a virtual machine. For outbound, we have a few options which I've kind of already mentioned, but obviously you can use Grafana, Python and Pandas. We actually have a library for that one in particular. And then a very straightforward one being Node.js React and Giraffe, the whole. That would be something like you might see in like a phone app or a website. When it comes to stacks on the Edge though, so some of the stacks will include the TIG stack, which is what we call Telegraph, Inflex, DB and Grafana. They're used so often together that they actually have their own little name. Teguido, which is not Telegraph, it's a Docker Compost script that sets up Telegraph and an MQTT broker to handle that common setup. It is on top of the TIG stack, which is why it has a similar, in my opinion, kind of funny name. The client libraries, which is what I mentioned earlier, those are gonna be the ones where you can code it up in the language of your choice. Probably most commonly, Python is normally what we work in. EdgeX plus Inflex DB plus Grafana. These next three are going to be, so EdgeX, AWS Greengrass and Azure IoT. All of these are frameworks to get data from Edge sensors up to the cloud. And they all use Inflex DB on their Edge gateways to provide a local dashboard. I'll be going more in depth actually on the final option though, which is specifically Inflex DB open source to the cloud. So just, I'd realized I actually hadn't mentioned this. Just a reference, we are completely open source. You can do everything on the open source. We do also have a cloud option. It's completely free. It's basically pay as you go, but it's free obviously when you start and as long as you keep yourself below a certain level. So that's the one we're gonna be mainly going through. So this is a very straightforward example of OSS to cloud. I do wanna clarify that as of like a week ago, this is considered the old way of doing Edge to cloud replication on our platform, but this will be the example that you see a lot of people using. So I'm gonna go over it really quick. The big thing with this is you're basically just going to need obviously a cloud account. After you sign up, you basically just create a bucket, create a token, make sure that the token that you're using has right permissions.  So yeah, as you can see here, we also are happening to filter this. So see, we've got a range of 10 minutes. We want these two data. And then we just wanna push that on up to the AWS cloud. For this, we've just put, you know, random gibberish for the or ID token, et cetera. But again, this is the old way that people used to do it. There are some limitations to this, obviously. It does offer an easy way to write data from the edge of the cloud. But the big thing is it's sent over HTTP. There's no built-in functionality for failure handling, which is not great, I can assure you. And there is also no built-in functionality for batching, retries or paralyzation. The two function really should only be used to consolidate data from OSS to cloud. If you're meeting these conditions, you intend to down sample your data first before writing it to limit the size of the request. You have a very small amount of devices, maybe only one or two sensors. You can't really use this for large workflows. It's not gonna work. It will probably actually cause a network failure, which is something that we saw quite often when people did this. And you aren't trying to overcome writing a large amount of data with micro-batching and generating a really high request count. Kind of similar storyline there. But as I said before, as of this month slash this week, we are now excited to announce the availability of Edge Data Replication that we've been working on for, I swear, since during COVID. So with that, this solution, it unifies time series data processing between Edge and cloud environments so developers can provide consolidated intelligence across widely distributed environments. So let me go ahead and show some of this. So specifically what this does is it is durable diskback hues and buffering to withstand planned and unplanned disruptions in network connectivity. In addition, this feature configures replication at the bucket level, so developers and operators can precisely define which sets of data to replicate and where to send them. This replication also happens on right when time series data arrives at the Edge and matches a replication rule. OSS immediately mirrors the data to the remote bucket defined in the configuration. When influx DB OSS cannot send the data to the remote instance, all events start to buffer in the local durable queue until the connectivity is restored. The size and retentable of the durable queue are configured are configurable. Sorry guys, I've got a lot of words that kind of jumble. So these are just some industry use cases that we were talking about when we originally started developing this months ago and I just wanted to put this up here. So basically, as you can see here, if you're dealing with something like retail, this would be inside of stores, last prevention devices, you know, this can have intermittent internet connectivity. I can tell you right now, my husband used to work for like Chipotle. They always seemed to lose internet just randomly and their cash registers didn't work, not great. Manufacturing, that's obviously pretty straightforward. A lot of the time manufacturing can be done in actually kind of remote regions and in general, thought necessarily super well connected and then banks as well.  Tangibly though, to get more into the in-depth features of this and how it's gonna work, we have two new API endpoints, remotes and replications, and then we have two new CLI commands, which is also happily named remote and replication. Each replicated bucket also, as I've already said before, gets that dispatch queue for buffering data safely in case of the disruptions. So this is just a very beautiful little design here that I built up, so as you can see, Telegraph puts the data into the influxDB OSS. From there, we have our disk with our buckets and our queue and we also have flux. Flux is kind of an optional thing, that's if you're down-sampling in particular, which I'll go into. And then obviously from there, it starts to upload this into influxDB cloud. And I'll actually show the commands for the CLI.  So as I just mentioned, let's go ahead and get started into the setup. So this is the influx remote create. So with this, I'm just going to clarify that, I'm assuming that you have an influxDB OSS instance running in a cloud account, that's the use case for this, that's what we're going into. In your local influxDB OSS instance, you would use this influx remote create command to create a remote connection to replicate your data. You have to provide the following, you need a remote name, the influxDB URL, an API token. It has to have write access, otherwise it cannot actually write to anything if you just give it read access that doesn't know good. And obviously just your organization. This is the replication create. So with this one, it actually creates the replication stream. And with this, you're just gonna have to give it the name, your remote connection ID, your local bucket ID. So that's the one on your OSS instance that it writes from. And then your remote bucket ID that the replication will write into. Once the replication stream is created, influxDB OSS will replicate all writes to your specified bucket, to the one on your cloud, the one we call the remote influxDB bucket. And then you can also use the influx replication list command to view information such as your current queue size, your max queue size, as well as your latest status code. So some important things to note here. Only write operations are replicated, other data operations like deletes or restores are not replicated. In influxDB OSS, large write request bodies are written entirely. When replicated, write requests are sent to the remote bucket in batches. The maximum batch size being currently 500 kilobytes. This may result in scenarios where some batches succeed and others fail.  I'm not gonna go in depth into that, but I just wanna let you guys know that we do actually have some failure handling already built in. In some cases, as I've mentioned before, you might not want to write that high, that raw high precision data to a remote influxDB instance or cloud instance. So to replicate any down sampled or processed data, you basically just, it's the same thing where you just create your bucket in the instance to store your down sampled or processed data in. Then you create the influxDB task that down samples or processes that data and then stores it into that new down sampled on your OSS instance. Getting the data, it's getting it raw. On the OSS instance, you still have another bucket called down sampled or you can name it whatever you want. That's where you're actually running a query like this where you're asking it to start to break it down, do the task instead of every second. This one is aggregating it down to every 10 minutes. And then from there, you wanna replicate that down sampled bucket. Now in theory, you could still obviously create a replication stream for the original data too. But the whole point in this is obviously to kind of make it a little bit more stream form to make it a little bit easier. So with this, you can see how these lines of code make a lot of the difficulties as it used to be a lot easier for people. It's a lot less writing. It's a lot more failure proof. It's not going to be as difficult for you to deal with intermittent connectivity issues. Basically, this really helps solve a lot of the big problems that we deal with when it comes to IoT edge to cloud. So I'm going to really quick go over an IoT edge example. One sec. So this is the architecture diagram for what is currently our plant buddy demo sitting back at our booth. Basically, we have a project where we want to monitor the health of, for this example, a household plant. And specifically, we are monitoring this data at the edge because when we go to conferences, we tend to lose wifi connectivity. And then we lose our data for our plant. So we needed something for edge to cloud replication. So what we also happen to do though is we also happen to down sample our data too before we send it into our cloud account. So basically to break this down, we have our plant and with that it has a microcontroller that basically has about four sensors on it. From there, we're using a telegraph to get it into our OSS instance. And we're actually running a flux down sampling on the moisture check.  So we like to clean them up a bit. Also, we just don't, we don't really want to store it down to the second. I'm sorry, but the household plant just doesn't require that. So we tend to aggregate it down to more like a minute or every 10 minutes. I luckily as an employee, basically have an unlimited free account, but I think even I'm reaching my limits at this point. But with that from there, we basically put into a down sample bucket on that OSS edge. And it stays in the replication queue. So when we do lose data, as we tend to here at the conference or just in general, like, I've obviously disconnected my laptop from the device and it's all this stuff. From there, we send it on up to the Influx DB cloud and we actually have it going to a web application right now, where we have, so we've actually, we have some alerts and notifications on it too. Like we're alerting through Twilio for moisture notification to let us know if the plant gets too dry or too, well, it's never too wet because we never water the poor thing. So it's always too dry. And basically from there we have our UI for it. I'm going to really quick do a plug that you can come and see this at our little booth. There's the plant and there's the ridiculous amount of cords and sensors attached to it. It's a lot of fun to see this in real life. And this is actually inspired by one of our clients who is doing this at a much bigger scale. They are specifically a, I'm going to call it a farm. It's kind of a farmish factory in New York that produces lettuce and tilapia together. That's obviously a very intense system. The fish feed the lettuce, the lettuce are not fed to the fish, they feed humans. But basically with that, they have a ton of IoT sensors and their farm tends to occasionally lose interconnectivity. It's just not well connected. I'm sorry, but farms are just kind of dead zones I guess, even ones in New York. So with that, they're using edge to cloud and they're also specifically down sampling because like us, they're dealing with IoT sensors that send them a lot of gibberish that they do not desire and they also don't need it down to the millisecond either. Another quick one that I wanted to go ahead and mention is a company called Bebox. So they are specifically out in, I do believe Africa if I remember correctly, but basically they have solar panels geographically dispersed. They have about 85,000 solar rooftops that are providing power to these very small villages and remote parts. From what I understand, they occasionally get internet connectivity from satellites, like kind of like the Tesla one or just occasionally reconnects to the main grid. But basically they're dealing with a lot of, a lot of loss of data originally. They were already doing edge to replication before, obviously like we started to do this more seriously till we built out everything for it, but they've been doing this for over 10 years. They've already got a few solutions, but I still like to mention the fact that this is an ideal use case. Obviously for some people, in general though, I do like to think about when it comes to edge to cloud, it's always good to somewhat store the edge because you might just have internet connectivity or just data loss just in general, just through life. Even if that's not a common problem that you deal with currently, it could be an issue that you have and it would suck to lose your data. So this is an overall great use case for that. So I do wanna mention some further resources as well. So as I've already talked about many times in this, this is actually where you can go ahead and find the cloud account is that the getting started. That would be where you actually create your inflex DB cloud. We also have our community forms as well as our Slack. So the community forms are more something that you could like search through if you're having any issues. We also have our Slack community is a lot more active. A lot of our employees are on there. We do, we're fully open source. So obviously on our GitHub, we get a lot of issue requests or things filed, but plenty of people just come to us on Slack to ask questions or make comments or even complain. We're open to all. We don't discriminate. And we also have a book. It basically goes more in depth as to how the time series database was built out like some of our core, I'm gonna call it theater reticle components, just some of the ideas on how this was built out, how we're building going forward, our actual docs, which go more in depth. And also that is where I grabbed the code commands for the create and replication stream that is inside of our docs now. We have blogs where we write about these kind of things, including this, and just in general, some of our client use cases, you know, all that good stuff. And then finally, Influx DB University, which is our brand new free university course where you can learn more about different components of the platform. And yeah, I managed to end this a little bit early, which is fine. I'm sure no one minds a little bit of extra time back. If you guys have any questions, you're welcome to ask. And like I said, I'm actually not gonna end on this slide, I don't like it. Go ahead and come back to our booth, if you have any more. We also do have some really awesome socks and stickers. And like I said, you can see a little bit more of the plant buddy. We actually have all the code on GitHub, specifically just to show off. I didn't wanna go super in depth into per se that code here, but I can do it at the booth. But yeah, thank you all for coming.


Okay, welcome back everyone. I've just started the recording of this continuing session, the second lecture. Okay, let's pick up from where we paused before the break. I'm gonna go ahead and share my screen. All right, so we spoke about the fact that the blood speaks. So in the spiritual realm, let me talk about the blood. It's very, very powerful, and the blood of Jesus speaks of better things. It's announcing of a new covenant with God. It's announcing the completed work of eternal redemption that we have. It's announcing that our sins have been forgiven. The debt's been cleared, so the blood is very powerful. We looked at Colossians 1, 13 and 14 in detail a little earlier on. We talked about the fact that we are delivered from Satan's dominion. So this truth has to be settled in our hearts, that Satan has no right over us, no claim over us, no access to us, because we are in the kingdom of Jesus Christ. Now we know he's gonna violate, try and violate that. We know that he's gonna try and, you know, in the natural, because this is spiritual reality, and he's gonna try to affect us through the natural. We are living in the natural world, and he's gonna try to work against us in the natural world. But this spiritual truth we will bring to bear in our natural life here on earth, and we will talk about that. So as part of this, as part of our redemption, we must understand we are God's property, right? We are a hundred percent God's property. First Corinthians 6 and verse 20, it tells us you were bought at a price. So that's redemption. We were bought at a price. In the same picture that we talked about, the picture of redemption. Jesus offered himself as a ransom, and he purchased us out of being in subjection to the devil. So we are bought. So when he paid the ransom for us, what happened? We became his property. So whose property are you? You're God's property. You're the property. You and I, we are property of the one who paid the ransom. So we were bought at a price. We are now God's, God's purchased possession. Therefore, our goal is to glorify God in our body, in our spirit, every part of our being, which are God's. That means every part of us, spirit, soul and body belongs to God. So you and I have a right to say I'm God's property, spirit, soul and body. By the means of our entire being belongs to God. And Satan has no right to trespass on God's property, spirit, soul and body. Every part of me is God's property. And this, this whole idea or this truth is repeated here. The song in the book of Revelation says, you have redeemed us to God by your blood. That means you have purchased us to God. You've redeemed us to God. You've purchased us to God by your blood. So we are God's property. We belong to God. So now what we want to do is we want to just kind of break it down and say, okay, what are we redeemed from so that we can, you know, very specifically say, look, I'm not enslaved by that. I'm free from it. And I can walk free from it. Right. So, and how do we do that? We should be able to finish that in this lecture. So we are redeemed from the curse of the law. So not only are we redeemed from, so we already mentioned the first thing is we are delivered from Satan's dominion. So that's the first thing. We are redeemed. We are delivered from Satan's dominion. Satan has no control over you and me. And we've been taken out in our God's purchased possession. In continuation, next, we're redeemed from the curse of the law. We will look at this in detail in the next chapter. That is lesson number eight. But what I want to emphasize here or just point to here is the law. Let me talk about the law. We are referring to the entirety of the law that was given through Moses. So the law was given through Moses. And that means the 10 commandments, the religious laws, you know, how the people had to worship God by various sacrifices, the ceremonial laws and how they would approach God, the feasts they had to keep, all of that. And the community laws, meaning how they had to deal with each other, living in the community and so on. Hygiene laws, laws that dealt with, you know, what you can eat and what you cannot eat, those kinds of things. So all of that was part of the law of Moses. So when you read Exodus and Leviticus, it's essentially the written law, the law that was given through Moses. And the New Testament is telling us that Christ has redeemed us from the curse of the law.  We need to understand this in two ways. One, the law itself was a curse, meaning, and in what sense? Meaning not that the law was bad, sorry, but we couldn't keep the law. People couldn't keep the law. And so the law just brought and a weight on the people. It was a heavy weight on the people. So in that sense, the law was a curse. But we also read about the curse of the law, which means it had to do with the penalty for violating the law. So we read about this in Deuteronomy, the 28th chapter. So if you have your Bibles, and I just want to point this out to you, in Deuteronomy, chapter 28, verses 1 to 14, are all the blessings of the law. Deuteronomy 28, 1 to 14. And then from verse 15, till the very end of the chapter, which is verse 68, from verse 15 to 68, are the curses of the law. So let me just write this down in the chat, Deuteronomy. Some of you may be familiar with this, are the blessings, and verse 15 to 68. So curses of the law. So under the curses of the law, if you look at it, you read it, you will find everything that all kinds of problems are listed there, poverty, financial trouble, sickness, problems at home, problems with the children, problems in the business, problems in relationships, all kinds of things, physical problems and so on. And then you can read it. And in fact here, it talks about verse 61, says, every sickness in every plague. So Deuteronomy 28, if you look at verse 61, it says, every sickness in every plague, which is not even written, you know, so sickness and plague is under the curse. It's not listed under the blessing, it's listed under the curse of the law. And all kinds of things here, if you read through this. So going back to Galatians chapter 3, and when you look at verse 13, it says, Christ has redeemed us from the curse of the law. Christ has redeemed us from the curse of the law. And what I just explained is, it must be understood in both sense. That is one is the law, it's being a curse, being too heavy for us to live under. And we will discuss that in detail in the next lesson. And also we must understand the curse of the law in the sense of what is written there in Deuteronomy 28 as under the curse of the law. Why? Because that is the outcome of not being able to keep the law. So what Christ redeemed us from? He redeemed us from all of these things, each and every one of these things listed in Deuteronomy 28 verses 15 to 68. Each and every one of those things, if you look at it and say, you know, all these things I am free from, they have no right to with me because Christ has redeemed me. He has redeemed me from the curse of the law. Right? Verses 15 to 68. And as I pointed out in verse 61, it says, every sickness and every plague, which is not even written down here, everything, it's part of the curse. So I wanted to think about this, right? Sometimes people say, well, God, God blessed me with a sickness to teach me a lesson. And now that is not scriptural because sickness and disease is not a blessing. It's under the curse. So we don't have any right to move sickness from the curse into a blessing. No, it's listed under the curse. So leave it there. Now, of course, we will face sickness and disease and, you know, we can learn things through the process, but we don't make call sickness and disease a blessing. It's not a blessing. It's under the curse. We leave it there. And we say, Christ has redeemed us from the curse of the law. Right? And that's repeated for us here in Galatians 4 verses 4 and 5, that Christ redeemed those of us who are under the law. And instead, He brings us into a place of being sons and daughters of God. So what are we redeemed from? We're redeemed from the curse of the law, both the weight of the law and the curses of the law have no right over us. We can stand at ground and, you know, resist those things. Next, we are redeemed from every lawless deed. Titus chapter 2 verse 14, it says that Jesus, who Jesus gave himself for us, that he might redeem us, same thought, you know, bring us out from being in captivity, that he might redeem us from what? From every lawless deed. That means every sinful deed and purify for himself his own special people, zealous for good works. So this is, again, very interesting. What did Jesus redeem us from? He redeemed us from every lawless deed. That means every sinful deed. So some people say, you know, I'm in bondage to this sin. I'm in bondage to this addiction. I cannot, I can't seem to come out of this. Well, when we understand redemption, we understand that our redemption includes freedom from every sinful deed. So he redeemed us from it. Remember earlier, we read whoever commit sin is a slave of sin. So sin and slaves, but Jesus redeemed us from every sinful deed. So no sinful deed or habit or addiction can hold a believer captive. Why? Because we're redeemed from it. And instead of being enslaved to lawless deeds, we can be purified. We can live pure as his own special people who are zealous for good works. So this is another part of our redemption. We are free from every lawless deed. So we've talked about three so far. First, we are redeemed from Satan's dominion or delivered from Satan's dominion. And therefore we become God's property. Second, we are redeemed from the curse of the law, both the law itself and all the curses under it. Third, we are redeemed from every lawless deed, every sinful deed. So no sin can hold us or enslave us. Number fourth, we're going to fourth one now. Yeah, it's a fourth one. We are redeemed from this present evil age. Somebody could read Galatians chapter one verses three and four for us, please. Galatians one, three to four. Grace to you in peace from God the Father and our Lord Jesus Christ. Galatians one, four, who gave himself for our sins that he might deliver us from this present evil age according to the will of our God and Father. Amen. Thank you. So look at that. He gave himself for our sins. So Jesus offered himself on the cross for our sins. We know that. And what was he trying to do? That he might deliver us or set us free from this present evil age. So let me highlight this. What's happening? This present evil age. Jesus has set us free from this present evil age. What does that mean? See, if you cross a reference and if you go to 1st John chapter five, and we look at verse, I think it's verse 18. 1st John, somebody could read this for us, please. 1st John chapter five and let's read verse 19, please. 1st John chapter five verse 19. Can somebody read that? We know that we are of God and the whole world lies under the sway of the wicked one. Thank you. So John is saying the whole world. So today, today, the world is under this sway or under the influence of the wicked one. So what is this present evil age? This present evil age talks about this entire system of the world that is demonically controlled. Now, I'm not saying everything is bad. I'm not saying the world is a terrible place. No. There are so many good things in the world we can enjoy. You can enjoy good food. You can enjoy good food. You can enjoy all the beautiful things that God has created, all of nature, beautiful things. But there is also the system of this world that is controlled or influenced by the wicked one, like we just read here in verse 19. And the Bible is telling us here in Galatians 1 verse 4, Jesus has delivered us from this present evil age, this current world system that is dominated or influenced by the devil. So we don't have to be submitted to the influence of evil that comes at us through the present world, present system. We are in the world. We have to engage with the world, of course. So we do interact with the world systems. We engage with the world systems. We are here to be salt and light. We are here to actually bring the light of God into the darkness. So we have to go where it's dark. We stay in a bright room. Well, okay, that's fine, but it's not going to do much good. So we are the light, so we need to go where darkness is so that we can be light there. But as we go there, we know that this present evil age has no power over us because we are delivered from this present evil age. We are not subject to its evil influence. Well, is there darkness around us? Yes. Well, the enemy tried to influence us, of course, but we must understand we are delivered from this present evil age. And so therefore we are not subject to the influence of darkness that comes at us through the world system, through this present evil age. So as we engage with the world, we interact with things of the world, the systems though we understand it, we engage with it, but we're not subject to it. We know we're confident. We're delivered from the influence of this evil age. Just a couple of things more here. What are we delivered from? We are redeemed from the fear of death. Could somebody read that Hebrews to 14 and 15? Please. Yeah, go ahead. In as much then as the children have partaken of flesh and blood, he himself likewise shared in the scene that through death, he might destroy him who had the power of death, that is the devil, and release those who through fear of death were all their lifetime subject to bondage. So the Bible is telling us here that Jesus took part in flesh and blood. That means he came like us. He became human. He shared in the same. He came on in a human body and through his death. So he died on the cross. But what did he do do through his death? He destroyed the one who had the power of death, that is the devil. So through his death that is on the cross, Jesus destroyed the devil. He rendered him powerless. He crushed the devil. He destroyed him. And the outcomes of that one of the outcomes is he would release those who through fear of death were all their lifetime in bondage. So as people, as sinners, it's quite possible that people would live in the fear of death, afraid because knowing that once they die, there's an eternity without God.  They're in bondage, in captivity. They're held in the fear of death. But now, because Christ has destroyed Satan, we are released from the sphere of death. So that's a beautiful thing. As believers, we have no fear of death. So our lifetime is not spent in bondage or in bondage to the sphere of death. We are, well, we all desire and all must desire to live out the full course of our lives. We're not afraid of death because we know death is only a transition and it's going to take us into the presence of God. So we are free from the fear of death. And as believers, we should not, we need not be living under fear of death. Okay, somebody has a question? Yes, you have a question, please? Yes. So for death, I know in terms of means like physical death, but also couldn't mean sickness, like what I mean sickness, like physical sickness, mental emotional, does that apply to that also? Over here. Yes. So here he's specifically talking about the fear of death. But I think definitely, I mean, I haven't thought of it like that, like the way you mentioned it, but it definitely can be extended. Meaning if I'm not afraid of death, then I don't have to be fearful of things that lead to death, which would be sickness and any kind of calamity that results in that. So by extension, yes, we can include that as well. So we're not fearful of death or the things that bring us to death, which would be sickness or calamities and so on. Okay, thank you. Yeah. So let's just go over a few more things here on what we are redeemed from. So we're also redeemed from generational bondages. I could somebody read this for us for Speeder 1, 18 and 19, please? First Peter 1, 18 and 19. No one that you are not redeemed with crepeable things like silver or gold from your aimless conduct received by tradition from your fathers, but with the precious blood of Christ as of a lamb without blemish or without spot. Thank you. So Peter is saying, knowing, so I want you to know this, that God in redeem us with gold or silver, but he gave the precious blood of Christ who was a lamb, like as a lamb without blemish or without spot. So there's perfect lamb. But in this verse, what's he telling us? He's saying you're redeemed from what? From your aimless conduct or way of life that was received by tradition from your fathers. So let's think about that. He says you're redeemed.  You're no longer subject to this. You're no longer enslaved by this, by what? Your aimless conduct.  You're set free from which was received by tradition from your fathers. That means your forefathers, your ancestors, right? They lived like this and they just passed it down, passed it down, passed it down. As it comes to you, but you're free from that. Now Peter, of course, is writing to Jewish believers. So Peter was an apostle to the Jews. He was writing to the Jewish believers who at that time had been scattered after the persecution that took place in Jerusalem at eight years or so after the day of Pentecost. There was a huge persecution in Jerusalem and then they were all scattered. And yeah, they were in and around that region. So Peter is writing to the believers. He started writing to those who are being dispersed because of the persecution Jewish believers. And I think, you know, you see a lot of things have, and I'm just part of raising this. He's telling them, look, you've got a lot of things handed down to you from your forefathers that tells you how to live and what to do or not to do and so on and so forth. He says, you're free from all of those things. You are not subject to whatever has been handed down by tradition from your forefathers. So again, now I'm applying this by extension. So we understand the context that we know, okay, who is he speaking to and what's he telling them. Now you and I are not Jewish people. But if the blood of Jesus would do this for them, then the blood of Jesus would do the same for us. So what I was handed down by tradition to us, which basically is aimless conduct is a vain and empty way of living has no meaning for us. Things that may have come down to us from generations. It has no relevance to the kingdom of God. The blood of Jesus Christ sets us free. And for those of us in different cultures, different parts of the world in different cultures, we could have had different things handed down to us. It could be lifestyles. It could be behavior patterns. Sometimes it could be religious beliefs. It could be whatever, whatever's been handed down, which doesn't fit into the kingdom of God, the blood of Jesus Christ sets us free. So we're not in bondage to that. And we can use the same thing if it comes to behaviors, you know, for example, anger or other kinds of addictions or sin, the sins that have been empowered, they're demonically empowered, you know, uncleanness and so on. Things that are Satan's foothold and he empowers those behaviors. So I'm redeemed from that. It doesn't fit into the kingdom of God. So whatever that does not fit into the kingdom of God, which has been handed down from forefathers, I am redeemed from you and I don't have to be subject to it.  But if it doesn't fit into the kingdom of God, you and I can take our stand and say, no, it's not going to continue in my life. The blood of Jesus Christ has redeemed me from it, set me free from it. Okay. And so the part of our redemption, I just want to finish a few more thoughts here. So redemption restores us to God, reconciles us to God, puts us in this wonderful relationship with God. Like we said, it brings us out of captivity, of being in bondage to sin and Satan, and it takes us into a beautiful relationship with God, the other side. So Romans 511, just not only that, but we also rejoice in God through our Lord Jesus Christ, through whom we have now received the reconciliation. So there's an there's an atonement and the atonement always results in reconciliation. We are restored to God. We are reconciled to God. We are made friends with God. So redemption includes our restoration, reconciliation with God. So we go back to that original verse, the first verse that we started, Prescurrentians 130 where it says Christ is our redemption. You know, so Christ is our redemption. So when we talk about redemption, we can say Jesus Christ is my redeemer. Jesus is the one who has redeemed me and Christ himself is my redemption. If Jesus is alive, then your redemption is valid and Jesus indeed is alive. So your redemption indeed is completely valid. Christ is our redemption. He is my redemption, our redemption. So what must we do, right? Two things. We need to say so. Psalm 172, let the redeemed of the Lord say so, whom he has redeemed from the hand of the enemy. This declaration of our redemption is important. When we say that we are redeemed, we can walk in our redemption. That means we are acknowledging that we know the truth of our redemption and that we are choosing to walk in that redemption. So here's where many believers fail to enjoy the redemption. That is, first they don't know what their redemption is and that it can be enjoyed here and now. You can actually walk in it here and now. They don't know it. And secondly, they don't say it. Let the redeemed of the Lord say so. You need to acknowledge I am redeemed. This is what God has given me. This is what God has done for me. Satan has no place in me, no claim in me. So we need to say so. Let the redeemed of the Lord say so. So you and I must say this. Satan, you have no claim over me, no place in me. I am God's purchase, possession. My spirit, soul and body belong to God. I am redeemed from the curse of the law. I am redeemed from every sickness, disease, poverty, failure, anything that's listed under that curse. I am redeemed from it. I am redeemed from every lawless tea. No sin can control me. I am redeemed from this present evil age. The influences of this world will not prevail over me. I am redeemed from every manner of life, manner of life that may have been handed down from my forefathers. I am redeemed. The sins of my forefathers will not affect me. Whatever they did, which is not aligned to the kingdom of God, will not affect me because I am redeemed. So Christ himself is my redemption. So we need to say that. We need to affirm that we are the redeemed of the Lord. And then the Bible teaches us, Revelation 11, that they overcame him by the blood of the Lamb and by the word of their testimony. So we must have the word of our testimony. What do we testify? We have to testify about the blood of the Lamb, of course. So the blood of the Lamb, remember we said earlier, the blood speaks. But now we have to do our speaking. That's our testimony. Our speaking is aligned to the blood of the Lamb. So they overcame him. That's Satan. If you read the Proceeding Verse of Revelation 12, 10, it talks about Satan. So we overcome the adversary.  The blood of the Lamb is already speaking. Now we speak and declare what the blood of the Lamb has done for us. And we do not love our lives under that. We are not afraid of death because Jesus redeemed us from the fear of death. We do not live in the fear of death. If we have to die for Jesus, we are fine. We are ready. But we overcome the enemy by the blood of the Lamb and by the word of our testimony. So we testify to what the blood of Jesus has done for us. Testify to the blood. The blood is speaking. The blood is announcing all this. I'm just quickly reviewing. The blood is announcing that you and I are delivered from Satan's dominion. The blood is announcing that we are God's property. The blood is announcing that we are redeemed from the curse of the law. All the curses listed there. The blood is announcing we have redeemed from every lawless deed. The blood is announcing we are redeemed from this present evil age. The blood is announcing we are free from the fear of death. The blood is announcing that we are free from generational bondages. The blood is announcing we have restored or reconciled to God and the Christ Himself is our redemption. So what must we do? We must testify to what the blood is already speaking. So this truth of our redemption is a very powerful truth. So it's true. It's spiritual, it's true. So now we have to stand up and say, you know, I'm redeemed. I know I'm repeating, but Satan is a trespasser. He's going to try to come and violate this. That's who he is. But you and I stand out ground and say, no, I am the redeemed of the Lord. The Bible says that the redeemed of the Lord says so. And the Bible says that we overcome the devil, how, by the blood and by our testimony. So the blood has done its work.  And that's how we overcome the enemy, live victoriously because of our redemption. So I'm going to pause here. I want to see if anybody has any questions before we close this lecture. Okay. Yes, Shani, please go ahead. For Revelation 12 11, I never understood the last part that says they did not love their lives to the death. What do they mean? I don't know what that means. Okay. So let me just give you a quick context. So Revelation chapter 12, it's a chapter, of course, we know the book of Revelation is about the end times. So what happens in the sequence of events that's unfolding in the book of Revelation? In Revelation 11 is the midpoint of the tribulation period, seven years of tribulation. Revelation chapter 11 verse one talks about the midpoint. That means the first three and a half years is over. It's the beginning of the second three and a half years. So in Revelation 11, it talks about the two witnesses and who come and doing what they do. Revelation 12 talks about what's going to happen to Satan in the second half of the tribulation. So, you know, it begins with a picture of the woman, the manchild and the dragon. The woman is the nation of Israel. The manchild is Jesus Christ. The dragon, of course, is Satan. And it basically tells us in chapter 12 that Satan makes a final attempt, if you read the preceding verses, he makes a final attempt to get into heaven. But Michael in the Archangels, they push him down. They cast him out of heaven. They're saying, sorry, no entry. You can't get into heaven. No access. So Revelation 12 says, Satan comes back with great vengeance on the earth, knowing his time is short. He's got just three and a half years left to do whatever he wants to do. So he's coming with great vengeance. Now, of course, on the earth, there are believers, people who have believed in Jesus since the time of the rapture. The rapture has taken place. We are three and a half years into tribulation. And there are people who believed. So it's talking about them and they, that means believers. Okay. So Satan is coming with great vengeance. He's got, he knows his time is short. He's coming with great vengeance, but they, the believers who are there on the earth at that time, they overcome him, that is the devil. Satan, how?  And they love not their lives unto death. That means they're not afraid. So that means even if Satan's going to kill them, and if you read the end of chapter 12, many are martyred. If you go into chapter 13, you read about the Antichrist and the false prophet where, you know, then the Antichrist introduces this economic system where you cannot buy or sell except you have the mark of the beast in Revelation 13.  So basically believers, you know, those who believe in Jesus, because during the tribulation, I have a very hard time. So that's what it's talking about. They do not love their lives unto death. That means to the point of death, they are willing to stand up for Jesus. Right? So the context of Revelation 12, of course, is there in the second half of the tribulation. But the essence, the truth is, we overcome Satan by the blood of the lamb and by the word of our testimony. Okay, thank you. Yeah, got that? Okay. Okay. Any other questions? So did we all understand this lesson on our redemption? So this is our identity and our inheritance in Christ. We are the redeemed of the Lord. You are redeemed. Okay. And you and I need to walk in our redemption. Say, God, this is our redemption blessing. This is what God has given to me as a blessing. In redemption, I'm going to walk in it and I'm going to enjoy the blessings of redemption. Okay. Let's take a moment just to pray. I want to pray with us as a class and I just want to pray that, you know, be each one of us. I will walk in our redemption blessings. Okay. Let's just pray together enough that we will close. Okay. Father, we thank you for the word we have heard today. And I pray for each and every person, God, who is in this class right now. And for those who may watch this later on. Father, thank you, your word says we are the redeemed of the Lord.  And I pray for every person here. And I announce to you, Satan, you have no right over God's property. If you have violated in any way, sickness, disease, any form of affliction, any thing that does not align itself with the kingdom of God today, right now in Jesus' name, I adore your devil, take your hands off of God's property. Take your hands off of God's property in the name of Jesus. I declare that each one of God's children here will walk in the full blessings of redemption. They'll walk free from sickness and disease. They will walk in wholeness. They will walk in blessing. They will walk in abundance. They will walk in God's provision over their lives. They will walk in victory and authority and dominion. They will walk free from every bondage because we are the redeemed of the Lord. And we say so. Father, we thank you for the blood of Jesus that has redeemed us, that announces that we are the redeemed of the Lord. Thank you, Father, in Jesus' name. Amen. All right, everyone. Thank you for being on the class today. I know we finished about five minutes early, but that's okay. I'll just take a few five minutes, a little extra break, and then you can proceed to your next class. God bless you. Enjoy the rest of your day. I'll see you again Friday. Thank you. God bless. Thank you, Paul. God bless you. Thank you, each one. God bless. God bless you. Thank you. God bless. Have a good day. I'm sorry. I have a question. You said that you were going to post something up over the weekend for us. Yes, Shani. I haven't given any assignment till now, so I will prepare an assignment to make that available in the coursework. That's the midterm, that's where 40%? 30%, yeah. 30%. Okay. It's going to be simple, easy, nothing to worry about. Okay. All right. Thank you. Bye.