Now we'll go into the Q&A. So if you have time, stick around, I'll answer all the questions that you could possibly have and I'll answer them the best of my ability, but that takes care of the segment for just news. Now we go into Q&A. All right, and that will be right here. So there was some great comments I saw before we even started, a couple of them. This was this call my attention. Jojo says, sell everything, we are entering a depression. And I gotta tell you, Jojo might not be wrong. And I know we just talked about a lot of great things right there, but you know, the job of the Fed is to stop a depression. I think a recession, which I think a lot of people believe we're gonna go towards is like the middle of the road, best case scenario. And I think that's where we're headed. Now when we do that, we're gonna get a lot of opportunities to buy all these things that were super overpriced, let's be honest. But a depression, that's why it's so important that these supply chains get opened up because the demand is still high, but there's not enough for those to actually get to people and then actually produce. So then you're gonna have a lot of problems with manufacturing. So the Fed can do only so much. They can raise those rates, which will probably help with like we talked about with the housing market, raise those rates. That's not gonna be much for supply chains and things like that. If things don't improve, and especially if we start to see unemployment rise, not too good. So do I think a depression, depression? I don't know if they'll allow that. I think before we hit that, we're gonna see some pretty big hikes by the Fed because they're like, let's pull all the stops, we don't want that to happen. And that's exactly what happened when Volcker was in power. I shouldn't say that, that's kind of like that. When he was the Fed Reserve Chairman in the late 70s, early 80s, when you had inflation above, I think it was like almost 12%. And because of his aggressive rate hikes, he's one that they credit for staving off the depression in the early 80s. Just a little history. All right. And then gas fee fees says recession is a good time to eat less and lose some weight. So I quit and plug in. You're not wrong, that is for sure. So, but don't worry everybody. Like I said, short-term pain is necessary for long-term gain. That's what it is. Rob, where are you? I didn't grow up in Iowa. Midwest, I think positive. Yes, exactly. Yeah, yeah, yeah, yeah. So this is from Joby Anderson. I worked in the US manufacturing department of defense related and we can't get parts. Terrible sign, not a good sign. And there's some of your proof right there. Now, not to say that it's all bad, but we know the supply chains are a little bit stressed right now, we will say.  I think it's a national security issue. And I've talked about this before, but this goes over. Echoes from above? Coming recession. If you guys haven't checked out Echoes from above, great channel, macro does way better stuff than I do. He says the upcoming recession is gonna be rough. Hang in there folks and keep cash in emergency fund. That's right, emergency fund. Save that fund. The rainy days right behind us or right in front of us, I guess. Hey, Rob, are you happy with the deal you got at Celsius? Is it manageable in a bear market? So if we're talking about the loan that I took, no. And we talked about this, I already got liquidated on that one. So I talked about this in depth a couple of weeks ago. So when I was over in Europe at a guys event, I had a loan.  And there was margin calls and I covered those margin calls. There's more margin calls, covered those and covered those. However, when I was in Europe, I was a little bit busy and that was a time when everything just went, pfft, I think that was runtime Luna actually crashed. And I was out of service and they liquidated me. So that's what happens. So the thing is, you have to remember though, is that for Celsius or any kind of crypto loans, when you put it up, let's say you need, I don't know, let's say 10,000 bucks, right? So I was gonna say, do you want $10,000? We'll give us $20,000 worth of whatever, Bitcoin, Ethereum, polygon, whatever. And that's your collateral. And when the loan to value ratio goes down, let's say that, you know, polygon goes from whatever it is and it goes in half like you need it to recladlize. And if not, we'll liquidate you because we don't wanna be under duress because we have a lot of people. If you don't collateralize, then they just liquidate you. Do they liquidate every single thing that you put in? No, they only liquidate the parts that will cover the initial cost of your loan. So in this case, if it's, you put up 20,000 of worth of Ethereum and you got $10,000 in cash, then the value goes to 15,000, they will liquidate $10,000 worth of your Ethereum and they will give you back the $5,000 worth of your Ethereum. They didn't liquidate, because that's yours. So there's a little bit of a price difference. I'll just tell you that. And then also be very well aware that borrowing money is not taxable. Borrowing money has nothing to do, you will not get taxed on the money that you borrow, but you will get taxed and everything got liquidated because they had to sell it. So just remember that. So it looks like old Rob's gonna have another tax bill, even though he lives in Puerto Rico, that's just because I can buy those Ethereum a long time ago. And that would actually leave me to my next point. There's a term called buy, borrow, die. And that's what the super rich do to get away from cap gains. They will buy an asset, they'll borrow against it, they'll put that in the trust, and they'll be able to die and leave it off to their family. Family hair is a trust, no taxes. Did a video on that, you should check it out. And it might help you if you're super rich. Okay, good stuff. What do you think of Kevin O'Leary as a crypto advocate? He's been very vocal to late. He cares about the industry, not just his coins. Debatable. Look, I'm not a big fan of the people who are out there in the public because they can turn you just like that. So to me, Kevin's a tourist so far. He's done a lot for the industry. I think he'll do a lot more later on. Time will tell. But I like the fact that people know Mr. Wonderful, Kevin O'Leary, and they say, hmm, I heard that Bitcoin was for the mafia and it was for terrorism and it was for money laundering. But Kevin O'Leary, he's on Shark Tank and he's a wholesome gent. So maybe I should give crypto a chance and that is the bigger news. And I think Kevin also is going on its pretty effective way as far as buying up exchanges in Canada and positioning himself as probably a leader in DeFi and crypto. So we'll see. We'll see. I don't know. Ah, Jacob, yeah. Oh, so this is a good one. Jay says, hey, Rob, what are your thoughts on JP Morgan now becoming more of a Bitcoin advocate? So JP Morgan, a couple of weeks ago, they came out and said that crypto was a pristine asset and they were swapping things around to get to unload some of their real estate positions to get more into crypto and digital assets. I found that very perplexing why they would go that route. However, I mean, if you think about it in the long run, what's gonna happen with real estate? The prices of real estate are gonna go down pretty far. And the reason is because as the rates go up, there's gonna be a lot of supply because all these, all the construction people I know are all working on new houses. The problem is is that when you have the Fed raise the rates, then people like, well, shoot, it was just 2.65% for a mortgage and now it's over five and it's only gonna go up to six, 7%. I'm not doing that. I'll just rent until they go down. So what does that mean?  So if J.P. Morgan was into that, they're just losing money essentially because it just sits there and does nothing. And it'll just sit, you'll have too much inventory and not enough demand. Now, that's them. If you wanna play it a better way, not financial advice, but I will tell you this, there's a reason why my wife did not buy a bunch of different houses and things during like the big run up. And actually we sold two of our houses in Houston.  And the other reason is that all we had to do was just wait when the sidelines just go, when are you gonna crash? And I hate to say it like that, but it is the truth. And that is exactly what happened in 2007, eight and nine. So I thought maybe it's pretty good play. Again, the other big question you gotta ask yourself is where are you gonna hide your money? You know, I mean, 8.5% is a pretty high inflation rate, although someone did say, make a good point. They go, look, I could rather, I have my cash in my bank account and yeah, it is 8.5%. But if I would have put it into Luna, I would have lost 100% or on Ethereum, I would have gone down 20% in a week. So what's your talking points there? And I was like, that's not a bad point. So it comes out of this. If you're looking for some short-term opportunities, it's pretty tough, always look long-term and things usually work out for the best, for the better, I would say. All right. Idle Luce has prepared for a double dip before the Wicca. We'll see. Maybe this is a bull trap. Hey, Rob. Marco says, hey, Rob, I really think Ben, talking about Ben Cowan from Into the Cryptiverse is right with his thoughts on market movement. He's super smart cat. That's for sure. Would you agree with Ben as well? Yeah. Ben thinks, and he does great, got a great channel. He's actually, we do a show together, DCA every Friday. And he also has a really good website, app.Into the Cryptiverse. Links in the description, non-affiliate link. Ben doesn't pay me a dime. I just like to talk about it. And a lot of the things that are there, which are great to look at, but there is one that I really important and it's called the risk assessment chart. And what it shows you is as the price starts to go up, the risk assessment goes a little bit to the right. So everything's between zero to one. And as we start to go down, you can see the risk assessment go, of course, the lower it goes, the better off you are. But there's these time frames. And he talks, and in the website, you can see like there's a point between zero and 0.1. It's only like a finite small amount of days. And we're getting towards that level. And when that level comes on, it doesn't last that long, but it's usually a great indicator for the bottom. So I think Ben's right on that one. I'm not sure if he's a hundred percent right on like, because he says don't get into alt, cause alt's are gonna get slaughtered. And he could be right. That's why I do what's called micro DCing. Every other week I buy a specific L1 crypto and go from there. And we'll see if it bottoms out. And if it doesn't work out like, like this one where I'm stopping the DCA until Friday, if it doesn't work out, I take a 5%, 10% haircut because maybe it goes up and I just keep doing DCA. So we'll see.  But right now I think it's like 56% dominance. Correct me. Is it 56 or 46? I think it's 46%. Let's find out. Let's go to his website, huh? Show all the secrets. I'll just do one thing. Let's see, let's see, let's see. Derivatives, social media, mining exchanges, valuation. Can't show you the risk. Supply addresses, valuation. Damn it, where'd it go? Supply, I'll find it in a second. Other, ah, ah, here we go. Yeah, 46%. I wish I could show it to you. Oh, let me see. Ah, it's right here. Sweet Mary Joes. Let me share my screen. I don't wanna, because there's some things Ben's like, don't show that part. That's only for paid customers. And the other one's like, okay, you can share that stuff. So hopefully this isn't the one I can't show. So this is Ben's website, a lot of great information. Here's the dominance in red. I didn't know it went up that high in January 2021, almost 69, 70%. And now here we are, 44. Why is that important? Because you start to see that people will start to sell off their alts and go into Bitcoin, such as myself. And you got 46%. So that's just one of them. And he's got some really good stuff over here. Volume of crypto options, exchange of money, transactions, supply, moving average. This is a good one, return on investment, monthly returns. I always like to see this one just to see where we're going. Cause man, we're going to, June's not a bad month. May was a junk month, negative 15. One of the few ones. I don't know. Just get to look at it and some other stuff. Blog rhythmic regressions and such. All right, let's see. Junk bond trader says there's so much more to crypto beyond Bitcoin. Don't tell the maxies that.   And you know what's funny? There was a great interview with Peter McCormack from what Bitcoin did and Lynn Alden. And in that show, we talked about this a couple of days ago, even Peter McCormack, who is like super Bitcoin maxy, was like, you know, he goes, in different countries that I've visited, there's these people that need stablecoins and they use stablecoins effectively. And it actually is a really great thing for them. But he says, they're based on Scoin protocol. You know, he's like, well, there's Ethereum and there's Tron and stuff like that, but he's stablecoins. He goes, so maybe stable, maybe he goes like, maybe these other coins aren't so bad. He goes, because if you're trying to do a store of value and you've got your, you make 100 bucks a week and Bitcoin goes down by 10, 15%, that's not a store of value. He goes, stablecoins really are good. And that was the first time I've actually heard anybody say anything positive as far as Bitcoin max books. So that was interesting. Robbie, you shouldn't give financial advice. I'm not giving financial advice.  I'm just telling you what I'm doing. And I say, don't forget, it's up to you to think about taking profits. And that's it. So Robert says, you shouldn't be giving financial advice when we're Luna. So if this is you talking to me about how I talked about how I dollar cost average and to Luna, I didn't give you financial advice. Did I tell you to buy Luna? I told you what I was doing. And that was it. I really don't like when people put words in my mouth and say, well, you did this and you did this. I didn't, I'm not your dad. So if you don't like the information I'm giving out, go someplace else.  Me personally, yeah, I bought Luna. Yep, I'd dollar cost average. I also was told that I was doing Bitcoin, Ethereum, Luna, Cardano, and things like that. And I'd go along the way, I've been saying the same thing. Have I not? Take profits. Nobody, everyone broke taking profits. It's a funny thing that I say these things and then people somehow forget about what's going on. Also, I will say this that in December and January when I was talking about taking profits, I got this weird look from everybody like, why are you doing that? Diamond hands forever, baby.  Okay, you know what's funny? I don't hear a lot of diamond hand talking right now. Just saying. I just, look, I'm gonna let that go before my blood pressure goes to the roof. And that's it. All right. Why keeping alts as they're bleeding against Bitcoin and bear market? That's up to you. You don't have to. So the thing is, is the same thing happened in 2018 when everything started to go down and everything was bleeding against Bitcoin. The question was, why even hold on to alts? Why don't just go everything and put yourself into Bitcoin? Well, there's a couple of reasons. Some people, they're like, they're not 100% sure that's actually gonna happen.  If I'm here for a three, five, 10 year outlook, I know right now it's not the greatest. And maybe if I was really gonna think about it, maybe I wouldn't even put it into Bitcoin. Because I mean, if you're thinking about, well, it bleeds against Bitcoin. So you put it into Bitcoin and then Bitcoin goes down. I mean, really think about this for a second. If you're not gonna think long term, if Ethereum goes down 10% and Bitcoin goes down 3%, you're still down, right? So if you're thinking about it very long term, you could say to yourself, well, look, I'm gonna go into stablecoins and just kind of write it out there and tell we hit whatever I think is the bottom and then starts to really accumulate. Here's a news flash. You will not hit the bottom. You will not time it perfectly. And you won't sell the top. I've been trying for quite some time. Hasn't worked out for me. Some people will say, yeah, but this one guy did it. Ah, that was mad. Is your son still mining helium? If yes, does he see if that's a good, oops, lengthy play? He still is, but he tells me that it's not very profitable right now.  So that's it. But he's in LA and everybody's mining helium. So it's like the worst place to do it. Sell in June, go away. I wish I would have said sell in April, go away. That'd have been perfect. But there's a video we did just digitalized that news, sell in May, go away. We did that in April, I think. April or March. And it was just a study that took a look at, you know, years and years of that old adage from Wall Street, sell in May and go away. They found that, you know, over the last 50 to 75 years, it's pretty darn accurate. So I see a lot of pain in the summer and then maybe a little rebound towards the end of the year. But 2022, let's be honest, is not gonna be like a bull run in any way, shape, or form. Jump on trail, fair take, thanks. All right. Chewie says, Kevin O'Leary doesn't care nothing about the industry as long as his money is going up. Well, he is an entrepreneur and that's pretty much it. Money talks and that's out. Let's see. And Aco, I think I answered this. So there we go. George and Robert the best, thanks. George does a lot more live streams than I do. He also has a car channel, you should check that out. Sus. Oh, this is interesting. Edward says, Sweatcoin is helping me and my wife to walk more, great. That's the whole point. Found out my son, found out my son since 2020 and literally impossible to catch. Yeah, that's the problem. And I will tell you, a lot of times when I look at my phone, I look at the steps and I'm like, damn, only at 7,000. I need 3,000 more steps and it forces you to kind of get in there. It's just a, it's a gamification. And if that helps you live longer, not so much the worst, I'll take it. 46.8, 47.5, 44.6, Bitcoin domination. And of course, it's different everywhere. You guys are correct. Yeah, so this is something. Jae Young Chow says, do you ever look how in real estate people are over leveraged with private loans and that can lead to another black eye for crypto? I feel July will be, it's historically the worst month. I, you have to understand that everything's connected. So when the stock market goes down, people have to pay their leverage positions because there's a bunch of degenerates over there, not like in crypto. So what do they got to do? Well, there's only one place that's open 24-7, 365, besides Forex, I know, is crypto.  Now, if we have an issue with real estate falling apart and then people going, wow, you know, God forbid they took a second mortgage against their house to pay for things and they can't pay for that. And then they look at all the crypto going down and stocks going down. So what are they gonna do? They're gonna liquidate so they can cover those and not lose their houses. Kind of what happened in 2008. So I see it happening again. And it's okay. If you set yourself up for it, you're waiting for, you want this to happen. You need it to happen. You'd like it to happen.  Bob Hayes, how's your theta? I haven't checked on the theta pineapple for quite some time. I know I still have it. It's in one of my wallets. I just don't know which one. I have a spreadsheet of all the stuff that I have. I make madding daily. Awesome. Maybe you staking? Yeah. Robert Goss says it's, yeah, young, I think that's a good point. Real estate trouble does spill over other assets. It, yeah. Didn't know wait. Everyone took a big hit. People overextended. You know who really took a big hit?  And there's two people that we listened to on YouTube when we first got into it. And one had the idea of you should never go to somebody and rent their place and then sub-lease it or sub-rent it out on Airbnb. Never do that. You must own properties. The second guy was like, no. What you need to do is just look for everything that's available and that's for rent. You go to that owner and say, look, I'm gonna rent your place but I'm gonna put an Airbnb. I'll pay you your mortgage, your rent every month but I'm gonna try to make more as like an arbitrage and go for Airbnb and Verbo customers. And it worked out great. This guy had like, I wanna say over 500 different properties. And that was awesome until March, 2020 when everybody stopped traveling because of the COVID virus. And then all of a sudden the money that he had kind of dried up and he had to pay the mortgages on 500 plus properties but no one was coming into his locations. And it lasted for a full year. I think he lost a bunch of properties. And it's just one of those things where it's like Warren Buffett says when the tide comes out you see who's swimming naked. And those are very, very dangerous place. And we just went for the fact of we thought, well, it's just better to own assets than to rent and not really have anything, anything. And that's what we did. It works out great. I mean, for us might not be for you, not financial advice. Yes, Mirko says it. This Friday we're very important to stocks and crypto, CPI numbers and next week I have that Fed Reserve. Yeah, there's a lot of development on Cardano. Yes, also cornucopia's game seems to be doing pretty great. Missed the boat on that one. Just did. So Matt, what's up brother? Are you moving on sweetcoin? See, that's why I like sweetcoin because it's free and it's for you to move. Then you get to compete against me. And if you beat me in the monthly steps, cause you can follow anybody you want to on the app. If you beat me, you can come on the show or I'll do a live portfolio review or I'll pay you 50 sweetcoins. That's the top three, not everybody. Robby thinks self-sufficiency to grow as a company. Or at the end of the last leg, I would not put anything in past Alex Vashinsky. There's different FUD and different issues going around with Celsius, but I will tell you, it's got paid today. I don't have a lot of crypto on Celsius because that's just not, I don't think that's smart to leave a bunch of crypto in any one place, even on Voyager or Kraken or whatever exchange you wanna say, or even on my MetaMask wallet. Usually it's one of these things, a ledger. So that's cause I feel just safer with that. So don't put anything more than what you're willing to part with and lose. That's dumb, I can't say that. Opinion on Cosmos. I was dollar-cost averaging Cosmos for quite some time. I think it's not only, well, first of all, you have to remember Luna was built on Cosmos. Don't give it a black eye just because of that, but also crypto.com or Crocoin was built on Cosmos. And a lot of different chains are gonna be built on Cosmos. It's a multi-operational, multi-function chain. And I see it doing very good things. It's just that now in the bear market, now they can grow and do all the great stuff that they wanna do. I'd like to do a deep dive on them, but I don't have time. Juggernaut, why did Voyager pump? Did it pump today or yesterday? Remember, the Voyager loyalty program 2.0 came out. So instead of having three tiers, now you have six tiers and it's accessible to everybody. And I want you to think about this for a second. What exchange do you guys use out there for to trade and buy crypto? Just put it in the comments, I'm just curious. Because think about all the exchanges that you use and some do this and some don't, but do they give you cash back? Do they give you a debit card? Do they pay in kind for the crypto that you keep on there? Have they never been hacked? Do they have competitive fees? That's what Voyager is. And that's why I use them all the time. So there's a reason why I pumped because that loyalty program just came out. Also, I heard Rumblings that, and I had Steve Erlich, the CEO on a month ago, and he said it was gonna come out in a month and be damned if he didn't hit it. And he also said two more things that they're gonna launch in Europe before the end of 2022. And also they're going to be able to trade equities or stocks on Voyager before the end of 2022. So just saying, let me go all the way down. I think these are questions I already answered. Ah, here we go. Binance, Bybit, Ave, Balvin, Celsius. Well, Ave, yeah. Celsius has a great swap function though. I will say that. I wish Voyager had that, it's pretty cool. Bybit, I can't use Bybit, I'm an American. Binance, I can't use Binance. I can't even use Binance US because I'm in Texas. Great question. Jeff says, Rob, how's your portfolio holding up? Not the greatest. However, let me show you something, two things actually. So my portfolio is not the greatest, but what has buoyed me or kept me afloat? I have this second channel, it's called Dan Degen. And I named it that specifically for two reasons. One is because I put it to a vote on Twitter and that's what people unanimously agreed. And the second reason I left it that is to let people know that these are super, super, super risky plays. And there was three that we've done so far that what I'm trying to do is get to those products that haven't even launched yet, but they're super risky. But the thesis is sound. The thesis is I only talk about those projects that have a huge community already built in. What am I talking about? Well, with Genso Kishi, they were already a game. Genso Kishi, G-E-N-S-O-K-I-S-H-I. This is the Degen spreadsheet. There's a link in the description. You can find it right now. And this is the deep dive videos I did. And here's the percentages gained. So when I looked against Genso Kishi, they already had a game that was on PS4, Nintendo Switch, iOS and Android and they were reporting over to Play to Earn. Like, well, this is that no brainer because I already have millions of people built in. That one, the purchase price was 0.015, about a penny and a half. It went up to 0.75, that's different. I think we're looking at 48 cents today. So it's still a 32X. That's doing pretty good. Everdome, they had some metaverse play but they're also backed by MetaHero and they have a pretty huge community as well. And they're all working together with 10 sets, like a wet, if it makes sense. Purchase price was half a penny and now it's two cents, so I got a 4X. These are all like bear market prices. And the last one was Fame MMA which that one was, it was UFC, Fame MMA is not UFC, it's a mixed martial arts organization in parts of Poland and different parts of Europe and they only have influencers fight, which is crazy in my opinion. But influencers get paid in their Fame token, they're doing NFTs, they're doing Play to Earn games, they're doing all this great stuff. You can help with your discounts on Pay Per View. They're using, so like that was, that's like millions of people, that was a no brainer too. And that one did really good.  So yeah, that's how it's been. Those are the ones that have booed me. Again, if you check out DigiLess Dan Degen, just know that they're super duper risky and you probably lose everything, that's all. Adrian, what's your thoughts on Matic for this bear market? I like Matic, we're gonna do a video about Matic. I'm gonna show you, I wanna show everybody how to use the bridge of Matic to go from Ethereum to Matic and back and forth so you don't lose all your crypto. Also how to purchase different things on DEXs and we're doing it to highlight Avogachy. It's a game that I feel honestly is kind of nerdy, but that's not my job as an investor. It's again, big community. There's always four things. How big is the community and how thriving is it? What's the utility? What does it do that's different? And is it just a me too product? What's the team? Where have they been before so I can know where they're going and what's the tokenomics? Am I gonna get dumped on? That's it, very simple. So for Matic for this bear market, you know what it really comes down to? Just how good and how well effectively that merge happens. I don't see good things for the merge because it's just that second part of the three-part process for, if not even called ETH 2.0, I was gonna get confused. ETH, I forgot. But sharding is the next unlock.  It's not what it's gonna do. That's it. Rob is holding the chain worth it. I don't hold it, but that doesn't mean anything. I miss out on a ton of stuff. Can't really tell you. I used to own the chain, just don't anymore. So Dolphin Daddy, we think about the Interday EMA on the daily. Everything we touch at pricing to slow down market. I was watching Ben's channel just a little bit ago on the 200 EMA. And he was talking about the bull support band and how it becomes, it's the support for the bull run, but it's resistance after that. I gotta take a look at it. I don't really, the thing is, if you take a look at the narrative, what is gonna drive, because what does TA show you?  Are they gonna buy? Are they gonna sell? Pretty much, where are they going? You can draw patterns and you can look at candles and all that stuff and it's great. But to me, I just think to myself in the macro environment, what's gonna push a bunch of people to buy or to get into crypto, because it's a risk on asset. Is the economy doing fantastic? Are these rates gonna be stabilized? Are these supply chains gonna be smoothed out? Is the stock markets gonna be that stable moving forward? Because of the economy, I just don't think it's there. I just don't see it. I think the narrative has to change. And there's three big things that actually has to change. One, the war in Ukraine has to have some kind of resolution. Two is we have to see if the Fed's actually going to continue on with this or increase or decrease or pivot. And then the third thing is the supply chain issue. And if we can't get those under control, then it doesn't really matter. And I'm not really concerned about next day, five days. And I'm more like one, three and five years. Let's see. Martin Lawrence is coming to us. I heard that, sounds good. World Mobile Token is coming to America. I'm in talks to bring them on the show. Sounds pretty good. Thanks, Jag, I try. Is VJX worth it? Depends, it depends on what you wanna do, right? If you're trading a lot on Voyager, it's probably worth it. If it's like not your main thing, I mean, probably not. But to me, I always think to myself, and the referrals are pretty good. Like it's like 50 bucks, depending on which tier you're at. It's like 50, 65, 75, 100, and like $125 per referral. So, and that just depends on the tier you're at. Again, if you use Voyager, like I do, also Voyager just upgraded their limit orders. Like I put in a limit order for 20,000 for Bitcoin. Like when I hit 20,000 to buy a full Bitcoin, I put that in and it's stuck. Because before the limit orders are very tight, you can only do like 1,000 up or 1,000 down or sell or buy. So like if Bitcoin's at 30,000 today, I can only say buy at a 29,000 and we only execute that, which kind of sucks, especially when it wicks out at 25K. So now it at least goes to at least 10,000 below. So I like that part. You know what, everybody's, I think I've answered this three times. I'm gonna say, I'm not, no, it's not. I'm not gonna hold it, but you can hold it. I know they're big with China, but I don't trust China. I just don't. Joby, do you think some amazing buying opportunities are coming? Yes, in the market, in the real estate market. Yes, there are. I don't know how soon it is though, but I can tell you from the real estate agents that in this area, there's a little bit more supply than there used to be. I was just walking my dog this morning. I saw two houses for sale, that had been for sale for like over two weeks. So to me, I thought it was interesting. Oh, thanks, man. Super sticker. This is a great question. Lotus Ferry. How come Voyager is paying rewards on crypto while Celsius and BlockFi can't do the SEC? So I had Steve Verlich, CEO of Voyager, and Alex Machinsky, the CEO of Celsius on at different times, obviously. And I asked Steve, I said, why are you able to give yield? And he's like BlockFi and Celsius are stopping that for Americans. Celsius hasn't stopped it, stopped it. But they've reduced it and then of course, accredited investors and things like that. That was the big thing, accredited investors, excuse me. In America, you have to be a accredited investor. Either you make so many millions of dollars in a business or you make over $200,000 per year, some combination of the two. If you're not a accredited investor, you will, past April 15th, you will not be able to accrue any interest on your crypto unless you had put crypto into your account before April 15th of this year. So everything that you put in your account on April 15th before the United States, you are gaining yield. After April 15th, if you are not an accredited investor, you will still gain that yield and the stuff before, but you can't add any more in. It's very, I hope to make sense. So the question then Celsius and BlockFi, so what's going on, especially with BlockFi? And I asked Steve that and he goes, I don't know what they're doing, but all of them do loans. He said there's an issue with the loans, with how they're doing it or how the verbiage, not that that's the thing with Celsius. He just said a blanket statement. I'm not gonna say this is the exact reason. And also remember that Voyager is a brokerage. It's not an exchange. So all they do is they're like the hotels.com, a crypto. So you want Bitcoin at $29,876? Okay, let's look at all these exchanges. This is the best price. There you go.  We're gonna take a little bit of money and that's what brokers do. And of course they don't do loans, which I'm glad they don't because I think that's a reason. Something is with that. I'm not for sure. So there's your answer from what I could get from both of them. Great. I tried to... Marquis Searcy, the OG of crypto was here.  Are you still holding Aida? Oh yeah. Well, I have to. I gotta hold Aida in my stake pools. I got two of them. Speaking of which, I haven't talked about that in a while. If you're looking to stake your Aida, you don't want to put it on exchange, help to secure the network, stake with DNews. There's a link in the description. I do a video, I explain exactly what there's been proof of work, proof of stake, how much you're actually gonna yield, how it actually works and everything in between. There's a video and I show you exactly how to stake it. That's it. Yeah. Ricochet-Rabbit says, I dropped my E holdings 80% over the course of two months and I'm grateful no matter what happens. Never know. Like I said, Ethereum can go to $10,000 tomorrow. Who knows? Do you think Aida is a better Biden soul? I will tell you this, the community is much better. Have you ever been in the Aida community? Oh, they love Aida. Talk about all the time. And the longer I'm in the space, the more I appreciate the tortoise and the hare analogy. That's all I'll say.  Just kidding. No, I mean, yeah. I think that's it. Oh man, we went way over. So look, let me make sure I didn't miss anything. I'm sure I did, so many. Eduardo, thoughts on the crypto regulation bill that will happen tomorrow with Lummis and Sailor. See what exactly what it says? Not for sure. But again, I think it's a step in the right direction.  That's just what it is. I know people think we don't need it, but we do. And before you say, what has regulation ever done? As far as like the positivity, government can't do squat. Did okay with OSHA, Occupational Safety and Health Act.  Just saying, all you have the corporations are gonna save us, let's be honest. And you know, Act 230 allowed the internet to flourish because the people who own the websites didn't wanna get sued for slander or libel for people that actually wrote different things on their websites as far as blog posts and things like that and be responsible. So it's not like it's all bad. Works out okay. Anyhow, that's it. So look, thanks so much for stopping by. I do appreciate the time. Always fun times, right? If you liked today's video, give it a thumbs up, consider subscribing and that's it for today. So thanks so much for being here. I appreciate it and I'll see you on the next one. Adios.


During the global financial crisis the crisis was severe but it took about two years from the time where you had the unraveling of the US housing market and mortgages until we got the collapse of Lehman and then things got much worse. This time around we've had economic activity like consumption, residential investment, retail sales, and production and capital spending collapsing sharply in a matter of few weeks of a month. During the global financial crisis it took almost two years until the stock market was down 30%. Now it's taken less than a month. And even if you compare these with the Great Depression, the Great Depression started in 1929 with a stock market crash but the depth of the Great Depression started only in 1932-33. So initially it was a stock market crash and then the mistaken response to it led it to become the Great Depression. So this is just something we've not really seen before. It's a bit like as if an asteroid ate the earth and not just one economy or the other. Sometimes we have a recession in the US but not in Asia or one in China but not in Europe. Right now pretty much every region in the world has gone into a free fall of economic activity. So as unprecedented in the speed, in the depth and into the global reach of it. So this is something much more severe than we've seen before. We don't know how severe this recession is going to be but it's going to be severe. Global economic activity will contract in the first quarter, in the second quarter and in my view highly likely it's going to contract at least even in the third quarter. We'll be lucky if it's just a three-quarter severe recession, it could be longer than that. And maybe by the fourth quarter of this year we're going to see some beginning of economic activity recovery in advanced economies and emerging markets but that's the best scenario. I think that a recession of at least three quarters around the world has to be your baseline.


The Universal Declaration of Human Rights was agreed at a time when the world was rising from the ashes of war to set out a path towards a new and brighter future. But today our rules-based world order is being challenged. We live in times marked by increased division and polarization. This anniversary provides an excellent opportunity for us to reconfirm our commitment to this declaration and to the UN Charter's provisions to cooperate to promote respect for human rights. Human rights are universally applicable everywhere and at all times. On behalf of Sweden, I would like to reconfirm these commitments and make the following pledges. We will continue to support Ukraine and its efforts to uphold human rights. Our recently adopted strategy for reconstruction and reform cooperation with Ukraine has a strong focus on human rights, democracy, the rule of law and gender equality, values that guide Sweden and the European Union. In parallel, holding Russia accountable for its violations of international law remains a top priority. We will continue to strengthen initiatives to combat racism in all its forms and to promote freedom of expression and freedom of religion or belief. This includes dialogue with faith communities in Sweden and follow-up on the recent visit of the UN Special Rapporteur on freedom of religion or belief to Sweden. With a view to strengthening human rights in Sweden, we will step up our efforts to combat sexual, gender-based and honor-based violence and present a new action plan to that effect for the coming three years. We will also work hard to implement our newly adopted 10-year national action plan for sexual and reproductive health and rights. Human rights can never be taken for granted. Sweden will continue to raise its voice whenever human rights are challenged and to support the work and independent mandate of the High Commissioner for Human Rights. The best way to commemorate the universal declaration of human rights today is by redoubling our efforts to implement it. Thank you so much.


When was the last time that you thought about that teacher who had a huge influence on your life? I want you to take a moment to think, well we hear from Vasu, one of the amazing partners we work with in India. Mrs. Rekha, you're an inspiration to me because you never gave up on the situations on the students and on the environment, the kind of environment that you were working in you still never gave up. You travel almost 12 kilometres a day by foot and go to a very small village in Uttarakhand and still do what you do, so thank you for that. Around the world, too many teachers are undervalued, demotivated and leaving the profession. I decided I wanted to be a teacher age five, but I have constantly been told, why would you want to do that? You can do so much more and this infuriates me. You know and the evidence shows that teachers are key to improving society and the education for the future generations. We have a global learning crisis where more children now than ever before are in school but they're not learning and this is costing us 129 billion a year and undermining our ability to meet the sustainable development goals. My social enterprise LRTT, limited resource teacher training, is tackling this problem by building a global teacher movement and bringing teachers together to support each other to connect, to inspire and motivate each other. By harnessing the power of teachers around the world, teachers are becoming the solution to education and not seen as a problem. To date we have done this without any external funding. The teachers we recruit as fellows, primarily from the UK, the US and hopefully more from Australia and New Zealand, self fund to take part in this programme and learn from the teachers they travel to work with. This means that this year we are recruiting 650 fellows to support 3000 teachers across 10 countries in the world. This innovative model for teacher training, we believe is very unique but we can't do it alone and we really need the partnerships and the people that we work with. And that's why I'm so excited to be returning back to New Zealand, to be settling in Christchurch and to be working and learning from this amazing community and the people in this room. I have been overwhelmed by the support I have already received and everything I have learnt already and I can't wait to continue this work. So I'd love to speak to anyone interested in education in New Zealand, in general or globally, especially with people who would like to work in partnership to support teacher training and to support the future generation. And I just want to finish by sharing the stories of some of the amazing teachers I've had the privilege of working with but who don't often get the same opportunity that I have had to share their stories. What I've learnt, what I'm taking home and what I'm going to implement is how I will be able to attract my students attention before I deliver what I have for them. I've really enjoyed every bit of it. I've learnt a lot from this place, especially with the phonics. How to blend the sounds of the letters, to form a word, teaching them the sounds. I've learnt a lot. I've learnt a lot. It's been so fun. I'm happy. I'm excited to hear from other parts of the world what they do to train their children, to bring them up very nice. It's fantastic. So thank you very much and I look forward to speaking with you all.


We have people from a lot of nationalities, from Ireland, New Zealand, England, Denmark of course, India, Pakistan, Bangladesh and Afghanistan. So all these people which are here, they are from almost different nationalities. International community basically consists of young people who come here for education and also sometimes jobs. When I came to Denmark I had a year where I didn't play cricket but then suddenly I thought maybe I should just search for it. It's a team sport and you know you get a chance to socialise with people and you know talk about your passion about cricket. So this is what I like most about it, that it is a social game and you have different disciplines you can work on, show your efficiencies.


IGX stands for Integrated Training Exercise, and it's a service level exercise, the purpose of which is to train a MAGTAP, Marine Air Ground Task Force, mission-essential tasks of offensive and defensive operations, and if you can do those two things well, you can do any special mission well. This is a chance for some Marines who have never been in such a kinetic environment like this before to get straight into it and start working and pounding that craft to become experts at it. We had artillery with us, which was very critical. We did work with second tanks. They're a huge mechanized force for us to be able to utilize for a support-by-fire asset, which allows our foot mobile troops to be able to close in and actually seize an objective and stand atop that ground, and AAVs being able to maneuver and get their reps in also. They were helping mobilizing and transport of all units on the ground. ITX is more of a platform for us to basically identify our discrepancies in the friction point and allow us to further better ourselves going forward and to be better prepared in future conflicts. So what we learned during this training is how to kind of think of new factors as we go fight near peer-to-peer adversaries, different threats that we've never faced in the past, and just having that different type of enemy threat.


Hi, thank you for coming to my presentation. Don't just consume, participate. Talk about operators in the community. I'll be talking today about how as a community, we should reevaluate the relationship between the people who build OpenStack and the people who operate OpenStack. And this is important because how we build and think about servers is constantly evolving. Well, how do I know? I'm Jay, I'm a sysadmin. I've configured systems, monitored them, woke up at 3 a.m. to fix them and solve their problems, but actually, I'm not. I'm not a sysadmin anymore. That's what I used to be. I'm a Linux engineer now. So what really changed? Instead of working on a server level, you kind of start working on an environment level. You start thinking about whole systems and how they interact. But the basics are staying the same. You're deploying and managing infrastructure to help the people who count on you get things done. But even this is wrong. I'm not really a Linux engineer. I'm a DevOps engineer. So this is more like it. Who configures systems by hand anymore? I have my little robot chef who configures them all for me. But really, I'm doing the same thing. I'm providing infrastructure to people who need it. And only the tools I'm using have changed through this transition. But even this, I'm not really a DevOps engineer anymore. I'm sorry, I'm just, I keep getting, I'm a developer. That's it. So really, it's a little over the top, clearly. But the point is that we've all held different titles or we may all hold different titles and we have opinions about what that means about what we're supposed to do, but they're just words. We shouldn't let our titles constrain us because despite what I've been called throughout my career, whatever title was placed on me, I built infrastructure. I cared about customer problems, be they internal or external. And I wanted to bring them infrastructure to help them solve these problems. But actually, I messed up again. I recently got manager. So basically, now I just give presentations at the OpenStack Summit instead of, but that's even not true because as a manager, even though my tools have changed from technological ones to kind of personnel and organizational ones, I'm still doing everything within my power to improve the infrastructure for the internal and external customers even if the ways I do it have changed again. So what does this really mean? It means that labels don't matter. We all, if you're in this room, you at least care about cloud infrastructure as a baseline. It's actually likely that at this point, if you're in this room, you're an expert in some portion of cloud infrastructure even if you don't realize it yet. Because we all consume cloud infrastructure in some way. We all operate or build cloud infrastructure and most of us do both. It shouldn't matter that our tools are different and that our areas of focus or our titles are different. And I'll give a little bit of a personal story here. About a year and a half ago, I moved to another team in Rackspace which gave me the opportunity to work on OpenStack Ironic as part of a new project. At the time, I would have preached to everyone that I was a DevOps engineer, that I didn't write code, I didn't know how, I didn't want to, you know, that's not my job, that's what the other people do. But over time, I found out as I worked with my local coworkers and my upstream coworkers that really it's just a tooling difference and that I can use Python as my tool in the form of a software project to do a lot of the same things that I was doing with operator tools before. And we're all focused on the same thing. But if you're an operator in this room and like that, I've been there and I still am there, you don't have a lot of time. So the question at the top of almost anyone's mind when they saw the title of this has to be what's in it for you? So it may seem like you don't have the time that it's not something that's in scope in your job but I view it as an investment. Getting involved in the community is investment in yourself, in your career path, in expanding your horizons and developing professional contacts. But it's also an investment in your environment. And that's because there's an infrastructure revolution that's ongoing right now. OpenStack is moving faster than ever. New ideas and tools about infrastructure are emerging quickly. And that's proven because more brain power than ever is being put into how to run infrastructure. It shows an open stack. For the Kilo integrated release, over 1,500 different individuals had contributions. And OpenStack is moving that fast because the industry is moving fast. We saw a demo in the keynote of Magnum which spun up a cluster of containers at the push of a button on a machine that was booted with Ironic. Something that would have been impossible because Magnum didn't exist 10 years ago. Six months ago, it would have been impossible last summit and even 12 months before that, Ironic maybe wasn't mature enough to have a good, easily consumable product. But this revolution is being enabled by software because software allows us to develop and iterate quickly. And a lot of us have been taking kind of six month or larger bites of that. And I don't necessarily think that we have to change that on a code side as much as we do on a knowledge side. When you're kind of at the end of the fire hose of the release, there's a lot of information that you're trying to consume in a short period of time to upgrade your environment safely. But realistically, you have to implement continuous learning. And then later you can implement continuous integration, continuous deployment if that's what you choose. But the continuous learning is very important because being at the end of the fire hose, I can barely consume what's changing in Ironic and I work in it every day as my primary job. If you're trying to consume it all via a release notes or something at the end of the cycle, you're gonna be disappointed and there's gonna be things that are missed. Another big reason you should participate is to advocate for your use case in your environment. I've seen many different environments of OpenSec installations that use different parts, mix and match them in different ways, use maybe obscure features that other people maybe even didn't know exist. But decisions are made all the time on a mailing list or on IRC or in design summits about which of those things should stay, which should go, how they should evolve. And if you're not in those conversations, something that you depend on may get dropped or a feature that you may be looking forward to might not happen. A good example of this is actually in the Ironic Python agent, which is the upstream project I primarily run on. I work on. We use systemDNspawn containers to run Ironic Python agent in the RAM disk, but we thought that that was a fine use case. They allow you to express capabilities so we can say, allow us to do crazy things to provision hardware, but then we go to upgrade the CoreOS image and we find that systemDNspawn has broken our use case because upstream made the assumption that no one would ever do certain things in a container and no one was in that community to stop and speak up for our use case. And another good example of participation is how we solved it in the end was by participating in the community, getting on the mailing list, going back and forth and actually end up spent today writing a patch to fix it. This sort of stuff can and does happen in OpenStack. Our APIs are versioned, but there's often a time when there'll be a mailing list message or an IRC message about a minor feature to get removed and if you aren't reading that, you're gonna miss it. So that's a couple of reasons. There are some others that are kind of sprinkled in throughout, but I wanna talk about how you can participate. And there are lots of different ways to participate. Include you can do code contributions in review, that's kind of the obvious one, that's what a lot of people think of when they think you're contributing. The spec writing in review, writing good bug reports, supporting other operators, troubleshooting test failures, or even building OpenStack project infrastructure. But we're gonna dig down into each one of these items and talk about how operators bring a special knowledge to the table that can make it useful in doing this. So if you want to contribute actual code though, that's fine, that's great too. I would suggest looking for bugs tagged low hanging fruit if you haven't contributed before and you wanna get a start. And you can ask the IRC for good things to work on or maybe if you're not confident in your abilities yet get someone to help mentor you through it. And if you don't know Python, that's perfectly fine. OpenStack has many repositories in many languages. There are entire projects written in Bash, there are entire projects dedicated to documentation and install automation. And even as we're gonna talk about later, there's an entire set of repositories that people contribute code to that actually build the infrastructure that the developers of OpenStack use every day. But if you don't wanna actually contribute code, you can review code. The big piece here is don't be afraid of reviewing code. I've talked to many operators, many people who claim that they aren't qualified to review code. I don't know Python well enough or that was already reviewed by someone more senior. But as we established earlier at the beginning, you're an expert on some aspect of cloud infrastructure. Already, if you're in this room, you're running it in production, you're an expert on it. Use that expertise when you're reviewing the code. Oftentimes the people who build OpenStack every day don't also have the opportunity to run clouds especially at scale. And so that insight that you gain can be helpful when you're reviewing code. Coder view can help the reviewer as well. You could see changes in parts of the software that might impact something you particularly care about or impact the scaling issue you've encountered. And generally speaking, being more familiar with how the code is organized in OpenStack can help you when you're having that 3 a.m. call because your cluster is down and you have to fix something.  But again, the biggest thing is to be brave though. Read the code, put your best effort, vote on it. If you look at that and you say, I don't really feel like I gave that a great review but you were able to see it, you should put your plus one or your minus one on it with a comment and say, I'm not sure I understand all of this but I looked at it for X, Y and Z and I didn't find any issues. And that extra plus one as a core on some projects in OpenStack, I find it helpful to know that an operator has looked at this and says it's nice.  You get to, because titles don't matter anyway. But you can also review specs. Now what is a spec? A spec is used in many OpenStack projects. Some of them use Blueprints instead but the same concepts apply as a form of requesting and also planning new features. And they're kind of varying levels of detail from project to project. But many specifications have a big impact on operators. So you should review them. Things that you can look for when you're reviewing specs as an operator include that if it's a new feature that you understand how you'd use it. That you actually think through how would I implement this in my cloud and make sure that the spec reflects that reasonably because oftentimes that gets missed. Look at potential performance bottlenecks. If you know there's a performance bottleneck in your cloud and that spec is going to touch that area of code, make sure it's not gonna make it worse or even better find a way that it can improve it. Things like does the client library need updating as well because there's nothing more frustrating than having your client tools broken after a server upgrade. And finally, is this internally consistent? Does this spec solve its own problem statement? Note that nowhere in there do you have to have knowledge of software architecture to make an impact. You don't have to have written a certain number of line of code to get in. There's no gate, it's open. The review process is open for the specs just like it is for the code. And there are even some projects. I'll give ironic as an example, I think Cender has a lot of the same problems where we have hardware specific drivers that are being written by maybe people at a hardware company and don't get anyone looking at them until they're actually used. So if you were using a piece of hardware and a driver is being written for it and the spec is up, please take the time and do a real good look at it because as we all know, what the hardware says it does is not always what the hardware does. How the protocol says it's supposed to work is not always how it works in the real world. And it can be helpful to use our experience in the real world to direct people away from that. So what about good bug reports? And there's a reason I put good here because there's a big difference between saying something is broken and equipping someone to fix the problem. So what makes a good bug report? Detailed reproduction instructions which must include how to set up the environment to reproduce the issue, which means your configs need to be there. Your full version and environment information need to be there, including what distribution you're using, the libraries installed, what pit freeze says your dependencies are if you're installing via that way. Literally anything that could be relevant. Sorting through the information in the bug later is a little bit easier than not having it to solve your problem in the first place. But if you want to go above and beyond, instead of having to provide that information, you can go boot DevStack. You can boot DevStack on the stable release that you're running if you are and reproduce it there so that your environment doesn't matter, or you can even try to reproduce it on master. Additionally, you can find the change that broke you. We're usually familiar enough, especially if you've been looking at the code to understand what pieces of the software could be impacting, and going in there and looking at recent changes or change log can sometimes help you pinpoint that. And having this information there means that your bug is more likely to get serviced because someone's gonna see it, the information's gonna be there for them to solve the problem. Another important way you can help is by supporting other operators. And yes, I do mean technical support, help desks sort of things. There are lots of questions about how to operate OpenStack. In fact, documentation is maybe one of those places that we don't do so well in that actually operators can contribute because documentation's code as well. But you can answer questions on IRC. And IRC's actually a good point that I'm gonna hit on a few times. This is the water core of the OpenStack in almost all OpenStack communities is what happens in IRC. You should join the channel. You should be conversational. Even if you never intend on contributing otherwise to OpenStack, being active in the IRC channel is a form of participation just by itself. You can also look at ask.openstack.org or use your operator mailing list and help people. And why?  But we all know that's not the real reason we should do this. The real reason we should do this is we've all been the person asking the question. We've all been there trying to do a new thing and not being sure how to do it and getting help from someone. And part of being in an open source community is taking on the responsibility of passing on that knowledge to others. And when we fail to pass it on in documentation, sometimes we have to pass it on in one-on-one help. So another way is by troubleshooting CI or test failures on patches that you care about. And this is actually a process that is gonna mimic what us as operators have done many times in the past in troubleshooting our own production environment. And basically here's how it works. Every patch that's submitted to OpenStack must pass a battery of tests. Some of them from just level of unit test all the way up to spinning up a mini cloud inside DevStack and functionally testing against it. But these tests fail. They fail for a variety of reasons other than the code being broken. And sometimes in the worst case, even the test on all changes in a project can fail and really clog up the pipeline. This is sort of the emergency nature of how these have to be fixed. Because every day that that's clogged or every hour it's clogged is an hour things aren't getting merged. And in OpenStack that can sometimes be a problem. So what do you do to troubleshoot? You read the logs, you look at what code or maybe dependencies changed in the environment. But the reality is you already know how to troubleshoot these problems. You have a production OpenStack cloud running if you're an operator and you can go in and apply the same knowledge you use to operate that cloud of troubleshooting these test failures. The logs are actually very well documented as well. And this is incredibly, incredibly high impact. Because through the work of one person on clogging that pipeline, you're unleashing dozens of developers to be able to get their code in again. So that's a good effort to value ratio for your input. And as a note here, troubleshooting doesn't necessarily mean you have to fix it. Fixing it can be a rabbit hole sometimes, I understand that. But sometimes just by looking at it and by pinpointing exactly what broke, you can accelerate that process. Because if you determined that every test that was running with version A of a library is passing but version B is failing, just pointing that out as often enough to enable very busy people in infra who fix these sort of things to fix them. Just research, comment on the bug or on the code review or even on IRC, and then someone can maybe help turn your diagnosis into a fix. Another kind of finally, a way that you can contribute is actually in the project infrastructure itself. OpenStack is a huge user of clouds as well as a builder of it. There are lots of tools that are used by OpenStack developers that are managed kind of in-house by an infrastructure group in OpenStack, the infrastructure project. Tools like Garrett, git.openstack.org, Storyboard, the various IRC bots and services that we use. The entire integrated gate that I was talking about before, Etherpad, the Wiki, the website hosting for the docs. All of this stuff that we consume as users and as developers of OpenStack are built by essentially people who are doing DevOps using Puppet. And these are all technologies you're familiar with. There's an ELK cluster with Elasticsearch, LogSash, and Kibana that I'm sure many of us have in our environments as well. And all this is built using Puppet. And what's really crazy about this is I've never seen a production environment documented as well as the open source production environment for OpenStack is. You can actually go to ci.openstack.org and see where everything is, see where the pieces are, try to fix them. And I'm sure if you have willingness and you don't know which direction to point it, if you talk to anyone in Pound OpenStack Infra, they would be happy to mentor you and point you in a direction of help because more hands are always useful. So now that we've talked about how you can help, let's give a few tips. If you're a first-time contributor and guest presenting with me for this will be Pixie Boots, the ironic mascot. And so Pixie Boots says we're gonna see if we can drum up some help for you. So first you have to get your bearings. Researching first is okay. Just join the IRC channels for any project you might be interested in. Read the mailing list or the archives if you haven't subscribed to the list. Look over the approved specifications, recently landed code, and give yourself an idea of how that community works. The different communities inside OpenStack behave differently and one of them may fit your taste more than another. You can also attend the OpenStack Summit. In fact, by being here in this session, by being here at the summit, you're already participating and doing that at at least a minimum. So you can do this research and then you can maybe decide what project should I contribute to. Now myself and Pixie Boots, we can't bear to build ironic without you. So it's really important to pick a project that's gonna be accepting and wanting to. I would advise, if you've never contributed to OpenStack before, maybe avoid some of the larger projects like Nova or Neutron, and Nova and Neutron is great software. It's excellent, it runs in my cloud. It's just a higher difficulty level. And so why make it more difficult and burden yourself with the difficulty level of trying to put into one of these bigger projects when they're smaller projects that your contributions can have a larger impact on. They're entire portions of OpenStack that are libraries we depend on that are managed by maybe one or two people. And by adding your help there, even a little bit of time can often make a big difference. The other big piece of advice is choose a project you care about and that runs in your production environment. Realistically, you're gonna bring the most value if you have experience running a project in production and if it's something you care about. Conflict is unbearable. So don't forget the human element. Treat people excellently. Your peers in the community are your coworkers. We're all working through the same goal. We all wanna make great infrastructure even if we have different customers or different approaches to it. So what does this mean? This means that if someone's short with you on IRC or a mailing list, remember it comes from a person and that a lot is lost in the translation from real life into text. Remember that if you do try to contribute for the first time and someone puts a minus one or maybe even a minus two on the patch, that that's not something against you personally but it's their way of pulling the rope and making OpenStack better and maybe in the process making you better by showing you something that you might can do better next time you contribute a patch or you can do better in this patch before it lands. And it's also important to open your mind to new ideas. We all have different ideas about how to run a production environment. You may choose to run stable branches. I may choose to deploy master often but that doesn't mean that one of us is right and one of us is wrong. It means that we should have our mind open to new ideas and determine why people are doing things the way they are in order to make it better for everyone.  You are likely your harshest critic. I know that if I had come to this talk two years ago and I was sitting in the audience, I would think, this is nice that there are operators around me who could contribute to OpenStack but I'm talking to you. I'm talking to every single person in this room. Like I established at the beginning, you're an expert in cloud infrastructure. If you're here to discover, you will be very, very soon.  You have to grow the areas of expertise you have. And there's really nothing to lose but a little bit of your time and after all, bravery is very metal. So in conclusion, we need to embrace our common goal of providing high quality infrastructure to the people who count on us. Focus more on what we have in common rather than the tools we use or the titles we hold. Understand that contributions are a lot more than code. Contributions can be an encouraging word in IRC for someone who's dealing with a hard problem. It can be a good bug report. It can be documentation. It can even be evangelizing OpenStack to a fellow operator who maybe is wondering how to adopt a cloud. And OpenStack, we're all better off if you're bringing your perspective to the table as an operator. That's what's really important. So I think OpenStack's better when we're all builders and operators. And I think we've made great strides toward that but we need to keep going. And also, there's no such thing as enough ironic puns. So thank you very much. Before I ask for questions, I will point out that Rackspace is hiring. Expo Hallbooth P11 or bit.ly slash rackertalent with a capital R and a capital T. Or you can come up here to the stage and chat with me afterwards and I can talk to you and tell you how great of a place Rackspace is to work. But at this time, I'll take questions. If you do have a question, please come to the microphone. Wonderful, thanks everyone. As a manager now, how do you keep up with all the emails from the DevOps distribution list and keep up with what's going on in the community? Note how much I focused on IRC and didn't focus on the mailing list. I have found in my personal experience, especially with OpenStack Ironic, that real work happens in IRC and at the design summits and mailing list posts tend to be more on a philosophical or a higher level about project governance, about what our approaches to problems should be. And honestly, as someone who has a product, has an infrastructure to provide to customers, you know that's not the sort of thing I have time for. I'm very glad that Rackspace hires people to have those discussions and to think about those things. But for me, I try to stay in the trenches and keeping up on what's going on and keeping an eye on the code and the specs and being really active in IRC and at the conferences, which oftentimes is where more of the work happens. Thank you, I got another one. With the documentation, Rackspace probably has some documentation that they wanna keep internally to maybe how they customize some features. How do you separate then documentation upstream and documentation internally and direct maybe tenants of the cloud to both sites? Our tenants get confused very easily and you send them to the upstream documentation and they just get even more lost. That's actually interesting because when I mentioned documentation here, I was almost thinking more along the lines of developer and operator documentation rather than user documentation. With developer and operator documentation, you don't really have that much of a problem. It's a lot more declarative of here's config where if you wanna build an ironic cloud integrated with Nova, here's a wiki page on the 10 config values you should set and where the caveats are and things like that. For user documentation, I think that's a very hard problem. But to be frank, it's a very hard problem when you're running a product which has patches and a downstream and an upstream as well. So I don't know how that's handled at Rackspace with user documentation, but I know we do handle it because I know we have an internal set and an external set of docs. When I say that, I'm mainly thinking about operator documentation or developer documentation. The operator documentation especially, I think is really lacking in a lot of places whereas the user documentation maybe gets more love because it's seen more often. Thanks. Yeah, if you wanna come up and say hi to me afterward, I would gladly introduce you to someone who knows how to handle it, who knows how that works. You mentioned IRC, so I feel compelled to ask as a very prolific IRC user, I'm kind of curious, how do you manage your IRC space if you're that reliant upon it? So like myself, I'm probably a member of like probably at least 100 channels at a time.  And do you have your dot files published anywhere? My dot files are up there in a private repo, but I could maybe finagle some things out of it. I'm always looking for like better tweaks for my configuration, so you know. So I'll give you my answer, and then I might redirect to I think Jim maybe has a better setup for this sort of stuff than I do in his bouncer, but for me, I found, I try to cap the number of channels I'm in at like 40 or 50. Once you get over that amount, I'm honestly a little bit shiny thing over here, shiny thing over here, so if I have that many channels, I find that I spend all day reading IRC and not all day doing anything. So for me personally, I just run WeChat inside of a team up session on a Rackspace cloud server. So I don't wanna apply a lot of technology to it. I'm also a speed reader, which makes it a little bit easier. I know that Jim has mentioned once that he uses ZNC and has it capture any notifications to him and put it in a separate buffer, which can be useful. But realistically, I just tried to be opportunistic with it. If I have an extra five minutes or if I have a distract time, I go look and I read some scroll back in IRC and try to determine what's going on and you can often skim through and determine if a conversation is something you care about or not in a big hurry. But I think what you'll find is if you're active in OpenStack IRC channels often enough, people will start pointing questions that you're capable of answering and things at you so that you can kind of shift from maybe having more actively monitor the channel to being slightly more passive about it. Right, fair enough, thanks. We chat, WEE chat, it's basically IRSSI plus modern. A little bit, but it's still text because we like good interfaces. Question, excuse my croaky throat. I'm kind of at a different stage of devolution to code, assist, objects, et cetera. I'm in business development and sales, so I'm probably the filter of the earth. How can I contribute? I'm not hands-on, I'm not seeing the bugs, but I'm hearing what the customers want from an operator. That's a great question and a great word. Devolution's a good word, even though it maybe means different things, but the point still remains, you may do sales and biz dev, but you care about quality infrastructure. You have to have that quality infrastructure to sell to customers for it to exist. So I would say that you maybe even have an interesting perspective as almost a user or as a representative of many users in OpenStack. And so you can still take that knowledge and apply it in ways close to this and maybe discard some of the more technical pieces if you're not technical and you can't do that, that's fine, but there's still plenty of places to help. You can still be in the primary IRC channel and answer user questions because they come up a lot. You can look and become very familiar with the client libraries and how to use them and then help others with those or maybe even work on the user docs as well. There's plenty of ways to be involved and honestly by being here, you are being involved by selling OpenStack and by spreading the open source commercial word to the masses, you're already somewhat participating and I would actually be very interested to see if you tried to participate, if maybe you could identify better places than I could for someone like you to enter into the process because I maybe don't have great answers for you as a salesperson, but I'm saying that if you go into IRC and you say I'm not very technical but I'm willing to help, someone's gonna find a way for you to do it cause we always need more hands and I've even seen in the past people who maybe when they started out less technical, they start getting involved, they can become really important in the community for helping things happen. Thanks. No problem. So I'd like to thank you all for coming and participating if you have any further questions, feel free to come and see me up front afterward. Thank you all very much.