This is Professor Gerald Friedman, the University of Massachusetts, Department of Economics. And we're here today to talk about rents, profits, surplus, and why monopoly is bad. At some point we'll talk about why you can't have anything but monopoly, but that's another story. Okay, social welfare is the goal of the whole thing. We are interested not in the amount you produce, but the amount you produce, the value of what you produce, the benefits people get minus the course. And that can be illustrated on this graph. Over here we have demand, which is the marginal utility for each one of these things. What is it we're making here? I didn't put a product name. So this is Q of acid. People are into acid. A little bit, they like a lot. At some point down around here, they're so out of it that they don't get any benefit from additional acid. It costs a certain amount to make acid. The first bits are cheap. Marginal productivity is very high. The marginal cost is very low. As you move along to make more, you have to start finding new places. You have to start hiring more and more workers. And marginal costs rise, giving you an upward-sloping marginal cost and downward-sloping marginal utility curve. All very familiar. How much acid do you want them to make? If you were the old gas plan, the people in Moscow who planned the Soviet economy, or if you were the war production board in the United States during World War II, then you would look, would you make the first one? Yeah, benefits high, costs low. Make the second? Yes, benefits high, costs low. Surplus in between. We'd keep going until the surplus on the marginal unit. The marginal surplus was zero. Would you go further? Would you make more acid? Some people at Grateful Dead concerts, or people listening to old tapes of Grateful Dead concerts, would say, yeah, make more acid.  You would think, no, the cost exceeds the benefit. They have benefits, but the costs are even greater. So you don't. You stop here at QPC, which is where perfect competitors will go. Perfect competitors will keep producing as long as they can sell for more than marginal cost. So they'll produce up to this point. And at this point, QPC, they'll sell at this price. The price equals the marginal cost of production and the marginal utility. And there's surplus. There are two types of surplus. Consumer surplus is the difference between the marginal utility and the price. Remember, we talked about that before. Producer surplus is the difference between the marginal cost and the price. So this whole area, this triangle down here, is producer surplus. This triangle up here is consumer surplus. Add them together and you have total social surplus. The level of happiness in the entire economy coming from acid. People are happy. They've got a big surplus. It's wonderful. They're stoned out of their minds and having a great time of it. Don't tell your parents, I said this. And that's where you'll be with perfect competition. Now mind you, one of these perfect competitors is going to get smart someday. Maybe it's you. Maybe you'll have taken some economics. And you'll say, oh, wait a second. You can increase your profits because you notice this curve, this straight line, marginal revenue. This is the change in total revenue that comes from producing and selling one more unit, one more hit of acid. Marginal revenue is always less than the price because to sell more, you have to lower prices.  And that discount translates into the difference between marginal revenue and the marginal utility curve. So the marginal revenue curve is below the marginal utility curve. This is tricky. It's very tricky, it's in the textbook. Think about it. The marginal revenue curve is less than the marginal utility curve, less than the demand curve. Therefore, it will intersect the marginal cost curve, the curve telling you how much each unit costs you to produce at a lower quantity. So you will go along, do you make the first unit? Yes, second unit? Yes, marginal revenue, the extra money you're getting is still greater than marginal cost. And you keep going along here, you're not looking at this one anymore. You're looking at this one, the marginal revenue curve.  You don't use your own stuff, which is always a bad idea. Never use your own stuff. And never use anybody else's stuff either if you wanna make a profit in this business. So you're looking at the marginal revenue curve and you move along here and you stop producing over here. You stop producing at the point where, obviously I misdrew this. You stop producing at the point where marginal revenue equals marginal cost. That's less production than had been the case with the perfect competitor. You're not producing all the way out here, you're just stopping over here at Q Monopoly. You stop over there. This quantity prices a higher because there's a lower quantity. So you can charge higher prices to fewer deadheads. So you have a price over here, forget this one. You produce and sell at that price, higher prices. What does this do to everybody's welfare? Higher prices means some stuff isn't produced. I mean, there's social benefit to these units, to these hits, but you're not making them. So you have a net loss. This is just total loss. We call this the deadweight burden of monopoly.  All this acid just being flushed down the toilet or something, probably contaminating the sewers and you have alligators in the sewers of New York City ingesting acid going crazy.   Well, that's New York, what do you expect? Okay, so you have deadweight burden over here, just plain loss. There's also transfer. This higher prices means there's benefit but it's taken from the consumers and given to the producers. So you get a transfer and what's left up here is consumer surplus with monopoly. Total surplus is less, we're worse off, even the alligators are worse off.  What you gain from the transfer is greater than what you lose by those units that you're not producing.  I hope you're happy. I do and have a nice day. Thank you, bye bye.


So, in addition to giving us the slope of the line tangent to the graph, what else can we do with the derivative? One of the other things we can do is we can try to find inflection points on the graph of y equals f of x. Now, in order to proceed, we'll limit the problem to make it a little easier to solve. And we'll do that by making a couple of assumptions. First, we'll assume that f, f prime, and f double prime are continuous over some interval. And second, we'll assume that a and b are in the interval with a less than b.  Likewise, since f prime of x is continuous over the interval, f prime of a must also exist. The existence of f of a tells us that there is a point on the graph of y equals f of x where x equals a, and the existence of f prime of a means that we know the slope of the line tangent to the graph through that point. And if we put these two things together, we know we can always write the equation of the tangent line. Moreover, since we know f double prime of x is continuous over the interval, we know f double prime of a must exist, and so we can determine the concavity of the graph at any point in the interval. So here's an obligatory mathematical joke. How does a mathematician catch an elephant? Well, one strategy is that a mathematician figures out everything that isn't an elephant, and whatever's left over must be an elephant. Well, in this case, the elephant in the room is the inflection point. So remember that definitions are the whole of mathematics, and inflection point is a place where the concavity changes. So suppose the inflection point occurs of x equals c. Because we've assumed that our function first and second derivatives are continuous, we know f double prime of c must exist, so what can we say about it? If our second derivative is positive, then the graph will be concave up, and it cannot be changing from up to down at x equals c. And if f double prime of c is less than zero, then the graph will be concave down, and it cannot be changing from down to up at x equals c. And so that means our second derivative can't be positive and can't be negative. And since we've assumed that f double prime of x is continuous, it must have some value, and this means that the second derivative must be equal to zero. Now this follows because we've assumed that our second derivative is continuous and that our second derivative has a value at c. But there is always this other possibility if our second derivative is not continuous. If you can't be positive and can't be negative, you might be undefined. What's the geometry of an inflection point beyond the change in concavity? So suppose x equals c corresponds to an inflection point. Let's describe the location of the line through the inflection point with slope f prime of c. So again, since we've assumed f prime of x is continuous, then f prime of c exists, and so there is a line through the graph at x equals c with slope f prime of c. So remember, if you only learn one thing in calculus, you'll probably fail the course. But one of the important things that you should learn is that the derivative is the slope of the line tangent to the curve. And so we might describe this line as the tangent to the curve. But what does it look like? So we know the concavity is changing. So suppose the concavity changes at the inflection point from down to up. So for a little bit before the inflection point, all our tangent lines are going to be above the graph.  So let's actually draw them short and in fact, let's draw them away from the inflection point so they look something like this. But if we're after the inflection point, all of our tangent lines are going to be below the graph and so they might look something like this. And what this suggests is that the backward part of the line through the inflection point with slope f prime of c is going to be above the graph while the forward part is going to be below the graph. And we might say that our line actually passes through the curve. And a similar argument can be made if the concavity changes from up to down. And so we get the following result. Let x equals c correspond to an inflection point on the graph of y equals f of x where y equals f prime of x and f double prime of x are continuous. The line through the inflection point with slope f prime of c will pass through the curve. So we know that if c is a point of inflection, then the second derivative at c is either 0 or doesn't exist. Does it work the other way around? Suppose our second derivative is 0. Does that give us an inflection point? And we might try to find a graph where the second derivative is 0 at some point but no inflection point exists. For example, suppose my second derivative is 0 at x equals 3. If I want this not to be a point of inflection, then I need to make sure that the concavity doesn't change. So maybe the second derivative before 0 is positive and the second derivative after 0 is still positive. And we'll randomly fill in what our first derivative looks like. So if such a function exists, then here's a case where my second derivative is 0 but we don't have an inflection point. So let's see if we can try and produce a graph with continuous f f prime and f double prime, which matches this description. So we'll start by setting down a few points and keep in mind that we may have to adjust the heights at the end. Since the first derivative is positive for all of these values, then we know that the tangent line's slope upward. But because the second derivative is also positive, we know that those slopes gradually get steeper. So our first tangent line might look like this, but the slope of the remaining lines would have to be even larger. So they would have to look like this. Next, since the second derivative is positive everywhere except at 3, then we know that all of these other points, the graph is concave up. So let's try and adjust the heights and fiddle with this to see if we can get a nice continuous graph. And it doesn't really seem possible to do so. Well, let's try at least one more time just to see if we can get this to work. Maybe we'll change our first derivative so that it's negative, then 0, then positive. And we can try and produce a graph with these characteristics. As before, we'll throw down some points with the i towards adjusting their heights later. Our first derivative starts out negative, so our first tangent line slopes downward. But since the second derivative is positive, we know that the slope is increasing, which means it goes from negative to less negative to 0 to positive to more positive. And since our second derivative is positive, we know that the graph will be concave up. And as before, we'll fiddle with the heights to try and make a continuous curve. And this time it seems to be possible to produce such a graph. And so even though the second derivative is 0 at a point, the graph itself does not have an inflection point. And so it's very important to remember, a second derivative of 0 does not guarantee an inflection point.


Every emotion, every experience that you go through in your life is after all you're making. If only be conscious that anyway it is you're making, you will definitely choose the sweetest way to be. Devotion is not only the sweetest way to be, it is also the highest form of intelligence.  So people who think they're intelligent always strive to stay away from any form of devotion. What devotion means? Devotion does not mean going to the temple, mosque or church and doing a particular form of ritual. Devotion simply means that in your life whichever moment in your life when you're aware that there is something larger than yourself functioning around you, there is no other way you will be devote.  There is no other way to be. You may not be bowing down, you may not be performing a ritual, you may not be sitting in a temple, you may not be doing any of those standard things which are expected. You may be not dressed like one. Maybe your clothes are not printed with God's name. Maybe you never uttered God's name in your mouth. But if you're aware, if you're conscious that something far larger than you is in function right now, you're naturally a devotee. There is no other way to be. When you're obsessed by the power of your muscle or the power of your mind or what silly little things that you can do and you think that's everything, only then you're not a devotee. In that condition you cannot be a devotee. When you think you're everything, you cannot be a devotee. When you see the reality of life that you're just a small happening here and something far larger than you is always in function, if you're aware of this, if this is a living reality for you, you're always a devotee. I've never said this before. I hesitate to say this because the word will spread and spoil my repetition. I'm a devotee.   It takes a lot. It takes a lot to look arrogant. What kind of devotee are you? Oh, you must be Shiva's devotee. Shiva is my partner. Let's be very hard for you to digest. I'm devoted to you. Whether you understand this or not, it's very difficult to understand this. Devotion does not mean that I have to bow down to you or touch your feet or sing your praises. In every way, I live for you. That's devotion. I took this very birth to make this happen for you and that's devotion. When you hold someone's well-being above your own, that's devotion. What a devotee does with absolute ease, many other people do it with great struggle. Keep this little fellow aside. What a lot of struggle. What a lot of struggle. Lifetimes of struggle. Standing on your head, holding your breath, going, crawling on the ground and all kinds of things. Devotion is just a simple, sweet, beautiful way of just keeping yourself aside.


Welcome to the Tick-Mail Update. I'm Kiana Daniel, the founder of the Investiva Movement. Wednesday was mainly about Trump's impeachment debate in the U.S. as the government decided whether or not to impeach the president of the United States. Elsewhere, the UK's CPI came in better than expected. Canada's CPI came in as expected and rose 2.2% on the year over your basis in November. New Zealand's GDP was up to 2.3% as expected. Thursday is another big day for the UK as we await the Bank of England's rate. We'll also get Japan's CPI during the Asian session. Today, I'm looking at the Dollar's Suissee pair, which is on its way to complete another range, as it normally does between Parity and 0.9725. The pair break broke below the daily HMCO Cloud last week. This week, other moving averages on the HMCO indicator also confirmed further bearish movement, including the Chico spam breaking below the Cloud. While Trump's impeachment results could create a choppy road to destination, we're generally looking for the pair to reach 0.9725 in the medium term. Of course, trading in the financial markets involves a risk of loss and you should only trade the money that you can afford to lose. If you liked this video, give it a thumbs up and subscribe to the TickMeal YouTube channel. I'll get back to you with more updates tomorrow.


T F N N headline news update Everyone Basel Chapman the host of the Tiger technicians hour coming up straight off this T F N and noontime update I'm also the author of the opening called any newsletter does down 281 off the low below today was 26,000 we haven't moved it over 26,000 130 And it's now trading at 26,195 up up 60 points from the low But still down 284 points this pattern here that we were looking at remember We talked about this for some time those peak D's in the chapwave methodology What we're looking at is also the cup formation and the arch formation straight line moves cup formation arch formation the three Different configurations that are in the market all the time now What's really important is that the support in the dollar is 26,070 That's the 200 period exponential moving average a close below that would suggest. Yep We're gonna test the 25,743 low of just four days ago. It was spectacular move It was what Thursday and Friday as Thursday. Yeah Friday and Monday So what we're all looking at in this particular point is This is a pattern that we got to watch so closely in the weekly chart because these cups and archers are getting closer And closer in and the number of bars before they roll over or they accelerate look at the S&P The S&P at this particular point is down 36 points is trading at 2902 it's off the low of the day which is at the 2906 area And what's really important about this is that the pattern was repelled just like the doubt from the 9 and 14 Moving averages yesterday in the day before very strong. It's filled the gap It's gone down to the low that says that if it was to take out today's loaf it goes to 28 Let me say 2898. This is a really good chance to 2876 level of the 200 period moving average Will be tested very soon the QQQ upside of course is today's high That's gonna be very difficult to attain unless something really fabulous happens on the economic front And yes Ruby will look at December hogs as soon as we get back This is 18612 on the QQQ NDX 100 down 2.10 Here again, the pattern is negative at the moment to make these negatives to cast exonium 43% So as weekly charts this week then again at Friday, that's gonna be so important and the IWM at this moment is down one No, it's down 2.28 and 14660 very very poor action It makes it 145 to 142 level absolutely


Hello everyone and welcome to the session on Windows in TCP learning outcome at the end of the session students will be able to describe the concept of Windows in TCP and uses of it about Windows in TCP. In the previous video we have discussed about what is TCP and what are the different concept to have used in TCP. In this video just we will discuss about different types of windows used in TCP. Here there are two types of windows we have to use in TCP. First one is sending window and receiving window. Before going to that let us see in detail about the or about windows in TCP. TCP uses two windows. First one is send and send window and receive window. For each direction of data transfer which means four windows for bidirectional communication. Bidirectional it means while sending the data and receiving the data we have to use two types of windows and for receiving the data also we have to use two types. So four different types we have to use in a bidirectional communication. To make the discussion simple we make a unrealistic assumption that communicate is only unidirectional that is client to server, not server to client. Client to server it means two types of windows we have to use. The bidirectional communication can be interfaced using two unidirectional communication with piggybacking. The piggybacking concept we have already discussed in the data communication. I hope it is clear the concept about the piggybacking you know. Next two types of windows these two are the main two types that has first one is send window and receive window. First we will discuss about the send window. The window we have used is of size 100 bytes. Normally 1000 sub bytes we have to use. In generally we have to use 100 bytes but actually we want to use 1000 sub bytes. Later we see that the send window size is dictated by the receiver and the congestion in the underlying network. How? The send window below the diagram is there. This is the block diagram of send window. Here this diagram can contain the different parts that are it opens. The send window can open the connection and closes the connection and shrinks the concept. Here it is a first outgoing byte. Next byte to send and timers we have to use. Here different user data is there. The user can send this data 200 is there, 201, 202 still that is 300 and 301. Here first bytes that are acknowledged we have to send and outgoing bytes and then bytes that can be sent. Here first initially the user can prepare the data. After that he can send the data that is first outgoing byte from here and then that is ST we have to. Then after that then if the user want to transfer the next data that is next byte to send this different parts can indicates a different identification. It can identify. Here this data is already sent. This is next byte to send. Then after that we have to bytes that cannot be sent and until the write a router to be the writes. Here these parts here not yet issued in the receiver side for that in detail about this it is in the second one that is opening closing and shrinking the send window. It can initially it can opens the wall that left wall and right wall is there. In the left wall it can closes and then first the user can transfer the data. After that it can closes the connection. After closing the connection it can pass the data to this side. Then after passing the data from the left wall it can shrinks to the right wall. Then after the wall shrinking it can opens the connection. After opening the data will goes to the receiver side. This is a sending sender side part. The user can this by using this concept the user can use sending concept of the data in the client side. It can contain three part that is opening closing and shrinking. It means it can in the before transmitting any data in the left wall side the user can opens the connection after passing the data from this side. It can shrinks in the receiver side that is right wall. Then after it can opens then the data will pass to the next user. Send window in TCP is similar to one used with the selective repeat protocol but with some differences are there. What are those some difference it means nature of the entity is used related to the window. Although actual transmission in the TCP co or occurs segment by segment. What are the different types of entities we have used that we have to define. And then some implementation TCP can store data resued from the process and send them later. The sending TCP is capable of sending segments of the data as soon as it resues them from its process. The number of timers the theoretical selective repeat protocol may be used use several times for each package and but the TCP protocol uses only one timer. Just now in the last video we have discussed about the timers why we have to use the timers it means to check that whether the forwarded data is reached to the destination or not. If not then again once again the user have to resend the data for that we have to use the timers different timer types of timers also we have discussed in the previous video. This is about the sending window. Now the think and write part can contains one question that is what is the role of send window in TCP and compare send window and receive window in TCP. Now pass the video and answer the above question. Now answer for the above question is the role is that the size of send window determines the sequence number of the outbound frame. It means here before transmitting any data the sender size of window determines the sequence number of the outbound frames. Why we have to use the sequence number it means whatever the data we have transmitted from the client side that all the data is reached to the destination or not because we have to give the confirmation because TCP is in connection oriented here the user how to give the confirmation about the data reached to the destination status to the client. So that here we have to use the send window as sequence number concept but before transmitting any data ok. The send window we have to use the CWND is a TCP state variable that limits amount of data the TCP can send into the network before receiving acknowledgement from the receiver side ok. Why we have to it means after sending the data the client have to wait to get the acknowledgement from the receiver side ok. In the receive window is a way it is also a variable that advertise the amount of data that the destination side can receive ok. This is about the receive window and it is about the in detail about the receive window the window we have used is of size in the receive window we have to use the same size that is send window and receive window that is 100 bytes in generally are normally we have to use thousands of bytes ok. The figure also shows the how the receiver window opens and closes in practice the window should never shrinks in the receiver side. Let us see the diagram ok. In the this is the block diagram receive window here next byte to be published by the client and next byte to expected to receive in the receiver side here is also different packets are there or segments are there the user have transmitted these packets and it will goes to this side and after that the data can be forwarded that is next byte here and then byte issued and then they are transmitted here in this data receive the window size alive and then after that this is the part in the receiver side how the whether the data is reached to the destination or not the user can identify this one in this part ok. Here and this is the receive window and allocate the buffer and this here buffer we have to use here in the same concept whatever we have used in the sending window in the sending window the left wall as well as right wall and then after passing the data from the left wall it can shrinks to the receiver side but in the receiver window we would not use the shrinking concept because here we are using the buffer. So, in the what after passing the data or packets or segments in this side the user can left in the left wall it can after pushing it can opens the left wall after passing the data from the user to the left wall then it can closes the connection after closing the data will goes to the receiver side then receiver side after pushing the data from the client side to the receiver side the left right wall can opens the connection after that the data will pass it to the receiver side because if the open wall is not open till that the data will be stored in the buffer ok. In the receiver side we have to use the buffer concept for why we have to use the buffer concept it means for storing the data temporarily ok. This is about the receiving window in TCP ok. Receiving window there are two differences that are the TCP allows the receiving process to pull a data at its own space ok. The this means that the part of the allocated buffer at the receiver may be occupied by the bytes that have been received and acknowledged. It means whatever the data it means user is transmitting five segments the two segments have already reached to the destination and three segments still have to reach to the destination it means if the network is down or some other user is using that receiver side it means until to get the next user is free till that the data will be stored in the buffer allocated buffer whatever the buffer they have used there the data will be weight or it can be stored for a temporary ok. The receive window size is then always smaller or equal to the buffer size because it should not be a less less greater than that the receiver side window we have to use the buffer if the size of that is smaller or equal to the buffer size ok whatever the buffer we have we have used the size of the data sizes it should be equal or smaller. Now it is not it should not be a greater than that because we have to give the confirmation about the data whether it is reached to the destination or not that confirmation we have to give it to the client. So, buffer we have to use the size of the buffer before transmitting we have to check out the buffer size and then that based on that only we have to send the data ok. The receive window size determines the number of bytes that the receive window can accept from the sender before being transmitted ok. Here a receive window is equals to buffer size minus number of weighting byte to be pulled. This one we have to use how much data or receiver side what is the concept or how much or how many sequence are there in a buffer for that we have to use this one that is a receive window is equals to buffer size minus number of weighting bytes to be pulled by the client ok. Receiving window the second difference is that the acknowledgement are used in the TCP protocol. Remember that the acknowledgement is a that is a select to friends is a select to defining the uncorrupted package that have been received. The major acknowledgement mechanism in TCP is the relative acknowledgement announcing the next expected byte to receive. The new origin of TCP however the uses of both cumulative as well as selective acknowledgement as we will discuss later option field ok. These are the references. Thank you.


Welcome, folks. This is Tom O'Brien of TFNN. We have five days a week. We go seven hours a day. We go 24 hours a day on the internet at TFNN.com. Always remember, folks, whatever you think about, you bring about whatever. You focus on growth. Hope everyone had a great weekend, safe weekend. Let's make it a great week, folks. Don't make assumptions. Learn to ask questions. It is always better to ask questions than to make assumptions. Have the courage to ask questions as clear as you can be. Once you hear the answer to the question, you won't have to make the assumption because you'll know the truth. Mm, I get a rise. Let's take a look at it out here. We have the Dow Industrial's trading up $735. Nasdaq up $310. S&Ps up $105. Gold. Gold contract down $7.40. Trade at $18.33 an ounce. With Silver up $9 cents. $21.77 an ounce. Platinum up $8.80. At $9.39 an ounce. Light sweet crude. Up a buck. $110.65. Notes and bonds. Ten-year note. Up $10.6. Trade in $1.15. $27. The third year up a full point. Plus five ticks. At a $133.16. And $Kingdollar. $Kingdollars down $273 ticks. Trade at $104.4. $27. Zeroes at $105. The ends at $136.57. The British pound is trading at $122.00 to $1.00 U.S. Dollar. iPhone numbers<PHONE_NUMBER>. Give us a call, folks. One note's going on in your world. In the world of the S&Ps, let's take a look at them. What do you have? Well, bottom line is you got a nice bounce out here. No doubt about that. You got the S&Ps right now trading up 2.7 percent, the Nasdaq 2.9, and the Dow Industrial 2.4. That being said, guess what, folks? It is building cause for more lower prices. Why bottom line? You get this bounce. S&P, yeah, you bounce over $52 million. You're coming into $176 million. You're coming into $125 million. You can expect the bounce out of it. I expect what you can see, the contraction of volume. We already got one ABC structure inside a larger ABC structure. Bottom line, you got another bounce going. That's in your S&P. We take a look at the NDX 100, same type of setup inside the NDX. What we have with the NDX, the three Q's out here. They are up $8 right now. You're trading at $282.00. Last Thursday, we hit lows at $81 million. We did $82 million on Friday. You're doing $38 million now. You're coming into $94 million. Gold. Gold contract is having a hard time holding price. This is telling me that this dollar has been just strong like bull. This pullback in the dollar looks to me like that's all it might be because this contract can't get out of its way. Right now, you're back $6.70. You do have light volume. We've been trading sideways for quite a bit. Now, if I go to the XAU and the HUI, though, this is what is pretty dangerous in this market right now, meaning in the metal market. The XAU and the HUI, what we did is this. We took out the lows last Thursday and rejected them, but the bottom line is that that rejection looks to me like it's going to go back after it again. The XAU got down to $118.00, $123.00. The low it took out was $119.00. It didn't take out the low that was established out here at $119.01.00. That was established in January. We got to $18.39. We did take it out. That's interesting, man. We did take it out. We're going back down there, man. This thing wants to go back and test. The Gold Bugs Index, same type of setup inside the Gold Bugs Index. We have there the Gold Bugs Index bottom line. We got down to below in January is $236.37. We got to $234.56. That thing wants to get down there again. If that's the case, this good old dollar, very well, this could have been just basically a pullback. It came down hard last Tuesday. Today, it couldn't get under the low that was established on Thursday. The high that it has to get over is this $105.00, $104.13. The way that thing's set up, man, that could be an ABC structure up. It failed on price last week, even on the weekly, but the way the rest of these metals are lining up, particularly, folks, on a day that, you know, yeah, the Golden Silver's up today, but they're not up with gusto, man. So that's telling me that we're not done yet on the way down. Yeah, or at least test them. Some of the high volume equities out here today. We got advanced backers up $2.70. We got invidiers up $8.00. Tesla's got a real move. That's up, and actually Tesla is moving with volume today. That's up $76.00. That's up over 10%. You got mob bells trading up $0.64. That's got a little juice underneath it. Exxon's up $6.00. Now, that looks like a good move, but that came down hard and fast. And the real question is, let's get over and take a look at this oil contract and let's see. Taking a look at it oil, you know, oil right now, this contract we're in the July contract. It's trading $110.65. And the real question is, is that, okay, so we came down hard. Now, what's this? That, what we did last Friday, last Thursday, rather, folks, yeah, 17th. That right there, you know, is very well, could be a loss in golfing, meaning that you have four or five days down. You get open tie, you get clothes lower. This thing still looks like it wants higher price. That's the real bottom line. Let me pull this up here one second. So the volume that we came down on, yeah, they're rolling contracts to one second. CO, CO. Yeah, that's still giving me that one. Yeah. If we go to the Exxon mobile, you're going to see what I'm talking about that.  Well, guess what? Exxon's down off of 105. On Friday, on Thursday, it hit 85. On Friday. Now, Friday hit 85.  You're trading at 92.30. Yeah. Well, actually, anything over 92.05 is saying that, yeah, I can go back to the high. Today, the volume is not bad on it. Chevron. Let's go look at Chevron. CVX. Chevron out here. Yeah, Chevron, this is telling me we're going to go into consolidation here. Chevron's got a high volume low. It broke the swing point. So Chevron wants to go back to its 145.79. Chevron's going up with light of volume today. That's telling me that those oil stocks, you know, bottom line just might get dragged down with the broad market. The next leg down. Stay right there, folks, to come right back. We have the Dow Industries right now trading up 745. NASDAQ's up 316. S&Ps are up 105. We'll come right back.


Hello everybody. My name is Akshay and I'm here to talk about monitoring and managing security vulnerabilities in open source software. The topics I'm going to be covering is what exactly is a CVE. How do you go about monitoring and fixing CVEs? And just the quality of the CVE data or covering statistics about the quality of CVE data and the tools and its shortcomings. And lastly, I'm going to cover security best practices to keep your product secure. And if not anything else, there are a lot of memes so you can have a laugh at those. So what is a CVE? CVE stands for common vulnerabilities and exposure. And whenever a security researcher or a developer finds a software bug which has a security impact, what they do is they notify an organization like MITRE and that organization keeps track of this in a public record or a database where they enter the vulnerability information in that database. And it gets tracked uniquely. However, if a developer treats that bug as a functional issue and does not evaluate the security impact, in that case it would get silently fixed as a regular ratio and it might not make it to the CVE list or CVE database. So your product might still be vulnerable from a security standpoint of you, but it's not tracked as vulnerability from a CVE dictionary standpoint of you. And then there is a whole bunch of undiscovered vulnerabilities which get discovered over time, might be zero-day exploits or might just be caught through fuzzing tools or static analysis tools. So now that you know the different types of vulnerabilities, how do you go about monitoring them? So if you just take CVE data, then there are open source tools which can be used to monitor the CVEs in a product. However, there are a lot of missed CVEs because of various issues with the quality of the CVE data which we're going to discuss in the upcoming slides. And the effort involved in monitoring using open source tools is quite minimal, but at the same time because of the missed CVEs, the product might not be secure. Then you can combine those tools along with some manual analysis of CVEs and in doing so, you can improve the security of your product, but the effort required is much more. So this covers CVEs. If you want to track all the silent bug fixes which have security impact as well, in that case, you might want to look at the security bulletins, issue trackers, change logs of new releases of software and see what got fixed in the latest version of software and then evaluate if it might have potential security impact yourself. And if you want to go into the undiscovered vulnerabilities, then you can run static analysis tools or fuzzers yourself and then discover them. And there are commercial tools available to help reduce the effort, but depending on the tool, it may or may not help secure your product. So you'll have to evaluate the tool on a case-by-case basis before starting to use them. And why exactly is monitoring CVEs a challenge? So if you take a look at the year-over-year data of the number of CVEs being reported, so it has been constantly growing. And in 2018, there were more than 16,000 vulnerabilities which were reported. So if you have to manually analyze each of these CVEs, then it's a big challenge. So how do we monitor CVEs? So before going into the details of monitoring CVEs, I want to just briefly talk about what are the contents of a CVE. The first one is like a CVE ID which is a unique ID given to the vulnerability. Then there's the description of the vulnerability. And NIST adds some additional metrics such as how severe the vulnerability is. And that depends on is it easily exploitable and what is the impact if somebody does exploit it? So it's a score between like 0 to 10. You have low, medium, high, and critical severity. There's also an attack vector field which means that do you need to be physically present at the device or do you need to be like a local user on the device to exploit the vulnerability or can you do it remotely through the network? It also has information whether like user interaction is required or not. And the last key piece of information which is also encoded is something called as CPE which stands for Common Platform Enumeration. And what this is is like it has information as to what the product is. For example like OpenSSL and who the vendor is and which versions of software is affected. So it could be a range, it could be a single version. And this is a key piece because if you're using tools to automate monitoring CVEs then this is the information the tools would look at to figure out if your product is or if the version of software you're using is vulnerable or not. So having talked about the contents of a CVE, so how do we go about monitoring it? So since like Ubuntu and Debian distros have been successful in monitoring security vulnerabilities and fixing them in a timely fashion, so if you consider their model what they kind of do is they manually review every CVE in the CVE feed and then see whether it's applicable to their product. If it is applicable to their product they go ahead and then like patch it, issue security advisories. And not only do they do that, they also monitor release notes whenever a new version of software is released they subscribe to various security mailing lists and then appropriately in a timely fashion fix vulnerabilities. And if you as an embedded developer are trying to mimic that model it's not feasible unless you have a dedicated cybersecurity team. And the reason being there are more than 16,000 known vulnerabilities which are reported on a yearly basis which translates to more than 300 CVEs weekly and you're also responsible for delivering features in a timely fashion. So it's not a practical model. So what are some of the other options? If you were to do it yourself the first step is to gather a list of software running on the device along with the associated version with it. Once you have that list what you can do is look at the NVD feed which is public or go to the NVD website and then like enter that information there and that's going to give you a list of CVEs and for that particular version of software. And once you have that list of CVEs then you can see whether they're really applicable to your product or not. For example you might not be using a certain kernel feature in which case if a CVE is against like the floppy driver and you're not using like floppy in your product then you can safely ignore that. So you'd analyze each of those CVEs, triage them and make a shorter list as to which ones need to be fixed or some of them might not be important based on like how your product is configured. So that constitutes the monitoring portion of CVEs. This is the website which I was talking about. So you can go in there, enter the vendor and product information. It also has an option for entering the version information. You do that, hit search and it's going to give you a list of CVEs for that particular product and version. And if you're coming from a build system such as Yachto, Yachto has this capability called CVE check class.  And at the end of the build it gives you a report which contains a summary of all the CVEs in your build. The only downside is the way it stands right now. Both host and host in the sense like native packages and target packages CVEs are all munched together and it's a giant list. So you'll have to shift through it which is cumbersome. So now you have different ways in which you get a list of CVEs. What do you do with that list? The first thing is you need to prioritize which CVEs need to be fixed. Ideally if you upgrade to the latest and greatest version of all the versions of software you have, you should get most of the CVE fixes automatically. But it might not be practical in that case. So what you do is apply various levels of filtering. So like how I mentioned that if you're not using certain kernel features, the CVEs might not be applicable to you. So you can go through the list. So for example, here's an example CVE list based on IMX Rocko release which is roughly two years old I think at this point. It had by default 658 CVEs out of which 339 were kernel CVEs. So after applying the kernel config filter, it dropped on to like 432. Now if you want to concentrate just on the high and critical CVEs core based CVEs, then it further drops down to 239 CVEs. And most embedded devices you don't have like local users logging into the device and interacting with the devices. So you could probably safely ignore those and look at the network attack vectors, which ones can be remotely exploited. So once applying that filter, you further drop down to like 158 CVEs. At this point, I would recommend going and fixing all of those. But if you're in a time crunch, you can also look at which ones have public exploits. So typically references for public exploits are also available in the NVD feed, or you can look at like a website called exploit DB. So which CVEs have exploits and prioritize those because those are the ones which most likely hackers would first target. So now that you have like a prioritized list of which CVEs you plan on fixing, how do you go about patching them? One option is to see if the latest version of software already fixes it in case it does upgrade to the latest version. Otherwise, look at the reference links in NVD to see what is the commit ID or where does the patch reside for that CVE and then back port it yourself. You can also look at commit logs from upstream packages. Typically people do tag CVE information in those as well. And if you do back port them, then you might have to maintain patches because there might be the number of CVEs over time keep growing and if you continue to back port other CVE fixes, there might be conflicts as well, which might not cleanly apply. So you might be on the hook for maintaining them as well if you do not upgrade the software. Talking more about like upgrading the software versus back porting, first question you get asked is why don't you just upgrade to the latest software? Most time like there are API changes, especially in user space components and that means you might have to change your application and if you're using like third party applications, you might be stuck with older versions because the third party application might be slow to make those API changes which your user application depends on. There might be license changes as well. So you might end up back porting which is complex but if you do do the back porting then if there is a public exploit available just run that, make sure the back port is cleanly done such that the exploit is not able to... such that the vulnerability is addressed with the back port. You can also run package tests in Yocto to make sure there are no regression related issues and make sure the back port is good. The last aspect is the practicality of addressing CVEs in the Linux kernel. If you consider the Linux kernel, there is one release every five days or so for the LTS branches which is good, which means it's getting all the bug fixes and the CVE fixes into the LTS branches. On an average, there's like one to two CVEs fixed but at the same time it means that you need to continuously upgrade and run tests and many times product test cycles are greater than five days. So how do you keep up? So this is where like having like a monthly release cadence or when sufficient number of like high or critical CVEs get accumulated then immediately jumping to the latest minor LTS release might make sense. And the kernel config filtering will definitely help because if the CVEs don't affect you then you might not need to upgrade. The other major thing which determines how many CVEs are there in your product is the number of packages in your product and how old your release is. So if you take again Yachto as an example, if you're running like core image minimal even a two and a half year old Morty release of Yachto just has 33 CVEs and the master branch has like just four CVEs. Whereas if you consider core image seto which includes a lot of graphic libraries and various other packages, it has 336 CVEs just from a user space standpoint of you and this does not include any kernel CVEs whereas the master branch contains 14. So periodically updating to the latest version of Yachto makes sense especially if you have a large number of packages. And it's also crucial that if you're not using certain packages get rid of it reduce your attack surface from a security standpoint of you. So now that you know how to monitor and patch CVEs the next step is the real issue with CVEs is the quality of data in the NVD database. So there are various issues. The first one being like inconsistent naming. So if you consider a package like ARM Trusted Firmware there are CVEs listed in NVD database against ARM-Trusted Firmware ARM-Trusted Firmware Trusted-Firmware-A. So if you did not know to look for all those three products you'd miss CVEs against that particular package. There are other issues where there are typos for example 2.23 might be listed as 2.2.3 in the CPE information in which case your automated tool would never cache that and report that CVE leading to a missed CVE. There might be typos and names as well. And sometimes there's incomplete analysis. So for example they may say all versions up to the latest version of software is affected because that's the easiest thing to do instead of figuring out which commit actually introduced the CVE and in doing so it will result in false positives. So if you're in the older version of software which is not affected you might still be, your tool might still be flagging that package as having a CVE. On the flip side sometimes there are entries saying only the latest version of software is affected whereas the prior versions of software also are affected. And lastly there is the issue of no CPE information or no version information leading to missed CVEs. So how do you address some of these issues? The doctor has solutions for some of these. So for example you can specify a CVE product and what that means is you have your Yachto recipe name and that needs to map to the NVD name for a particular CVE. So for curl, CVE might be listed against curl or lip curl. So by specifying the CVE product saying like curl, space, lip curl is going to search for CVEs against both of those in the NVD database. So this will reduce the number of missed CVEs. If the Yachto recipe versioning scheme is different from what's in NVD you can also have a CVE underscore version which will help you do the mapping between Yachto to NVD. Lastly the Yachto community itself is pretty good at backporting CVE fixes and when they do that they tag that information in the patch headers or in the file name itself. So the CVE check class looks for the patch headers and or the CVE ID in the file name to see whether the CVE is fixed. This way you don't have to look at CVEs which are already fixed which helps you save time. All these solutions are good but it totally depends on which version of Yachto you are on. So taking CVE product as an example, if you consider the Morty release which was like two years back against Watts Warrior there's 22 entries for CVE product which is missing. So nobody backported those CVE products to Morty. So 22 might look like a small number but it means that 22 of the packages are not being tracked for CVEs and that translates to 151 CVEs which are missed out of which 96 of them were high or critical. So you need to consider that when you use the CVE check tool in Yachto and this is just including Pokey. Not even talking about the hundreds of other meta layers out there I haven't analyzed those, just analyzed Pokey and that's the data from that. The other aspect of it is the tools themselves constantly improve and recently Yachto moved from CVE check tool to something called CVE update database and that's only in the master branch and what that does is it moves from like a XML feed which used to do like a string comparison to using the JSON feed and doing logical comparison like greater than or equal to or less than equal to for version numbers and just taking three recipes as an example for the same version of the package with the old scheme and new scheme there's like 10 new CVEs which are being reported and that's only in master branch. So unless these patches have been backported to previous versions you might be missing a lot of CVEs because of that and as the tools improve you get a lot less missed CVEs but at the same time it exposes some of the other issues with the quality of data in NVD leading to more false positives so that's at least been my experience using that. So how do we improve the NVD feed data quality? So first thing is if you see something which is inconsistent or inaccurate just send an email to nvdatmiss.co My personal experience is within an hour they update it and their website is updated, the feeds are updated and it fixes the issue for everybody so everybody doesn't have to keep looking at the same CVE saying like oh this is bad data and continuing to ignore them so that's the least you can do. If you see any discrepancies in the CVE summary or references you can submit that information to MITRE and if you see the CVE product which is being missed for a particular recipe submit a Yocto patch or if you want to improve the tools yourself you can do that as well. So there's also another issue with the CVE data quality that's mainly for the Linux kernel. So whenever a CVE is being reported against the Linux kernel what NVD does is like they analyze that and then report it against all versions up to like the latest version let's say 5.2 for example. Then the kernel maintainers propose a fix, mainline it and then the community or the stable kernel maintainers go ahead and then backport those fixes to all the LTS branches. However, NIST does not go ahead and then like reanalyze these CVEs to say okay this fix was backported and they don't update the NVD database for it. This results in a lot of false positives. Just taking 4.4 as an example, if you query the 4.4184 kernel there are more than 400 CVEs being reported out of which 415 of them are false positives. So just waste all your time looking at these saying okay these are not applicable to me because I'm on like the latest LTS release of 4.4 kernel. So those are all problems with the quality of data. Then there is another aspect which is the delay in reporting the CVE data itself. So it can vastly vary. So taking two of the CVEs as an example, the processes the security reporter goes back and forth with the maintainer in private. After the fix has been developed, then what happens is the maintainer either discloses it on the public list like OSS security. If you're not subscribed to it, I would recommend subscribing to it. That's where most of the CVEs do get reported or else it might get reported on a private list like distros where it goes through a seven day embargo period where Linux distributions can patch it so that they don't have to scramble on the day when the CVE is made public. And then once the CVE does go public, the CVE starts showing up on NVD. And after a few days, the CVE is analyzed and the NVD entry is updated to add the CVE information. And if your automated tools rely on the CVE information, it's not going to report the CVE until this initial analysis is done. So it could be up to like, for example, in this case, 68 days before your tool starts reporting that CVE against your version of software. Here's some fun stats. So from when NVD publishes the data to when the initial analysis is done, which is when the CVE entry is added, it could be in 2017 the average delay was 11 days. 2018 it went up to 34 and then 2019 it went back to 10. So it varies quite a bit there. And there's also another interesting thing where sometimes I talked about these silent bug fixes where a bug gets fixed and years later somebody looks at that and says, hey, this had a security impact and then goes ahead and then requests MITRE to issue a CVE against that. So there's an example for a CVE from 2019, which was actually fixed in the kernel in 2016. So three years later somebody requested for a CVE for it and it got assigned. So Red Hat, for example, tracks such information where vulnerability was actually made public. So if you consider that with a grain of salt for a limited number of set of packages, the average delays were roughly 101 in 2007 and it's down to 25 in 2019. So next time when you see a CVE in the news and you're wondering why your tool is not reporting that CVE, that's probably because the delays in the CVE information being added in the NVD database. So how do you mitigate some of these? So most of these CVEs are already being analyzed by Ubuntu, Debian, Red Hat, and most of them have public trackers available. So if you can write scripts which can aggregate that information from Ubuntu and Debian, then you could leverage or reuse some of that information to report the CVEs in a more early fashion for yourself. And Ubuntu also has commit IDs as to which commit fixes a particular CVE and which one introduced it. So the Civil Infrastructure Platform uses that to reduce the number of false positives in the CIP kernel. So another aspect which I wanted to talk about was Secure Boot. So many of our customers implement Secure Boot, Chain of Trust, and then just forget about it thinking their product is secure. But if you go back and look at CVEs affecting, let's say the processor itself, for example, the IMX processor had few CVEs related to Secure Boot in which it would allow unauthorized code to run because of a buffer overflow issue in the checking of the signature. Arm trusted firmware, Opti, which are Secure World operating system code, also have multiple CVEs reported against them. So it's not enough to just initially design Secure Boot. As part of development, you also need to continuously monitor for CVEs against those. And it's not just software which are assigned CVEs, it's also like processors and processor firmware. So if you look at the Snapdragon 410 processor and look at how many CVEs are there, it's like 246 CVEs reported against the processor and the firmware, binary blobs as well. So you need to look at those and manage those because those are typically not included in your build system like Yachter. So given all the challenges with monitoring CVEs, what is a good strategy? My recommendation is a two-fold approach. One is during the design of the product, bake-in security. And what that means is whether you're locking down hardware by disabling the serial console, disabling JTAG, implementing Secure Boot, Chain of Trust, implementing access control like SE Linux or App Armor, and then the other key aspect is having a secure firmware update mechanism such that when you do discover CVEs, you can go ahead and then securely deploy new versions of software, reduce the attack surface by reducing the number of unused components. And the next aspect is staying secure, which is periodically updating your software versions, managing vulnerabilities, monitoring them and then patching vulnerabilities, also having some sort of audit log and monitoring that as well. So from a tool standpoint of you, if you're evaluating any commercial tools or if you're trying to improve the existing open-source tools themselves, here are some of the wish list such that the effort involved in monitoring CVEs can be reduced. One thing I talked about was kernel-config-based filtering. So you can go ahead and then have some kind of CVE to kernel-config mapping so that you don't have to look at those CVEs if they're not applicable, having ability to add notes for a particular CVE, team collaboration, sharing. Another thing is right now with the Octo, whenever you run a re-scan of the CVE, you don't get a comparison report. So you have to manually diff the results and figure out which ones are new which ones are already addressed, so on. And the other aspect is, are there multiple sources other than NVD being used to mitigate the delays in NVD updating the database? So if you want to see some of these features in action, stop by the times booth or check out this particular link, we have a tool which can help with some of these things. So to wrap most of these things up, the key takeaway is there is no magic bulletin managing and monitoring CVEs here. So you need to design security in from the get-go, allow for firmware upgrades, continuously monitor mailing lists, triage them, triage the vulnerabilities, patch and update to the latest version of software. Try and automate it wherever it's possible, but just be aware of the more you automate because of the quality of the NVD data being bad, you might result with missed CVs and false positives as well. And whenever you do see such quality issues, go ahead and then improve the database by sending an email to NIST or submitting Yachto patches for the tools. And if your product does not have security, please don't connect it on the Internet. That's it. Any questions? Fido. That's like more than four years old at this point, I think. Okay. So I don't think I can answer that off the top of my head, but I think it should be fairly okay because the tool itself is like natively compiled and doesn't have too many dependencies other than like Python and URL lib3, I think. So it should be possible to backport, but Fido is not actively maintained, so nobody's going to do it, so you'd have to probably do it yourself, and if you do, you can contribute back if they accept those patches. Yeah. Any other questions? No? Okay. Thanks, everyone.


it over. What's up money geeks Mr. V here welcome to another video guys so in today's video we are going to talk about tesla stock split so we're going to talk about if this is a buy or this is a wait or whatever it's going on so we're going to cover that in today's video but before we get started guys if you're new to the channel we talk about how to earn money how to save money how to invest and build wealth so if that's something that interests you go ahead and hit that subscribe button and your notification bell so you don't miss out on new content so i did a video here when tesla first announced that they were going to do a five for one split so i did that video if you haven't already checked it out i'm going to hook it up here so you can definitely go check it out to this video we're just going to take it one step as this talks the split is going to start trading on monday august 31st so the question is should you wait or buy or i mean like what should you do and people have a lot of questions to as far as hey what happens to fraction issues if you own fraction issues so we're going to cover all of that today but where i want us to start is yes the split has already happened if you were holding tesla as of friday august 28th that is that's it it's done the split has happened so as we get up monday morning august 31st you're going to see that instead of the one share that you had for tesla you're going to have five shares the beauty is that the value of your shares is not going to change so if you own one share of tesla all you're going to do is take that share and split it into five so it's going to be the same amount you're going to use an example here assume that you have a pizza right one big peter you cut it in five pieces it's not like you've added or taken away from the peter it's still five pieces that make that one so the value of your pizza is still the same but it's just been broken up into five separate pieces so that's what tesla did and so that's why you're going to get up in the morning you're going to see that the number of shares that you own would be higher but the value would stay the same then the price per share would be lower than what you were that you closed the market on friday with so it's not something for you to panic and so in a situation like this a lot of people are wondering like hey this is a good time to get into tesla because what they call formal that fear of missing out a lot of people miss town and tesla when it was at say 150 or 200 or 250 300 350 even as just as just back in march when we had that huge covid crash tesla came down to 350 most people still didn't buy and then tesla just skyrocketed all the way to over two thousand dollars so you're going to see a lot of pressure in the market tomorrow a lot of volume people again this is my speculation i'm anticipating a lot of people are going to want to jump in because they don't want to miss out this time and that's going to push the price up because the way the market works is that you have people that are selling you have people that are buying so if somebody is if somebody wants to to to buy in there's not enough in the market they're going to increase their their their their price right they're going to they're going to increase the price to to so that they can they can get filled so if let's say if i want to buy the stock and nobody's willing to sell i'm going to keep opting my price like hey how about 2000 how about 2500 how about 2700 until somebody on the sales side be like oh that's a good price i might sell it at that price so i'm anticipating again that as soon as the market opens on monday morning we're going to see huge volume orders are going to come in people are going to be selling people are going to be buying again for people that are long term if you can go in the lower the price for you to enter the better for people that are going to swing it they can just go in it moves up they sell it and get out for day traders and again i'm going to say i'm anticipating that a lot of day traders are probably going to want to trade this and then some people are just going to wait for it as soon as it goes in that first rush that mad rush as soon as that slows down it starts pulling back some people are going to try to short it so there's so many strategies that are going to play in here but here's what i want you to do if you want to buy tesla long term don't buy tesla long term just because you hear about people talking about it or you're worrying about the fear of missing out i want you to buy tesla long term because you understand the business model you believe in what elon mass is doing and you know for sure that this company is worth 393 billion dollars and i guarantee you that after monday the price of this company might be 300 or maybe 400 billion dollars who knows but i want you to approach it from that perspective especially if you want to hold it long term if you're day trading it you have no emotions all you want to do is either go in uh low and and sell high and if you are people that do short selling you want to buy high and you want to sell high and then buy low and make some profit that's it but if you're long term you want to hold this for for the long run make sure that you understand that this company has so many other company not just cars and here's where i personally i'm holding have a position um in in my account that i'm going to hold long term the reason is because i don't just look at tesla as a car manufacturing or ev car manufacturing company i look at it more as a technology company first and then secondly uh from a business standpoint yes they do make cars do make cars that people are excited about secondly they've actually shifted their business now they do talking about not just supplying uh cars but also supplying batteries and they have uh i think battery day is coming up and illa must is going to present on battery day and so they're going to try to make battery as a service so b a a s so that's barriers a service where um and people can can actually um subscribe to to the service and get batteries i don't know how they're going to do it if you're going to get your battery shipped to you every month or you can go get it charged somewhere um i know at the fee and get your battery replaced every month i don't really know how that's going to work but they are building that business model and then the solar panels too where hey not only would you get shingles in your house but the shingles are going to be solar panels so you have shingles that are powering your house which is awesome and then they have the mega pack which is actually used um to store power so if you go to like windmills and all these other places you can store windmills even in your house you can have a mega pack where um you have backup power where if you like where to go off it would switch that backup and and continue to power your house until lights come back so um tesla has so many things um going on for them um and again i'm anticipating that uh once you're staying um the market opens on monday morning the price of this stock is probably going to move a lot but right kind of ten percent um just to start the day but eventually um pretty slowly back up to somewhere around the six seven hundred or eight hundred mark even by december because battery days people are going to be talking about tesla so they're not going anywhere soon um i'm super excited about it so um question of the day guys what do you anticipate uh is going to happen to tesla in the next three months um again let me know in the comment section my personal take i think the price is going to squeeze up um during the market open on monday there will be a huge rush and then slow down before maybe a little pull back and then gradually start pulling up again um over the long run but again i want you to go in with that mindset that this is not just um because everybody's talking about it or the fear of missing out that you understand why you're investing in this company long term you're not worried about anything so hey let me know in the comment section again if you're looking to get started with investing um now we have a promotion going on with webo way if you sign up um using the link in the description you get two free stocks not one two to get you started when you deposit a hundred dollars i think it's a wonderful deal to get free stocks to get you started it's awesome so again check the links in the description below and as always guys stay motivated


What's up everybody takedown here welcome back to the channel so recently I've been working on a nether video Talking about flat earth theory more in-depth and it really got me thinking if I could pull off a prank Where I pranked my best friend jack into thinking that I believe in flat earth and it turned out amazing Let me show you what I'm talking about You think the earth is flat No, oh Right, right, yeah, I thought you did too Yeah, yeah, I am believe the earth is flat Well, I mean it is but Your mics your mics hot note all I'm hearing is it It No, but my one cut now. I'm just sincerely at a loss for words. I'm never at a loss for words I know That I'm right. No But you gotta think of the facts though like the facts or what back it up. Yeah There are facts Yeah, we'll take the same approach you do My choice to be a Christian every time I thought it up. You've been very respectful Yeah, I'm gonna do the same thing like this even though in my opinion this is off base When did you make this? I really remember that Come to this realization that the world is flat I mean I'm not sure like when I thought of it, but Never really asked him. Did you like watching YouTube video? Well, I mean I've been I've been Over the years hearing different things and it's like, yeah, I see that I don't know how really to Scribe it All right, I just got to tell you right now, okay, yeah, I gotta tell you something The earth is round But I'll tell you why I did it I Am making a video I'm trying to get ideas flowing and trying to get some of the facts on both sides But I'm gonna make a video talking about it Because it's an interesting topic to me at least Oh No, this is gonna be a side video.  I'm so happy with the outcome Jack isn't one to usually fall for anything like this that I do but for once I actually made him do it and the prank turned out Well, usually pranks that I try to do Don't turn it well because I'll usually start laughing and then they'll catch on that it is a prank But that did not happen today surprise surprise, but I'm super happy I do want to thank Ashley her YouTube channel is dead girl superstar I recommend checking her out she did a video similar to this on her channel And I asked her if I could use this idea for my channel for my video and she said yes go ahead So I'll leave her links down below But I'm super happy with how this turned out the main video where I talk about flat earth theory should be out pretty soon I recommend checking it out because I'm actually shocked with what I found out But I'm gonna leave this video here. Hope you guys did enjoy. Please take care. Peace