WEBVTT 00:00:11.489 --> 00:00:16.169 Hello, friends, and welcome back to your weekly Linux talk show. My name is Chris. 00:00:16.369 --> 00:00:17.129 My name is Wes. 00:00:17.369 --> 00:00:18.329 And my name is Brent. 00:00:18.749 --> 00:00:22.269 Hello, gentlemen. Coming up on the show today, we'll tell you about a homemade 00:00:22.269 --> 00:00:25.269 tool that we just built that I think you're going to like. 00:00:25.409 --> 00:00:28.509 And then it's time for config confessions. 00:00:28.709 --> 00:00:34.649 From finely tuned setups to total config carnage, we're going to review some listener home labs. 00:00:34.829 --> 00:00:36.809 Then we'll round it out with some great shout outs, some picks, 00:00:37.009 --> 00:00:41.069 and more. So before we get into all of that, we have to say time-appropriate 00:00:41.069 --> 00:00:43.409 greetings to a packed mumble room. Hello, virtual lot. 00:00:44.109 --> 00:00:48.029 Hello. Hello. Hello. Hello, everybody. 00:00:49.269 --> 00:00:54.549 Goodness. We got a big one today. Hello. This is our last episode in the studio 00:00:54.549 --> 00:00:57.309 before we hit the road for Texas Linux Fest. 00:00:57.829 --> 00:01:02.889 So I want to say a good morning to our friends over at Defined Networking. 00:01:03.029 --> 00:01:09.649 Go to Defined.net slash unplugged Nebula. It's a decentralized VPN built on the Nebula platform. 00:01:10.089 --> 00:01:13.649 I don't know, Wes, maybe you were hip to this first between the two of us. 00:01:13.769 --> 00:01:19.709 You were on this like a bonnet when Nebula shipped. It's really something special. 00:01:19.929 --> 00:01:25.589 It's optimized for speed. And what that means is, like on your mobile device, less battery usage. 00:01:25.809 --> 00:01:30.449 On your servers, on your laptops, on your desktops, less traffic. 00:01:30.529 --> 00:01:32.669 It also means there's a simplicity to it. 00:01:32.769 --> 00:01:35.469 And they're using industry-leading security that you can trust. 00:01:35.469 --> 00:01:39.489 And unlike traditional VPNs, Nebula has a decentralized design, 00:01:39.489 --> 00:01:43.289 so your network stays resilient if you're using their managed system or you're 00:01:43.289 --> 00:01:45.989 building yourself for your home lab or a global enterprise. 00:01:46.829 --> 00:01:52.169 I mean, we're talking massive, massive corporations and organizations already use Nebula. 00:01:52.369 --> 00:01:57.749 It was developed in 2017 to get Slack connected across their various data centers around the world. 00:01:57.989 --> 00:02:01.689 So it was engineered for scale and performance from day one. 00:02:02.289 --> 00:02:05.929 Nothing else is like Nebula. And when we get back from Texas Linux Fest, 00:02:06.129 --> 00:02:08.969 I am looking forward to a fabulous network makeover. 00:02:09.169 --> 00:02:11.589 It might just be Wes and I, but we're going to do it. 00:02:12.209 --> 00:02:17.329 Brent has another tale to tell us. But we're going to redo a network from a 00:02:17.329 --> 00:02:25.349 design that's about five years old and modernize it with new DNS and a Nebula mesh network. 00:02:25.509 --> 00:02:28.289 And you can take advantage of Nebula if you want to build it in your home lab 00:02:28.289 --> 00:02:34.509 or get started with 100 hosts absolutely free, no credit card required on Managed Nebula. 00:02:34.649 --> 00:02:36.929 Go to define.net slash unplugged. 00:02:37.149 --> 00:02:40.889 Redefine your VPN experience today. Support the show and try it out. 00:02:41.249 --> 00:02:44.029 It's define.net slash unplugged. 00:02:46.042 --> 00:02:50.162 Yes, Texas Linux Fest, October 3rd through the 4th at the Commons Conference 00:02:50.162 --> 00:02:54.322 Center, is just about five days away. 00:02:54.522 --> 00:02:57.642 And our buddy Carl George joins us to celebrate. Hey, Carl! 00:02:58.102 --> 00:02:58.762 Howdy, y'all. 00:02:58.982 --> 00:02:59.322 Hey! 00:02:59.542 --> 00:03:00.142 Hey, hey! 00:03:00.602 --> 00:03:04.502 How you feeling? Things are getting pretty close? You got like that pre-fest 00:03:04.502 --> 00:03:07.122 jitter anxious stuff, or are you feeling confident? 00:03:07.222 --> 00:03:07.302 Absolutely. 00:03:07.522 --> 00:03:11.062 You do? You're supposed to be like, no, it's all handled, man. It's great. 00:03:12.122 --> 00:03:14.522 Yes, yes, everything's lining up perfectly. 00:03:15.142 --> 00:03:16.162 No problems at all. 00:03:16.442 --> 00:03:20.262 I mean, it's a community-run event, right? It's not like there's a big corporation 00:03:20.262 --> 00:03:23.322 that has a team of people that run these things every year and they just come 00:03:23.322 --> 00:03:25.322 in and execute on some plan they already have. 00:03:26.342 --> 00:03:29.762 Correct. It's all volunteer run, so a lot of times, you know, 00:03:29.822 --> 00:03:32.562 stuff needs to happen and it's like, okay, well, I'll get to that this weekend 00:03:32.562 --> 00:03:34.482 when I'm not doing my day job and things like that. 00:03:34.602 --> 00:03:37.622 And it's at a new location. I imagine that's a pretty new, big variable. 00:03:38.702 --> 00:03:42.842 Yeah, being a new location, I was worried about, but thankfully this venue has 00:03:42.842 --> 00:03:46.282 been really nice to work with. So a little bit lower stress there. 00:03:47.102 --> 00:03:48.122 That's working out well. 00:03:48.782 --> 00:03:52.122 So I think one of the things we haven't been very clear about is people do need 00:03:52.122 --> 00:03:53.882 to register. There's a process there, right? 00:03:54.922 --> 00:03:59.502 Yes, sir. You can just go to the website, 2025.texaslinuxfest.org. 00:04:00.162 --> 00:04:02.022 There's a little link there to buy a ticket. 00:04:02.422 --> 00:04:05.482 Right now, the ticket prices are $75 for the main ticket. 00:04:05.882 --> 00:04:08.922 And there's a $100 ticket that will get you the swag pack. 00:04:09.262 --> 00:04:16.082 Ooh, swag pack. And we have a promo code JB15 will get you 15% off the ticket price, too. 00:04:16.762 --> 00:04:19.142 So that ain't too bad. Save a little money there. 00:04:20.222 --> 00:04:23.562 Carl, one of the things I'm concerned about is that you won't have time to take 00:04:23.562 --> 00:04:25.002 us to a new barbecue location. 00:04:25.222 --> 00:04:28.782 I mean, I still wouldn't mind going to Terry Black's, but I'm concerned you're 00:04:28.782 --> 00:04:31.742 going to be too busy to sneak out for a good barbecue. 00:04:32.962 --> 00:04:36.202 That is a concern of mine as well. Definitely not Terry Black's. 00:04:36.242 --> 00:04:39.242 That's going to be way too far from where the venue is. It's a little bit different 00:04:39.242 --> 00:04:40.442 part of town than last year. Yeah. 00:04:41.591 --> 00:04:46.311 There's a few other barbecue spots in the area. I'm going to try to go find some good barbecue. 00:04:46.771 --> 00:04:49.831 There's one that's really highly ranked called Interstellar Barbecue that's 00:04:49.831 --> 00:04:51.851 about 10 minutes away from the conference center. 00:04:52.031 --> 00:04:56.051 I'm going to try and go out there on Thursday and try my luck there and wait in line. 00:04:56.771 --> 00:04:59.371 Now, I don't know. Maybe we could talk to somebody at the fest and say, 00:04:59.411 --> 00:05:02.691 look, it's really important that Carl takes this time because it's fest outreach 00:05:02.691 --> 00:05:05.111 and its relations with the media. 00:05:05.251 --> 00:05:08.211 And so he's got to take them out and show them a good time. 00:05:08.231 --> 00:05:11.611 So that way they talk really well about the fest. I mean, you know, 00:05:11.671 --> 00:05:14.451 we can reach out and, you know, suggest that to somebody if it carves a little time. 00:05:14.631 --> 00:05:17.091 But I support this idea. 00:05:17.371 --> 00:05:19.651 We have lunch planned. I don't know if you can make it on Saturday. 00:05:19.651 --> 00:05:24.671 We have our birthday lunch during the Saturday lunch break. 00:05:25.231 --> 00:05:27.951 So if you're around, you're totally welcome to join us for that, too. 00:05:28.451 --> 00:05:29.791 Of course. I'm going to try to make it. 00:05:30.311 --> 00:05:32.811 Well, I'm excited, Carl. Can't wait to see you in just a few days. 00:05:33.411 --> 00:05:36.351 You may end up having lunch with Brent. He's making good progress. 00:05:36.571 --> 00:05:40.111 So hope a whole bunch of the community can come out there to the event. 00:05:40.511 --> 00:05:46.131 There's the Texas Linux Festival matrix room on the JB server that a few people 00:05:46.131 --> 00:05:48.951 are chatting about, you know, either going to a conference for the first time 00:05:48.951 --> 00:05:52.671 or they're conference regulars, but they haven't been to Texas Linux Fest before. 00:05:53.011 --> 00:05:55.751 So hoping to see a lot of the JB folks out there. 00:05:56.071 --> 00:06:00.551 Yep, that Texas Linux Fest chat is a good one. If you want details about our 00:06:00.551 --> 00:06:03.151 lunch event, we'll have links to that in the show notes. Of course, 00:06:03.171 --> 00:06:04.531 links to Texas Linux Fest, too. 00:06:04.731 --> 00:06:05.591 I'm getting excited. 00:06:05.891 --> 00:06:09.071 Yeah. I'm hoping you'll have some pocket meat, too. That's right. 00:06:09.331 --> 00:06:10.371 Don't you think, Brent? That's important. 00:06:10.511 --> 00:06:15.551 I mean he always gets me when i go anywhere he's just like hey hey hey vegan 00:06:15.551 --> 00:06:20.231 hey i know you only like eat meat a couple times a year and like do you want 00:06:20.231 --> 00:06:22.871 some out of my pocket it's nice and warm and. 00:06:22.871 --> 00:06:23.591 Brent always says yes, 00:06:25.632 --> 00:06:28.472 The warmth helps, you know, makes it a little softer. 00:06:28.632 --> 00:06:32.732 We did want to try another little piece of software you've been excited about, 00:06:32.812 --> 00:06:36.012 Chris, at the meetup, but also at the conference. 00:06:36.212 --> 00:06:38.232 You wanted to get people to try BitChat. 00:06:38.612 --> 00:06:42.512 Yeah, I think especially once we're either in route or on the ground, 00:06:42.512 --> 00:06:43.992 because it doesn't require a server. 00:06:44.752 --> 00:06:48.652 It doesn't really require creating an account. It's all location based. 00:06:49.152 --> 00:06:52.852 And when you're at the venue, it'll all be Bluetooth based. So it should also 00:06:52.852 --> 00:06:55.532 survive like Wi-Fi issues or if you don't have cellular data. 00:06:56.052 --> 00:06:59.132 and we're going to talk more about bit chat but i do think it's worth mentioning here 00:06:59.132 --> 00:07:02.272 that we are planning to use it to sort of coordinate with folks on the 00:07:02.272 --> 00:07:04.932 ground for like the lunch day or people have 00:07:04.932 --> 00:07:09.072 questions things like that we're going to be popping into bit chat bit chat 00:07:09.072 --> 00:07:14.552 which we'll have links to that in the show notes too but let's get into it let's 00:07:14.552 --> 00:07:19.592 get into the show gentlemen we are like i said just five days away from texas 00:07:19.592 --> 00:07:23.612 linux fest and brent is already on the road i, 00:07:24.572 --> 00:07:30.292 I suggested that by this point I would be able to guess if he has a chance of beating Wes and I, 00:07:30.472 --> 00:07:36.632 and I'm feeling a little nervous, and I know so far it's been pretty adventurous, 00:07:36.712 --> 00:07:41.612 so now I'm gambling on some more adventure, I think, in order to beat you. How's it going? 00:07:41.832 --> 00:07:45.712 Where are you right now, Brent? What's going on? You're already well into the trip. 00:07:48.532 --> 00:07:52.832 I use the tauntings that you've been doing for the last week of saying that 00:07:52.832 --> 00:07:58.752 i would arrive last to get a head start yesterday somehow i managed to drive, 00:08:00.352 --> 00:08:02.492 700 miles or something like that. 00:08:02.492 --> 00:08:06.792 How did that happen don't hurt yourself how are you even here today. 00:08:06.792 --> 00:08:12.152 I wanted to give myself a really really really good head start you wanted to. 00:08:12.152 --> 00:08:13.512 Put the fear of god in us and you did. 00:08:13.512 --> 00:08:20.132 Yeah how's it going over there guys i'm i hear you're not leaving till monday so. 00:08:20.132 --> 00:08:30.232 Uh as of right now brent is um about 800 miles for uh no 945 miles from austin 00:08:30.232 --> 00:08:33.712 as the crow flies and as the crow flies and west under a. 00:08:33.712 --> 00:08:37.252 Thousand that that's what i felt like that was my marker it's like okay if he crosses that. 00:08:37.252 --> 00:08:42.032 Already you and i are about 2300 miles as as it goes uh so. 00:08:42.032 --> 00:08:45.032 I'm basically 00:08:45.032 --> 00:08:47.912 to you know if you want to situate yourself i'm just a little bit 00:08:47.912 --> 00:08:51.412 south of chicago currently okay and i'm 00:08:51.412 --> 00:08:57.232 i think in a really special place uh it just so happened i got invited by one 00:08:57.232 --> 00:09:04.912 of our absolute baller boosters to hang out at his place for the show so um 00:09:04.912 --> 00:09:10.212 i'm sitting here beside adversary 17 can you believe it. 00:09:10.212 --> 00:09:13.352 Hello adversaries thank you for helping our boy Brent. 00:09:13.492 --> 00:09:17.332 Yes. Wow. How cool is that? That, you know, a little shout out there. 00:09:20.550 --> 00:09:26.010 That's pretty cool because, you know, I felt like Brent was visiting a celebrity. He was stopping by. 00:09:26.550 --> 00:09:29.230 We're jealous. You're at Adversary's house right now? 00:09:29.410 --> 00:09:30.030 No way. 00:09:31.010 --> 00:09:32.930 That's pretty great. And then he's hooking you up, you know, 00:09:33.010 --> 00:09:36.250 he got you on the internet, he got you a little spot to record. 00:09:36.690 --> 00:09:38.690 You refused his glorious ethernet. 00:09:38.950 --> 00:09:42.690 You have no idea, Chris. I got here and there was a little bit, 00:09:42.810 --> 00:09:45.190 you know, I'm driving a 30-year-old van, 00:09:45.430 --> 00:09:48.490 so, and me being me, as you guys know, like, 00:09:48.610 --> 00:09:52.070 maybe I'm a little behind the schedule that I was hoping for so i got 00:09:52.070 --> 00:09:55.390 in this morning just in time and and 00:09:55.390 --> 00:09:58.130 basically 10 minutes before they had to leave they had a thing 00:09:58.130 --> 00:10:01.010 this morning and uh there's like these 00:10:01.010 --> 00:10:05.910 beautiful little like handwritten notes all over the kitchen just like hey brent 00:10:05.910 --> 00:10:11.650 we set up a custom wi-fi network for you the name is you know linux unplugged 00:10:11.650 --> 00:10:15.550 with the episode number and you just connect to that if you need to there's 00:10:15.550 --> 00:10:20.050 coffee over there and everything you need there's ethernet on the desk here if you wait wait can we. 00:10:20.050 --> 00:10:25.910 Can we take a moment and appreciate that he stood up, a standalone AP titled 00:10:25.910 --> 00:10:29.330 after the episode just for this? Love that. 00:10:29.550 --> 00:10:34.190 Yeah, so if anyone in the area needs Wi-Fi, it's unplugged, 634, 00:10:34.210 --> 00:10:35.670 and Brent leaves a password. 00:10:37.290 --> 00:10:39.190 Yeah, act now before he tears it down. 00:10:40.170 --> 00:10:41.450 Limited time only. 00:10:41.930 --> 00:10:46.690 So I got to say, A, thank you for having me and reaching out and suggesting it. 00:10:46.690 --> 00:10:50.910 And because of the reach, um, you reach out like perfectly in time when I was 00:10:50.910 --> 00:10:54.390 sat down, you know, those last moments when you sit down and you're like, 00:10:54.490 --> 00:10:57.410 okay, I need to leave like in a couple hours, but there's still a couple of 00:10:57.410 --> 00:10:59.110 like final details I got to sort out. 00:10:59.710 --> 00:11:05.750 And then I got a message from you just saying, Hey, you want to like stay at 00:11:05.750 --> 00:11:08.010 my place maybe for Linux unplugged while you're here. 00:11:08.250 --> 00:11:10.450 And it was just such perfect timing. And now that we're here, 00:11:10.530 --> 00:11:13.050 it's working out beautifully. So thank you for having me in your home. 00:11:14.570 --> 00:11:15.270 It's a pleasure. 00:11:16.190 --> 00:11:20.790 And I think you needed that, Brent, because it was a bit rocky, 00:11:20.890 --> 00:11:22.870 right? It wasn't a super smooth start to the trip. 00:11:23.730 --> 00:11:28.550 Well, I'm learning, Chris, that if you have a van like this, 00:11:28.710 --> 00:11:30.610 which is, you know, adventures built in, 00:11:30.850 --> 00:11:37.750 the first day or so of a trip is really just ironing out all the uncertainties 00:11:37.750 --> 00:11:41.410 and the things you didn't plan for and the things that, you know, 00:11:42.310 --> 00:11:44.510 are going to happen to you whether you want them to or not. 00:11:45.430 --> 00:11:49.850 So I was something like three and a half hours into the trip and I stopped at 00:11:49.850 --> 00:11:53.270 Canadian Tire, as you do, you know, just before you cross the U.S. 00:11:53.370 --> 00:11:58.070 border and just to get a few little last-minute solar supplies. 00:11:59.370 --> 00:12:01.770 And then I realized I ran into an issue. 00:12:26.056 --> 00:12:29.736 Not a great start. Not a great start. And I love if you have headphones on, 00:12:29.856 --> 00:12:33.556 you'll hear Cosmo in the background yelling at him like, what are you doing, idiot? Get in the car. 00:12:34.456 --> 00:12:39.556 I have a photo basically of the moment when my mood changed drastically when 00:12:39.556 --> 00:12:43.336 I realized I had locked both my sets of keys in the van. 00:12:43.916 --> 00:12:44.836 With the two cats. 00:12:45.216 --> 00:12:48.616 Oh, yeah. I'm outside looking into the window and the cats are like, 00:12:48.676 --> 00:12:51.436 hey, how's it going? I haven't seen you in like 20 minutes. 00:12:51.736 --> 00:12:54.456 And I'm like, guys, can you get the door for me? 00:12:55.036 --> 00:12:58.376 just like paw at the door would you uh luckily 00:12:58.376 --> 00:13:02.896 you know there are about five pretty easy ways to break into the van one of 00:13:02.896 --> 00:13:06.656 them i taped up because that one seemed too easy but uh so i was able to get 00:13:06.656 --> 00:13:09.716 in in like two minutes so a modern vehicle would have been like that would have 00:13:09.716 --> 00:13:15.936 been the end of the day yeah but i gotta tell you an old van it's got quirks and perks easy. 00:13:15.936 --> 00:13:21.876 Access wow so so then then i suppose it's just get down some distance right 00:13:21.876 --> 00:13:25.116 get across the border which by the way, kind of a stressful thing to happen 00:13:25.116 --> 00:13:26.656 right before you cross the U.S. border. 00:13:26.876 --> 00:13:31.496 Tell me about it. Hey, you were worried about crossing the border because basically 00:13:31.496 --> 00:13:37.576 like, this vehicle is registered in your name and I'm driving it across the 00:13:37.576 --> 00:13:40.516 border on the complete other side of the continent. 00:13:41.476 --> 00:13:43.076 How did you think it was going to go? 00:13:43.376 --> 00:13:48.576 I wasn't sure. I figured because you got in it was probably going to be okay 00:13:48.576 --> 00:13:51.616 getting back in since it's registered to a U.S. 00:13:51.696 --> 00:13:57.416 citizen, but what I'm So I'm a little, it's like a little, they kind of have 00:13:57.416 --> 00:13:58.436 to wonder a little bit, like the 00:13:58.436 --> 00:14:02.576 names don't match, the residency doesn't match. So was it okay? Did it go? 00:14:03.536 --> 00:14:06.996 Well, I wasn't too sure which question they would ask about the van, 00:14:07.116 --> 00:14:08.976 because like the, you know, the van, it's. 00:14:10.176 --> 00:14:11.756 There's a lot of questions you could ask. 00:14:12.016 --> 00:14:13.056 Is that a meth lab? 00:14:13.296 --> 00:14:14.856 How many cats you got in there? 00:14:14.956 --> 00:14:18.196 Hey, meth lab. It's like one step up from a meth lab. 00:14:18.256 --> 00:14:19.196 I'm kidding. I'm kidding. 00:14:19.376 --> 00:14:22.676 Give me something. But it has an apocalyptic look to it, right? 00:14:22.676 --> 00:14:25.776 and uh the fact that i pull up in this thing and also 00:14:25.776 --> 00:14:31.576 i am canadian but i'm driving a vehicle register in the u.s is kind of so i 00:14:31.576 --> 00:14:34.436 wondered what they were going to ask and basically asked me one question it 00:14:34.436 --> 00:14:42.376 felt like a trivia question he said what is the state plate on this vehicle 00:14:42.376 --> 00:14:44.556 like which state is it registered to, 00:14:45.995 --> 00:14:49.315 That is not the question I expected. Of course, I knew the answer, 00:14:49.555 --> 00:14:51.215 which means I probably didn't steal it. 00:14:51.675 --> 00:14:54.375 But that was the only question he asked about the van. I was like, 00:14:54.475 --> 00:14:57.055 oh, wow. A, I didn't expect that. B, that was really easy. 00:14:57.235 --> 00:14:59.795 Well, there you go. Hot tip it, everybody. If you ever steal a vehicle, 00:14:59.975 --> 00:15:01.415 memorize where the plates are. 00:15:01.495 --> 00:15:03.475 Yeah, yeah, yeah, exactly. Both plates. 00:15:03.715 --> 00:15:07.275 I mean, I'm damn impressed. You put down some serious miles. 00:15:07.675 --> 00:15:11.415 So you must have slept once you got just inside the States? 00:15:11.655 --> 00:15:15.375 Well, that would have been the reasonable thing to do. I decided since it was 00:15:15.375 --> 00:15:19.835 A, beautiful out, and B, there was seemingly no traffic at all, 00:15:19.915 --> 00:15:21.675 I thought this is my opportunity. 00:15:22.235 --> 00:15:27.715 So I put down miles until I couldn't stay awake anymore, basically. 00:15:28.015 --> 00:15:35.195 I know of nothing that motivates you more than proving Wes and I wrong. Yeah? Seriously. 00:15:36.775 --> 00:15:38.715 He's going to be in Austin on Wednesday. 00:15:38.855 --> 00:15:39.315 I know! 00:15:39.315 --> 00:15:42.195 Like that was driving 00:15:42.195 --> 00:15:45.135 day one of the trip and i'd say okay i locked myself out 00:15:45.135 --> 00:15:48.095 of the van uh which isn't so good but 00:15:48.095 --> 00:15:52.235 i made some distance so yeah success but 00:15:52.235 --> 00:15:55.655 there are still like three to four 00:15:55.655 --> 00:16:04.455 days left of this so anything can go wrong and well we'll see but uh man i gotta. 00:16:04.455 --> 00:16:09.355 Tell you after sleeping for three hours in the middle of nowhere and then pulling 00:16:09.355 --> 00:16:15.355 up to just a wonderful listener's place. It was just such a warm welcome. 00:17:48.875 --> 00:17:52.395 Some real value. I mean, you know, think about, too, from a logistics standpoint, 00:17:53.115 --> 00:17:55.395 Brett needs to be somewhere with reliable internet, reliable power. 00:17:55.575 --> 00:17:58.315 You can't even get that from most Airbnbs and hotels these days. 00:17:58.515 --> 00:17:59.435 That's so true. 00:17:59.995 --> 00:18:01.275 Yeah. Best audience ever. 00:18:01.535 --> 00:18:06.215 Yeah. With that said, I had a typical colonel also reach out and say, 00:18:06.295 --> 00:18:08.495 Hey, I heard you bought a solar panel. 00:18:08.655 --> 00:18:12.375 Like, if you're cruising by, I can help you install it or fix it or whatever. 00:18:12.615 --> 00:18:15.895 So it didn't quite work out for timing yesterday to see each other. 00:18:15.895 --> 00:18:19.535 But on the way back, I might stop in and don't tell Jeff, but I might get a 00:18:19.535 --> 00:18:25.495 solar upgrade or like, you know, get some proper less jank, let's say. So we'll see. 00:18:26.015 --> 00:18:32.195 That's exciting. Yeah. All right. Well, Wes and I, we hit the road tomorrow 00:18:32.195 --> 00:18:37.915 morning and we have a little bit of distance to catch up, but we are in a lean 00:18:37.915 --> 00:18:38.835 and mean and nimble vehicle. 00:18:39.195 --> 00:18:44.475 And I'm familiar with the route. So I'm fairly, well, I'm not confident at all 00:18:44.475 --> 00:18:46.355 that we'll catch up. But I think we'll make good time. 00:18:46.695 --> 00:18:50.455 That is, you know, victory is a secondary target. 00:18:50.595 --> 00:18:51.995 Right, right. I mean, maybe. 00:18:52.435 --> 00:18:53.655 Linux, you know, Texas Linux. 00:18:54.015 --> 00:18:58.295 You know, my weakness is, though, meeting up with listeners. 00:18:58.295 --> 00:19:01.935 So I think if you convince enough listeners to be on my path, 00:19:01.975 --> 00:19:05.355 you can really slow me down here. So that's maybe the angle you could take. 00:19:05.475 --> 00:19:11.515 This is the way to go. That could happen to us as well. So we decided to build a tool. 00:19:11.735 --> 00:19:14.875 And this is pretty great. It's built on top of something we've covered on the 00:19:14.875 --> 00:19:19.955 show before, and we hope you'll take advantage of it over the next couple of weeks. 00:19:20.315 --> 00:19:26.595 And we have an official Texas tracker. Two teams, Team Bigfoot. That's Wes and I. 00:19:26.915 --> 00:19:28.715 That's right. Civic Northwest represent. 00:19:28.715 --> 00:19:32.655 Here we go. And then, of course, you've got Team Moose. 00:19:33.335 --> 00:19:36.655 That's Brent and the Cats. Brent's coming down the East Coast. 00:19:36.795 --> 00:19:40.155 We're coming down the West Coast, both headed for Austin. And we wanted a way 00:19:40.155 --> 00:19:44.815 where you could watch our progress, see our distance between each other and our distance to Austin. 00:19:45.435 --> 00:19:49.695 And there's lots of ways to build this, but we wanted something that would work great for the show. 00:19:49.815 --> 00:19:54.635 And so we needed a back end thing to kind of keep track of all of the logistics 00:19:54.635 --> 00:19:57.395 and the travel data and something we could report to. 00:19:57.855 --> 00:20:01.135 So we pulled out our old friend, the big D witch, Dara witch, 00:20:01.375 --> 00:20:04.975 which you might recall automatically can track your daily life. 00:20:04.975 --> 00:20:09.915 so that way you can go back in time and see everywhere you went and mark locations. It's pretty neat. 00:20:10.495 --> 00:20:12.695 It's kind of like the Google Timeline feature. 00:20:14.950 --> 00:20:16.670 Totally under your control and self-hosted. 00:20:16.870 --> 00:20:20.410 Yeah, well, we've started first playing with this sometime around our trip to 00:20:20.410 --> 00:20:21.910 Boston for Red Hat something. 00:20:22.090 --> 00:20:26.630 That's right. Episode 614, Self-Hosted Location Tracking. 00:20:27.170 --> 00:20:31.930 You can check that out, and we kind of go into more details about the project. 00:20:31.930 --> 00:20:34.870 But it's something that we've kind of become familiar with. 00:20:34.990 --> 00:20:40.790 I'm still using it every single day for my setup. I actually have it integrated with Home Assistant. 00:20:41.070 --> 00:20:45.210 And so I'm just reporting my location to Home Assistant. and then Home Assistant 00:20:45.210 --> 00:20:50.050 is relaying that to Darwich, which is really nice because it's just sort of one app on my phone. 00:20:50.490 --> 00:20:54.650 And then you get location and maps with lines of where you've been and hotspots. 00:20:55.110 --> 00:20:59.510 But maybe the most important part for our project, you get an API. 00:21:00.370 --> 00:21:03.810 And once we realized there was an API that we could poke at, 00:21:04.550 --> 00:21:06.150 well, I think Wes had a dream. 00:21:06.210 --> 00:21:10.090 He had a dream and he built us a front end to sit on top of that API. 00:21:10.610 --> 00:21:12.390 Yeah, well, maybe more like Vibe built. 00:21:13.930 --> 00:21:19.390 Yeah. I mean, give yourself some credit. Like you got to have an understanding 00:21:19.390 --> 00:21:21.150 of how to properly design these things. 00:21:21.350 --> 00:21:25.650 Right. Like if I had vibed this, it would have been a total piece of crap. So let's, you know. 00:21:26.330 --> 00:21:29.150 We'll get it. That's for later in the episode. yeah. 00:21:29.150 --> 00:21:30.790 It is yeah it is. 00:21:30.790 --> 00:21:33.870 But yeah but we have just like it's like a single page uh 00:21:33.870 --> 00:21:37.390 html just has like plain um embedded css 00:21:37.390 --> 00:21:40.730 and javascript uses leaflet js 00:21:40.730 --> 00:21:43.470 to do map rendering and then 00:21:43.470 --> 00:21:47.890 kind of just the main thing is that it's able to pull on the back end we have 00:21:47.890 --> 00:21:54.510 a little tiny container that just runs and sinks down a set of points from the 00:21:54.510 --> 00:22:01.290 big d which api and then we aggregate those and upload that to an S3 bucket and then... 00:22:02.554 --> 00:22:04.234 The JavaScript and the web page 00:22:04.234 --> 00:22:07.854 can just pull down the data from that and then just render on the map. 00:22:07.994 --> 00:22:11.514 And the end result is you get a real-time location, roughly, 00:22:11.694 --> 00:22:15.114 of where we are at, and you can see the path we have traveled. 00:22:15.394 --> 00:22:19.954 So you know if we're in your neck of the woods. And then the thing that Wes 00:22:19.954 --> 00:22:24.654 did that's a real kind of nice chef's kiss touch is he's automatically computed 00:22:24.654 --> 00:22:27.554 the BitChat geohash for our current location. 00:22:27.554 --> 00:22:32.094 And one of the things we're going to try to do is have BitChat running as we go down the road. 00:22:32.494 --> 00:22:35.854 In theory, although I don't know if it works 100%, but in theory, 00:22:36.034 --> 00:22:38.594 it will auto-switch locations as we go down the road. 00:22:38.814 --> 00:22:42.034 And so if we're in your location, we'll be in your local chat room. 00:22:42.254 --> 00:22:46.614 And you'll see the geohash of where we're at at the time listed on this tracker. 00:22:46.914 --> 00:22:51.054 And it's nice. It's clean. It also has a time range filter. You can replay some data. 00:22:51.514 --> 00:22:53.634 There's a couple of different view options in here. 00:22:54.134 --> 00:22:57.474 I'd really like it if you checked it out and followed along as we make our way 00:22:57.474 --> 00:22:58.594 down to Texas Linux Fest. 00:22:58.774 --> 00:23:02.454 It's texastracker.jupiterbroadcasting.com. 00:23:04.894 --> 00:23:07.394 texastracker.jupiterbroadcasting.com. It's pretty cool, Wes! 00:23:07.594 --> 00:23:12.414 And if you'd like, it is open source over on our GitHub, jupiterbroadcasting.com 00:23:12.414 --> 00:23:13.594 slash texastracker there. 00:23:13.874 --> 00:23:17.214 And, you know, if you want to make it better, it was vibe-coded, 00:23:17.334 --> 00:23:18.794 so surely there's lots that could be fixed. 00:23:18.874 --> 00:23:25.774 We would love that because our stinking plan is we could kind of stand this up for every big trip. 00:23:25.974 --> 00:23:29.334 You know, you relabel it the scale tracker or whatever it might be. 00:23:31.234 --> 00:23:34.894 And we could use it from time to time and other people could use it for their 00:23:34.894 --> 00:23:38.414 trips because what we're using to actually make it all work, 00:23:38.454 --> 00:23:44.034 and we'll put a link to this in the show notes for you, is we're just running a client on our phone. 00:23:44.694 --> 00:23:47.934 And there's a couple of options. Dara, which makes a client for iOS, 00:23:48.174 --> 00:23:50.414 but you just need something that can report to the big D. 00:23:50.414 --> 00:23:56.154 And so, Brent and the, well, anybody using an Android, I think should check 00:23:56.154 --> 00:24:00.454 out GPS Logger, which is a really lightweight GPS logging application we've 00:24:00.454 --> 00:24:01.574 actually talked about before. 00:24:01.574 --> 00:24:09.234 And it can just log your travel location to a, you know, a GPX file on your local device. 00:24:09.574 --> 00:24:12.034 Or it can report to an HTTP endpoint. 00:24:12.374 --> 00:24:15.874 Yeah, there's a little custom configuration you have to do. but the plus side 00:24:15.874 --> 00:24:19.274 of that is you can make it work with basically anything that can accept an HTTP 00:24:19.274 --> 00:24:20.614 request of some kind or another. 00:24:20.874 --> 00:24:25.314 So you can make it work with Darawich, which is what we're doing. 00:24:25.454 --> 00:24:29.114 And so that's communicating to Darawich and the API we're using to build the website. 00:24:30.394 --> 00:24:34.994 Anybody could do this. We're just doing a Docker Compose container for Darawich, 00:24:35.094 --> 00:24:39.214 and then Wes's project is posted on GitHub. It's pretty small on the dependency side. 00:24:39.834 --> 00:24:42.734 You need a way to store the file and all that kind of stuff. 00:24:43.916 --> 00:24:46.736 you could label it your own thing and have at it or send us some, 00:24:46.796 --> 00:24:51.416 you know, some fixes. This thing's pretty cool. And it's already using a bunch of great technology. 00:24:52.096 --> 00:24:55.576 And the way we can do it is we can turn our tracker on and off if we need to. 00:24:55.776 --> 00:25:00.656 So, you know, I'm going to start our tracker officially Monday after Wes and I are on the road. 00:25:01.276 --> 00:25:05.116 So if you check this as you're listening and our location isn't on the map yet, 00:25:05.316 --> 00:25:09.256 you only see Brent's location, then you're probably catching us just before we've hit the road. 00:25:09.356 --> 00:25:12.636 But if you check later in the day, Monday, you'll see where we're at. 00:25:13.356 --> 00:25:17.096 and you can follow along. You can see our geohash location so you can say hi 00:25:17.096 --> 00:25:20.056 and pop in. And the whole stack is really great. 00:25:22.096 --> 00:25:27.036 It's just such a cool set of technology from Darowich to the little thing you 00:25:27.036 --> 00:25:30.036 vibe coded to the BitChats stack. 00:25:31.396 --> 00:25:33.576 It's a lot of good little tools. I think that's what made it. 00:25:33.596 --> 00:25:33.856 Yes. 00:25:33.956 --> 00:25:36.316 Like, you know, we didn't have all week or anything to work on this. 00:25:36.416 --> 00:25:39.576 We basically just threw it together after the show last week. 00:25:39.676 --> 00:25:40.376 Yeah, in an evening. 00:25:40.936 --> 00:25:44.756 And so there's a lot of good stuff, I think as primitives, otherwise we would not have been able to. 00:25:45.016 --> 00:25:48.396 Yeah, and we've been playing it with the week and kind of testing on it. It's been great. 00:25:49.516 --> 00:25:54.036 Also, if you're interested in BitChat, don't sleep on it. We covered this weeks 00:25:54.036 --> 00:25:57.036 ago, and it's exploded since we've talked about it. 00:25:57.096 --> 00:26:02.116 It's had some major rewrites, and there's a lot of now really nice tools built around it. 00:26:02.356 --> 00:26:05.816 I'm going to link in the show notes to a guide, and I would really recommend 00:26:05.816 --> 00:26:09.196 you give it a peruse, look at some of the tools they link to, 00:26:09.336 --> 00:26:14.476 and try out BitChat. It's awesome, and in an emergency, it could be a life-saving tool. 00:26:14.596 --> 00:26:18.016 But it's also perfect for events where everybody's kind of at a location. 00:26:18.216 --> 00:26:20.456 And I'll just remind you, one of the neat things about BitChat, 00:26:20.756 --> 00:26:27.356 no login required, and it can switch between relay over IP or over Bluetooth mesh. 00:26:27.416 --> 00:26:32.136 So if you're at an event, everything can be just taken right there device to 00:26:32.136 --> 00:26:34.296 device. It's really great for that kind of stuff. 00:26:34.676 --> 00:26:40.276 So do go look at BitChat. you can find it at bitchat.free and I'll have a guide 00:26:40.276 --> 00:26:44.336 to bitchat in the show notes as well as a couple other links in there once we 00:26:44.336 --> 00:26:48.676 get to Austin we should be at geohash 9v6sb, 00:26:49.756 --> 00:26:53.276 I don't know if we can put that in the show notes or not but 9v6sb I believe 00:26:53.276 --> 00:26:57.156 is where we will be you pop in there and you chat with us it's going to be great, 00:26:57.616 --> 00:27:03.636 so the next time you hear our voices we'll be in Austin, Texas from the next episode for 635, 00:27:04.516 --> 00:27:05.356 better bring the gear. 00:27:08.356 --> 00:27:13.276 1Password.com slash unplugged. That's the number one password.com and it's unplugged 00:27:13.276 --> 00:27:15.116 in the classic lowercase style. 00:27:15.316 --> 00:27:19.256 Go take the first step to better security for your team by securing credentials 00:27:19.256 --> 00:27:23.396 and protecting every application, even unmanaged shadow IT. 00:27:23.616 --> 00:27:26.876 You want to go to 1Password.com slash unplugged to learn more. 00:27:27.076 --> 00:27:31.076 So this is the thing that I think is a clear and present reality. 00:27:31.076 --> 00:27:35.376 If you're in security or you're in IT, you already have a mountain of assets to begin with. 00:27:35.496 --> 00:27:37.976 You've different devices, different identities for the staff, 00:27:38.396 --> 00:27:41.476 all the different applications required to run the business. It's a lot. 00:27:42.337 --> 00:27:46.497 And there's a lot of security risks just there. But now there's also all of 00:27:46.497 --> 00:27:50.117 these additional different SaaS applications and different services that your 00:27:50.117 --> 00:27:52.197 end users want to do their job better. 00:27:52.397 --> 00:27:57.477 Well, you can conquer this mountain of security risks with 1Password Extended Access Management. 00:27:57.797 --> 00:28:01.517 It's a real problem. Over half of IT pros that were surveyed say this is one 00:28:01.517 --> 00:28:02.677 of their biggest challenges. 00:28:02.877 --> 00:28:06.657 And that's where Trellica by 1Password can help you discover and understand 00:28:06.657 --> 00:28:13.197 and learn about all of the apps your users are using, managed or not. Yeah, that's powerful. 00:28:13.457 --> 00:28:16.557 That's Trelica by 1Password. It inventories everything at your company. 00:28:16.697 --> 00:28:20.437 It has pre-populated app profiles, so you can kind of assess the risk right 00:28:20.437 --> 00:28:21.857 there in a dashboard with a report. 00:28:21.957 --> 00:28:27.477 It lets you manage and access who has what logins and also how you off-board 00:28:27.477 --> 00:28:31.017 people when that time comes. And then ultimately, if you need, 00:28:31.097 --> 00:28:32.277 it helps you optimize your spend. 00:28:32.357 --> 00:28:34.877 So you can eliminate redundancies, make sure you're not spending for multiple 00:28:34.877 --> 00:28:38.417 services for the same thing, for the same people, and ensure that your best 00:28:38.417 --> 00:28:41.777 practices are being followed across every app your employees use. 00:28:42.497 --> 00:28:45.697 Even shadow IT, which I used to be when I was a contractor, I'd plug in. 00:28:46.037 --> 00:28:49.097 I'd get on the network. And the other thing I always saw companies struggle 00:28:49.097 --> 00:28:55.597 with is a secure, standardized process and procedure to onboard or off-board employees. 00:28:55.857 --> 00:28:58.557 You want to make sure you're also meeting compliance goals. That's where Trellica 00:28:58.557 --> 00:29:02.337 by 1Password provides a complete solution for SaaS access governance. 00:29:02.357 --> 00:29:06.377 And it's just one of the ways extended access management helps teams strengthen 00:29:06.377 --> 00:29:08.357 compliance and security. 00:29:08.537 --> 00:29:12.017 You know 1Password and their award-winning password manager and how important 00:29:12.017 --> 00:29:14.717 good password hygiene is and how they've helped millions of users and hundreds 00:29:14.717 --> 00:29:15.697 of thousands of businesses. 00:29:17.244 --> 00:29:21.044 1Password Extended Access Management builds on all of that and so much more. 00:29:21.164 --> 00:29:25.704 They get regular third-party audits, they have the industry's largest bug bounty, 00:29:25.804 --> 00:29:28.104 and they exceed the standards set by various authorities. 00:29:28.444 --> 00:29:32.664 1Password is always taking it up a notch. So take the first step to better security 00:29:32.664 --> 00:29:36.604 for your team by securing credentials and protecting every application, 00:29:36.804 --> 00:29:38.344 even the unmanaged shadow IT. 00:29:38.544 --> 00:29:42.444 You need to go learn more at 1Password.com slash unplugged. 00:29:42.484 --> 00:29:47.064 That is the number 1Password.com slash unplugged, all lowercase. 00:29:47.244 --> 00:29:49.744 More information, and it's a great way to support the show. 00:29:50.464 --> 00:29:52.804 1password.com slash unplugged. 00:30:00.364 --> 00:30:06.064 Well, come on in, my friends. We asked you to send us your config sins for the 00:30:06.064 --> 00:30:09.264 last couple weeks, and you have. Thank you. 00:30:09.864 --> 00:30:14.604 We have a massive batch of Homelab configs that we need to go through. 00:30:15.944 --> 00:30:17.864 but where do we start? 00:30:18.164 --> 00:30:23.224 Where do we start indeed? Yes. Well, I think we have, we've gone through some 00:30:23.224 --> 00:30:26.104 of these and now we have more that have come in but we'll see if y'all like 00:30:26.104 --> 00:30:29.844 this segment, let us know and we'll do another batch. But why don't we start with Zach? 00:30:30.284 --> 00:30:34.584 He says, I've been listening for a few years now and I've learned a lot by listening to the show. 00:30:34.764 --> 00:30:38.064 I heard you were looking for some NixOS configs to look over so I started using 00:30:38.064 --> 00:30:40.784 Nix after listening to one of your podcasts and I've been slowly converting 00:30:40.784 --> 00:30:42.604 all my servers to it this year. 00:30:42.824 --> 00:30:47.904 I still have a few more servers or services to go, then I'll work on converting my laptop over to Nix. 00:30:48.704 --> 00:30:52.204 The configs are pretty rough as I'm still trying to figure it all out. 00:30:52.544 --> 00:30:57.484 So, Brentley, if you pull up his GitHub there and peruse through that, see what interests you. 00:30:58.664 --> 00:31:02.344 Wes and I took a little look in there, and I'm curious to see what jumps out 00:31:02.344 --> 00:31:05.624 at you just from an overall structure standpoint or interesting packages. 00:31:06.544 --> 00:31:11.864 Wes, when we started this process, you're like, I want to see if anybody does 00:31:11.864 --> 00:31:14.144 X. Do you remember what that was? 00:31:14.844 --> 00:31:18.944 We had a few things we kind of discussed you know I'm always curious about like 00:31:18.944 --> 00:31:24.024 how much do people define their own sets of tooling are they kind of using a 00:31:24.024 --> 00:31:27.404 template or going their own way do they use special args or not the. 00:31:27.404 --> 00:31:30.184 One that stuck out to me is like I wonder if anybody's doing any custom modules. 00:31:30.184 --> 00:31:31.424 Stuff and. 00:31:31.424 --> 00:31:33.164 Then we pulled up Zach's and it was right there. 00:31:33.164 --> 00:31:33.984 Yeah right at the top. 00:31:35.964 --> 00:31:38.184 So can you explain what a custom module is. 00:31:38.184 --> 00:31:43.924 Well so you know how there's NixOS modules right so like you say services.vscode.enable.true 00:31:43.924 --> 00:31:48.424 So if you'd like the VS Code service running in the background, 00:31:48.564 --> 00:31:52.284 the web version, or whatever service that NixOS supports, 00:31:52.944 --> 00:31:55.084 well, you can do that yourself, right? 00:31:55.164 --> 00:32:00.864 So you can add so that the system now accepts new parameters that you can input and define. 00:32:01.064 --> 00:32:04.464 And that's a way to, I mean, not only like enable or disable functionality, 00:32:04.464 --> 00:32:07.764 but also pass things through your system and through your configuration. 00:32:09.170 --> 00:32:13.930 And he has, like, so in here he has vscodeserver.nix. And so he's got a .nix 00:32:13.930 --> 00:32:15.270 just for running vscode. 00:32:16.250 --> 00:32:19.490 And he's defining, like, of course, enable the options module, 00:32:19.750 --> 00:32:22.510 optional vscodeserver enabled, so that turns it on right there. 00:32:23.130 --> 00:32:26.150 Yeah, so in this case, right, so in the normal setup, you just do, 00:32:26.350 --> 00:32:29.250 like, hey, tell me I want to run the vscodeserver. 00:32:29.650 --> 00:32:34.450 And then here you've got, like, extra wrapper stuff you can do around to apply, 00:32:34.570 --> 00:32:37.150 like, oh, here's a workaround for something that I need to work around. 00:32:37.150 --> 00:32:42.110 I know I want these initials like enabling Nix LD here to make it so that like 00:32:42.110 --> 00:32:45.270 random extensions that have their own binaries might have a better chance of working. 00:32:45.450 --> 00:32:48.970 So that's, that's a nice little thing because sometimes those are edge cases 00:32:48.970 --> 00:32:51.230 with some of these apps on Nix you do need to solve. 00:32:51.310 --> 00:32:55.450 And so he solved it once, he put it in its own file, and then any system he 00:32:55.450 --> 00:32:59.010 wants to use that on, he's got that, that LD library problem solved now. 00:32:59.370 --> 00:33:01.850 And this is where it's kind of interesting because like Nix provides a lot of 00:33:01.850 --> 00:33:02.790 ways to structure things. 00:33:02.950 --> 00:33:06.570 And so one method we'll see, I think later on is you can kind of just have like, 00:33:06.670 --> 00:33:10.690 you can include modules or not just by whether you include the file or not, 00:33:10.890 --> 00:33:14.750 or you can go this route where you sort of define it and you gate it behind 00:33:14.750 --> 00:33:16.550 like actual first class config options. 00:33:17.070 --> 00:33:18.750 So I don't know if I would call that rough shape. 00:33:19.050 --> 00:33:23.170 Also kind of a common approach we saw, but managing secrets, 00:33:23.370 --> 00:33:24.810 he's got that taken care of here. 00:33:25.310 --> 00:33:30.270 Yeah. Using age nix. I think we see both swaps and age nix happening here. 00:33:30.370 --> 00:33:33.450 It's kind of fun to see how people do handle secrets or if they just, 00:33:33.590 --> 00:33:35.690 you know, some aren't addressed in the repo at all. 00:33:36.730 --> 00:33:40.490 We do have a couple of small nitpicks if we were going to dig in there. 00:33:41.590 --> 00:33:46.270 We did a little review, and one of the things that stood out was you could review 00:33:46.270 --> 00:33:49.970 your domains, your ports, your GitLab image tags, and your registry wiring. 00:33:50.130 --> 00:33:53.430 They all are repeated across multiple modules, so you could maybe centralize 00:33:53.430 --> 00:33:58.890 that in one common NICS file so you're not having to change those names everywhere 00:33:58.890 --> 00:33:59.850 in all those different files. 00:34:00.050 --> 00:34:03.150 It might make it easier for future upgrades, less typos. It's probably something 00:34:03.150 --> 00:34:05.830 I would screw up if I had to change something across six or so files. 00:34:06.350 --> 00:34:08.090 did we have any other nitpicks with uh. 00:34:10.181 --> 00:34:15.901 No, I don't think so. I mean, it seems like a lean, mean config to me. 00:34:16.081 --> 00:34:21.281 One thing the LLM called out is that maybe he could look at changing permissions 00:34:21.281 --> 00:34:26.021 for some of the files he does do with secret management, but we didn't really think it was a big deal. 00:34:26.881 --> 00:34:29.341 And it also dinged him, again, on Nix, 00:34:29.401 --> 00:34:31.741 not a big deal, but maybe on other distributions this would make sense. 00:34:31.901 --> 00:34:35.081 The LLM dinged him for using a mix of Docker and Podman. 00:34:35.761 --> 00:34:39.261 We don't think that's a real problem, but it thought it was weird. 00:34:39.321 --> 00:34:43.521 I think it was interesting just to note that, one, you can do that, 00:34:43.561 --> 00:34:47.381 and two, it makes me wonder, what's the reasoning behind that? 00:34:47.701 --> 00:34:50.901 Not that it's not legitimate, but just what drove that choice. 00:34:51.321 --> 00:34:55.201 Right. You can see the care and the love. So he has this hosted on GitLab, 00:34:55.201 --> 00:35:01.121 and you see on the readme, he has essentially instructions for himself if he 00:35:01.121 --> 00:35:03.461 ever needs to get this up and running again. I love that. 00:35:03.641 --> 00:35:06.281 I mean, obviously a good choice, and the readme was updated, 00:35:06.341 --> 00:35:11.821 what, 21 hours ago? so either that's for our benefit or for their benefit but 00:35:11.821 --> 00:35:13.381 everyone's benefiting that's for sure. 00:35:14.521 --> 00:35:18.881 Also I think some others will use this too but using NVF which I hadn't seen 00:35:18.881 --> 00:35:25.021 before is a modular extensible distro agnostic NeoVim configuration framework for Nix and NixOS. 00:35:25.021 --> 00:35:28.481 Yeah that could be a good little pick we'll have a link to that in the show 00:35:28.481 --> 00:35:29.701 notes if you want to check that out. 00:35:29.701 --> 00:35:32.901 Also using Home Manager and Disco very nice. 00:35:32.901 --> 00:35:38.541 Yeah to get everything laid out on the disk And a lot of home manager use In 00:35:38.541 --> 00:35:41.881 the audience A lot of home manager Overall though pretty good config, 00:35:45.550 --> 00:35:51.850 Thank you, Zach. Thank you, Zach. Sutterman boosted in his config with 5,555 sats. 00:35:53.130 --> 00:35:56.770 I've never boosted before, but you asked for a Nix config, so I had to share mine. 00:35:57.310 --> 00:36:01.030 It's an impermanent setup for all my machines, complete with Home Manager, 00:36:01.230 --> 00:36:04.890 Disco, and Hyperland. Secrets are encrypted via... 00:36:06.230 --> 00:36:06.670 AgentX. 00:36:06.850 --> 00:36:15.710 AgentX. I always want to say age and X, using a key derived from my cold wallet's seed words and BIP85. 00:36:16.590 --> 00:36:22.270 Okay, that's cool. My SSH keys and age identities are deterministically delivered 00:36:22.270 --> 00:36:27.470 from this key, meaning I can bootstrap a host scanning a QR code on my cold card Q. 00:36:27.690 --> 00:36:31.650 And if the key gets compromised, I can rekey everything by picking a different 00:36:31.650 --> 00:36:33.470 derivation index number. 00:36:33.730 --> 00:36:34.370 Wow. 00:36:34.830 --> 00:36:38.010 Fancy. that's so nerdy and great that. 00:36:38.010 --> 00:36:43.290 Is that really is also so open this one up Brent I mean it's a beaut, 00:36:44.850 --> 00:36:50.730 some of these really give me like the most FOMO ever like I just I could do 00:36:50.730 --> 00:36:55.330 so much better on my readme this is another really nice readme he's taking advantage of blueprint here. 00:36:55.330 --> 00:37:01.450 Yeah that's a project from numtide a standard folder structure for Nix projects 00:37:01.450 --> 00:37:05.930 yeah so it's like an opinionated library and map standard folder structure to 00:37:05.930 --> 00:37:09.810 flake output so like it kind of handles automatically you just put files in 00:37:09.810 --> 00:37:13.790 folders and then it'll make sure those get exported out of the flake automatically. 00:37:15.190 --> 00:37:18.790 Sutterman's also accomplished something that I'm still struggling to fully pull 00:37:18.790 --> 00:37:26.150 off and that is a custom ISO for the setup a custom ISO to get the setup going from scratch, 00:37:27.030 --> 00:37:32.090 mine is still kind of get a base system going and then build my setup on top 00:37:32.090 --> 00:37:36.550 of that he's also using impermanence what does he what do you mean impermanence yeah. 00:37:36.550 --> 00:37:41.110 So impermanent is impermanence is that setup that basically there's a very you 00:37:41.110 --> 00:37:44.330 can use like temp fs you can use rollbacks on something like butter fs there's 00:37:44.330 --> 00:37:50.190 various mechanisms but essentially it's where you wipe your uh file system every reboot you like. 00:37:50.190 --> 00:37:51.490 Don't leave stuff hanging. 00:37:51.490 --> 00:37:54.730 Around that isn't controlled somehow by nix. 00:37:54.730 --> 00:37:59.710 Right boy it's there's a lot of these terms i also was really impressed with 00:37:59.710 --> 00:38:05.670 a very slick server setup he has where he's configured automatic backups and 00:38:05.670 --> 00:38:09.970 he's mounting Backblaze into a common spot and then backing systems up to it, 00:38:10.976 --> 00:38:14.156 Really slick. Really well done. I think anybody that's curious about a setup 00:38:14.156 --> 00:38:17.976 like that should check out Sutterman's link in the show notes for that. 00:38:18.096 --> 00:38:20.216 Just going through there and perusing that section. 00:38:20.536 --> 00:38:23.476 It's really nice. I was really impressed by that. I know I'm supposed to be 00:38:23.476 --> 00:38:27.816 criticizing, but it, this is one of the cleanest configs that was sent into 00:38:27.816 --> 00:38:29.016 the show in terms of readability. 00:38:29.856 --> 00:38:33.756 I mean, just very well structured, very clearly thoughtfully put together. 00:38:33.756 --> 00:38:36.676 Yeah yeah i want it i wanted to be really critical 00:38:36.676 --> 00:38:40.016 but it's kind of beautiful it's 00:38:40.016 --> 00:38:44.956 kind of like when it's readable it's so it's so intelligently structured it's 00:38:44.956 --> 00:38:49.136 clean the way the backups work like for example uh he's got like some stuff 00:38:49.136 --> 00:38:52.576 in here for tail scale to make sure some unused routes are cleaned up after 00:38:52.576 --> 00:38:56.816 the backups like he's just really got it dialed in boys also. 00:38:56.816 --> 00:39:00.856 Some custom nix like library code of helper functions and other stuff in here 00:39:00.856 --> 00:39:06.076 like some custom um gen adders to first convert provided paths or attributes 00:39:06.076 --> 00:39:11.116 to a list that seems nice or even like a nix module here that has um attribute 00:39:11.116 --> 00:39:13.356 set describing my domains and ip addresses. 00:39:13.356 --> 00:39:17.096 Neat good idea a lot of these setups are multi-machine 00:39:17.096 --> 00:39:19.996 a lot of these setups are multi-machine they got home lab 00:39:19.996 --> 00:39:23.276 servers they've got desktops and laptops some people 00:39:23.276 --> 00:39:26.296 even have surface books uh but before we before 00:39:26.296 --> 00:39:30.496 we get off of setterman's pretty impressive setup i noticed a tool he was using 00:39:30.496 --> 00:39:35.696 in here that i think i need to take advantage of he has um nick's flat pack 00:39:35.696 --> 00:39:41.196 and it's declaratively installing flat packs this as i become a larger and larger 00:39:41.196 --> 00:39:43.896 user of flat packs this is really something how. 00:39:43.896 --> 00:39:44.716 Many flat packs again. 00:39:44.716 --> 00:39:50.356 Yes you know this embarrasses you're making me say it in the show it's. 00:39:50.356 --> 00:39:52.416 Like as many as i have tabs open. 00:39:52.416 --> 00:39:55.556 It's 59 ish i think 59 flat packs 00:39:55.556 --> 00:39:58.316 it takes a long time to update all those over starlink i'll 00:39:58.316 --> 00:40:02.336 just say that but you know i try stuff out for the show and i 00:40:02.336 --> 00:40:05.116 also i kind of i kind of go with a base minimal well that's 00:40:05.116 --> 00:40:08.016 not true either anymore but i have too many flat packs 00:40:08.016 --> 00:40:10.656 uh and so one of the issues is i've kind of come 00:40:10.656 --> 00:40:13.396 to depend like telegram is a flat pack i think i'm 00:40:13.396 --> 00:40:16.136 using steam as a flat pack now maybe not so i 00:40:16.136 --> 00:40:20.136 need something and this declared a flat pack manager essentially is just you 00:40:20.136 --> 00:40:23.436 define everything you want installed and you can do versions and all that and 00:40:23.436 --> 00:40:26.416 then when you stand up a system you just get those flat packs from flat hub 00:40:26.416 --> 00:40:31.016 installed really nice and one of the things i when i went through i was like 00:40:31.016 --> 00:40:33.996 oh i gotta do that some custom stuff in here too, 00:40:35.356 --> 00:40:39.836 also a nice slick implementation of the r stack if you know what i mean for 00:40:39.836 --> 00:40:44.916 backing up your media nice little nix based implementation of the r stack there 00:40:44.916 --> 00:40:47.076 not the full full stack but the solid A. 00:40:47.076 --> 00:40:47.796 Lot of good components. 00:40:48.016 --> 00:40:53.136 Yeah. So I really had no complaints. 00:40:53.496 --> 00:40:57.296 The LLM dinged him on a mix of SOPs and... 00:40:57.296 --> 00:40:58.276 Aged nicks. 00:40:58.596 --> 00:41:02.416 But again, I don't know if we really would ding him on that. 00:41:03.442 --> 00:41:06.262 It does ding him on a mix of a secret manager. 00:41:06.302 --> 00:41:08.902 I think that it just says it's a testament to how good it is. 00:41:09.362 --> 00:41:10.642 Sophia thinks to Chris says. 00:41:11.062 --> 00:41:12.602 Yeah, I really wanted something. Brent, do you have anything? 00:41:12.762 --> 00:41:15.462 It's beautiful, right? It's got a nice readme. It's structured. 00:41:16.222 --> 00:41:18.822 Even the config files themselves are clean. 00:41:19.062 --> 00:41:22.362 I know. I feel like even I could learn something from this. There's a little 00:41:22.362 --> 00:41:25.342 note at the bottom of the readme here that I think might explain why. 00:41:25.342 --> 00:41:31.882 It says, when trying to figure out how to do something, examples are almost always best in NixOS. 00:41:32.442 --> 00:41:36.542 Make use of GitHub's search with the code language filter to find examples from 00:41:36.542 --> 00:41:38.442 other Nix users' personal configurations. 00:41:38.682 --> 00:41:41.742 And it gives a nice little handy link for, like, you know, an NGINX example. 00:41:42.002 --> 00:41:45.662 This is like a step up. Not only do you get a great example of an actual working 00:41:45.662 --> 00:41:47.542 config, you get tips for how to find more. 00:41:47.682 --> 00:41:51.422 Other examples, yeah. I've heard that is a great way to do it, 00:41:51.422 --> 00:41:53.202 too. I do it every now and then, but I forget. 00:41:53.622 --> 00:41:55.722 Okay, so next up, huh? We got Adam. 00:41:55.982 --> 00:41:57.102 Yeah, yeah, tell me about Adam. 00:41:57.242 --> 00:41:59.022 I reverse-engineered the past 00:41:59.022 --> 00:42:03.402 hostname into Flake as parameter setup from Wimpy's Nix configs. Nice. 00:42:03.702 --> 00:42:03.902 All right. 00:42:04.042 --> 00:42:07.362 I'm particularly proud of my install instructions in the readme. 00:42:07.582 --> 00:42:11.302 Just boot into the Nix installer, open terminal, and copy and paste just two 00:42:11.302 --> 00:42:17.062 commands to get the disks partitioned with Disco and get the latest configurations installed. 00:42:17.322 --> 00:42:21.702 I even have an alternate install path for VMs that have less than 5 gigs of RAM. 00:42:22.222 --> 00:42:26.482 I'm a puppet refugee that just couldn't stand not having strong declarative 00:42:26.482 --> 00:42:27.942 configurations for my systems. 00:42:28.542 --> 00:42:31.222 NixOS fit the bill for me, and I haven't looked back. 00:42:31.962 --> 00:42:36.542 Again, a very well-structured readme. It starts with, this is my Flake-enabled 00:42:36.542 --> 00:42:39.962 NixOS configuration repository. It uses Home Manager, but not extensively. 00:42:40.002 --> 00:42:43.062 I've only implemented just enough from tutorials to get it to work. 00:42:43.142 --> 00:42:47.302 And then he's got a broken down by section, including how to get it working on a new host. 00:42:47.542 --> 00:42:51.202 Here's the URLs you need to pull down. Here's the commands to get it installed. 00:42:51.382 --> 00:42:52.842 Here's how to do system secrets. 00:42:53.822 --> 00:42:57.522 The kind of stuff that when you only do something once or twice a year, 00:42:57.522 --> 00:43:00.862 or maybe once a year or every couple of years, really nice to have it written down. 00:43:01.342 --> 00:43:05.202 So he gets immediately good marks right there just for a fantastic readme. 00:43:05.422 --> 00:43:08.462 And a nice-looking flaked.nix as he was talking about here. 00:43:08.562 --> 00:43:13.362 There's some helpers, like this make system function that has a hostname parameter 00:43:13.362 --> 00:43:18.562 to make it easy to build systems and pass the hostname in and make it nice and 00:43:18.562 --> 00:43:21.042 clean, as well as a bundle of all your inputs. 00:43:21.042 --> 00:43:24.182 So if you are doing the special arg stuff, you can pass that through in a clean way. 00:43:24.702 --> 00:43:27.902 There's also another one of these, I got to do it this way now. 00:43:28.102 --> 00:43:31.582 Now that I've seen this working functionally, I can't go back. 00:43:33.082 --> 00:43:39.162 And I'm going further down the Git rabbit hole. So he is using branches as he builds out new configs. 00:43:39.202 --> 00:43:44.242 And as we were reviewing his config, Adam's config, we saw him very recently 00:43:44.242 --> 00:43:45.702 committing things to a new branch. 00:43:45.902 --> 00:43:49.842 I think he was building out something for Jellyfin trying to get no, it was ersatz. 00:43:49.982 --> 00:43:50.742 It was ersatz. 00:43:50.782 --> 00:43:55.342 He was trying to get ersatz to have hardware acceleration which I lit up when I saw that. 00:43:55.562 --> 00:43:58.562 I was so excited to see him deploy an ersatz. I'm very, very, 00:43:58.602 --> 00:44:01.442 very excited because it's such a great app. And so... 00:44:02.927 --> 00:44:06.427 Basically, can you convince me why I should be building out my future configs 00:44:06.427 --> 00:44:08.107 this way, especially on my home server? 00:44:08.287 --> 00:44:09.427 Because this really does seem 00:44:09.427 --> 00:44:12.927 like a superior way to test something out without breaking production. 00:44:13.067 --> 00:44:15.847 Well, it's using the power to Git now that we've got you using Git. Yeah. 00:44:16.827 --> 00:44:19.747 You know, when Git came around, unlike some of the past systems, 00:44:19.947 --> 00:44:24.327 it made working with and using branches cheap and easy to do. 00:44:24.447 --> 00:44:28.367 And so it lets you have a separate place where you can freely make changes, 00:44:28.827 --> 00:44:30.187 vibe to your heart's content. 00:44:30.187 --> 00:44:33.827 And then at the end of the day, you can pick and choose which things you want 00:44:33.827 --> 00:44:38.507 to actually keep and get a really clean diff view of what's changed between 00:44:38.507 --> 00:44:40.107 you and your base system. 00:44:40.287 --> 00:44:43.447 And if you want to work on multiple things at the same time, you can do that too. 00:44:43.627 --> 00:44:47.887 When you say it makes it cheap and easy to do branches, what do you mean? 00:44:48.627 --> 00:44:51.127 Like you just don't have to worry about it. Make as many branches as you want. 00:44:51.367 --> 00:44:55.827 Oh, because it's just managing it all for you. You don't have to do the math. Yep. Okay. 00:44:55.947 --> 00:44:58.787 And it's not an expensive process for the way Git works internally. 00:44:59.747 --> 00:45:03.027 So that was really cool. It was neat to see him testing that out as a way to 00:45:03.027 --> 00:45:06.247 build out his new config. And then I imagine he just merges it when it's time to roll. 00:45:06.387 --> 00:45:11.067 Yeah, exactly. Plus, it then opens you up to all of the especially modern Forge 00:45:11.067 --> 00:45:15.247 workflows, right, where you can have PRs or MRs and do review and take a look 00:45:15.247 --> 00:45:18.507 at things or trigger CI tests if you want to run tests or... 00:45:18.507 --> 00:45:20.527 This would be a great way to manage Home Assistant. 00:45:21.970 --> 00:45:26.390 yeah i know that smile what i didn't do anything smiles i'm gonna get him to 00:45:26.390 --> 00:45:30.010 drop dockers what that smile was that's what that smile was well we'll see you 00:45:30.010 --> 00:45:33.630 do a lot you know see the flatback count um i. 00:45:33.630 --> 00:45:35.390 Was gonna what was i gonna say i don't know. 00:45:35.390 --> 00:45:38.650 Special he's got some special args in here did we mention that did we want to 00:45:38.650 --> 00:45:41.910 go over that we talked about the oh also the r suite in here yeah. 00:45:41.910 --> 00:45:44.950 I was gonna say there's just the structure's really nice in that there's a ton 00:45:44.950 --> 00:45:49.030 of just explicit modules that are all set aside so this is i think where we 00:45:49.030 --> 00:45:51.230 want to take your config which we'll touch on later. 00:45:51.230 --> 00:45:51.870 Okay right. 00:45:51.870 --> 00:45:55.910 It's like pretty much all the functionality rather than being in like directly 00:45:55.910 --> 00:45:58.650 in the host config it's all implemented in different modules. 00:45:58.650 --> 00:46:00.050 Yeah that is great and. 00:46:00.050 --> 00:46:01.990 Then the various hosts can just import those modules. 00:46:01.990 --> 00:46:04.650 I i had a bit of feedback we don't need to spend a lot of time 00:46:04.650 --> 00:46:07.350 on this but i noticed uh those of you that do have 00:46:07.350 --> 00:46:11.450 the r suite nobody has their own local indexer nzb 00:46:11.450 --> 00:46:14.670 hydra or prowler something like that might be worth considering um 00:46:14.670 --> 00:46:17.690 nobody had that in their stack oh also i i 00:46:17.690 --> 00:46:21.110 thought this was hilarious adam has a bonker 00:46:21.110 --> 00:46:24.090 setup oh brand i don't know if you can find this if you 00:46:24.090 --> 00:46:27.030 look in his uh repository he has a bonker setup 00:46:27.030 --> 00:46:29.930 to get world of warcraft working no and just looking 00:46:29.930 --> 00:46:33.010 through it i'm kind of picturing what he does and i'm 00:46:33.010 --> 00:46:36.290 thinking he's got he's got like a a disc 00:46:36.290 --> 00:46:39.510 somewhere or a partition somewhere with a massive world 00:46:39.510 --> 00:46:42.190 of warcraft installation that's been patched and all of 00:46:42.190 --> 00:46:45.030 that and then he kind of like mounts it in and 00:46:45.030 --> 00:46:47.750 then launches world of warcraft which probably points at 00:46:47.750 --> 00:46:50.450 that that path and then he plays the game i don't. 00:46:50.450 --> 00:46:54.590 Know if he uses it to cross machines because back in my day when wow was brand 00:46:54.590 --> 00:46:59.010 new i did that i had i had a central storage location and then i would mount 00:46:59.010 --> 00:47:02.170 it on various places so that way i wouldn't have to patch and all of that stuff 00:47:02.170 --> 00:47:06.150 every single time i don't know if that still works or not but it was pretty 00:47:06.150 --> 00:47:09.410 funny to see a world of warcraft module in its configuration, 00:47:09.970 --> 00:47:13.150 and then to see such a technical approach to setting up World of Warcraft. 00:47:13.590 --> 00:47:18.790 I also find it interesting how the World of Warcraft module has options ZFS 00:47:18.790 --> 00:47:21.370 util in there because you do need that for your gaming, right? 00:47:21.590 --> 00:47:25.730 Yeah, well, I mean, you got to have your World of Warcraft data on ZFS. You don't want BitRot. 00:47:26.450 --> 00:47:29.550 Adam, you should write back to us or something sometime. I'd be curious. 00:47:29.690 --> 00:47:33.110 I'll have to follow up in one way or another because if you get the acceleration 00:47:33.110 --> 00:47:35.990 stuff working with our sets, I would definitely want to pull that upstream too. 00:47:36.230 --> 00:47:37.170 Yeah, for sure. 00:47:37.170 --> 00:47:40.390 I did notice two interesting things that stood out for me, at least, 00:47:40.630 --> 00:47:42.750 from what I can tell from state version here. 00:47:43.290 --> 00:47:47.030 I've been using this at least since 2023, so that's a good long while. 00:47:47.470 --> 00:47:47.670 Yeah. 00:47:48.270 --> 00:47:54.570 But the other thing is, in the list of hosts, I noticed one here called Boomer Nix OS. 00:47:54.850 --> 00:47:58.410 I'm just curious, is that like your family deployments? 00:47:58.550 --> 00:48:01.610 You know, you do it for your parents, and that's the one you put on their machines? 00:48:01.610 --> 00:48:04.490 Because I know my parents can use Nix OS. 00:48:04.490 --> 00:48:11.450 I said the same exact thing when I saw the boomer OS or the boomer config I 00:48:11.450 --> 00:48:14.950 thought oh this is like this is like a family but now I think one of his machines 00:48:14.950 --> 00:48:18.470 is named boomer oh sure he's got it yeah, 00:48:20.361 --> 00:48:26.641 But I had the same thought, like, oh, a special config of Nix for my boomer 00:48:26.641 --> 00:48:29.181 folks, that's actually a great idea. 00:48:29.581 --> 00:48:32.241 I mean, I do it for my kids. Why not do it for my folks? 00:48:33.141 --> 00:48:35.961 The boomer does play World of Warcraft, just saying. 00:48:37.941 --> 00:48:41.441 That was another really good one that put me to shame, Adam. 00:48:41.541 --> 00:48:42.441 Thank you for sending that in. 00:48:42.881 --> 00:48:45.661 I think it's Kieran, I think maybe, or Kyron came in. 00:48:45.801 --> 00:48:49.221 He says, I have a Nix, or they have a Nix configuration that hopefully you can 00:48:49.221 --> 00:48:51.041 rip apart. It does need some improvement. 00:48:51.341 --> 00:48:55.461 I made my dots about a year ago and have been running them up until about a 00:48:55.461 --> 00:48:58.161 month ago on Hyperland with my framework 13. 00:48:58.481 --> 00:49:02.661 Although it randomly died the other day, I needed one for school. 00:49:02.921 --> 00:49:07.141 So now I'm begrudgingly on Darwin, in other words, macOS. 00:49:07.561 --> 00:49:11.501 And I do manage as many servers as I can and as well as my MacBook with it. 00:49:11.581 --> 00:49:14.961 So far, it's been rock solid for me. And I love learning how Nix works. 00:49:15.401 --> 00:49:18.641 So we took a look at this. We hated it. 00:49:20.101 --> 00:49:21.521 I'm just teasing. We didn't hate it. 00:49:21.661 --> 00:49:23.821 It's a beautiful setup. I love the screenshot. 00:49:24.001 --> 00:49:24.141 Yeah. 00:49:24.401 --> 00:49:27.001 You've been eyeing a lot of this screenshot for a while. 00:49:27.001 --> 00:49:30.161 I like that Waybar. That's a good Waybar setup. 00:49:30.901 --> 00:49:35.541 I think it's a little bit more elegant than mine. And I also appreciate a nice layout snapshot. 00:49:36.121 --> 00:49:39.061 I've attempted to do something similar just right there. 00:49:39.221 --> 00:49:42.981 And then, as I've noted with some of these other ones, some one-liners so you 00:49:42.981 --> 00:49:47.061 can just get this thing going and get it set up so you can get right back to your config. 00:49:47.241 --> 00:49:50.901 I appreciate the exposition. and there's a big caution bar at the top that says 00:49:50.901 --> 00:49:53.221 these dots are highly prone to change or breakage. 00:49:53.381 --> 00:49:56.261 And then there's a crossed out thing that says like, I'm not an expert. 00:49:56.261 --> 00:49:57.561 I'm just kind of figuring this out. 00:49:57.761 --> 00:49:59.321 That's crossed out now. 00:49:59.501 --> 00:50:04.421 And it says after 284 successful days of these dots being in constant operation, 00:50:05.041 --> 00:50:12.161 many, many rebuilds and 364 commits, these dots have been rock solid and I have no complaints. 00:50:12.321 --> 00:50:13.061 I think that's great. 00:50:13.341 --> 00:50:14.001 Very nice. 00:50:14.541 --> 00:50:20.281 Yeah. There was, everybody organizes these differently. 00:50:20.781 --> 00:50:23.181 And so that's always interesting because it's kind of like you can get a little 00:50:23.181 --> 00:50:26.541 bit of personality traits when you look at these. 00:50:26.761 --> 00:50:36.721 And one that stood out to me is Kieran has a aesthetics module where they configure their aesthetics. 00:50:37.281 --> 00:50:39.161 It's a nice way to break it out. 00:50:39.921 --> 00:50:42.701 I love the Hyperland module. I'm going to steal some ideas from that. 00:50:42.961 --> 00:50:48.081 And then I don't know why this is funny to me but a dedicated wallpaper Wallpapers.nicks, 00:50:48.461 --> 00:50:50.961 which just has like a bunch of great wallpapers to find in it. 00:50:51.501 --> 00:50:53.041 That to me, I don't know why. 00:50:53.201 --> 00:50:54.261 Why are we doing that? 00:50:54.461 --> 00:50:57.461 Yeah. First, I was like, that's so silly. You're overthinking it. 00:50:57.541 --> 00:50:58.421 And then I thought, actually- 00:50:59.758 --> 00:51:03.818 You know, there's probably about 10, 15 wallpapers I really like that I have. Why not? 00:51:04.038 --> 00:51:07.438 And what, you don't do declarative wallpapers, Chris? Jeez, man. 00:51:08.518 --> 00:51:09.558 Go with the times. 00:51:09.838 --> 00:51:13.698 I got real interested because I've been using that Crush tool, 00:51:13.878 --> 00:51:17.658 the like vibe coding little 2E thing more just because it's really convenient. 00:51:17.798 --> 00:51:20.338 I don't, you need it a ton, but you know, when I want it, it's handy, 00:51:20.438 --> 00:51:21.658 especially because it works with Open Router. 00:51:22.378 --> 00:51:25.678 But like kind of like reconfiguring it sometimes can be a bit of a pain. 00:51:25.898 --> 00:51:31.038 And it turns out there's, in these dots, we've got a HomeManager config for Crush. 00:51:31.238 --> 00:51:31.478 Yeah. 00:51:31.798 --> 00:51:34.538 And that seems like something I might want to copy. 00:51:34.538 --> 00:51:36.118 Do you think that might pull you into HomeManager? 00:51:36.158 --> 00:51:38.518 Well, it might. We'll see. That's tempting. 00:51:38.798 --> 00:51:42.738 Yeah. There's so much HomeManager use here. It's a little rough. 00:51:43.178 --> 00:51:46.658 It's making me feel like I'm missing out. But I'm also curious if I could do 00:51:46.658 --> 00:51:49.138 without it. The Crush config is pretty tempting, though. 00:51:50.238 --> 00:51:53.738 All right. So let's talk about just a couple more here. 00:51:54.338 --> 00:51:59.638 40Deuce came in. He sent in a boost with 42,000 sats, and we captured this last 00:51:59.638 --> 00:52:03.298 week, but I think it maybe came in after the show? 00:52:04.258 --> 00:52:05.598 No, it's in the boosts. 00:52:05.718 --> 00:52:06.698 Oh, it came in this week? 00:52:06.798 --> 00:52:08.498 No, it was in last week's boosts. 00:52:08.518 --> 00:52:12.858 I can't keep it straight. I'm sorry. But anyways, so he came in with 42,000 00:52:12.858 --> 00:52:15.598 sats and said, you asked for it, you got it, my Nix config. I've shared this 00:52:15.598 --> 00:52:17.078 before, but it's come a long way. 00:52:17.558 --> 00:52:21.718 This is my Nix OS and Home Manager flake that manages multiple hosts with many 00:52:21.718 --> 00:52:24.498 shared modules and a few host-specific modules. 00:52:25.218 --> 00:52:28.078 It has a pretty nice usable configs for Hyperland, Neary, Sway, 00:52:28.298 --> 00:52:33.378 River, and Wayfire compositors, as well as enabling Plasma and the Cosmic desktop. 00:52:33.818 --> 00:52:37.618 One recent change you might appreciate, I abstracted out all the usernames to 00:52:37.618 --> 00:52:43.918 a let statement in myflake.nix to make it easy for another user trying myflake 00:52:43.918 --> 00:52:47.198 to quickly change the username in just one place. 00:52:47.858 --> 00:52:51.038 That way you might have a chance to try it, so you can slam Chris F in there. 00:52:51.038 --> 00:52:55.258 I mean, yeah, I guess I would just put Chris F. in there if I were you, 00:52:55.458 --> 00:52:57.218 40 Deuce, but I guess that's fine. 00:52:57.538 --> 00:52:58.518 Everyone is Chris F. 00:52:59.609 --> 00:53:06.949 Um, what I thought was hilarious about this config is 40deuce has obviously 00:53:06.949 --> 00:53:12.489 spent some time getting FireWire devices working and FireWire audio devices. 00:53:12.489 --> 00:53:15.009 And he has an audio prod dot nix. 00:53:15.209 --> 00:53:18.109 Yeah, there's a lot of good audio config in here. I like that. 00:53:18.109 --> 00:53:23.189 Real-time. Real-time's in here. And some kernel parameters to make FireWire 00:53:23.189 --> 00:53:31.149 behave appropriately, as well as some rules to make it work with the audio subsystem and with UDev. 00:53:31.429 --> 00:53:36.129 And then disabling some conflicting subsystems, enabling the appropriate pipewire 00:53:36.129 --> 00:53:41.569 subsystems and the appropriate pipewire latency settings as well for really quick real-time audio. 00:53:41.989 --> 00:53:44.729 Enabling Wireplumber and hooking it up with FireWire support. 00:53:44.849 --> 00:53:50.729 I mean, everything. It took so much work. And then again, 40Deuce has a beautiful 00:53:50.729 --> 00:53:54.469 syntax structure to the point where I thought this almost looks machine generated. 00:53:54.469 --> 00:53:56.169 It's so clean. It's so consistent. 00:53:56.369 --> 00:53:59.569 But then when you read the comments, they're clearly written by a human. 00:54:00.709 --> 00:54:04.469 Although, much like you were learning about, you know, development stuff from 00:54:04.469 --> 00:54:09.049 the branches and another one, this one you noticed that there was an agent.md. 00:54:09.469 --> 00:54:12.689 Yes. So there may be some LLM going on here. 00:54:12.829 --> 00:54:14.509 Either way, the end result is lovely. 00:54:14.689 --> 00:54:19.209 It is very clean, very readable. So if that was an LLM, I should use that one. 00:54:19.389 --> 00:54:24.769 Yeah, I think, right? We should offer like a bounty. Do you want to clean up Chris's config? 00:54:24.969 --> 00:54:27.889 We'll shoot you some sats. Go look at my Hypervibe config and I'll shoot you 00:54:27.889 --> 00:54:31.689 some sats if you want to clean it up because I would love it to be as clean as yours. 00:54:32.589 --> 00:54:36.169 So the AgentsMD is interesting. Pretty simple layout, right? 00:54:36.329 --> 00:54:39.909 Not too confusing. Not overdone. Sometimes people get a little too complicated. 00:54:40.169 --> 00:54:40.449 Yeah, true. 00:54:41.535 --> 00:54:44.435 Uh, individual hosts only is nice. 00:54:45.335 --> 00:54:49.415 I like the way bar again here. This is another really nice way bar config. 00:54:49.815 --> 00:54:56.175 Um, too much home manager, maybe one of the cleanest configs overall sent in. I don't know. 00:54:56.295 --> 00:54:59.415 I like the thoughtful read me in terms of like folks actually trying it, 00:54:59.535 --> 00:55:01.935 you know, that wasn't, I mean, many of them didn't have that, 00:55:02.015 --> 00:55:04.315 but there's especially taken to another degree with this one. 00:55:05.075 --> 00:55:09.395 A lot of hyperland. I mean, hyper, he's got a lot. He's got cosmic. He's got plasma. 00:55:09.715 --> 00:55:09.955 Neary. 00:55:09.955 --> 00:55:13.995 Yeah, you can switch between them depending on which one you want to enable, which is neat. 00:55:15.715 --> 00:55:20.295 But all the screenshots were Hyperland. A lot of the default configs are Hyperland. 00:55:21.195 --> 00:55:23.915 I guess I'm late. I'm late. Yeah. 00:55:24.735 --> 00:55:29.895 It's like, welcome, welcome. Been here for a minute. It's funny. A lot of setup. 00:55:30.555 --> 00:55:35.015 Really nice. A lot of intention has gone into these. People have really built something pretty cool. 00:55:35.115 --> 00:55:39.795 Do we have any criticism for Deuce here? Do we have anything we want to lob? 00:55:39.955 --> 00:55:42.115 Brent, you got any criticism? We got to come up with something. 00:55:42.235 --> 00:55:43.275 We're being way too nice here. 00:55:44.215 --> 00:55:46.195 I got a softball if you need one. 00:55:46.395 --> 00:55:47.395 Yeah, give me something. 00:55:48.015 --> 00:55:52.235 In the screenshot, is that pipes in the background? I think it might be pipes 00:55:52.235 --> 00:55:54.455 or snakes or something. What's going on there? 00:55:54.735 --> 00:55:58.775 Come on. Yeah, and you know what? Not a single Fast Fetch. 00:55:59.115 --> 00:56:02.675 And is it really a Hyperland desktop screenshot without a Fast Fetch? 00:56:03.355 --> 00:56:04.875 So dinging them for no Fast Fetch. 00:56:05.075 --> 00:56:08.075 The Fast Fetch is in the Matrix code there. I think you're missing that. 00:56:08.335 --> 00:56:13.795 Oh, okay. I love I do kind of like the pipes though so I like the pipes I think 00:56:13.795 --> 00:56:16.275 I'll give them credit for that I'm going to ding them, 00:56:18.101 --> 00:56:22.561 oh god i gotta have something here there's got to be something i can think the readme is too long. 00:56:25.961 --> 00:56:29.641 You know what i did notice in the readme that i'm seeing as a bit of a theme 00:56:29.641 --> 00:56:34.361 here uh there's one line that says uh i'm still very much learning next along 00:56:34.361 --> 00:56:38.481 with many other things so please leave feedback on any bugs best practices corrections 00:56:38.481 --> 00:56:43.321 or appreciation as indicated a lot of people saying like hey i'm just learning 00:56:43.321 --> 00:56:45.381 so here you go and have fun she's. 00:56:46.941 --> 00:56:49.721 I'm going to need to know what 40 Deuce is doing with Firewire. 00:56:49.941 --> 00:56:52.541 I got to know what's going on. Why are you using so much Firewire audio? 00:56:53.461 --> 00:56:56.141 What are you doing? It's 2025. What's your plan for the future? 00:56:56.561 --> 00:56:57.681 Can you get us some Firewire? 00:56:57.701 --> 00:56:58.741 Yeah, I'm also kind of envious. 00:57:01.441 --> 00:57:04.661 Let us know, okay? Okay, you ready for the last couple here, boys? 00:57:04.821 --> 00:57:05.041 Yeah. 00:57:05.461 --> 00:57:08.361 All right, we're rounding it out now. Team Toronto, a.k.a. Brad, 00:57:08.521 --> 00:57:12.981 came in with 20,000 sats, and he says, In the past 12 months, 00:57:13.101 --> 00:57:17.421 I've gone from Windows to Mint to Ubuntu, now to Nix OS. 00:57:18.041 --> 00:57:20.221 Linux Unplugged has been the best and the worst influence. 00:57:22.041 --> 00:57:23.081 It is for us, too. 00:57:23.861 --> 00:57:28.041 So he's coming in hot here, boys. He's got a couple of interesting things, 00:57:28.101 --> 00:57:31.681 Wes. I noticed you noted maybe a custom library here. 00:57:31.681 --> 00:57:36.121 Yeah, that always stands out. You know, if you're writing a bunch of Nix code 00:57:36.121 --> 00:57:39.881 that you're using, reusing throughout, there's some fancy stuff. 00:57:39.881 --> 00:57:45.821 It's list importable subders, make system, list Nix files. I like it. 00:57:46.704 --> 00:57:50.444 Okay, so he's got modules. So his modules are broken out into hardware, 00:57:50.664 --> 00:57:52.864 programs, and services. Let's go look at services here. 00:57:54.284 --> 00:57:56.144 Oh, yeah, Restic, rsync. 00:57:56.744 --> 00:57:57.864 Secrets with SOPs. 00:57:57.944 --> 00:58:03.184 Nice. Scrutiny collector.nix? What is this? Restic backup. Oh, 00:58:03.264 --> 00:58:04.464 something for Restic. I see. 00:58:04.684 --> 00:58:07.264 We were also noticing various Samba mounts going on. 00:58:07.464 --> 00:58:07.664 Yep. 00:58:07.824 --> 00:58:09.424 In a nice way, I think, that you liked. 00:58:09.644 --> 00:58:14.624 Yep, yep. I'm always a fan of doing Samba nice and clean and just having a Samba config there. 00:58:16.144 --> 00:58:18.864 Also, I think this is smart. More people should consider a separate printer 00:58:18.864 --> 00:58:22.304 config. We didn't see that a lot. But do all your systems really need to print? 00:58:23.124 --> 00:58:25.944 Why not just have that as an optional feature on the systems that need it? 00:58:26.044 --> 00:58:27.024 Some of you could just pull in. 00:58:27.664 --> 00:58:31.524 Seeing, you know, that kind of stuff also to me is just kind of thinking ahead, 00:58:31.604 --> 00:58:34.184 like, oh, for a linear system, I don't need it. I don't need it. 00:58:35.584 --> 00:58:39.924 Nice, simple, straightforward config, Brad. I think it could use a little more 00:58:39.924 --> 00:58:42.804 love in the readme department, and explain what's going on and maybe give yourself 00:58:42.804 --> 00:58:45.024 some tips for future you to get going. 00:58:45.164 --> 00:58:48.604 I do like to see some secret management. Got to give them credit there. 00:58:48.884 --> 00:58:49.124 Absolutely. 00:58:50.084 --> 00:58:52.904 And we do like to see you getting fancy with the Samba mounts. 00:58:53.324 --> 00:58:58.164 All right, before we tear mine apart, the last one of the batch for this round is Monty. 00:58:58.284 --> 00:59:04.164 He came in with 6,666 sats, which a row of ducks for each one of the repos, he says, I'm sharing. 00:59:04.444 --> 00:59:08.064 First is my HomeLab Ansible config, which was the only Ansible submission, 00:59:08.064 --> 00:59:12.284 which is totally fine, of the show. Next is my Nix config, which is a multi-host 00:59:12.284 --> 00:59:16.084 for a few parts of the home lab and growing, as well as the family PCs here. 00:59:16.264 --> 00:59:22.904 And finally, a relatively new project that spins up a Nix LXC container on my Proxmox node. 00:59:23.164 --> 00:59:26.964 Might seem like an odd combination, but I actually dig the declarative config 00:59:26.964 --> 00:59:31.124 and easy update of Nix and the portability and isolation of LXC. 00:59:31.304 --> 00:59:33.384 I'm no expert, so be gentle with me. 00:59:35.164 --> 00:59:39.784 Yeah, yeah. All right. Okay. Okay, so we liked a lot what we saw here. 00:59:40.444 --> 00:59:43.704 Lots of commits, clearly well used, lots of functionality. 00:59:44.224 --> 00:59:49.304 It is a little bit all over the place. Did you have any notes on the ANSW? Oh, God, yeah, we did. 00:59:49.724 --> 00:59:54.504 No, it was mostly that it was just, you know, it was a lot of YAML for us. 00:59:54.504 --> 00:59:58.544 It's a lot of YAML that references YAML that references YAML that then just 00:59:58.544 --> 01:00:00.684 executes a command. And I'm not exaggerating. 01:00:00.864 --> 01:00:05.064 And it's just what it is. And when you go through, dear listener, 01:00:05.604 --> 01:00:06.744 take the exercise yourself. 01:00:07.064 --> 01:00:10.264 go to the show notes, peruse through everybody's Nix configs, 01:00:10.364 --> 01:00:12.844 and then go check out the Ansible config. 01:00:13.124 --> 01:00:18.144 And tell me if it isn't three or four layers of turtles before you actually get to what you want. 01:00:18.724 --> 01:00:20.844 It's just a totally different level of abstraction. 01:00:22.604 --> 01:00:25.444 You know, Monty is transitioning, so I'm not going to ding him too much. 01:00:25.924 --> 01:00:28.704 Nice docs, definitely. Also a nice JustFile setup. 01:00:28.704 --> 01:00:31.324 What's going on there with the JustFile? Not everybody has a JustFile. 01:00:31.424 --> 01:00:33.564 A couple of people did. Why is he using a JustFile? 01:00:34.444 --> 01:00:38.804 I mean, that just kind of vibe, right? Maybe it was a good way to provide easy 01:00:38.804 --> 01:00:40.464 access to run various commands. 01:00:40.644 --> 01:00:46.604 Yeah, because he's got a bunch of stuff in there. Like, he's got Nick's flake check mapped to NFC. 01:00:47.224 --> 01:00:51.084 He's got a bunch of, like, longer commands that also have host variables in 01:00:51.084 --> 01:00:52.924 them, mapped to like three-letter words. 01:00:53.324 --> 01:00:55.544 Yeah, and like, you know, here's your Ansible playbook, bootstrap, 01:00:55.764 --> 01:00:58.104 just as AP bootstrap. That's nice, right? 01:00:58.464 --> 01:01:01.924 Yeah, and it automatically, dynamically, it figures out the host name and all 01:01:01.924 --> 01:01:03.264 that kind of stuff. So it's pretty sweet. 01:01:03.964 --> 01:01:08.064 I mean, Monty's doing some clever stuff there that I didn't really see anybody else doing. 01:01:08.764 --> 01:01:11.864 So some of the other folks that send in your configs, you might want to go check 01:01:11.864 --> 01:01:15.164 out. Again, we see secrets management with SOPs again this time. 01:01:15.284 --> 01:01:20.644 Mm-hmm. In Monty's next config, some nice auto-upgrading going on. I like that. 01:01:21.444 --> 01:01:27.524 I, again, love the naming. One of his host configs is Omnitools. 01:01:28.984 --> 01:01:33.084 Omnitools. I don't know what he's doing over in Omnitools, but I like it. 01:01:33.544 --> 01:01:37.264 It's a pretty simple config over there, but the naming of these things are always funny. 01:01:37.424 --> 01:01:41.744 And then this NXC scripts, like this Proxmox plus Nix thing, I like it. 01:01:41.884 --> 01:01:45.784 It combines the declarative configuration power of NixOS with the portability 01:01:45.784 --> 01:01:48.604 and isolation benefits of Linux containers, LXC. 01:01:49.424 --> 01:01:53.684 You can clone this repository and use the included examples or point the scripts 01:01:53.684 --> 01:01:58.724 to your own Nix configuration repository to deploy and update your custom NXCs. 01:01:59.144 --> 01:01:59.884 It's nice. 01:02:00.924 --> 01:02:05.424 I was also impressed with the fancy backup setup, the auto-upgrade setup, 01:02:05.464 --> 01:02:09.504 and the dope tailscale setup, which is one of the cooler ones we'd seen. 01:02:10.304 --> 01:02:11.804 There's a lot going on in there. 01:02:12.064 --> 01:02:15.664 I'm impressed that there's all, you know, all like the expansive, 01:02:15.664 --> 01:02:21.904 well-used Ansible configuration plus now nix configs as well and you're doing this lxc stuff. 01:02:21.904 --> 01:02:25.744 Yeah we need a good criticism though and that might be you need to get all under 01:02:25.744 --> 01:02:31.004 one house or something you know pick a horse i don't know can you think of a criticism yeah. 01:02:31.004 --> 01:02:31.844 All right we can go with that. 01:02:31.844 --> 01:02:36.024 Pick a horse yeah that's it there you go we got tough there for a second but 01:02:36.024 --> 01:02:40.684 maybe we could be easy on this next one maybe we could go gentle here for a minute why. 01:02:40.684 --> 01:02:42.564 Is that why would we change our tune chris. 01:02:42.564 --> 01:02:48.084 Uh So I thought I would submit my config for review, and as you know, 01:02:48.264 --> 01:02:52.584 this is called Hypervibe because it's a riced-up Hyperland desktop built on 01:02:52.584 --> 01:02:56.304 top of NixOS that I vibed together. And, well... 01:02:58.040 --> 01:03:04.140 It's not like go-to-town ready. I'll just say that. It's not something you want 01:03:04.140 --> 01:03:05.780 to go to town in, but it's close. 01:03:06.780 --> 01:03:10.980 Wes, you had a go at this recently, trying to install it live on the show. How was that? 01:03:11.220 --> 01:03:15.280 It did not end well, if I recall. I try not. I sort of blanked that out for some reason. 01:03:15.960 --> 01:03:20.060 I see my screenshot isn't loading anymore in my readme, so I'm going to ding me for that. 01:03:21.440 --> 01:03:22.580 Yeah, bad readme. 01:03:22.720 --> 01:03:25.480 I do have a screenshot, but I just think maybe it got taken out. 01:03:25.760 --> 01:03:27.420 I mean, I do really enjoy the desktop. 01:03:28.060 --> 01:03:30.220 Uncontrolled vibe usage so. 01:03:30.220 --> 01:03:33.940 Lay it on wes what's the worst give me like the you know. 01:03:33.940 --> 01:03:38.560 I don't know the bad the good the ugly kind of there's a lot of scripts folders 01:03:38.560 --> 01:03:42.780 you just there's a lot of scripts folders sort of just strewn about for some reason yeah. 01:03:42.780 --> 01:03:44.520 A lot of activation scripts. 01:03:44.520 --> 01:03:48.420 Yeah there's also a lot of duplication like uh there's just between them like 01:03:48.420 --> 01:03:52.200 you have a lot of copied packages and which is can be totally fine like there's what. 01:03:52.200 --> 01:03:54.900 Do you mean what do you mean like i've got the same package listed twice or something. 01:03:54.900 --> 01:03:57.680 Well that yeah that's been somewhat cleaned up i think there's probably 01:03:57.680 --> 01:04:00.460 still a couple of those but then just between like you 01:04:00.460 --> 01:04:07.320 have sort of um you've started using some shared modules like we saw nice implementations 01:04:07.320 --> 01:04:11.560 today yeah yeah but it's sort of like halfway done so you have like a packages 01:04:11.560 --> 01:04:14.500 like an area where in theory you'd have packages but there's not that many packages 01:04:14.500 --> 01:04:18.660 there but then in each of your hosts they have a whole bunch of packages in there and. 01:04:18.660 --> 01:04:19.400 A lot of the same. 01:04:19.400 --> 01:04:21.620 Yeah across the two that's very true, 01:04:22.546 --> 01:04:28.986 And then, so it's kind of unclear how far that's been adopted in terms of modularity. 01:04:29.046 --> 01:04:30.446 That wouldn't be too bad to clean up. 01:04:30.586 --> 01:04:33.666 And then in what you did do, you put it under kind of a weird, 01:04:33.946 --> 01:04:36.246 actually someone opened an issue about this. 01:04:36.426 --> 01:04:36.726 Oh, really? 01:04:36.886 --> 01:04:37.086 Yeah. 01:04:37.366 --> 01:04:37.546 Okay. 01:04:38.046 --> 01:04:39.326 Do you have 10 issues already? 01:04:39.926 --> 01:04:40.626 Oh my God. 01:04:40.786 --> 01:04:41.766 I don't know if you've been attending. 01:04:41.926 --> 01:04:42.666 Oh, T-Cario. 01:04:43.006 --> 01:04:43.546 Okay, great. 01:04:43.726 --> 01:04:46.746 I haven't been looking. I really should get back to it. I'm sure I'll get right on that. 01:04:46.766 --> 01:04:51.726 T-Cario was so polite too. You have Nix OS modules that can be reused in other 01:04:51.726 --> 01:04:54.026 people's system configs. This is awesome. 01:04:54.786 --> 01:04:57.686 But then continues to go on to point out some of the problems. 01:04:58.246 --> 01:05:02.546 The current namespace name of shared may not be highly likely to conflict, 01:05:02.566 --> 01:05:04.906 but it's also not specific to this project. 01:05:05.186 --> 01:05:08.046 I think it would make more sense to name these under Hypervibe, 01:05:08.126 --> 01:05:11.926 so just kind of changing the namespacing being used for the modules, which is a great idea. 01:05:12.166 --> 01:05:16.886 Sam H. contributed a pull request of how I could add options for different users. 01:05:17.286 --> 01:05:18.846 Hey, there we go. you. 01:05:18.846 --> 01:05:21.606 And i should go through this and merge some of these west because some of this 01:05:21.606 --> 01:05:23.466 is probably with a few tweaks actually pretty usable. 01:05:23.466 --> 01:05:27.726 And then there's like the searching and replacing and copying and like basically 01:05:27.726 --> 01:05:32.246 the giant activation script that yeah sort of is brutal yeah and in place of 01:05:32.246 --> 01:05:34.026 maybe something like home manager yeah. 01:05:34.026 --> 01:05:38.206 It is my it is my hack around home manager i will admit i'm leaning heavily 01:05:38.206 --> 01:05:39.366 on a few scripts to do that. 01:05:39.366 --> 01:05:42.066 So it's not yet and you kind of touched on that with the users it's not yet 01:05:42.066 --> 01:05:44.906 like portable right it's still kind of like really specific to your config it's 01:05:44.906 --> 01:05:50.266 getting there and we're gonna get it there but and then um yeah what else well 01:05:50.266 --> 01:05:54.426 you you got sudo set up without a password you don't have a firewall hell yeah 01:05:54.426 --> 01:05:57.006 buddy you're living pretty dangerously i. 01:05:57.006 --> 01:06:00.506 Love it i don't i don't need i don't need no stinking password to use sudo. 01:06:00.506 --> 01:06:06.306 And then i think this one came from the uh lm noting just that you know your 01:06:06.306 --> 01:06:09.626 gpu temp setup it depends on amd yeah. 01:06:09.626 --> 01:06:13.846 Yeah yeah i need a way to abstract out the gpu temperature stuff. 01:06:13.846 --> 01:06:18.106 So maybe we can you know list that up like brittle weight bar setup yeah. 01:06:18.106 --> 01:06:19.046 Brittle weight bar set up, 01:06:19.969 --> 01:06:27.109 So it's a mess, too many scripts, duplication, need to modularize the user stuff, 01:06:27.649 --> 01:06:31.629 reduce dupe apps across machine configs and put them in a shared config. 01:06:31.689 --> 01:06:32.169 We'll just start fresh. 01:06:32.589 --> 01:06:36.949 Yeah, and then I've got nine poll requests. Nine poll requests, 01:06:37.149 --> 01:06:39.209 all of which actually seem like a pretty good idea. 01:06:41.249 --> 01:06:43.569 Who knew the distro would be so much work? 01:06:44.589 --> 01:06:46.929 Adversaries here has a criticism you'd like to share. 01:06:47.149 --> 01:06:47.689 Oh, good. 01:06:47.789 --> 01:06:48.729 I got one too. 01:06:48.729 --> 01:06:49.189 Actually. 01:06:49.189 --> 01:06:50.369 Okay excellent. 01:06:50.369 --> 01:06:55.969 You know what you really need chris is a ci config that way every time you commit 01:06:55.969 --> 01:07:00.709 and push it just resets all your hosts to whatever broken config you have. 01:07:00.709 --> 01:07:05.829 I do i do you're right i do because like i do something on one machine oh yeah 01:07:05.829 --> 01:07:08.389 i gotta go update over here now you're right i should just push it all out and 01:07:08.389 --> 01:07:11.609 break all of them at once that's a good that's a great tip what's yours brent. 01:07:11.609 --> 01:07:15.749 Well i'm just gonna lean in with wes on one of his criticisms and say like, 01:07:15.869 --> 01:07:23.529 you know, there's 63.7% Nix in here, but 30.4% shell scripts? 01:07:23.909 --> 01:07:28.029 You said you were leaning on shell scripts, but like, that's a lot, dude. 01:07:28.189 --> 01:07:29.289 2.6% is Python. 01:07:30.469 --> 01:07:32.929 Maybe we should see if we can vibe convert it to Rust. 01:07:35.149 --> 01:07:36.069 Vibe convert, sorry. 01:07:37.389 --> 01:07:43.669 And then I can say it's a hyper-vibed, hyper-land-based, Wayland-first NixOS 01:07:43.669 --> 01:07:46.969 desktop using Rust configuration management. 01:07:48.129 --> 01:07:49.129 Nix OS native. 01:07:49.269 --> 01:07:49.749 Yeah, right. 01:07:49.969 --> 01:07:50.189 Nailed it. 01:07:50.809 --> 01:07:55.849 I mean, it's funny, like, as busted as it is, it has been working very solidly for me. 01:07:56.409 --> 01:08:00.009 The other critique is it hasn't yet been totally adapted for Brent and I, right? 01:08:00.309 --> 01:08:01.829 Oh, yeah, well, that's true. 01:08:02.309 --> 01:08:05.609 You know, this is your production, and we're kind of, like, helping you with 01:08:05.609 --> 01:08:07.309 it, and so it's customary that you 01:08:07.309 --> 01:08:11.109 provide us and sort of a flake for our computer configs with our users. 01:08:11.209 --> 01:08:14.209 I do ultimately want to get it running on the studio computers. 01:08:16.100 --> 01:08:16.940 I know it's crazy. 01:08:17.060 --> 01:08:17.480 Let's do it. 01:08:17.540 --> 01:08:20.860 I do ultimately want to get it running on there because we can't keep running these OSs forever. 01:08:21.120 --> 01:08:24.300 I can hear Wes's tone. He says yes, but he means no. 01:08:25.220 --> 01:08:26.020 No, I'm in. 01:08:26.480 --> 01:08:30.720 The fear in his face also suggested no. He's like, oh my God, 01:08:30.820 --> 01:08:31.800 we have so much work to do. 01:08:33.120 --> 01:08:35.380 So mine's clearly in the worst state of the group. 01:08:36.620 --> 01:08:39.780 I mean, cancel the Texas trip. You guys should just spend a week over there. 01:08:39.780 --> 01:08:45.820 I think what I'm learning, too, is watching Wes vibe code a live tracking website 01:08:45.820 --> 01:08:49.140 front end and then watching our listeners vibe code some of these configs. 01:08:49.420 --> 01:08:54.240 It's not the LLM. So you thought my excuse for being a mess was that I used an LLM. 01:08:54.380 --> 01:08:55.680 But these other people are using 01:08:55.680 --> 01:08:59.840 LLMs. And it's much cleaner and much tighter. So it's me. It's all me. 01:09:00.740 --> 01:09:03.980 And I do appreciate anybody that has any suggestions, pull requests or issues 01:09:03.980 --> 01:09:05.220 they want to pull against mine. 01:09:06.200 --> 01:09:11.320 Because I do intend to come back around to it eventually. and incorporate some of that stuff. 01:09:11.520 --> 01:09:14.580 If you enjoyed this too, send us a booster and email and let us know because 01:09:14.580 --> 01:09:16.900 we do have another batch of configs and we could use a few more. 01:09:17.100 --> 01:09:18.540 We could definitely do round two. 01:09:19.020 --> 01:09:25.240 And I hope maybe in round two we'd get some real, real awful ones because I'm ready to be a stinker. 01:09:39.542 --> 01:09:43.022 Unraid.net slash unplugged. Go unleash your hardware. 01:09:43.262 --> 01:09:47.882 Unraid is a powerful, easy to use NAS operating system for those of you that 01:09:47.882 --> 01:09:52.782 want control, flexibility, and efficiency in managing your own data. 01:09:52.962 --> 01:09:56.102 What you got in the closet is going to work with Unraid. It allows you to mix 01:09:56.102 --> 01:09:57.422 and match drives of any size. 01:09:57.542 --> 01:10:01.842 You can build what you want with no restrictions. There's also built-in support 01:10:01.842 --> 01:10:06.722 for things like tail scale and one-click remote access and easy hardware acceleration 01:10:06.722 --> 01:10:12.602 and a ginormous community app store that has everything in there from AlbiHub 01:10:12.602 --> 01:10:15.402 to the latest RAR series of things. 01:10:15.622 --> 01:10:18.722 And if you know what I mean, you know what I mean. Now, I got a note from Alan 01:10:18.722 --> 01:10:22.582 in Texas. He says, in your latest read, you mentioned you wanted to hear people 01:10:22.582 --> 01:10:23.482 with their Unraid setups. 01:10:23.622 --> 01:10:30.022 Well, I am running Unraid on a Dell PowerEdge R730XD as my home server. 01:10:30.582 --> 01:10:34.162 It's running a couple of VMs for Home Assistant, PFSense, and a Minecraft server 01:10:34.162 --> 01:10:37.222 on Ubuntu, and a couple of Linux distros to play around with. 01:10:37.622 --> 01:10:41.142 There are also several containers for Image, Jellyfin, Nextcloud, 01:10:41.302 --> 01:10:45.182 Pinchflat, Matrix, Minifold, Vault Warden, and more. 01:10:45.362 --> 01:10:49.242 I've been busy with work, so it needs some love. I'm not really sure if that's 01:10:49.242 --> 01:10:52.222 worth sharing, but if you guys want to pull the trigger on Linux Unplugged Home 01:10:52.222 --> 01:10:56.642 Lab Extreme Makeover Podcast, I could be a prime candidate. I would love to do that, Alan. 01:10:57.222 --> 01:11:01.582 Thank you for sending that note in about your Unraid setup. I love hearing what people use it for. 01:11:01.922 --> 01:11:04.522 I'm going to check out Minifold. I know everything on that list. 01:11:04.522 --> 01:11:06.142 I'm not sure if I'm familiar with Minifold. 01:11:06.402 --> 01:11:10.262 I might check that out after this show. So go get set up with Unraid and then 01:11:10.262 --> 01:11:12.382 write in and tell me what you've built, what you're running. 01:11:12.542 --> 01:11:13.762 Could be huge, could be small. 01:11:14.142 --> 01:11:17.262 What really matters is that it makes a difference for you. Get started. 01:11:17.502 --> 01:11:21.222 Support the show. Try it for 30 days for free. Unraid's fantastic. 01:11:21.382 --> 01:11:23.502 Built on modern Linux. You're going to love it. 01:11:23.882 --> 01:11:29.442 Unraid.net slash unplugged. That's unraid.net slash unplugged. 01:11:32.645 --> 01:11:36.745 Well, we would like to do one big, huge shout-out to Chris B., 01:11:36.745 --> 01:11:38.265 a new core contributor this week. 01:11:39.985 --> 01:11:42.445 That's not Chris Brentley, is it? 01:11:42.945 --> 01:11:44.505 Welcome, Chris Brentley. 01:11:44.745 --> 01:11:48.685 You are one new member this week, and we appreciate you very, very much. Thank you. 01:11:48.925 --> 01:11:53.565 Now, we have been raising funds to get to Texas Linux Fest, and we have the 01:11:53.565 --> 01:11:56.965 fake booths, which are set in Just in Love, because you can send an amount, 01:11:56.965 --> 01:11:59.905 it's to a particular thing, and you can attach a message. 01:12:00.465 --> 01:12:04.405 and park a launch came in with 25 us 01:12:04.405 --> 01:12:07.385 dollars eagerly awaiting this coverage sending 01:12:07.385 --> 01:12:12.745 some value back to you all that you can send to me you got it buddy pack a lunch 01:12:12.745 --> 01:12:17.045 pack a lunch we should pack a lunch wes should we pack some food for monday 01:12:17.045 --> 01:12:20.705 we probably should pack some snacks oh yeah we should get in the snack headspace 01:12:20.705 --> 01:12:24.805 thank you pack a lunch i appreciate that very much brooke. 01:12:24.805 --> 01:12:32.665 H fake boosen with 50 usd thanks for the great content been listening since linux action show. 01:12:32.665 --> 01:12:33.265 Oh and. 01:12:33.265 --> 01:12:34.625 A member oh wonderful. 01:12:34.625 --> 01:12:36.545 Thank you thank you your. 01:12:36.545 --> 01:12:40.205 Boost financial transparency is awesome would you consider including your number 01:12:40.205 --> 01:12:43.985 of paid members when you report boosts or amount of membership income. 01:12:43.985 --> 01:12:48.685 I don't even know if i have that number handy that's a good question there's 01:12:48.685 --> 01:12:53.025 something i can look into there the system is sort of a black box to a degree 01:12:53.025 --> 01:12:55.405 because we don't host that aspect of it. 01:12:55.485 --> 01:12:58.445 And one of the things that's really great about the node setup is that we can 01:12:58.445 --> 01:13:00.385 pull that information and store it in a database constantly. 01:13:01.165 --> 01:13:05.325 But yeah, thank you, Brooke. Appreciate the value and we'll look into that. It's a good question. 01:13:06.085 --> 01:13:11.785 Well, we have Brad who boosted, oh no, not a boost, a fake boost of 50 US dollars. 01:13:15.185 --> 01:13:21.065 Now Brad says, team Toronto, and they recently in Toronto had a meetup. 01:13:21.065 --> 01:13:24.365 I think was that last week and a bunch of people showed up some people took 01:13:24.365 --> 01:13:30.185 the train to go in I unfortunately missed it I'm so sorry try to be there next time go. 01:13:30.185 --> 01:13:34.065 Figure it's that's the timing of things I suppose but that's great I'm glad 01:13:34.065 --> 01:13:39.765 they had a good meetup go team Toronto Brian came in with 15 U.S. 01:13:39.925 --> 01:13:40.945 greenbacks thank you Brian, 01:13:42.483 --> 01:13:45.423 Here's a little something for the trip. If you guys happen to be passing through 01:13:45.423 --> 01:13:49.943 Boise on your journey, I'm happy to meet up and top off your supply of snacks. 01:13:50.123 --> 01:13:51.183 Oh, that's so sweet. 01:13:51.323 --> 01:13:53.003 That is actually the point where we'd be out of snacks. 01:13:53.363 --> 01:13:54.503 Maybe I'll take a detour. 01:13:55.183 --> 01:14:00.743 So we probably will go through Boise. Keep an eye on texastracker.jupiterbroadcasting.com. 01:14:01.403 --> 01:14:04.383 We may, or near it, we may be glancing through it. 01:14:05.043 --> 01:14:08.523 If we make really good time, I think we'll make it there. Thank you, Brian. 01:14:08.783 --> 01:14:12.243 Appreciate that offer. and maybe get BitChat so you can hit us up. 01:14:12.303 --> 01:14:16.203 Also, I'll be trying to keep an eye when we stop on things like Matrix and maybe email. 01:14:16.723 --> 01:14:19.223 But while we're on the go, it's probably going to be BitChat. 01:14:19.483 --> 01:14:25.923 Alex Gates comes in with 50 USD. Lit streams on standalone apps is especially 01:14:25.923 --> 01:14:29.583 difficult without any backend infrastructure to watch for podpings. 01:14:29.863 --> 01:14:34.603 I've been working on a solution for this, a service to allow apps to register 01:14:34.603 --> 01:14:39.883 for podping notifications via either Unified Push or Web Push. 01:14:39.903 --> 01:14:43.823 It will be self-hostable, but I also want to offer a managed service. 01:14:44.043 --> 01:14:46.723 The problem is free services are not sustainable. 01:14:47.223 --> 01:14:50.983 Question for the crew and the audience. What would you pay for such a service 01:14:50.983 --> 01:14:54.843 for use in applications such as AntennaPod? Interesting. 01:14:55.103 --> 01:14:58.863 That is an interesting idea. As a podcaster that wanted to get my live stream 01:14:58.863 --> 01:15:03.043 into AntennaPod, I'd probably be willing to pay like 10 bucks a month to notify AntennaPod users. 01:15:03.843 --> 01:15:07.583 Assuming that was a way they could hook up to it and not have to implement PodPing on the back end. 01:15:08.383 --> 01:15:12.123 I love the goal, Alex, of trying to make it so that way podcast apps don't need 01:15:12.123 --> 01:15:12.923 back end infrastructure. 01:15:13.363 --> 01:15:13.623 Totally. 01:15:14.123 --> 01:15:18.163 Yeah, and just because it's in the RSS feed, I mean, the only other option would 01:15:18.163 --> 01:15:21.983 be that the client is refreshing manually and reparsing the XML all the time, right? 01:15:22.143 --> 01:15:23.103 As some of them do now. 01:15:23.283 --> 01:15:25.883 Yeah, yeah. Let us know, Alex. Keep us posted on that. 01:15:26.523 --> 01:15:31.403 Well, Dave M. sent in 60 US dollars. No message, just a whole lot of value. 01:15:32.423 --> 01:15:37.823 Thank you, Dave. Appreciate that. Eric T. came in with 25 U.S. greenbacks. 01:15:38.863 --> 01:15:42.723 Sold some old junk from the garage and got paid for it for your Venmo. 01:15:42.863 --> 01:15:45.923 So I'm passing the found money along to you. Have a great trip, guys. 01:15:46.523 --> 01:15:50.843 Well done, Eric. Thank you. I need to do that. I need to do a garage purge very 01:15:50.843 --> 01:15:53.643 badly. I am buried in stuff. 01:15:53.743 --> 01:15:55.263 You're going to reduce the laptop stack? 01:15:56.663 --> 01:16:00.183 Yeah, I'll even give a discount. Tell you what, buy a bundle. 01:16:02.183 --> 01:16:06.603 Erixi octane comes in with 123 dollars. 01:16:06.603 --> 01:16:10.443 And 45 cents that might be a one two three four five boost, 01:16:14.603 --> 01:16:15.523 Heck yes. 01:16:15.983 --> 01:16:20.023 Some filthy fiat for the cause. See y'all in Texas. I'll see you there. 01:16:21.223 --> 01:16:23.003 Thank you for the support. 01:16:23.183 --> 01:16:25.963 I hope so. Yeah, be sure you say hi. Come to the lunch. 01:16:26.363 --> 01:16:31.123 Did you say lunch? Jens didn't boost in 10 US dollars. 01:16:33.303 --> 01:16:37.523 Posting from the past. Hope it's soon enough for the Texas Linux Fest. Have fun, boys. 01:16:37.983 --> 01:16:41.423 Oh, thank you. It is just in time for the Texas Linux Fest. 01:16:41.503 --> 01:16:44.563 We are hitting the road. we had nine 01:16:44.563 --> 01:16:47.423 fake boosts everybody who fake boosted in thank you very much 01:16:47.423 --> 01:16:52.203 and you stacked $408.45 yes we'll 01:16:52.203 --> 01:16:56.343 have the link in the show notes we are making the trip down and back still appreciate 01:16:56.343 --> 01:17:00.283 the support it's been tremendous we're hitting the road thank you everybody 01:17:00.283 --> 01:17:04.863 who supported the show with a fake boost and with that we also have a batch 01:17:04.863 --> 01:17:09.523 of regular boosts came in and is Brad our baller this week, 01:17:10.563 --> 01:17:13.223 Brad coming in at 20,000 sets. 01:17:15.783 --> 01:17:20.343 Brad, who also sent us a fake booth? Is this the same Brad? Or was Brad that sent us? 01:17:20.343 --> 01:17:21.243 Yeah, Brad's all over. 01:17:21.263 --> 01:17:23.743 And this is what we used for the Knicks. 01:17:23.843 --> 01:17:28.183 Brad sent us a Knicks. Brad, way to go, man. Dude, being engaged. 01:17:28.363 --> 01:17:29.943 Thank you, sir. Appreciate that. 01:17:30.183 --> 01:17:34.183 I think Brad should, you know, get a brunch. Brunch with Brad. We'll make that happen. 01:17:34.563 --> 01:17:37.263 There we go. I'll take the next one, too. 01:17:37.343 --> 01:17:43.463 Batvin came in with 2,000 sets oh no did i miss the live stream nope well you 01:17:43.463 --> 01:17:47.543 missed last week's but you made it just yeah that was on the 21st but you're 01:17:47.543 --> 01:17:50.123 early for this week so it just depends on your perspective we. 01:17:50.123 --> 01:17:55.543 Hope you're out there user 304 comes in with 18 000 sets, 01:17:58.338 --> 01:18:03.178 Okay, for the Texas trip. Oh, and this must be, oh yeah, this is stuff earned 01:18:03.178 --> 01:18:06.158 on Fountain. I see I have earned more, so boosting again. 01:18:06.378 --> 01:18:08.838 Well, thank you, user304. We appreciate it. 01:18:08.898 --> 01:18:09.398 Yeah, seriously. 01:18:11.738 --> 01:18:15.058 Well, we got a boost here, a row of ducks from the Golden Dragon. 01:18:15.418 --> 01:18:15.798 Hey-oh! 01:18:17.498 --> 01:18:21.638 Great episode, gents. I hope to get to bigger boosting soon. 01:18:21.938 --> 01:18:25.218 Say, I know you guys set up fake boost for Texas Linux Fest, 01:18:25.358 --> 01:18:28.238 but what are the chances it sticks around long-term? 01:18:28.338 --> 01:18:32.478 It seems that it was pretty popular for some of those non-Bitcoin folks. 01:18:33.118 --> 01:18:37.878 It has some technical limitations in that it doesn't do splits. 01:18:38.138 --> 01:18:43.438 So it makes sense when we're allocating all the funds anyways to one particular cause. 01:18:44.818 --> 01:18:48.598 That works perfect for that. But on a day-to-day way of supporting the production, 01:18:48.898 --> 01:18:53.278 one of the brilliant things about the boosts is they baked in the split system. 01:18:53.478 --> 01:18:57.358 So we all get a cut. Editor Drew gets a cut. The podcast app developer gets 01:18:57.358 --> 01:18:59.258 a cut. the podcast index gets a little split. 01:18:59.518 --> 01:19:02.858 We're all happy to participate. And it happens automatically at the protocol 01:19:02.858 --> 01:19:06.858 level, if you will, or at the application level. And so the contract is in the code. 01:19:07.098 --> 01:19:10.118 It's in the RSS feed for you to be able to just review it yourself. 01:19:10.118 --> 01:19:12.438 You can look at our XML file and you can see what the splits are. 01:19:13.058 --> 01:19:17.318 That's a level of transparency I really like. And the fiat systems don't yet offer that. 01:19:17.758 --> 01:19:21.258 However, there may be something in the future we could rig up, 01:19:21.398 --> 01:19:24.658 but we would try to make it an even better experience and make it something 01:19:24.658 --> 01:19:26.438 that people could actively participate and enjoy. 01:19:26.738 --> 01:19:30.538 But it has worked tremendous for this, so it's on the back of our minds, Dragon. 01:19:32.618 --> 01:19:35.138 You know, if it sticks around, we're going to have to start calling it fake 01:19:35.138 --> 01:19:37.078 real boosts, or real fake boosts. 01:19:37.098 --> 01:19:41.558 You're right, you're right, you're right. Ed comes in with one, 01:19:41.698 --> 01:19:43.478 two, three, four, five sets. 01:19:46.498 --> 01:19:49.338 All right, I'm giving Fountain another try after the 1.3 release, 01:19:49.458 --> 01:19:51.878 hoping to replace Intenapod as my go-to podcasting app. 01:19:52.078 --> 01:19:55.158 The Nostra integration and value-for-value features aren't making 01:19:55.158 --> 01:19:58.058 it into antenna pod soon enough i listened 01:19:58.058 --> 01:20:00.798 to the episode on the next unplugged today while offline and watch the sat 01:20:00.798 --> 01:20:03.558 streaming while i listen it's very nice i have to do some 01:20:03.558 --> 01:20:07.158 tuning on the best amount to stream to my to meet my budget but fountain makes 01:20:07.158 --> 01:20:11.038 that pretty easy to do the good news is is that the show will now be received 01:20:11.038 --> 01:20:14.078 more consistent support from me will be receiving consistent support from me 01:20:14.078 --> 01:20:17.658 thanks for the show and all the hard work that goes into it ed thank you for 01:20:17.658 --> 01:20:22.158 putting the time effort and often honestly the thoughtfulness into that really appreciate that. 01:20:22.238 --> 01:20:24.558 I've always liked that aspect of the streaming side. It's just sort of like, 01:20:24.618 --> 01:20:26.658 yeah, you know, you kind of set a budget you're comfortable with, 01:20:26.758 --> 01:20:29.038 and then you're just automatically supporting it as you're using it. 01:20:29.138 --> 01:20:30.798 Yep, that is great. Thank you. 01:20:31.378 --> 01:20:34.858 GeekDude comes in with 13,260 sats. 01:20:37.618 --> 01:20:39.018 Boost for Linux Fest. 01:20:39.118 --> 01:20:42.018 Heck yeah, we're getting there. One bit at a time. 01:20:43.138 --> 01:20:47.378 Monty's here with his boost for his config with 6,666 sats. 01:20:51.350 --> 01:20:54.810 Okay, we'll go with that. And we went over Monty's config. Thank you, 01:20:54.910 --> 01:20:56.270 Monty, for sending in a boost with that. 01:20:56.450 --> 01:20:58.490 Yeah, that's value, double the value over there. 01:20:59.070 --> 01:21:00.830 Oh, and look who it is, Wes. 01:21:01.130 --> 01:21:06.130 Oh, we got Adversary 17 coming in with 4,096 ads. 01:21:06.370 --> 01:21:07.290 I believe it's adversaries. 01:21:07.490 --> 01:21:08.370 You're right, you're right. 01:21:09.630 --> 01:21:13.330 Would you like them to read their own boost? That seems like a reasonable thing to do. 01:21:14.590 --> 01:21:17.790 Is that nice? That's pretty, that's mean. That's on the spot, Brent. Come on. 01:21:18.130 --> 01:21:20.690 Oh, there it is. Adversary, if you want to read your own boost. 01:21:20.790 --> 01:21:22.930 Here we go. your own voice regarding. 01:21:22.930 --> 01:21:26.570 Multi kernels maybe you have a specifically optimized 01:21:26.570 --> 01:21:29.410 for gaming kernel run on a few cores so that 01:21:29.410 --> 01:21:34.350 all the gaming tasks have better performance wait if there's a different kernel 01:21:34.350 --> 01:21:38.710 running on each core does that mean that things like kernel anti-cheat won't 01:21:38.710 --> 01:21:44.110 be able to see other tasks running elsewhere so do you negate the privacy implications 01:21:44.110 --> 01:21:47.150 of kernel level anti-cheats that way hmm. 01:21:47.150 --> 01:21:50.610 That is a great question yeah. 01:21:50.610 --> 01:21:51.870 I like where your head's at. 01:21:51.870 --> 01:21:54.730 Yeah so you could have one kernel that's all like compromised up with 01:21:54.730 --> 01:21:57.730 drm and crap like that so you could play your stupid windows game and 01:21:57.730 --> 01:22:01.490 then all your other kernels live in free and that has it's none the wiser or 01:22:01.490 --> 01:22:04.950 something like that but your other idea of like you can have a gaming optimized 01:22:04.950 --> 01:22:09.430 kernel a video production optimized it's an interesting idea and you could see 01:22:09.430 --> 01:22:12.870 how you could sell that as a service like it's a box it does hardware accelerated 01:22:12.870 --> 01:22:16.010 this and it does this and that and it's like multi-kernel setup to actually accomplish it. 01:22:16.970 --> 01:22:21.150 I don't know, guys. We haven't heard much more, but it may be the future just one day. 01:22:22.430 --> 01:22:24.570 Sutterman's here with 11,110 sets. 01:22:26.564 --> 01:22:28.284 And we loved your config. Thank 01:22:28.284 --> 01:22:31.364 you very much. And also, thank you for setting up the tooling to boost. 01:22:31.584 --> 01:22:35.304 Yeah, I've never boosted before, but you asked for NixConfig, so I had to share mine. 01:22:35.644 --> 01:22:36.824 Do really appreciate that. 01:22:37.004 --> 01:22:42.184 I like this bit. P.S., I blame you for my NixOS Hyperland and Bitcoin journey. Thank you so much. 01:22:42.424 --> 01:22:45.004 This is another thing, and this happens all the time and I love it, 01:22:45.324 --> 01:22:49.204 is I still feel like such a Nix noob, especially looking at the configs that 01:22:49.204 --> 01:22:51.264 we have been, right? There's so much to learn. 01:22:51.744 --> 01:22:56.404 and uh so that even if we've helped in that journey you're also there's so much 01:22:56.404 --> 01:22:57.704 you teach us back which is amazing. 01:22:57.704 --> 01:23:00.544 Yeah this is this is one this one is i'm stealing that 01:23:00.544 --> 01:23:03.944 i'm stealing that this has been a good one for that thank you everybody who 01:23:03.944 --> 01:23:07.524 sent a fake boost or a real boost as we call them uh we do appreciate it you 01:23:07.524 --> 01:23:13.104 sat streamers uh stepped up too we stacked 40 54 671 sats just by all the out 01:23:13.104 --> 01:23:16.744 there streaming it as you listen to us and we always appreciate that And then 01:23:16.744 --> 01:23:18.724 when you combine that with our boosters, 01:23:18.964 --> 01:23:23.664 we stacked a grand total of 144,620 sats this week. 01:23:25.604 --> 01:23:28.524 You've heard the way to do it. Fountain.fm makes it real easy. 01:23:29.444 --> 01:23:30.484 AlbiHub is something you can 01:23:30.484 --> 01:23:32.884 also get into if you want to get real nerdy and do all the self-hosted. 01:23:32.964 --> 01:23:35.864 And then there's lots of apps you can pick from, including just boosting from 01:23:35.864 --> 01:23:39.724 the podcast index website, actually. You don't even need an app for that. 01:23:40.204 --> 01:23:43.284 And it's a fun experiment, and you'll learn a lot about the technology and the process. 01:23:43.564 --> 01:23:45.904 Or Fountain.fm if you just want somebody to manage it all for you. 01:23:46.164 --> 01:23:49.784 And thank you, everybody who supports the show with a boost or a membership. 01:23:51.804 --> 01:23:55.664 You actually found the pick this week. I don't know if you knew I was going to make it a pick. 01:23:55.824 --> 01:23:56.584 I did not. 01:23:56.924 --> 01:24:01.084 But it's so cool, and it helped with our little project that we worked on this 01:24:01.084 --> 01:24:04.464 week, so it seemed only appropriate to include vTunnel. 01:24:05.044 --> 01:24:12.184 It's a tool that proxies IP traffic between a guest and a host network by using the VSOC protocol. 01:24:13.177 --> 01:24:17.157 So this could be a way to make inter-container communication, 01:24:17.157 --> 01:24:18.377 perhaps, really simple. 01:24:18.557 --> 01:24:22.297 You don't even need it really with containers, but with anything when you're 01:24:22.297 --> 01:24:24.437 doing with a hypervisor in a virtual machine. 01:24:24.717 --> 01:24:28.097 Okay, so a VM, and so two different VMs that need to talk to each other? 01:24:28.537 --> 01:24:36.377 You can use it for that, but primarily communication from the host context into 01:24:36.377 --> 01:24:37.317 the virtual machine and back. 01:24:37.537 --> 01:24:40.317 Oh, just to basically build a network between the host and the VMs. 01:24:40.477 --> 01:24:44.357 Yeah, but instead of having to necessarily. So VSOC in general is essentially, 01:24:44.457 --> 01:24:48.197 it's a type of socket. So it's kind of like a Unix socket, but it's used specifically for this. 01:24:48.257 --> 01:24:52.457 And the idea is you can have a connection over this socket between the virtual 01:24:52.457 --> 01:24:58.297 machine and the host, and you don't have to deal with a whole bunch of like the entire IP stack. 01:24:58.417 --> 01:25:01.457 If you don't want to necessarily, you can have this kind of faster, 01:25:01.637 --> 01:25:02.557 higher throughput connection. 01:25:02.737 --> 01:25:05.717 A little private networking that's actually a little bit simpler in its stack. 01:25:05.897 --> 01:25:08.917 You know, maybe you have something, some server or some process running stuff. 01:25:08.917 --> 01:25:11.957 You kind of just want to feed in data, calculate stuff and spit stuff back out. 01:25:11.957 --> 01:25:15.737 you can have that all connected up without having to have all of the like you 01:25:15.737 --> 01:25:19.757 know the switch the virtual switch on the host and having all the plumbing and 01:25:19.757 --> 01:25:23.817 running DHCP and having DNS set up for it and all the right forwarding and firewalling, 01:25:24.637 --> 01:25:27.697 vTunnel comes in if say maybe you do still need some 01:25:27.697 --> 01:25:30.417 you know maybe this little server process does need to like 01:25:30.417 --> 01:25:34.097 make a couple of outbound calls to grab some data occasionally for its cache 01:25:34.097 --> 01:25:38.597 or something so this can enable proxying without still having to go set up all 01:25:38.597 --> 01:25:42.777 of that traditional infrastructure you can use that vsoc and then have a ip 01:25:42.777 --> 01:25:46.577 stack on top just a proxy to like carry those connections out to the internet 01:25:46.577 --> 01:25:48.577 and get your reply back that's. 01:25:48.577 --> 01:25:50.677 Really handy it's really useful in little ways. 01:25:50.677 --> 01:25:53.377 Yeah there's a few tools like this and this is one that seems like it actually 01:25:53.377 --> 01:25:56.737 works with um a lot of different setups so. 01:25:56.737 --> 01:26:02.557 That's v tunnel and it is bsd licensed um and then this one probably not blowing 01:26:02.557 --> 01:26:06.477 away anybody with this particular pick but wes finally convinced me. 01:26:06.477 --> 01:26:08.037 Oh did i you. 01:26:08.037 --> 01:26:13.417 Did Tab Session Manager, a tool to save and restore the state of browser windows and tabs. 01:26:13.637 --> 01:26:17.277 And we like this one just because it is... 01:26:18.154 --> 01:26:23.674 Open source. It's MPL2 licensed and really easy to get in Chrome or Firefox 01:26:23.674 --> 01:26:25.054 or in Chrome-based browser. 01:26:26.014 --> 01:26:29.514 And I started, what really got me is, you know, I have multiple Firefox windows 01:26:29.514 --> 01:26:33.134 open, and sometimes the wrong one is the last one to close, and then I lose 01:26:33.134 --> 01:26:35.954 all of my tabs and my restore isn't working properly. 01:26:36.554 --> 01:26:39.894 While Firefox is generally pretty good at restoring your previous session, 01:26:40.054 --> 01:26:41.314 it just wasn't quite doing it. 01:26:41.494 --> 01:26:42.614 Yeah, you were hitting an edge case. 01:26:42.734 --> 01:26:44.894 But you also, one of the things you like about this, right, is you can, 01:26:44.914 --> 01:26:49.394 like, save the tabs. You can export the tabs. You can make a list of the tabs. 01:26:49.394 --> 01:26:50.794 Yeah, and there's a lot of ways to do all this stuff, right? 01:26:50.834 --> 01:26:52.734 There's tab groups now, and you can have all kinds of it. 01:26:52.834 --> 01:26:56.734 But especially for the show, because often I want to reload all the stuff that 01:26:56.734 --> 01:26:58.674 we have in the doc for the links we're talking about today. 01:26:58.874 --> 01:27:02.434 But I had state I was working on yesterday, right? And I can kind of just store 01:27:02.434 --> 01:27:05.334 that, work on the stuff for today, and then restore that after the fact. 01:27:05.574 --> 01:27:09.794 Yeah, I'm not blowing anyone away, but this is a solid one. And it's open source, 01:27:10.094 --> 01:27:12.354 cross-browser, so that's nice too. 01:27:12.954 --> 01:27:16.674 And that's tab session manager. will have a link to that in the show notes. 01:27:16.814 --> 01:27:23.294 Links to all this stuff that we talked about today, that's at linuxunplugged.com slash 634. 01:27:25.334 --> 01:27:26.534 Okay, there we go. 01:27:26.634 --> 01:27:27.914 Yeah, that's what my tab session is named. 01:27:28.934 --> 01:27:34.014 I'm just, this is it. This is it. It's going to be you and me in a tiny car 01:27:34.014 --> 01:27:35.374 for about three days after this. 01:27:35.374 --> 01:27:35.914 That's right, 635 from Texas. 01:27:36.834 --> 01:27:38.614 Makes the van feel so spacious. 01:27:39.214 --> 01:27:44.674 Yeah. So follow us on texastracker.jupiterbroadcasting.com. We'll be hitting 01:27:44.674 --> 01:27:45.974 the road Monday morning. 01:27:46.174 --> 01:27:50.854 Wes and I, Brent's already on the road, and we'll have BitChat going if you 01:27:50.854 --> 01:27:54.094 want to chat with us along the way. And, of course, we're looking forward to getting down to Austin. 01:27:54.614 --> 01:27:56.994 And then we'll be on the route back to where we're going to be taking a slightly 01:27:56.994 --> 01:27:59.134 different return trip as well. 01:27:59.494 --> 01:28:02.814 You know, we didn't factor something in. What? We don't have, 01:28:02.874 --> 01:28:04.574 like, a virtual walkie system with Brent. 01:28:04.814 --> 01:28:07.714 Yeah, that would be cool. We should have thought of something. 01:28:07.934 --> 01:28:09.434 You can vibe something up, right? 01:28:09.554 --> 01:28:12.914 I should try to remember to pack some walkie-talkies, though, 01:28:12.914 --> 01:28:15.114 So when we're caravanning on the return trip. 01:28:15.274 --> 01:28:15.754 Oh, yeah. 01:28:16.474 --> 01:28:21.574 You know, Chris, the last time we were together, it turns out you left a walkie 01:28:21.574 --> 01:28:24.834 in my glove box. So I have one ready to go. 01:28:25.234 --> 01:28:27.174 All right. We'll make sure it's charged up and I'll bring another one. 01:28:27.374 --> 01:28:29.094 Okay. I'll need a bigger antenna, though, I don't think. 01:28:29.854 --> 01:28:32.954 And you can be there in spirit at Texas Linux Fest with a boost. 01:28:33.154 --> 01:28:35.594 If you want to send us a boost to support the trip and the show, 01:28:35.674 --> 01:28:37.094 we always really do appreciate that. 01:28:37.634 --> 01:28:39.814 And a big shout out to all our members who make the show possible. 01:28:39.814 --> 01:28:42.814 And everybody who participated in the fake boost, too. The link's still going. 01:28:42.914 --> 01:28:47.634 We really do appreciate that as we stack that up and actually begin to have 01:28:47.634 --> 01:28:49.274 to absorb some of these costs. 01:28:49.694 --> 01:28:54.454 So it's all it's all happening and it's because of our community and we greatly appreciate it. 01:28:58.043 --> 01:29:01.643 We will try to be live from Austin, Texas next Sunday. 01:29:02.443 --> 01:29:06.763 We'll see how that goes. So I'm going to bring all the right gear. It survives the trip. 01:29:07.763 --> 01:29:11.643 And the internet connection works in the Airbnb. We will be live from Austin, 01:29:11.743 --> 01:29:14.603 and we'd love to have you join us over at jblive.tv. Times. 01:29:14.943 --> 01:29:17.123 Yeah, it's 10 a.m. Pacific. 01:29:17.343 --> 01:29:17.523 Yeah. 01:29:17.603 --> 01:29:19.063 But that means it's noon central. 01:29:19.263 --> 01:29:23.463 Yeah. JupyterBroadcasting.com slash calendar for that. Hey, pro tip for them, right, Wes? 01:29:23.663 --> 01:29:24.163 Oh, yeah. 01:29:25.443 --> 01:29:29.103 The doggo's got the pro tip. that bark right there that's your key to go get 01:29:29.103 --> 01:29:31.763 chapters go get transcripts with the podcasting 2.0. 01:29:31.763 --> 01:29:34.623 App it's a fully loaded podcasting 2.0 feed you gotta check. 01:29:34.623 --> 01:29:36.903 It out let us know if the bark shows up in the transcript and we'll see you 01:29:36.903 --> 01:29:38.303 right back here next week.