Skip to main content
LawHub
Sign In
About LawHub Advantage EXPLORING LAW Preparing for the LSAT Applying to Law School EXCEL IN LAW SCHOOL CHARTING YOUR CAREER Listen to I Am The Law Podcast Trends Sign In
Search

Arch Enemies

Aug 24, 2025
Listen to this episode

Arch is under fire, two weeks and counting. We'll break down the mess, and share a quick fix. Plus, the killer new apps we've just added to our homelabs.

Sponsored By:

Support LINUX Unplugged

Links:

Transcript

WEBVTT 00:00:11.483 --> 00:00:16.123 Hello, friends, and welcome back to your weekly Linux talk show. My name is Chris. 00:00:16.283 --> 00:00:16.963 My name is Wes. 00:00:17.183 --> 00:00:17.963 And my name is Brent. 00:00:18.623 --> 00:00:23.423 Hello, gentlemen. Coming up on the show today, we're going to start with the 00:00:23.423 --> 00:00:26.483 attack that's been going on for Arch Linux for over two weeks, 00:00:26.563 --> 00:00:28.323 tell you what we know, and some quick workarounds. 00:00:28.743 --> 00:00:32.803 Plus, we found some really useful apps that we're adding to our home lab this 00:00:32.803 --> 00:00:35.683 week, so we'll share those with you, and then we'll round out the show with 00:00:35.683 --> 00:00:38.723 some great feedback boosts and too many picks. 00:00:38.723 --> 00:00:43.363 So before I go any further, let me say hello to our virtual lug. 00:00:43.683 --> 00:00:45.503 Time-appropriate greetings, Mumble Room. 00:00:45.783 --> 00:00:48.063 Hello. Hey, Chris. Hey, Wes. And hello, Brent. 00:00:48.423 --> 00:00:52.083 Hi, everybody. Shout out to all of you up there in quiet listening and everybody 00:00:52.083 --> 00:00:54.723 joining us live in the Matrix Room. 00:00:55.263 --> 00:00:57.723 And shout out to our friends at Defined Networking. 00:00:58.523 --> 00:01:03.503 Defined.net slash unplugged. Go check out their decentralized VPN built on the 00:01:03.503 --> 00:01:07.503 incredible open source Nebula platform that you can completely self-host yourself 00:01:07.503 --> 00:01:11.383 the entire infrastructure or take advantage of their managed service and get 00:01:11.383 --> 00:01:16.043 100 devices for free when you go to define.net slash unplugged. 00:01:16.243 --> 00:01:22.083 It's really, truly a unique product because unlike others, you have the entire 00:01:22.083 --> 00:01:25.023 infrastructure if you want it with Nebula. You can run your own lighthouses. 00:01:25.423 --> 00:01:28.763 You can do all those things, and it means there could be a few things you have 00:01:28.763 --> 00:01:31.983 to set up. And you found Nebula Manager this week. 00:01:32.103 --> 00:01:36.083 Yeah, it builds itself as a unified CLI tool to manage and maintain multiple 00:01:36.083 --> 00:01:38.123 Nebula VPN servers with ease. 00:01:38.663 --> 00:01:41.643 I don't know if it's fair to call it a TUI, but it sure kind of is a TUI. 00:01:41.823 --> 00:01:44.363 It's very TUI adjacent if it's not a TUI. 00:01:44.743 --> 00:01:47.803 But yeah, it lets you just manage all of the Nebula things you need, 00:01:47.923 --> 00:01:52.543 including some niceties, like managing your local system's inbound and outbound 00:01:52.543 --> 00:01:54.023 firewall rules, if you have them on. 00:01:54.243 --> 00:01:57.303 So when you get Nebula going, your firewall just works. 00:01:57.583 --> 00:02:01.203 And of course, they also support multi-node reachability. They have that latency 00:02:01.203 --> 00:02:03.183 table where you can see how your latency is to the different systems, 00:02:03.243 --> 00:02:04.443 which is really cool to look at. 00:02:04.603 --> 00:02:08.423 Auto-update scheduler in there via cron that's really cool, 00:02:09.231 --> 00:02:11.451 Very nice interface, too. It looks very straightforward. 00:02:11.891 --> 00:02:18.111 Yeah, and I'm excited to see more tools being built on top because the open 00:02:18.111 --> 00:02:21.731 source Nebula stuff really gives you a really good framework to build on, 00:02:21.731 --> 00:02:25.411 and it's just kind of been waiting for folks to take advantage of making some 00:02:25.411 --> 00:02:29.231 smooth workflows on top to suit whatever the particular use cases are. 00:02:29.331 --> 00:02:30.411 And we're seeing more and more of those. 00:02:30.511 --> 00:02:30.651 Yeah. 00:02:30.911 --> 00:02:33.631 I thought every now and then I'd highlight a couple of them because this one's 00:02:33.631 --> 00:02:37.491 really great. We'll put a link in the show notes. Nebula powers thousands of 00:02:37.491 --> 00:02:38.791 data centers, thousands of systems. 00:02:39.231 --> 00:02:43.071 I've heard some really amazing use cases. You may be even surprised to learn 00:02:43.071 --> 00:02:48.071 that there are vehicles on the road that are powered by Nebula. So check out Nebula. 00:02:48.331 --> 00:02:53.131 It's built from the ground up to work across a very diverse data center, multi-network setup. 00:02:53.291 --> 00:02:56.811 So if you've got things behind carrier-grade NAT, if you've got systems that 00:02:56.811 --> 00:03:01.011 are in one VPS on another VPS and on your LAN, or if you've got a data center 00:03:01.011 --> 00:03:04.711 with tens of thousands of systems in it, they all will work with Nebula. 00:03:05.091 --> 00:03:08.951 Nothing else offers Nebula's level of resilience, speed, and scalability. 00:03:09.231 --> 00:03:12.991 So you can build it all yourself or get started with their managed system and 00:03:12.991 --> 00:03:18.411 100 hosts absolutely free, no credit card required. Go to defined.net slash unplugged. 00:03:21.268 --> 00:03:23.848 Okay, I got a little ask out there for the audience, for those of you, 00:03:23.928 --> 00:03:26.848 and I know PJ is one of them, that have Frigate systems. 00:03:27.108 --> 00:03:29.928 Something I've been thinking about for a long time is the Frigate NVR, 00:03:30.048 --> 00:03:31.008 the network video recorder. 00:03:32.108 --> 00:03:35.828 Really nice, and if you pair it with something like a Coral USB accelerator, 00:03:36.228 --> 00:03:40.808 you can do a lot of fancy image recognition near on the fly. 00:03:40.808 --> 00:03:45.828 And one of the things they've added in their 0.16 release, that kind of makes 00:03:45.828 --> 00:03:50.088 me want to really go all in now, is they have license plate detection. 00:03:50.088 --> 00:03:52.588 Oh, build your own flock, finally. 00:03:52.968 --> 00:03:57.808 Right. I want my own way of knowing when somebody new has pulled up at the RV 00:03:57.808 --> 00:03:59.828 when I'm not there or when it's somebody we know. 00:03:59.988 --> 00:04:04.408 And so I'm on a farm and there are farmhands that have trucks and they drive 00:04:04.408 --> 00:04:07.348 around all the time. And that's totally normal expected behavior. 00:04:08.188 --> 00:04:12.468 Occasionally, randos show up or people that need help or service or whatever 00:04:12.468 --> 00:04:16.448 show up. And I'd like to know when it's the difference between a vehicle I've 00:04:16.448 --> 00:04:22.148 seen and and sort of proved and a vehicle that I've never seen before and then get an alert for those. 00:04:22.248 --> 00:04:25.148 And there's a lot of cool tooling you can do around the learning in general. 00:04:25.988 --> 00:04:29.048 Plus, as you know, everything I kind of look at these days, there's an angle 00:04:29.048 --> 00:04:30.228 with Home Assistant here. 00:04:30.348 --> 00:04:32.868 I mean, there has to be. Otherwise, you won't even let it on the show. I mean, what? 00:04:33.088 --> 00:04:35.808 Yeah, you can actually like. So for this license plate, yeah, right. 00:04:36.068 --> 00:04:39.568 It has to be for this license plate automation detection, for example, 00:04:39.668 --> 00:04:43.788 you can build alerts and Home Assistant. So you can have home assistant aware of this license plate. 00:04:44.008 --> 00:04:46.048 Yeah. Okay. This sounds pretty darn cool. I like where you're going. 00:04:46.188 --> 00:04:52.228 I know. Very cool. But of course I have to do it the way that is the least recommended, 00:04:52.748 --> 00:04:54.608 the least reliable because of my 00:04:54.608 --> 00:05:00.568 situation. And that is I need audience recommendations for wifi cameras. 00:05:00.908 --> 00:05:05.128 I know Chris use ethernet, use POE Chris use ethernet. They're going to be more 00:05:05.128 --> 00:05:07.528 reliable. Chris, you got to use ethernet. I can't. 00:05:07.928 --> 00:05:12.248 My God. If you want to come out and make Ethernet go through places that I didn't 00:05:12.248 --> 00:05:14.988 know Ethernet could go through, I would love to have you. I'll host you. 00:05:15.068 --> 00:05:16.288 You can stay for as long as you need. 00:05:17.273 --> 00:05:22.993 But I need Wi-Fi recommendations. Ideally, even things that are battery-powered is a major bonus. 00:05:23.153 --> 00:05:26.093 Like some of the commercial competitors, like the Ring and the Wyze cams, 00:05:26.173 --> 00:05:30.133 maybe not Wyze, but like Ring cams and some of the others, they have battery packs in them. 00:05:30.193 --> 00:05:32.733 So as long as they're on your Wi-Fi network, you can stick them out in the yard. 00:05:32.873 --> 00:05:34.753 You can stick them out on the fence, all over the place. 00:05:34.813 --> 00:05:36.193 Super easy deployment, yeah. 00:05:36.413 --> 00:05:38.553 Yeah. So battery-powered would 00:05:38.553 --> 00:05:41.833 be a major bonus or USB-powered if I can plug it into a battery pack. 00:05:42.373 --> 00:05:46.813 And so I'm looking for outdoor and indoor recommendations, both Wi-Fi. 00:05:46.813 --> 00:05:49.833 Yes, I know that work well with Frigate. 00:05:49.933 --> 00:05:53.833 And so that's probably RTSP and OVFH or whatever it's called. 00:05:54.233 --> 00:05:57.613 I'm going to be learning all about that. But right now, before I dive too deep 00:05:57.613 --> 00:05:59.833 and spend my precious sats, 00:05:59.913 --> 00:06:04.333 I'd like to get the recommendations from the audience out there because I've 00:06:04.333 --> 00:06:06.973 looked at a lot of different options and I've just kind of checked out over 00:06:06.973 --> 00:06:10.333 and over again because I could see myself spending a bunch of money on cameras 00:06:10.333 --> 00:06:11.813 and not really having the results I want. 00:06:12.053 --> 00:06:14.633 I know I have to lower my expectations when it comes to Wi-Fi, 00:06:14.673 --> 00:06:16.273 but if you have any suggestions, 00:06:16.273 --> 00:06:22.153 please boost them in or go to our contact page and let me know because i i have 00:06:22.153 --> 00:06:26.293 a feeling if i can find even just a handful of good cameras i think we'll have 00:06:26.293 --> 00:06:27.213 a segment on it pretty soon 00:06:27.633 --> 00:06:30.813 and i'll do like a little frigate coverage on the show and try to convince you 00:06:30.813 --> 00:06:33.273 guys to use it that's i always do. 00:06:36.893 --> 00:06:41.913 Well the arch linux project has been getting hammered for just over two weeks 00:06:41.913 --> 00:06:45.693 i was hoping by the time we went on the air today, I'd have an update saying it's over. 00:06:46.433 --> 00:06:53.133 It is not. The attack is primarily targeted the main website and the AUR and the forums via a DDoS. 00:06:54.313 --> 00:06:56.893 Arch's maintainers has confirmed that the incident is ongoing. 00:06:56.893 --> 00:07:01.133 It is indeed a DDoS attack, and they're trying to collaborate with service providers 00:07:01.133 --> 00:07:02.633 to mitigate it as much as they can. 00:07:03.033 --> 00:07:06.233 However, full restoration has been challenging. There's even issues as of the 00:07:06.233 --> 00:07:07.713 Sunday morning as we're live on the air. 00:07:08.393 --> 00:07:11.393 And this also unfortunately follows kind 00:07:11.393 --> 00:07:17.113 of a rough summer for the aur in general there were some browser packages in 00:07:17.113 --> 00:07:21.353 july that were replaced that had the chaos rat installed in them we've already 00:07:21.353 --> 00:07:25.073 talked the whole you know aur user repository stuff to death so i don't think 00:07:25.073 --> 00:07:28.013 we need to dig into that too much but it's worth saying that it's been a rough 00:07:28.013 --> 00:07:29.693 summer for the aur to begin with. 00:07:29.693 --> 00:07:32.213 I try to use arch by the way. 00:07:32.213 --> 00:07:36.913 Yeah oh is this really unfortunate i mean i don't think it even needs to be 00:07:36.913 --> 00:07:39.853 said, but this is probably about as low as it gets, 00:07:40.093 --> 00:07:45.173 attacking a free software project, non-profit like this, like Arch, 00:07:45.313 --> 00:07:49.133 that's not even associated with any particular commercial company and it's just 00:07:49.133 --> 00:07:50.273 people working hard trying to 00:07:50.273 --> 00:07:53.213 make a distribution that people love and they're trying to run services. 00:07:54.033 --> 00:07:59.473 I think it's without any question that we totally, totally, totally are disappointed 00:07:59.473 --> 00:08:01.053 to hear this. Very frustrated, 00:08:02.642 --> 00:08:06.342 Maybe we could get into what we know about it, but before we get into all of 00:08:06.342 --> 00:08:09.962 that, why don't we just take a moment, step back, and talk about workarounds 00:08:09.962 --> 00:08:13.702 that users of the show could potentially implement right now while Arch is figuring this out. 00:08:13.822 --> 00:08:16.502 And then we'll get into speculation and other stuff. 00:08:16.922 --> 00:08:21.722 Yeah, well, unfortunately, things like the mirror list endpoint used by tools 00:08:21.722 --> 00:08:26.222 like Reflector, that kind of thing, well, that's hosted on archlinux.org. 00:08:26.502 --> 00:08:29.782 So if that's having issues, which it has been, one 00:08:29.782 --> 00:08:32.982 thing you can do is look at the mirrors listed in the pacman dash 00:08:32.982 --> 00:08:35.742 mirror list package so you should probably already 00:08:35.742 --> 00:08:39.122 have that on a normal arch system so go take a peek in there that'll 00:08:39.122 --> 00:08:44.022 at least help you get some options and then the iso is also available on a lot 00:08:44.022 --> 00:08:47.622 of the mirrors they link to some in their news announcement but if you're going 00:08:47.622 --> 00:08:51.762 to do that or download stuff manually do uh make sure you to confirm that it's 00:08:51.762 --> 00:08:55.482 actually signed by the arch trusted keys because you're kind of taking that 00:08:55.482 --> 00:08:57.822 could be taking that into at your own hands. 00:08:58.722 --> 00:09:03.862 I think maybe that's worth underscoring. This is a moment in time where it's 00:09:03.862 --> 00:09:10.282 behoovant on you to be a little extra careful because these are times that attackers can exploit. 00:09:10.562 --> 00:09:13.982 So be sure things are signed. They look legitimate. Take an extra step. 00:09:14.142 --> 00:09:21.442 For the case of the AUR in particular, they maintain a mirror of AUR packages on GitHub. 00:09:21.522 --> 00:09:24.642 It's kind of an interesting setup so if you go there it looks empty but they 00:09:24.642 --> 00:09:31.502 have a branch per package and their announcement has a little tip about a one-off 00:09:31.502 --> 00:09:35.422 git clone command you can do to just check out a particular package that you're interested in. 00:09:35.622 --> 00:09:39.522 But that can be a backup way to get your AUR if you need to, 00:09:39.602 --> 00:09:42.142 which is nice. That's kind of handy, even just regardless. 00:09:42.442 --> 00:09:46.862 I mean, just temporarily, that might be the way to do it. One of the things 00:09:46.862 --> 00:09:52.302 that the ARCH wiki, if you use the AUR properly via the whole guide, 00:09:52.862 --> 00:09:55.022 they start with having you build your own packages. 00:09:55.722 --> 00:09:58.182 It's almost kind of this is the moment where it's like oh that was actually 00:09:58.182 --> 00:10:00.482 worth paying attention to yeah. 00:10:00.482 --> 00:10:03.942 You know those make package skills they pay off sigh. 00:10:06.814 --> 00:10:10.074 I've been watching social media. I've been seeing people talk about this. 00:10:10.254 --> 00:10:12.834 There's been some good coverage, LWN and The Register, I think, 00:10:12.874 --> 00:10:15.414 in particular, and some others had some good coverage. 00:10:15.774 --> 00:10:17.614 Brent, do you have a sense of the impact on the users? 00:10:17.974 --> 00:10:22.814 Well, people are reporting, basically, AUR slowness and occasional, 00:10:22.814 --> 00:10:28.694 like, complete downtime, basically, which clearly will affect installations and updates. 00:10:29.014 --> 00:10:31.754 So, Chris, you can't always update before the show. Sorry. 00:10:32.134 --> 00:10:35.894 You know, if this had happened to the CentOS archives, no one would notice. 00:10:35.894 --> 00:10:39.274 But Arch users, they're doing Pac-Man, SYU, you know, every two seconds. 00:10:39.654 --> 00:10:43.174 Yeah, it's just built into the fingers now. Now, there is, of course, 00:10:43.354 --> 00:10:47.734 some users noting that this has also disrupted OMarchie, you know, 00:10:47.834 --> 00:10:51.314 that DHH Arch initiative that came out recently. 00:10:51.894 --> 00:10:56.954 So the new setups for that have been quite painful. Let's just put it that way. 00:10:57.694 --> 00:11:02.014 And some people have also, of course, complained about problems during fresh 00:11:02.014 --> 00:11:06.314 installs. And DHH actually addressed this on X recently. 00:11:06.814 --> 00:11:10.494 His Omarchi 2.0 release might have to wait a little longer. 00:11:10.754 --> 00:11:14.474 The AUR denial of service attack has picked back up. 00:11:14.614 --> 00:11:18.754 But the upside is that we're building in all sorts of resilience for the installer 00:11:18.754 --> 00:11:21.574 to deal with this style of assault. 00:11:22.274 --> 00:11:26.314 And meanwhile, we'll build a complete Omarchi package mirror for all. 00:11:26.774 --> 00:11:28.514 Oh, that's a big thing there. 00:11:28.514 --> 00:11:32.634 I think this is notable that, first of all, they're releasing it as its own 00:11:32.634 --> 00:11:37.814 standalone ISO now, but also that this big moment had to be delayed by this 00:11:37.814 --> 00:11:40.474 DDoS attack. That really stings. 00:11:41.194 --> 00:11:46.674 It continues here. We're pulling the AUR out of the Omarchi install hotpath. 00:11:46.674 --> 00:11:50.634 It's an incredible resource, but we actually only need a handful of packages 00:11:50.634 --> 00:11:54.074 for the initial setup, and we can just host those ourselves. 00:11:54.074 --> 00:11:58.694 So the AOR really needs a new mirror strategy to avoid this type of predicament. 00:11:59.454 --> 00:12:03.434 Interesting. Kind of unfortunate that they have to do that, but probably a pretty 00:12:03.434 --> 00:12:06.554 good solution. There has been some spec- Well. 00:12:06.554 --> 00:12:10.334 It's at least resources, right, that I guess DHH can offer to a community project, 00:12:10.454 --> 00:12:12.034 or at least to offload from, anyway. 00:12:12.174 --> 00:12:18.354 Yeah, I mean, Shaw, I have never seen anything in the Linux desktop space see 00:12:18.354 --> 00:12:19.594 this kind of continued momentum. 00:12:19.594 --> 00:12:24.754 Him we could have a segment on every week of the show of people that you know 00:12:24.754 --> 00:12:28.154 dozens of people that are switching it's really impressive so i suppose moving 00:12:28.154 --> 00:12:31.614 that off of the aur will probably reduce some of the strain you. 00:12:31.614 --> 00:12:35.754 Know steam is based on arch these days and it gets me wondering if they're having 00:12:35.754 --> 00:12:39.754 issues if anyone's having issues with their steam decks maybe there's a different 00:12:39.754 --> 00:12:42.114 strategy there do you guys have any thoughts on that. 00:12:42.114 --> 00:12:46.034 They don't really take advantage of the aur unless the user drops down to desktop 00:12:46.034 --> 00:12:49.774 mode and kind of gets that going so i suppose it really only impact them up 00:12:49.774 --> 00:12:52.694 at Valve where they're building it, you know, if they're pulling things in from 00:12:52.694 --> 00:12:55.954 the AUR, which isn't good. I mean, that's not great either. It's... 00:12:56.960 --> 00:13:02.080 It's hard to understand why anyone would do this. I saw some people speculating that it's Oma Archie, 00:13:02.800 --> 00:13:07.880 that Oma Archie has put so much traffic with the new users, but the Arch developers 00:13:07.880 --> 00:13:12.680 have kind of distilled or dispelled that myth. So, no, we don't think that's what it is. 00:13:12.840 --> 00:13:19.680 In the past, we have seen AUR helper tools that have been broken and unintentionally DDoS the AUR. 00:13:19.980 --> 00:13:24.120 I suppose that could always be possible. It may be particularly hard to track 00:13:24.120 --> 00:13:28.500 down. One of the issues is that multiple aspects of the Arch infrastructure 00:13:28.500 --> 00:13:33.900 have been attacked, and the tools that they use to manage the Arch infrastructure are hosted where? 00:13:34.280 --> 00:13:35.700 The Arch infrastructure. 00:13:35.740 --> 00:13:41.600 You got it, Wes. So they're unable to access some of their own tooling to solve and mitigate this. 00:13:41.820 --> 00:13:45.320 Yeah, so far they've only said, we are keeping technical details about the attack, 00:13:45.320 --> 00:13:49.760 its origin, and our mitigation tactics internal while the attack is still ongoing. 00:13:49.760 --> 00:13:52.820 So maybe when it finally ends, we'll get some more details. 00:13:52.820 --> 00:13:58.020 Yeah, as we're recording on August 24th, there has been no specific group that 00:13:58.020 --> 00:13:59.740 has come forward and claimed credit. 00:13:59.980 --> 00:14:05.520 And there's been nobody that's sort of been trying to tie it to any particular people or motive. 00:14:05.900 --> 00:14:10.020 But the fact remains that we're going on now two weeks of either some kind of 00:14:10.020 --> 00:14:11.960 intentional attack or misconfiguration. 00:14:14.080 --> 00:14:19.920 And I hope it's in a way just a misconfiguration because I'd be really disappointed 00:14:19.920 --> 00:14:22.580 to learn that people out there would be attacking Arch. 00:14:22.680 --> 00:14:26.680 And Arch has responded by putting up a status.archlinux.org page, 00:14:26.880 --> 00:14:29.800 which you can check and see how services are doing. 00:14:31.200 --> 00:14:34.840 Some systems are down right now. The website is down right now as we record. 00:14:35.160 --> 00:14:39.320 The AUR looks like it's at about an 83% reliability today. 00:14:40.200 --> 00:14:42.820 Not great. It was at 78% earlier. 00:14:43.300 --> 00:14:46.500 And wiki is doing pretty good though. So yeah. 00:14:46.600 --> 00:14:48.920 And the forum is doing better today. The forum was also, it's interesting that 00:14:48.920 --> 00:14:51.040 it's different aspects of the infrastructure at different times. 00:14:52.713 --> 00:14:56.513 Which kind of suggests targeted attacking to me. Again, these are just things 00:14:56.513 --> 00:14:57.113 that are being speculated. 00:14:57.213 --> 00:15:02.393 Some people have also speculated that it's somehow because of this malware that 00:15:02.393 --> 00:15:03.653 we've talked about on the AUR. 00:15:03.853 --> 00:15:08.413 And that people are trying to disable the AUR or something because of it. 00:15:09.273 --> 00:15:12.113 But I think actually, isn't there just even a more recent malware incident? 00:15:12.293 --> 00:15:13.993 Didn't somebody just slip something in again? 00:15:14.533 --> 00:15:20.373 Well, yeah, there was the one, it was like a malicious package named Google Chrome Stable. 00:15:20.553 --> 00:15:21.693 Oh yeah, it was Firefox and then Google, right. 00:15:21.693 --> 00:15:24.253 Yeah, so the browsers have been a big thing of attack here. 00:15:24.253 --> 00:15:29.873 And they're putting in remote access Trojans. And the Google one is the google-chrome-stable. 00:15:30.053 --> 00:15:34.093 Yeah, it looks like a legit name, but by a brand new account. 00:15:34.753 --> 00:15:40.613 And then Chrome does actually start, but it runs a little Python program first. 00:15:40.613 --> 00:15:43.233 And then that turns out to be a remote access Trojan. 00:15:43.373 --> 00:15:47.573 It can install other malware, spy on users, tries to connect to its command 00:15:47.573 --> 00:15:51.953 and control stuff. It's no good. I mean, the AUR maintainers did remove it pretty quickly. 00:15:52.073 --> 00:15:52.173 Yeah. 00:15:52.533 --> 00:15:57.333 It did apparently still get a few upvotes, though, so some folks might have installed it. 00:15:57.533 --> 00:16:00.633 I mean, Brian, this is what we talk about, right? People do need to be aware 00:16:00.633 --> 00:16:03.913 of this, perhaps more so than ever right now as Arch gets more popular. 00:16:04.093 --> 00:16:06.093 Good time to have those ButterFS snapshots. 00:16:06.333 --> 00:16:11.913 I mean, it's really one of the main criticisms of the AUR forever is that anyone 00:16:11.913 --> 00:16:17.493 can just upload a package, and there's not lots of vetting going on. 00:16:17.493 --> 00:16:20.673 So even though it's widely used there's 00:16:20.673 --> 00:16:23.593 no vetting and the trust is maybe let's 00:16:23.593 --> 00:16:26.853 say a little questionable so they specifically 00:16:26.853 --> 00:16:29.833 say you know arch devs are not responsible for aur 00:16:29.833 --> 00:16:36.213 content 100 community maintained and unsupported by the core arch team so that's 00:16:36.213 --> 00:16:40.553 super important to keep in mind that said i mean we've all loved the aur for 00:16:40.553 --> 00:16:45.833 years and years and it's super useful chris it kind of saved you recently so 00:16:45.833 --> 00:16:47.833 it's popular but you know you're taking some chances. 00:16:49.463 --> 00:16:54.983 Maybe now, I think, you know, this is maybe a theory that I'm just roughing, 00:16:55.423 --> 00:16:57.303 roughly trying out right now in the air. 00:16:58.323 --> 00:17:00.983 Arch has gotten a lot of attention from a few vectors recently. 00:17:03.443 --> 00:17:06.683 YouTube, CacheOS, and Omarchi. 00:17:08.303 --> 00:17:12.443 And because of these, I would say these three things, it has drawn different 00:17:12.443 --> 00:17:17.063 user bases to Arch, and it's giving Arch a lot of attention. 00:17:17.283 --> 00:17:20.643 And so there's two thoughts I have with that. One, kind of coincidental, 00:17:20.863 --> 00:17:24.063 the timing of this and its peak popularity right now. 00:17:24.443 --> 00:17:26.763 Number two, what a damn shame. 00:17:27.303 --> 00:17:32.983 You know, like, Arch has been building something incredible for many, many years. 00:17:34.143 --> 00:17:38.623 And it's getting the recognition it deserves after so many years of being the butt of a joke. 00:17:38.783 --> 00:17:42.743 It's getting the recognition, the attention, and the adoption it rightly deserves. 00:17:43.203 --> 00:17:45.763 And then some jackass goes and does something like this. 00:17:46.403 --> 00:17:51.343 And knocks them down and shakes people's faith and trust in the platform and 00:17:51.343 --> 00:17:56.483 forces folks like DHH to rebuild their products to avoid using core Arch infrastructure. 00:17:56.983 --> 00:18:00.843 I don't know. So right now, here's what we do know is we're now into the second week. 00:18:01.383 --> 00:18:04.503 They have partial mitigations in place. Some GitHub mirrors are up. 00:18:05.203 --> 00:18:10.283 I think Cloudflare has offered to help, but acceptance seems like the group 00:18:10.283 --> 00:18:13.403 over at Arch isn't totally down to clown. The Cloudflare's like, 00:18:13.443 --> 00:18:14.423 yeah, we'll help you with this. 00:18:14.923 --> 00:18:17.583 And DHH has been very much like, you should take their help on this. 00:18:17.683 --> 00:18:21.363 And they're very much like, we don't know how we feel about Cloudflare. 00:18:21.683 --> 00:18:23.203 So that's where that's at right now. 00:18:24.363 --> 00:18:27.763 There are some tools where you could roll your own AUR. So while it's up, 00:18:27.903 --> 00:18:29.603 like you could mirror the packages you need. 00:18:29.903 --> 00:18:34.283 We were looking at a couple of them. One of them, we'll have both these linked in the show notes. 00:18:34.423 --> 00:18:39.323 But AUR Publish is one of them. It seems pretty straightforward. 00:18:40.243 --> 00:18:44.203 And you can export things from the AUR and then build them locally and host them. 00:18:45.480 --> 00:18:49.740 And Salvador is a similar tool. It's a little older. It's a Bash script that'll 00:18:49.740 --> 00:18:54.260 help you maintain your own AUR packages and has some neat features in there. 00:18:54.440 --> 00:18:58.000 You can also, it looks like, just self-host maybe even the AUR web, 00:18:58.120 --> 00:19:01.240 like the same software running the main one. 00:19:01.640 --> 00:19:05.680 Oh, yeah, that would make sense. Yeah, it's on GitHub. So wouldn't that be funny? 00:19:05.780 --> 00:19:08.440 And then, like, replace the logo with, like, some sort of crappy, 00:19:08.480 --> 00:19:11.240 like, your own logo kind of paint shop together. 00:19:12.100 --> 00:19:16.600 You know, if you run a decent amount of Arch machines, maybe it's worth considering 00:19:16.600 --> 00:19:17.700 some of these tools anyways. 00:19:18.280 --> 00:19:21.480 One of the ways we could help the project out is just by taking some of the load off. 00:19:22.120 --> 00:19:25.240 If you got more than a handful of Arch systems, maybe you should just mirror 00:19:25.240 --> 00:19:26.760 the packages you use most frequently. 00:19:27.420 --> 00:19:32.240 And some of these tools support fetching the latest updates and then, 00:19:32.240 --> 00:19:35.320 you know, caching them locally for you. And then you update your systems from that. 00:19:36.300 --> 00:19:37.880 I don't know, it seems like it could be a good way to do it. 00:19:38.160 --> 00:19:40.440 Get it going, Wes. We got an Arch box. 00:19:40.440 --> 00:19:43.420 We do we should do this therefore we need our own repo, 00:19:46.700 --> 00:19:47.740 1password.com. 00:19:47.740 --> 00:19:52.720 Slash unplugged that's the number 1password.com slash unplugged all lowercase 00:19:52.720 --> 00:19:57.020 go take the first steps to better security for your team by securing credentials 00:19:57.020 --> 00:20:02.600 and protecting every application even your shadow unmanaged IT which I used to be, 00:20:03.180 --> 00:20:06.860 and I can speak to how tricky that is so that's why you want to go to 1password.com, 00:20:07.680 --> 00:20:12.160 slash unplugged if you're in IT If you're in security, you know the mountain 00:20:12.160 --> 00:20:13.680 of assets you have to protect these days. 00:20:13.900 --> 00:20:17.400 It's not just devices and, of course, identities, which are critical. 00:20:18.220 --> 00:20:21.700 It's applications, too. And there's more and more applications all the time, 00:20:21.720 --> 00:20:24.360 and it's creating just a mountain of security risks. 00:20:25.447 --> 00:20:27.887 But you really can't afford to just have that mountain around. 00:20:28.107 --> 00:20:32.947 It may become a volcano one day. That's where 1Password Extended Access Management comes in. 00:20:33.187 --> 00:20:37.127 And you're not alone. A lot of IT pros out there say this is one of their biggest challenges. 00:20:37.627 --> 00:20:42.147 And Trelica, by 1Password, will discover the applications, even the ones you 00:20:42.147 --> 00:20:46.027 didn't know about, managed or unmanaged, and help you inventory all of them. 00:20:46.507 --> 00:20:52.207 Understand your spend. Understand where there's redundancy and too much use. And manage shadow IT. 00:20:52.767 --> 00:20:56.347 Stuff that you didn't even know your users were using that's on your network. 00:20:56.547 --> 00:21:00.367 And the other thing that I think is really lovely is there's a process to securely 00:21:00.367 --> 00:21:04.907 onboard and off-board employees. So you can meet those compliance goals with 00:21:04.907 --> 00:21:06.447 an actual system and process. 00:21:06.747 --> 00:21:11.027 That's where Trellica by 1Password provides a complete solution for SaaS access and governance. 00:21:11.227 --> 00:21:14.387 It's just one of the ways that extended access management helps teams strengthen 00:21:14.387 --> 00:21:15.887 compliance and security. 00:21:16.367 --> 00:21:19.887 You're probably familiar with 1Password's award-winning password manager that's 00:21:19.887 --> 00:21:21.787 just trusted by millions of users and businesses. 00:21:22.367 --> 00:21:26.747 IBM, Slack, many others have used 1Password to secure their passwords. 00:21:26.927 --> 00:21:31.767 But now it's more than just securing passwords, isn't it? And that's where 1Password 00:21:31.767 --> 00:21:34.347 Extended Access Management comes in. 00:21:34.867 --> 00:21:38.287 They're really great. And, you know, they undergo third-party audits on the regular. 00:21:38.447 --> 00:21:41.827 They have one of the industry's largest bug bounties. 00:21:41.867 --> 00:21:45.367 And they try to exceed the standards set by various authorities when it comes 00:21:45.367 --> 00:21:46.767 to, like, encryption standards and whatnot. 00:21:46.767 --> 00:21:51.767 They really try to be and are the leader in security. So take the first step 00:21:51.767 --> 00:21:56.227 to better security for your team by securing credentials and protecting every 00:21:56.227 --> 00:22:00.227 application, even the unmanned shadow IT stuff. So go learn more. 00:22:00.447 --> 00:22:06.927 You start by going to 1password.com slash unplugged. That's the number 1password.com slash unplugged. 00:22:07.087 --> 00:22:10.627 Go there, check out the information they have, and support the show. 00:22:10.787 --> 00:22:13.267 It really is something I wish I had when I was in IT. 00:22:13.467 --> 00:22:16.207 I think it could have stayed in the game a little longer if I had something 00:22:16.207 --> 00:22:21.087 like this. So go check it out. Support the show. 1Password.com slash unplugged. 00:22:23.448 --> 00:22:28.948 Well, you teased a whole bunch of apps this week, and I've got the feeling one 00:22:28.948 --> 00:22:31.808 of these might just be up my alley. But, Chris, what is it? 00:22:32.308 --> 00:22:34.468 All right, Brantley, let me see if I can sell you on this one. 00:22:34.768 --> 00:22:37.828 I think you're going to like it. I think it would be pretty easy to get going 00:22:37.828 --> 00:22:39.268 on your machine in the van. 00:22:39.848 --> 00:22:44.848 It's called Task Trove. It's pretty new. It's a self-hostable task management 00:22:44.848 --> 00:22:47.828 app that respects your privacy. And I know that's a big one for you. 00:22:48.408 --> 00:22:52.828 And you could think of it as offering a lot of the same features as the commercial, 00:22:52.828 --> 00:22:55.508 like Todoist style and some of the other bigger to-do apps. 00:22:55.728 --> 00:22:57.548 Yeah, it looks a lot like Todoist, really. 00:22:57.688 --> 00:23:01.148 Yeah, right. Well, this is what I was looking for, something to kind of replace 00:23:01.148 --> 00:23:04.388 Todoist. So obviously you can self-host it, zero data tracking. 00:23:04.748 --> 00:23:07.448 They have smart task creation where you can use natural language. 00:23:07.508 --> 00:23:09.548 And I actually do like this when I'm on the phone with somebody, 00:23:10.308 --> 00:23:12.268 you know, call Brent 2 p.m. on Friday. 00:23:13.348 --> 00:23:16.328 And then you can do subtasks with like rich text details 00:23:16.328 --> 00:23:19.648 which is i use subtasks all the time you 00:23:19.648 --> 00:23:22.408 know figure out linux unplugged and then there's 00:23:22.408 --> 00:23:25.068 like 25 subtasks to that right and so it's nice to have all 00:23:25.068 --> 00:23:28.648 that you can have reoccurring tasks set linux unplugged pending on saturday 00:23:28.648 --> 00:23:33.348 and you can have custom patterns in there and it does automatic scheduling it 00:23:33.348 --> 00:23:38.448 also has like a kanban style project organization with colored labels and multiple 00:23:38.448 --> 00:23:42.688 different style views really nice clean design with dark and light themes, 00:23:42.928 --> 00:23:45.708 mobile friendly, but also works on the desktop, keyboard shortcuts. 00:23:46.008 --> 00:23:50.288 Mobile apps are just like a web app that works well for mobile too. 00:23:50.428 --> 00:23:52.408 But are you ready for the big one? 00:23:52.628 --> 00:23:53.268 Is it Rust? 00:23:53.888 --> 00:23:55.088 It's built in Canada. 00:23:55.748 --> 00:23:57.528 Whoa. Okay. 00:23:57.848 --> 00:23:57.988 In Canada. 00:23:58.408 --> 00:23:59.788 You're right. That is in my lane. 00:24:00.828 --> 00:24:04.648 Really nice data storage too. It's file-based, which I always like. 00:24:04.768 --> 00:24:09.408 Just a simple JSON format that's really easy to back up, transfer, move around, restore. 00:24:10.628 --> 00:24:15.668 They are working on a paid hosted version. If you don't want to self-host, not available yet. 00:24:16.128 --> 00:24:19.268 But also, it looks like there will be a way to have your totally private, 00:24:19.488 --> 00:24:20.748 totally self-hosted version. 00:24:21.910 --> 00:24:26.510 But still hook into a couple of the cloud features as well as contribute towards development. 00:24:27.150 --> 00:24:32.250 So I like that there is a path to sustainability there, but it doesn't negate 00:24:32.250 --> 00:24:35.430 you from using it full-functional self-hosted when they do get there. 00:24:35.690 --> 00:24:37.530 They're not there yet, but that's what they're working towards. 00:24:37.590 --> 00:24:39.510 And they're very upfront about that, which I like. 00:24:40.010 --> 00:24:43.510 Really nice app. What do you think, Wes? Have you looked at the GUI and taken a poke at it? 00:24:43.630 --> 00:24:47.810 It does look pretty nice. I will just call out, which is make of it what you 00:24:47.810 --> 00:24:50.810 will. It does kind of have an interesting license situation. 00:24:50.810 --> 00:24:51.810 Oh, yes. Thank you. Yeah. 00:24:51.910 --> 00:24:55.510 Content of branches other than the main branch are not licensed. 00:24:55.850 --> 00:25:00.770 Source code files that contain .pro in their file name or their directory name 00:25:00.770 --> 00:25:03.850 are not licensed under this license. So there's some exceptions. 00:25:04.070 --> 00:25:08.870 And then the whole thing is under a sustainable use license, V1.0. 00:25:09.130 --> 00:25:13.430 You can use or modify the software only for your own internal business purposes 00:25:13.430 --> 00:25:15.550 or for non-commercial or personal use. 00:25:15.690 --> 00:25:20.710 So there's some restrictions from your traditional open source license just to be aware of. 00:25:20.710 --> 00:25:24.350 Because, you know, they're going to kind of try to find a way to monetize some 00:25:24.350 --> 00:25:26.790 of the pro features while still giving you the core functionality. 00:25:26.950 --> 00:25:28.310 And the core functionality is kind of there today. 00:25:29.470 --> 00:25:34.530 But here's my final kind of pitch to you, Brent. Okay. It's a pretty new project. 00:25:35.150 --> 00:25:37.410 And it's under active development. 00:25:38.310 --> 00:25:44.310 And you could get in with your bug field today and engage with the developer 00:25:44.310 --> 00:25:48.610 who is very clear about how you do that. You engage in, essentially, 00:25:48.870 --> 00:25:50.930 the issue process on GitHub and walk through all of that. 00:25:51.490 --> 00:25:54.310 And you could make an impact here. And you could end up with, 00:25:54.310 --> 00:25:59.910 perhaps, your perfect task management application that's finely tuned for Brentley 00:25:59.910 --> 00:26:02.030 and have full control over it. 00:26:02.110 --> 00:26:05.870 Self-hostable, respects your privacy, has a sustainable path. 00:26:06.110 --> 00:26:08.550 The developer is an independent Canadian developer. 00:26:09.310 --> 00:26:12.990 And they're actively looking for input from folks like yourself. 00:26:13.210 --> 00:26:16.830 That sounds perfect. I don't see any downsides. where do I sign up? 00:26:16.910 --> 00:26:20.570 It's called Task Trove you can check out their, they've got a nice website it's 00:26:20.570 --> 00:26:26.190 on GitHub obviously, but you can also go to tasktrove.io and see their fancy 00:26:26.190 --> 00:26:31.130 website and it's just a simple Docker Composer way if you like to go that route, 00:26:31.970 --> 00:26:34.630 or set it up yourself, there's a couple options there they have instructions 00:26:34.630 --> 00:26:40.010 on the GitHub take back control of your productivity is their tagline on their main site, nice site too, 00:26:41.339 --> 00:26:43.619 They've put some real thought into this. That's also what's jumped out at me 00:26:43.619 --> 00:26:46.379 is there's a lot of care and thought into this. 00:26:46.539 --> 00:26:51.259 And it's in a state right now where it's essentially ready to take on something 00:26:51.259 --> 00:26:53.379 like Todoist. And they're just getting started. 00:26:54.059 --> 00:26:58.099 So that's pretty exciting. And it kind of falls in line with taking these types of things. 00:26:58.259 --> 00:27:01.999 These are little signals and bits of data that I used to feed to the cloud and 00:27:01.999 --> 00:27:03.539 moving it to my own self-hosted network. 00:27:03.839 --> 00:27:06.959 And what I really appreciate is it's one of these applications you can just 00:27:06.959 --> 00:27:09.239 run and you don't even really notice it's going. 00:27:09.999 --> 00:27:14.339 You can't really see it in the process viewer. It's just really nice and straightforward. 00:27:14.599 --> 00:27:17.159 And then in the future, there will have more collaborative features. 00:27:17.259 --> 00:27:18.879 I think that'll also be where some of the pro stuff comes in. 00:27:18.959 --> 00:27:20.899 The cloud maybe enables that kind of connectivity. 00:27:21.219 --> 00:27:26.159 So are you going to run it long-term? Does it have enough that you're able to switch? 00:27:26.339 --> 00:27:30.159 The moment I could do collaborative tasks with the wife. Or I'd really love 00:27:30.159 --> 00:27:31.339 something where we could use it too. 00:27:31.419 --> 00:27:31.679 Sure. 00:27:32.979 --> 00:27:37.099 Yeah. I'd even pay a reasonable monthly fee for that. 00:27:37.099 --> 00:27:41.519 It does look like it's ready to go with Docker. They've got a Docker Compose 00:27:41.519 --> 00:27:46.839 or just plain Docker or some manual setup instructions if you're down with PNPM. So that's nice. 00:27:46.939 --> 00:27:50.199 Yeah, you could do it that way. Task Trove, link in the show notes. 00:27:50.479 --> 00:27:51.579 And then here's the next one. 00:27:51.939 --> 00:27:56.639 This one's really more for future, Chris. This is really, I'm trying to pitch to myself. 00:27:57.279 --> 00:27:59.239 Could actually be useful for both of you, though. 00:28:00.370 --> 00:28:03.750 This one's called Shuthost, and it's a little helper that manages the standby 00:28:03.750 --> 00:28:07.090 states of your Linux boxes and supports Wake on LAN. 00:28:07.310 --> 00:28:14.050 And it has a very usable web GUI to manage all of this. And here's where I've needed this. 00:28:15.030 --> 00:28:20.770 I never need this until I'm traveling. And then I need it. And I need it every damn time. 00:28:21.210 --> 00:28:24.190 Like inevitably something in the studio goes to sleep, usually the soundboard 00:28:24.190 --> 00:28:29.210 machine, and I need to wake it up. or my workstation upstairs is asleep because 00:28:29.210 --> 00:28:32.610 I haven't been here for two weeks because I'm traveling and now I need something off of it. 00:28:32.870 --> 00:28:37.270 Or for some reason, this has happened, like some device at home has gone to 00:28:37.270 --> 00:28:39.170 sleep and I need to power it up and use it. 00:28:39.570 --> 00:28:43.950 And so this little helper gives you a web front end where you can have these 00:28:43.950 --> 00:28:46.450 hosts pop it off and it's just ready to go. 00:28:46.870 --> 00:28:50.670 He does disclaim that he did use an LLM to generate. It's not vibe coded, 00:28:50.810 --> 00:28:52.270 but he used an LLM in some of this. 00:28:52.470 --> 00:28:54.070 But you can manage the standby state 00:28:54.070 --> 00:28:59.110 of Unix hosts with Wake on Land or a lightweight agent if you prefer. 00:28:59.330 --> 00:29:03.350 There's a web GUI, which you can install as a progressive web app on your phone. 00:29:03.550 --> 00:29:08.690 It also provides an API so you could integrate Home Assistant pretty easy with 00:29:08.690 --> 00:29:12.170 just like a webhook call or build a quick integration around this, 00:29:12.270 --> 00:29:14.030 which that would really take it to the next level. 00:29:14.270 --> 00:29:17.030 And they also include some convenient scripts to just make it work for you. 00:29:17.350 --> 00:29:22.190 And there's actually a respectable amount of documentation for a project of 00:29:22.190 --> 00:29:23.370 this size. It's not a huge project. 00:29:23.890 --> 00:29:27.610 It's a pretty straightforward thing to set up, but respectable amount of documentation 00:29:27.610 --> 00:29:31.010 and future direction, too. 00:29:31.350 --> 00:29:34.270 Seems to have both the Apache and MIT license. 00:29:34.490 --> 00:29:37.610 Have you had this problem? You know, where everything works great, 00:29:37.850 --> 00:29:40.610 maybe because you're there and you touch things from time to time, 00:29:40.670 --> 00:29:44.330 but then when you leave, like, whatever... I know you don't have a lot of systems 00:29:44.330 --> 00:29:47.350 running at home, but have you had this problem where, like, it's, 00:29:47.410 --> 00:29:48.290 of course, when you're traveling? 00:29:48.570 --> 00:29:52.690 Yes. For sure. Yep. You're out of your rhythm. You didn't realize that something 00:29:52.690 --> 00:29:57.950 somehow has sleep enabled or something weird happened with your power and things 00:29:57.950 --> 00:30:02.230 didn't fully come back online right there can be a lot of situations here's. 00:30:02.230 --> 00:30:03.550 My sales hook for Brent are you ready, 00:30:05.365 --> 00:30:10.605 I actually think something like this would be useful for you in the van scenario. 00:30:11.205 --> 00:30:11.405 Really? 00:30:11.685 --> 00:30:16.025 Yeah, yeah. So again, this is called shut host, S-H-U-T host, link in the show notes. 00:30:16.625 --> 00:30:19.945 You got to have a minimal power draw in that van. 00:30:20.065 --> 00:30:22.365 Like right now, I've been thinking about this. It's parked outside that fancy 00:30:22.365 --> 00:30:24.725 hotel, really class in the joint up. 00:30:24.905 --> 00:30:25.965 No solar panels connected. 00:30:26.145 --> 00:30:30.665 Right. And things are just kind of running, hopefully fine, but you don't really 00:30:30.665 --> 00:30:32.485 have visibility on any of this stuff right now. 00:30:32.485 --> 00:30:35.285 These are really common scenarios especially for a 00:30:35.285 --> 00:30:38.445 guy like yourself and it would 00:30:38.445 --> 00:30:41.425 be nice to have things on standby not consuming power 00:30:41.425 --> 00:30:44.745 but then with a tool like shut host being 00:30:44.745 --> 00:30:47.985 able to fire things up so you have observability you could you 00:30:47.985 --> 00:30:50.785 could turn on a camera system or you could turn on the home 00:30:50.785 --> 00:30:53.825 assistant box you could enable more things remotely to 00:30:53.825 --> 00:30:57.605 like check in on the box and then also use something like this to bring them 00:30:57.605 --> 00:31:02.005 back down when you're done and so you could you know kind of like the mars rover 00:31:02.005 --> 00:31:06.925 you could you know like the nasa people or the jpl folks that are powering things 00:31:06.925 --> 00:31:09.425 up and managing things as they need it then they turn it back down like you 00:31:09.425 --> 00:31:11.785 could do the same thing for the van with a tool like this. 00:31:11.785 --> 00:31:15.585 So like when the valet goes to like try to start the thing i can boot the cameras 00:31:15.585 --> 00:31:20.045 up and then once they give up i can just kind of put them back into a rest state. 00:31:20.045 --> 00:31:23.745 I mean you know i do this not with this tool but you know that's what i do right 00:31:23.745 --> 00:31:27.545 when i take jupes in to the shop that's true when the folks when the folks enter 00:31:27.545 --> 00:31:31.305 the motion sensors detect motion and they activate the cameras and then I can 00:31:31.305 --> 00:31:33.025 peep on the technicians. 00:31:33.945 --> 00:31:37.925 I'm most excited about the API component of it. I mean, Home Assistant are not 00:31:37.925 --> 00:31:40.205 just like for backups, for family backups. 00:31:40.405 --> 00:31:42.945 Like I can definitely see my folks having machines that, you know, 00:31:43.005 --> 00:31:48.565 they just power off and if I can, you know, wake up when they're in bed and suck up that data. 00:31:48.705 --> 00:31:52.625 It also made me wonder, is there like a bit focus workflow for like gear automation? 00:31:52.765 --> 00:31:56.805 Bit focus is such a great tool. If you have a stream deck, you can automate 00:31:56.805 --> 00:31:59.465 so many things to get like a lab ready or a studio ready. 00:31:59.685 --> 00:32:02.745 And so if you could just have a button on here that wakes the studio up, 00:32:03.165 --> 00:32:04.885 so then you don't have to have the machines running all the time. 00:32:04.945 --> 00:32:06.425 You can have them sleeping, conserving power. 00:32:06.745 --> 00:32:09.345 You sit down, you hit one button, as long as the bit focus, Raspberry Pi, 00:32:09.445 --> 00:32:11.905 or whatever is going, boop, boop, boop, studio comes online. 00:32:12.525 --> 00:32:14.785 Which, you know, if you're doing it off-grid or something like that, 00:32:14.865 --> 00:32:18.265 or have a little home lab where you want to try to save as much power as possible, 00:32:18.385 --> 00:32:19.665 it's shut down the systems you don't need. 00:32:20.885 --> 00:32:24.545 These kinds of things are just really nice. And part of it is having also a 00:32:24.545 --> 00:32:27.305 nice little UI to do it, and the other part of it is something that works on 00:32:27.305 --> 00:32:29.745 your mobile and then lastly something that doesn't take 10 years to get going. 00:32:30.505 --> 00:32:36.685 And the config syntax for this is stupid simple. It's server name, port, the IP. 00:32:38.165 --> 00:32:40.985 That's pretty much it. It's two lines. 00:32:41.405 --> 00:32:43.865 I don't know if you noticed, but it is written in Rust. 00:32:44.105 --> 00:32:49.325 Oh, I did not notice. That did not influence the pick. How about that? 00:32:52.976 --> 00:32:58.016 That's true, PJ. You've got a solution for this already that doesn't require any Docker, does it? 00:32:58.076 --> 00:33:01.796 Let's go use the ESPN and relay. Still need home assistant running, though. 00:33:02.196 --> 00:33:06.416 I'm going to have that. Yeah. Well, you know, to be honest, one of the ways 00:33:06.416 --> 00:33:12.236 I do solve this today, because I did not have this tool, is I just plug my PCs 00:33:12.236 --> 00:33:13.776 and my monitors into smart plugs. 00:33:15.016 --> 00:33:20.636 And the PCs and the BIOS are set to power on when the power is restored, just boot up. 00:33:21.776 --> 00:33:27.816 And that's how i solve this and it's great too because the other night dylan 00:33:27.816 --> 00:33:31.016 was playing video games too late and i use the intercom and i tell him hey you 00:33:31.016 --> 00:33:32.696 got to wrap up and then like you know, 00:33:33.176 --> 00:33:35.916 30 minutes go by and he hasn't wrapped up and hey you got five 00:33:35.916 --> 00:33:38.736 minutes you need to get off the computer five minutes go by he's not off the computer so 00:33:38.736 --> 00:33:43.296 i just bring up homo system boop kill the power he's still 00:33:43.296 --> 00:33:46.036 sore about that one this is like a week ago and 00:33:46.036 --> 00:33:48.676 he's still bringing it up but it's really nice to have that kind 00:33:48.676 --> 00:33:51.316 of control over your individual systems and one of 00:33:51.316 --> 00:33:53.956 the other ways i use this and you could absolutely especially like you 00:33:53.956 --> 00:33:56.856 said with this api and you could do this without smart plugs 00:33:56.856 --> 00:33:59.736 and brent's unfortunately experienced the downside of 00:33:59.736 --> 00:34:02.776 some of these automations that always work well but when i 00:34:02.776 --> 00:34:07.636 arrive at the studio uh the smart plug activates in my office and turns on the 00:34:07.636 --> 00:34:12.376 monitors in my office and if the computer if my workstation isn't on turns it 00:34:12.376 --> 00:34:17.196 on because it it takes an obnoxiously long time to post so by the time i get 00:34:17.196 --> 00:34:22.256 up there everything's going and it doesn't have to be running 24 7 to accomplish that. 00:34:23.876 --> 00:34:26.576 Unfortunately i didn't really build that automation with other people in mind, 00:34:27.336 --> 00:34:32.276 which brent brent sometimes experiences when he stays at the studio yes. 00:34:32.276 --> 00:34:36.296 I always know when you arrive at the studio though so that's a benefit. 00:34:36.296 --> 00:34:39.036 That's true yeah i guess it gives you a warning that I'm here, 00:34:39.136 --> 00:34:40.756 right? So you can chase the girls out. 00:34:41.116 --> 00:34:43.176 I always know when you leave too because all the lights go out. 00:34:46.696 --> 00:34:50.316 Sorry about that. I swear, one of these days, I'm going to fix that. 00:34:53.301 --> 00:35:00.101 Unraid.net slash unplugged. Go unleash your hardware, and we are in the final countdown. 00:35:01.681 --> 00:35:05.921 It is the final days of the 20 days of Unraid summer. Can you believe it? 00:35:06.521 --> 00:35:11.141 Summer has gone by, and 20 years of Unraid has come very, very quickly. 00:35:11.321 --> 00:35:14.421 But you're not too late. You can still save 20% off licenses, 00:35:14.661 --> 00:35:18.521 upgrades, exclusive new Unraid merch until August 26. 00:35:19.341 --> 00:35:23.401 That's your deadline. So there's just enough time to go grab a deal and enter 00:35:23.401 --> 00:35:26.721 the Show Your System competition so you can win prizes during their live stream 00:35:26.721 --> 00:35:28.421 that's coming up on August 30th. 00:35:28.541 --> 00:35:30.661 They're going to have their founder there. They're going to have special guests. 00:35:30.781 --> 00:35:33.221 There's going to be hardware giveaways. There's going to be other giveaways as well. 00:35:33.541 --> 00:35:35.541 And they're going to celebrate 20 years of Unraid. 00:35:36.081 --> 00:35:40.141 So go learn more by going to our URL while you support the show, 00:35:40.701 --> 00:35:42.881 unraid.net slash unplugged. 00:35:42.961 --> 00:35:45.181 Can you believe it? 20 years of Unraid. 00:35:45.601 --> 00:35:49.581 Unraid gives you the ability to take what you have today the different size 00:35:49.581 --> 00:35:54.701 drives you have in your closet, take the hardware you have right now and build 00:35:54.701 --> 00:35:57.721 something that lets you run the stuff we talk about in every show. 00:35:58.361 --> 00:36:01.301 You know, it's like one of these things where if you've got a few hours on a 00:36:01.301 --> 00:36:03.161 Saturday, you can actually get up and running. 00:36:03.881 --> 00:36:06.961 Unraid really does let you unleash your hardware and they're always running 00:36:06.961 --> 00:36:08.541 on top of a modern Linux stack. 00:36:08.821 --> 00:36:11.941 It's one of the things I like about Unraid is they have a legitimate monetization 00:36:11.941 --> 00:36:16.261 strategy that means they can continue to develop and support your system for the long haul. 00:36:16.361 --> 00:36:19.281 I mean, here they are at 20 years And it honestly feels like the energy they 00:36:19.281 --> 00:36:23.361 got They're just getting going It's incredible So check it out, 00:36:23.461 --> 00:36:30.241 that special deal goes until just August 26 The final 20 days Of summer for Unraid Are almost here. 00:36:31.001 --> 00:36:37.541 To celebrate 20 years of Unraid Go to unraid.net slash unplugged Don't miss the big bash on the 30th, 00:36:38.101 --> 00:36:40.901 Giveaways, I have a feeling too If you tell them you're from Linux Unplugged 00:36:40.901 --> 00:36:44.141 You might get a little special treatment A little special attention You know, 00:36:44.201 --> 00:36:48.921 they love you guys Alright, one last time Unraid.net slash unplugged. 00:36:51.902 --> 00:36:56.002 Well, we've had another great week and want to say a huge thank you to the new members. 00:36:56.222 --> 00:37:02.202 That's Justin N., Caden, Nathan R., Wesley J.P., Jonathan G., and Adam T. 00:37:02.302 --> 00:37:08.722 And we have exactly one redemption left for our very special bootleg promo code. 00:37:08.922 --> 00:37:11.242 Chris, what's this all about? There's only one? 00:37:11.582 --> 00:37:17.602 Only one left. Take 15% off every single month forever. Thank you to our new members. 00:37:19.002 --> 00:37:21.722 Thank you for supporting the show, putting that support on autopilot. 00:37:22.222 --> 00:37:26.802 And keeping us going. It's a great feeling to see those come in and see that support like that. 00:37:27.422 --> 00:37:33.902 Now, we also got some emails into the show, and I got various versions of this all week long. 00:37:33.902 --> 00:37:37.882 So I wanted to put this in here because I thought BHH32 had a very articulate 00:37:37.882 --> 00:37:43.142 version of this response, and this is in regards to our BcacheFS coverage and 00:37:43.142 --> 00:37:45.282 its exclusion so far from the Linux kernel. 00:37:45.462 --> 00:37:47.802 We talked about this last week, and I was pretty disappointed. 00:37:48.282 --> 00:37:52.542 And I made the point that I felt like the kernel developers were losing touch 00:37:52.542 --> 00:37:55.962 with the users on the ground and that it was now becoming feels over features. 00:37:57.262 --> 00:38:00.562 Well, BHH writes that, Chris, I don't agree with your sentiment on BcacheFS. 00:38:01.222 --> 00:38:05.482 I think it comes down to Kent's inability to adhere to kernel development policies, 00:38:05.482 --> 00:38:09.262 his attitude and sneakiness trying to sneak in new features during a feature 00:38:09.262 --> 00:38:11.262 freeze when only bug fixes are allowed. 00:38:11.582 --> 00:38:14.902 Now he's dogging on other file system developers. 00:38:15.342 --> 00:38:19.522 In any industry job, he'd have been fired a while ago. I don't think Linus is 00:38:19.522 --> 00:38:21.382 in the wrong, no matter the technical loss. 00:38:21.682 --> 00:38:25.442 If he were to remove Bcash from the kernel, well, it's just not fair to the 00:38:25.442 --> 00:38:29.082 project and other developers to have to continue to deal with issues from someone 00:38:29.082 --> 00:38:32.602 that can't follow the rules after being warned many times already. 00:38:33.782 --> 00:38:36.962 And I think this is... There's a lot of things in here I actually kind of agree 00:38:36.962 --> 00:38:39.102 with in the sense that, hey, if they don't want to work with somebody, 00:38:39.162 --> 00:38:40.062 they don't have to work with somebody. 00:38:40.882 --> 00:38:45.562 But one of the sentiments that I saw over and over again this week was. 00:38:47.270 --> 00:38:51.150 Hey man, Kent tried to squeeze a new feature in during an RC freeze, 00:38:51.210 --> 00:38:54.250 and everybody knows the golden rule, only fixes, no features. 00:38:55.010 --> 00:38:58.030 And then when he got caught, he got pissy about it, and it's on him. 00:38:58.170 --> 00:39:01.570 He shouldn't have tried to squeeze these features in. He was not following the 00:39:01.570 --> 00:39:04.410 release process, or he was being 00:39:04.410 --> 00:39:08.470 sneaky, or he doesn't know how the kernel works is also one that I got. 00:39:08.570 --> 00:39:11.150 Because I think people don't know Kent's been around longer than BcashFS. 00:39:12.470 --> 00:39:17.570 And my position, and I think probably Wes and Brent agree, but I'll let you guys speak to this. 00:39:17.850 --> 00:39:21.670 My position is quite simply, there's nuance to this problem. 00:39:22.230 --> 00:39:26.910 I did a little research, and over the years, I kind of went back to Linux kernel 00:39:26.910 --> 00:39:30.550 3 something, so it was during the development phase all the way forward. 00:39:32.270 --> 00:39:38.770 And I, you know, I mean probably over a dozen examples of gray line issues of 00:39:38.770 --> 00:39:41.890 feature slash fix, because often a fix is a feature and a feature is a fix. 00:39:42.470 --> 00:39:48.210 I saw multiple, I saw three examples for ButterFS, totally fine, 00:39:48.670 --> 00:39:49.810 fixes during the RC window. 00:39:50.090 --> 00:39:54.630 I saw examples for the sound subsystem. I saw examples for the sound blaster drivers. 00:39:54.870 --> 00:40:01.570 I saw examples for the sleep and suspend subsystems. I saw examples for video 00:40:01.570 --> 00:40:07.710 things, all kinds of examples of fix slash features getting added during the RC window. 00:40:07.710 --> 00:40:12.670 And so I think Kent's position has always been that what I was contributing 00:40:12.670 --> 00:40:15.910 was more akin to a fix than a feature. 00:40:16.050 --> 00:40:20.690 And I have users in production that need this fix and the RC periods for fixes. 00:40:21.270 --> 00:40:26.110 And Linus's position was, I disagree. It is a feature ad. It's not a fix. 00:40:26.650 --> 00:40:29.470 And therefore, it's not allowed. And I'm totally fine with that. 00:40:29.550 --> 00:40:31.270 That's Linus's call. It's his kernel. 00:40:31.690 --> 00:40:34.450 And, you know, how Kent responds to that is his responsibility. 00:40:34.770 --> 00:40:37.470 But I actually think there's importance to understand here. It's not like he 00:40:37.470 --> 00:40:41.790 was trying to add some new feature to BcacheFS that was just absurd. 00:40:42.030 --> 00:40:43.930 In Kent's opinion, he was trying to do a fix. 00:40:44.590 --> 00:40:48.190 Fixes are allowed in the Linux kernel during the RC process. 00:40:48.550 --> 00:40:53.730 And maybe it's more of people hear the story, but they don't look into the issue. 00:40:53.910 --> 00:40:55.550 And this is where I'm going to turn to you, Wes. 00:40:55.750 --> 00:41:01.290 In my opinion, what Kent was doing was more akin to fixing log issues than it 00:41:01.290 --> 00:41:02.630 was a new feature of BcacheFS. 00:41:02.630 --> 00:41:06.890 This time we're just talking about a 70 line patch that just picks overwrites 00:41:06.890 --> 00:41:10.250 instead of updates from the journal and sorts them in reverse order is how he 00:41:10.250 --> 00:41:15.590 built it at one point in terms of the kind of code for journal replay stuff he was trying to add this. 00:41:15.590 --> 00:41:19.530 Was to help people in production that were trying to be cache fs out on their systems, 00:41:21.103 --> 00:41:23.723 And so they, in theory, were writing the latest kernels to get these things. 00:41:24.663 --> 00:41:27.303 And so is it a new feature or is it a fix? 00:41:28.043 --> 00:41:32.183 But where I see a lot of people short-circuit on this issue is, 00:41:32.323 --> 00:41:35.063 well, he wasn't following the best practices of kernel development. 00:41:35.063 --> 00:41:36.883 He was trying to ram features in during an RC. 00:41:38.123 --> 00:41:42.603 I don't agree with that assessment. I think that's kind of a lightweight take. 00:41:42.603 --> 00:41:45.583 If you look into it, I think there's nuance here. 00:41:46.303 --> 00:41:49.503 But there, Linus can make his call and how Kent responds to that's on Kent. 00:41:49.503 --> 00:41:53.483 But do you agree there's nuance this is you could call it a feature but you could also call it a fix. 00:41:53.483 --> 00:41:56.223 Yeah and i mean as with all rules right you have 00:41:56.223 --> 00:41:59.203 to kind of understand what what they're there what they're trying to prevent is there you 00:41:59.203 --> 00:42:02.323 know uh what is the real risk that this 00:42:02.323 --> 00:42:05.003 if added can break other parts of 00:42:05.003 --> 00:42:08.303 the kernel or other users outside of the bcash fs you know there's all kinds 00:42:08.303 --> 00:42:11.063 of things that ultimately get considered into like what actually really gets 00:42:11.063 --> 00:42:16.423 stamped into the kernel or not i think it is totally true that kent failed to 00:42:16.423 --> 00:42:21.703 gain the trust of the kernel community to be able to have leeway to successfully 00:42:21.703 --> 00:42:23.863 get these kinds of things pushed upstream. 00:42:25.323 --> 00:42:29.083 We're all dealing with the results of that. But I do think you're right in most 00:42:29.083 --> 00:42:32.943 or at least many development communities there are rules and then sometimes 00:42:32.943 --> 00:42:36.323 there are exceptions and there's classifications and not all things fall into 00:42:36.323 --> 00:42:39.263 clear cut categories and judgment calls get made and that's where the social 00:42:39.263 --> 00:42:40.683 dynamics really do become important. 00:42:41.983 --> 00:42:46.923 I don't think it's fair though to write Kent off because of that one debate 00:42:46.923 --> 00:42:48.043 if it was a feature or not. 00:42:48.423 --> 00:42:53.583 And that's where I see a lot of people maybe failing to intellectually follow 00:42:53.583 --> 00:42:56.663 this all the way through and just kind of using it as a shortcut to just write 00:42:56.663 --> 00:43:02.063 Kent off, who has been a longtime contributor outside of just BcacheFS and knows what he's doing. 00:43:03.583 --> 00:43:07.523 But I do agree that if Linus doesn't want it, that's all that really matters. 00:43:08.323 --> 00:43:10.223 I think it's a shame and it's a loss. 00:43:11.903 --> 00:43:16.063 And it's my opinion that the kernel developers have probably never really been 00:43:16.063 --> 00:43:19.663 big file system guys that just don't think it's a thing they really care or 00:43:19.663 --> 00:43:22.323 think a lot about. It's not a problem they really have to solve a lot. 00:43:23.163 --> 00:43:26.783 And like Wes said, there isn't a social relationship there to kind of allow 00:43:26.783 --> 00:43:29.843 for this stuff where some of these developers that have squeezed things in under 00:43:29.843 --> 00:43:34.203 the wire, not only have they been long-time contributors to a Linux kernel, 00:43:34.363 --> 00:43:37.243 but their employer probably financially contributes to the Linux Foundation too. 00:43:37.323 --> 00:43:41.023 So there's a trust there and a relationship there for better or for worse. 00:43:41.443 --> 00:43:44.403 But thank you, BHH, and everybody who did push back. I did want to hear from 00:43:44.403 --> 00:43:47.483 you and I really appreciate the conversation. And if you disagree, keep it going. 00:43:47.483 --> 00:43:54.723 Oh hey we've got next in the old mailbag a note from our pal olympia mike with 00:43:54.723 --> 00:43:57.563 a nick's book update oh good. 00:43:57.563 --> 00:43:58.603 I've been wanting one of these. 00:43:59.598 --> 00:44:04.258 Hey, gents, it's been a long and busy summer here, finally catching up with the back catalog. Nice. 00:44:04.678 --> 00:44:09.038 I wanted to give you an update on my next book project and the computer upcycling I've been doing. 00:44:09.298 --> 00:44:15.238 I've definitely passed 1,000 computers donated to regular folks out there, 00:44:15.258 --> 00:44:17.138 and the feedback is awesome. 00:44:17.478 --> 00:44:20.718 People are loving it. That's just, congrats. 00:44:20.818 --> 00:44:21.598 Huge. That's huge. 00:44:22.418 --> 00:44:24.658 Regular people loving Linux. 00:44:24.938 --> 00:44:25.358 Yeah, I love that. 00:44:25.358 --> 00:44:29.098 It's been so successful that the local library system hosted me for a talk and 00:44:29.098 --> 00:44:32.318 a workshop all about it and interviewed me for their blog. 00:44:32.938 --> 00:44:35.758 It's really awesome to see this thing being talked about openly. 00:44:36.118 --> 00:44:41.578 Yeah, I'd love to. The seemingly wider and wider interest in the upcycling of 00:44:41.578 --> 00:44:42.578 machines are perfectly good. 00:44:43.278 --> 00:44:48.738 Mike gave us some Nixbooks, and it's my only laptop, my only x86 laptop. I have a MBP1. 00:44:49.598 --> 00:44:53.938 But it's been great. I'm using the hell out of this thing that somebody was going to throw away. 00:44:53.938 --> 00:44:58.038 It sounds like we should probably check out what Mike's doing here because Nixbook 00:44:58.038 --> 00:45:01.318 itself now has a standalone GUI installer. 00:45:01.898 --> 00:45:05.898 Now you can literally grab an ISO, burn it to a USB drive, and convert any computer 00:45:05.898 --> 00:45:08.118 into an easy-to-use Nixbook in minutes. 00:45:08.618 --> 00:45:10.238 Yeah, maybe we could ape that for Hypervibe. 00:45:10.298 --> 00:45:13.378 Uh-huh. Kind of going on the reverse end of the spectrum there, but same deck. 00:45:13.618 --> 00:45:15.818 Hypervibe's a bit of a different direction than the Nixbook. 00:45:16.778 --> 00:45:20.158 Thank you, Mike. Thank you for that update. It's always really nice to hear that. 00:45:20.218 --> 00:45:20.958 Keep up the great work. 00:45:21.118 --> 00:45:24.678 Mm-hmm. We'll put a link to his next book project in the show notes. 00:45:25.198 --> 00:45:28.918 Well, we have another little piece of mail here. Jesus, this thing's full. 00:45:29.118 --> 00:45:34.038 This one from Nemo, who sent this one in via the Matrix chat. 00:45:34.358 --> 00:45:38.478 I just wanted to shout out that Crush was a great pick the other day. 00:45:38.618 --> 00:45:44.578 I gave it a few small scripts I wrote for work recently and passed it through Quen 3 Coder 30B. 00:45:44.818 --> 00:45:50.138 That's the K4KM quantized version running on my own GPU, and it was great. 00:45:50.138 --> 00:45:53.098 It then got me thinking about a framework. 00:45:54.059 --> 00:45:59.659 Pre-order from one of those desktops that i've got in on batch number 12 though. 00:45:59.659 --> 00:46:00.299 It's not. 00:46:00.299 --> 00:46:06.119 Going to come for another few months i'm so excited to have up to 112 gigs of 00:46:06.119 --> 00:46:11.559 vram i can just fill with an lm or two i was a little surprised though that 00:46:11.559 --> 00:46:13.119 i hadn't heard you guys get excited 00:46:13.119 --> 00:46:15.919 about it and how they started shipping them over the last week or so. 00:46:15.919 --> 00:46:20.099 Yeah well we're just getting the reports of them shipping um that's really always 00:46:20.099 --> 00:46:22.859 what i wait with the framework stuff still just i want to i want to hear about 00:46:22.859 --> 00:46:25.779 it in people's hands get the report so if anybody out there is getting them 00:46:25.779 --> 00:46:29.339 please let me know i am tempted yeah. 00:46:29.339 --> 00:46:34.699 Yeah for kind of precisely that reason too i mean it looks like a good a nice cool rig all around. 00:46:34.699 --> 00:46:41.419 Yeah for sure it does it does 112 gigs of vram you maniac you maniac you maniac 00:46:41.419 --> 00:46:47.299 thank you everybody who uh reached out via the matrix or as a chat We really appreciate it. 00:46:47.499 --> 00:46:51.119 And we now transition into the boost. 00:46:56.559 --> 00:47:01.279 And this week, we, as we like to do, are going to start with our baller booster, 00:47:01.479 --> 00:47:06.879 the person who contributed the most to episode 629, who really stepped up above 00:47:06.879 --> 00:47:09.099 the crowd and sent in some real support. 00:47:09.099 --> 00:47:18.319 And this week, it is Blackhost, and he comes in with a really astonishing 435,000 SATs. 00:47:41.423 --> 00:47:45.523 Black Host writes, boosting for some sats for Texas Linux Fist snacks. 00:47:45.743 --> 00:47:49.963 Oh, wow. Thank you, Black Host. And that's actually going to move the needle. 00:47:50.083 --> 00:47:55.383 We have not had any, let's say, commercial bites on working with us to get to Texas Linux Fest. 00:47:55.703 --> 00:47:58.923 We are still bound and determined like hell to get there. You know, 00:47:58.983 --> 00:48:03.023 I've been thinking, too, like these people, they put so much work into these 00:48:03.023 --> 00:48:06.243 events and people show up from all around the world, literally, 00:48:06.543 --> 00:48:10.423 and vendors show up and community happens and ideas are created. 00:48:10.423 --> 00:48:13.243 And it's a damn shame that we don't 00:48:13.243 --> 00:48:15.963 get these captured for more people because it's like 00:48:15.963 --> 00:48:18.703 a tree falling in the forest and nobody's there to hear 00:48:18.703 --> 00:48:21.503 it and it's i'm not trying 00:48:21.503 --> 00:48:25.543 to overstate our role here but what 00:48:25.543 --> 00:48:28.363 happens at these events is unique and special in 00:48:28.363 --> 00:48:31.243 the linux community and i think it's extremely important that a the 00:48:31.243 --> 00:48:33.903 show participate in it and b is the 00:48:33.903 --> 00:48:37.663 show try to capture it the best we can and convey that to the audience this 00:48:37.663 --> 00:48:40.383 is something really unique here and i really want 00:48:40.383 --> 00:48:43.423 to get to texas linux fest and i think we're going to do it with sats 00:48:43.423 --> 00:48:46.583 because nobody else is stepping up uh to 00:48:46.583 --> 00:48:49.783 like work with us and do like a sponsor promo deal and i understand i 00:48:49.783 --> 00:48:52.623 understand i understand but of course the offer's still out there chris at 00:48:52.623 --> 00:48:57.843 jupiter broadcasting uh dot com but uh thank you blackhost that will move the 00:48:57.843 --> 00:49:02.803 needle if we have to self-fund it it's going to be uh with the boost so appreciate 00:49:02.803 --> 00:49:08.863 that very much and that is definitely our baller boost for this week thank you 00:49:08.863 --> 00:49:10.663 sir appreciate it very much well. 00:49:10.663 --> 00:49:14.423 Next up no stromo boosts in with 25 000 cents, 00:49:17.923 --> 00:49:21.483 congrats on the new nebula sponsor i was wondering. 00:49:21.483 --> 00:49:23.423 Though it doesn't have any. 00:49:23.423 --> 00:49:24.323 Coffee in it. 00:49:24.323 --> 00:49:25.143 Oh you know it. 00:49:28.156 --> 00:49:31.956 I think the coffee is the enterprise-grade encryption, maybe? 00:49:31.956 --> 00:49:35.796 No, no. The coffee is what you enjoy when you have a solid networking infrastructure 00:49:35.796 --> 00:49:38.016 that just works. That's where the coffee is, you see? 00:49:39.736 --> 00:49:42.376 Yes. Thank you, Dostro. It's nice to hear from you. 00:49:43.216 --> 00:49:47.336 We have a boost here from Caden. 3,500 sats. 00:49:48.296 --> 00:49:53.056 Hey, guys. I'm still loving the show, and I recently got Hyperland working on 00:49:53.056 --> 00:49:56.736 Ubuntu, but I borked my gaming desktop. 00:49:57.256 --> 00:50:00.736 I did learn apparently my motherboard doesn't like Manjaro for some reason. 00:50:01.396 --> 00:50:07.836 Though I am interested in Hypervibe. Would you recommend it for someone with no NixOS experience? 00:50:08.796 --> 00:50:13.216 You know, for that I might go to CacheOS first. You wouldn't get Hyperland necessarily. 00:50:13.636 --> 00:50:17.536 Maybe you could, but you would get a lot of the optimizations. Not all of them, though. 00:50:18.356 --> 00:50:22.536 I will admit I have a really special collection of optimizations. 00:50:22.736 --> 00:50:27.456 Not to brag, but you know me, guys. And I've been building these for the last couple of years. 00:50:28.336 --> 00:50:32.216 Yeah, you know how I do it. So it's not the same, but they're still, 00:50:32.296 --> 00:50:33.276 they got a really great thing going. 00:50:35.476 --> 00:50:39.976 Hypervibe is nearly impossible to get going without some NixOS experience at the moment. 00:50:40.796 --> 00:50:44.896 We're experimenting with options there. You got pretty far with ISO images this week. 00:50:45.016 --> 00:50:46.296 Yeah, I don't know. Did you ever try it? 00:50:46.456 --> 00:50:49.276 I did not get a chance to try it. We could try it on my Nix book. 00:50:49.356 --> 00:50:49.796 Yeah, we should. 00:50:50.096 --> 00:50:54.356 Totally be down. But I also, of course, while Wes is trying to spin up an ISO, 00:50:54.556 --> 00:50:55.856 I'm like actively making changes. 00:50:56.076 --> 00:50:57.496 Yeah, we'll have to do some catch up there. 00:50:57.636 --> 00:50:57.756 Yeah, yeah. 00:50:58.216 --> 00:51:01.996 I have made some good changes. I did see Hybrid Sarcasm was forking your stuff 00:51:01.996 --> 00:51:05.436 off just to copy the Hyperland setup on top of an Arch install. 00:51:05.616 --> 00:51:05.636 Totally. 00:51:05.636 --> 00:51:06.836 So something like that's possible too. 00:51:07.016 --> 00:51:10.796 The Hyperland configuration, the Waybar configuration, that kind of stuff will 00:51:10.796 --> 00:51:12.156 work across distro bases. 00:51:12.416 --> 00:51:15.816 So that could be a great place to start is cache OS, install Hyperland, 00:51:15.836 --> 00:51:17.336 and then go grab my configs off of my GitHub, 00:51:18.476 --> 00:51:23.916 which is chrislast slash hypervibe I think you'll like it thank you for asking 00:51:23.916 --> 00:51:27.196 and good luck it sounds like you're going to be enjoying it one thing to know 00:51:27.196 --> 00:51:31.276 is just to touch on your hardware issues there it's probably not, 00:51:31.996 --> 00:51:36.216 Manjaro specific it's probably more likely kernel specific and it just happens 00:51:36.216 --> 00:51:40.336 to be the kernel that Manjaro is using and another distribution may very well 00:51:40.336 --> 00:51:41.576 end up using that kernel too, 00:51:42.096 --> 00:51:44.836 Manjaro just might be using it before others are just something 00:51:44.836 --> 00:51:47.996 to keep in mind it's not likely a manjaro specific issue 00:51:47.996 --> 00:51:51.096 uh it could be that is in the realm of possibility but 00:51:51.096 --> 00:51:55.076 it is more likely a kernel issue specifically kernel 00:51:55.076 --> 00:51:58.796 driver issue because the that all is all the driver stuff is not handled by 00:51:58.796 --> 00:52:03.216 the distribution generally except for the nvidia driver like i say generally 00:52:03.216 --> 00:52:11.316 but good luck let us know how it goes thank you for the boost oppi 1984 comes in with 4 000 sats, 00:52:12.967 --> 00:52:17.827 Mad TV was superior to Saturday Night Live. Lower Expectations is a nice nostalgia 00:52:17.827 --> 00:52:20.527 hit. I just wish it didn't mean lower boost amounts. 00:52:21.687 --> 00:52:24.087 It's a great, have you seen the lower expectations bit? 00:52:24.247 --> 00:52:25.707 Yes, it is so good. 00:52:25.747 --> 00:52:28.987 It's worth a YouTube search if you haven't, Mad TV, lowered expectations. 00:52:29.427 --> 00:52:32.607 It's one of my favorite bits. Thank you very much for the boost there. 00:52:32.707 --> 00:52:35.207 Appreciate it, Opby1984. It's good to hear from you. 00:52:36.547 --> 00:52:42.147 Podbun comes in with a row of ducks. Seems very petty to not add it's because 00:52:42.147 --> 00:52:44.527 he isn't as nice as they want him to be. 00:52:44.527 --> 00:52:49.027 I agree talking about bcashfs here um, 00:52:49.907 --> 00:52:52.867 again i know i made this point especially because the people 00:52:52.867 --> 00:52:55.947 that are now excluding him for his behavior are sort of famously 00:52:55.947 --> 00:52:58.667 called out online for their behavior right or 00:52:58.667 --> 00:53:01.367 wrong some of these people involved in 00:53:01.367 --> 00:53:04.947 this discussion have been the focus of 00:53:04.947 --> 00:53:08.847 toxic behavior and claims of toxic behavior going 00:53:08.847 --> 00:53:11.767 on a decade now and now they're using that same 00:53:11.767 --> 00:53:17.147 labeling to exclude kent from the kernel for a feature that makes linux more 00:53:17.147 --> 00:53:22.087 competitive and linux is less competitive without it so the stakes are higher 00:53:22.087 --> 00:53:27.527 than you know i don't know a samba file server built into the kernel but that 00:53:27.527 --> 00:53:30.787 makes it and this doesn't thank you pod bun good boost. 00:53:30.787 --> 00:53:37.167 Well gene bean sent in a batch of boosts seven in total for 10,057 sats, 00:53:42.899 --> 00:53:47.199 This is okay. Episode 626 here. Checking in from the past. 00:53:48.179 --> 00:53:53.339 How did I get so far behind? Here's hoping I catch up before Sunday's new episode. 00:53:53.839 --> 00:53:54.959 Time machine boost. 00:53:56.619 --> 00:54:01.159 He says, FYI, Sonos works super well with music assistant. 00:54:01.419 --> 00:54:08.079 I have heard that. So the wife got the Kia speakers that are essentially Sonos 00:54:08.079 --> 00:54:09.659 speakers that we're going to set up at her office. 00:54:09.659 --> 00:54:12.459 But, you know, in the back of my mind, if I ever get rid of the HomePods, 00:54:12.559 --> 00:54:16.579 which will happen one day, maybe I go to Sonos. Maybe. I don't know. 00:54:17.019 --> 00:54:20.779 Gene is also pretty stoked about the AirPods integration on Linux recently. 00:54:20.779 --> 00:54:24.719 And that's going to be super handy, especially with access to that noise canceling. 00:54:25.579 --> 00:54:31.219 For Linux Unplugged 627, this episode has been extra good. And I really enjoyed 00:54:31.219 --> 00:54:33.179 hearing the vibe coding adventure. 00:54:34.319 --> 00:54:40.099 He says uh chris check out this four button device with switching music at the 00:54:40.099 --> 00:54:44.999 clinic it integrates with zha without issue for me. 00:54:44.999 --> 00:54:48.039 Uh so i like these quad panel buttons 00:54:48.039 --> 00:54:50.759 gene and i have one similar like i mentioned to you in a dm that's kind of like 00:54:50.759 --> 00:54:53.459 that but for this use case i'm seeing 00:54:53.459 --> 00:54:56.859 if i can find it in my order history there's another type of z 00:54:56.859 --> 00:54:59.679 wave button that i like even more and it's 00:54:59.679 --> 00:55:04.899 got two big buttons on the top and then two small buttons along the bottom and 00:55:04.899 --> 00:55:09.059 it fits really nicely on the wall it's really clean you can magnetically mount 00:55:09.059 --> 00:55:13.059 it or you can install it i think zeus makes one that's not the one i've been 00:55:13.059 --> 00:55:15.979 buying but i think that's the one i'm going to buy in the future but i'll put 00:55:15.979 --> 00:55:18.379 a link to it in the show notes it's a four wave z wave button, 00:55:18.979 --> 00:55:23.739 panel but it's tiny and it supports magnetic mounts or you can put it in like 00:55:23.739 --> 00:55:25.539 a traditional wall switch mount. 00:55:25.739 --> 00:55:29.739 It supports Z-Wave 800 too with that long range support that just came out with 00:55:29.739 --> 00:55:33.159 that new Home Assistant antenna. And I've got, 00:55:34.235 --> 00:55:39.155 Three, I think, three or so. And they last over a year, I can tell you that. 00:55:39.395 --> 00:55:42.875 I have them up front, so I can just with a button while I'm driving, 00:55:43.035 --> 00:55:45.135 I can turn off all the lights or turn off the water pump. 00:55:45.495 --> 00:55:48.515 I have one in the bathroom. So if you come into the bathroom late at night, 00:55:48.635 --> 00:55:51.195 you have a button you can hit that'll turn the lighting on really dim in there. 00:55:51.655 --> 00:55:54.015 Or if you step into the bathroom late at night and it's cold, 00:55:54.935 --> 00:55:57.755 or whatever it might be, could be in the morning, I have a button you can press, 00:55:57.855 --> 00:56:00.555 one button, and it increases the temperature in the bathroom by five degrees. 00:56:01.135 --> 00:56:03.575 Also, transversely, if you get in the bathroom and it's too warm, 00:56:03.575 --> 00:56:07.975 another button in there decreases the temperature in the bathroom by five degrees and then lastly so. 00:56:07.975 --> 00:56:09.875 This is why you're always hanging out in there. 00:56:09.875 --> 00:56:13.095 Yeah it's my home office and then lastly i 00:56:13.095 --> 00:56:15.895 have a button because i'm an rv that toggles the water 00:56:15.895 --> 00:56:18.655 pump and this thing fits within 00:56:18.655 --> 00:56:23.155 the size of a traditional light switch socket so that's how small it is it's 00:56:23.155 --> 00:56:26.355 really great very big fan and the battery life is fantastic takes a standard 00:56:26.355 --> 00:56:31.535 kind of coin type battery and it's worked really well for me so i'll toss a 00:56:31.535 --> 00:56:35.915 link to that in the show notes gene always appreciate hearing from you thank 00:56:35.915 --> 00:56:37.775 you very much for the boost gene. 00:56:37.775 --> 00:56:43.395 Also sent in a little fountain fm clip of me saying a certain something. 00:56:43.395 --> 00:56:47.135 Oh i you know i should have pulled this ahead of time because i saw this come 00:56:47.135 --> 00:56:51.255 in early and i played it gene did some yeoman's work for us here. 00:56:57.728 --> 00:56:59.968 I see there's a collection starting here. 00:57:00.228 --> 00:57:02.648 I like it. I like it. 00:57:02.768 --> 00:57:07.248 Gene's last boost here. I'm really interested in Bcash FS, but I think it's 00:57:07.248 --> 00:57:11.308 perfectly acceptable for the maintainers to kick it if the maintainer is a jerk. 00:57:11.768 --> 00:57:15.168 I've worked with really smart jerks, and it just isn't worth it. 00:57:15.368 --> 00:57:18.188 To be fair, I also don't agree with how Linus treats people, 00:57:18.328 --> 00:57:20.368 but no one has the power to change Linus. 00:57:20.548 --> 00:57:24.888 They do have the power to not perpetuate it, though. i hope they work it out. 00:57:24.888 --> 00:57:29.068 Yeah i mean i think i generally agree on a no jerks policy and i do think it's 00:57:29.068 --> 00:57:32.908 a good opportunity for everyone involved to reflect on how best to communicate, 00:57:33.448 --> 00:57:36.948 uh because i think even kent would agree you know he he did cross some some 00:57:36.948 --> 00:57:40.488 lines here here and there and there are a lot of ways we could probably be doing 00:57:40.488 --> 00:57:42.048 it more effectively on all sides i. 00:57:42.048 --> 00:57:45.828 Agree with all that i just have one question when did we close the jerk door 00:57:45.828 --> 00:57:51.028 at what point was when did we cut off the jerks from the kernel because we obviously 00:57:51.028 --> 00:57:55.608 let a lot of jerks in so when was the jerk door closed, and how come nobody told Kent? 00:57:57.088 --> 00:57:58.628 That's all. I mean, what do you think about that? 00:57:59.888 --> 00:58:05.628 I think it's not a close and you're done with the door. It's sort of a continual evaluation. 00:58:06.208 --> 00:58:07.768 A constantly improving process. 00:58:07.868 --> 00:58:10.888 Yes, that's what we're hoping for. Because people are going to make mistakes, 00:58:10.988 --> 00:58:14.648 there are going to be flare-ups, but like, if we can try and commit to continue 00:58:14.648 --> 00:58:16.568 to do better as a community. 00:58:16.828 --> 00:58:20.368 I agree. Although, you know, remember just a week or so before this conversation 00:58:20.368 --> 00:58:24.848 happened, Linus told a developer to get bent and his code made the world a worse place. 00:58:24.928 --> 00:58:25.068 Yep. 00:58:25.868 --> 00:58:29.548 Direct quotes. I mean, I agree with you, but it's like we're sometimes applying 00:58:29.548 --> 00:58:33.008 the brakes and sometimes we're applying the gas. Sometimes we're doing it both at the same time. 00:58:33.628 --> 00:58:37.448 Like, we're literally telling somebody to get bent while we're yelling at Kent for his toxic behavior. 00:58:38.108 --> 00:58:40.648 I don't know. I do hope they work it out. I agree with that. 00:58:40.748 --> 00:58:41.688 And I do think you're right. 00:58:41.728 --> 00:58:43.988 It should be something that's a constantly improving process. 00:58:44.028 --> 00:58:46.868 It's just unfortunate that this has happened. 00:58:47.428 --> 00:58:50.028 And, you know, with a little more diplomacy, it probably could have been avoided. 00:58:51.228 --> 00:58:55.408 Odyssey Western comes in with 3,333 sats. That's a Chuck E. Cheese boost. 00:58:57.876 --> 00:59:01.356 Okay, sending a boost because I didn't realize my wallet had ran out of SATs, 00:59:01.396 --> 00:59:02.156 so I guess he wasn't streaming. 00:59:02.576 --> 00:59:06.856 With regard to the last episode with Crush, it really resonated with me because 00:59:06.856 --> 00:59:10.556 I'm currently using Warp Terminal and Claude to go through my Markdown notes 00:59:10.556 --> 00:59:12.936 and clean them up. It is good at Markdown. 00:59:13.276 --> 00:59:18.156 Plus, it helped me learn how to research and do some tech for, what's DDGR? 00:59:18.396 --> 00:59:21.056 Duck, duck, go, but it's a terminal app. 00:59:21.176 --> 00:59:24.356 Right, on the terminal, right, and links, too. Oh, cool, cool. 00:59:24.356 --> 00:59:26.636 So, Odyssey's busting up some links action now. 00:59:27.096 --> 00:59:30.536 He says i was able to break down information and get summaries took me about 00:59:30.536 --> 00:59:34.536 a week to get through the rules to tune it because you know it's like trying to guide a toddler, 00:59:36.776 --> 00:59:40.096 it is that's a good yes that's how you got to think of it you really got to be very clear, 00:59:40.636 --> 00:59:44.596 anyways i'm warming up to the idea of using some lms as a tool to solve problems 00:59:44.596 --> 00:59:48.336 and maybe document work processes that i can reference later anyways love you 00:59:48.336 --> 00:59:52.276 guys we love you too always nice to hear from you yeah. 00:59:52.276 --> 00:59:55.156 It really was resonating with me this week just because it's like oh i had some 00:59:55.156 --> 01:00:00.316 LLM successes and some like I was telling you guys I was been using UDHCP and 01:00:00.316 --> 01:00:03.356 I wanted like a little viewer for the lease files like oh surely an LLM can 01:00:03.356 --> 01:00:05.796 make me a little 2E really quick that'll just but. 01:00:05.796 --> 01:00:07.096 It could. 01:00:07.096 --> 01:00:09.276 Not hack the binary decoding it 01:00:09.276 --> 01:00:12.956 could get the 2E part it just couldn't get the bytes in the NDN is right. 01:00:12.956 --> 01:00:18.756 My theory continues to be there's like a line of complexity and when you cross 01:00:18.756 --> 01:00:23.096 it there are really no help at all but if you're dealing with like you know 01:00:23.096 --> 01:00:27.936 plain text config files simpler stuff you know an nginx config file, 01:00:28.516 --> 01:00:31.796 they're pretty good at that and it's also really well documented online anyways, 01:00:32.356 --> 01:00:36.576 so they have a lot of reference material to train from but then when you get 01:00:36.576 --> 01:00:41.196 to more complex obscure niche things or things that are super, 01:00:41.756 --> 01:00:45.916 modern relevant just changed kind of stuff bleeding edge it struggles not deeply 01:00:45.916 --> 01:00:47.576 indexed yeah yeah exactly. 01:00:48.036 --> 01:00:52.056 Ooh okay well outdoor geek is coming in with some stuff I think we're gonna 01:00:52.056 --> 01:00:54.276 like with 5,000 sets yeah, 01:00:55.551 --> 01:00:58.991 Hey, Chris, what's more bleeding edge of the Nix OS Unstable? 01:00:59.231 --> 01:01:01.671 The Nix Package's Master Branch. 01:01:01.851 --> 01:01:06.111 Oh, I thought I was going to say Nix OS Ice Cold. Oh, yeah, the Master Branch, sure. 01:01:06.851 --> 01:01:11.231 Now, I'm using Overlies to access that I'm not just YOLOing my whole OS on Master. 01:01:11.551 --> 01:01:15.071 Really, I just added it so I could get the latest Nexus mod app. 01:01:15.311 --> 01:01:18.171 And then a little link here pointing you maybe to how to do it. 01:01:18.251 --> 01:01:24.491 Am I crazy to kind of want to do this? So right now, I pull from Nix OS Unstable, 01:01:24.491 --> 01:01:29.851 but i am pulling hyperland for master and so there are days where i'll have 01:01:29.851 --> 01:01:32.711 multiple updates to hyperland in one day i. 01:01:32.711 --> 01:01:35.091 Think you probably do have to be prepared right you're going to be building stuff. 01:01:35.091 --> 01:01:36.371 Yourself yeah so. 01:01:36.371 --> 01:01:37.091 You will be. 01:01:37.091 --> 01:01:40.691 Although it's pretty simple benefit so it's it's it's yeah. 01:01:40.691 --> 01:01:42.151 If it's not like a giant browser or whatever. 01:01:42.151 --> 01:01:46.631 Exactly i was gonna say it's nothing like building firefox or chromium um you 01:01:46.631 --> 01:01:50.711 know i also want to give a shout out because i i figured out thanks to some 01:01:50.711 --> 01:01:54.211 help from uh i should have gotten your name i'm so sorry somebody who helped 01:01:54.211 --> 01:01:55.991 me with an issue I had on GitHub with Hypervibe, 01:01:56.131 --> 01:02:01.551 where every now and then I would sit down at my machine and some of my configs had been reverted. 01:02:01.751 --> 01:02:05.571 I'd have errors on the screen about some config files missing and my key bindings would be reverted. 01:02:07.071 --> 01:02:10.171 And I was trying to track this down because it was initially also reverting 01:02:10.171 --> 01:02:14.251 my wallpaper to like stock Hyperlint wallpaper or whatever. I got that solved. 01:02:14.771 --> 01:02:19.271 But I kept having this problem where my key bindings would revert and I'd have errors on my screen. 01:02:19.491 --> 01:02:23.511 And if I did a new build and either switched or rebooted, everything would be 01:02:23.511 --> 01:02:27.331 fine and even if I even experimented with I did a build before I went to bed 01:02:27.331 --> 01:02:32.131 went to bed left the machine running came back it had been reverted did a build again it was fine. 01:02:32.691 --> 01:02:35.511 It was do you have stuff that's getting garbage collected? 01:02:36.111 --> 01:02:40.491 It was automatic updates and maybe garbage collection too were not pulling from my flake, 01:02:41.111 --> 01:02:44.991 and so it was rebuilding and then Hyperland one of the neat things about it 01:02:44.991 --> 01:02:49.131 is it hot reloads its config so it was just hot reloading because it was also 01:02:49.131 --> 01:02:51.191 doing a switch when it was doing an automatic upgrade, 01:02:52.751 --> 01:02:56.211 so uh you know the reason why i didn't catch that is because yourself. 01:02:56.211 --> 01:02:57.671 Over a little fun corner. 01:02:57.671 --> 01:03:00.351 Yeah you know trying to ride the bleeding 01:03:00.351 --> 01:03:03.371 edge and all that and i didn't catch it because i i inherited 01:03:03.371 --> 01:03:06.051 that when i burned my system down i left like my 01:03:06.051 --> 01:03:10.171 stock like out of memory config and my performance tuning and that stuff and 01:03:10.171 --> 01:03:12.791 got rid of all the packages and the desktop environment and replaced all that 01:03:12.791 --> 01:03:16.031 and so i inherited that from the old system config and didn't even think about 01:03:16.031 --> 01:03:20.131 it and so now that is fixed and that was the last outstanding issue it's been 01:03:20.131 --> 01:03:22.691 really great great to hear from you outdoor geek thank you for the boost and 01:03:22.691 --> 01:03:24.731 i love your style i approve. 01:03:25.451 --> 01:03:28.171 Well jasko boosts in 5 000 sets, 01:03:31.685 --> 01:03:36.625 Regarding Bcash FS, I find it sad that these squabbles in the mailing list impact 01:03:36.625 --> 01:03:38.145 support within the kernel. 01:03:38.845 --> 01:03:43.445 Riser FS is still in the kernel, and I don't think there's anything more toxic than killing your wife. 01:03:44.025 --> 01:03:47.545 Free software has its legacy on the shoulders of abrasive personalities, 01:03:47.865 --> 01:03:50.965 whether it be Stallman, Torvalds, or the myriad of other characters. 01:03:51.405 --> 01:03:55.725 Why do they get a pass, but Overstreet doesn't? Also, man, I can't wait for 01:03:55.725 --> 01:03:59.985 all the bugs to be ironed out on Lightning. I can't seem to boost at a higher 01:03:59.985 --> 01:04:03.165 value on Fountain or through Albi or even Podverse. 01:04:03.685 --> 01:04:07.465 So to the first point, I mostly agree, you know, it's, but like Wes says, 01:04:07.785 --> 01:04:08.805 there's two factors here. 01:04:08.965 --> 01:04:10.645 It's a process of improving communications, 01:04:10.785 --> 01:04:14.245 but two, it comes down to relationships and established trust. 01:04:14.965 --> 01:04:17.665 Lightning could be a liquidity issue on one of our nodes. Sometimes some of 01:04:17.665 --> 01:04:20.065 your boost will get through, but not all of it. Something we could check on. 01:04:20.305 --> 01:04:24.845 Generally, it comes down to liquidity problem. Fountain should be fine. 01:04:25.305 --> 01:04:27.925 I'm surprised you're having problems. I'm sorry to hear that. 01:04:28.505 --> 01:04:30.745 Be happy to troubleshoot with you if you want to ping us on Matrix. 01:04:31.385 --> 01:04:34.845 We do also have a boost group on Matrix as well that helps do some troubleshooting. 01:04:35.465 --> 01:04:38.565 Definitely want to hear a large boost come in. Thank you, Jasko. Appreciate it. 01:04:39.225 --> 01:04:42.885 Forty Deuces here with 8,400 sats. 01:04:46.835 --> 01:04:49.855 I've been feeling the pain of no boosting your sat streaming from the private 01:04:49.855 --> 01:04:51.355 bootleg feed. Yeah, I know. 01:04:51.895 --> 01:04:56.515 One idea would be to credit or pod press system for fountain that allows this 01:04:56.515 --> 01:04:57.675 podcast creator to give value. 01:04:57.855 --> 01:05:00.155 Yeah, if we move over to the fountain system, that could be true. 01:05:00.575 --> 01:05:03.975 That could be true. Yeah. Or if we generated the RSS feed ourself, 01:05:04.375 --> 01:05:05.575 he says, you know, you could ditch it. 01:05:05.735 --> 01:05:08.155 It's true. We have thought about it. We have thought about it. 01:05:08.215 --> 01:05:11.835 It's just they do a pretty good job except for this one thing, right? 01:05:12.295 --> 01:05:16.235 It's really nice in a lot of other ways, like to be able to spin up promo codes and things like that. 01:05:17.215 --> 01:05:20.755 But with something also we're considering maybe just building our own workaround 01:05:20.755 --> 01:05:23.795 that just bypasses all of this, which we may have more on in the future. 01:05:24.435 --> 01:05:29.395 And it may just be a lot easier and be app independent. You never know. 01:05:30.055 --> 01:05:33.335 He says, it's great to hear you on the Hyperland train. I'll be checking out 01:05:33.335 --> 01:05:37.015 your config for sure. I've been going on this route for a while and loving it. 01:05:37.175 --> 01:05:40.595 It sounds like you've gone a similar route to the multi-host like Flake approach. 01:05:40.795 --> 01:05:44.875 Someone mentioned the repeated builds. This takes a little less time with Home 01:05:44.875 --> 01:05:47.855 Manager, and there are a couple of ways to approach this. 01:05:48.215 --> 01:05:52.495 My tip would be keep it as a standard Hyperland config file outside of Nix and 01:05:52.495 --> 01:05:55.035 Home Manager while making heavy changes inside. 01:05:55.255 --> 01:05:58.415 This way you benefit from the hot reload and saving of the config file. 01:05:58.795 --> 01:06:02.455 Once it's more stable, start writing it to your .config folders with Home Manager's 01:06:02.455 --> 01:06:06.295 home.file. Then convert to a Nix eventually when it's pretty solid. 01:06:06.715 --> 01:06:08.595 That does sound like a nice iteration process. 01:06:09.275 --> 01:06:11.995 I have been tapping the brakes on Home Manager. 01:06:12.875 --> 01:06:17.915 I know myself, and I know that if I like it, I can really go down a rabbit hole and hyper-optimize it. 01:06:18.435 --> 01:06:21.315 And so I often resist these kinds of things. 01:06:22.015 --> 01:06:25.275 But as I've talked to people out there, like in the Knicks Nerds chat, 01:06:25.975 --> 01:06:30.235 and the feedback I've gotten from you folks out there, it does seem like a lot 01:06:30.235 --> 01:06:34.175 of people are recommending I just bite the bullet and use Home Manager for this 01:06:34.175 --> 01:06:36.275 stuff. I thought you would do it before me, Wes. 01:06:36.755 --> 01:06:38.095 Yeah, I think we've both been like, well... 01:06:39.156 --> 01:06:42.516 That's going to be a whole Easter egg to get into. 01:06:42.736 --> 01:06:46.756 Yeah, a whole can of worms, as they say. Thank you very much. 01:06:46.856 --> 01:06:49.676 Appreciate that boost. Nice to hear from you. Four to deuce. 01:06:50.996 --> 01:06:54.976 SatStagger7 comes in with 9,472 sats. 01:06:57.276 --> 01:06:57.716 Nice. 01:06:58.116 --> 01:07:01.876 Hey there. Last week's Baller Booster here. Just wanted to apologize for the 01:07:01.876 --> 01:07:03.856 many typos in my message last week. 01:07:04.036 --> 01:07:04.856 Do not worry about it. 01:07:04.856 --> 01:07:05.276 Yeah, it happens to all of us. 01:07:05.276 --> 01:07:06.456 That's the least of our concern. 01:07:07.416 --> 01:07:10.636 These last days i was looking into a pic from a couple episodes ago 01:07:10.636 --> 01:07:13.916 oh my mesh sidecar nix os module lets 01:07:13.916 --> 01:07:17.236 you make any service available as a node in your tail net uh cool 01:07:17.236 --> 01:07:20.256 glad to hear you checked it out um and but 01:07:20.256 --> 01:07:22.976 sat stacker goes on but since i'd like 01:07:22.976 --> 01:07:26.616 to communicate to my services over tls i started looking into other solutions 01:07:26.616 --> 01:07:30.996 and i would like to propose an amazing pic for all the self-hosters out there 01:07:30.996 --> 01:07:36.556 oh caddy dash tail scale ah it's a plugin for the caddy reverse proxy that connects 01:07:36.556 --> 01:07:40.276 to your tail net and can serve each site as a separate tail net node. 01:07:40.476 --> 01:07:40.676 Aha. 01:07:41.056 --> 01:07:45.536 Caddy can then automatically fetch the tail scale certificate and serve your page via TLS. 01:07:45.776 --> 01:07:50.856 And the NixOS package even has a function with plugins to build in the plugin. 01:07:51.116 --> 01:07:52.856 I can see that being a system that works pretty well. 01:07:53.116 --> 01:07:56.616 Yeah, I've been pleased to see that the Caddy support NixOS has been getting better over the years. 01:07:56.856 --> 01:07:57.196 Mm-hmm. 01:08:01.476 --> 01:08:04.136 Well, Sam H boosted in here two boosts for 01:08:04.136 --> 01:08:06.976 a total of 3333 and 01:08:06.976 --> 01:08:12.776 one of these is road ducks i love 01:08:12.776 --> 01:08:15.476 your hyper vibe idea i think 01:08:15.476 --> 01:08:18.396 we need more of this for nix os the only system i 01:08:18.396 --> 01:08:21.856 have available to try it on is my framework laptop so 01:08:21.856 --> 01:08:27.116 i did the right thing and blew away my config to try your flake yes 01:08:27.116 --> 01:08:32.636 i noticed a few problems and i had to google how to fix the dpi but it was great 01:08:32.636 --> 01:08:37.256 to see it working and after a quick reboot back to my previous config for now 01:08:37.256 --> 01:08:41.936 cool that's neat i'd like to integrate it into my normal config so i can try 01:08:41.936 --> 01:08:44.816 it on a more long-term basis you. 01:08:44.816 --> 01:08:48.096 Know you'd like west said earlier you could grab some of the hyperlink config 01:08:48.096 --> 01:08:51.596 stuff and just keep that but we are trying to get it more and more portable 01:08:51.596 --> 01:08:54.896 too and just recently i got it much more multi-machine so you would be able 01:08:54.896 --> 01:08:57.436 to just essentially i have a host folder, 01:08:57.576 --> 01:09:02.096 and you would just put your own system.nix in there with any of the differences for your system. 01:09:02.216 --> 01:09:04.656 And then you could also put your own hyperlink config files and Waybar config 01:09:04.656 --> 01:09:08.556 files in there and override the defaults. Takes a little work, but you can do it. 01:09:09.569 --> 01:09:14.389 Sam continues here i just got an email saying they charged me for my framework 01:09:14.389 --> 01:09:19.469 desktop so hopefully i'll be giving hypervibe a try button that soon i've learned 01:09:19.469 --> 01:09:25.249 to put it next to my tv for big screen gaming but the main use will be for local ai. 01:09:25.249 --> 01:09:28.209 Oh that's gonna be fun i hope you 01:09:28.209 --> 01:09:31.289 like it and i would very much love a follow-up on 01:09:31.289 --> 01:09:34.149 your takes when you get it and after you've used it for a bit it's on 01:09:34.149 --> 01:09:37.309 my radar as maybe a future workstation for me i 01:09:37.309 --> 01:09:40.529 was trying to make myself feel better and i i went over to uh 01:09:40.529 --> 01:09:43.309 like you know some one of these lms and i said here's all 01:09:43.309 --> 01:09:46.129 my system specs of my workstation upstairs and i'm 01:09:46.129 --> 01:09:49.309 like compared to like a current gen intel or 01:09:49.309 --> 01:09:52.209 amd system like this is still a pretty good system 01:09:52.209 --> 01:09:54.949 for like day-to-day web browsing and and just you 01:09:54.949 --> 01:09:57.729 know standard desktop tasks right i mean maybe i 01:09:57.729 --> 01:10:00.489 do a little bit of this and that but it's you know so i ask it to try to make me feel better 01:10:00.489 --> 01:10:03.689 and it comes back with no you would 01:10:03.689 --> 01:10:07.589 see a substantial and noticeable improvement if you upgraded your system like 01:10:07.589 --> 01:10:13.529 no holes bar totally trashed my box and i'm like okay it's like your your processor 01:10:13.529 --> 01:10:20.089 it's like from 2015 brother like what are you doing what are you doing like 01:10:20.089 --> 01:10:21.589 well it's been fine i just closed maybe. 01:10:21.589 --> 01:10:23.109 They got better in 10 years i don't know. 01:10:23.109 --> 01:10:26.349 Well i hope you get it soon yeah well they might you know maybe they made some 01:10:26.349 --> 01:10:30.669 improvements wes you just never know i also saw user 46 come and say they were 01:10:30.669 --> 01:10:36.089 definitely going to try out hypervibe And, you know, we have the 2,000-sat cutoff, 01:10:36.169 --> 01:10:37.929 but we try to read your boosts if they come in. 01:10:38.249 --> 01:10:41.689 And so every now and then we'll pull them forward. So user's 46,000-sats. 01:10:41.809 --> 01:10:44.469 He says, I'm checking out Hypervibe. Definitely checking it out. 01:10:45.029 --> 01:10:48.629 Let me know how it goes. And also, if you want to set your username and your 01:10:48.629 --> 01:10:50.309 fountain profile and boost back in, let us know who you are. 01:10:50.869 --> 01:10:53.729 We appreciate it. Now, we had quite the showing today, boys, 01:10:53.749 --> 01:10:58.749 because we had that monster baller boost that talk about setting the tone from the top. 01:10:59.729 --> 01:11:03.869 Setting the tone from the top. Blackhost with his 435,000 sat boost, 01:11:04.009 --> 01:11:08.129 one of our best baller boosts we've had in ages. So we had a really good showing this week. 01:11:08.229 --> 01:11:16.469 So let's talk about our sat streamers. We had 38,872 sats that were streamed by our sat streamers. 01:11:17.109 --> 01:11:20.769 Individually, it was a total of 1,141 streams. 01:11:21.569 --> 01:11:26.569 That is pretty cool. So when you combine that with our boost, yeah, you know. 01:11:26.769 --> 01:11:34.129 You know it's a good one because we stacked a grand total of 554,411 sets. 01:12:02.690 --> 01:12:06.230 Thank you very much, everybody who participated in the boost or is a member. 01:12:06.350 --> 01:12:07.530 This is a value for value podcast. 01:12:07.670 --> 01:12:11.290 What we really are trying to do here is keep a sustainable program that focuses 01:12:11.290 --> 01:12:14.090 on the things you really care about because you're our biggest customer. 01:12:14.270 --> 01:12:16.630 And we're serious about what we do. We put a lot of work into it. 01:12:16.870 --> 01:12:19.430 An enormous amount of work, attention and effort goes into this. 01:12:19.570 --> 01:12:24.330 If you got some value out of it, you can become a member or you can send us a boost with a message. 01:12:24.430 --> 01:12:28.070 And if it's above 2000 sats, we will read it on the show. Thank you, 01:12:28.150 --> 01:12:33.670 everybody who supports this here podcast, making episode 629 of Your Unplugged program possible. 01:12:35.870 --> 01:12:39.590 We got a smattering of picks to get out of here. One of them's on theme, 01:12:39.610 --> 01:12:41.650 so we really had to include it this week. 01:12:41.890 --> 01:12:44.230 We were going to stick with just a couple of picks, but then we're like, 01:12:44.310 --> 01:12:45.910 this is too perfect not to include it. 01:12:45.910 --> 01:12:46.650 And it has a great name. 01:12:46.970 --> 01:12:52.250 That's true. It's called Wake My Potato. This is a theme on a project I talked 01:12:52.250 --> 01:12:55.790 about earlier, but a little bit different. This is really meant for those of 01:12:55.790 --> 01:12:58.330 us who try to make the most out of our old potato computers. 01:12:59.130 --> 01:13:03.450 Maybe they don't even have batteries. Some old machines actually wake, 01:13:03.710 --> 01:13:05.550 don't have proper wake on LAN support. 01:13:05.770 --> 01:13:09.830 Yeah, so you want to use Shuthose, but you can't. But you could use WakeMyPotato, 01:13:10.110 --> 01:13:14.870 which is a simple and last resort, as they say, systemd Linux service to keep 01:13:14.870 --> 01:13:18.710 your old potato laptop alive and running in the event of a power failure. 01:13:18.710 --> 01:13:24.090 So it uses RTC wake to schedule wake ups in the near future but it has some 01:13:24.090 --> 01:13:28.170 built in safety so like if you have a laptop it's running on AC power power 01:13:28.170 --> 01:13:31.090 failure but it has some amount of battery capacity this thing will, 01:13:32.070 --> 01:13:37.350 tell the clock to keep waking it up in case it does go to sleep but it will 01:13:37.350 --> 01:13:39.930 detect if like your laptop's going to run out of power. 01:13:39.930 --> 01:13:40.270 And it. 01:13:40.270 --> 01:13:41.890 Will safely power it off at that point. 01:13:41.890 --> 01:13:45.350 I mean this is awesome if you've got I mean not that I would ever do this but 01:13:45.350 --> 01:13:49.210 let's say you had like an old x86 thinkpad that was kind of working as one of 01:13:49.210 --> 01:13:52.610 your home lab machines and then you hung a bunch of discs off that plus it has 01:13:52.610 --> 01:13:56.050 two discs inside there and you want to make sure your file systems are safe 01:13:56.050 --> 01:13:59.670 and properly shut down and your battery only lasts for like 10 minutes because 01:13:59.670 --> 01:14:01.170 it's old and probably about to blow up, 01:14:02.409 --> 01:14:06.689 Well, wake my potato. I can solve that for you. That's one of the things I really appreciate about it. 01:14:06.749 --> 01:14:10.009 It's like, oh, you're about to run out of power. Let me safely shut down your 01:14:10.009 --> 01:14:12.189 stuff, save your data, unmount your stuff. 01:14:12.689 --> 01:14:16.809 And then you can also use it to turn it back on, which seems like the really 01:14:16.809 --> 01:14:20.409 useful case for me. It is a GPL 3.0. 01:14:20.689 --> 01:14:24.049 So nice and easy, breezy, no concerns there. 01:14:24.289 --> 01:14:29.429 So that's our on theme pick. But then this is too cool not to share. 01:14:29.429 --> 01:14:35.109 Spectacle is a really, really well-equipped screenshot tool for the Plasma desktop. 01:14:35.649 --> 01:14:40.269 And it's just missing one feature that I hope one day gets baked in. 01:14:40.429 --> 01:14:43.449 But Wes, you found a way to add it today. We don't have to wait. 01:14:43.769 --> 01:14:49.389 No, you did not. Welcome Spectacle OCR Screenshot, a simple QT application that 01:14:49.389 --> 01:14:54.609 integrates KDA Spectacle Screenshot tool with the Tesseract OCR engine to extract 01:14:54.609 --> 01:14:56.969 text from screenshots as well as QR codes. 01:14:57.969 --> 01:15:02.549 Really, really nice. So you can, I love this functionality on iOS. 01:15:03.269 --> 01:15:06.669 You take a picture of something, and then you can highlight the text in it. 01:15:06.909 --> 01:15:11.269 Oh, it's surprisingly useful. Also, it makes it indexable for search later on. 01:15:11.809 --> 01:15:17.889 Yeah, so this one's like a separate cute app. But then there's also Spectacle-OCR, 01:15:18.229 --> 01:15:19.589 which is just a shell script. 01:15:19.729 --> 01:15:22.629 It does expect you to have Tesseract installed as well. 01:15:22.849 --> 01:15:26.869 And Spectacle. But it adds it to the existing Spectacle install if you already have it. 01:15:26.889 --> 01:15:31.349 Yeah, so it's two takes on the same idea. hopefully one of them works for your situation. 01:15:31.349 --> 01:15:34.269 And that one is gpl3 indeed so you 01:15:34.269 --> 01:15:37.409 got a couple options there if you're a spectacle user which i've discovered 01:15:37.409 --> 01:15:42.609 needs a lot of plasma infrastructure unfortunately because it's my favorite 01:15:42.609 --> 01:15:47.849 screenshot tool uh but i'm not using it anymore in hyperland in fact like an 01:15:47.849 --> 01:15:51.629 animal i'm just using command line apps i sent you guys a screenshot today i just, 01:15:52.658 --> 01:15:56.638 I just used a command line tool to take that screenshot. It does a wailing grab 01:15:56.638 --> 01:15:57.658 and dumps it to the clipboard. 01:15:57.758 --> 01:15:59.378 Vibing yourself backwards over there. 01:15:59.558 --> 01:16:04.558 So if anybody has any recommendations for some screenshot tools that are not 01:16:04.558 --> 01:16:10.098 GNOME or Plasma specific, that are lightweight, my main thing I want is I want 01:16:10.098 --> 01:16:12.558 to be able to take a box. I want to be able to draw a box, take a screenshot 01:16:12.558 --> 01:16:13.818 of that box, copy to the clipboard. 01:16:14.058 --> 01:16:16.438 I don't need a file. I don't need my whole desktop. 01:16:16.978 --> 01:16:19.638 Don't you want it to upload to one of a few different proprietary images? 01:16:19.638 --> 01:16:20.818 I do not need that generally. 01:16:21.478 --> 01:16:25.998 Although every now and then it's kind of handy for Lincoln. I will admit that. I will admit that. 01:16:26.438 --> 01:16:29.978 Okay, that's it for us this week. You can find links to our picks and our news 01:16:29.978 --> 01:16:37.278 and our self-hosted HomeLab apps in the show notes over at linuxunplugged.com slash 629er. 01:16:37.598 --> 01:16:40.458 And, of course, we'd love it if you want to make it a live Tuesday on a Sunday. 01:16:40.638 --> 01:16:45.218 You can join us Sundays at 10 a.m. Pacific, 1 p.m. Eastern. 01:16:49.198 --> 01:16:52.038 You know i think we got a hot tip in here for him too west there's some extra 01:16:52.038 --> 01:16:54.498 functionality in this here podcast they might not know about. 01:16:54.498 --> 01:17:02.458 Yes embedded deep within our rss feed it's json chapters and podcasting 2.0. 01:17:02.458 --> 01:17:05.458 Transcripts yep transcripts and chapters you can jump around 01:17:05.458 --> 01:17:08.178 and re-listen or find what we talked about we love 01:17:08.178 --> 01:17:12.638 it when you do that because then you don't have to ask us uh it's mostly true 01:17:12.638 --> 01:17:16.698 also i want your tips on wi-fi cameras that will work with frigate please help 01:17:16.698 --> 01:17:19.958 me out with this one i'd love to do a big old segment on it and thank you so 01:17:19.958 --> 01:17:24.238 much for joining us on this week's episode of your unplugged program we'll see 01:17:24.238 --> 01:17:27.498 you right back here next tuesday as in sunday.
Previous episode Next episode

Related episodes

Search

Search

Listen on

Apple Podcasts Spotify RSS feed

Tags

Privacy