WEBVTT 00:00:32.329 --> 00:00:34.170 Hey, Chris, how's it going? Good. How you doing, 00:00:34.229 --> 00:00:39.250 John? I'm making it. Yes. I'm pretty tired. Like, 00:00:39.289 --> 00:00:43.149 I'm not you tired. I didn't put down flooring 00:00:43.149 --> 00:00:48.229 today or yesterday. Well, just today so far. 00:00:48.250 --> 00:00:52.950 I'll finish up tomorrow. Wow. Because I had to 00:00:52.950 --> 00:00:55.289 stop a couple of times. You're a beast, dude. 00:00:56.700 --> 00:01:00.420 Take Tori to her driving test or class or whatever 00:01:00.420 --> 00:01:03.060 it is. How'd that go? Because she's got to do, 00:01:03.159 --> 00:01:05.420 I think, five of these. Okay. Part of what we 00:01:05.420 --> 00:01:10.000 paid for. So dropped her off at two, went back 00:01:10.000 --> 00:01:14.299 and got her at four. In between, did a little 00:01:14.299 --> 00:01:16.819 bit of reading for what we're going to discuss 00:01:16.819 --> 00:01:18.340 tonight just to make sure I have it straight 00:01:18.340 --> 00:01:20.340 in my head. And then, of course, she's like, 00:01:20.400 --> 00:01:23.159 can we go to the mall on the way home? Sure. 00:01:24.859 --> 00:01:29.219 So. Maybe I can complete the last two partial 00:01:29.219 --> 00:01:32.500 rows tonight and then keep going and sometime 00:01:32.500 --> 00:01:35.859 tomorrow have it done. That's just impressive. 00:01:36.599 --> 00:01:38.920 Well, it's the best time to do it. The boy's 00:01:38.920 --> 00:01:42.560 out of the country, so his bedroom is all slammed 00:01:42.560 --> 00:01:45.980 in the living room right now. And his floor is 00:01:45.980 --> 00:01:48.719 torn up. Yes, but it's starting to come together. 00:01:48.780 --> 00:01:52.659 It looks nice. Good. I mean, I would expect nothing 00:01:52.659 --> 00:01:56.400 else. Anyway. If you're going to do something, 00:01:56.459 --> 00:02:00.159 you usually do it pretty stellar. Well, I'm just 00:02:00.159 --> 00:02:03.280 thankful that I grew up with my dad being a carpenter, 00:02:03.340 --> 00:02:05.780 so I feel comfortable with tools. There you go. 00:02:06.400 --> 00:02:09.219 I will tell you, coming from the other side of 00:02:09.219 --> 00:02:11.819 it, the uncomfortable with tools, like having 00:02:11.819 --> 00:02:15.520 to figure all that out by yourself, it's pretty 00:02:15.520 --> 00:02:18.000 rough. Yeah. And you just spend the whole time 00:02:18.000 --> 00:02:22.659 going, I'm making this up, man. I hope it works. 00:02:22.860 --> 00:02:25.580 Well, I mean, the... The fun part is you go, 00:02:25.699 --> 00:02:27.699 you know, I can save us some money if you let 00:02:27.699 --> 00:02:30.439 me go buy these tools. Yes. And that's how you 00:02:30.439 --> 00:02:32.560 grow your tool collection. Yeah, I've done that 00:02:32.560 --> 00:02:35.180 a couple times without telling her. I was like, 00:02:35.240 --> 00:02:37.400 well, you wanted that done, and I needed these 00:02:37.400 --> 00:02:39.520 tools to get it done. And it made it cheaper. 00:02:40.039 --> 00:02:42.539 I mean, it will for the next time probably, but 00:02:42.539 --> 00:02:44.659 it didn't make it cheaper this time. Well, yeah, 00:02:44.719 --> 00:02:46.879 I guess it depends on the project. And the tool. 00:02:47.439 --> 00:02:50.520 Well. I have a tendency to. Did you buy team 00:02:50.520 --> 00:02:54.259 red or team yellow? Yellow. All right. I keep 00:02:54.259 --> 00:02:56.039 it a little more affordable. I go team green. 00:02:56.340 --> 00:02:59.039 Okay. So, but they work. They get the job done. 00:02:59.580 --> 00:03:02.620 Teal green or the other green? Ryobi. Okay, yeah. 00:03:02.800 --> 00:03:04.259 Whichever green you want to call that. Yeah, 00:03:04.259 --> 00:03:06.740 I mean, I think it's the teal green. The other 00:03:06.740 --> 00:03:10.560 one is. We'll go with it. Oh, the other is. No, 00:03:10.800 --> 00:03:14.139 they're the blue. Yeah, you're talking. I've 00:03:14.139 --> 00:03:18.020 got their minor saw. Hitachi. Hitachi, thank 00:03:18.020 --> 00:03:20.159 you. I think now they're Matabo, I think is who 00:03:20.159 --> 00:03:22.330 bought them. Really? Yeah. All these companies 00:03:22.330 --> 00:03:25.490 all get bought out all the time. Yeah. No, I, 00:03:25.569 --> 00:03:30.909 I have a lot of stuff from asking a certain friend 00:03:30.909 --> 00:03:35.770 who has all of the yellow tools. Yeah. Like all 00:03:35.770 --> 00:03:40.310 of them. Um, so with that direction, I have another 00:03:40.310 --> 00:03:43.129 friend who's a, uh, Ryobi guy and he was like, 00:03:43.150 --> 00:03:46.770 or Makita guy. And he was like, you did, you 00:03:46.770 --> 00:03:50.229 did wrong. It's like, Oh man, now you gotta, 00:03:50.930 --> 00:03:53.349 Anyway, I wish I could afford the Milwaukee. 00:03:53.949 --> 00:03:56.330 Yeah. I mean, those tools are amazing. My dad 00:03:56.330 --> 00:03:59.509 has owned that reciprocating saw since I was 00:03:59.509 --> 00:04:02.469 in high school and it still runs and you have 00:04:02.469 --> 00:04:04.689 to plug it in the wall. It's not battery, but 00:04:04.689 --> 00:04:07.889 it runs like a champ and he's got a, a Hilti 00:04:07.889 --> 00:04:10.550 hammer drill from when I was in middle school. 00:04:10.650 --> 00:04:13.210 Yeah. Again, still runs. He's had to have it 00:04:13.210 --> 00:04:15.569 repaired a couple of times, but the thing just 00:04:15.569 --> 00:04:18.850 keeps going. Yeah. I mean, back then it's like 00:04:18.850 --> 00:04:21.139 I was talking to a, What were we having repaired? 00:04:21.379 --> 00:04:28.519 Oh, we were getting our washer repaired. And 00:04:28.519 --> 00:04:32.079 the guy was like, I mean, how long have you had 00:04:32.079 --> 00:04:34.720 this? And I was like, well, it was the first 00:04:34.720 --> 00:04:37.060 thing that we bought as a married couple. So 00:04:37.060 --> 00:04:41.459 17 years, almost 17 years. And he was like, yeah, 00:04:41.699 --> 00:04:44.160 they just don't last this long anymore. No. And 00:04:44.160 --> 00:04:46.439 I was like, oh, that's not good because I was 00:04:46.439 --> 00:04:50.189 about to replace this one. Keep it for as long 00:04:50.189 --> 00:04:52.009 as you can. Evidently. As long as you can still 00:04:52.009 --> 00:04:53.569 find the parts. Same thing with refrigerators. 00:04:53.670 --> 00:04:58.550 Yeah. It's just ridiculous. It's all built to 00:04:58.550 --> 00:05:03.689 fail. Okay. Oh, man. What was that? Planned obsolescence. 00:05:03.910 --> 00:05:07.430 Planned obsolescence. It's real. Did we talk 00:05:07.430 --> 00:05:09.230 about that last time or was there like a... No, 00:05:09.230 --> 00:05:13.050 last time we talked about security. No, I watched 00:05:13.050 --> 00:05:19.019 Casey Neistat did a... He doesn't do as many. 00:05:20.600 --> 00:05:22.639 You know who Casey is, right? I know the name, 00:05:22.660 --> 00:05:27.519 yeah. So YouTuber was really famous. I would 00:05:27.519 --> 00:05:30.819 still consider him famous in the YouTube world, 00:05:30.920 --> 00:05:35.040 of course, but it kind of moved into more of 00:05:35.040 --> 00:05:38.139 a godfather situation where he just doesn't make 00:05:38.139 --> 00:05:40.420 as many videos. It doesn't seem like he's relying 00:05:40.420 --> 00:05:47.819 on it for his major outlet. of uh creativity 00:05:47.819 --> 00:05:50.240 anyway maybe he made enough money it doesn't 00:05:50.240 --> 00:05:52.079 matter anymore i mean it sure seemed like he 00:05:52.079 --> 00:05:55.920 was making a lot but regardless um he he made 00:05:55.920 --> 00:05:57.759 a thing about planned obsolescence because he 00:05:57.759 --> 00:06:00.879 had he had done a long time ago he had done a 00:06:00.879 --> 00:06:05.740 uh video you know calling out apple for planned 00:06:05.740 --> 00:06:10.220 obsolescence when it came to the batteries ipod 00:06:10.220 --> 00:06:12.379 battery or was it there was definitely one with 00:06:12.379 --> 00:06:15.879 the iphone battery okay And they had to admit 00:06:15.879 --> 00:06:21.259 that they were using the code of iOS to actually 00:06:21.259 --> 00:06:24.639 make the batteries on older devices not last 00:06:24.639 --> 00:06:27.740 as long. Yeah, I think this was before that even. 00:06:27.800 --> 00:06:30.500 I think it was an iPod. And maybe it wasn't, 00:06:30.500 --> 00:06:34.240 but he was saying that the battery died on it 00:06:34.240 --> 00:06:36.339 and he just wanted a new battery and they would 00:06:36.339 --> 00:06:42.660 not do it. So this was way back, you know. way 00:06:42.660 --> 00:06:47.160 back um that he made that um and was interviewed 00:06:47.160 --> 00:06:48.860 and everything he did it with his brother and 00:06:48.860 --> 00:06:52.279 then was interviewed a lot in probably new york 00:06:52.279 --> 00:06:57.199 but maybe maybe more uh national coverage but 00:06:57.199 --> 00:07:00.879 anyway he did another thing about it because 00:07:00.879 --> 00:07:04.100 he was uh interviewing this guy who makes um 00:07:04.100 --> 00:07:08.040 game boys okay now but i mean they're they're 00:07:08.040 --> 00:07:12.810 not like the new fancy game boys that you have 00:07:12.810 --> 00:07:14.769 like all the games on them and everything they're 00:07:14.769 --> 00:07:17.410 game boys they like you need a cartridge for 00:07:17.410 --> 00:07:20.250 the back interesting um but they're made like 00:07:20.250 --> 00:07:26.670 really well um and the idea and they cost a lot 00:07:26.670 --> 00:07:30.449 and the idea would be like for super nerds i 00:07:30.449 --> 00:07:33.550 guess as the guy calls himself i don't know it 00:07:33.550 --> 00:07:36.089 was something like super nerd um that it was 00:07:36.089 --> 00:07:42.019 uh he was saying that this is like a That's the 00:07:42.019 --> 00:07:44.160 thing where you hand it down to heirloom piece. 00:07:44.199 --> 00:07:47.639 There you go. Family heirloom. I was like, well, 00:07:47.779 --> 00:07:52.680 I mean, why not? And if it's designed to last, 00:07:52.779 --> 00:07:55.800 why not? Sure. I always remember the cartridges 00:07:55.800 --> 00:07:59.680 giving up before the game boys. Yeah. You can 00:07:59.680 --> 00:08:02.139 only blow in that thing so many times. True. 00:08:02.759 --> 00:08:07.399 Very true. Anyway. Hey, I brought beer, but you 00:08:07.399 --> 00:08:14.360 brought beer. I did. So what do you have? The 00:08:14.360 --> 00:08:18.480 first one is the Wild Acre Brewing Bock Bock 00:08:18.480 --> 00:08:24.079 Imperial Bock, a Texas take on the Doppelbock. 00:08:25.199 --> 00:08:28.680 It's 8 .8%. I've never had it before. I mean, 00:08:28.699 --> 00:08:31.800 it sounds like there should be a chicken on it. 00:08:32.539 --> 00:08:35.000 The Bock Bock? Yes. Bock, Bock, Bock. Bock, Bock, 00:08:35.000 --> 00:08:36.820 Bock. It's a Bock, Bock, Bock. It's a Doppelbock. 00:08:36.820 --> 00:08:40.620 Well, there's some kind of bird, if that helps. 00:08:40.860 --> 00:08:43.379 Yeah. And there's all kinds. Oh, is that a chicken? 00:08:43.840 --> 00:08:45.779 I think that is a chicken. It should be a chicken. 00:08:46.279 --> 00:08:47.960 There needs to be a chicken. I'm calling that 00:08:47.960 --> 00:08:49.620 a chicken. Oh yeah. It's a rubber chicken. Yeah. 00:08:49.620 --> 00:08:51.740 Rubber chicken. That works. Rubber chicken. There's 00:08:51.740 --> 00:08:54.659 a Ram's head. Apparently there's an atomic bomb 00:08:54.659 --> 00:08:57.740 going off. Okay. A cowboy riding an armadillo. 00:08:59.220 --> 00:09:03.320 There you go. So I have that. Super fancy. New 00:09:03.320 --> 00:09:12.649 one. And then another. another new one. And this 00:09:12.649 --> 00:09:15.230 one drew me in by the name. And so if, if you're 00:09:15.230 --> 00:09:17.470 going to make this the name of your beer, you 00:09:17.470 --> 00:09:20.590 had better deliver. Yeah. This one is called 00:09:20.590 --> 00:09:26.809 plutonium two 39. So I'm going to give it a shot. 00:09:26.990 --> 00:09:30.210 I mean, I mean, obviously I have enough here. 00:09:30.269 --> 00:09:31.789 If you want some of this, you can have some too. 00:09:32.389 --> 00:09:37.590 It says coconut. It's a Porter, but it says coconut. 00:09:37.710 --> 00:09:41.080 I understand that. But it's, The name. It's the 00:09:41.080 --> 00:09:43.899 name. That's what made me go. Oh, sure. Okay. 00:09:44.220 --> 00:09:49.700 Okay. That's bold. Bold. To say plutonium 239. 00:09:49.840 --> 00:09:52.399 Yeah. And then at the bottom, it says a coconut 00:09:52.399 --> 00:09:55.879 porter. Like, so I'm going to find out if they 00:09:55.879 --> 00:09:57.539 deliver. I'm interested to know what you think. 00:09:57.580 --> 00:10:01.519 I am back in Texas after a long trip, which is 00:10:01.519 --> 00:10:05.120 why I'm tired. I went on a family trip. Yeah, 00:10:05.120 --> 00:10:08.860 you did. Which. I don't know if you got any other 00:10:08.860 --> 00:10:11.179 dads out there. No, I know we've got dads out 00:10:11.179 --> 00:10:15.240 there listening. Dads, you can be with me on 00:10:15.240 --> 00:10:20.740 this. That's not a vacation. No. As my friend 00:10:20.740 --> 00:10:23.860 said yesterday whenever I was talking to him 00:10:23.860 --> 00:10:30.139 about it, that's a work trip. I drove 4 ,000 00:10:30.139 --> 00:10:33.639 miles. Wow. Because we were pulling the trailer 00:10:33.639 --> 00:10:36.940 and my wife was not comfortable. pulling the 00:10:36.940 --> 00:10:40.620 trailer so i drove the entire time yeah um and 00:10:40.620 --> 00:10:48.580 we did a lot of things okay in new mexico arizona 00:10:48.580 --> 00:10:52.700 california camifornia and then back in yeah and 00:10:52.700 --> 00:10:58.820 then back in oh my gosh and then back in uh um 00:10:58.820 --> 00:11:01.860 arizona before coming home okay but the last 00:11:01.860 --> 00:11:05.759 thing we did was uh camp two days and At the 00:11:05.759 --> 00:11:08.379 Grand Canyon. Nice. And it was fantastic. Don't 00:11:08.379 --> 00:11:12.059 get me wrong. But some of my nieces and nephews 00:11:12.059 --> 00:11:15.820 in California gave me some sort of head cold. 00:11:16.039 --> 00:11:19.100 So that was a little bit more miserable. Sure. 00:11:19.279 --> 00:11:22.720 Not being able to breathe. And, you know, not 00:11:22.720 --> 00:11:26.460 sleeping. But it was a good trip. I'm just tired. 00:11:27.320 --> 00:11:30.259 Oh, yeah. You need a vacation from your vacation. 00:11:30.539 --> 00:11:35.230 Yeah. Too bad I got to go to work. Pay for all 00:11:35.230 --> 00:11:38.330 these vacation days. I took time off work to 00:11:38.330 --> 00:11:41.250 install a floor. Yeah. You're a better man than 00:11:41.250 --> 00:11:45.590 me. I don't know about that. I do. Okay. I'm 00:11:45.590 --> 00:11:48.970 going to open this. Did I even say? I've got 00:11:48.970 --> 00:11:50.990 Ziegenbach. Ziegenbach, yes. That is a good one. 00:11:51.710 --> 00:11:53.789 Because I'm back in Texas and I needed a Texas 00:11:53.789 --> 00:11:55.769 beer. I feel like I had a Ziegenbach on the last 00:11:55.769 --> 00:11:58.909 show. No, no, no. It was like two or three. Yeah, 00:11:59.029 --> 00:12:01.889 it was a couple shows back. Did they give you 00:12:01.889 --> 00:12:05.929 a blurb? Oh, yeah. I don't think Ziegenbach puts 00:12:05.929 --> 00:12:07.389 anything on the bottle, if I remember correctly. 00:12:07.509 --> 00:12:10.570 I don't think so. No, they're very, it's a Texas 00:12:10.570 --> 00:12:13.750 twist on a German classic is all they say. And 00:12:13.750 --> 00:12:18.450 it's just a beautiful beer. True. So not quite 00:12:18.450 --> 00:12:21.370 as well known as Shiner, but if you've never 00:12:21.370 --> 00:12:22.830 had Ziegenbach, you need to. It's still good. 00:12:22.929 --> 00:12:25.250 Okay, so I'm going to roll with the plutonium 00:12:25.250 --> 00:12:29.950 and see if I can read this on the back because 00:12:29.950 --> 00:12:32.779 I'm getting the old man eyes. It says, pairs 00:12:32.779 --> 00:12:36.919 well with nuts, chocolate, and steak. Those are 00:12:36.919 --> 00:12:39.799 all good things. I mean, if I had to pick some 00:12:39.799 --> 00:12:43.519 stuff. I mean, that's not bad. Not bad. To pair 00:12:43.519 --> 00:12:47.639 well with. Some good choices. So it says, if 00:12:47.639 --> 00:12:50.860 you like coconut and chocolate, this beer is 00:12:50.860 --> 00:12:53.120 for you. Yeah, I don't like coconut. No, I like 00:12:53.120 --> 00:12:57.620 coconut. It's lighter on the palate than you 00:12:57.620 --> 00:13:04.340 might think. Which means it is, okay, man, bad 00:13:04.340 --> 00:13:09.320 high day. If the weather is warm and the food 00:13:09.320 --> 00:13:16.220 is rich. Beer, not bear. That says beer. There 00:13:16.220 --> 00:13:20.259 you go. As the beer breathes, the freshly roasted 00:13:20.259 --> 00:13:23.740 coconut begins to shine. I said that last time, 00:13:23.759 --> 00:13:26.179 right? About every time I... Type beer and gear 00:13:26.179 --> 00:13:29.940 type. Yep. Bear. Bear and gear. I would also 00:13:29.940 --> 00:13:31.899 say that these guys should probably choose a 00:13:31.899 --> 00:13:35.960 different font. Yeah. So. All right. Here we 00:13:35.960 --> 00:13:41.779 go. It's a very black can. Yes, it is. With a 00:13:41.779 --> 00:13:45.879 tiny white font. Tiny white font. All right. 00:13:45.899 --> 00:13:48.019 You don't have your mug. No, no. I have cans 00:13:48.019 --> 00:13:52.879 tonight. Cheers. Cheers. I know what I think 00:13:52.879 --> 00:14:00.039 about this. Smells good. I'm interested. Actually, 00:14:00.039 --> 00:14:05.720 that's not bad. It's got a balkish type color, 00:14:05.799 --> 00:14:08.840 very similar to your Ziegenbach. I really don't 00:14:08.840 --> 00:14:17.919 taste coconut. Okay. I think I like that. Maybe 00:14:17.919 --> 00:14:19.940 I'll try it. It's brewed by the Manhattan Project 00:14:19.940 --> 00:14:25.899 Beer Company, Dallas, Texas. We did have others 00:14:25.899 --> 00:14:28.740 of theirs, right? Potentially. That name seems 00:14:28.740 --> 00:14:32.000 familiar. No, I think so. The Manhattan Project, 00:14:32.120 --> 00:14:36.500 we had two of theirs, one of the other shows. 00:14:38.039 --> 00:14:40.419 Golly. I should know our shows better than I 00:14:40.419 --> 00:14:43.360 do. Well, I was thinking about that when I was 00:14:43.360 --> 00:14:46.039 selecting these. I keep saying that we need to 00:14:46.039 --> 00:14:47.600 build a site that kind of talks about all the 00:14:47.600 --> 00:14:53.620 beers and gives them a little bit of our review, 00:14:53.820 --> 00:14:57.200 but I just never get around to it. And it would 00:14:57.200 --> 00:14:59.720 also help when I'm trying to find, A new beer. 00:15:01.000 --> 00:15:03.879 To be able to go, oh, no, actually, we didn't 00:15:03.879 --> 00:15:06.100 have that one already. Yeah, this seems like 00:15:06.100 --> 00:15:07.879 something that should be pretty easy for us to 00:15:07.879 --> 00:15:13.779 handle. Pretzels. I know some IT guys. Pretzels. 00:15:18.879 --> 00:15:23.779 So we talked about security last time. We did. 00:15:23.919 --> 00:15:25.799 We're going to talk a little bit more about security 00:15:25.799 --> 00:15:31.220 this time. Yeah. Last time almost turned into 00:15:31.220 --> 00:15:35.360 my political treaties on not trusting the government. 00:15:35.740 --> 00:15:38.740 Well. I think we'll avoid that this time. Yeah. 00:15:38.779 --> 00:15:45.919 I mean, because. Yep. So. I think I'd like to 00:15:45.919 --> 00:15:50.019 start with the Cloudflare. Cloudflare. Pretzel 00:15:50.019 --> 00:15:55.539 in the mouth. The outage that they had on back 00:15:55.539 --> 00:16:01.350 on June 12th, 2025 of this year. No doubt that 00:16:01.350 --> 00:16:05.029 pretty much everybody out there felt it in some 00:16:05.029 --> 00:16:08.129 way. Because it seems like almost everybody uses 00:16:08.129 --> 00:16:12.830 Cloudflare in some way these days. Yeah, they 00:16:12.830 --> 00:16:16.809 said the services, hold on. I mean, it pretty 00:16:16.809 --> 00:16:19.230 much talked out everything they do. Right, yeah. 00:16:19.350 --> 00:16:22.809 But in saying all of the things they were talking 00:16:22.809 --> 00:16:25.830 about, everything that they do, basically. And 00:16:25.830 --> 00:16:30.690 I was like, whoa. Workers KV, Warp, Access, Gateway, 00:16:30.950 --> 00:16:34.230 Images, Stream, Workers AI, Turnstile, and Challenges, 00:16:34.429 --> 00:16:39.669 Autorag, Zeres, and parts of the Cloudflare dashboard. 00:16:40.029 --> 00:16:43.509 Yeah, Images, Stream, Real -Time, Workers AI, 00:16:43.950 --> 00:16:49.029 Pages and Workers Assets, Durable Objects. I 00:16:49.029 --> 00:16:53.049 mean, it knocked out the CDN that they do. I 00:16:53.049 --> 00:16:57.009 mean, it was across the board, just, they're 00:16:57.009 --> 00:17:02.889 gone. And then when you look into the actual 00:17:02.889 --> 00:17:07.710 root cause, it's kind of surprising. But what 00:17:07.710 --> 00:17:11.890 I haven't been able to find is the actual company 00:17:11.890 --> 00:17:15.140 who caused them to have the problem. Yeah. Because 00:17:15.140 --> 00:17:16.119 when you look into it. Because they mentioned 00:17:16.119 --> 00:17:18.859 that. They're like, this wasn't us, but we should 00:17:18.859 --> 00:17:21.519 be more careful who we depend on. Correct. And 00:17:21.519 --> 00:17:24.119 I was like, ooh, shots fired. You know who you 00:17:24.119 --> 00:17:27.680 are. Yeah. So everybody just says a third -party 00:17:27.680 --> 00:17:31.660 storage company. Is that Amazon? Right. Is that 00:17:31.660 --> 00:17:35.019 Microsoft? I mean. Is that some other vendor 00:17:35.019 --> 00:17:39.200 out there that I'm not aware of? But yeah, so 00:17:39.200 --> 00:17:43.160 they had disk issues. Which caused cascading 00:17:43.160 --> 00:17:44.700 effects through all their service, which then 00:17:44.700 --> 00:17:47.920 cascaded out until everybody else who uses it, 00:17:47.960 --> 00:17:51.460 you couldn't get the sites. I mean, it was crazy. 00:17:52.019 --> 00:17:55.660 I mean, unfortunately, we've built these systems 00:17:55.660 --> 00:18:00.519 that everybody is so dependent upon. And when 00:18:00.519 --> 00:18:05.859 they have a problem, it hits everything. So I 00:18:05.859 --> 00:18:08.819 hear... John C. Dvorak in my head, and it's not 00:18:08.819 --> 00:18:11.440 quite a one -for -one translation, but he usually 00:18:11.440 --> 00:18:15.579 gripes about microservices architecture. And 00:18:15.579 --> 00:18:20.180 so you have this multiple -layer stack, and all 00:18:20.180 --> 00:18:24.740 it takes is for one layer to say, I'm out, and 00:18:24.740 --> 00:18:27.279 the whole stack collapses. The system just can't 00:18:27.279 --> 00:18:30.400 handle that or recover from it. And so that's 00:18:30.400 --> 00:18:33.900 literally what happened here. They had their 00:18:33.900 --> 00:18:37.910 only... Storage provider have an issue. So, of 00:18:37.910 --> 00:18:40.170 course, everything is gone. Now, what they are 00:18:40.170 --> 00:18:42.130 saying is they're going to work on diversifying 00:18:42.130 --> 00:18:46.630 their storage so that if one goes, they can essentially 00:18:46.630 --> 00:18:49.450 try to recover. I mean, are they talking about... 00:18:49.450 --> 00:18:54.450 I mean, I was going to say raid, but not raid. 00:18:54.670 --> 00:19:00.779 But, like, are they talking about... So diversifying 00:19:00.779 --> 00:19:03.019 in terms of like some of their stuff will go 00:19:03.019 --> 00:19:05.000 down and not all of their stuff. Are they talking 00:19:05.000 --> 00:19:08.200 about like if they lose one or are they talking 00:19:08.200 --> 00:19:10.619 about doing some sort of like redundancy where 00:19:10.619 --> 00:19:13.900 there's like, oh, no, we switch to that. The 00:19:13.900 --> 00:19:16.180 way that I interpreted what they said is they're 00:19:16.180 --> 00:19:19.740 actually going to bring in other additional storage 00:19:19.740 --> 00:19:22.839 providers. Now, how they plan on distributing 00:19:22.839 --> 00:19:26.160 their data across those for redundancy, they 00:19:26.160 --> 00:19:28.369 don't really go into a lot of detail. Yeah, probably 00:19:28.369 --> 00:19:32.029 on purpose. Oh, I'm sure. But so it would seem 00:19:32.029 --> 00:19:34.369 like once they get this implemented, because 00:19:34.369 --> 00:19:37.210 it's not, last I checked, I don't think they're 00:19:37.210 --> 00:19:41.730 done yet. But the whole idea would be, okay, 00:19:41.750 --> 00:19:44.170 if this particular vendor goes down again, number 00:19:44.170 --> 00:19:45.450 one, they're probably never going to use them 00:19:45.450 --> 00:19:49.210 again. But the number two on that is they could 00:19:49.210 --> 00:19:52.730 roll over to whoever the additional providers 00:19:52.730 --> 00:19:54.809 are. So I'm going to assume that they have to 00:19:54.809 --> 00:19:58.910 have all their data. across all of these in order 00:19:58.910 --> 00:20:02.970 to be able to handle that kind of an outage. 00:20:03.809 --> 00:20:10.349 Yeah, I mean, that's... There is dependent on 00:20:10.349 --> 00:20:14.390 themselves as everybody else is. So I do think 00:20:14.390 --> 00:20:17.069 it would make more sense for there to be just 00:20:17.069 --> 00:20:22.650 straight redundancy in diversified locations. 00:20:24.319 --> 00:20:28.579 I don't know. That's why they pay them big bucks, 00:20:28.619 --> 00:20:30.440 and I'm just sitting here doing this podcast 00:20:30.440 --> 00:20:34.660 with my beer. There you go. And I think the other 00:20:34.660 --> 00:20:39.000 thing that was surprising to me is all these 00:20:39.000 --> 00:20:42.539 folks, they have their own data centers. Yeah. 00:20:42.680 --> 00:20:45.819 So I would have expected them to own their own 00:20:45.819 --> 00:20:49.180 storage. Apparently, that's not correct. So they 00:20:49.180 --> 00:20:51.660 must keep just the minimum that they need in 00:20:51.660 --> 00:20:56.079 whatever. or white boxes that they're utilizing 00:20:56.079 --> 00:20:58.000 in the data center, and then they're depending 00:20:58.000 --> 00:21:04.500 on some other data center somewhere to give them 00:21:04.500 --> 00:21:07.259 the storage that they need. So I found that to 00:21:07.259 --> 00:21:10.779 be intriguing. And so now I'm sitting here going, 00:21:11.019 --> 00:21:13.700 okay, so does Microsoft own their own storage? 00:21:13.799 --> 00:21:17.119 Does Amazon own their own storage? Is this unique 00:21:17.119 --> 00:21:19.920 to Cloudflare? Well, actually, I know it's not 00:21:19.920 --> 00:21:22.119 because this will dovetail into something that 00:21:22.119 --> 00:21:24.460 happened on the same day. But it was intriguing 00:21:24.460 --> 00:21:27.900 to understand that these guys don't own their 00:21:27.900 --> 00:21:37.140 own storage to some capacity. Yeah. I mean, yeah. 00:21:37.420 --> 00:21:41.319 I think that, like you said, they do, just not 00:21:41.319 --> 00:21:45.059 the level of storage that's necessary for. And 00:21:45.059 --> 00:21:46.980 I think that that has a lot to probably do with. 00:21:49.220 --> 00:21:51.980 That being more complicated than everybody gives 00:21:51.980 --> 00:21:54.720 it credit for. Perhaps. Server farms are not 00:21:54.720 --> 00:21:59.059 easy things. No, not at all. But I would figure 00:21:59.059 --> 00:22:02.579 if you're building out these data centers, you're 00:22:02.579 --> 00:22:05.480 also building out the storage inside of it, but 00:22:05.480 --> 00:22:09.980 apparently not. So what also happened on that 00:22:09.980 --> 00:22:13.099 same day, but kind of went mostly unreported 00:22:13.099 --> 00:22:17.200 and where I get my information from was that. 00:22:17.900 --> 00:22:21.680 Google cloud had an outage because they use the 00:22:21.680 --> 00:22:25.980 same third party vendor, whoever it is. So on 00:22:25.980 --> 00:22:29.000 that day when this happened and we, for us, it 00:22:29.000 --> 00:22:33.420 first presented as a Spotify outage. Yeah. And 00:22:33.420 --> 00:22:36.119 then shortly thereafter it was like, Oh no, that 00:22:36.119 --> 00:22:37.960 actually there's a cloud flare outage. Okay. 00:22:38.019 --> 00:22:40.920 So that's probably why Spotify is down because 00:22:40.920 --> 00:22:42.660 they probably leverage cloud flare. And to some 00:22:42.660 --> 00:22:45.970 degree that's probably true. But it seems like 00:22:45.970 --> 00:22:49.450 the bigger problem for Spotify on that day is 00:22:49.450 --> 00:22:53.150 they use Google Cloud Compute. And so when Google 00:22:53.150 --> 00:22:56.390 had the problem, they had the problem. And there 00:22:56.390 --> 00:22:58.670 may or may not have been some extra layer there 00:22:58.670 --> 00:23:01.349 with them potentially leveraging Cloudflare as 00:23:01.349 --> 00:23:04.650 well. But that was an outage that kind of went 00:23:04.650 --> 00:23:10.349 unannounced, kind of unnoticed. So again, Google, 00:23:10.529 --> 00:23:12.809 I would imagine that Google would have owned 00:23:12.809 --> 00:23:14.630 all their own storage, but apparently they don't. 00:23:16.929 --> 00:23:22.049 No. No, they don't. To me, that was kind of telling. 00:23:23.349 --> 00:23:29.329 I mean, I think you're right. I think it's a 00:23:29.329 --> 00:23:34.190 surprising thing, but I don't think that it's 00:23:34.190 --> 00:23:38.710 unreasonable to expect people to focus on what 00:23:38.710 --> 00:23:45.329 they're actually good at. Sure. Something tells 00:23:45.329 --> 00:23:50.789 me it is a difficult thing to do, making sure 00:23:50.789 --> 00:23:52.809 that all those servers are going and functioning 00:23:52.809 --> 00:23:54.430 properly and doing what they're supposed to do 00:23:54.430 --> 00:23:59.309 and always connected and always running, all 00:23:59.309 --> 00:24:02.130 of that. But it does seem like the kind of thing 00:24:02.130 --> 00:24:05.470 that's going to be kind of lowest bidder. Somebody 00:24:05.470 --> 00:24:11.509 can do a bunch of that and then not have to hit 00:24:11.509 --> 00:24:17.700 your... What do you call it? Capital line? Oh, 00:24:17.700 --> 00:24:20.700 yeah. The bottom line. Yeah. I got a little coconut 00:24:20.700 --> 00:24:27.420 that time. It wasn't bad. Gross. Stop it. I probably 00:24:27.420 --> 00:24:30.019 won't. Stop trying to make it okay. No, no, no. 00:24:30.019 --> 00:24:31.599 I won't go out of my way to probably buy it again. 00:24:32.500 --> 00:24:36.079 But, I mean, it's not bad. I mean, it's better 00:24:36.079 --> 00:24:39.619 than the porter that we had last time for founders. 00:24:39.880 --> 00:24:44.579 Oh. I didn't remember the porter's founder being. 00:24:45.299 --> 00:24:50.019 Being that way, but the breakfast out is amazing. 00:24:50.480 --> 00:24:56.140 Breakfast out was amazing. Yes. So good. I mean, 00:24:56.440 --> 00:25:01.220 I'll finish off this six pack probably by the 00:25:01.220 --> 00:25:06.019 end of the show. Well, no. No, I need to drive. 00:25:06.640 --> 00:25:08.960 End of the weekend. End of the weekend. End of 00:25:08.960 --> 00:25:10.880 the weekend, yes. You're definitely going to 00:25:10.880 --> 00:25:13.829 need one after you finish tomorrow. Goodness. 00:25:15.890 --> 00:25:19.710 I'll go into that and into the, the bach bach, 00:25:19.730 --> 00:25:22.430 the chicken, the chicken beer, the chicken beer, 00:25:22.529 --> 00:25:24.890 man. Um, I, yeah, I don't know. That's a very 00:25:24.890 --> 00:25:31.869 funny name for a beer. Yeah. Yeah. So you're 00:25:31.869 --> 00:25:35.950 kind of taller cans too. So, so yeah. So this 00:25:35.950 --> 00:25:39.250 cloud flare, I mean, that was, that was, that 00:25:39.250 --> 00:25:41.470 was crazy. I mean, I'm, we were sitting at work 00:25:41.470 --> 00:25:45.559 and, like i said started with uh spotify and 00:25:45.559 --> 00:25:48.279 then it just kind of cascaded through other cloud 00:25:48.279 --> 00:25:50.519 systems that we use and it's just like oh my 00:25:50.519 --> 00:25:55.339 goodness and it uh it hit uh eight by eight our 00:25:55.339 --> 00:25:58.279 phone system and of course they're all like hey 00:25:58.279 --> 00:26:00.619 what are we gonna do and i'm like there's nothing 00:26:00.619 --> 00:26:04.480 we can do yeah we are we're in the cloud we're 00:26:04.480 --> 00:26:06.640 dependent upon these things and when they go 00:26:06.640 --> 00:26:10.319 belly up so do we we got nothing this is one 00:26:10.319 --> 00:26:12.940 of those like oh Everybody understands us when 00:26:12.940 --> 00:26:15.480 it comes to electricity. And they're like, okay. 00:26:15.680 --> 00:26:17.700 Except, I will tell you, there are some people 00:26:17.700 --> 00:26:19.579 that whenever the electricity goes out, they 00:26:19.579 --> 00:26:24.319 do like to, at our location here, they do like 00:26:24.319 --> 00:26:28.220 to ask me if the internet is still working. In 00:26:28.220 --> 00:26:29.519 which case, I'm going to tell you. For the moment. 00:26:30.259 --> 00:26:33.440 I mean, we've probably got 20 minutes. Yeah. 00:26:34.980 --> 00:26:38.720 But that's it. And only because we're running 00:26:38.720 --> 00:26:45.680 these. Battery backups. Get off. It's just funny 00:26:45.680 --> 00:26:48.259 that like, well, what I was saying is when people 00:26:48.259 --> 00:26:50.099 know that the electricity has gone out, they 00:26:50.099 --> 00:26:52.759 don't expect the air conditioning to work. True. 00:26:54.619 --> 00:26:56.980 I do still walk into rooms and try to flip on 00:26:56.980 --> 00:27:00.000 the lights. Yes. It's just a habit. Yes. Force 00:27:00.000 --> 00:27:03.420 of habit. But it is very much like one of those 00:27:03.420 --> 00:27:07.160 things where now you see them like. Everybody 00:27:07.160 --> 00:27:08.880 doesn't understand the dependencies that are 00:27:08.880 --> 00:27:13.500 happening across different areas in order to 00:27:13.500 --> 00:27:18.000 make your phone work. You're just like, well, 00:27:18.079 --> 00:27:21.480 I used to pick it up and hear the party line. 00:27:22.940 --> 00:27:27.140 Very true. Well, you know, you could tell them 00:27:27.140 --> 00:27:31.140 and go, well, if you let me buy an inverter generator. 00:27:31.539 --> 00:27:34.339 Yeah, right. I could at least keep the student 00:27:34.339 --> 00:27:36.910 building online. Yeah. And then you can have 00:27:36.910 --> 00:27:39.390 all the internet you want. I have mentioned it 00:27:39.390 --> 00:27:43.690 for when other things happen in that building 00:27:43.690 --> 00:27:47.990 that are going to change things. But that's all 00:27:47.990 --> 00:27:53.210 I do is mention things now. I was looking at 00:27:53.210 --> 00:27:56.150 the notable Cloudflare outages that have happened 00:27:56.150 --> 00:27:58.609 over the past few years. They had one in 2022 00:27:58.609 --> 00:28:03.069 and one in 2023. And then one of those I think 00:28:03.069 --> 00:28:11.440 was a hack. Yeah. The 2022 was a configuration 00:28:11.440 --> 00:28:17.180 change. 23 was a network -wide issue caused by 00:28:17.180 --> 00:28:20.640 a brief outage affecting many websites and businesses. 00:28:21.200 --> 00:28:25.079 I don't know if that was a hack or not. And then 00:28:25.079 --> 00:28:34.799 there was one in 2024. And then three. So far 00:28:34.799 --> 00:28:44.660 in 2025. February, June, and July. Yes. So in 00:28:44.660 --> 00:28:49.599 2023, they were compromised, but it had more 00:28:49.599 --> 00:28:53.599 to do with the breach in Okta than it had to 00:28:53.599 --> 00:28:57.500 do with Cloudflare. So again, all of these interdependencies, 00:28:57.500 --> 00:29:03.069 you leverage Okta, they get hacked. Okay, where 00:29:03.069 --> 00:29:05.869 else can that person go? Anyone that's using 00:29:05.869 --> 00:29:09.990 single sign -on with Okta? Yeah. And again, if 00:29:09.990 --> 00:29:13.890 they get access to the admin side of Okta, game 00:29:13.890 --> 00:29:17.549 over. And we would have the same thing at Pine 00:29:17.549 --> 00:29:20.289 Cove if somebody was to, and it has happened, 00:29:20.390 --> 00:29:22.910 but it was a very limited scope. But if somebody 00:29:22.910 --> 00:29:26.529 compromised JumpCloud, they could come after 00:29:26.529 --> 00:29:29.049 anybody within it. Now, the one that they had, 00:29:29.150 --> 00:29:33.420 I think was a year or so ago. But they were going 00:29:33.420 --> 00:29:38.880 after NGOs. Really? And they never quite said 00:29:38.880 --> 00:29:42.480 who it was. So I would assume going after NGOs, 00:29:42.660 --> 00:29:45.880 it's got to be a state actor. And thinking of 00:29:45.880 --> 00:29:48.160 what's been going on recently. I mean, there's 00:29:48.160 --> 00:29:50.700 a few that are popping in my head. I go to Russia. 00:29:50.980 --> 00:29:55.000 Yeah. Because they kicked all the NGOs out. And 00:29:55.000 --> 00:29:59.650 then potentially China as well. But it was intriguing 00:29:59.650 --> 00:30:01.890 that they specifically went to these. It's always 00:30:01.890 --> 00:30:04.890 potentially China. They do some shady stuff. 00:30:05.109 --> 00:30:09.849 Well, I'm saying. I think there was the one that 00:30:09.849 --> 00:30:12.309 we're going to talk about here in a second with 00:30:12.309 --> 00:30:16.849 another company. Everybody was eyeballing China 00:30:16.849 --> 00:30:18.910 pretty hard for that. Yeah, they were. Still 00:30:18.910 --> 00:30:22.670 are. I guess we can just jump over there. So 00:30:22.670 --> 00:30:27.450 Microsoft got hacked. Yeah, they did. This was 00:30:27.450 --> 00:30:30.829 in July, though, right? Yeah, this one just happened. 00:30:31.369 --> 00:30:35.170 So still pretty fresh. Not that the Cloudflare 00:30:35.170 --> 00:30:38.849 we just talked about wasn't too far back. Well, 00:30:38.869 --> 00:30:40.289 there was another Cloudflare. We'll talk about 00:30:40.289 --> 00:30:41.990 that later, too. There was another Cloudflare 00:30:41.990 --> 00:30:44.390 that happened later as well. But this Microsoft 00:30:44.390 --> 00:30:47.049 one. It's still ongoing. That's what makes this 00:30:47.049 --> 00:30:49.069 one intriguing. Still trying to figure out the 00:30:49.069 --> 00:30:55.170 extent. Correct. So what this gets into is using 00:30:55.170 --> 00:30:58.980 SharePoint. which a ton of corporations use. 00:30:59.400 --> 00:31:02.779 But what's so far unique to this is it doesn't 00:31:02.779 --> 00:31:07.559 impact cloud. Too many things. SharePoint online, 00:31:07.900 --> 00:31:11.579 it's local running it on your own gear is where 00:31:11.579 --> 00:31:15.019 this is being impacted. So that's kind of intriguing. 00:31:15.579 --> 00:31:19.599 Yeah, so if you were using SharePoint as the 00:31:19.599 --> 00:31:24.589 SharePoint server. in like Microsoft, if you 00:31:24.589 --> 00:31:27.490 were using Microsoft SharePoint. Yeah, 365. 365, 00:31:27.690 --> 00:31:32.470 you're fined. Currently. Currently. Oh, gosh. 00:31:32.789 --> 00:31:36.849 But if you were running an instance of SharePoint 00:31:36.849 --> 00:31:40.450 on a server locally, there were a lot of those 00:31:40.450 --> 00:31:46.710 that got hit. Yes. They said 100. So far. And 00:31:46.710 --> 00:31:49.170 then it turned into, I mean, I just kept reading 00:31:49.170 --> 00:31:51.789 the article, and I was like, oh, 100, 100, 100. 00:31:51.990 --> 00:31:55.490 And then it was like, well, conservatively, we 00:31:55.490 --> 00:32:00.109 think 9 ,000. And I was like, what? I hadn't 00:32:00.109 --> 00:32:02.269 read that number yet. So a pool of potential 00:32:02.269 --> 00:32:05.269 targets remains vast, according to data from 00:32:05.269 --> 00:32:10.809 Shodan. This is from Reuters. Reuters. Reuters. 00:32:11.170 --> 00:32:15.329 Reuters, yeah. According to the data from Shodan, 00:32:15.390 --> 00:32:17.730 a search engine that helps to identify internet 00:32:17.730 --> 00:32:21.289 -linked equipment, over 8 ,000 servers online 00:32:21.289 --> 00:32:23.869 could theoretically have been compromised by 00:32:23.869 --> 00:32:26.269 hackers. Shadow Server put the number a little 00:32:26.269 --> 00:32:28.829 more than 9 ,000 while cautioning that that figure 00:32:28.829 --> 00:32:32.190 was a minimum. So what they were saying is when 00:32:32.190 --> 00:32:38.490 they noticed a problem and it was, what's that 00:32:38.490 --> 00:32:45.039 guy's name? Vysha Bernard? Chief hacker at iSecurity 00:32:45.039 --> 00:32:49.180 in the Netherlands or a Netherlands -based cybersecurity 00:32:49.180 --> 00:32:54.559 firm. And he was either using, he was doing a 00:32:54.559 --> 00:32:56.519 scan carried out with the Shadow Server Foundation, 00:32:56.819 --> 00:33:00.960 which you just got to love. Shadow Server, I 00:33:00.960 --> 00:33:04.740 mean. Yeah. Good name. Way to domain that bad 00:33:04.740 --> 00:33:13.109 boy. Yeah. Golly. Anyway. Jealous. But they were 00:33:13.109 --> 00:33:14.950 saying that when they noticed that it was 100, 00:33:15.130 --> 00:33:22.990 they were seeing traffic on around 100 different 00:33:22.990 --> 00:33:27.430 companies, different organizations. Can't even 00:33:27.430 --> 00:33:30.089 call them companies. Sorry. Organizations. Because 00:33:30.089 --> 00:33:37.240 some of them were definitely government. Everybody 00:33:37.240 --> 00:33:39.779 was notified that they could tell. It seemed 00:33:39.779 --> 00:33:42.880 to be mostly affecting United States and Germany. 00:33:43.259 --> 00:33:48.000 But again, this was the first time that this 00:33:48.000 --> 00:33:56.160 Microsoft weakness, weak spot, whatever you call 00:33:56.160 --> 00:34:03.670 it, security. whole vulnerability vulnerability 00:34:03.670 --> 00:34:09.530 was was used so they don't know they don't know 00:34:09.530 --> 00:34:12.130 how many actually got hit they just know how 00:34:12.130 --> 00:34:15.909 many like that they saw this activity on yeah 00:34:15.909 --> 00:34:18.789 and so that's why they're saying eight thousand 00:34:18.789 --> 00:34:22.030 nine thousand conservatively like the that's 00:34:22.030 --> 00:34:27.380 the number of instances of yeah a conservative 00:34:27.380 --> 00:34:30.480 number for the number of instances of SharePoint 00:34:30.480 --> 00:34:35.800 that were running not at Microsoft. Yeah. And 00:34:35.800 --> 00:34:40.000 so what's also was intriguing in this is this 00:34:40.000 --> 00:34:43.519 vulnerability was identified at a hacking event. 00:34:44.460 --> 00:34:47.599 Really? Yes. That's what they were doing. Yes. 00:34:47.639 --> 00:34:51.260 And so they know, obviously they, it was a trend 00:34:51.260 --> 00:34:54.760 micro. Okay. And the hacker who did it was given 00:34:54.760 --> 00:34:56.929 a hundred thousand dollars. And of course, they 00:34:56.929 --> 00:34:58.949 then go, hey, Microsoft, here's this. You need 00:34:58.949 --> 00:35:02.769 to go fix it. And so Microsoft pushed the fix. 00:35:03.889 --> 00:35:06.869 But it didn't fix it. It didn't fix it or people 00:35:06.869 --> 00:35:09.170 didn't run the... Oh, no, it didn't fix it. Oh, 00:35:09.210 --> 00:35:14.090 that sucks. Yeah. And then on top of that, they 00:35:14.090 --> 00:35:18.130 were then leveraging other known vulnerabilities, 00:35:18.369 --> 00:35:20.610 which probably comes down to people not doing 00:35:20.610 --> 00:35:25.130 proper patching. Yeah. Because there's... I'm 00:35:25.130 --> 00:35:28.989 seeing four different ones here. And this one 00:35:28.989 --> 00:35:32.530 that's being leveraged, I forget the name of 00:35:32.530 --> 00:35:36.710 the company that has the new scale, but basically 00:35:36.710 --> 00:35:39.610 it goes from zero to 10. And this particular 00:35:39.610 --> 00:35:44.030 issue was rated a 9 .8. I mean, that's like... 00:35:44.030 --> 00:35:47.170 That's serious. The house is on fire. Drop everything. 00:35:47.969 --> 00:35:51.760 You need to go fix this now. See, I got confused 00:35:51.760 --> 00:35:55.059 because in my reading or whatever, I was seeing 00:35:55.059 --> 00:35:58.659 that Microsoft was saying, like, there's a fix. 00:35:58.880 --> 00:36:04.440 You need to run your updates, basically. But 00:36:04.440 --> 00:36:07.239 you're saying that the initial fix was not a 00:36:07.239 --> 00:36:10.019 fix. No, no, no. Oh, gosh. No, because Microsoft 00:36:10.019 --> 00:36:13.480 themselves said there is a zero -day vulnerability. 00:36:14.059 --> 00:36:18.260 Here's the patch. Install this. And people did, 00:36:18.400 --> 00:36:20.659 but unfortunately, it still didn't completely 00:36:20.659 --> 00:36:25.059 fix the fix. So depending on how people were 00:36:25.059 --> 00:36:31.699 running SharePoint, somebody either had to be 00:36:31.699 --> 00:36:34.659 inside the network already, which once they're 00:36:34.659 --> 00:36:36.800 inside, it doesn't matter what you've got. It's 00:36:36.800 --> 00:36:40.139 game over. But SharePoint, it's not uncommon 00:36:40.139 --> 00:36:42.539 as well for it to be accessible from the outside 00:36:42.539 --> 00:36:47.119 world. Because you're trying to talk to different 00:36:47.119 --> 00:36:49.300 things. Correct. And you need access to the company 00:36:49.300 --> 00:36:53.360 data. So a hacker who's worth his salt is going 00:36:53.360 --> 00:36:56.800 to be able to find that opening in the firewall 00:36:56.800 --> 00:37:00.360 and be able to pull some back and go, oh, SharePoint. 00:37:01.619 --> 00:37:04.000 And no, these are the current vulnerabilities. 00:37:04.199 --> 00:37:07.980 Let's see how up -to -date they are. But again, 00:37:08.079 --> 00:37:10.219 once they got in, then they were able to leverage 00:37:10.219 --> 00:37:13.139 three other vulnerabilities. Now, they're all 00:37:13.139 --> 00:37:18.690 from this year. Because they're CVE -2025. So 00:37:18.690 --> 00:37:22.550 they're all recent things that have been discovered. 00:37:23.190 --> 00:37:26.909 But it's just crazy to think that I'm going to 00:37:26.909 --> 00:37:29.989 leverage the one, and then now I get to leverage 00:37:29.989 --> 00:37:34.670 all these others and run crazy. And once they're 00:37:34.670 --> 00:37:38.409 in, they're pushing malware. Well, they're trying 00:37:38.409 --> 00:37:41.429 to open up. all kinds of vulnerabilities into 00:37:41.429 --> 00:37:43.690 your system. Correct. Yeah. That they can then 00:37:43.690 --> 00:37:46.610 get back into. Yeah. Because now they're not 00:37:46.610 --> 00:37:49.929 just in one, like they're in the whole thing. 00:37:49.969 --> 00:37:52.730 Correct. And so they were able to leverage this 00:37:52.730 --> 00:37:55.530 to obviously push ransomware, but then they were 00:37:55.530 --> 00:37:59.230 able to pivot into other systems as you were 00:37:59.230 --> 00:38:02.869 referring to and just spread their way through 00:38:02.869 --> 00:38:05.849 these internal networks. And so it turned into 00:38:05.849 --> 00:38:09.920 way more than just. Our SharePoint got compromised. 00:38:10.780 --> 00:38:14.179 It's company -wide. See, what they should be 00:38:14.179 --> 00:38:17.380 doing is trying to take just fractions of a penny 00:38:17.380 --> 00:38:25.539 off of every... Hello, Superman 3. Hackers. And 00:38:25.539 --> 00:38:31.079 hackers. And hackers. It eats itself. And then 00:38:31.079 --> 00:38:36.280 it's gone. Yes. And all the tankers. Never mind. 00:38:36.840 --> 00:38:39.320 Hack the planet. Hack the planet, yes. The visuals 00:38:39.320 --> 00:38:44.380 in that show were crazy. Oh, my gosh. As ridiculous 00:38:44.380 --> 00:38:49.599 as some of it was, it was not nearly as bad as, 00:38:49.619 --> 00:38:54.599 I think there was a CSI or NCIS, one of those. 00:38:56.679 --> 00:39:01.780 It was NCIS. Somebody was getting hacked, and 00:39:01.780 --> 00:39:05.719 two people were on a single keyboard. What? Yeah. 00:39:06.269 --> 00:39:09.110 Like that makes it better. Like sharing a piano. 00:39:09.289 --> 00:39:15.309 Yeah. It was, it was, it was a little bit like, 00:39:15.389 --> 00:39:19.309 what have you, y 'all don't know. That's not 00:39:19.309 --> 00:39:21.550 how this works. Who's y 'all's consultant. Yeah. 00:39:22.769 --> 00:39:28.909 Don't do that. Anyway, it was, I don't watch 00:39:28.909 --> 00:39:30.809 the show, but somebody showed me a clip from 00:39:30.809 --> 00:39:33.789 it. Cause I was, Oh man, that was pretty great. 00:39:34.269 --> 00:39:40.769 Wow. So you're going to the bach bach? Mm -hmm. 00:39:41.949 --> 00:39:45.210 Cheers. Cheers again. Do they give me... Definitely 00:39:45.210 --> 00:39:49.510 on my second Zigen here. There's the ingredients. 00:39:50.909 --> 00:39:55.170 8 .8 ABV. Nope. They just say, finally, a Texas 00:39:55.170 --> 00:40:00.570 -sized bach. One can, two bachs. What? That's 00:40:00.570 --> 00:40:02.829 what it says. One can, two bachs. Okay, well... 00:40:02.829 --> 00:40:07.650 Fort Worth. Fort Worth. 8 .8. That's why there's 00:40:07.650 --> 00:40:10.630 a cowboy riding on Armadillo. Yeah, there is. 00:40:10.769 --> 00:40:13.969 Very, very Fort Worth, Texas. I mean, there's 00:40:13.969 --> 00:40:18.210 all kinds of stuff on here. Choo -choo train. 00:40:18.409 --> 00:40:22.010 So this is Wild Acre? Wild Acre, yeah. Wild Acre 00:40:22.010 --> 00:40:26.909 Brewing. I cannot overstate how much I'm enjoying 00:40:26.909 --> 00:40:32.409 my Zegans over here. Zegan is good. It feels 00:40:32.409 --> 00:40:40.219 very much like a... Smells like a Bach. Heat 00:40:40.219 --> 00:40:44.219 beer. It's too hot outside, so I'm drinking this 00:40:44.219 --> 00:40:47.679 beer. I would think that would be too dark of 00:40:47.679 --> 00:40:51.280 a beer for you on a hot day. Oh, no. It's still 00:40:51.280 --> 00:40:56.039 refreshing. All right. Give us the whatever you 00:40:56.039 --> 00:40:59.719 call it. Imperial Bach. It said it was a double 00:40:59.719 --> 00:41:02.460 Bach. Tastes like a Bach. I don't know what else 00:41:02.460 --> 00:41:07.320 to say. Okay. I mean. Makes me think of Ziegen. 00:41:07.360 --> 00:41:13.199 Makes me think of Shiner. Okay. Yeah, it just 00:41:13.199 --> 00:41:16.400 tastes like a bog. So Wild Acre Brewing is in 00:41:16.400 --> 00:41:21.699 Fort Worth. According to the can. Fort Worth, 00:41:21.800 --> 00:41:25.639 Texas. And then it also says Maine and Delaware. 00:41:26.619 --> 00:41:32.139 Hmm. Oh, no. Ha, ha, ha. I can't read. Fort Worth, 00:41:32.219 --> 00:41:36.619 Texas made. But the abbreviations. Oh, my God. 00:41:37.820 --> 00:41:41.420 Yeah, pay attention, idiot. Well, there you go. 00:41:42.019 --> 00:41:44.039 And then, of course, right next to it is Texas 00:41:44.039 --> 00:41:48.519 with the TX on it. I mean, I don't know what 00:41:48.519 --> 00:41:50.579 else to say. It's a very Texas can. It tastes 00:41:50.579 --> 00:41:58.079 like a Bach. Mm -hmm. How dark is it? Can't tell 00:41:58.079 --> 00:42:00.380 in the can. Well, you can see a little bit on 00:42:00.380 --> 00:42:03.119 the. rim there i mean it just looks like a normal 00:42:03.119 --> 00:42:06.960 looks like a bach brown golden brown brown yeah 00:42:06.960 --> 00:42:10.880 maybe a little bit darker brown yeah it's a bach 00:42:10.880 --> 00:42:14.219 well there you go so way to go bach bach yeah 00:42:14.219 --> 00:42:20.880 bach bach yeah so the but no coconut so no no 00:42:20.880 --> 00:42:24.119 coconut and just a couple of swigs where i actually 00:42:24.119 --> 00:42:27.340 got the coconut but yeah so what's intriguing 00:42:27.340 --> 00:42:29.960 with the microsoft hit is that it's still ongoing 00:42:29.960 --> 00:42:33.260 yeah they're they're still uncovering yeah so 00:42:33.260 --> 00:42:36.340 all these all these systems i'm sure they're 00:42:36.340 --> 00:42:38.059 trying to put as many patches on as they can 00:42:38.059 --> 00:42:41.440 and i would assume this instruction is going 00:42:41.440 --> 00:42:45.039 to change but i was watching a video on youtube 00:42:45.039 --> 00:42:47.920 about it and they were saying that the government 00:42:47.920 --> 00:42:51.440 was telling various uh other parts of the government 00:42:51.440 --> 00:42:54.659 and third parties yeah if you don't have this 00:42:54.659 --> 00:42:57.289 patch installed by i think it was Like August 00:42:57.289 --> 00:42:59.150 10th? We're not touching you. You're getting 00:42:59.150 --> 00:43:01.389 disconnected. Yeah. And I'm just kind of like, 00:43:01.449 --> 00:43:02.969 I don't think I would even give them that long. 00:43:03.170 --> 00:43:06.250 No. I would give them 48 hours. You need to have 00:43:06.250 --> 00:43:09.010 this in. Well, I don't. I mean, some of it, it 00:43:09.010 --> 00:43:10.809 feels like it should be even faster than that. 00:43:11.030 --> 00:43:18.130 Sure. The idea that there's this kind of vulnerability 00:43:18.130 --> 00:43:24.489 and it's been leveraged and they know that there's 00:43:24.489 --> 00:43:31.940 already a problem. Stop it. Correct. You don't 00:43:31.940 --> 00:43:35.980 give the gangrene 48 hours to see if it spreads 00:43:35.980 --> 00:43:39.900 to the arm. No. Like just cut off the finger 00:43:39.900 --> 00:43:44.300 or whatever it is. Cut it out. Oh, nice. There 00:43:44.300 --> 00:43:47.519 you go. There's your reference. Took me back. 00:43:48.429 --> 00:43:52.949 I mean, y 'all not being in the room is really 00:43:52.949 --> 00:43:57.030 sad for you because, I mean, it was full house, 00:43:57.130 --> 00:44:00.389 full hand gestures. Is that Dave Coulier? Yeah, 00:44:00.469 --> 00:44:05.630 absolutely. I seem to feel like he passed away 00:44:05.630 --> 00:44:08.590 recently. You know who did pass away recently? 00:44:09.309 --> 00:44:13.070 There was one today. Hulk Hogan. Yeah, and then 00:44:13.070 --> 00:44:15.070 a couple of days ago it was Ozzy Osbourne. Yeah. 00:44:16.010 --> 00:44:22.349 It's not a good day for us. No. I did see a video 00:44:22.349 --> 00:44:26.949 earlier today of a guy who actually gave Ozzy 00:44:26.949 --> 00:44:31.650 Osbourne a Bible within the last six months to 00:44:31.650 --> 00:44:35.409 a year. Yeah. Because he had previously met him 00:44:35.409 --> 00:44:37.550 and he said, I'd love to read the Bible, but 00:44:37.550 --> 00:44:41.150 I can't understand the dadgum thing because it's 00:44:41.150 --> 00:44:44.550 in Old English. So this guy gave him a new version. 00:44:45.769 --> 00:44:48.869 He had his name embossed on the whole thing and 00:44:48.869 --> 00:44:51.269 gave it to him at the next Comic -Con type event 00:44:51.269 --> 00:44:54.630 that he saw him at. Oh my gosh. And so he catches 00:44:54.630 --> 00:44:59.150 them again in a couple of weeks. Yeah. And runs 00:44:59.150 --> 00:45:01.349 into him again and like, oh, you can't believe 00:45:01.349 --> 00:45:03.449 the impact you've had on dad. And they're like, 00:45:03.489 --> 00:45:06.829 come up to the hotel room after and they're in 00:45:06.829 --> 00:45:10.650 the elevator and Ozzy's like, whoa, I can't go 00:45:10.650 --> 00:45:13.289 up without my Bible. And they're like, what? 00:45:14.039 --> 00:45:15.440 And there's like all these people because he's 00:45:15.440 --> 00:45:17.900 at like some horror convention. Yeah. And these 00:45:17.900 --> 00:45:20.900 people are like, why is Ozzy talking about a 00:45:20.900 --> 00:45:23.940 Bible? Excuse me. The Prince of Darkness is asking 00:45:23.940 --> 00:45:27.219 for his Bible. Yeah. Could somebody get the Prince 00:45:27.219 --> 00:45:30.039 of Darkness his Bible? Yeah. So he made them 00:45:30.039 --> 00:45:33.579 wait while they went back in and got his Bible 00:45:33.579 --> 00:45:38.139 to bring it up to his hotel room. Yeah. So I 00:45:38.139 --> 00:45:42.610 would have never picked Ozzy for a guy who. Was 00:45:42.610 --> 00:45:46.590 at least open to the gospel. Apparently he was. 00:45:46.730 --> 00:45:50.329 I mean, he's British, and he's always been Anglican 00:45:50.329 --> 00:45:53.030 because he's British. And now Anglican is a lot 00:45:53.030 --> 00:46:03.650 like, no, I am not trying to defraud our Anglican 00:46:03.650 --> 00:46:07.730 brothers. It's a lot like being Baptist in the 00:46:07.730 --> 00:46:12.670 South. Sure. It's a lot like being. culturally 00:46:12.670 --> 00:46:17.570 jewish okay in england anglican means you're 00:46:17.570 --> 00:46:22.570 english yeah that you have a long line of english 00:46:22.570 --> 00:46:26.030 ancestors is is what it feels like so the you 00:46:26.030 --> 00:46:28.690 know the idea that i heard a long long time ago 00:46:28.690 --> 00:46:31.690 that ozzy osbourne was a member of the anglican 00:46:31.690 --> 00:46:35.750 church didn't really surprise me um but you know 00:46:35.750 --> 00:46:38.250 when you actually listen to the like war pig 00:46:38.250 --> 00:46:44.349 is not about Anything that I feel like the church 00:46:44.349 --> 00:46:51.929 should be worried about, you know, in terms of 00:46:51.929 --> 00:46:56.849 what he's actually going after, it seemed like 00:46:56.849 --> 00:47:01.869 in his lyrics. So, I mean, I was, and he just, 00:47:01.969 --> 00:47:07.690 anybody who watched the Osbournes. You got to 00:47:07.690 --> 00:47:13.489 see the humanity of this guy. That was awesome. 00:47:14.190 --> 00:47:17.230 And I've always got a soft spot in my heart for 00:47:17.230 --> 00:47:21.530 Parkinson's victims. My grandfather had Parkinson's 00:47:21.530 --> 00:47:24.170 victims. That makes it sound like it's not a 00:47:24.170 --> 00:47:31.050 disease. Patients, Parkinson's patients. My grandfather 00:47:31.050 --> 00:47:35.809 had Parkinson's. It's hard to watch. And you 00:47:35.809 --> 00:47:38.070 just listen to him talk and you don't expect 00:47:38.070 --> 00:47:41.250 that to be the voice that's making the voice 00:47:41.250 --> 00:47:45.570 that you hear in Black Sabbath. Anyway, all that 00:47:45.570 --> 00:47:48.409 to say, that was a tough one. And then today, 00:47:48.650 --> 00:47:51.710 Hulk Hogan, my wife sent me a text. I was like, 00:47:51.789 --> 00:47:56.349 I think she sent it to me because my son is actually 00:47:56.349 --> 00:48:01.690 a little bit obsessed with Hulkamaniac. Yeah, 00:48:01.690 --> 00:48:04.050 he's Hulkamaniac. What are you going to do, brother, 00:48:04.130 --> 00:48:07.550 when Hulkamania comes down on you? On you. Oh, 00:48:07.550 --> 00:48:11.429 my gosh. But that was one of the ones, like, 00:48:11.469 --> 00:48:13.630 when I was Cade's age, when I was my son's age, 00:48:13.730 --> 00:48:17.869 like, I was. Him and Andre the Giant. Oh, my 00:48:17.869 --> 00:48:23.030 gosh. I had the two little rubber wrestling. 00:48:23.309 --> 00:48:25.570 Yes. I didn't have the ring. I wanted the ring. 00:48:26.070 --> 00:48:28.659 Ultimate Warrior. In that same time frame, yeah. 00:48:28.880 --> 00:48:33.460 A lot of Randy the Macho Man. Randy Savage Macho 00:48:33.460 --> 00:48:41.440 Man. Ric Flair. Yes. The Undertaker was always 00:48:41.440 --> 00:48:47.320 a favorite. Yes. I played the, you know, whatever 00:48:47.320 --> 00:48:50.260 the wrestling Nintendo game was. See, I would 00:48:50.260 --> 00:48:54.599 have thought growing up the son of a pastor, 00:48:54.699 --> 00:48:58.320 that would have been like. Oh, it was. I definitely 00:48:58.320 --> 00:49:01.940 didn't do this at home. Okay. Okay. This was 00:49:01.940 --> 00:49:05.840 not widely. Not a family sanctioned event. No. 00:49:06.260 --> 00:49:12.860 Okay. And the two little wrestling. Figures. 00:49:12.900 --> 00:49:19.519 Figures that I had were not purchased by my family. 00:49:19.659 --> 00:49:24.800 I'll put it that way. Okay. So. Okay. But I had 00:49:24.800 --> 00:49:28.860 Andre the Giant and Hulk. And Hulk Hogan apparently 00:49:28.860 --> 00:49:34.079 was a recent convert to Christianity, I hear. 00:49:34.239 --> 00:49:37.559 I mean, that's what it said. Him and his blonde 00:49:37.559 --> 00:49:42.820 family. Yes. So, I mean, I hope that's true. 00:49:42.940 --> 00:49:48.699 That's always the hope that we all have inside 00:49:48.699 --> 00:49:55.929 of that. But, again, you know. the persona with 00:49:55.929 --> 00:49:58.210 both of these guys, the persona, you know, larger 00:49:58.210 --> 00:50:02.550 than life and just irreverent as can be because 00:50:02.550 --> 00:50:06.449 of what it requires to be at the top of that 00:50:06.449 --> 00:50:11.949 game. And then you see them as actual human beings 00:50:11.949 --> 00:50:17.030 later on in life. And you're like, Oh yeah, I 00:50:17.030 --> 00:50:20.150 think probably could have sat down and had a 00:50:20.150 --> 00:50:22.050 beer with either one of these guys. Yeah. And 00:50:22.050 --> 00:50:25.329 then just fine. In terms of having something 00:50:25.329 --> 00:50:32.570 to connect on. Yeah. Anyway. I did see a video 00:50:32.570 --> 00:50:34.769 a long time ago of a little kid coming up to 00:50:34.769 --> 00:50:38.849 Hulk and doing the whole, like, the whole, whole 00:50:38.849 --> 00:50:44.389 spiel. And it was just amazing. I'm sure he got 00:50:44.389 --> 00:50:48.349 a kick out of it. It had to. Like, he looked 00:50:48.349 --> 00:50:50.969 like he did. I mean, he reciprocated. So it was 00:50:50.969 --> 00:50:54.409 awesome. but this little dude and i don't know 00:50:54.409 --> 00:50:56.730 if that's also because i feel like i guess with 00:50:56.730 --> 00:51:00.070 both of those guys you know they were more in 00:51:00.070 --> 00:51:03.289 my timeline and then to see younger generations 00:51:03.289 --> 00:51:10.250 interact with them is is kind of a funny thing 00:51:10.250 --> 00:51:13.369 especially since they're supposed to be so scary 00:51:13.369 --> 00:51:19.489 correct so yeah i never would have pictured ozzy 00:51:19.489 --> 00:51:23.289 as potentially having a relationship with Jesus, 00:51:23.429 --> 00:51:29.070 but perhaps he did. Perhaps he did. He sure seemed 00:51:29.070 --> 00:51:31.630 to love his family. Absolutely. And that's a 00:51:31.630 --> 00:51:35.789 beautiful thing. Absolutely, yes. That, again, 00:51:36.889 --> 00:51:41.969 is one of those. That's what I think of whenever 00:51:41.969 --> 00:51:46.489 I think of C .S. Lewis talking about there being 00:51:46.489 --> 00:51:52.289 desires in us that are beyond. What this world 00:51:52.289 --> 00:51:58.389 can provide. Yeah. Yeah, that was surprising 00:51:58.389 --> 00:52:00.690 to hear about Hulk Hogan. Sounded like it was 00:52:00.690 --> 00:52:07.070 pretty sudden. Yeah. Sad day. Yeah. Yeah, yeah, 00:52:07.070 --> 00:52:10.250 yeah. I hate to end this on a downer like that. 00:52:10.449 --> 00:52:16.340 Well, let's go to the... Cloud Flare 1 .1 .1 00:52:16.340 --> 00:52:20.739 .1. Yeah, Cloud Flare 1 .1 .1 .1. On July 14th. 00:52:20.739 --> 00:52:26.019 July 14th, folks, 2025. Not that it's uplifting 00:52:26.019 --> 00:52:28.980 to talk about an outage, but it's better than 00:52:28.980 --> 00:52:31.960 the bummer of somebody dying. A complex routing 00:52:31.960 --> 00:52:38.000 incident resulted in the unavailability. Of Cloudflare's 00:52:38.000 --> 00:52:41.579 public DNS resolver for about an hour. Let me 00:52:41.579 --> 00:52:46.880 translate that for you. We screwed up. All right. 00:52:46.940 --> 00:52:52.659 Who plugged in the loop? Yeah. I'm taking back 00:52:52.659 --> 00:52:56.280 a few years now to when the entire IT department 00:52:56.280 --> 00:53:00.539 followed Chris Kincaid to one building on our 00:53:00.539 --> 00:53:03.900 property in the middle of the summer. Yeah. It's 00:53:03.900 --> 00:53:06.960 hot. We're all sweating. We did some poor man 00:53:06.960 --> 00:53:09.679 sleuthing that day. And we just walked around 00:53:09.679 --> 00:53:14.699 this building. Until we found it. Plugging and 00:53:14.699 --> 00:53:18.440 unplugging cables. It was crazy because we had 00:53:18.440 --> 00:53:22.260 no way to kind of detect it. No. So I was like, 00:53:22.340 --> 00:53:26.500 okay, so. I mean, this is over a decade ago. 00:53:26.760 --> 00:53:30.619 Yeah. So we pulled the plug on the site -to -site 00:53:30.619 --> 00:53:33.380 T1. Yeah. Which was the Ranch Timbers Bluffs 00:53:33.380 --> 00:53:35.500 and Shores. Right. It didn't stop. It was like, 00:53:35.519 --> 00:53:37.800 okay, so we can eliminate those properties. They're 00:53:37.800 --> 00:53:42.139 fine. Pull the towers. Nope. It's in the woods. 00:53:42.260 --> 00:53:43.679 It's got to be the woods because you pull the 00:53:43.679 --> 00:53:45.059 woods and you're like, boom, it's immediately 00:53:45.059 --> 00:53:46.860 gone. It's like, all right, it's definitely at 00:53:46.860 --> 00:53:48.739 the woods. And we could have, like, honestly, 00:53:48.820 --> 00:53:52.539 though, it was at the woods. It was at the woods. 00:53:52.559 --> 00:53:57.260 Everybody knew it was at the woods. So get to 00:53:57.260 --> 00:54:00.159 the woods and you start disconnecting individual 00:54:00.159 --> 00:54:04.199 buildings until it's like. Oh, it's in the media. 00:54:04.340 --> 00:54:07.000 It's at the Mr. T. Of course it's in the media 00:54:07.000 --> 00:54:08.239 department. And then you're running around the 00:54:08.239 --> 00:54:10.000 Mr. T trying to find it. And I don't remember 00:54:10.000 --> 00:54:13.360 who found it. It wasn't me. But somebody found 00:54:13.360 --> 00:54:18.539 where a singular network cable, both ends were 00:54:18.539 --> 00:54:22.019 plugged into the same switch. And this is before 00:54:22.019 --> 00:54:25.320 we had the ability to have switches that could 00:54:25.320 --> 00:54:28.079 eliminate these problems. Yeah, these were. Very 00:54:28.079 --> 00:54:30.619 dumb switches. Yeah, they were. And it was just 00:54:30.619 --> 00:54:33.960 repeating the fire out of whatever. Oh, man, 00:54:33.980 --> 00:54:38.940 the bridge loop was, oh. It was, there was, yes. 00:54:39.360 --> 00:54:41.400 The force was strong in that bridge loop. Like, 00:54:41.440 --> 00:54:43.760 okay, all the phones are down. What happened? 00:54:43.820 --> 00:54:46.219 Okay, now we can't do anything. What's going 00:54:46.219 --> 00:54:52.019 on? Mm -hmm. And as soon as you unplug one end, 00:54:52.519 --> 00:54:55.500 boom. Everything's fine. It was an immediate 00:54:55.500 --> 00:54:59.429 change. Yeah. And I was just like, guys, let's 00:54:59.429 --> 00:55:03.130 not do that again. If you just see a random cable 00:55:03.130 --> 00:55:05.929 and one end is unplugged. Plug it in. Don't plug 00:55:05.929 --> 00:55:08.949 it in. You don't know. If you don't know what 00:55:08.949 --> 00:55:10.889 you're doing, don't act like you know what you're 00:55:10.889 --> 00:55:16.510 doing. Correct. Oof. Yeah, so this one was very 00:55:16.510 --> 00:55:20.789 much they screwed up. Yeah. I don't know. This 00:55:20.789 --> 00:55:23.389 was caused by an internal configuration error 00:55:23.389 --> 00:55:29.269 and not. A BGP hijack. Yeah. And they reference 00:55:29.269 --> 00:55:32.989 Anycast, which is intriguing because I tend to 00:55:32.989 --> 00:55:38.570 link Anycast with IPv6. Okay. Not so much IPv4. 00:55:39.969 --> 00:55:45.250 So I found that intriguing. Mm -hmm. And I'm 00:55:45.250 --> 00:55:46.769 not surprised that they would be trying to leverage 00:55:46.769 --> 00:55:49.750 IPv6 because eventually they'll need to get there. 00:55:50.210 --> 00:55:54.190 Yeah. So, yeah, somebody didn't test their... 00:55:54.519 --> 00:55:57.239 Config changes well. Yeah, I will tell you, we 00:55:57.239 --> 00:56:00.539 had a similar, not a similar, because it's not 00:56:00.539 --> 00:56:09.739 nearly as big, but the same type of IPv6. So 00:56:09.739 --> 00:56:16.000 Wi -Fi 6, I think even though we're at Wi -Fi 00:56:16.000 --> 00:56:20.719 7, is still not used by a lot of different people. 00:56:20.960 --> 00:56:27.500 Yep. And so Wi -Fi. Six has some security options 00:56:27.500 --> 00:56:31.780 that if you're not careful with the way you do 00:56:31.780 --> 00:56:35.760 your configurations on your network can cause 00:56:35.760 --> 00:56:41.639 some issues with older devices. Yep. I think 00:56:41.639 --> 00:56:45.139 that's what happened to us that one day that 00:56:45.139 --> 00:56:53.150 I got in trouble for. certain Wi -Fi devices 00:56:53.150 --> 00:56:56.269 not connecting when they should have. So were 00:56:56.269 --> 00:57:00.409 you doing stuff with WPA3? I didn't mean to. 00:57:00.610 --> 00:57:05.289 Okay. Okay. But in trying to fix the endpoint 00:57:05.289 --> 00:57:10.610 issue we were having with that one AP, I think 00:57:10.610 --> 00:57:16.769 that I caused a problem. Oh, yeah. So. Okay. 00:57:17.130 --> 00:57:20.570 Just not letting too much out of the bag there, 00:57:20.690 --> 00:57:25.079 but. I know for sure it can be kind of a tricky 00:57:25.079 --> 00:57:29.579 thing in trying to understand some of the new 00:57:29.579 --> 00:57:34.679 configuration that's necessary. What's great 00:57:34.679 --> 00:57:41.219 about 6 and 7 is this ability to do higher -end 00:57:41.219 --> 00:57:46.940 security, but it doesn't work with any of the 00:57:46.940 --> 00:57:50.480 older devices. No. So we've got to wait. Yeah, 00:57:50.519 --> 00:57:53.179 you got to let all of it. Well, yeah, I guess 00:57:53.179 --> 00:57:56.280 what you've got is you could make sure that all 00:57:56.280 --> 00:57:59.900 of your church -owned devices can support it. 00:57:59.980 --> 00:58:01.820 Yeah, they can. And then you can move staff. 00:58:02.019 --> 00:58:06.320 Yeah. But then you'd have to leave gas backwards. 00:58:06.719 --> 00:58:09.480 Yeah. Because you can't guarantee that everybody 00:58:09.480 --> 00:58:11.260 coming to the church on a Wednesday or a Sunday. 00:58:11.260 --> 00:58:14.679 Remember, we didn't get to spend all of the money 00:58:14.679 --> 00:58:18.539 that we had asked for. No. So there's a lot of 00:58:18.539 --> 00:58:20.869 devices that aren't. capable of doing that. Two 00:58:20.869 --> 00:58:23.869 consecutive budgets, right? Yeah. Yeah. Okay. 00:58:23.989 --> 00:58:26.849 Yeah, I mean, that happens. Two and a half. Two 00:58:26.849 --> 00:58:28.469 and a half. And I'm supposed to have my new budget 00:58:28.469 --> 00:58:30.730 ready. Oh, we need to talk about that when we 00:58:30.730 --> 00:58:34.550 get off the show. Okay. I need to have that in 00:58:34.550 --> 00:58:39.969 the next six days. Okay. Okay. Now, I will say. 00:58:40.329 --> 00:58:42.250 Just talking a little business here on the podcast. 00:58:42.429 --> 00:58:47.150 Yeah. Since, and I hate to say this as a Microsoft 00:58:47.150 --> 00:58:52.880 guy. Yeah. But since we stopped leveraging Windows 00:58:52.880 --> 00:58:56.280 servers for DNS, it seems to have fixed some 00:58:56.280 --> 00:59:01.519 of the issues, which is intriguing. I want to 00:59:01.519 --> 00:59:05.139 understand why. Well, sure. Because DNS should 00:59:05.139 --> 00:59:08.480 just simply be DNS. Right. And I also understand 00:59:08.480 --> 00:59:12.440 that a ton of problems on a network generally 00:59:12.440 --> 00:59:16.980 point to DNS. Right. So I would love to know. 00:59:17.840 --> 00:59:22.260 Why dropping Windows DNS and using the internal 00:59:22.260 --> 00:59:25.900 DNS of the unified gear seems to have fixed the 00:59:25.900 --> 00:59:29.900 problem with that U7 access point. Yeah, that 00:59:29.900 --> 00:59:37.739 makes sense. All right. Sounds like we have something 00:59:37.739 --> 00:59:41.579 to talk about when we wrap up. We don't have 00:59:41.579 --> 00:59:45.820 a boost. No, there's no boost. Jason, I mean, 00:59:45.860 --> 00:59:48.829 I've been on vacation. Where have you been? We 00:59:48.829 --> 00:59:51.809 praised you on the previous episode. Especially 00:59:51.809 --> 00:59:54.610 since you said such nice things. Yes. Holy cow. 00:59:54.809 --> 00:59:58.829 Now we have to chastise you again. And you looked 00:59:58.829 --> 01:00:01.289 in the right place this time. I did. So it's 01:00:01.289 --> 01:00:06.150 not our fault. No. We didn't overlook it. Anyway. 01:00:06.349 --> 01:00:10.670 Should probably give my current boss a hard time, 01:00:10.730 --> 01:00:12.409 too, because I think he still listens. Listen, 01:00:12.530 --> 01:00:22.619 Michael. Figure out how SATs work. Yes. Let me 01:00:22.619 --> 01:00:26.739 tell you what app to use. Yeah, y 'all need to 01:00:26.739 --> 01:00:32.619 be using Podcast 2 .0. 2 .0. Fountain's a good 01:00:32.619 --> 01:00:38.239 one. Crosses iOS and Android. Yeah, it is. Fountain 01:00:38.239 --> 01:00:43.880 .fm? Mm -hmm. Castamatic is a good one again. 01:00:44.409 --> 01:00:47.530 If you're on iOS. What was the other one that 01:00:47.530 --> 01:00:51.250 we did or that I was looking at? I don't think 01:00:51.250 --> 01:00:54.590 it was. This was when we were trying to figure 01:00:54.590 --> 01:00:57.090 out the live stuff that I was looking at all 01:00:57.090 --> 01:01:02.809 these other ones. On the Android side, I like 01:01:02.809 --> 01:01:05.730 Podcast Addict. Podcast Addict. That's the one 01:01:05.730 --> 01:01:08.469 that you were talking about. Yeah. And that's 01:01:08.469 --> 01:01:10.489 when I found out that it was Android. Android 01:01:10.489 --> 01:01:12.010 only. Yeah, of course. I have an Android phone. 01:01:12.440 --> 01:01:16.380 And thanks for that. Podcast Guru is another 01:01:16.380 --> 01:01:20.260 good one if you have Android. Okay. Technically, 01:01:20.360 --> 01:01:23.300 that live stream is successful in what I did. 01:01:25.699 --> 01:01:32.860 But your app has to support .m3u. Oh, my gosh. 01:01:33.360 --> 01:01:39.280 And not be looking for .m3u8, which also translates 01:01:39.280 --> 01:01:44.460 to HLS. which is more video driven, but we just 01:01:44.460 --> 01:01:47.679 want the audio side. So I've got to figure out 01:01:47.679 --> 01:01:53.639 the HLS piece to see, can I run something internally 01:01:53.639 --> 01:01:59.820 or would it require something in the cloud? Yeah, 01:01:59.880 --> 01:02:02.420 that's interesting. So, but it was a six, it 01:02:02.420 --> 01:02:06.280 was success. I was able to listen to myself in 01:02:06.280 --> 01:02:10.059 a, about a 10 second delay on my phone, which 01:02:10.059 --> 01:02:14.139 was amazing. So set up that ice cast server was 01:02:14.139 --> 01:02:18.360 using, but with two Ts to talk to ice cast and 01:02:18.360 --> 01:02:22.019 then it going out. So that, that was, that was 01:02:22.019 --> 01:02:23.659 cool to be able to just throw that off on an 01:02:23.659 --> 01:02:28.340 old Dell PC that I had and had it running on 01:02:28.340 --> 01:02:32.380 windows, had it running on Linux as well. And 01:02:32.380 --> 01:02:34.340 it was like, this is amazing. But unfortunately 01:02:34.340 --> 01:02:38.460 ice cast doesn't run what these apps are mostly 01:02:38.460 --> 01:02:41.570 looking for. Really? Because they all want the 01:02:41.570 --> 01:02:46.849 M3U8. Because apparently M3U is more of a playlist 01:02:46.849 --> 01:02:54.570 where the M3U8 is that HLS stream. Yeah, that's 01:02:54.570 --> 01:02:58.110 definitely better for life. So once I get the 01:02:58.110 --> 01:03:01.809 flooring done, since my wife is out of town, 01:03:01.929 --> 01:03:05.010 I want to try to figure out the M3U8 HLS option. 01:03:05.710 --> 01:03:10.599 I don't know how far I'll get into it. Oh, the 01:03:10.599 --> 01:03:15.980 chips. Members mark, baby. Spared no expense. 01:03:17.420 --> 01:03:20.519 Spared all the expense. Yeah, and if you've been 01:03:20.519 --> 01:03:23.639 hearing me crunch on the pretzels, they are great 01:03:23.639 --> 01:03:27.719 value, but they're pretty good to me. Mini pretzel 01:03:27.719 --> 01:03:30.980 twists. Sometimes you got to go budget to get 01:03:30.980 --> 01:03:34.239 the stuff that you actually want. To get the 01:03:34.239 --> 01:03:36.639 good beer? To get the good beer. Yeah. Oh, my 01:03:36.639 --> 01:03:40.329 gosh. Alright, thanks for hanging out. Yeah, 01:03:40.329 --> 01:04:19.940 I enjoyed it. See you, everybody. When I first 01:04:19.940 --> 01:04:22.940 started college, when I went running, after five 01:04:22.940 --> 01:04:24.800 minutes I started feeling a burning in my chest. 01:04:25.039 --> 01:04:29.119 And it was just me sucking in soot and smog. 01:04:30.659 --> 01:04:35.099 The smog was so bad, it was like you might die.