WEBVTT 00:00:11.471 --> 00:00:16.191 Hello, friends, and welcome back to your weekly Linux talk show. My name is Chris. 00:00:16.411 --> 00:00:17.131 My name is Wes. 00:00:17.311 --> 00:00:18.191 And my name is Brent. 00:00:18.811 --> 00:00:22.871 Hello, gentlemen. Coming up on the show today, we're finally doing something 00:00:22.871 --> 00:00:24.211 we've wanted to do for years. 00:00:24.351 --> 00:00:29.991 In episode 650, we're going on-site, and we're fixing a network and rebuilding 00:00:29.991 --> 00:00:31.671 it with Linux at the core. 00:00:31.831 --> 00:00:34.511 Then, of course, we've got some great feedback, some great picks, 00:00:34.671 --> 00:00:36.391 and some fantastic boosts. 00:00:36.431 --> 00:00:39.891 All that is coming up later on in the show. But before we get to that, 00:00:40.011 --> 00:00:43.391 let's say hello to our virtual lug who's live with us right now. 00:00:43.571 --> 00:00:45.231 Time appropriate. Greetings, Mumble Room. 00:00:46.432 --> 00:00:48.372 Hello, Brent. 00:00:48.732 --> 00:00:49.672 Oh, hello, gang. 00:00:49.952 --> 00:00:50.592 Hello, guys. 00:00:50.732 --> 00:00:51.752 Thanks for joining us. 00:00:52.132 --> 00:00:55.572 Everyone up there in the quiet listening, too. The Mumble Room's always a-rockin' 00:00:55.632 --> 00:00:58.052 on a Sunday, which is a Tuesday but on a Sunday. 00:00:58.452 --> 00:01:01.572 And you can get details at jupiterbroadcasting.com slash mumble. 00:01:01.992 --> 00:01:05.372 And a big good morning to our friends at Defined Networking. 00:01:05.452 --> 00:01:10.392 Go to defined.net slash unplugged and meet Managed Nebula from Defined Networking. 00:01:10.552 --> 00:01:14.692 It's a decentralized VPN that is built from an open source project. 00:01:14.692 --> 00:01:16.772 The entire thing is open source. 00:01:17.112 --> 00:01:21.152 And as I was building out a network using this recently, what really, 00:01:21.252 --> 00:01:25.612 really is nice is you don't need anyone else's permission to provision a system. 00:01:25.612 --> 00:01:27.712 It's not somebody else's control plane. 00:01:27.972 --> 00:01:31.512 Everything is under your control. And if you want something turnkey, 00:01:31.692 --> 00:01:33.052 they have managed Nebula. 00:01:33.412 --> 00:01:38.252 It's such a nice mix between the two. And if you go to define.net slash unplugged, 00:01:38.292 --> 00:01:41.432 you can sign up for 100 devices for free, no credit card required, 00:01:41.452 --> 00:01:44.112 and try it out. This would be a great way for like your home lab, 00:01:44.392 --> 00:01:45.532 you know, experiment with this. 00:01:45.672 --> 00:01:48.212 And then when it comes time to the enterprise, you can own it from the ground 00:01:48.212 --> 00:01:51.852 up and you can watch where the project's going just by paying attention to their GitHub. 00:01:52.072 --> 00:01:56.332 And there are some fantastic features nobody else is doing coming down the pipe. 00:01:57.212 --> 00:02:00.712 Very excited about the future. And I think it's a great time to try it out. 00:02:00.852 --> 00:02:04.352 So this is what I'm building on now because I want to own the entire stack, everything. 00:02:04.612 --> 00:02:07.472 And I don't want to have any big tech between me and my network. 00:02:07.712 --> 00:02:11.512 And I can trust that Defined is focused on building these things out. 00:02:11.512 --> 00:02:13.872 But, you know, it's been around since 2007, Nebula has. 00:02:14.072 --> 00:02:19.052 It was built for Slack, had to be good from day one, and now it's just everywhere. 00:02:19.152 --> 00:02:23.772 It's in places you would never expect, like vehicles going down the road right now. 00:02:23.932 --> 00:02:28.812 It's top, high-end, production-ready, on-the-road stuff, and you can use it. 00:02:28.892 --> 00:02:31.872 Defined.net slash unplugged. Go check out Nebula. 00:02:32.112 --> 00:02:36.452 It is that good. That's what we're using. And a big thank you to Defined for 00:02:36.452 --> 00:02:37.532 sponsoring the Unplugged program. 00:02:37.732 --> 00:02:40.332 Defined.net slash unplugged. 00:02:43.398 --> 00:02:47.558 48 days remain until Planet Nix and Scale 23. 00:02:47.678 --> 00:02:48.038 Oh, boy. 00:02:48.138 --> 00:02:50.198 That's not enough days. I don't like this. 00:02:51.098 --> 00:02:52.618 I'm excited. Yeah, Brent, you're behind. 00:02:52.718 --> 00:02:53.718 I got to get the van in shape. 00:02:54.858 --> 00:03:00.598 Yes, you do. We have a promo code, Unpludge, U-N-P-L-G. You'll get 40% off your Scale tickets. 00:03:00.858 --> 00:03:03.958 And that's what you got to do, right? Go sign up for Scale. And then you can 00:03:03.958 --> 00:03:05.918 just attend Planet Nix. I mean, go sign up, too. 00:03:06.138 --> 00:03:09.578 Yeah. I think we're probably going to have a meetup on Friday or Saturday. 00:03:10.438 --> 00:03:13.058 We haven't locked that in yet, but I think it's going to happen. 00:03:13.398 --> 00:03:17.698 And this is one of the big events in North America around free software. 00:03:17.898 --> 00:03:20.938 And one of the things they do is they have these tracks, like Planet Nix, and there are others. 00:03:21.098 --> 00:03:25.078 We are partial to Planet Nix, but there's some benefit to focused tracks as 00:03:25.078 --> 00:03:27.198 well, which you might want to look into. There are other ones. 00:03:27.338 --> 00:03:32.358 The dates to remember are March 5th through the 6th in Pasadena, California. 00:03:33.378 --> 00:03:36.418 And then shortly— They always also have great Postgres talks, okay? 00:03:36.618 --> 00:03:40.918 They do. They have a great Postgres community there. We also have LinuxFest 00:03:40.918 --> 00:03:43.598 Northwest coming up just around the corner as well. That's in April. 00:03:44.038 --> 00:03:48.558 But before we get that far, we would really like to have swag this year. 00:03:48.718 --> 00:03:52.218 And none of us are really great at this, but we would love to have something 00:03:52.218 --> 00:03:55.578 by scale, but definitely for LinuxFest Northwest. So we're putting a call out 00:03:55.578 --> 00:04:00.598 for ideas to the audience for a shirt, maybe something to do with Linux Tuesday on a Sunday. 00:04:01.438 --> 00:04:04.798 You know, anything you could think of from the show that might make a great 00:04:04.798 --> 00:04:07.558 shirt. Send them to unplugged at jupiterbroadcasting.com. 00:04:08.391 --> 00:04:09.731 Or maybe tag one of us in Matrix. 00:04:10.071 --> 00:04:10.731 Yeah, you can tag me in the Matrix. 00:04:11.111 --> 00:04:14.051 Thank you, Wes. He's taking one for the team there. 00:04:15.531 --> 00:04:18.271 And let us know. And we'll work with you. Like, we'll kick a little back to 00:04:18.271 --> 00:04:20.851 you or something. I don't know what, you know, because we'll see how they sell. 00:04:20.931 --> 00:04:22.891 But we'll work with you and thank you for it. 00:04:22.971 --> 00:04:25.291 And we'd love to have something great pretty quick. 00:04:26.011 --> 00:04:29.891 So unplugged at jupiterbroadcasting.com where you can tag Mr. Wes. 00:04:31.091 --> 00:04:33.471 And come up with a fun idea for the show, something that makes you think about 00:04:33.471 --> 00:04:37.471 the show. Because why we love these is not only could it be a way to help cover 00:04:37.471 --> 00:04:41.951 some of the costs of the show during the event, but it really makes it easy to find each other. 00:04:42.471 --> 00:04:45.491 And that makes the conversation real smooth. 00:04:45.711 --> 00:04:48.111 You've got an opener right there. Hey, you listen to the show. 00:04:48.331 --> 00:04:52.111 And it makes the networking aspect of that for those of us that are not particularly 00:04:52.111 --> 00:04:55.051 great at the conversation starting that much smoother. 00:04:55.151 --> 00:05:01.091 And also means for the boys, we can see in the audience who's there from the show. 00:05:01.191 --> 00:05:04.251 And it makes it easier for us to find people. And we don't have to have that 00:05:04.251 --> 00:05:07.151 awkward conversation of, have you listened to my podcast before? 00:05:07.411 --> 00:05:12.031 Well, and we feel more, you know, secure because we know we have reinforcements right there. 00:05:12.911 --> 00:05:17.971 Call the army. So we'd love a great swag idea. Shoot them over to us, 00:05:18.051 --> 00:05:19.691 unpluggedjupiterbroadcasting.com. 00:05:19.851 --> 00:05:21.651 You never know. We might just use it. 00:05:24.871 --> 00:05:28.271 Well, something we fancy ourselves doing is going out to listeners' businesses, 00:05:28.651 --> 00:05:33.091 their friend's place, or I don't know, their family's businesses, maybe even home labs. 00:05:34.031 --> 00:05:35.671 Maybe Airbnbs we stay at. 00:05:35.711 --> 00:05:38.991 Nope, that's a great idea, actually. We should fix up people's, 00:05:39.071 --> 00:05:41.431 oh my God, we should fix up people's Airbnbs. 00:05:41.531 --> 00:05:41.931 Yes. 00:05:42.351 --> 00:05:43.371 They're probably pretty bad. 00:05:43.491 --> 00:05:48.011 We have practice. So basically helping people with their home network setups, 00:05:48.251 --> 00:05:52.931 business network setups, Airbnb network setups, everything from Wi-Fi to storage, 00:05:53.091 --> 00:05:55.331 find those pain points and solve them all. 00:05:55.531 --> 00:05:58.691 With, of course, you know, as we do, as much Linux as possible. 00:05:58.691 --> 00:06:03.531 And to get our sea legs, we started local, quite local. 00:06:04.636 --> 00:06:10.156 Yeah, in fact, not long ago, my wife moved to clinics, and her tech setup has been rough ever since. 00:06:10.256 --> 00:06:14.636 And I have been like the shoemaker here where my wife's tech setup is abysmal. 00:06:15.476 --> 00:06:15.876 Embarrassing. 00:06:16.336 --> 00:06:19.416 And I've been meaning to get to it, meaning to get to it. And I thought, 00:06:19.516 --> 00:06:21.216 this is our chance right here. 00:06:21.276 --> 00:06:24.376 Let's dip our toes and figure out what's going on. 00:06:24.456 --> 00:06:27.336 And I knew immediately there was a couple of items we had to bang off. 00:06:27.436 --> 00:06:35.396 Like, she's using a MiFi from AT&T for some of this, and it's an LTE 4G thing. Not even 5G. 00:06:35.476 --> 00:06:38.376 Yeah, and not just as the upstream, like as the entire network. 00:06:38.436 --> 00:06:39.436 Oh, my goodness. 00:06:39.676 --> 00:06:45.596 Yeah, it's bad. And then she has no local storage. So let's just say the backup situation is bad. 00:06:46.056 --> 00:06:48.556 And the Wi-Fi situation is bad. 00:06:49.776 --> 00:06:52.876 Thankfully, though, you know, we didn't have to start from total scratch because 00:06:52.876 --> 00:06:58.936 she did have some hardware, obviously that Wi-Fi, but also a potential server, 00:06:59.196 --> 00:07:03.776 a Geekom IT13 Mini PC 2026. 00:07:04.396 --> 00:07:06.936 from their mini Air series line. 00:07:07.136 --> 00:07:07.956 That thing's cool. 00:07:08.236 --> 00:07:16.496 Yeah, 13th gen Intel i5, 13600H, 16 gigs of DDR4 RAM, 1 terabyte SSD. 00:07:16.916 --> 00:07:19.636 I guess it came with a Windows 11 Pro. Is that right? 00:07:19.636 --> 00:07:21.396 Did you see that? I never even booted it, dude. 00:07:21.596 --> 00:07:25.016 Okay, good. It was already rebooted into the Nix OS installer by the time I arrived. 00:07:26.016 --> 00:07:26.976 Did not buy it. 00:07:26.976 --> 00:07:33.416 It's got two USB 4.0s up to 40 gigabit per second, 8K quad display support, 00:07:33.416 --> 00:07:37.836 Wi-Fi 6E, an SD card slot, up to two disk possible. 00:07:38.036 --> 00:07:43.916 You can have a 2.5 SATA SSD, and there's also an M.2 slot in there. Total price was $600. 00:07:44.436 --> 00:07:47.136 Yeah, so not the cheapest, but also when you think not... 00:07:47.806 --> 00:07:51.186 What it can do, not that bad. You know, you get a more modern gen, 00:07:51.806 --> 00:07:55.066 cheap, low power, cool Intel processor. 00:07:55.666 --> 00:08:00.446 And I think the big thing for us was Wi-Fi 6E in there, two storage slots. 00:08:00.866 --> 00:08:04.746 And this also has been blessed by folks in the Home Assistant community as a 00:08:04.746 --> 00:08:07.326 good Home Assistant server. And we'll get to that. 00:08:07.486 --> 00:08:11.726 Great size too. I mean, just lovely form factored, felt pretty premium, good product. 00:08:11.846 --> 00:08:16.566 It's really a successor to the NUC. It really, truly is a successor to the NUC. 00:08:16.566 --> 00:08:20.326 and it's a good little box and just right out of the box, great compatibility 00:08:20.326 --> 00:08:21.946 with Linux and that's what we needed. 00:08:22.166 --> 00:08:26.206 So then on the Wi-Fi side, we're going to move her from, I had this set up for 00:08:26.206 --> 00:08:29.526 originally, but then she moved clinics and I'm going to put it back into action for her. 00:08:29.606 --> 00:08:35.946 And so it's the OpenWRT1. We already had this and in fact, it was partially already set up. 00:08:36.246 --> 00:08:41.006 And so this was just an obvious go-to to move her Wi-Fi clients over to this 00:08:41.006 --> 00:08:43.506 instead of a Wi-Fi. So this is the hardware we brought. 00:08:43.666 --> 00:08:46.026 We had this NUC killer, essentially. 00:08:46.566 --> 00:08:51.006 We had the OpenWRT1 little blue box, the little physical hardware box, 00:08:52.126 --> 00:08:57.006 and a few other items that you might find to be a little surprising. 00:08:57.006 --> 00:09:00.866 Did you catch on the parts list here what else I brought? 00:09:02.266 --> 00:09:08.066 I'm looking here. So, well, I see a Zigbee radio. 00:09:08.386 --> 00:09:10.766 I thought you were a Z-Wave guy. 00:09:11.486 --> 00:09:13.066 I am a pretty big Z-Wave stan. 00:09:13.566 --> 00:09:14.846 What's going on here then? 00:09:15.826 --> 00:09:16.346 Traitor. 00:09:16.566 --> 00:09:18.786 You keep recommending things to me and then changing your mind? 00:09:18.966 --> 00:09:21.206 Is this back to the don't do as I do thing? 00:09:21.306 --> 00:09:25.766 It is. Yeah, it is. Yeah, call the launch. Well, so this, Zigbee's the right 00:09:25.766 --> 00:09:27.046 tool for the job on this one. 00:09:28.226 --> 00:09:32.126 This she already owned as well. It's a Sonoff Zigbee USB dongle. 00:09:32.846 --> 00:09:37.006 And it's a nice little dongle, really good reputation. If she was purchasing 00:09:37.006 --> 00:09:40.726 it today, I would have had her get the Home Assistant Connect ZBT2, 00:09:40.726 --> 00:09:43.706 which is their nice new Zigbee dongle. 00:09:44.706 --> 00:09:49.626 But her clinic isn't particularly large, and I think the coverage is going to be good. 00:09:49.646 --> 00:09:54.306 And the Sonoff dongle has an antenna that sticks out and goes up a bit, 00:09:54.326 --> 00:09:55.646 so you get away from the machine piece. 00:09:56.606 --> 00:09:58.406 Yeah, all you had to do, we just had to plug it into the back, 00:09:58.526 --> 00:10:00.806 and it showed right up on Linux. It was ready to go. 00:10:00.946 --> 00:10:05.826 Yeah. And the nice thing this will enable is she'll have control surfaces around 00:10:05.826 --> 00:10:08.506 the clinic for different lighting and music. 00:10:09.026 --> 00:10:12.406 Yeah, and like cleaning mode, just turn everything up bright and stuff like 00:10:12.406 --> 00:10:16.646 that. And so those will be Zigbee buttons because they're low power and they're low cost. 00:10:16.806 --> 00:10:23.326 And then the other thing that we brought is the rather infamous speakers from 00:10:23.326 --> 00:10:25.666 Ikea that have Sonos guts in them. 00:10:25.806 --> 00:10:26.806 The Symphonisk. 00:10:27.026 --> 00:10:31.766 Yeah. And these are killer. And I had her pick a couple of these up while they were still for sale. 00:10:31.866 --> 00:10:36.126 You can still find them in some places because you essentially get a $300, 00:10:36.566 --> 00:10:42.166 $400 speaker or more in a $150, $180 speaker package. 00:10:42.886 --> 00:10:47.226 And it integrates perfectly with Home Assistant using the Sonos integration, 00:10:47.226 --> 00:10:49.306 and you can control everything over the LAN. 00:10:49.966 --> 00:10:51.266 Which, I mean, just seems ideal. 00:10:51.506 --> 00:10:55.266 I'm hoping no Sonos app required. And so that'll be how she does some of the, 00:10:55.306 --> 00:10:58.006 you know, like the wait music or the whatever music she wants to play. 00:10:58.066 --> 00:11:00.266 I don't know, but she'll do it through these speakers throughout the office. 00:11:00.426 --> 00:11:03.286 Sadly, as we're about to get into, that was sort of, you know, 00:11:03.526 --> 00:11:06.326 one of the end goals. Sort of the nice, I'll go get to play with the fun new 00:11:06.326 --> 00:11:07.586 speakers and set those up. 00:11:07.726 --> 00:11:08.546 We didn't quite get there. 00:11:08.646 --> 00:11:08.846 No. 00:11:09.006 --> 00:11:11.046 No, no, we did not. No, we did not. 00:11:11.786 --> 00:11:15.106 Well, Friday morning you guys were planning to roll up to the clinic and I would 00:11:15.106 --> 00:11:20.106 imagine your first priority was to ask Adia what her top issues were? 00:11:21.404 --> 00:11:24.164 It's a network makeover day, so I thought I should get from you, 00:11:24.404 --> 00:11:27.724 what are your top three or so pain points that you're having right now? 00:11:28.244 --> 00:11:31.904 Well, mostly that I just have to slow down because my internet's inconsistent. 00:11:32.484 --> 00:11:36.724 I just don't have access to, well, it feels like I'm on dial-up, 00:11:36.824 --> 00:11:39.324 which is no good. And then sometimes your printer drops off the network? 00:11:39.544 --> 00:11:42.304 Yeah, and then I've got to go search for wherever it is. 00:11:42.684 --> 00:11:49.804 I suppose it doesn't change where it is. But because my iPad will just switch 00:11:49.804 --> 00:11:53.584 from whatever network it can get on, I go to print from it, and it's not on 00:11:53.584 --> 00:11:55.244 the same network, and then I... 00:11:55.244 --> 00:11:58.584 Yeah, and the fact that your network is switching on the iPad suggests that 00:11:58.584 --> 00:12:01.964 the iPad's determined that there's no Internet available on your main Wi-Fi. 00:12:02.064 --> 00:12:04.504 And it's like, oh, I have this one saved, so I'll just switch to that. 00:12:05.084 --> 00:12:08.004 So that's definitely something we'll take a look at to see if we can't get that 00:12:08.004 --> 00:12:10.764 more consistent. We brought some hardware that I think could solve that. 00:12:12.144 --> 00:12:17.424 And I think that's job one. And then job two is I know you have lights and speakers 00:12:17.424 --> 00:12:18.844 that we need to get working. 00:12:19.144 --> 00:12:23.904 It would probably be good to move out of the 90s because I've been using a physical 00:12:23.904 --> 00:12:25.944 CD player. So I think we'll do home assistant for that job. 00:12:26.144 --> 00:12:28.284 All right. You're familiar with that. I'm familiar with that. 00:12:28.324 --> 00:12:29.944 So that should be fine. Office assistant. 00:12:30.544 --> 00:12:32.484 Yeah, we'll call it office. That's a good name for it. Clinic assistant. 00:12:32.684 --> 00:12:34.344 Office assistant. That's what I'll name it. Okay. 00:12:35.824 --> 00:12:39.144 Little did we know the Wi-Fi would be, and the networking in general, 00:12:39.364 --> 00:12:43.164 would be such a challenge. So that's where we had to start, and that's where 00:12:43.164 --> 00:12:44.084 we spent a good amount of time. 00:12:47.352 --> 00:12:51.932 1Password.com slash unplugged. That is the number one, then password, 00:12:52.152 --> 00:12:53.452 and unplugged, all lowercase. 00:12:53.732 --> 00:12:57.012 You know, I know this one to be true. It's easy to assume that being small means 00:12:57.012 --> 00:12:58.152 that you're flying under the radar. 00:12:58.392 --> 00:13:02.952 The reality is, small businesses are being targeted more and more by bad actors these days. 00:13:03.432 --> 00:13:07.852 Cyber criminals know that a lean, mean team often means they lack resources 00:13:07.852 --> 00:13:09.392 to prevent or respond to a breach. 00:13:09.972 --> 00:13:13.272 In short, the bad news is a team of any size can be a target. 00:13:13.272 --> 00:13:17.832 But the good news is even the smallest team can actually foil cybercrime. 00:13:18.212 --> 00:13:21.932 OnePassword provides the simplest security to help small teams manage the number 00:13:21.932 --> 00:13:24.492 one risk that bad actors exploit, weak passwords. 00:13:24.792 --> 00:13:28.612 And OnePassword provides a centralized management to make sure your company's logins are secure. 00:13:28.812 --> 00:13:32.232 It's simple. It's a turnkey solution that can be rolled out in hours, 00:13:32.232 --> 00:13:34.892 whether you have a dedicated IT staff or not. 00:13:35.052 --> 00:13:40.052 And the reality is the earlier you start, the easier it is to build your business on a secure foundation. 00:13:40.632 --> 00:13:44.412 Compromised passwords are the number one way bad actors attack companies. 00:13:44.572 --> 00:13:48.592 So a password manager really should be the first security purchase you make for your team. 00:13:49.132 --> 00:13:52.412 And on a small team, often security just defaults to one employee. 00:13:52.672 --> 00:13:56.532 Somebody who's already juggling other functions and they just happen to probably be the most tech savvy. 00:13:56.792 --> 00:14:00.252 And really the most effective thing they could do, and it's a security solution 00:14:00.252 --> 00:14:03.772 for everyone, is an intuitive and user-friendly password manager. 00:14:03.932 --> 00:14:06.512 One that everyone at your company can and will use. 00:14:07.132 --> 00:14:11.252 That's something I have seen with 1Password. above and beyond everywhere else, 00:14:11.392 --> 00:14:12.912 every other thing that I have seen. 00:14:13.132 --> 00:14:16.492 In a team, when you roll out 1Password, they use it, it sticks. 00:14:16.792 --> 00:14:19.812 And I think it's, honestly, it's the intuitive design, it's the integration 00:14:19.812 --> 00:14:24.512 with the OS and the applications, it's the range and availability of apps on different platforms. 00:14:24.792 --> 00:14:30.532 It just meets the users where they're at, but it has the management functionality a growing team needs. 00:14:31.032 --> 00:14:34.752 And those are results I've seen for years. So take the first step to better 00:14:34.752 --> 00:14:36.692 security by securing your team's credentials. 00:14:36.852 --> 00:14:42.312 Find out more. Go to 1password.com slash unplugged and start securing every login. 00:14:42.472 --> 00:14:48.352 You go there, support the show, and learn more. That's the number 1password.com slash unplugged. 00:14:51.662 --> 00:14:56.242 Well, you heard the client. We got right to work on that Wi-Fi situation, 00:14:56.702 --> 00:14:59.382 especially because, I mean, we wanted to set some servers up, 00:14:59.502 --> 00:15:02.322 Home Assistant, and we're going to be pulling down a bunch of packages. 00:15:02.622 --> 00:15:05.622 We wanted a connection that was going to be rock solid, not get an R-Way, 00:15:05.722 --> 00:15:07.422 and actually work for Hadea long term. 00:15:08.682 --> 00:15:12.902 So it'd been a little while, but we got to work setting up and re-familiarizing 00:15:12.902 --> 00:15:17.842 ourselves with the OpenWRT1, which I think ultimately was pretty quick to set 00:15:17.842 --> 00:15:22.102 up, even if it took longer than we would have liked to get everything right. 00:15:22.822 --> 00:15:25.802 Okay, so the thing I was kind of the most worried about was networking, 00:15:25.802 --> 00:15:27.942 and I think we have that working. 00:15:29.142 --> 00:15:35.642 Though every eight or ten pings, I'm getting a dupe error message from the ping command. 00:15:35.762 --> 00:15:40.162 So you get the ping that comes back with the milliseconds and all the normal 00:15:40.162 --> 00:15:44.342 stuff, but then it's got this dupe error next to it. Yeah, I don't know if I've seen that either. 00:15:44.922 --> 00:15:48.462 I don't know if this is some sort of double NAT thing that we're hitting, 00:15:48.482 --> 00:15:49.282 because we are attached. 00:15:49.782 --> 00:15:55.182 Her OpenWRT1 is attached to a LTE network. So maybe it's a carrier-grade NAT 00:15:55.182 --> 00:15:57.662 thing. I don't know. But it seems to be working. 00:15:57.842 --> 00:15:59.882 And the server's up. It's a basic config. 00:16:00.342 --> 00:16:06.002 But the server's up. So what's next for the server will be NextCloud and a KVM 00:16:06.002 --> 00:16:08.582 and then Home Assistant once we get all that going. 00:16:08.722 --> 00:16:11.102 Once the basics are done getting configured. You feeling good? 00:16:11.442 --> 00:16:13.862 Oh, yeah. We got NixOS running. How could I not feel good? 00:16:15.102 --> 00:16:19.822 Of course. Of course. Now, so not only were we getting these dupe pings every 00:16:19.822 --> 00:16:24.142 couple of pings and honestly the response time wasn't ideal, 00:16:25.686 --> 00:16:29.746 You're thinking maybe we were having some sort of Wi-Fi weirdness in here as well. 00:16:30.006 --> 00:16:32.806 So I wanted to know what the audience would use at this point. 00:16:32.926 --> 00:16:36.926 If you think maybe there's maybe a channel congestion or honestly, 00:16:37.066 --> 00:16:41.686 we thought perhaps one AP was just spazzing out because the one has a channel 00:16:41.686 --> 00:16:46.306 analysis tool in it, which we used, and we could see that everything was just 00:16:46.306 --> 00:16:47.526 stacked on top of each other. 00:16:47.626 --> 00:16:50.166 And there's this massive gap in the middle of the spectrum that just wasn't 00:16:50.166 --> 00:16:52.306 being used. So that's where we went. 00:16:52.306 --> 00:16:57.146 Well, we ran into so many ridiculous collisions this time. 00:16:57.326 --> 00:17:00.006 I mean, not only in like, oh, these are already on the same channel. 00:17:00.086 --> 00:17:00.986 We should move one of those. 00:17:01.126 --> 00:17:07.666 But then also in just like they were all using the most common IP address schemes in the 192.168. 00:17:07.906 --> 00:17:11.746 So multiple times it was like, oh, we should have just moved this from the start. 00:17:12.306 --> 00:17:15.766 Yeah, it was. And then we realized, too, like one of the things we could be 00:17:15.766 --> 00:17:19.926 dealing with is, you know, carrier grade NAT. And there is a shop next to us 00:17:19.926 --> 00:17:24.386 that has nice Wi-Fi hooked up to Fiber, and they have a guest network. 00:17:24.386 --> 00:17:27.006 So maybe we just take the LTE out of the picture. 00:17:27.306 --> 00:17:31.446 Okay, so we're still having some networking problems, and we've bounced around 00:17:31.446 --> 00:17:32.766 a couple of things. So here's what we've tried. 00:17:33.426 --> 00:17:36.746 To try to figure out why we're seeing these dupes in our pings. 00:17:37.026 --> 00:17:41.286 And honestly, we're getting 8 megabits when we should be getting 80. 00:17:41.286 --> 00:17:45.226 Yeah, we kind of expected, like, okay, maybe up to, like, 50% loss just from 00:17:45.226 --> 00:17:49.206 all the extra Wi-Fi and the double hops and all that, but not a factor of 10. 00:17:49.406 --> 00:17:53.266 So we also, as a troubleshooting thing, decided to swap over to the neighbor's 00:17:53.266 --> 00:17:55.886 Wi-Fi, which they have a guest public Wi-Fi that's open. 00:17:55.986 --> 00:17:59.906 And they're on Zip.ly fiber, so it's a good, solid connection. 00:18:00.126 --> 00:18:04.466 Yeah, we're getting, like, 80 plus minus over there. And then when we connect 00:18:04.466 --> 00:18:07.346 to the network directly, we can get 80 megabits, but when we do the bridge from the... 00:18:08.990 --> 00:18:13.570 OpenWRT1 to their public network, again, we're getting like 8 megabits, 00:18:13.710 --> 00:18:17.090 10 megabits, and also do pings. 00:18:17.430 --> 00:18:21.070 So it's got to be the configuration of the OpenWRT, but it's pretty simple, 00:18:21.210 --> 00:18:23.990 and I'm not really, nothing's jumping out at me. 00:18:24.050 --> 00:18:27.130 We've tried messing around with Wi-Fi radio channels. 00:18:27.410 --> 00:18:32.330 Yeah, we did move to another channel, and that helped a little bit, but no major change. 00:18:32.590 --> 00:18:34.930 There are two radios, and so... 00:18:34.930 --> 00:18:38.470 Yeah, it's possible maybe we're not using the best radio for this job. 00:18:38.590 --> 00:18:42.250 And it may be falling down to sort of the lowest common denominator of what 00:18:42.250 --> 00:18:44.170 it can actually talk to our attempted upstream. 00:18:44.310 --> 00:18:47.430 But we, of course, in this case, we don't actually know what the device we're 00:18:47.430 --> 00:18:48.690 talking to on the other side is. 00:18:49.510 --> 00:18:51.550 That's the problem with this particular troubleshooting technique. 00:18:51.990 --> 00:18:53.310 So, I mean, it's workable. 00:18:53.510 --> 00:18:58.390 I mean, 8 megabits you could live on, but it's not the 80 or 90 she should be getting. 00:18:58.870 --> 00:19:02.470 So I think this is an item that we're going to have to try to figure out. 00:19:02.470 --> 00:19:05.110 I mean, it's workable for today, but we need to figure it out. 00:19:05.230 --> 00:19:09.030 And it turned out we needed to pivot our strategy a little bit. 00:19:09.150 --> 00:19:13.350 And we also needed there are there are two different Wi-Fi antennae in this 00:19:13.350 --> 00:19:15.950 thing. And one is better at the 2.4 gigahertz stuff. 00:19:16.210 --> 00:19:21.110 And we needed that for the printer. We decided to split the labor up. 00:19:21.330 --> 00:19:24.910 And Wes worked on a very unplugged solution for something coming up. 00:19:25.050 --> 00:19:26.330 And we'll get to that in a moment. 00:19:26.330 --> 00:19:26.610 Yeah. 00:19:27.568 --> 00:19:31.768 And he was, you know, banging on a plan B for our Internet problems. 00:19:31.908 --> 00:19:37.288 And I decided to go back to my roots and get into some network printing and 00:19:37.288 --> 00:19:41.508 network printing troubleshooting, which, trust me, guys, I just love. 00:19:44.088 --> 00:19:47.668 OK, I've been trying to connect. There we go. Oh, my God. 00:19:48.928 --> 00:19:54.228 So I just got a report from the printer here. It took five minutes to print 00:19:54.228 --> 00:19:57.208 to tell me what it told me on the screen is that the connection failed. 00:19:58.328 --> 00:20:02.288 Wow, that's what it was taking so long to print? It's this black and white page 00:20:02.288 --> 00:20:04.348 with, like, monospace font on it. 00:20:04.468 --> 00:20:07.388 Is it just because I didn't intercap the AP name? 00:20:07.588 --> 00:20:10.088 Oh, maybe. Like, you can't figure that out? 00:20:10.648 --> 00:20:13.768 It's got to be exact. Well, at least I have to tap it all out on this tiny screen 00:20:13.768 --> 00:20:16.368 again. It's the world's tiniest screen. What is that, the size of a quarter? 00:20:16.548 --> 00:20:18.708 I mean, oh, my gosh. That's stupid. 00:20:19.488 --> 00:20:20.688 Well, maybe, do you think we're 00:20:20.688 --> 00:20:24.108 going to get another fun print after we successfully connect? I hope so. 00:20:24.628 --> 00:20:27.208 Don't you land? Well, we know that if I don't successfully connect, 00:20:27.228 --> 00:20:28.448 we'll get another fun one. 00:20:30.303 --> 00:20:32.823 I don't even know what's happening here right now, Wes. This is so bad. 00:20:33.263 --> 00:20:37.923 So, I mean, I'm a big fan of brother printers, but the Wi-Fi stack on this relatively 00:20:37.923 --> 00:20:42.263 new printer, I think it was bought late last year, so bad. 00:20:42.763 --> 00:20:48.343 Thankfully, the WRT1 is flexible, and I could take that antennae that was good 00:20:48.343 --> 00:20:52.503 at the 2.4, and I could just really make that a crappy security 2.4 gigahertz 00:20:52.503 --> 00:20:55.943 dedicated IoT network, which the printer could then join. 00:20:55.983 --> 00:20:59.663 But it's just got this tiny little UI where you've got to scroll through the 00:20:59.663 --> 00:21:04.563 numbers and tap out your WPA password and all of that. Absolute murder. 00:21:05.123 --> 00:21:09.443 I've recommended that series of printers to so many friends and family and then 00:21:09.443 --> 00:21:12.043 had to be the person to connect it to the Wi-Fi network. 00:21:12.543 --> 00:21:16.623 In that moment, you're like, why did I do this? They are rock solid once you 00:21:16.623 --> 00:21:20.023 get it on the network, but that's like the biggest pain point. 00:21:20.803 --> 00:21:23.783 The big question, though, Chris, is did you get that thing working? 00:21:24.683 --> 00:21:27.823 Credit to Wes. It really was. Wes was the one that figured out that I needed 00:21:27.823 --> 00:21:31.143 to ratchet down. Definitely, that was like the WPA security. 00:21:31.303 --> 00:21:35.683 Yeah, we specifically had to do WPA2, PSK, and then there was a couple other 00:21:35.683 --> 00:21:37.203 things, BGN compatibility. 00:21:37.403 --> 00:21:40.183 I don't know, like there was three or four specific tweaks. Like you really 00:21:40.183 --> 00:21:44.303 had to have a specific mode and a specific cipher that would really play best with. 00:21:44.863 --> 00:21:47.083 I think one of the LLMs grabbed some of those details. Like, 00:21:47.183 --> 00:21:51.123 yeah, this is kind of the profile you want to do. And once we got that specific configuration... 00:21:52.411 --> 00:21:53.211 Popped on just fine. 00:21:53.391 --> 00:21:56.071 Yeah, what surprised me is when it would do that ridiculous printout, 00:21:56.171 --> 00:22:00.871 which would take forever, it would identify the network security that it was using in the type. 00:22:01.311 --> 00:22:05.811 So it had the ability to recognize, like, WPA3 AES. 00:22:06.111 --> 00:22:09.551 It just couldn't join it. Which I thought, like, what is that? 00:22:09.551 --> 00:22:11.171 And it didn't say that that was the reason. 00:22:11.371 --> 00:22:12.011 No, it didn't. 00:22:12.211 --> 00:22:14.111 That was just a stat on the page. 00:22:14.231 --> 00:22:14.371 Yeah. 00:22:14.591 --> 00:22:16.991 As helpful as you can be without being any help at all, basically. 00:22:17.211 --> 00:22:17.351 Yeah. 00:22:17.831 --> 00:22:21.591 Yeah. So, but, you know, with that, thankfully, we're able to get that dedicated 00:22:21.591 --> 00:22:23.131 what I'm going to call the IoT network. 00:22:23.251 --> 00:22:26.491 So there'll probably be other IoT devices in the future that have similar problem. 00:22:26.631 --> 00:22:27.391 That's fine. They're safe. 00:22:28.231 --> 00:22:33.571 And really, the thing that I think was our greatest moment was part of all of this in the background. 00:22:33.811 --> 00:22:38.671 Wes was pivoting to building a Linux router, and we made a few tweaks to this, 00:22:38.891 --> 00:22:42.171 including one of the things that we decided about building this Linux router 00:22:42.171 --> 00:22:47.531 is we're going to get this MiFi into shape and we're just going to disable Wi-Fi on the MiFi. 00:22:47.851 --> 00:22:54.411 and plug it in over USB directly into a Nix router that we'll have do all the heavy lifting. 00:22:54.671 --> 00:22:58.531 Okay, a little pre-lunch pivot. Might regret, but we were just looking at this 00:22:58.531 --> 00:23:00.351 networking situation, and it's just insufficient. 00:23:00.751 --> 00:23:05.951 And we're not experts in the OpenWRT1. 00:23:06.131 --> 00:23:10.271 I mean, it's a great little device with great options, but we're fiddling around with the UI. 00:23:10.531 --> 00:23:13.751 I mean, honestly, it feels like the last 45 minutes to an hour have just been 00:23:13.751 --> 00:23:18.331 like us exploring a UI to find options. I think we could get to the UCI stuff 00:23:18.331 --> 00:23:20.891 underneath and, you know, put even more. Yeah, yeah, true. 00:23:21.071 --> 00:23:24.531 I don't know if that's what we want necessarily because we don't also know that very well. 00:23:24.811 --> 00:23:28.791 Yeah, so we're going to do the right thing, and we're going to set up the server 00:23:28.791 --> 00:23:34.611 that's our NextCloud and Home Assistant box to also be our router DNS and DHCP box. 00:23:34.771 --> 00:23:38.451 And, like, primary connection to the Wi-Fi that we're using as the upstream. 00:23:38.651 --> 00:23:43.891 So it will connect to the upstream Wi-Fi, and then using the Ethernet port, 00:23:44.071 --> 00:23:46.711 we will connect to the WRT1. 00:23:47.418 --> 00:23:50.898 which will then share that connection out via Wi-Fi. And we'll just have the 00:23:50.898 --> 00:23:55.818 NIC server doing the routing and the DNS and the HTTP because that's an interface we understand. 00:23:56.138 --> 00:23:59.498 And then, honestly, it might make it easier for me to make changes from remote, 00:23:59.678 --> 00:24:01.038 too, the more I think about it. 00:24:01.198 --> 00:24:05.458 Now I don't have to try to open up, like, a web UI in a remote browser kind of thing. 00:24:06.718 --> 00:24:10.558 Or it's going to be a huge pain in our butt and waste an hour of our time. We'll find out. 00:24:10.778 --> 00:24:14.758 I want to ask the audience in particular what tools you would have used to figure 00:24:14.758 --> 00:24:17.418 out what's going on with these Wi-Fi problems we had. 00:24:17.698 --> 00:24:20.618 And our solution was just remove as much Wi-Fi from the picture altogether. 00:24:21.398 --> 00:24:25.198 But this was extremely crowded. I'd say on the low side, there was probably 00:24:25.198 --> 00:24:26.678 30 APs that we could pick up. 00:24:26.938 --> 00:24:27.218 Easy, yeah. 00:24:27.478 --> 00:24:34.098 And some of them were pretty strong. And some of them seemed like businesses, AP1, AP2, AP3, AP4. 00:24:34.238 --> 00:24:37.458 And then others were obviously residential because it's a mix of business and residential. 00:24:37.638 --> 00:24:40.478 It's business on the first floor, residential on the second floor. 00:24:40.478 --> 00:24:45.538 Right. And like the open, you know, the one isn't like crazy underpowered or anything. 00:24:45.678 --> 00:24:48.678 I don't know if it's like blasting anything out, but fine. 00:24:48.998 --> 00:24:53.398 And we could see things that were at least as strong as it right there. 00:24:53.518 --> 00:24:54.458 And it was sitting next to us. 00:24:54.458 --> 00:24:58.258 Yes, right there at the desk. So I would like to know what you would use to 00:24:58.258 --> 00:25:02.198 troubleshoot and analyze Wi-Fi in this situation. 00:25:02.258 --> 00:25:05.518 Is there a particular tool that's beyond just Wi-Fi analyzer, 00:25:05.938 --> 00:25:08.678 or am I discounting Wi-Fi analyzer on Android? 00:25:08.878 --> 00:25:11.698 If you could boost in and tell us what you would use, because I think if we 00:25:11.698 --> 00:25:16.018 did this again, that would be a tool I would like to have in our toolbox to 00:25:16.018 --> 00:25:18.618 troubleshoot, because I could see that being an issue when we go to places like this. 00:25:18.718 --> 00:25:21.498 And we were kind of left just blind with what was really going on, 00:25:21.618 --> 00:25:22.958 with only what we could tell just by, 00:25:24.074 --> 00:25:28.254 what was in the one and with the tools in the one and what we had on our phones or our laptops. 00:25:28.734 --> 00:25:33.754 So that was, you know, a challenge. But I think once we moved over to USB and 00:25:33.754 --> 00:25:37.874 Wes got a nice little basic config going with DNS, mask and DHCP and all of 00:25:37.874 --> 00:25:42.154 that, we had started making some real progress finally on the networking. 00:25:43.534 --> 00:25:48.434 Well, progress has been made. We have the networking all set up on the Nix host. 00:25:48.574 --> 00:25:53.734 It's doing DHCP and DNS and it's routing out quite nicely. and we're using now 00:25:53.734 --> 00:25:57.814 the OpenWRT1 as an AP that's connected to the NixOS box. 00:25:58.134 --> 00:26:02.774 And I could not tell you why, but our throughput has gone from, 00:26:02.894 --> 00:26:06.114 at best, 8 megabits to now 60 megabits. 00:26:06.214 --> 00:26:09.274 We're not at the 80 we should be, but we're a lot closer. 00:26:10.230 --> 00:26:13.930 Do you have any thoughts on why? Blame Nix, in a good way. 00:26:14.830 --> 00:26:18.490 Or the magic of a full Linux kernel on x86? 00:26:18.850 --> 00:26:21.590 I don't know. But we're going to take the W where we can take it, 00:26:21.630 --> 00:26:23.470 and we're going to get Home Assistant spun up. 00:26:23.590 --> 00:26:27.530 So we're working right now on getting a bridge interface, so that way Home Assistant 00:26:27.530 --> 00:26:32.530 OS can run in KVM, but essentially get link-level access to the LAN so it can 00:26:32.530 --> 00:26:33.750 find all the stuff it needs to find. 00:26:34.070 --> 00:26:36.950 And we're setting up a little Home Assistant config, and then, 00:26:37.010 --> 00:26:40.310 well, I mean, a VM, and then we'll get a booting. I'm looking right now because 00:26:40.310 --> 00:26:41.450 Wes is doing the rebuild right now. 00:26:41.470 --> 00:26:45.310 Doing a boot command, getting ready to reboot, maybe with a new fancy bridge 00:26:45.310 --> 00:26:47.050 actually working. We'll see. 00:26:47.530 --> 00:26:51.730 Yeah, we can sometimes get it up and sometimes it just gets shut down by the system. 00:26:51.990 --> 00:26:55.050 But I think this reboot's going to do it, and then we'll have Home Assistant 00:26:55.050 --> 00:26:57.150 up and running. Because it's just the image. 00:26:57.330 --> 00:27:01.210 Once the VM starts, now we get Home Assistant configured. So we're really close. 00:27:01.790 --> 00:27:04.870 Boy, you know, I think we were losing it a little bit there. 00:27:04.990 --> 00:27:06.350 Clearly, we were getting hungry. 00:27:06.490 --> 00:27:10.030 We'd kind of been going in circles for a while. I didn't mention it before, 00:27:10.190 --> 00:27:13.590 but I think it's worth saying that part of the benefit of moving things over 00:27:13.590 --> 00:27:19.590 to NixOS was making sure you didn't have to spend any more time in the OpenWrt1 00:27:19.590 --> 00:27:24.790 web interface, which I think maybe might have cost you some sanity. 00:27:25.010 --> 00:27:27.890 I've realized this about myself in the past, too. 00:27:28.410 --> 00:27:31.810 I seem to have a threshold of fiddling with GUIs, as I put it. 00:27:31.950 --> 00:27:35.770 And I've hit it before with TrueNaz. I've hit it with PFSense. 00:27:35.930 --> 00:27:37.330 I've hit it with Proxmox. 00:27:37.330 --> 00:27:41.230 We would get to a state where you were trying to set a particular value that 00:27:41.230 --> 00:27:44.570 you'd know you'd seen where to set it, but then we're not that familiar with 00:27:44.570 --> 00:27:46.610 this UI. We used it for one day recently, right? 00:27:46.870 --> 00:27:50.370 And then so you're trying to hunt through the entire UI to go find it on which 00:27:50.370 --> 00:27:52.830 page and which button to get to that setting screen. 00:27:52.850 --> 00:27:55.450 I've already spent more than an hour on this, and I thought this would be a 00:27:55.450 --> 00:27:59.630 10-minute thing, right? And it's like, I just want to look at it all on one screen. 00:28:00.030 --> 00:28:04.730 I just want it in a config all on one screen, and then I don't have to hunt like this. 00:28:04.730 --> 00:28:09.190 So we thought Nick's would be the opposite experience. And for the most part, it was. Except. 00:28:09.907 --> 00:28:14.987 tang bridge yeah we would reboot the bridge would appear and um just for background 00:28:14.987 --> 00:28:18.827 right so what we're trying to do is run home assistant in kvm libvert virtual 00:28:18.827 --> 00:28:23.327 machine but obviously home assistant wants to talk to all the stuff on your network so big. 00:28:23.327 --> 00:28:23.727 Part of it. 00:28:23.727 --> 00:28:26.747 We were going to make a virtual switch a bridge on the 00:28:26.747 --> 00:28:29.847 linux host and then put the ethernet address 00:28:29.847 --> 00:28:34.087 that we're using to talk to the wi-fi as the backbone of the network in as a 00:28:34.087 --> 00:28:38.027 slave to the bridge and then that would be able to make sure that the VMs that 00:28:38.027 --> 00:28:42.087 get added and are also added to the ports of the bridge can talk automatically 00:28:42.087 --> 00:28:46.367 to the network and it'll just use all the same sort of DHCP setup and just get 00:28:46.367 --> 00:28:48.007 a regular IP on the network. 00:28:48.867 --> 00:28:53.167 Being Home Assistant to everything on the network just looks like another device 00:28:53.167 --> 00:28:57.427 directly on the network which is that link layer you really need for Home Assistant to do all its magic. 00:28:57.687 --> 00:29:02.467 But it would pop up, we would see it coming online successfully DNS Mask was happy about it. 00:29:02.587 --> 00:29:04.587 Hey, there's our BR0, we've got a bridge, great! 00:29:04.907 --> 00:29:06.147 And then it would disappear. 00:29:10.987 --> 00:29:15.027 Okay, this is genuinely perplexing. It's got to be vert manager or something's 00:29:15.027 --> 00:29:17.147 messing with us. But we reboot the system. 00:29:17.347 --> 00:29:20.487 The bridge interface comes up. You can even list interfaces, 00:29:20.487 --> 00:29:21.947 and for a few seconds, you'll see it. 00:29:22.207 --> 00:29:25.907 We have the right IP address. I mean, I bet the SMS was happy for a moment. 00:29:26.127 --> 00:29:29.067 And then, I don't know, 20 seconds after the system's loaded, 00:29:29.547 --> 00:29:31.007 the interface shuts down. 00:29:32.934 --> 00:29:35.874 And we don't have a network manager running on this system. Nope. 00:29:36.954 --> 00:29:40.834 So that is weird. That's a little problem. We thought we just had fixed with 00:29:40.834 --> 00:29:43.234 that last build. And yet it persists. 00:29:43.654 --> 00:29:47.954 This is exactly how network troubleshooting or, you know, quote-unquote upgrading 00:29:47.954 --> 00:29:49.494 always goes when I try it. 00:29:49.774 --> 00:29:54.814 This is why I hate networking. So did you boys just, like, keep at it and try 00:29:54.814 --> 00:29:58.494 to figure this out and an hour later make progress? Or how did this go? 00:29:59.314 --> 00:30:02.554 Well, we came up with a viable solution. 00:30:02.934 --> 00:30:05.254 You know, sometimes you just got to let the machine take a look. 00:30:05.394 --> 00:30:08.494 So we kind of threw our hands up and we threw the machine at it and said, 00:30:08.574 --> 00:30:13.514 hey, LLM, review all the logs and figure out why our bridge keeps disappearing. 00:30:13.734 --> 00:30:16.954 And sure enough, it found a correlation. I think it would have taken us a little while. 00:30:17.494 --> 00:30:21.814 And it appears to be related to our USB connection to the MiFi, 00:30:21.894 --> 00:30:23.694 that is our primary Internet connection. 00:30:24.514 --> 00:30:29.194 When it goes down and then comes back up, the bridge is getting shut down and 00:30:29.194 --> 00:30:30.034 then isn't starting again. 00:30:30.434 --> 00:30:34.774 And we need to make that independent of the rest of it. So it has it lined up. 00:30:34.874 --> 00:30:38.274 It says we can rebuild. So I'd say rebuild and reboot, and let's see if it works. 00:30:40.934 --> 00:30:45.134 Oh, also, look here. It has a line suggesting that we add USB power management to help. 00:30:45.354 --> 00:30:48.114 I think it just disconnected because we rebooted. That's why it disconnected. 00:30:48.254 --> 00:30:50.834 And I think it takes a bit before the interface appears. Right. 00:30:50.954 --> 00:30:53.714 And it might be just enough. It might be waiting until the host even starts 00:30:53.714 --> 00:30:57.534 to negotiate before it even creates an interface, because that thing also, port works for storage. 00:30:58.354 --> 00:31:01.754 So it can do a USB storage, or it can be a tethering interface. 00:31:02.174 --> 00:31:04.214 So it may have to do some sort of negotiation. 00:31:04.994 --> 00:31:07.894 I don't know how that works, but I do like that it found it. 00:31:07.974 --> 00:31:09.954 Do we have a bridge? Oh, this is looking better. We have a bridge. 00:31:12.023 --> 00:31:16.103 The bridge has disappeared before, so we don't know if we have a persistent bridge. Oh, okay, good. 00:31:16.383 --> 00:31:20.043 It's still there. Yes, and we just got an IP on our MiFi upstream, 00:31:20.223 --> 00:31:23.023 which is, I think, when it was failing before. Yes, that would make sense. 00:31:23.123 --> 00:31:27.283 Yeah, of course, right. I think we would have found that, but we don't have 00:31:27.283 --> 00:31:30.003 a full graphical environment here, so it's not the best for reading through 00:31:30.003 --> 00:31:33.343 files of system delay. It's just on a console. LM is perfect for that. 00:31:33.603 --> 00:31:36.303 Yeah, reading through and finding that correlation, I think that solved it. 00:31:36.683 --> 00:31:38.923 Nice. So now we have a bridge. 00:31:38.923 --> 00:31:43.243 Yeah, to really underscore that, what worked super well is Wes was physically at the console. 00:31:43.423 --> 00:31:47.663 You can imagine what that's like, a little headless server that we have a monitor attached to. 00:31:47.883 --> 00:31:53.483 And then I'm on my little laptop, and I'm SSH'd in. And I have to give a shout out to OpenCode. 00:31:54.463 --> 00:31:59.403 This is a killer LLM2E that really made this quick work, because it just was 00:31:59.403 --> 00:32:02.663 able to review the logs super quickly, find the correlation, 00:32:02.663 --> 00:32:04.543 and be like, well, here you go, dummy, this is your problem. 00:32:05.063 --> 00:32:08.503 And it was something that, yeah, like Wes said, maybe we would have found that. 00:32:09.350 --> 00:32:13.490 it found it very quickly. And the great thing about OpenCode is you can connect 00:32:13.490 --> 00:32:17.070 it to local models, you can connect it to remote cloud models, 00:32:17.210 --> 00:32:18.930 it has a lot of different options in there. 00:32:19.230 --> 00:32:20.090 OpenRouter easily. 00:32:20.390 --> 00:32:20.950 OpenRouter super easy. 00:32:20.950 --> 00:32:25.330 Any of the big cloud providers. And they also give you some free usage on their 00:32:25.330 --> 00:32:26.710 models without even logging in. 00:32:26.830 --> 00:32:30.290 Yeah, they have like these Zen models that they've kind of vetted and they host 00:32:30.290 --> 00:32:31.550 and let you use for a little bit. 00:32:31.930 --> 00:32:35.910 But the big thing is that it's MIT licensed, it's vendor neutral, 00:32:35.910 --> 00:32:39.390 and it's perfect for these kind of quick, I need to get something running and 00:32:39.390 --> 00:32:40.850 diagnose and read through some logs. 00:32:41.350 --> 00:32:44.070 And I think it made it go a lot faster for us. We probably would have had to 00:32:44.070 --> 00:32:46.930 burn, you know, another 10, 20 minutes trying to find that correlation. 00:32:47.310 --> 00:32:50.470 And it's nice to see this when every other provider has their own version, right? 00:32:50.550 --> 00:32:53.590 And now you're seeing like folks locking it down more where only some plans 00:32:53.590 --> 00:32:56.590 can be used with their particular version of these kinds of tools. 00:32:56.770 --> 00:32:59.570 So it's nice to have an open source thing for a very useful tool. 00:32:59.590 --> 00:33:01.250 Yeah, if you're playing around with something like Cloud Code, 00:33:01.610 --> 00:33:04.090 you could easily use something like this. Then you're not tied to a particular 00:33:04.090 --> 00:33:06.430 vendor. You could keep using the Cloud stuff if you want. 00:33:06.650 --> 00:33:10.870 But OpenCode is vendor neutral. Like I said, it's MIT licensed. And it's beautiful. 00:33:11.090 --> 00:33:11.910 It's really snappy. 00:33:12.130 --> 00:33:15.190 It's beautiful. It's fast. And it's got a lot of smart features. 00:33:15.450 --> 00:33:19.550 And it was just like it was taking a laser at this and just boom, found it right away. 00:33:19.730 --> 00:33:23.770 Oh, here's your problem. And then it was so obvious. Oh, of course. Right. Duh. 00:33:24.517 --> 00:33:27.957 Okay, so we've got the bridge. It was actually staying around doing its job. 00:33:28.117 --> 00:33:31.677 So that means the Home Assistant virtual machine could actually start and get 00:33:31.677 --> 00:33:34.877 on the network and actually start getting configured. It had a bunch of stuff 00:33:34.877 --> 00:33:38.537 to pull down, some Docker containers, because we're using the whole Home Assistant 00:33:38.537 --> 00:33:42.037 OS setup here. But we had a little more work to do. 00:33:42.717 --> 00:33:48.217 And the final piece falls into place. We had one last thing to do, and that was? 00:33:48.997 --> 00:33:52.257 Establish a Nebula network. That's right. By directional SSH, 00:33:52.257 --> 00:33:54.937 because otherwise we can't actually do what we need to do. Yeah. 00:33:55.337 --> 00:33:58.177 I mean, not only does it mean that we get to wrap up and finish anything that 00:33:58.177 --> 00:34:01.277 needs to be finished remotely, but that's also what I'll use for off-site backups 00:34:01.277 --> 00:34:03.237 as well. So it's really good to have that. 00:34:04.017 --> 00:34:07.417 And that'll be something I can work on from my leisure at home. 00:34:08.117 --> 00:34:11.657 And now you can print your lady love notes wherever you are. 00:34:13.157 --> 00:34:15.137 Yeah, I signed you up for that. So you better make good on it. 00:34:16.657 --> 00:34:19.637 This is awesome. I didn't know you guys were going to do the Nebula part of it. 00:34:19.677 --> 00:34:24.317 How did that go? And, well, basically, Chris, I'm assuming doing all your work 00:34:24.317 --> 00:34:27.637 from home is going to be much better than having to deal with the office internet? 00:34:28.597 --> 00:34:32.197 Yes, very much so. Just being able to chill and do it from the comfort of home 00:34:32.197 --> 00:34:34.357 is nice. Or support her when she needs it. 00:34:34.697 --> 00:34:38.297 You know, because part of this also is which didn't work in the clips just for timing. 00:34:38.457 --> 00:34:42.217 But we have a little basic NextCloud setup on there. And I'm going to offsite 00:34:42.217 --> 00:34:46.597 backup that for her. But long story short, the nice thing I really clicked in 00:34:46.597 --> 00:34:51.877 with Nebula is we didn't have to ask permission from any service or log in any service provider. 00:34:52.317 --> 00:34:56.637 We just issued ourself the keys and set up a quick lighthouse, 00:34:56.637 --> 00:34:59.637 which I almost had completely finished anyways. It just takes no time at all. 00:34:59.957 --> 00:35:05.017 And then it was we had a private mesh VPN with no other person, 00:35:05.257 --> 00:35:06.717 company, entity involved at all. 00:35:06.977 --> 00:35:10.657 And it's perfect for a clinic, you know, trying to do offsite backups privately. 00:35:10.657 --> 00:35:13.017 Yeah, and it was pretty easy to get it kind of connected to the rest of what 00:35:13.017 --> 00:35:17.057 you needed so that you had a link from your existing setup in there when you do need remote access. 00:35:18.047 --> 00:35:21.227 And then Nebby has a lot of nice firewall rules, too, so you can kind of make 00:35:21.227 --> 00:35:24.387 sure that only the stuff and the directions that you want are allowed. 00:35:25.187 --> 00:35:30.107 We started the show talking about what Hadiyah wanted out of all of this, 00:35:30.127 --> 00:35:33.507 and you boys spent all of your time seemingly trying to troubleshoot the network. 00:35:34.287 --> 00:35:38.367 Did you get there? Like, was she happy with the end result? 00:35:39.007 --> 00:35:42.307 Okay, so it took a little longer. It's 6 p.m. I thought we'd be done at 3 p.m. Yeah. 00:35:43.407 --> 00:35:47.167 But here's what we got for you. So that over there is your new server. 00:35:47.167 --> 00:35:49.987 I'm pointing at the little tiny box. Great. We need it doctor. 00:35:50.287 --> 00:35:54.367 Yeah, that's doctor server, server doctor. And it's going to run your home assistant, 00:35:54.467 --> 00:35:56.647 which you can see we have up and running over there on that screen. 00:35:56.807 --> 00:36:01.307 I see it. And that blue box is the WRT1. And that's going to be doing your Wi-Fi now. 00:36:02.787 --> 00:36:05.867 Your internet connection is now connected over USB to your server. 00:36:07.099 --> 00:36:09.319 And so we're just going to need to find a place for all this. 00:36:09.439 --> 00:36:12.879 But I've tested your printing. The Wi-Fi network is way solid, 00:36:12.879 --> 00:36:15.079 so the devices shouldn't drop off anymore. Good. 00:36:15.759 --> 00:36:19.699 And your Internet is much better than it was. We were having some sort of weird, 00:36:19.699 --> 00:36:22.259 like, IP conflict. I don't know what was going on. 00:36:23.019 --> 00:36:26.839 How did you solve it without knowing what it was? We swapped out the hardware 00:36:26.839 --> 00:36:30.159 and just YOLO'd into using the server to act as a router. 00:36:30.219 --> 00:36:35.319 And then we switched from using Wi-Fi or Ethernet to connect to the Wi-Fi to using USB. 00:36:35.559 --> 00:36:38.819 Oh, that's what I would have done. I should have mentioned that to begin with. 00:36:38.939 --> 00:36:41.179 Yeah. Yeah, that would have saved us some time. We should have waited for you to get back. 00:36:42.279 --> 00:36:45.939 I didn't want to step on you or woman's plane, you know? All right. 00:36:46.999 --> 00:36:49.299 Well, we'll check back in and see how it's working in a few days. 00:36:49.639 --> 00:36:53.219 I mean, the core thing she wanted was solid Wi-Fi, and I think we delivered that. 00:36:54.099 --> 00:36:57.319 The NextCloud stuff, she and I need to work on more because we need to develop 00:36:57.319 --> 00:37:00.819 a workflow for how she actually exports her backup data to the NextCloud. 00:37:01.099 --> 00:37:01.259 Yeah. 00:37:01.339 --> 00:37:03.959 We haven't worked that workflow out yet. So that remains to be done. 00:37:03.999 --> 00:37:06.099 And the Home Assistant instance is basic. 00:37:06.579 --> 00:37:10.039 And so there's some refinement needs to be there. But some of that she'll do 00:37:10.039 --> 00:37:11.499 on her own. She doesn't mind toying with that. 00:37:12.619 --> 00:37:15.819 But I think, you know, there's probably room for improvement, 00:37:15.819 --> 00:37:19.279 but we got the job done. And I actually would like to punt that over to the audience. 00:37:19.439 --> 00:37:22.559 And, you know, a great way to boost in and support the show is how do we do? 00:37:22.939 --> 00:37:27.999 Give us your grade, you know, A to F, what we can improve if we did this out 00:37:27.999 --> 00:37:31.899 in production for a listener in the future or somebody's Airbnb or small business 00:37:31.899 --> 00:37:35.699 or home lab and some Wi-Fi tools. 00:37:36.862 --> 00:37:40.222 I think would be good. And also just general, like, what we could have done better. 00:37:40.482 --> 00:37:42.382 What pro tips, setups you like? 00:37:42.742 --> 00:37:46.142 I am very happy with how solid we got the internet ultimately. 00:37:46.462 --> 00:37:50.502 And then the Wi-Fi LAN seems to be very solid too, so she's not going to have the drop-off. 00:37:50.682 --> 00:37:54.542 Yeah, that's, I mean, at least even if there are sort of upstream issues or, 00:37:54.602 --> 00:37:58.842 you know, service provider, etc., at least having a stable LAN means you don't go insane. 00:37:59.002 --> 00:38:03.382 And ultimately, the reason why I wanted to use NixOS for doing the DNS and DHCP 00:38:03.382 --> 00:38:06.462 is because it's just there in the declarative configuration. 00:38:06.942 --> 00:38:09.742 And so I just need to back that up. And if I ever have to restore her server, 00:38:09.982 --> 00:38:13.662 I just restore that configuration and all of her core network settings get restored. 00:38:13.782 --> 00:38:16.982 That was also handy as we were like onboarding the VM and onboarding the printer. 00:38:17.202 --> 00:38:20.762 And like it just was super easy to add reservations and check on things. And yeah. 00:38:20.942 --> 00:38:23.542 That's a great point, Wes. As we started to build that stuff up, 00:38:23.602 --> 00:38:26.622 it was just sort of obvious that this was a better route for us to go for the 00:38:26.622 --> 00:38:27.462 kind of integration we wanted. 00:38:27.742 --> 00:38:31.682 So I am happy with the results, but there is still a little bit of work left to be done. 00:38:32.262 --> 00:38:35.782 I think if we hadn't spent so much time troubleshooting the different network stuff. 00:38:35.782 --> 00:38:39.602 We did kind of spend half the day getting to the point where we even ended up 00:38:39.602 --> 00:38:40.942 on the path that was the good path. 00:38:41.082 --> 00:38:45.662 So that limited our results. Because we knew the WRT1 was good and we could 00:38:45.662 --> 00:38:47.902 probably get it working, but just ultimately. 00:38:48.022 --> 00:38:51.582 There really are limited know-how of how to properly utilize it. 00:38:51.622 --> 00:38:52.502 It's probably part of it. 00:38:53.462 --> 00:38:57.742 At the end, though, we switched to our strength and it worked pretty well. 00:39:00.905 --> 00:39:05.265 Well, thank you very much to our members. The early year sales are lean, 00:39:05.405 --> 00:39:09.205 and this is an area where we lean very much on the members to keep things going. 00:39:09.545 --> 00:39:14.205 There's no understatement there. The members are making these episodes possible, 00:39:14.205 --> 00:39:16.765 and I really do appreciate it. 00:39:16.885 --> 00:39:19.685 You can get a membership right now at a great discount. I think we still have 00:39:19.685 --> 00:39:24.585 some bootleg promo codes to claim for the annual or for the month-to-month membership. 00:39:24.585 --> 00:39:28.845 You can apply them for the linuxunplugged.com membership. We'll get you a core 00:39:28.845 --> 00:39:33.965 membership and that gets you the unedited bootleg version now in video in that 00:39:33.965 --> 00:39:35.545 feed as well, a video version of the show. 00:39:36.245 --> 00:39:38.985 Wave, boys. Hi. We see we're waving right now to the video version of the show. 00:39:39.145 --> 00:39:42.665 And then – but notice how we haven't effed up the audio version because we love you. 00:39:42.985 --> 00:39:46.305 And then also there is an ad-free version of the audio version that's still 00:39:46.305 --> 00:39:48.405 got all of Drew's great touches that's available for you. 00:39:48.525 --> 00:39:51.325 And then at jupiter.party, that's a whole network membership because we have 00:39:51.325 --> 00:39:55.665 a bootleg thing going for launch and other shows that will eventually also be 00:39:55.665 --> 00:39:58.845 on there. So that's jupyter.party for the whole network membership and then 00:39:58.845 --> 00:40:01.385 bootleg for the promo code. 00:40:01.905 --> 00:40:04.925 The bootleg really is where it's at. I got to say, there's some good stuff in 00:40:04.925 --> 00:40:05.665 there. We had a good bootleg. 00:40:05.745 --> 00:40:07.105 Some sneaky extras, you might say. 00:40:07.485 --> 00:40:09.845 Thank you very much to our members for making it possible. And of course, 00:40:10.045 --> 00:40:14.825 everyone who boosts each episode. These are the things that keep us going and sustain the podcast. 00:40:18.434 --> 00:40:23.474 This week we were lucky enough to receive a little update from Olympia Mike, dear friend of the show. 00:40:23.634 --> 00:40:28.334 He says, hey Lupp family, I got a great follow-up to the Holiday Home Lab episode. 00:40:28.614 --> 00:40:31.774 My little Nixbook side project has all grown up. 00:40:32.034 --> 00:40:38.474 The Computer Upcycle Project is now an official non-profit taking donated hardware, fixing it up, 00:40:38.914 --> 00:40:41.634 and getting it into the hands of people who need it 00:40:41.634 --> 00:40:44.854 recently we received a donation of 35 00:40:44.854 --> 00:40:48.554 hp pro desk 600 g5 minis 00:40:48.554 --> 00:40:51.854 they're 8th and 9th gen i5s 8 00:40:51.854 --> 00:40:54.594 to 16 gigs of ram they generally have a 00:40:54.594 --> 00:40:57.954 serial ata ssds in them they're small quiet fast 00:40:57.954 --> 00:41:00.874 and easy to upgrade now there is one catch though 00:41:00.874 --> 00:41:06.574 they don't have built-in wi-fi which makes them less than ideal for everyday 00:41:06.574 --> 00:41:13.314 home desktops but these things make fantastic little home servers so here's 00:41:13.314 --> 00:41:18.954 the deal i want to offer them completely free to the linux unplugged community, 00:41:19.714 --> 00:41:24.634 you cover the shipping from olympia washington i send you a box no strings attached 00:41:24.634 --> 00:41:29.894 and you use it for whatever you want home lab server experiments chaos it's up to you. 00:41:31.883 --> 00:41:35.883 That is pretty great, Mike. So how do they reach out to Mike if they're interested 00:41:35.883 --> 00:41:39.643 in covering the shipping and grabbing one of these HP Homelab boxes? 00:41:39.843 --> 00:41:42.723 Yeah, if you're interested, just, well, shout out to Mike. 00:41:43.363 --> 00:41:48.523 So it's Mike at ComputerUpcycleProject.org, and you can organize how all that 00:41:48.523 --> 00:41:51.123 shipping is going to work and where to send these little monsters. 00:41:51.403 --> 00:41:56.323 That is so kind and great. And congrats on the nonprofit and just this continuing. 00:41:56.323 --> 00:42:01.063 I mean, also, I saw, we previously mentioned the license discussion that Mike 00:42:01.063 --> 00:42:02.043 was having with his community. 00:42:02.223 --> 00:42:02.343 Right. 00:42:02.483 --> 00:42:07.523 Well, they kept going after we talked about it and had some great discussions 00:42:07.523 --> 00:42:12.123 and reasonings shared from the project side and have ended up going through 00:42:12.123 --> 00:42:17.363 the steps to get all the approval from all the contributors and are now officially licensed as MIT. 00:42:17.623 --> 00:42:18.703 Hey, that's good to hear. 00:42:18.883 --> 00:42:19.303 Hopefully. 00:42:19.483 --> 00:42:20.043 Glad they got that sorted. 00:42:20.403 --> 00:42:23.623 Yeah, right? So it's the next stage of the project in many ways, which is wonderful. 00:42:23.623 --> 00:42:29.703 I want to give a huge thank you to listener Alex and also to producer Jeff. 00:42:30.043 --> 00:42:36.903 They each sent in a Coral USB accelerator for the show, and I grabbed one right away as it came in. 00:42:37.063 --> 00:42:41.063 And one just came in too. Wes has one now. I, of course, hooked mine up to Frigate. 00:42:41.163 --> 00:42:44.063 I have now Frigate with accelerated detection. 00:42:44.743 --> 00:42:48.063 And I'm really liking it. So if people are interested in an episode on Frigate, 00:42:48.323 --> 00:42:51.603 the open source DVR, where you can take a bunch of different kind of camera 00:42:51.603 --> 00:42:54.083 feeds and put them into one DVR and keep it all local. 00:42:54.363 --> 00:42:58.083 And with this accelerator, I'm doing, you know, millisecond face detection now 00:42:58.083 --> 00:43:00.523 and stuff like that and object detection and motion detection. 00:43:01.123 --> 00:43:05.943 And so we have the second one here because listener Alex and PJ were both very generous. 00:43:06.243 --> 00:43:09.743 And so while I think while we have it around, we should play audio tagging. 00:43:09.803 --> 00:43:12.383 Wes, you were looking at ways to maybe do a little tagging with audio and whatnot 00:43:12.383 --> 00:43:15.363 with the choral chatted about that. So I think that could be a fun project. 00:43:15.363 --> 00:43:18.483 It does seem like there's got to be some wacky, fun things we can do with this thing. 00:43:18.783 --> 00:43:21.663 And Brent rumor has it there may be a third one if you make it over here sooner or later. 00:43:21.843 --> 00:43:22.823 Oh, I'm on my way. 00:43:22.823 --> 00:43:25.803 I don't know. We don't know. Maybe it ends up, you know, sneaking out in the 00:43:25.803 --> 00:43:27.083 hands of somebody else. But. 00:43:27.642 --> 00:43:30.622 Thank you, Alex, and thank you, PJ. Really appreciate that. 00:43:30.722 --> 00:43:35.862 And would love, love to hear what you can do with the West and be happy to do 00:43:35.862 --> 00:43:39.542 a report on Frigate if people are interested. Just let us know. 00:43:39.802 --> 00:43:40.022 Indeed. 00:43:45.442 --> 00:43:49.482 Well, we received a baller boost. Wait, there's several baller boosts here, 00:43:49.562 --> 00:43:56.622 but the top one, 100,000 sats from CJ McAdemy. 00:43:58.062 --> 00:43:58.542 Macademy. 00:43:58.722 --> 00:43:59.842 Yes, CJ Macademy. 00:44:00.402 --> 00:44:01.282 Or CJ Macademy. 00:44:01.382 --> 00:44:04.782 Thank you for the boost. Well, 00:44:10.942 --> 00:44:15.322 CJ Macademy says, Hey, I've been a weekly listener for about two years now. 00:44:15.522 --> 00:44:20.342 I am a macOS system admin with a little prior Linux experience, 00:44:20.482 --> 00:44:26.442 and the show was recommended to me by one of our company's Linux devs as a place to dive into Linux. 00:44:26.982 --> 00:44:30.982 Well, long story short, I run Nix packages and NixOS on everything possible 00:44:30.982 --> 00:44:33.522 now. So here's some value for value. 00:44:33.782 --> 00:44:36.242 See you all at scale and plan Nix. 00:44:36.562 --> 00:44:41.262 Oh, great. Looking forward to that. Wonderful. Thanks for saying hi. 00:44:41.402 --> 00:44:43.662 Yeah, thank you very much. Thank you for listening. I'm glad to hear that. 00:44:44.042 --> 00:44:47.622 Interesting, too, because I think that's a really neat demonstration of the 00:44:47.622 --> 00:44:49.602 demographic that listens to the show as well. 00:44:50.082 --> 00:44:53.762 And I'm glad to hear that these tools are useful on all the platforms out there. Thank you, CJ. 00:44:53.902 --> 00:45:00.082 Appreciate you being our baller booster. Mr. Hybrid Sarcasms back with a nice 25,000 sets. 00:45:05.301 --> 00:45:08.861 Well, wouldn't you know it? He's on to actual budget. When I saw the actual 00:45:08.861 --> 00:45:12.401 budget supports multiple users via OIDC. 00:45:12.621 --> 00:45:13.861 Is that the Excel connection? 00:45:14.541 --> 00:45:16.001 No, that's OpenID. 00:45:16.241 --> 00:45:20.721 Okay. Oh, right. I'm thinking of whatever it used to be where you could connect Excel to SQL Server. 00:45:20.741 --> 00:45:21.381 I love that idea. 00:45:21.621 --> 00:45:24.701 I'm like, what is he doing? I'm thinking budgets, right? I'm thinking spreadsheets. 00:45:25.041 --> 00:45:26.601 I implemented PocketID. 00:45:26.861 --> 00:45:29.481 Oh, there you go. I should have just read the next sentence in my home network. 00:45:29.641 --> 00:45:32.621 It's game-changing to log into an app using a pass you stored in BitWarn. 00:45:32.621 --> 00:45:35.301 Now I'm O-dicking all the things. 00:45:35.721 --> 00:45:36.081 Wow. 00:45:36.541 --> 00:45:40.761 I have been very tempted by this, too. In fact, this is what makes me a little 00:45:40.761 --> 00:45:43.541 pro passkey, is a setup very much like this. 00:45:44.321 --> 00:45:49.101 And also, I think using Bitwarden or a 1Password password manager makes it a lot smoother. 00:45:49.241 --> 00:45:49.921 For sure, yeah. 00:45:50.101 --> 00:45:52.901 But then you've got to kind of commit for a while. So consider that. 00:45:52.981 --> 00:45:55.201 That's why I like hybrid setup here. That's something I could commit to. 00:45:55.241 --> 00:45:56.321 Yeah, very nice work, hybrid. 00:45:56.621 --> 00:45:58.381 I could OIDick all over the place. 00:45:58.501 --> 00:46:01.641 Curious how you like actual budget, too. That's been curious about that. 00:46:01.681 --> 00:46:02.161 Yeah, good call. 00:46:03.441 --> 00:46:08.781 The DudaBinds abides in with McDuck's 22,222 sets. 00:46:10.861 --> 00:46:13.281 You brought back some memories with the disc burner. 00:46:13.541 --> 00:46:13.701 Oh, good. 00:46:13.941 --> 00:46:19.261 I remembered I used to use Nero on Windows and K3B and Bracero on Linux. 00:46:19.441 --> 00:46:20.661 Uh-huh, you used all those, yep. 00:46:20.801 --> 00:46:25.361 I don't know why, but I specifically remember the Tayo Yudin DVDs, 00:46:25.461 --> 00:46:27.221 buying them by the hundreds back in the day. 00:46:27.901 --> 00:46:31.181 I bought an LG Blu-ray writer in 2023, actually. 00:46:31.301 --> 00:46:31.361 Same. 00:46:31.361 --> 00:46:34.841 The flashable version, WH-16NS40. 00:46:35.041 --> 00:46:36.201 That was the one. 00:46:36.681 --> 00:46:41.181 But I hardly ever used it. If when I ever get it out of storage, 00:46:41.601 --> 00:46:44.321 I might give this cold storage idea a go. 00:46:44.421 --> 00:46:44.801 Do it. 00:46:44.941 --> 00:46:46.441 Thanks for the content, as always. 00:46:46.861 --> 00:46:51.661 And I was reminded via email this morning, when it comes to optical media, 00:46:51.881 --> 00:46:56.021 why not burn two? Because one is none, after all. And you never know when it 00:46:56.021 --> 00:46:57.021 comes to optical storage. 00:46:57.401 --> 00:47:01.221 So, thank you very much. Appreciate it, dude. It's good to hear from you. 00:47:01.621 --> 00:47:05.461 Well, Johnny Castaway boosted in a Spaceballs boost. One, two, 00:47:05.661 --> 00:47:07.141 three, four, five Satoshis. 00:47:12.092 --> 00:47:16.852 I'm just passing this along for your perusal. It's a little Reddit thread. 00:47:17.072 --> 00:47:20.772 It's only an open source one petabyte NAS. 00:47:21.012 --> 00:47:22.932 No big deal. Seems doable, right? 00:47:23.572 --> 00:47:26.472 Might try building this one myself after Fosdom this month. 00:47:26.772 --> 00:47:29.752 That's a lot of spinning rust. Wow, man. 00:47:29.992 --> 00:47:31.232 You seem like you're sweating a little bit. 00:47:31.392 --> 00:47:34.792 I just get a little nervous about babysitting that much spinning rust, 00:47:34.912 --> 00:47:38.392 but that would be cool. It's usually one of these open enclosures. I do love that idea. 00:47:39.072 --> 00:47:42.172 the closure and closure is printed and then it has the back planes in there 00:47:42.172 --> 00:47:46.772 and wiring channeling for it and i mean it looks really slick it can hold up 00:47:46.772 --> 00:47:52.172 to 45 discs so uh yeah that's how you get to a petabyte right 45 24 terabyte 00:47:52.172 --> 00:47:55.632 that's absolutely we could. 00:47:55.632 --> 00:48:00.992 Just build one of these for the jv colony to use you know let's put it in space 00:48:00.992 --> 00:48:04.312 or something and we can all access it and have some off-site backups. 00:48:04.312 --> 00:48:07.832 It will even contribute to the ipfs network you never know. 00:48:08.652 --> 00:48:09.752 A networking dream. 00:48:09.752 --> 00:48:16.692 Wow thanks Johnny appreciate it hey there's Gene Bean he's here with 4,813 sats 00:48:16.692 --> 00:48:18.032 I think he wants some mac and cheese, 00:48:20.350 --> 00:48:23.790 He says, I'm using Backblaze B2 for my backups. It's the way to go, 00:48:23.870 --> 00:48:28.170 in my opinion. And he says, Chris, you made me nostalgic with your Blue Vault project. 00:48:28.930 --> 00:48:34.670 And he links me to the old Svelte CD DVD case that many of us have. 00:48:34.670 --> 00:48:35.590 Yes, look at this. 00:48:35.610 --> 00:48:39.650 With the plastic bindings where you slide 96-disc capacity. Yeah. 00:48:39.950 --> 00:48:43.550 I think I still have one of those, actually. It's got a couple of Ubuntu discs in there. 00:48:43.550 --> 00:48:45.530 It works for car, home, office, or travel. 00:48:45.650 --> 00:48:46.030 Honestly. 00:48:46.270 --> 00:48:47.210 You need backups everywhere. 00:48:47.250 --> 00:48:50.230 It's actually a good idea. That is actually a really good idea. 00:48:50.350 --> 00:48:53.390 Because what am I going to do? Have a stack of jewel cases like an animal where 00:48:53.390 --> 00:48:55.510 I could have one pack and it's only $10. 00:48:55.970 --> 00:48:59.290 Did any of you have one of these in your car so that you could just like? 00:48:59.330 --> 00:48:59.630 Oh, yeah. 00:48:59.710 --> 00:49:00.150 For sure. 00:49:00.290 --> 00:49:00.610 Oh, yeah. 00:49:00.730 --> 00:49:00.990 All right. 00:49:01.090 --> 00:49:03.170 I also had the one that clipped onto the visor. 00:49:03.850 --> 00:49:05.130 Yeah, the quick switch. 00:49:05.790 --> 00:49:05.970 Yep. 00:49:06.110 --> 00:49:06.830 You pro. 00:49:08.010 --> 00:49:12.910 And he shouts out to Unify for a great Wi-Fi hardware and stuff. 00:49:13.090 --> 00:49:16.010 So thank you, Gene. Appreciate you, sir. Always great to hear from you. 00:49:16.990 --> 00:49:19.410 Well, PCNORF boosts in with 5,000 cents. 00:49:19.610 --> 00:49:20.370 Oh. Thank you. 00:49:25.458 --> 00:49:28.038 Don't forget to do a dedicated burn for Jar Jar. 00:49:28.218 --> 00:49:33.638 You always want to have an extra burn for Jar Jar, right? Because one is none, 00:49:33.658 --> 00:49:35.598 and Jar Jar needs at least one. 00:49:40.378 --> 00:49:47.058 Doornail 7887 boosted in a row of ducks. Damn it, Chris, your timing is quite suspicious. 00:49:47.058 --> 00:49:52.658 I just wrote a very similar app, which is, granted it's a Python-based app, 00:49:52.658 --> 00:49:57.258 for backing up my ever-growing data to a suite of old, small, 00:49:57.258 --> 00:49:59.838 offline hard drives I keep in a safe. 00:49:59.838 --> 00:50:04.998 I pull them out regularly and was manually managing which data went on which 00:50:04.998 --> 00:50:09.198 drive, but that was getting quite a bit out of hand, and I needed some automation. 00:50:09.358 --> 00:50:13.298 Maybe you should consider more than just optical destinations? 00:50:13.938 --> 00:50:14.478 Hmm. 00:50:15.698 --> 00:50:15.898 Huh? 00:50:16.098 --> 00:50:18.018 Blue fault. If I could find a nice stasher of spinning rust, 00:50:18.118 --> 00:50:19.198 that's probably the way I would go. 00:50:20.158 --> 00:50:23.578 I had. Maybe if I dug through all the systems here in the studio, 00:50:23.698 --> 00:50:26.538 I could probably come up with a few terabytes. You know what I mean? 00:50:26.858 --> 00:50:30.578 Just pull them out of those old laptop stacks. 00:50:30.918 --> 00:50:33.418 Why don't I think that every raid you make is a scary raid? 00:50:33.518 --> 00:50:34.238 No kidding, right? 00:50:34.658 --> 00:50:36.358 Except for my raid one. I had to 00:50:36.358 --> 00:50:39.398 do a raid one over the week to save my Butterfest install. That one is... 00:50:39.398 --> 00:50:40.158 Fair, fair. 00:50:41.078 --> 00:50:45.278 All right. Thank you very much, Dornell. Appreciate that. Lymilus? 00:50:45.998 --> 00:50:48.218 Imilus? What do you think there, Wes? What would you give that one? 00:50:48.978 --> 00:50:49.738 Elmilus. Milus comes in. 00:50:49.838 --> 00:50:50.158 Milius? 00:50:50.258 --> 00:50:54.918 Yeah. It's good, though. I like it. It's good. It's good. They come in with 4,000 sats. 00:50:57.036 --> 00:50:59.476 Wow, check this out, party member and listener since 2020. 00:50:59.736 --> 00:50:59.976 Nice. 00:51:00.276 --> 00:51:02.896 On the Self-Husted Show and then added love. Well, thank you very much. 00:51:03.036 --> 00:51:06.516 Thank you for being here. So I ran out of episodes to listen to. 00:51:06.576 --> 00:51:07.796 This is my first boost. Hey! 00:51:08.896 --> 00:51:11.756 Welcome. Thank you for figuring it out. 00:51:12.876 --> 00:51:18.416 He said, oh, good. I use Friggin on an Intel system, and you could try out OpenVINO. It's a detector. 00:51:18.676 --> 00:51:24.236 Rather than getting a Coral TPU, it utilizes the iGPU on 6th Gen and later Intel 00:51:24.236 --> 00:51:28.976 CPUs. inference time on my 6th gen has been reliable in the sub-20 millisecond 00:51:28.976 --> 00:51:31.816 timing, you know, compared to the 9 to 10 you get on the Coral. 00:51:31.956 --> 00:51:32.396 Not bad. 00:51:32.516 --> 00:51:36.396 Run it for about six months. This is a great field report because we were talking 00:51:36.396 --> 00:51:39.336 about OpenVino behind the scenes and maybe doing an episode on it, 00:51:39.356 --> 00:51:42.596 and I want to know if you could tell me, and this is something I should look 00:51:42.596 --> 00:51:45.536 into, but I have an Intel Arc, one of the first generation Intel Arcs, 00:51:45.776 --> 00:51:48.656 in the machine here in the studio, and could I use OpenVino, 00:51:49.176 --> 00:51:53.496 to start doing inference on that Intel Arc? Oh, that'd be great. 00:51:53.496 --> 00:51:56.836 And then we could have it maybe it could watch Brent and we could tell when 00:51:56.836 --> 00:51:59.016 he sneaks away or if there's a cat in the frame or not. 00:51:59.016 --> 00:52:01.696 Definitely and whenever there's a cat in the frame we just switch to him. 00:52:02.156 --> 00:52:03.736 Exactly for the clicks and the. 00:52:03.736 --> 00:52:05.496 Views thank you everybody. 00:52:06.116 --> 00:52:09.736 Maybe we should pull up advantage I think. 00:52:09.736 --> 00:52:10.816 We should yeah let's do it. 00:52:10.816 --> 00:52:15.716 So adversaries comes in here with the 1701 sets which maybe we should have an 00:52:15.716 --> 00:52:19.936 exception in the script for that one I don't know I officially volunteer to 00:52:19.936 --> 00:52:23.256 help with blue faults sounds like something I've been wanting to do for a while 00:52:23.256 --> 00:52:25.556 and Rust is my preferred language. 00:52:25.956 --> 00:52:26.296 Oh, really? 00:52:26.776 --> 00:52:29.396 Send me a message on Matrix or Signal if you want to discuss. 00:52:29.876 --> 00:52:32.736 Very nice. Well, I think we should. Signal, huh? Let's hook up on Signal. 00:52:32.936 --> 00:52:34.796 Whoa. Are you feeling okay? 00:52:34.876 --> 00:52:37.836 It'll be my... I know. It'll be my second person on Signal ever. 00:52:38.376 --> 00:52:40.916 You haven't added me yet. I feel so... 00:52:40.916 --> 00:52:44.756 Dude, you haven't added... You are the Signal ambassador in the friend group here. 00:52:44.756 --> 00:52:47.756 I didn't know you were on it. You were so against it for years. You were like. 00:52:48.316 --> 00:52:52.076 I ain't a gain it. I just didn't need it. I ain't a gain it. I ain't a gain it. 00:52:52.076 --> 00:52:52.876 All right. We'll talk later. 00:52:53.016 --> 00:52:53.276 I just didn't need it. Thank you. 00:52:54.485 --> 00:52:58.825 So thank you. I did get a couple of PRs. 00:52:58.925 --> 00:52:59.225 Nice. 00:52:59.385 --> 00:53:03.185 And I got an issue or two, and I resolved a couple of them. I think the hot 00:53:03.185 --> 00:53:04.385 dog colors are still outstanding. 00:53:04.585 --> 00:53:05.405 Yeah, what's the deal with that? 00:53:05.525 --> 00:53:09.705 I'll be getting around to that, I'm sure. I'm sure, yeah. What does GitHub do 00:53:09.705 --> 00:53:12.865 with issues or PRs that sit around for a while? 00:53:13.025 --> 00:53:15.905 Is there like a stale bot that comes around and. 00:53:15.905 --> 00:53:15.905 Cleans them up? 00:53:16.025 --> 00:53:19.225 I mean, you can set those things up. Or I could push some updates. 00:53:19.445 --> 00:53:23.705 Oh! You want to just ride it yourself? You feel like doing a little rusty-roo? 00:53:24.045 --> 00:53:25.505 I knew it would come to this. 00:53:25.885 --> 00:53:27.045 I could get some help. 00:53:28.865 --> 00:53:32.465 All right. Thank you, everybody, who boosted this episode to support us directly. 00:53:32.785 --> 00:53:36.205 We had 24 of you stream them, Sats, as you listened to the show. 00:53:36.385 --> 00:53:41.945 And you all collectively stacked 35,406 Sats. This is one of those nice boosts in this episode. 00:53:42.165 --> 00:53:46.105 And when you combine that with our boosters, who also sent us a message, 00:53:46.425 --> 00:53:50.905 this episode stacked 212,809 Sats. 00:53:51.385 --> 00:53:55.905 Not bad at all. Fountain FM is going from win to win, making it easier and easier 00:53:55.905 --> 00:53:58.585 to boost. There's also some self-hosted options. 00:53:58.745 --> 00:54:04.245 Just look into AlbiHub, and you can find a bunch of great apps at newpodcastapps.com. 00:54:04.245 --> 00:54:05.925 Thank you, everybody, who supported this episode. 00:54:17.968 --> 00:54:22.428 Okay, this week we have two picks, and I'm pretty tickled with both of them. 00:54:23.708 --> 00:54:27.988 And Wes, you've been playing around with Pocket TTS. 00:54:28.608 --> 00:54:35.188 Yes, 100 million parameter model, text-to-speech, voice cloning abilities, 00:54:35.388 --> 00:54:38.688 small enough to run in real time easily on your laptop's CPU. 00:54:38.888 --> 00:54:42.628 On the CPU. So this is voice cloning anyone can play with. 00:54:42.768 --> 00:54:43.228 That's right. 00:54:43.448 --> 00:54:46.388 So probably should set expectations because you said it's kind of a smaller... 00:54:46.388 --> 00:54:49.348 Yes, that's right. It's not like a giant thing, 100 million parameter model. 00:54:49.528 --> 00:54:51.988 It's pretty small by modern standards. 00:54:52.168 --> 00:54:54.548 But that's what lets it run on your laptop CPU. 00:54:54.708 --> 00:54:54.828 Yeah. 00:54:55.128 --> 00:54:58.028 And it's just a PIP or UV install away. 00:54:58.268 --> 00:55:03.348 So here's a little comparison just to set the expectations. We're going to play a clip of Editor Drew. 00:55:03.688 --> 00:55:09.988 First will be the original Drew. And second will be the Pocket TTS version of Drew. 00:55:10.228 --> 00:55:11.328 I get so mad. 00:55:11.648 --> 00:55:14.468 All right. That's real Drew. And here is Pocket Drew. 00:55:14.688 --> 00:55:16.188 I get so mad. 00:55:16.508 --> 00:55:18.588 Right. And Wes, why don't you say it? 00:55:19.688 --> 00:55:20.528 I get so mad. 00:55:20.928 --> 00:55:22.528 I get so mad. 00:55:22.808 --> 00:55:24.288 I get so mad. 00:55:24.528 --> 00:55:25.608 Brent, why don't you give it a go? 00:55:25.988 --> 00:55:27.068 I get so mad. 00:55:28.208 --> 00:55:29.968 I get so mad. 00:55:30.368 --> 00:55:31.948 Brent says, I think, the furthest off. 00:55:32.108 --> 00:55:33.188 I get so mad. 00:55:34.428 --> 00:55:36.028 I get so mad. 00:55:36.408 --> 00:55:38.888 Okay, here's Chris. I get so mad. 00:55:39.547 --> 00:55:42.207 I get so mad. I get so mad. 00:55:42.407 --> 00:55:43.187 I like that one. 00:55:43.267 --> 00:55:45.947 That's actually kind of fun. I like the little extra it added in there. 00:55:46.527 --> 00:55:49.247 So you can play around with it and get different results. And you probably weren't 00:55:49.247 --> 00:55:50.667 giving it like the most amazing sample. 00:55:50.847 --> 00:55:55.167 No. So this was literally, I just took, Editor Drew is kind enough to clip and 00:55:55.167 --> 00:55:57.707 save our predictions so that we have them to review for next year. 00:55:57.807 --> 00:55:57.967 Yeah. 00:55:58.127 --> 00:56:01.747 I took the smallest or shortest samples of those, one for each of us. 00:56:01.807 --> 00:56:05.447 So it's like 30 seconds or less of audio. And that's all it got is a sample. 00:56:05.787 --> 00:56:07.147 Literally a one sentence thing. 00:56:07.307 --> 00:56:09.207 Yeah. But pretty neat. and all 00:56:09.207 --> 00:56:13.607 on your laptop cpu right so that's pretty cool too just a little python. 00:56:13.607 --> 00:56:17.547 Yeah it has a ui you can do and then um it has an interface you just upload 00:56:17.547 --> 00:56:21.087 your sample wave you do probably want to um you know a few things like make 00:56:21.087 --> 00:56:24.107 it 16-bit depth and there's a few other things that are nice for these kinds 00:56:24.107 --> 00:56:28.467 of generative generative audio in particular but real easy upload in the ui 00:56:28.467 --> 00:56:32.427 has a text box to type in what you want then you hit generate and it'll stream it right back to you. 00:56:32.427 --> 00:56:35.827 Yeah you could yeah you could put anything right now and do it live and they 00:56:35.827 --> 00:56:39.007 can render it in the browser. That's a pretty good demo right there. 00:56:39.127 --> 00:56:40.127 It's small enough to fit in your pocket. 00:56:40.407 --> 00:56:42.487 There you go. Just played that live in the web page. 00:56:42.647 --> 00:56:44.987 Yeah, and it's got, of course, built-in ones that you can use. 00:56:45.107 --> 00:56:50.947 If you do want to do the voice cloning on your own, then you do need to have a Hugging Face account. 00:56:51.067 --> 00:56:53.887 They are open models, but you have to sign in and do a little agreement that 00:56:53.887 --> 00:56:58.327 says you're not going to abuse them or use it for whatever variety of nefarious things. 00:56:58.547 --> 00:56:58.867 Okay. 00:56:59.167 --> 00:57:03.287 But it's only like 250 meg download, and you're ready to do voice cloning. 00:57:03.527 --> 00:57:07.087 So good. So this next pick is for- Also. 00:57:07.207 --> 00:57:13.207 I just want to say, this opens the absurd possibility of having Chris or recording 00:57:13.207 --> 00:57:17.187 your own voice and then having it read your own audio books or reading audio books back for you. 00:57:18.607 --> 00:57:21.387 Chris would like his audio books read as Shatner. 00:57:21.607 --> 00:57:21.767 Okay. 00:57:21.767 --> 00:57:22.147 From now on. 00:57:22.287 --> 00:57:25.027 I thought, whoa, there you go. I would. But I thought of a scenario like, 00:57:25.167 --> 00:57:28.747 maybe if when my kids were young and I was traveling and I wanted to have some 00:57:28.747 --> 00:57:30.347 books for them that I was reading to them. 00:57:30.727 --> 00:57:31.287 Oh, yeah. 00:57:31.447 --> 00:57:34.207 I mean, is that weird? Maybe I might actually consider it if it was close. 00:57:34.687 --> 00:57:38.947 that could be kind of sweet we'll see or maybe it'd freak me out I'm not sure, 00:57:39.451 --> 00:57:43.111 All right, this next pick is for those of us that like to slap an Android tablet 00:57:43.111 --> 00:57:48.831 on the wall and make a Home Assistant dashboard or maybe a Frigate dashboard or whatever, Grafana. 00:57:48.971 --> 00:57:51.131 I don't know what you do. You got dashboards, dashboards for days. 00:57:51.431 --> 00:57:57.611 But the key of it is you just want this dedicated tablet that does nothing but show your dashboard. 00:57:58.031 --> 00:58:01.551 Maybe it has some settings for when the lights go out, it goes to sleep. 00:58:01.751 --> 00:58:06.831 It refreshes if the Wi-Fi goes out. And ideally, maybe you could even centrally 00:58:06.831 --> 00:58:10.511 manage some of the settings from like Home Assistant or an automation platform. 00:58:10.751 --> 00:58:13.691 And Fully Kiosk has served this role for many years. 00:58:13.851 --> 00:58:15.991 It's a great app. In fact, it's still a little better what I'm about to talk 00:58:15.991 --> 00:58:18.991 about, but it's commercial and it's not cheap. And when you start having five 00:58:18.991 --> 00:58:22.531 or six tablets over the years and you're paying like 30 bucks a tablet, 00:58:22.671 --> 00:58:24.551 you're like, is there a way to do this for free? 00:58:25.211 --> 00:58:29.691 Well, friends, let me tell you about WebView Kiosk. You can turn any Android 00:58:29.691 --> 00:58:33.551 device into a lockdown, full-page, full-screen kiosk. 00:58:33.791 --> 00:58:38.811 And yes, of course, it is open source. It's AGPL 3.0. 00:58:38.971 --> 00:58:44.231 So it's WebView kiosk, and you can get it directly from GitHub or FDroid or Google Play. 00:58:44.871 --> 00:58:47.951 And it works essentially like I just described. 00:58:48.051 --> 00:58:51.751 The way you do the remote management features is through MQTT, 00:58:52.051 --> 00:58:55.171 which I'm an MQTT pro now, so no problem for me. 00:58:55.351 --> 00:58:59.231 But once you hook up MQTT to this thing, you don't have to. But once you do, 00:58:59.571 --> 00:59:03.591 you can monitor events, you can update settings remotely, you can execute commands 00:59:03.591 --> 00:59:06.111 on the tablet, and of course you can build automations. 00:59:06.351 --> 00:59:10.911 So you do need a mosquito broker, like a mosquito or something like that. And it's really great. 00:59:11.511 --> 00:59:14.391 And it has all kinds of permissions, so you can access the camera feed if you 00:59:14.391 --> 00:59:17.211 want. You can make sure it's the foreground application. 00:59:17.551 --> 00:59:20.951 You could even have the, you could access the speakers and play audio on it. 00:59:21.211 --> 00:59:24.631 It's very feature complete. It's not, I would say it's not fully, 00:59:24.671 --> 00:59:25.931 it's not a fully kiosk killer. 00:59:28.042 --> 00:59:32.162 WebView-Kiosk, we'll have a link in the show notes, is a free way to get a lot of the functionality. 00:59:33.302 --> 00:59:37.762 And for me, I like to watch for Black Friday, and I try to snipe the cheapest, 00:59:38.142 --> 00:59:40.462 best 11-inch or so Android tablet I can get. 00:59:40.582 --> 00:59:44.482 And for a couple of years in a row, I've picked up like an $85 tablet that lasts 00:59:44.482 --> 00:59:48.382 me two, three years running a piece of software, formerly fully Kiosk, 00:59:48.442 --> 00:59:49.482 but probably this going forward. 00:59:49.942 --> 00:59:53.082 And this is how I am then in each different areas. 00:59:53.402 --> 00:59:58.402 I have dashboards for that area of the home. and this is how most of my interactions 00:59:58.402 --> 01:00:00.482 and my family's interactions with Home Assistant are. 01:00:00.962 --> 01:00:03.982 Yeah, and I mean, it seems I haven't tried it yet, but when I saw this floating 01:00:03.982 --> 01:00:05.182 around, I thought you might like it. 01:00:05.282 --> 01:00:05.622 Yeah, good for that. 01:00:05.622 --> 01:00:09.122 It's 100% Kotlin, so it's, I think, probably pretty snappy and new. 01:00:09.302 --> 01:00:12.102 And probably would work even on some of these slower, like Android Fire. 01:00:12.302 --> 01:00:17.242 Yeah, and it's AGPL 3.0. Pocket TTS is MIT, by the way. 01:00:17.382 --> 01:00:20.522 Yes. So we'll have links to that in the show notes. 01:00:20.682 --> 01:00:24.322 Now, what'd you say, show notes, Chris? Yes. In fact, things are copiously linked, 01:00:24.322 --> 01:00:30.202 including the hardware we talked about and all of that at linuxunplugged.com slash 650. 01:00:31.542 --> 01:00:36.602 Halfway to the big 700, so we'd love it if you found time to join us live and 01:00:36.602 --> 01:00:38.182 make it a Linux Tuesday on a Sunday. 01:00:38.382 --> 01:00:41.682 That's right, 10 a.m. Pacific, 1 p.m. Eastern over jblive.tv. 01:00:45.781 --> 01:00:50.061 And now for our members, we have a video version of the show in their feed. 01:00:50.061 --> 01:00:52.161 It is just part of the podcasting tutorial spec. 01:00:52.361 --> 01:00:55.881 So it is the same RSS feed. You don't have to resubscribe or change anything. 01:00:56.161 --> 01:00:59.781 If you have a podcasting tutorial app like Fountain or Podverse that supports 01:00:59.781 --> 01:01:02.181 video, you now have a video version of the show. 01:01:02.321 --> 01:01:04.901 And we're not going to mess up the audio version one little bit. 01:01:04.961 --> 01:01:06.161 It's still our top priority. 01:01:06.321 --> 01:01:10.281 It's just an option that's available for our members. Or you can catch it over at jblive.tv. 01:01:10.501 --> 01:01:13.461 You know, there's other things in that feed too, like extra data, 01:01:13.661 --> 01:01:14.821 say transcripts or whatnot. 01:01:14.981 --> 01:01:18.681 Wes. Oh, yeah, we got transcripts, diarizations, you know, who's saying what 01:01:18.681 --> 01:01:22.781 silly thing. We've also got cloud chapters, so you can go right to your favorite segment. 01:01:23.021 --> 01:01:26.401 Yeah, that's nice, too. All right, you know, you don't want to hear about the 01:01:26.401 --> 01:01:28.621 pick? That's fine. Actually, the picks are great. Those are bangers. 01:01:28.621 --> 01:01:30.941 Yeah, that's on you, but maybe jump right to the picks. 01:01:31.261 --> 01:01:31.581 Yeah. 01:01:32.341 --> 01:01:34.421 Who cares about our printer problems? Get to the picks. 01:01:35.541 --> 01:01:39.221 All right, thank you so much for tuning in this week's episode of Your Unplugged Program. 01:01:39.621 --> 01:01:42.321 This is a fun one to get out in the field and fix somebody's problems for the 01:01:42.321 --> 01:01:45.601 real, real like you know real world stuff even if it was the wife it was a good 01:01:45.601 --> 01:01:47.401 dip in the toe in the water yeah. 01:01:47.401 --> 01:01:48.241 She has high standards. 01:01:48.241 --> 01:01:52.381 And happy wife happy life that keeps the show going too like i said links over 01:01:52.381 --> 01:01:56.901 at linuxunplugged.com and then we got a bunch of great shows over at jupiterbroadcasting.com 01:01:56.901 --> 01:02:01.621 check out the launch with angela and myself and sometimes brent too the. 01:02:01.621 --> 01:02:03.221 Best way to check it out is to call. 01:02:03.221 --> 01:02:07.021 Yeah that's true weeklylaunch.rocks for that thank you so much for joining us 01:02:07.021 --> 01:02:10.901 on this week's program, and we'll see you right back here next Tuesday, 01:02:11.321 --> 01:02:13.701 which is really a Sunday.