Skip to main content
LawHub
Sign In
About LawHub Advantage Thinking About a Career in Law Applying to Law School Thriving in Law School and Beyond Listen to I Am The Law Podcast Trends Sign In
Search

25.05 Reasons to NixOS

May 18, 2025
Listen to this episode

With NixOS 25.05 around the corner, we sit down with a release manager to unpack what's new, what's changing, and what's finally getting easier. Spoiler: it's not just the tooling.

Sponsored By:

Support LINUX Unplugged

Links:

Transcript

WEBVTT 00:00:11.405 --> 00:00:15.985 Hello, friends, and welcome back to your weekly Linux talk show. My name is Chris. 00:00:16.165 --> 00:00:16.965 My name is Wes. 00:00:17.165 --> 00:00:17.945 And my name is Brett. 00:00:18.085 --> 00:00:20.905 Hello, gentlemen. Coming up on the show today, we're going to chat with the 00:00:20.905 --> 00:00:25.325 NixOS release manager and get the inside scoop on what is a unique process to 00:00:25.325 --> 00:00:27.845 NixOS that I don't think any other distribution does. 00:00:28.065 --> 00:00:32.245 And then we're going to dig through the 2505 release and really just geek out 00:00:32.245 --> 00:00:35.725 on our favorite new things like applications and services you can run. 00:00:36.025 --> 00:00:38.585 Really, anybody's going to love that stuff. And then we're going to round it 00:00:38.585 --> 00:00:43.845 out with some great boosts, picks, and a lot more. We do not have a mumble room today. 00:00:44.105 --> 00:00:46.565 Oh, God, this is where they'd be right now, too. 00:00:46.805 --> 00:00:47.325 I miss them. 00:00:48.805 --> 00:00:54.465 I miss them, too. But we're pre-recording because we're going to be flying Sunday 00:00:54.465 --> 00:00:59.465 morning off to Boston to cover Red Hat Summit, and we'll come back with the signal from the noise. 00:01:00.125 --> 00:01:03.025 But first, I want to say good morning to our friends at TailScale. 00:01:03.165 --> 00:01:05.465 TailScale.com slash unplugged. 00:01:05.865 --> 00:01:10.125 TailScale is the easiest way to connect your devices and services to each other wherever they are. 00:01:10.365 --> 00:01:13.985 It is modern networking powered by the WireGuard. 00:01:14.385 --> 00:01:18.805 And when you go to tailscale.com slash unplugged, you get it on 100 devices with three users. 00:01:19.005 --> 00:01:22.205 Not a limited time trial, my friend. No, no, no credit card required. 00:01:22.345 --> 00:01:26.025 That is the plan I am on like three years later. I don't know what it has been. 00:01:26.425 --> 00:01:30.125 I love it. It is fast and simple to set up. If you got five machines, 00:01:30.125 --> 00:01:32.285 you can probably get it running like three minutes. 00:01:32.545 --> 00:01:36.765 It's just about packaged for every dang distro. It's literally one line of my 00:01:36.765 --> 00:01:40.565 Nix config to get it working on Nix. And even on my older Linux systems and 00:01:40.565 --> 00:01:44.365 my strange architecture systems and even some of my embedded Linux systems, 00:01:44.545 --> 00:01:46.345 I have tail scale running on them. 00:01:46.485 --> 00:01:51.465 It builds out something truly useful that the Internet needed from the very beginning. 00:01:51.465 --> 00:01:55.505 And that is a private encrypted way for all your machines, regardless of the 00:01:55.505 --> 00:01:59.445 network infrastructure, behind double carrier grade net, on multiple VPSs, 00:01:59.505 --> 00:02:01.605 on a VM, in a Docker container. 00:02:01.865 --> 00:02:05.025 You bridge all of them together onto one flat tail net. 00:02:05.745 --> 00:02:09.165 Wherever you move them, wherever you start them, they still have the same machine IP. 00:02:09.385 --> 00:02:12.665 And now I don't have any inbound ports on any of my firewalls. 00:02:12.725 --> 00:02:16.105 And I've upgraded the Jupyter Broadcasting Network backend to use Tailscale 00:02:16.105 --> 00:02:17.225 for so many different things. 00:02:17.285 --> 00:02:21.485 A lot of the communication happening between services is happening over Tailscale. 00:02:21.685 --> 00:02:24.625 It's great for the business and it's great for individuals. So go get it for 00:02:24.625 --> 00:02:31.825 free on 100 devices for three users and no credit card required at tailscale.com slash unplugged. 00:02:34.517 --> 00:02:38.537 All right, so we have published the TUI Challenge rules. We're going to spend 00:02:38.537 --> 00:02:42.577 seven days in a terminal user interface with seven objectives to complete. 00:02:42.617 --> 00:02:47.057 We have published the early alpha draft of the rules on our GitHub. 00:02:47.397 --> 00:02:51.877 And the community has also created a discussion thread on our GitHub around it. 00:02:51.977 --> 00:02:54.837 And we're really just looking for feedback at this point, because when we get 00:02:54.837 --> 00:02:57.557 done with all our traveling, we want to kick things off. 00:02:57.597 --> 00:03:01.917 And this is the moment for the community to kind of review, suggest changes, 00:03:02.237 --> 00:03:03.357 improvements, and stuff like that. 00:03:03.357 --> 00:03:08.417 I'm loving. So we've got a issue with discussion happening there. 00:03:08.657 --> 00:03:10.457 I'm loving some of these comments already. 00:03:11.317 --> 00:03:16.517 20 years ago, I was watching Star Trek in the TUI using M player with FBCon 00:03:16.517 --> 00:03:21.077 support while waiting for my Gentoo system to finish building X and KDE. 00:03:21.077 --> 00:03:25.797 Oh my god, he and I may have been building Gen 2 and watching Star Trek at the 00:03:25.797 --> 00:03:28.617 same exact time in two different places in the world. 00:03:28.717 --> 00:03:29.217 Was this you? 00:03:29.617 --> 00:03:30.017 Right. 00:03:30.037 --> 00:03:35.197 This is Ben, and so Ben's conclusion is MPV is therefore cheating. 00:03:36.177 --> 00:03:36.717 Oh, okay. 00:03:37.577 --> 00:03:39.917 Strong argument, you know, it's a pretty strong argument. 00:03:40.057 --> 00:03:43.537 Yeah, no, I mean, you gotta have X, or Weyland, I think it's cheating. 00:03:44.517 --> 00:03:46.897 But you have to have X or Weyland to run the terminal these days. 00:03:47.557 --> 00:03:50.097 Oh man, we really need, this is still a gray area, I think. 00:03:50.097 --> 00:03:55.977 we need people to get in on that conversation we also want to recommend a little 00:03:55.977 --> 00:04:02.817 extra listening for you a little extra dose of podcasting a little extra Chris and Brent like. 00:04:02.817 --> 00:04:04.257 A deep dive Chris and Brent. 00:04:04.257 --> 00:04:11.957 A deep dive yeah Launch 21 really it's the Brent show it was good I really enjoyed 00:04:11.957 --> 00:04:15.957 it you know editor Drew rarely compliments the shows you know good job guys 00:04:15.957 --> 00:04:18.877 but he said what did he say on this one This. 00:04:18.877 --> 00:04:20.677 Was a really, really great episode. 00:04:20.877 --> 00:04:25.437 That's what editor Drew said about, you know, it's good about Bigfoot as a service episode 21. 00:04:26.917 --> 00:04:30.417 Yes, Bigfoot as a service will make sense once you listen to it. 00:04:31.077 --> 00:04:34.977 And also, we want to have a call out here to our completionist in the audience. 00:04:36.002 --> 00:04:39.382 We know some of you are often listening in the past, like we just heard from 00:04:39.382 --> 00:04:41.262 somebody who just got to episode 600. 00:04:41.922 --> 00:04:44.482 So, you know, you can be up to like 15 episodes or more behind, 00:04:44.482 --> 00:04:46.822 and then you kind of catch up over time as a completionist. 00:04:46.882 --> 00:04:52.002 So we want to do a little test here in 615. If you're listening in the past, boost us in the future. 00:04:52.702 --> 00:04:55.162 And we just want to help kind of measure or send us an email, 00:04:55.262 --> 00:05:00.662 let us know where you're at so we can kind of gauge how far back some of you are in the back catalog. 00:05:01.042 --> 00:05:04.062 The completionists of you out there are really something I would just skip right 00:05:04.062 --> 00:05:11.282 to this latest episode myself and then i i might go back i like. 00:05:11.282 --> 00:05:13.462 This it's a little survey of folks who are back in time. 00:05:13.462 --> 00:05:15.942 Yeah exactly that's what we're hoping to hear from i'm. 00:05:15.942 --> 00:05:17.382 Definitely a completionist. 00:05:17.382 --> 00:05:21.542 Yeah it doesn't surprise me at all no no how come what gave it away uh-huh yeah 00:05:21.542 --> 00:05:24.382 i could see that so do you do it for podcasts that you listen to even if they're 00:05:24.382 --> 00:05:26.682 like 600 episodes in yeah. 00:05:26.682 --> 00:05:31.822 I guess i don't necessarily listen to the my particular podcast choices for 00:05:31.822 --> 00:05:38.762 like a current information they're more like story based or something like that uh. 00:05:38.762 --> 00:05:39.382 Evergreen. 00:05:40.082 --> 00:05:41.502 Or i'm just broken maybe. 00:05:41.502 --> 00:05:45.662 Well i actually this is how i do it and again i'd love to just get input from 00:05:45.662 --> 00:05:50.602 the audience on how you do it but i will subscribe to a podcast and if i like it a lot, 00:05:51.162 --> 00:05:54.722 when they haven't released an episode for a bit or like it's the off you know 00:05:54.722 --> 00:05:59.262 whatever i will just go back and like fill in with their previous episodes depending 00:05:59.262 --> 00:06:02.582 on the show i sometimes will do completionist but generally i just sort of cherry 00:06:02.582 --> 00:06:05.322 pick i bet everybody has their own style yeah. 00:06:05.322 --> 00:06:08.102 I think i'm about the same as you kind of go for the ones that seem interesting 00:06:08.102 --> 00:06:12.282 or roll through them depends on how many there are and uh how much time i'm trying to fill. 00:06:15.146 --> 00:06:21.206 While we are traveling to Red Hat Summit and back, we should see Nix OS 2505 00:06:21.206 --> 00:06:23.006 released. And there's a lot. 00:06:23.106 --> 00:06:23.606 Update your flakes. 00:06:24.066 --> 00:06:28.046 Okay. Or your channels. It's okay. It's okay. Channels are okay, too. 00:06:28.326 --> 00:06:33.446 And so this week, we wanted to deep dive into this because it's going to be 00:06:33.446 --> 00:06:34.386 a pretty significant release. 00:06:34.486 --> 00:06:37.986 And there's a lot of things we're looking forward to that anybody's going to find appealing. 00:06:38.246 --> 00:06:42.206 But there's a process when it comes to releasing a distribution. 00:06:42.206 --> 00:06:48.046 And there's probably no one better to speak to about this process than the Nix OS release manager. 00:06:49.986 --> 00:06:55.046 So with a brand new Nix OS just around the corner, 2505, we wanted to talk to 00:06:55.046 --> 00:07:00.366 Tristan Ross, who is a release manager and is working on this fresh release 00:07:00.366 --> 00:07:01.466 right now. We're all very excited. 00:07:01.586 --> 00:07:05.166 I've seen some of your posts online, Tristan. Welcome in to the Unplugged program. 00:07:05.326 --> 00:07:09.046 I've been following this closely, and I'm really glad you can make time early this morning. 00:07:09.426 --> 00:07:10.846 Thank you for having me here. 00:07:11.026 --> 00:07:16.006 Well, thank you. And before we get into it, I know I read a while back that 00:07:16.006 --> 00:07:20.886 you were using Asahi Linux with NixOS for over a year on your laptop. 00:07:21.126 --> 00:07:25.146 I'm wondering, are you still rocking Asahi or have you switched to something else on there? 00:07:25.466 --> 00:07:28.466 Oh, I'm using it right now actually to do this podcast. 00:07:28.926 --> 00:07:31.886 Amazing. Hey, bonus points for that. 00:07:32.046 --> 00:07:33.386 We're getting out-nerded here, boys. 00:07:33.646 --> 00:07:36.386 Is it an M1? I don't know the details, but that's what I have, 00:07:36.446 --> 00:07:38.126 and I know that works pretty well. yeah. 00:07:38.126 --> 00:07:42.366 It's an m1 pro with 16 gigs of ram and a terabyte of storage. 00:07:42.366 --> 00:07:46.486 So you're you're almost on like uh well you're more you're almost on two years 00:07:46.486 --> 00:07:50.266 now then aren't you 1.8 years you got to be almost the two-year mark. 00:07:50.266 --> 00:07:57.606 Yeah because i got this it was mentioned on my blog somewhere that i got it like, 00:07:59.055 --> 00:08:04.755 not last year but the prior year so that would have been 2023 in like august 00:08:04.755 --> 00:08:08.435 from apple's refurbishment site ah. 00:08:08.435 --> 00:08:13.395 Nice that's the way to do it yeah making it work yeah i've had pretty good success 00:08:13.395 --> 00:08:16.475 and look at you doing a call with video and everything we can see your shiny 00:08:16.475 --> 00:08:17.435 face and everything with it. 00:08:17.435 --> 00:08:21.015 I mean that must be mean either you're building a lot or the actual sort of 00:08:21.015 --> 00:08:24.215 build cache and package availability for that system isn't too bad huh. 00:08:24.215 --> 00:08:34.475 So the way i do things is a little bit different where i just have a 120 core ampere ultra max i. 00:08:34.475 --> 00:08:40.335 Love it oh okay that helps things huh i see so you build on that and then just 00:08:40.335 --> 00:08:42.555 install it on the macbook yeah. 00:08:42.555 --> 00:08:48.475 Yeah i just all i do is just tell it hey build my config and then i just tell 00:08:48.475 --> 00:08:53.495 my laptop just pull everything from that and then i reboot and then i use don't 00:08:53.495 --> 00:08:58.155 have to struggle with 16 gigs of ram versus the 256 in my desktop. 00:08:58.475 --> 00:08:58.715 Heck yeah. 00:08:59.115 --> 00:09:01.735 Yeah, that is a little superpower there. I mean, Nix makes it so easy, 00:09:01.795 --> 00:09:04.335 right? As you said, you just point it at your config, it's all the same, 00:09:04.475 --> 00:09:05.915 and pull the build files later. 00:09:06.495 --> 00:09:12.775 That's great. Okay, so I wanted to kind of pick your brain on how the release manager process works. 00:09:13.395 --> 00:09:17.095 Because I might be wrong, but I don't know if it works like any other distro that I'm familiar with. 00:09:17.875 --> 00:09:21.655 Reading through the wiki, it seemed to me like there's two release managers 00:09:21.655 --> 00:09:24.655 at a time, and then after the release, 00:09:25.535 --> 00:09:29.135 after a manager has managed two releases they step down essentially like it's 00:09:29.135 --> 00:09:33.595 there's a built-in term limit for the release manager could you just kind of 00:09:33.595 --> 00:09:36.135 you know explain it to somebody who doesn't quite understand this because it 00:09:36.135 --> 00:09:37.035 seems pretty fascinating. 00:09:37.035 --> 00:09:39.895 Yeah so i believe 00:09:39.895 --> 00:09:44.075 this kind of came about from an rfc from 00:09:44.075 --> 00:09:52.075 2021 2022 somewhere around that time uh where the idea was to like i believe 00:09:52.075 --> 00:09:57.135 it was to get a more like formal process of release managing releases because 00:09:57.135 --> 00:10:03.375 it was an informal like way as far as i understood i wasn't in the project during that time quite yet, 00:10:03.975 --> 00:10:07.235 but the current solution is just you have 00:10:07.235 --> 00:10:11.295 the previous release manager and the coming up release manager and the previous 00:10:11.295 --> 00:10:15.995 one is the one who picks at the end of the release who out of the people who 00:10:15.995 --> 00:10:22.255 have commit access to nick's uh packages to determine who's going to be the 00:10:22.255 --> 00:10:26.275 release manager and we also have release editors and. 00:10:26.275 --> 00:10:30.175 That must help right so in a sense like when you came on to do it for the first 00:10:30.175 --> 00:10:33.815 time that the other person there had at least done it that one other time before 00:10:33.815 --> 00:10:37.535 so there's some sort of knowledge transfer or training or at least just double 00:10:37.535 --> 00:10:38.475 checking on things to help. 00:10:38.475 --> 00:10:44.955 Yeah that's kind of the general idea it is to kind of essentially be like a 00:10:44.955 --> 00:10:47.275 mentoring kind of thing where it's like if the, 00:10:48.559 --> 00:10:52.399 upcoming release manager doesn't like quite understand 00:10:52.399 --> 00:10:55.619 the previous one can help around and it's 00:10:55.619 --> 00:11:01.119 just easier with nix as it grows more uh there's a lot of stuff to kind of manage 00:11:01.119 --> 00:11:05.319 like picking like what packages should be backported or what changes need to 00:11:05.319 --> 00:11:10.059 be rejected because it could cause some issue with the current release because 00:11:10.059 --> 00:11:14.939 it could be just too close to the release window to throw in some breaking change. 00:11:14.939 --> 00:11:18.119 I love this i feel like it kind of highlights the unique challenges nix 00:11:18.119 --> 00:11:22.919 os is such sort of a you know distributed online community without necessarily 00:11:22.919 --> 00:11:26.279 i mean it's all being worked on as we're as we've seen but without necessarily 00:11:26.279 --> 00:11:29.479 a lot of structure at first and so you kind of do have to come up with how do 00:11:29.479 --> 00:11:33.199 we get a good process going that can make all those decisions because there's 00:11:33.199 --> 00:11:37.019 there's a lot actually that it turns out goes into a nix os release huh yeah. 00:11:37.019 --> 00:11:41.799 There's quite a bit i'm not sure how other districts do it because it, 00:11:41.999 --> 00:11:47.619 from my understanding, it's easier to find information on Nix for the release process. 00:11:48.039 --> 00:11:52.739 And with just the matrix being out there and just how easy it is to get into 00:11:52.739 --> 00:11:56.899 the community, it's easy to find like what processes are going on and stuff like that. 00:11:57.319 --> 00:12:00.819 Now, help me understand. So you're a release manager and then there's a release 00:12:00.819 --> 00:12:02.079 editor. What does the editor do? 00:12:02.519 --> 00:12:09.359 The editor will go around the documentation and the release notes and kind of 00:12:09.359 --> 00:12:10.879 just make sure things are clean. 00:12:11.939 --> 00:12:15.799 Like if there's an issue with the previous releases documentation that people 00:12:15.799 --> 00:12:21.219 found, then they kind of like fix up the process for the upcoming release and 00:12:21.219 --> 00:12:24.979 manage just like, oh, this is weird wording. 00:12:25.119 --> 00:12:28.019 Let's just reword this thing a little bit nicer and stuff like that. 00:12:28.279 --> 00:12:33.499 So there's ownership of kind of an important part of the release process at 00:12:33.499 --> 00:12:37.199 these steps is really what it kind of comes down to. Somebody is making sure 00:12:37.199 --> 00:12:40.159 that the process is being managed or that the notes are getting edited. 00:12:40.979 --> 00:12:44.439 That's really great. I mean, I really appreciate that that process probably 00:12:44.439 --> 00:12:47.079 took some time to form, but it seems this formalized. 00:12:47.319 --> 00:12:51.659 What made you want to do it? What made you want to get involved in the release 00:12:51.659 --> 00:12:54.619 process and become a release manager? Why take on the extra work? 00:12:54.839 --> 00:13:01.839 I thought it would be interesting and that I could use my Ampere desktop to 00:13:01.839 --> 00:13:03.539 help around with things. 00:13:04.039 --> 00:13:05.899 Right. Yeah, very true, I suppose. 00:13:06.039 --> 00:13:06.419 How generous. 00:13:06.739 --> 00:13:10.959 Has it been? Would you describe it as interesting or did it meet expectations 00:13:10.959 --> 00:13:14.019 so far? I know we're not at the finish line yet, but we're really close. 00:13:14.279 --> 00:13:15.939 Yeah, I think it's interesting. 00:13:16.519 --> 00:13:17.499 Would you do it again? 00:13:18.879 --> 00:13:22.039 Maybe in like a few years. Not quite sure. 00:13:22.399 --> 00:13:25.959 Ah, yeah, okay. Has it been a considerable time commitment? 00:13:26.379 --> 00:13:31.079 It's one of those things where it's not a huge time commitment, 00:13:31.079 --> 00:13:36.379 But it is There is a certain amount of effort And time that needs to be taken 00:13:36.379 --> 00:13:40.159 to Put into the releases Right. 00:13:41.061 --> 00:13:46.261 I'm curious what you learned about the Nix and NixOS ecosystem by being a release 00:13:46.261 --> 00:13:52.461 manager versus maybe how you were being involved earlier, maybe just a committer or a user. 00:13:52.721 --> 00:13:57.121 So we had different channels of how we push PRs through. 00:13:57.301 --> 00:14:02.401 We have staging, and then we have unstable, and then we have the master branch, 00:14:02.501 --> 00:14:06.041 and then we have the stable branches, which are for every release. 00:14:06.041 --> 00:14:13.841 and so when you're a release manager kind of learn how like you set up those stable branches, 00:14:14.981 --> 00:14:20.241 so that it is possible for people to so that the release is kind of segmented 00:14:20.241 --> 00:14:25.161 away from the current unstable set of things and. 00:14:25.161 --> 00:14:29.301 Is that where some other processes come in like i know there's the zero hydra 00:14:29.301 --> 00:14:32.361 failure component often of the release cycle which i think can be a little opaque 00:14:32.361 --> 00:14:35.061 to folks who are not familiar maybe even what hydra is. 00:14:35.061 --> 00:14:38.301 Yeah that kind of comes from there can. 00:14:38.301 --> 00:14:40.461 You explain hydra to me because i'm not familiar with what it is. 00:14:40.461 --> 00:14:44.221 Hydra is the ci server and 00:14:44.221 --> 00:14:51.501 build farm for nix it is powered by multiple machines that we have access to 00:14:51.501 --> 00:14:57.821 that the infrastructure team manages and the general thing is you just push 00:14:57.821 --> 00:15:03.221 a pr in and then and it just builds whatever, and it puts it into the cache. 00:15:03.581 --> 00:15:07.941 Oh. So it's integrated right into the workflow. So you, from GitHub, 00:15:08.121 --> 00:15:10.341 can essentially have something sent off to this build farm? 00:15:10.721 --> 00:15:20.121 GitHub doesn't really trigger anything, because it's on an automated set of when to run the job sets. 00:15:21.341 --> 00:15:27.541 Typically, from the trunk, we have it where it usually takes about eight hours, 00:15:27.541 --> 00:15:30.021 because Nick's package is so large. 00:15:31.328 --> 00:15:37.768 But the general way it works is it's configured to push the, 00:15:37.768 --> 00:15:44.968 like, things in the pipeline 10 minutes after, like, the current set. 00:15:45.108 --> 00:15:48.788 So if your pipeline was small enough where it's like, oh, there's only a couple 00:15:48.788 --> 00:15:53.548 packages, what it's going to do is it would build, wait 10 minutes, 00:15:53.708 --> 00:15:56.708 then build again with the current set of updates. 00:15:57.448 --> 00:16:01.448 I'm curious how close to what you thought it would be when it started, 00:16:01.768 --> 00:16:04.208 now that we're close to the end, like how accurate were projections, 00:16:04.568 --> 00:16:07.628 estimates, plans at the beginning of the release process, 00:16:08.148 --> 00:16:11.428 and now here we are at the end, like how much has changed, how much didn't work 00:16:11.428 --> 00:16:14.408 out, was it pretty smooth, just that kind of overall picture? 00:16:15.148 --> 00:16:22.468 Yeah, it was pretty smooth. We did have an issue with 2411 that kind of laid 00:16:22.468 --> 00:16:27.928 it a little bit, But we did add a buffer of time when I was figuring out the 00:16:27.928 --> 00:16:29.328 schedule to get around that. 00:16:29.548 --> 00:16:32.888 But as far as I can tell, 2505 is on track. 00:16:33.268 --> 00:16:36.888 That is great to hear. We're going to be traveling when it lands. 00:16:37.488 --> 00:16:41.328 That's why we wanted to get you on a little early. But it doesn't mean we won't 00:16:41.328 --> 00:16:43.348 be upgrading systems just because we're traveling. 00:16:44.528 --> 00:16:45.388 Of course not. 00:16:46.068 --> 00:16:48.448 Tristan, thanks for coming on and explaining some of this because it is a pretty 00:16:48.448 --> 00:16:50.248 unique release process that Nix does. 00:16:50.888 --> 00:16:53.588 And I just think it helps wrap our heads around it a little bit. 00:16:53.748 --> 00:16:54.668 So thanks for coming on early. 00:17:02.468 --> 00:17:08.888 1password.com slash unplugged. That is the number 1 password slash unplugged, all lowercase. 00:17:09.268 --> 00:17:14.288 Okay, I have a question. Do you have an idea, and I mean a really clear picture 00:17:14.288 --> 00:17:18.568 without any exception, where your users are working, what services they use, 00:17:18.568 --> 00:17:23.428 if they're always using company-owned devices and IT-approved apps? I didn't think so. 00:17:23.568 --> 00:17:26.948 So my next question becomes, how do you keep your company's data safe when it's 00:17:26.948 --> 00:17:29.148 sitting on all these unmanaged apps and devices? 00:17:30.145 --> 00:17:33.325 That's where 1Password has an answer to this very hard question. 00:17:33.485 --> 00:17:35.305 It's extended access management. 00:17:35.725 --> 00:17:40.285 1Password extended access management. It helps you secure every sign-in for 00:17:40.285 --> 00:17:45.385 every app on every device because it solves problems that traditional IAMs and 00:17:45.385 --> 00:17:47.925 MDMs really were never designed to touch. 00:17:48.065 --> 00:17:51.705 It's the first security solution that brings all your unmanaged devices, 00:17:51.945 --> 00:17:55.825 all your apps, and even identities under your control. 00:17:55.965 --> 00:17:58.925 It ensures that every user's credential is strong and protected. 00:17:58.925 --> 00:18:02.165 Every device is known and healthy, and every app is visible. 00:18:03.225 --> 00:18:07.045 Imagine how that could change the game, bringing it all into one dashboard. 00:18:07.885 --> 00:18:11.585 I really think I could have gotten a few more years out of being in IT if I 00:18:11.585 --> 00:18:12.805 had something like this. 00:18:12.945 --> 00:18:16.745 I mean, we know how password managers have improved the password hygiene game 00:18:16.745 --> 00:18:19.545 out there, which is just a critical first step for security. 00:18:19.845 --> 00:18:24.165 One password extended access management takes it to the app level, the identity level. 00:18:24.845 --> 00:18:29.465 It really is powerful. And it is right now generally available for companies 00:18:29.465 --> 00:18:30.965 with Okta, Microsoft, Entra. 00:18:31.545 --> 00:18:35.225 And it's in beta for Google Workspace customers, too. So you can just get plugged 00:18:35.225 --> 00:18:37.025 in and get started right away. 00:18:37.465 --> 00:18:40.985 That's right. It's 1Password. You know them for their award-winning password manager. 00:18:41.185 --> 00:18:45.745 Now go check out Extended Access Management. Solve problems that those traditional 00:18:45.745 --> 00:18:49.225 IEMs and MDMs were just simply not built to touch. 00:18:49.405 --> 00:18:54.765 Secure every app, every device, and every identity, even those unmanaged ones. 00:18:54.765 --> 00:18:59.265 You just got to go to onepassword.com slash unplugged. That's all lowercase. 00:18:59.445 --> 00:19:01.545 You can support the show that way, too, and check them out. They got a lot of 00:19:01.545 --> 00:19:05.765 great info there. So it is the number one, password.com slash unplugged. 00:19:06.585 --> 00:19:08.705 Onepassword.com slash unplugged. 00:19:11.965 --> 00:19:15.545 All right. Well, now we know how the sausage is made. I think we got to taste 00:19:15.545 --> 00:19:20.885 the sausage. It's not out yet, but people are hard at work compiling the release notes. 00:19:21.105 --> 00:19:23.385 So, you know, we took a little sneak peek. 00:19:23.385 --> 00:19:27.665 There is some really neat things in here. But let's start with the table stakes, boys. 00:19:28.225 --> 00:19:33.325 And of course, that is the Cosmic Desktop. The Alpha 7 is going to be officially 00:19:33.325 --> 00:19:37.705 supported. It's initial, but it's in here in Nix OS 2505. 00:19:37.885 --> 00:19:40.825 Yeah, there's been various ways you can run it and try it out and all that. 00:19:40.905 --> 00:19:42.225 But now it'll be easier than ever. 00:19:42.305 --> 00:19:43.225 So that's pretty neat to see. 00:19:43.405 --> 00:19:47.305 Has any desktop ever gotten this much traction while still being Alpha? 00:19:47.765 --> 00:19:48.945 I think it's super impressive. 00:19:49.625 --> 00:19:51.625 Yeah, you're right. It is getting everywhere fast. 00:19:51.625 --> 00:19:55.585 This is more one of those Gmail-style alphas, you know, where everyone's used it for years. 00:19:55.745 --> 00:19:56.765 Where's the invite code? 00:19:56.905 --> 00:20:00.625 Yeah, right. The invite code is you've got to install 2505, I guess. 00:20:00.965 --> 00:20:04.645 Of course, we're getting GNOME 48 in here, which is a fantastic release. 00:20:04.645 --> 00:20:05.805 We've covered that pretty extensively. 00:20:06.245 --> 00:20:09.905 And Plasma 6.3.5, which is very fresh, very recent. 00:20:10.505 --> 00:20:13.565 So you're getting all the good standard table-stake desktops. 00:20:13.865 --> 00:20:19.145 But, Wes, there's something in 2505 that feels like, you know, 00:20:20.280 --> 00:20:24.160 We've seen Ubuntu get App 3.0. We've seen Fedora working on DNF5. 00:20:24.520 --> 00:20:31.240 Now it's kind of Nix's turn. And NixOS rebuild ng is a full rewrite of the Nix 00:20:31.240 --> 00:20:34.920 rebuild command, which is what is responsible for rebuilding and upgrading your system. 00:20:35.120 --> 00:20:38.140 Yeah, it's a little bit important if you're going to be running the NixOS system. 00:20:38.280 --> 00:20:41.520 It's the thing that helps you actually turn your configuration and the updates 00:20:41.520 --> 00:20:44.100 you made there into an actually updated system. 00:20:44.260 --> 00:20:48.740 Pretty essential. And there is a litany of reasons. 00:20:49.600 --> 00:20:56.000 I suppose the code for Nix OS rebuild right now is written in Bash and not necessarily 00:20:56.000 --> 00:20:59.040 awful itself. It does mean it's just sort of difficult to refactor. 00:20:59.380 --> 00:21:02.560 It's kind of difficult to parse and get through. It's a big slog. 00:21:03.060 --> 00:21:07.480 It's also a bit of a hacky mess, the developer notes. It also doesn't have proper testing. 00:21:08.260 --> 00:21:12.480 There are some integration tests, but no unit tests and coverage is probably 00:21:12.480 --> 00:21:14.380 a little less than it should be. 00:21:14.980 --> 00:21:18.580 and the code itself predates some of the improvements in nix that have just 00:21:18.580 --> 00:21:23.060 happened over the years and so you give it you bring all that together and instead 00:21:23.060 --> 00:21:29.700 of just fixing up the version written in bash it kind of makes sense to just rewrite nix os rebuild. 00:21:29.700 --> 00:21:33.100 Yeah and that's where we get nix os rebuild ng written 00:21:33.100 --> 00:21:36.280 in python yeah why python well you 00:21:36.280 --> 00:21:39.120 know there's a bunch of reasons but a lot of it has to do with 00:21:39.120 --> 00:21:41.960 it's very flexible dynamic it's a scripting language so you 00:21:41.960 --> 00:21:44.620 can like easily update or change it and you don't 00:21:44.620 --> 00:21:47.480 have to do a whole compile cycle it's also 00:21:47.480 --> 00:21:50.100 well supported in nix right there's lots of 00:21:50.100 --> 00:21:53.140 pythons available there's also python libraries packaged in nix 00:21:53.140 --> 00:21:56.440 if you want to use those and it has a pretty good size standard library 00:21:56.440 --> 00:21:59.120 out of the gate as well so there's lots of stuff you don't even have to rely 00:21:59.120 --> 00:22:03.820 on a package for and at the end of the day it's also got you know it's got good 00:22:03.820 --> 00:22:07.940 linting tools you can now have optional type hints and there's robust support 00:22:07.940 --> 00:22:13.500 for doing unit and integration tests for python So if you look at the PR for this, 00:22:13.580 --> 00:22:16.720 you'll see there's now a bunch more tests added as part of this new version, 00:22:16.940 --> 00:22:18.320 which is always nice to see. 00:22:18.500 --> 00:22:21.260 I would also say, and lots of languages have this, but, you know, 00:22:21.380 --> 00:22:26.840 Python, unlike Bash, you have to actually say what the arguments to your functions 00:22:26.840 --> 00:22:28.940 are. And now you can include types as well. 00:22:29.580 --> 00:22:33.660 Plus, Python has doc strings, which are inline descriptions of what the function 00:22:33.660 --> 00:22:34.960 does, what it takes, what it returns. 00:22:34.960 --> 00:22:41.200 Before you go, explain why, between Bash and Python, why it's for maintainability 00:22:41.200 --> 00:22:44.000 and other developers coming along, why it's superior. 00:22:44.220 --> 00:22:47.940 Yeah, so like in Bash, if you're trying to take a bunch of arguments to a function, 00:22:48.240 --> 00:22:51.860 they're just like the numbered, you know, dollar sign one and two and three. 00:22:52.080 --> 00:22:55.560 And for small things, that works. But if you're trying to write a robust program 00:22:55.560 --> 00:22:58.420 where maybe you're having a lot of peer functions, so they just like take in 00:22:58.420 --> 00:23:02.000 whatever data they need and then transmute it and return you whatever their 00:23:02.000 --> 00:23:03.860 actual logic is supposed to be. 00:23:04.500 --> 00:23:07.940 that can be unwieldy and it's hard to know and then you have to kind of do all 00:23:07.940 --> 00:23:11.740 the documentation yourself whereas just setting it up in Python already gets 00:23:11.740 --> 00:23:15.740 you some of that documentation plus it has more facilities in an organized way 00:23:15.740 --> 00:23:17.060 to add even more if you want to, 00:23:18.334 --> 00:23:20.514 It makes for a good, nice starting point. 00:23:20.874 --> 00:23:23.894 And it's something that's probably easier to maintain by a group of people, too. 00:23:24.114 --> 00:23:28.314 Yeah, exactly. And, you know, Python is simple enough, like for small enough 00:23:28.314 --> 00:23:29.914 things, Bash can be easier. 00:23:30.114 --> 00:23:34.494 Right. But once you've got like logic where you have actual conditionals and 00:23:34.494 --> 00:23:38.174 like multiple paths and you want to have error handling and that's where it's 00:23:38.174 --> 00:23:41.614 kind of it's not everyone's forte and not everyone is like that, 00:23:41.634 --> 00:23:43.934 you know, experience with writing that level of Bash. 00:23:43.934 --> 00:23:46.374 It's one thing to write a simple script that doesn't fork at all. 00:23:46.514 --> 00:23:49.134 And then it's another thing to maintain a complicated program that needs to 00:23:49.134 --> 00:23:53.354 handle flakes and channels and a bunch of other options. All that at once. 00:23:53.734 --> 00:23:58.314 Indeed, it does get complex pretty fast. So something else that we saw land 00:23:58.314 --> 00:24:02.834 in here is NixOS rebuild build image subcommand has been added. 00:24:03.114 --> 00:24:07.054 Now, I know already that I could produce a container image. In fact, 00:24:07.194 --> 00:24:10.334 this is kind of nice because I was looking at Nifty or Notify. 00:24:10.634 --> 00:24:13.414 I talked about that in self-hosted that came out on Friday. 00:24:14.114 --> 00:24:19.574 And in there, they have pretty clear documentation for the Nix configuration syntax. 00:24:19.754 --> 00:24:25.094 And you can really get it working in Nix with probably four or five lines of configuration. 00:24:25.674 --> 00:24:28.834 And from that, you could then generate a Docker container. 00:24:28.954 --> 00:24:32.094 Because I was in a position where I wanted to specify some of this stuff, 00:24:32.134 --> 00:24:35.254 and I don't want to use their environment variable file and all that stuff. 00:24:36.094 --> 00:24:39.094 And in the documentation, I'm like, or just build your own image. 00:24:40.430 --> 00:24:43.610 I could have an image, I could have a container image as the output, 00:24:43.610 --> 00:24:46.830 and I could still run it as a container, but with all the configuration I needed. 00:24:47.010 --> 00:24:49.690 So I love this functionality, but this is something different. 00:24:49.910 --> 00:24:53.210 This is, I believe, correct me if I'm wrong, is this more about, 00:24:53.210 --> 00:24:55.150 like, disk images that you could boot? 00:24:55.370 --> 00:25:01.390 Yeah. So now you can do NixOS rebuild and use build image, new subcommand, 00:25:01.490 --> 00:25:06.010 and it allows you to build a platform-specific disk image from a NixOS configuration. 00:25:06.530 --> 00:25:07.310 Hoo-wee boys! 00:25:07.310 --> 00:25:11.410 So you could then run that as a container or as a virtual machine or as a whole 00:25:11.410 --> 00:25:12.930 machine, depending on what you put in the config. 00:25:13.150 --> 00:25:15.990 Well, and just think about the potential here for testing. You know, 00:25:16.070 --> 00:25:20.810 before you deploy it, you could build a VM, power that up inside QMU and run 00:25:20.810 --> 00:25:23.690 through an entire test process before you actually commit it. 00:25:23.850 --> 00:25:27.530 Yeah. And there has already been some tooling around just building a VM to test out. 00:25:27.630 --> 00:25:32.030 But I think that probably was customized a bit to like be a VM to run on your 00:25:32.030 --> 00:25:36.550 architecture there for that purpose. So I'm imagining that build image may be 00:25:36.550 --> 00:25:38.730 a bit more flexible in terms of exposing this. 00:25:38.910 --> 00:25:40.390 You could already include the 00:25:40.390 --> 00:25:43.090 right modules and then build the right build output and do it yourself. 00:25:43.270 --> 00:25:47.670 But as always, the more neat Nix functionality gets exposed at the surface, 00:25:47.870 --> 00:25:49.610 the more people actually get to use it. 00:25:49.930 --> 00:25:54.350 One last bit here on the other side of the install cycle. When you're setting 00:25:54.350 --> 00:25:59.310 up a new machine, you know, often these days I'm doing that flakes first without any channels. 00:25:59.490 --> 00:26:02.490 But you need an initial flake. and for 00:26:02.490 --> 00:26:05.910 a long time NixOS generate config it would make you your hardware config and 00:26:05.910 --> 00:26:09.790 your sort of starter config template but that was it you had to make your own 00:26:09.790 --> 00:26:13.650 Flake well now there's a dash dash Flake option and it will generate the whole 00:26:13.650 --> 00:26:18.130 thing so you get the original two files plus a Flake.nix so your Etsy NixOS 00:26:18.130 --> 00:26:19.990 out of the box is Flake friendly. 00:26:19.990 --> 00:26:25.290 I think for onboarding new people to Flakes this is going to be such a great tool yeah. 00:26:25.290 --> 00:26:30.370 But they're still not officially supported but yeah you can do this all right all right I'll take it. 00:26:30.370 --> 00:26:31.930 Officially unofficial Yeah. 00:26:32.090 --> 00:26:35.370 Really. Of course, the user statistics say otherwise, they say rather official. 00:26:35.590 --> 00:26:38.630 But one of the things that when we talk about a distro release, 00:26:38.710 --> 00:26:43.590 we don't usually talk about is how much easier it is to do new fun stuff like 00:26:43.590 --> 00:26:47.610 run services or applications and with an XOS release. 00:26:48.562 --> 00:26:53.642 you get new modules. And a module is like a full set of configuration. 00:26:54.562 --> 00:26:58.602 It's isolated for like a particular application. A lot of it's reusable. 00:26:58.802 --> 00:27:01.582 So like I could share a module with the boys, the boys could share a module 00:27:01.582 --> 00:27:02.942 with me and they could get it up and running. 00:27:03.282 --> 00:27:05.282 And it declares options that you 00:27:05.282 --> 00:27:07.942 can define in there for the services and applications you're going to run. 00:27:08.022 --> 00:27:11.722 Maybe even like backups and things like that, that all can be defined in this 00:27:11.722 --> 00:27:13.822 module. Help me here, Wes. Am I doing a decent job? 00:27:13.982 --> 00:27:16.682 Yeah, you can sort of think of it as a function where you put in all these options 00:27:16.682 --> 00:27:19.622 that you say like, oh, I want it to listen on this port, and I want it to support 00:27:19.622 --> 00:27:21.422 these features, or, you know, whatever else. 00:27:21.562 --> 00:27:22.102 Right, open this port in the firewall. 00:27:22.262 --> 00:27:26.622 Yeah, exactly. It generates an updated Nix config for you that sets all those 00:27:26.622 --> 00:27:31.382 options and creates the right systemd services to run whatever it is that it runs. 00:27:31.482 --> 00:27:34.602 And then once you rebuild and start, all that happens. 00:27:34.862 --> 00:27:39.042 Yeah, like I have Nix Cloud on my system as a module, and, oh, it's great. 00:27:39.442 --> 00:27:44.402 So we get a whole bunch of new ones that land in 2505. 00:27:44.522 --> 00:27:45.802 I counted them for you. 00:27:45.942 --> 00:27:46.522 Oh, you did? 00:27:46.582 --> 00:27:46.802 Yeah. 00:27:47.022 --> 00:27:47.222 Okay. 00:27:47.402 --> 00:27:48.442 Uh, 95. 00:27:49.042 --> 00:27:52.882 Ah, yeah. So we'll link to the full list, but we're going to go through like 00:27:52.882 --> 00:27:56.142 our top three, four, five that we think are really awesome and fun. 00:27:56.422 --> 00:27:59.062 And let's start with yours, Wes, because you have a, you have a really good one. 00:27:59.242 --> 00:28:02.242 Yeah, this one I was just scrolling through and it stood out because it seemed fun. 00:28:02.662 --> 00:28:08.782 It's called Mary TTS, an open source multilingual text to speech synthesis system 00:28:08.782 --> 00:28:12.102 written in pure Java and it has a web UI. 00:28:12.282 --> 00:28:15.762 So to get this working, was it just name enable? Yes. 00:28:15.762 --> 00:28:19.702 Yeah, I didn't quite have the module on my system yet. So I was able to just 00:28:19.702 --> 00:28:23.422 run the main executable from Nix packages. It's already in unstable. 00:28:23.702 --> 00:28:26.282 Once you have the module, then you just go into your configuration and you say 00:28:26.282 --> 00:28:30.482 like service name, enable. And you could probably just get off to the races 00:28:30.482 --> 00:28:31.682 from there. And sometimes, yeah. 00:28:32.242 --> 00:28:34.702 All right, so let's try it out. This is the Mary web client. 00:28:35.469 --> 00:28:39.289 For, uh, is it, it's Mary TTS. Okay. All right. All right. 00:28:39.489 --> 00:28:42.869 Hello to the unplugged audience. Please excuse my nervousness. 00:28:43.109 --> 00:28:45.389 This is my world debut after all. 00:28:45.709 --> 00:28:47.989 Boost in if you want me to replace Brent. 00:28:48.249 --> 00:28:51.809 Oh, whoa. It got, it chose violence. 00:28:52.289 --> 00:28:57.089 Um, there are some fun effects you can do. Jet pilot is one of them. 00:28:57.229 --> 00:28:58.749 How does, has anybody tried jet pilot? 00:28:59.029 --> 00:29:00.909 I read about it, but it was too scared to. 00:29:00.929 --> 00:29:04.089 Hello to the unplugged audience. Please excuse my nervousness. 00:29:04.609 --> 00:29:06.589 This is my world debut after all. 00:29:06.789 --> 00:29:10.489 Yeah, you could put in there like, hello, everybody, and it would kind of sound like a pilot. 00:29:10.849 --> 00:29:14.529 Or, you know, you really want to get better at hearing and be able to understand 00:29:14.529 --> 00:29:18.309 all that pilot chat over the radio, which is impossible to understand. 00:29:18.589 --> 00:29:23.149 Apparently, you can also sound like you're in a stadium, so it can generate, and it gives you a... 00:29:23.149 --> 00:29:26.849 Hello to the in-plug audience. Please excuse my nervousness. 00:29:27.109 --> 00:29:29.409 That's kind of fun, and it gives you different output options, 00:29:29.629 --> 00:29:34.009 like a WAV file or an AIF file or an AU file. The AU file is kind of neat. 00:29:34.429 --> 00:29:38.809 And you could also output just words. There's like all kinds of different output 00:29:38.809 --> 00:29:40.829 options in this one simple website here. 00:29:40.929 --> 00:29:42.909 And you have different input types as well. 00:29:43.609 --> 00:29:48.089 Look at this. There's all kinds of different things you can feed into it to have it generate. 00:29:48.669 --> 00:29:52.369 So it gives you a really kind of silly web page to play around with. 00:29:52.769 --> 00:29:54.689 But the engine itself is actually quite capable. 00:29:55.029 --> 00:29:58.969 Yeah. And obviously, you know, we're just using the default voice model it comes 00:29:58.969 --> 00:30:02.609 with. So I'm curious to see. It does sound like, yeah, it does. 00:30:02.809 --> 00:30:05.909 So I'm curious to see how far you can take this with other voice models. 00:30:06.209 --> 00:30:09.449 I saw that you also picked out a handy Postgres tool. 00:30:09.729 --> 00:30:13.349 Ah, yes. This one, I'm surprised it didn't exist already because it's been around 00:30:13.349 --> 00:30:16.189 for a while, but great to have it as easy to run with a module. 00:30:16.189 --> 00:30:17.989 It's called Postgresed. 00:30:18.831 --> 00:30:23.091 So you put a little G in there. Because what it takes is Postgres and adds an 00:30:23.091 --> 00:30:25.051 automatic REST server on top. 00:30:25.171 --> 00:30:29.511 So you get like a nice swagger open API dock and page for it. 00:30:29.671 --> 00:30:34.791 And basically all of your tables and views get exposed via an HTTP API. 00:30:35.031 --> 00:30:36.071 Oh, that's cool. 00:30:36.311 --> 00:30:40.331 So there's tons of stuff where you want to connect and use like an actual SQL connection. But. 00:30:40.451 --> 00:30:40.971 Yeah, not always. 00:30:41.151 --> 00:30:43.631 Yeah, if you have a lot of views you're using or like stored procedures you 00:30:43.631 --> 00:30:48.551 want to call. or just as like a quick way to expose data for backups or for automation. 00:30:48.851 --> 00:30:49.191 For sure. 00:30:49.371 --> 00:30:53.131 Super handy. Okay, and this one I haven't tried but I'm curious about because 00:30:53.131 --> 00:30:54.491 we've discussed several of 00:30:54.491 --> 00:30:58.351 these over the years, as have you guys on self-hosted. It's called Omnom. 00:30:58.771 --> 00:31:00.231 Okay, I love the name, Omnom. 00:31:00.431 --> 00:31:04.911 It's a webpage bookmarking and snapshotting service. Access and share previously 00:31:04.911 --> 00:31:08.051 visited pages without worrying about modifications or availability, 00:31:08.051 --> 00:31:09.771 which I thought could be great too for us. 00:31:09.871 --> 00:31:13.031 It's just ways to like make sure we still have access to sources we're using for a show. 00:31:13.031 --> 00:31:16.351 I've been using Kara Keep for a while, and this looks like it could be another 00:31:16.351 --> 00:31:19.071 one to check out. Om Nom is a great name. 00:31:19.251 --> 00:31:21.671 And then this is maybe a bit self-serving, but check this out. 00:31:21.731 --> 00:31:24.331 It's called YouMurmur, or maybe MicroMurmur. 00:31:24.811 --> 00:31:29.151 It's a minimalistic Mumble server primarily targeted to run on embedded computers 00:31:29.151 --> 00:31:32.071 like routers with an open OS like OpenWRT. 00:31:32.291 --> 00:31:32.571 Whoa. 00:31:32.751 --> 00:31:35.431 So maybe you're running NixOS on like a tiny device. You don't have a ton of 00:31:35.431 --> 00:31:38.431 resources, but you still want Mumble running. You want to be able to host Mumble. 00:31:38.431 --> 00:31:42.091 Or you're like, Brent and I, you've got a couple of low-power machines, 00:31:42.231 --> 00:31:45.631 and you can throw a mumble. Whoa, that's crazy. It's a mumble server? 00:31:45.971 --> 00:31:46.191 Yeah. 00:31:46.511 --> 00:31:50.391 That's so neat. That'd be great for a little family or a little LAN party. 00:31:50.911 --> 00:31:54.691 That's pretty neat. Nice finds. All right, what did you dig out over there, Brent? 00:31:54.831 --> 00:31:58.211 I pulled out a few. They're maybe of a different flavor, but there's one here 00:31:58.211 --> 00:31:59.211 that caught my attention. 00:31:59.651 --> 00:32:05.831 I think it's Gawk API or GoCappy or any way you want to say it. 00:32:05.831 --> 00:32:09.411 The reason it caught my attention is that it's a lightweight self-posted Firefox 00:32:09.411 --> 00:32:12.491 Send alternative without public uploads. 00:32:13.779 --> 00:32:16.639 Which I thought was interesting. So if you want to share some files, 00:32:16.759 --> 00:32:20.179 I don't know, with friends, family, that kind of thing, you can throw them up on this thing. 00:32:20.599 --> 00:32:25.719 I think partly this stood out for me because I used and loved Firefox and I 00:32:25.719 --> 00:32:26.739 thought it was a great service. 00:32:26.859 --> 00:32:30.919 I would imagine it got misused quite a bit when they had it, 00:32:30.999 --> 00:32:33.519 but as a public service, it's just awesome for everybody. 00:32:33.699 --> 00:32:39.959 Well, what's neat too is it looks like if you wanted to slap AWS or any S3 compatible 00:32:39.959 --> 00:32:42.439 storage as the backend, it supports that. 00:32:42.439 --> 00:32:46.559 So you don't have to host the files, but you could still have a private Firefox-like 00:32:46.559 --> 00:32:53.299 send with S3 kind of, if you want, to call it unlimited backend storage support, 00:32:53.359 --> 00:32:55.119 I suppose. I mean, that's kind of a nice feature. 00:32:55.799 --> 00:32:59.699 Yeah, and you just maybe add to this, but if not, right, just set up something 00:32:59.699 --> 00:33:02.499 that goes through and deletes things in there every once in a while. 00:33:02.499 --> 00:33:04.839 Or some of these services offer that built in. 00:33:05.079 --> 00:33:05.899 Be a good feature. 00:33:06.279 --> 00:33:09.679 Yeah, that's one of the main features here is things just disappear whenever you decide to. 00:33:09.799 --> 00:33:10.179 Oh, perfect. 00:33:10.179 --> 00:33:15.339 Oh, okay. GoK API, and as you would probably guess, it's mostly written in Go, 00:33:15.499 --> 00:33:18.319 which probably makes it pretty easy to get up and going. 00:33:18.919 --> 00:33:22.679 Also, most Go things tend to be really easy to build with Nix, which is great. 00:33:23.099 --> 00:33:24.099 I know you got one more, though. 00:33:24.279 --> 00:33:24.999 Oh, I got two more. 00:33:25.119 --> 00:33:25.639 Oh, you do? Okay. 00:33:25.839 --> 00:33:27.939 One of them that stood out for me is actual budget. 00:33:28.159 --> 00:33:29.259 Uh-huh. Yeah, I saw this one. 00:33:29.359 --> 00:33:34.159 I've been looking for something to improve my, let's say, perspectives on my 00:33:34.159 --> 00:33:38.639 finances, and actual budget kept coming up, and I never had an easy way to deploy 00:33:38.639 --> 00:33:43.659 it. And as a NixOS module, sounds like I should dive into this one. 00:33:43.879 --> 00:33:46.719 You want something that will tell you how much money you're spending on Thai food, basically? 00:33:47.099 --> 00:33:47.459 Yeah. 00:33:47.779 --> 00:33:49.159 I mean, probably good to at least know. 00:33:49.679 --> 00:33:54.339 How much money we spent on mediocre food in California is really what I wanted to know. 00:33:54.339 --> 00:33:55.299 No, you don't want to know that. 00:33:55.379 --> 00:33:56.259 Oh, you're right. Okay. 00:33:56.399 --> 00:33:58.659 And you don't want to see the van category. 00:33:58.819 --> 00:34:03.159 No. If you're going to do budgeting and financing, it's nice to have something 00:34:03.159 --> 00:34:05.039 that's local first and run it on your own machine. 00:34:05.179 --> 00:34:08.079 You don't want a third party to have access to all of your banking details? 00:34:08.079 --> 00:34:08.919 Well, they already do. 00:34:09.019 --> 00:34:09.939 It's a strange concept. 00:34:10.279 --> 00:34:12.899 You know. All right. You ready to hear my finds? Oh, no, you had one more. 00:34:13.079 --> 00:34:16.619 One last one I thought more I chose for the audience than for myself. 00:34:16.679 --> 00:34:22.179 It's Cursor, which is a VS Code-based editor that uses AI to help you do coding and stuff. 00:34:22.299 --> 00:34:25.299 I think some of our audience, at least a subsection, would be interested in 00:34:25.299 --> 00:34:28.319 that. And as a module, it might be nice and fast to get going. 00:34:28.959 --> 00:34:34.099 I agree. Now, get ready for the ones I found because these are going to knock your socks off. 00:34:34.099 --> 00:34:41.099 The first one has been a bit of a bear to manage via Docker because you've got 00:34:41.099 --> 00:34:45.719 to build it every time, and then it builds the container, and then it produces 00:34:45.719 --> 00:34:47.439 a Docker Compose, and then you run that. 00:34:47.899 --> 00:34:50.379 So every update, it's quite the process. 00:34:50.579 --> 00:34:52.159 And it's a great app, but yeah, a bit. 00:34:52.459 --> 00:34:55.679 Yep. And I am talking about Pinchflat. 00:34:56.859 --> 00:35:01.499 I love this application. You know, we were joking about taking your stuff offline. 00:35:01.919 --> 00:35:09.079 This really is, it's YouTube offline for me. And it is a media manager for YouTube. 00:35:09.319 --> 00:35:13.919 And it's a self-hosted app that in the background, when your favorite YouTube 00:35:13.919 --> 00:35:18.639 channels publish new content, it pulls it down gently in the background. 00:35:18.639 --> 00:35:20.279 It'll also do playlists. 00:35:20.519 --> 00:35:24.879 And it'll capture the information necessary for, say, like Jellyfin to then 00:35:24.879 --> 00:35:30.039 index it and display it like all of your other TV shows and movies in your home entertainment system. 00:35:30.379 --> 00:35:33.759 It has an easy-to-use web interface, so you go in and you can add the URLs to 00:35:33.759 --> 00:35:37.539 the channels you want, set things like don't download their tinies. 00:35:37.859 --> 00:35:40.699 You know, some channels, like, they post a video a week, and then during the 00:35:40.699 --> 00:35:43.299 week, they'll post, like, three or four tinies that are clips of the video you 00:35:43.299 --> 00:35:44.739 already watched. I don't need those. 00:35:44.979 --> 00:35:48.359 And I don't want to watch a tiny on my television anyways. so don't download 00:35:48.359 --> 00:35:52.719 the tinies it's just a checkbox boom right there no tinies but also you can 00:35:52.719 --> 00:35:55.839 have an age out content so you're not filling up your hard drive with youtube content. 00:35:56.919 --> 00:36:00.119 So you know i have mindset after 30 days it deletes 00:36:00.119 --> 00:36:02.839 the videos even if i've watched them or not and i can have a different setting 00:36:02.839 --> 00:36:07.159 for the ones i have watched and there's one youtube channel where the guy he 00:36:07.159 --> 00:36:10.639 always gets embarrassed by his videos so he deletes them well i don't have that 00:36:10.639 --> 00:36:15.959 problem anymore it'll also download audio only content from youtube so nice 00:36:15.959 --> 00:36:18.639 if you're doing your podcast that way. You can grab them with this. 00:36:19.019 --> 00:36:23.799 It's basically, it's handling YouTube DLP, but then it has advanced options 00:36:23.799 --> 00:36:26.339 to link it to an API to your account. 00:36:27.403 --> 00:36:31.263 And that gives it the ability via the YouTube API to crawl new releases. 00:36:31.263 --> 00:36:34.703 And so it can do it even faster than the traditional manual scan method. 00:36:34.983 --> 00:36:37.703 And probably maybe have a better time with the right limiting. 00:36:38.163 --> 00:36:41.723 Yes. So pinch flat. And then it has a UI that lets you know this is all the 00:36:41.723 --> 00:36:45.243 latest downloads. These are how many videos you downloaded. This is how much space it's taken up. 00:36:46.523 --> 00:36:51.763 And for me, it means that I'm not watching these videos over my LTE or Starlink connection. 00:36:52.043 --> 00:36:54.743 Because the server is downloading them for me in the background. 00:36:54.743 --> 00:37:00.383 and then I just go into Jellyfin and I have a YouTube library and this has added 00:37:00.383 --> 00:37:03.863 all the NFO information that Plex or Jellyfin or Cody needs. 00:37:04.563 --> 00:37:07.543 And so they all just show up there and I just watch them like a regular TV show 00:37:07.543 --> 00:37:10.203 over my LAN with no buffering, high quality. 00:37:10.423 --> 00:37:14.923 So that's pinch flat. And now it's simple to enable and I no longer have to 00:37:14.923 --> 00:37:18.983 go through this entire process of downloading it manually, building it manually, 00:37:19.223 --> 00:37:20.883 producing the Docker Compose and then running it. 00:37:21.403 --> 00:37:25.463 Nerdy detail that really doesn't matter But we don't yet have a soundboard clip 00:37:25.463 --> 00:37:27.943 for this, but it's written in Elixir, which I just like to see. 00:37:28.043 --> 00:37:29.763 Oh, yeah. It's been really nice. 00:37:33.603 --> 00:37:36.823 Could somebody just do a little work to that? Maybe give it some effects and 00:37:36.823 --> 00:37:39.583 that could be it. That could be our Elixir. So that's really, 00:37:39.743 --> 00:37:41.463 really, really happy to see Pinchflat in there. 00:37:42.123 --> 00:37:46.283 Tracker, which we've talked recently about the Big D Witch and tracking ourselves 00:37:46.283 --> 00:37:50.663 with that. This is another GPS tracking platform that's self-hosted and lets 00:37:50.663 --> 00:37:53.163 you use things like own tracks to get location information. 00:37:53.483 --> 00:37:56.203 And then you can plug it into other front-end applications. 00:37:56.623 --> 00:38:01.063 Nextcloud offers one and others to actually visualize all of your tracking. 00:38:01.463 --> 00:38:05.603 So that's nice to see. How about this one, boys? Crabhole. 00:38:06.963 --> 00:38:12.143 Crabhole. It's a cross-platform piehole clone written in Rust using Hickory 00:38:12.143 --> 00:38:18.803 DNS and TrustDNS. and now it's available as services.crab-hole and you can enable it. 00:38:19.023 --> 00:38:21.443 Yeah, send all that tracking stuff right to the crab hole. 00:38:21.583 --> 00:38:25.683 Yeah. And then just a couple of quick hits, if you will, because I was just 00:38:25.683 --> 00:38:26.843 really happy to see this. 00:38:26.983 --> 00:38:30.503 There are three different Nostre packages landing. Really happy. 00:38:31.463 --> 00:38:34.483 Nostre RS Relay is a Nostre Relay written in Rust. 00:38:34.963 --> 00:38:39.643 There's also Haven, which is a high availability vault for events on Nostre to store Nostre events. 00:38:39.903 --> 00:38:44.583 And there's now, I don't know how you pronounce it, but it's s-t-r-f-r-y stir 00:38:44.583 --> 00:38:48.523 fry i was thinking stir fry i like that a relay for the nostril protocol i just 00:38:48.523 --> 00:38:52.963 mentioned this because nix is going to would make such a solid oh this is. 00:38:52.963 --> 00:38:57.183 Great well i mean especially too there's more things you can do with the nostril 00:38:57.183 --> 00:38:59.203 wallet connect stuff if you're doing lightning things. 00:38:59.203 --> 00:38:59.963 So maybe you. 00:38:59.963 --> 00:39:01.703 Want to host your own nostril relay for that. 00:39:01.703 --> 00:39:05.163 No kidding and now it's going to make that a little bit easier a lot easier 00:39:05.163 --> 00:39:09.663 actually and then And last but not least, because I just love the Image Project, 00:39:09.903 --> 00:39:14.743 which is IMMICH, and it is essentially a self-hosted Google Photos replacement, 00:39:15.970 --> 00:39:19.690 It has an ecosystem of applications around it now. It's getting very popular. 00:39:19.850 --> 00:39:26.130 And so there are apps that make it possible to publicly share your images, lots of other things. 00:39:26.230 --> 00:39:29.190 I have one that's called like Image Kiosk. 00:39:29.570 --> 00:39:34.670 And all it does is takes URL parameters and then creates pretty slideshows for 00:39:34.670 --> 00:39:36.270 all the tablets that I have Home Assistant. 00:39:36.550 --> 00:39:40.210 And so all my tablets, when they're not being used, are running through my favorite 00:39:40.210 --> 00:39:42.770 photos being powered by Image Kiosk. 00:39:43.110 --> 00:39:47.910 Well, another app now that is easily installable is going to be ImagePublicProxy, 00:39:47.950 --> 00:39:52.510 which is a proxy for sharing image albums without exposing the actual image 00:39:52.510 --> 00:39:54.410 API to the public internet. 00:39:54.610 --> 00:39:55.370 Oh, that's great. 00:39:55.690 --> 00:40:00.050 Mm-hmm. And again, it's just services.image-public-proxy, you know, 00:40:00.110 --> 00:40:02.570 enable. And you've got it, assuming you've got the module. 00:40:03.270 --> 00:40:06.770 And it's going to make a, you know, it kind of rounds out the image hosting, 00:40:07.530 --> 00:40:10.430 and makes it really straightforward for people that want to get started with 00:40:10.430 --> 00:40:13.850 a Google Photos alternative, but don't know all of these intricacies. 00:40:13.850 --> 00:40:17.890 Now they can go read these plain, practically plain text modules and services, 00:40:18.170 --> 00:40:20.210 figure out what the options are and get up and going. 00:40:20.930 --> 00:40:25.670 And Image is one of those where you truly feel a sense of freedom when you break free of Google Photos. 00:40:25.950 --> 00:40:30.030 And the search is fantastic. The face recognition has been getting really great. 00:40:30.350 --> 00:40:32.230 The geolocation stuff has always 00:40:32.230 --> 00:40:35.190 been solid since they've added it and it does the map overlay stuff. 00:40:35.370 --> 00:40:40.150 We talked about it last week. We pulled it into the Big D Witch to overlay location 00:40:40.150 --> 00:40:45.270 information from Image. it's a very very powerful application with a broader 00:40:45.270 --> 00:40:48.850 and broader ecosystems of apps around it and it's getting simpler and simpler 00:40:48.850 --> 00:40:50.230 to self-host now with this stuff. 00:40:50.230 --> 00:40:55.090 Just with this release you get a sweet little box you know um get it on nyx 00:40:55.090 --> 00:40:59.090 put it on tail scale you get next cloud going you put tracker on there you get 00:40:59.090 --> 00:41:02.090 image going you get a proxy going then you have. 00:41:02.090 --> 00:41:02.970 A stir fry for dinner. 00:41:02.970 --> 00:41:07.030 Yeah and then right and then you can connect all that stuff from your your mobile 00:41:07.030 --> 00:41:10.970 device over tail scale and you're off to the races that's basically you build 00:41:10.970 --> 00:41:15.250 yourself a custom boot disk image with the new build image thing and then deploy it on a server oh. 00:41:15.250 --> 00:41:19.270 My gosh it's the golden setup it really is there you go westpain just figured it out, 00:41:22.022 --> 00:41:25.742 This show is looking for another sponsor. If you want to support independent 00:41:25.742 --> 00:41:29.562 Linux content that is focused on its audience, drop me a line, 00:41:29.722 --> 00:41:31.242 chris at jupiterbroadcasting.com. 00:41:31.462 --> 00:41:34.182 I'll make a great deal for a listener out there that wants to advertise their 00:41:34.182 --> 00:41:35.982 product, service, or business on the show. 00:41:36.222 --> 00:41:40.802 Reach the world's largest best Linux audience. Let's chat, chris at jupiterbroadcasting.com. 00:41:41.122 --> 00:41:44.222 Now, if you're not in a position to become a sponsor, but you still want to 00:41:44.222 --> 00:41:47.742 support the show and keep us going, linuxunplugged.com slash membership, 00:41:48.222 --> 00:41:54.082 the bootleg really is something special we have a lot of extra content on weeks like this. 00:41:55.002 --> 00:41:58.022 We're really just kind of cutting loose and just chatting 00:41:58.022 --> 00:42:01.842 with our members the bootleg offers a lot more but we also for those of you 00:42:01.842 --> 00:42:04.962 that are time constrained have a slightly shorter version of the show that's 00:42:04.962 --> 00:42:07.982 available for our members you get two options the bootleg or the ad free version 00:42:07.982 --> 00:42:11.842 you also get that when you become a jupiter party member that way you support 00:42:11.842 --> 00:42:15.742 all the shows you get access to all of the features and we do have some special 00:42:15.742 --> 00:42:17.742 content after the travel that we are, 00:42:18.302 --> 00:42:21.082 stewing up i'm not saying it's cooking yet but we're like you know 00:42:21.082 --> 00:42:24.142 we're we got it simmering in a crock pot for the base and we 00:42:24.142 --> 00:42:28.882 have some neat ideas some real cool keen ideas for our jupyter party members 00:42:28.882 --> 00:42:33.722 some exclusive things so jupyter.party for the entire network or linuxunplugged.com 00:42:33.722 --> 00:42:39.242 slash membership for this humble show and you can give each production a little 00:42:39.242 --> 00:42:44.062 boost when you use Fountain or any of the apps out there that are listed at podcastapps.com. 00:42:44.202 --> 00:42:47.802 And then we also get to read your message. And it's a signal for the show about 00:42:47.802 --> 00:42:50.862 your feelings towards the content, positive or negative. 00:42:51.222 --> 00:42:54.542 And it's a signal for the value as well. So there's a lot of ways to support 00:42:54.542 --> 00:42:55.802 an independent production like this. 00:42:56.302 --> 00:42:58.882 Each one of them just takes a little bit of effort on your time, 00:42:58.962 --> 00:43:00.802 but that's why we call it a value for value production. 00:43:01.102 --> 00:43:05.042 We put the show out there for free. We put, you know, God knows how many hours 00:43:05.042 --> 00:43:06.362 into the show every single week. 00:43:06.362 --> 00:43:10.342 we do that and then if you get a little value from the show you send some back 00:43:10.342 --> 00:43:14.962 our way either through becoming a sponsor becoming a member or by boosting that's 00:43:14.962 --> 00:43:18.142 it it's pretty simple i know sounds complicated but when you think about it 00:43:18.142 --> 00:43:20.922 it's really not that hard right you got to figure it out right yeah you got 00:43:20.922 --> 00:43:24.782 it did you did you catch all that i think so okay all right i'm. 00:43:24.782 --> 00:43:27.742 Gonna just i'm just gonna rely on brent i'm gonna he's gonna. 00:43:27.742 --> 00:43:30.062 Yeah did you take notes uh. 00:43:30.062 --> 00:43:31.402 I opened my. 00:43:31.402 --> 00:43:34.542 Note application i'm gonna have to do it again now i'll. 00:43:34.542 --> 00:43:35.182 Listen next week, 00:43:39.197 --> 00:43:43.457 Well, we got a whole bunch of boosts here and one baller from the Wine Eagle. 00:43:43.717 --> 00:43:47.877 It is 26,666 sets. 00:43:50.597 --> 00:43:54.697 I feel like there might be a message in there. And he says, I hate going to 00:43:54.697 --> 00:43:56.437 the Nick's option search site for options. 00:43:56.757 --> 00:44:03.197 So check out Nick's search TV and you won't have to leave the terminal. Okay. 00:44:03.677 --> 00:44:06.537 This is just setting us up for when we don't have access to a browser. 00:44:06.757 --> 00:44:11.837 Oh, he does have a Tui challenge tip for us. games and GUI work programs should they be allowed? 00:44:12.677 --> 00:44:16.997 Well, GUI work programs I mean you gotta do your work. 00:44:17.137 --> 00:44:21.377 So the idea is to do as much of your work in the terminal as possible I think. 00:44:21.957 --> 00:44:25.577 And then if you look at the challenge rules we have like specific things to 00:44:25.577 --> 00:44:26.857 accomplish in the terminal. 00:44:27.377 --> 00:44:31.317 And I think that leaves room for like okay I gotta go do XYZ in this like web 00:44:31.317 --> 00:44:34.557 app that work requires or something. So what are you gonna do, right? 00:44:34.717 --> 00:44:38.377 Yeah, we're not gonna have a Microsoft Teams calls one of our checklist items. 00:44:38.917 --> 00:44:42.877 He says, I was having problems boosting from Breeze. I didn't see the JB node in the split. 00:44:43.577 --> 00:44:46.777 That does happen sometimes. The Lightning network is a peer-to-peer network. 00:44:47.137 --> 00:44:50.617 And the way Breeze works, which is very awesome, is it's a node in your pocket. 00:44:50.917 --> 00:44:54.297 And so I think sometimes when it starts up, it needs, you know, 00:44:54.377 --> 00:44:59.437 a minute, I don't know, 30 seconds to kind of like discover the network possibly. What do you think? 00:44:59.497 --> 00:45:03.037 It may also help to send, like just send a low SAT test boost or something. 00:45:03.157 --> 00:45:03.457 Yeah, yeah, yeah. 00:45:03.537 --> 00:45:06.877 We can always skip reading those or, you know, they'll still get counted as your contribution. 00:45:06.877 --> 00:45:11.037 Send like a 50 sat boost or 500 sat, something small and make sure it gets to 00:45:11.037 --> 00:45:13.317 them and then send your, send your boost that you want read on the show. 00:45:13.577 --> 00:45:16.257 That's probably, I know that's a little wonky and we'll probably have better 00:45:16.257 --> 00:45:17.517 answers for you very soon. 00:45:18.097 --> 00:45:22.577 So keep listening, but appreciate that baller boost, Wine Eagle. Thank you very much. 00:45:23.997 --> 00:45:27.277 Mr. Nick 86 boosts in with a row of duck. 00:45:29.079 --> 00:45:34.539 Uh, merch goes to crunch bang bus crunch bang slash bus. 00:45:34.839 --> 00:45:37.639 Yeah. We're trying to come up with good names for the bus. 00:45:37.879 --> 00:45:38.739 I do like crunch bang bus. 00:45:38.879 --> 00:45:44.019 Crunch bang bus isn't bad. Uh, we've had so many. Do any really stick out to 00:45:44.019 --> 00:45:45.679 you so far, brand of ones that are real winners. 00:45:45.959 --> 00:45:49.579 I have a note here. Someone, uh, suggested the into penguin. 00:45:50.919 --> 00:45:53.499 Right? Cause it's a road track independent. Yeah. 00:45:53.599 --> 00:45:53.739 Okay. 00:45:54.059 --> 00:45:54.199 Yeah. 00:45:54.499 --> 00:45:56.219 Or the USS Brenter prize. 00:45:56.599 --> 00:45:58.719 I liked soyager, but yeah, Brenter prize is better. 00:45:59.299 --> 00:46:00.559 Soyager was really good. 00:46:01.539 --> 00:46:03.399 There's also the Maple Meanderer. 00:46:03.979 --> 00:46:08.359 That's pretty fitting. Which ones for you, though, have really stuck out? 00:46:08.619 --> 00:46:09.679 Probably Poutine Wagon. 00:46:10.739 --> 00:46:12.679 Oh, that's my least favorite. 00:46:12.819 --> 00:46:13.219 Oh, okay. 00:46:13.339 --> 00:46:14.639 Because it doesn't really rhyme. 00:46:14.739 --> 00:46:15.879 We should open up some voting. 00:46:16.459 --> 00:46:18.359 Well, we'll have to get there. We have to get some good names. 00:46:18.399 --> 00:46:20.599 And remember, it has to look good on a whole van ramp. 00:46:20.859 --> 00:46:24.419 And maybe a shirt and a hat. You know, as a car guy, Brett needs a hat. 00:46:25.099 --> 00:46:29.359 Well, Tomato boosted in 13,369 sets. 00:46:29.579 --> 00:46:29.959 All right. 00:46:32.719 --> 00:46:36.279 Actually, in a couple boosts, and one of these is 1, 2, 3, 4, 5 sets. 00:46:40.419 --> 00:46:46.379 The headsets sound good to me. And for the TUI challenge, I think sixles should 00:46:46.379 --> 00:46:50.939 be allowed, since it's something that real deck terminals did. 00:46:50.939 --> 00:46:54.839 Otherwise, I vote no for external graphics. 00:46:55.179 --> 00:46:55.259 Whoa. 00:46:55.399 --> 00:46:55.719 Whoa. 00:46:55.999 --> 00:46:56.179 Okay. 00:46:57.563 --> 00:47:02.763 I was really loving the idea of getting a Mac Plus off of eBay that still works 00:47:02.763 --> 00:47:05.263 and then just getting some sort of terminal app. 00:47:05.523 --> 00:47:06.343 Like literally your terminal? 00:47:06.463 --> 00:47:10.743 So if I had to go to a GUI, I'd have to only could run on the Mac Plus. Probably not viable. 00:47:11.523 --> 00:47:17.403 We'll see. So, you know, we've been getting pretty good feedback on the headsets, I think. 00:47:17.623 --> 00:47:22.043 I am extremely grateful for the audience's support there and then also the feedback. 00:47:22.043 --> 00:47:27.323 it makes me feel immensely more comfortable traveling with them and it sounds 00:47:27.323 --> 00:47:32.103 silly but you got to agree it made life so much easier on the road brent oh 00:47:32.103 --> 00:47:37.163 yeah not it's really the mic stands that are the problem because our studio 00:47:37.163 --> 00:47:41.083 mics need a stand in even small portable table stands well you. 00:47:41.083 --> 00:47:45.323 Need the right table i've run into this several times where the table is incompatible 00:47:45.323 --> 00:47:49.183 and then what do you do we've had to figure out all sorts of different ways. 00:47:49.183 --> 00:47:52.843 So it meant having a range of movement, which is always an issue when we're live. 00:47:53.183 --> 00:47:58.643 And I think you have been sort of perfecting your own use of the microphone. 00:47:58.783 --> 00:48:01.963 You were trying it in studio last week, so you're happy with that. 00:48:02.423 --> 00:48:05.863 I'm still trying to get used to drinking with the thing, but we'll get there. 00:48:06.203 --> 00:48:08.223 I did have a couple of times where I bumped it trying to drink, 00:48:08.343 --> 00:48:11.463 but I think Drew just cleaned that up. Thank you, Drew. Appreciate you. 00:48:11.803 --> 00:48:15.263 They do continue here. Also, what about another bonus challenge to do social 00:48:15.263 --> 00:48:18.623 media from the two-y. Maybe a toot for Mastodon is a great example. 00:48:18.863 --> 00:48:22.623 I was considering social media, but I don't like social media, 00:48:22.683 --> 00:48:24.003 so I didn't put it on the challenge. 00:48:24.523 --> 00:48:25.363 Well, we could try. 00:48:25.903 --> 00:48:28.923 That might be a nice bonus, though. Somebody should submit that as a PR. 00:48:28.923 --> 00:48:29.743 Send your two-y to it. 00:48:29.923 --> 00:48:37.463 Yeah, maybe a suggestion, too. Gene Bean comes in with 4,444 sats. 00:48:37.743 --> 00:48:40.503 You know what? I'm going to give that some strange odds. 00:48:41.943 --> 00:48:44.343 I don't know. He also might have been going for a McDuck. 00:48:46.585 --> 00:48:49.605 He says, I actually really like the sound of the headset you're using in studio. 00:48:49.785 --> 00:48:51.045 And he has a question for you, Wes. 00:48:51.605 --> 00:48:55.945 Why not check out TSD proxy? It was mentioned on self-hosted last week. 00:48:56.045 --> 00:49:00.145 So this could be like an alternative to the tail scale module that you created 00:49:00.145 --> 00:49:01.045 and announced last week. 00:49:01.285 --> 00:49:04.425 Yeah, and it's a great option. There's lots of great little this. 00:49:04.565 --> 00:49:08.885 There's a few other, I think, competing projects, various methods to proxy things 00:49:08.885 --> 00:49:13.305 to tail scale with or without their own tail scale host entry. 00:49:13.645 --> 00:49:17.405 This one does that, right? so you can basically tell it to proxy things it can 00:49:17.405 --> 00:49:21.645 access and for each thing it proxies, make it show up on Tailscale, which is super great. 00:49:21.925 --> 00:49:27.025 So I think this would be a good alternative if you don't want to go the full sidecar route. 00:49:27.245 --> 00:49:31.745 I was interested in the network isolation factor as well. 00:49:32.105 --> 00:49:37.085 So it sort of gives you full, that app can do multiple things on its own, 00:49:37.405 --> 00:49:40.645 listen, configure however you want because that's full access to the interface. 00:49:40.705 --> 00:49:44.465 So I think it'd probably be a little more flexible, especially given whatever 00:49:44.465 --> 00:49:47.465 this proxy might support although it might support everything practically that 00:49:47.465 --> 00:49:51.445 you need I also think TSD proxy would be a great candidate especially since 00:49:51.445 --> 00:49:55.865 you can just configure it with a YAML file for a NixOS module right? 00:49:56.425 --> 00:50:03.225 So that could be another way to get very equivalent functionality Mentat boosts in with 2048 sats, 00:50:05.425 --> 00:50:09.325 I'd like to recommend LandVan for Brent's new ride Oh. 00:50:09.325 --> 00:50:14.565 LandVan does slide right off the tongue land van. I kind of like that. 00:50:14.765 --> 00:50:17.885 It'd have some, you know, being a good lineage here. 00:50:17.965 --> 00:50:21.225 A friend of mine had a minivan we dubbed the land van back in the day, 00:50:21.325 --> 00:50:26.365 which was often used during our regular land parties. Up until the engine got fired. 00:50:26.565 --> 00:50:29.805 Oh, do we want that bad juju? Oh, nobody got hurt. 00:50:29.805 --> 00:50:32.425 Nobody got hurt. It would be a story, but let's hope not. 00:50:32.545 --> 00:50:37.485 You know, because you could really simplify the logo to just like an Ethernet plug. 00:50:38.445 --> 00:50:44.765 You know, the land van. Maybe with like a hat or like an ethernet plug with wheels on the road. 00:50:45.545 --> 00:50:49.025 Right. And like a windy road in Utah. You know what I'm saying? 00:50:49.105 --> 00:50:53.025 I feel like maybe you've got a crush on this van. Maybe you're falling in love with this. 00:50:53.185 --> 00:50:54.345 I might love another man's van. 00:50:54.525 --> 00:50:54.825 I might. 00:50:55.305 --> 00:50:58.105 That's a good one. Land van should go on the night. I don't know if it's a winner, 00:50:58.105 --> 00:51:02.085 especially with that bad juju there at the end, but I think it's worth consideration. 00:51:02.605 --> 00:51:06.205 Well, our van hasn't caught on fire yet, but it does smell like waffles. 00:51:06.425 --> 00:51:06.885 That's true. 00:51:06.885 --> 00:51:10.985 While Oppie 1984 boosted in 4000 sets. 00:51:14.264 --> 00:51:17.464 Note to self here, don't use the auto-suggestions for names. 00:51:17.724 --> 00:51:20.304 Sorry, Brent, for calling you Brett last episode. 00:51:20.504 --> 00:51:25.184 Hold on. No apology necessary at all, Opi1984. 00:51:25.264 --> 00:51:28.864 We have been riffing on that idea all week. 00:51:28.964 --> 00:51:29.784 Yeah, behind the scenes. 00:51:30.224 --> 00:51:34.424 Yeah, I got a whole new podcast lined up for Brett Johnson, so don't worry about 00:51:34.424 --> 00:51:37.344 it at all. I think you may have inspired my best podcast idea yet. 00:51:37.924 --> 00:51:43.104 That's a cute dog, too. As for why truckers have migrated to GMRS, 00:51:43.104 --> 00:51:47.964 The stated reason is better audio quality, being FM rather than the CB's AM. 00:51:48.404 --> 00:51:52.264 And antennas are generally pre-tuned and slightly better range. 00:51:52.484 --> 00:51:55.584 Oh, so that was going to be my question. I thought maybe the AM would be like 00:51:55.584 --> 00:51:57.984 on the lower hertz spectrum. Lower. 00:51:58.444 --> 00:52:02.924 Maybe you would transmit fervor. But sounds like GMRS actually has better range. 00:52:03.284 --> 00:52:04.524 Well, that settles it right there. 00:52:05.184 --> 00:52:09.404 Obby continues here. The unstated reason, though, is since the late 70s, 00:52:09.564 --> 00:52:12.484 four-wheelers were getting on the CB's and messing things up for drivers. 00:52:12.484 --> 00:52:14.524 So they switched to get away from them. 00:52:15.184 --> 00:52:21.224 And, well, those reasons stated above as well. Besides, a license is just $35 and there is no test. 00:52:21.544 --> 00:52:25.324 Well, isn't that funny how if you just put a $35 license in front of it, 00:52:25.904 --> 00:52:30.044 you get all the guys that are just sitting there slack-jawing off. 00:52:30.244 --> 00:52:30.944 No more riff-raff. 00:52:31.044 --> 00:52:33.664 We use, you know, the consumer radios that you just... 00:52:34.304 --> 00:52:35.784 Family radios, they're sometimes called. 00:52:35.924 --> 00:52:39.484 Yeah, family radios. Yeah. And the wife and I were on a road trip one time. 00:52:40.542 --> 00:52:45.762 And for, I don't know, eight minutes, as we were driving along, we heard two buddies. 00:52:46.522 --> 00:52:50.702 And the first one, where are you at? Oh, yeah, I'm just getting back in range. 00:52:50.862 --> 00:52:53.222 Sorry about that. I had to stop and use the bathroom. 00:52:53.502 --> 00:52:58.522 I had. And then he goes on to describe what was a significant BM for this guy 00:52:58.522 --> 00:53:01.802 over the radio on the channel the wife and I are on. 00:53:01.982 --> 00:53:02.562 Quite the movement. 00:53:02.622 --> 00:53:04.782 And we don't want to, like, jump in because we're listening. 00:53:05.462 --> 00:53:08.062 And they don't know we're listening. So, like, we had to wait until we were, 00:53:08.062 --> 00:53:10.422 like, way out of range. And then we're like, did you hear that? 00:53:12.782 --> 00:53:18.242 So, yeah, there's people on there just, I don't know, talking about anything, I guess. 00:53:19.322 --> 00:53:23.222 I got slow-brained today. So one last piece of follow-up for Gene there. 00:53:23.342 --> 00:53:23.802 Oh, yeah, sure. 00:53:23.982 --> 00:53:27.802 It does also work with Netbird, and I think it should work with something like 00:53:27.802 --> 00:53:30.222 Nebula or other services to the module. 00:53:30.322 --> 00:53:34.042 Yeah, so that'd be another reason if you wanted something that wasn't Tailscale-specific support. 00:53:34.182 --> 00:53:39.982 But could, or, you know, it could swap out, too. Outdoor Geek's back with 10,000 SATs. 00:53:41.202 --> 00:53:45.422 the van name should be good on a t-shirt. I know it should look good on a t-shirt. I agree. 00:53:46.062 --> 00:53:50.782 Like disco or cosmic. I came up with Vamoose. 00:53:53.302 --> 00:53:54.142 That's pretty good. 00:53:54.182 --> 00:53:54.782 That's pretty good. 00:53:54.922 --> 00:53:58.882 Vamoose looks even slightly better. That's V-A-M-O-O-S with no E at the end. 00:53:59.222 --> 00:54:02.862 I'm imagining a t-shirt art and van also being moose. 00:54:03.142 --> 00:54:08.082 Like, oh my God, this is so good. Like the cat bus in my neighborhood, Toronto. 00:54:08.942 --> 00:54:13.942 The moose is so obviously the branding to lean into for the van. Oh, I love this idea. 00:54:14.062 --> 00:54:16.682 If you think about it, even the E they're deleting there, you know. 00:54:16.842 --> 00:54:18.422 And E is sort of just like antlers. 00:54:18.702 --> 00:54:21.202 Yeah, that's true. The E could be antlers. 00:54:21.222 --> 00:54:23.722 It could be like a little moose thing, you know, a little moose logo. 00:54:23.962 --> 00:54:27.482 The moose has to be on the list. I really like that, Outdoor Geek. 00:54:27.542 --> 00:54:28.322 Adding it to the list. 00:54:28.442 --> 00:54:31.122 All right. Thank you. That's a good one. That's a good one. 00:54:32.582 --> 00:54:35.242 Bologna 9,000 moose in with 6,000 sets. 00:54:38.753 --> 00:54:43.233 Hey guys, I'm behind a couple months, but here's 6,000 for 600. 00:54:43.413 --> 00:54:43.553 Hey! 00:54:44.033 --> 00:54:44.953 Keep up the good work. 00:54:45.833 --> 00:54:47.633 I love it when we get the... 00:54:50.073 --> 00:54:53.693 All right. You get some plaid, too. I love it when we get the people in the 00:54:53.693 --> 00:54:57.473 back catalog catching up and letting us know. We want more of that. Thanks, Belagna. 00:54:57.913 --> 00:55:00.353 How long ago does episode 600 feel to you guys? 00:55:00.813 --> 00:55:01.573 Two years ago. 00:55:01.713 --> 00:55:03.353 Yeah, I would say about the same. 00:55:03.533 --> 00:55:04.473 Yeah, it's about two years ago. 00:55:04.973 --> 00:55:09.753 Well, Raving Rob sent in 13,345 sets. 00:55:11.573 --> 00:55:16.673 Y'all are trying to rename the Bang Bus when the only choice in your minds should be the Shebang Bus. 00:55:19.033 --> 00:55:22.373 Maybe that would change the perspective people get when they hear the name. 00:55:22.673 --> 00:55:26.093 I think the problem is when you take the name and you combine it with the look 00:55:26.093 --> 00:55:29.833 of the vehicle, the two things take you to the wrong direction. 00:55:30.313 --> 00:55:35.713 You know, Shebang Bus might be better. but Vamoose with Vamoose branding. 00:55:36.793 --> 00:55:40.053 Send in your boost to vote for what do you think it should be? 00:55:40.053 --> 00:55:42.993 So good. It's so good. Maybe we're missing something but yeah I'd like to know. 00:55:43.233 --> 00:55:48.953 Oh there's a PS here. I messed it up already. It says PS. It's pronounced raving grub. 00:55:49.793 --> 00:55:52.413 I just dropped the extra G so sorry about that. 00:55:53.753 --> 00:55:56.413 Alright well thank you everybody who boosted it. We had Shy Fox come in too 00:55:56.413 --> 00:56:00.393 with some comments on the headset just under the 2000s at cutoff. 00:56:01.073 --> 00:56:07.093 We also had wartime boost in he misunderstood, he thought Darwich or the Big 00:56:07.093 --> 00:56:09.213 D Witch as I call it was iOS only, 00:56:10.173 --> 00:56:14.333 no, you can use OwnTracks and lots of other applications including just Home Assistant, 00:56:14.813 --> 00:56:19.193 to feed into the Big D Witch they do have an iOS only app that just connects 00:56:19.193 --> 00:56:24.293 directly only to it, but you do not need that Brent and Wes used OwnTracks on 00:56:24.293 --> 00:56:25.573 their Paizels just fine if. 00:56:25.573 --> 00:56:28.893 You're real crazy, you just make sure you take a new picture every time you 00:56:28.893 --> 00:56:31.333 make a significant movement and then you let it suck that up. 00:56:31.333 --> 00:56:35.353 Yeah then use image as your location thing and yeah i would actually not be 00:56:35.353 --> 00:56:38.593 a half bad solution for just partial tracking as long as you're really good 00:56:38.593 --> 00:56:40.393 about taking pictures one. 00:56:40.393 --> 00:56:45.293 Thing we didn't mention last week too that came up was that you can import a ton of. 00:56:45.293 --> 00:56:46.213 Different services. 00:56:46.213 --> 00:56:47.653 Into devar including. 00:56:47.653 --> 00:56:50.773 Just gpx files so like a garmin something 00:56:50.773 --> 00:56:53.593 like that you could actually pull into it and then visualize on there so 00:56:53.593 --> 00:56:56.313 thank you everybody who sends in feedback and supports the 00:56:56.313 --> 00:56:58.993 show with a boost it's one of our absolute favorite segments of 00:56:58.993 --> 00:57:01.773 the show and it brings up conversations we never would have 00:57:01.773 --> 00:57:04.533 thought to include we had 22 of 00:57:04.533 --> 00:57:10.553 you stream sats as you listened and collectively you all stacked 43 270 sats 00:57:10.553 --> 00:57:14.313 by just streaming them to us and we appreciate that a lot and then when you 00:57:14.313 --> 00:57:21.793 combine that with our boosters we stacked a humble but appreciative 128 572 sats. 00:57:26.051 --> 00:57:28.771 Now, we are recording a little early, so if we missed your boost, 00:57:28.891 --> 00:57:30.111 we'll catch it in the next episode. 00:57:30.231 --> 00:57:34.071 And please do consider supporting the show with the boost. It is an open-source, 00:57:34.231 --> 00:57:35.671 peer-to-peer network with no middleman. 00:57:35.851 --> 00:57:39.411 Nobody takes a cut, and we don't have to ask anybody for those funds. 00:57:39.451 --> 00:57:41.431 And they go directly to our wallets via the splits. 00:57:41.991 --> 00:57:45.071 It is a value-for-value system that is pretty awesome. 00:57:45.251 --> 00:57:49.211 And, of course, a shout-out to our members. You also pretty darn awesome. 00:57:49.211 --> 00:57:53.111 We appreciate everybody who supports any production of the show and everybody 00:57:53.111 --> 00:57:57.331 who supported episode 615 of your Unplugged podcast. 00:57:59.411 --> 00:58:03.951 Two picks. Two picks. I was on fire this week. 00:58:04.371 --> 00:58:09.231 Actually, what it was is one of my tools I use just very helpfully on the back 00:58:09.231 --> 00:58:14.191 end, like doubled the image size that it generates, which is great. 00:58:14.191 --> 00:58:19.551 It's nice and high resolution, but now it means I'm going from like a 1.2 megabyte 00:58:19.551 --> 00:58:22.911 downloaded file to like four to six megabytes, depending on the image. 00:58:23.011 --> 00:58:25.591 And then like I want to slap that in our matrix chat room. 00:58:25.751 --> 00:58:29.011 Well, every time I do that, I'm tossing like a six meg file on our matrix server 00:58:29.011 --> 00:58:32.031 and then everybody has to pull down a six meg file to view. It's crazy. 00:58:33.171 --> 00:58:36.471 So I've been using something for a little while to solve this problem. 00:58:36.571 --> 00:58:39.291 And I realized time for a make good got to talk about on the show. 00:58:39.591 --> 00:58:42.591 It's called switcheroo or switcheroo. 00:58:43.091 --> 00:58:47.751 I guess the same. And it is a very simple desktop application that converts 00:58:47.751 --> 00:58:53.751 between different image file types and also resizes them very easily. 00:58:53.811 --> 00:58:57.511 It's fired up, add the image, resize, done. Love that. 00:58:57.671 --> 00:58:59.991 That sounds pretty convenient, especially if you don't, you know, 00:59:00.531 --> 00:59:03.751 want to have to remember image magic convert command lines. 00:59:04.471 --> 00:59:07.711 Now, what if you need to solve this problem for more than just yourself? 00:59:08.391 --> 00:59:14.071 Friends, family, significant others. Or maybe, maybe you don't want to have it just on one computer. 00:59:14.191 --> 00:59:21.791 Well, that's where Muzanook comes in, a self-hosted local image optimizer that runs in your browser. 00:59:22.211 --> 00:59:27.791 So it is a very easily well-designed, easy-to-use application that is a browser 00:59:27.791 --> 00:59:29.391 app that will work offline, actually. 00:59:30.311 --> 00:59:35.031 And it strips out all of the stuff you don't want to share when you're sharing 00:59:35.031 --> 00:59:39.471 an image. So it pulls out, like, the location information and the camera information 00:59:39.471 --> 00:59:40.871 that can be stored in the image. 00:59:40.971 --> 00:59:44.771 It lets you adjust the image quality size. You can set a target file size and 00:59:44.771 --> 00:59:46.151 then have it figure out all the stuff. 00:59:46.311 --> 00:59:50.291 You can move between JPEG, PNG, and WebP, and they're adding more file formats. 00:59:50.851 --> 00:59:55.031 It is a progressive web app that's really well designed. And all the image processing 00:59:55.031 --> 00:59:57.751 happens offline in your browser. 00:59:58.171 --> 01:00:01.491 So you don't have to have it running on a super nice server. So I have it on my Odroid. 01:00:02.071 --> 01:00:06.471 And everything stays on your device. And both of these are GPL3. 01:00:07.803 --> 01:00:11.223 So you can go real easy and just a simple little desktop app, 01:00:11.243 --> 01:00:16.763 or you can go the Manzanuk route, which is actually very simple to get running as well. 01:00:17.043 --> 01:00:19.423 Pretty straightforward Docker Compose if you want to go that route. 01:00:19.863 --> 01:00:23.283 I'm happy to report Switcheroo is packaged already in Nix. 01:00:24.023 --> 01:00:25.583 And then I was able to just quickly 01:00:25.583 --> 01:00:30.723 find here someone is working on a derivation in Flake for Manzanuk. 01:00:31.223 --> 01:00:35.703 Can I just have you look at this UI for a second? I know this is an audio podcast, 01:00:35.863 --> 01:00:37.543 but both of you pull it up there in your browser for just a sec. 01:00:38.483 --> 01:00:40.163 How clean and simple is that? 01:00:40.303 --> 01:00:40.943 Oh, I like it. 01:00:41.283 --> 01:00:43.363 Super spousal approval factor here, boys. 01:00:43.563 --> 01:00:44.903 Yep. I think anyone could use this. 01:00:45.063 --> 01:00:49.483 My wife, for her patients, writes a newsletter, and she's often putting images in there. 01:00:49.583 --> 01:00:53.043 And I'm like, you know, we could take out all the privacy and all the private 01:00:53.043 --> 01:00:57.263 info. You could resize it and make it really, really efficient for the email client to load. 01:00:57.503 --> 01:01:00.423 It looks like it has a nice mobile, you know, looks good on mobile, too. 01:01:01.183 --> 01:01:05.343 You know, I wish these functions were built into just our mobile operating systems 01:01:05.343 --> 01:01:11.383 from, just natively because well we all need to resize stuff and we all need 01:01:11.383 --> 01:01:14.283 to keep ourselves more private and that should just be built in I think. 01:01:14.283 --> 01:01:16.923 I don't think most people that take pictures are even aware, 01:01:17.243 --> 01:01:20.183 well I'm sure our listeners are but I don't think most folks know that there's 01:01:20.183 --> 01:01:23.743 XF data in there that has location, date, camera type, 01:01:24.443 --> 01:01:29.103 you can tell a lot from that stuff and then you go post that online or share 01:01:29.103 --> 01:01:33.023 it in like a Telegram or a Discord or a Matrix, you could be giving away information 01:01:33.023 --> 01:01:37.363 you don't intend to And also, you're probably uploading a file larger than you need to. 01:01:37.503 --> 01:01:40.403 Or if you're on iOS, you're getting those HEIC files. 01:01:41.383 --> 01:01:44.823 You know, you can run it through this thing and make a JPEG or a PNG out of 01:01:44.823 --> 01:01:47.463 it and then send it to somebody that can actually render that. 01:01:47.803 --> 01:01:51.243 So these are just a couple of great apps. But I think Mazinuk is really the 01:01:51.243 --> 01:01:52.983 one to go for if you've got the time to get it running. 01:01:53.203 --> 01:01:55.443 And then you can just share it with your friends and family. 01:01:55.903 --> 01:01:56.923 You don't think that's how it's pronounced? 01:01:57.303 --> 01:02:00.083 No, I just love the way you're pronouncing it. Can you do it one last time? 01:02:00.443 --> 01:02:01.663 Mazinuk. How do you say it, Wes? 01:02:02.703 --> 01:02:02.983 Mazinuk. 01:02:03.143 --> 01:02:03.623 Oh, okay. 01:02:03.783 --> 01:02:05.263 I was going to go with Mazinuk. 01:02:05.423 --> 01:02:06.543 I was hoping you would. 01:02:06.643 --> 01:02:07.123 Oh, yeah, there we go. 01:02:07.203 --> 01:02:10.903 I was hoping one of you would because I thought that was a possible pronunciation. 01:02:10.903 --> 01:02:12.263 But you prefer... 01:02:12.263 --> 01:02:14.683 They are capitalizing it, so I think we have to yell it. 01:02:14.903 --> 01:02:15.363 Yeah, that's why I was. 01:02:16.163 --> 01:02:16.963 It's... Mazanoke! 01:02:17.203 --> 01:02:21.403 Thank you. I am just going with what the developers clearly intended. Yeah. 01:02:21.803 --> 01:02:22.483 That's all we ask. 01:02:22.743 --> 01:02:25.103 All right, as we wrap up, remember, we're looking for all of you that are on 01:02:25.103 --> 01:02:29.283 the tail end back catalog completionist trajectory. Tell us where you're at. 01:02:29.703 --> 01:02:34.323 Say hi to us into the future. Of course, we want your feedback on our TUI challenge. 01:02:34.323 --> 01:02:36.983 We'll have that linked in the show notes, so you can go over to our GitHub there. 01:02:37.283 --> 01:02:41.723 We're also soliciting names for Brent's van. And I think we've got to figure that out pretty soon. 01:02:41.923 --> 01:02:46.423 And last couple of weeks to get your TUI apps in. So anything we could use in 01:02:46.423 --> 01:02:48.983 the terminal to survive and then share with the audience, please. 01:02:49.543 --> 01:02:52.583 Let's make this actually something that might stick. And I think the best way 01:02:52.583 --> 01:02:56.663 for some people to stick using TUI applications would be to actually give them 01:02:56.663 --> 01:03:01.103 a good set to choose from, a real shot. So please boost those in as well. 01:03:01.323 --> 01:03:05.643 Now, we will have sort of a weird live schedule coming up for the next few weeks 01:03:05.643 --> 01:03:07.683 as we're traveling for different events and whatnot. 01:03:07.683 --> 01:03:12.903 so the best source of information is always going to be jupiterbroadcasting.com 01:03:12.903 --> 01:03:18.243 slash calendar or even better and more up to date will be a podcasting 2.0 app 01:03:18.243 --> 01:03:22.543 where we will be able to set a pending and actual lifetime that'll show up in your app of choice. 01:03:22.543 --> 01:03:26.843 You can also just do mpv jblive.fm and periodically check. 01:03:26.843 --> 01:03:31.003 Yeah yeah or just pop it in a browser tab jblive.fm are they live oh nope that's 01:03:31.003 --> 01:03:36.003 an old one if you hear music and farting around it's probably live That's how you know. 01:03:36.943 --> 01:03:40.743 Links to what we talked about today at linuxunplugged.com slash 615. 01:03:41.483 --> 01:03:44.723 Matrix info. Membership info. Mumble info. 01:03:44.943 --> 01:03:49.583 How to contact us. It's all over there. Hyperlinks on a website at linuxunplugged.com. 01:03:50.043 --> 01:03:53.363 And then we mentioned it earlier. But go. If you're ready, go get some more 01:03:53.363 --> 01:03:56.843 Brent. Go get some more me and hear the full story of the van rescue. 01:03:57.043 --> 01:03:59.383 The complete story since we left off last week. 01:04:00.083 --> 01:04:04.643 Weekly launch.rocks. Episode 21. Editor Drew says it's a banger, 01:04:04.803 --> 01:04:06.063 which means you're probably going to love it. 01:04:06.443 --> 01:04:09.243 Thanks so much for tuning in this week's episode of the Unplugged program. 01:04:09.503 --> 01:04:13.783 And we'll see you next Tuesday, as in Sunday, which, who knows, might be a Monday.
Previous episode Next episode

Search

Search

Listen on

Apple Podcasts Spotify RSS feed

Tags

Finance