WEBVTT 00:00:11.375 --> 00:00:16.235 Hello, friends, and welcome back to your weekly Linux talk show. My name is Chris. 00:00:16.395 --> 00:00:17.075 My name is Wes. 00:00:17.295 --> 00:00:18.215 And my name is Brent. 00:00:18.595 --> 00:00:22.535 Hello, gentlemen. Coming up on the show today, it's our take on Ubuntu's plan 00:00:22.535 --> 00:00:26.175 for a leaner, meaner grub that drops some of our favorite features. 00:00:26.455 --> 00:00:31.715 And then one of my favorite open source apps of all time is coming to an end. 00:00:32.295 --> 00:00:35.315 And what I'm going to do, my alternative, and what I'm switching to, 00:00:35.395 --> 00:00:36.115 tell you about that today. 00:00:36.435 --> 00:00:39.175 Then we'll round the show out with some great boosts, some picks, 00:00:39.375 --> 00:00:42.435 and a lot more. So before we get there, let's say time-appropriate greetings 00:00:42.435 --> 00:00:44.555 to our virtual lug. Hello, Mumble Room. 00:00:44.815 --> 00:00:47.595 Hey, Chris. Hey, Russ. And hello, Brent. Hello. 00:00:47.715 --> 00:00:47.895 Hello. 00:00:48.515 --> 00:00:51.895 Hello up there in the quiet listening. Always like having the Mumble Room. 00:00:51.915 --> 00:00:54.995 Here's our virtual lug every single Sunday. We get started with them... 00:00:55.806 --> 00:00:59.786 Quite a while before the show and hang out and talk and stuff like that. 00:01:00.006 --> 00:01:04.046 And you're always welcome. Jupyter Broadcasting dot com slash mumble for details on that. 00:01:04.366 --> 00:01:08.906 And say good morning to our friends at defined dot net slash unplugged. 00:01:08.966 --> 00:01:09.986 Go meet Define Networking. 00:01:10.226 --> 00:01:14.226 They have managed Nebula. And when you go to defined dot net slash unplugged, 00:01:14.246 --> 00:01:18.246 you'll get started with up to one handy host for free. No credit card required. 00:01:18.526 --> 00:01:23.146 And you can check out what we think is one of the absolute best mesh network 00:01:23.146 --> 00:01:27.246 in the world. We love the Nebula platform, and that's what Managed Nebula is 00:01:27.246 --> 00:01:28.226 from Defined Networking. 00:01:28.546 --> 00:01:33.546 It's a really strong contender. You can control the flexibility and discoverability 00:01:33.546 --> 00:01:38.206 of the network and the redundancy of the network, and their long-term story really shines. 00:01:38.726 --> 00:01:44.846 It's a much more, let's just say, reliable long-term story, especially when 00:01:44.846 --> 00:01:48.886 it comes to the 100 hosts for free, and they give you real control. 00:01:49.506 --> 00:01:54.486 And one of the things I love is I have found it to be surprisingly good just 00:01:54.486 --> 00:01:57.546 for a couple of machines that are doing direct-to-direct backup that I don't 00:01:57.546 --> 00:02:02.126 need a big tech login for. I don't need a key that expires every whatever days 00:02:02.126 --> 00:02:03.186 or any of that kind of stuff. 00:02:03.326 --> 00:02:05.066 I just need two machines to talk 00:02:05.066 --> 00:02:08.826 reliably to each other, and the entire infrastructure is between them. 00:02:09.146 --> 00:02:13.046 But then, of course, this was designed to manage Slack's global infrastructure 00:02:13.046 --> 00:02:18.006 back in 2017. So it hit the ground running for one of the most important data-sensitive 00:02:18.006 --> 00:02:22.106 companies in the world with one of the largest distributed backends in the world. 00:02:22.626 --> 00:02:27.506 Nebula is really incredible. And what's amazing is it's so light on the CPU 00:02:27.506 --> 00:02:28.746 and the networking, too. 00:02:28.886 --> 00:02:33.166 And they just recently introduced Always-On VPN mode for iOS and Android. 00:02:33.346 --> 00:02:38.546 So now your mobile devices can participate in what is the best mesh networking out there. 00:02:38.826 --> 00:02:43.146 So go check it out. Support the show. and free for 100 hosts. 00:02:43.406 --> 00:02:48.126 Define.net slash unplugged. That's Define.net slash unplugged. 00:02:48.226 --> 00:02:51.746 Go redefine your VPN experience today. Check out Nebula. See why we love it. 00:02:51.846 --> 00:02:56.686 See why we have been thrilled to have them as a sponsor and why we're deploying it on our systems. 00:02:59.755 --> 00:03:04.295 A quick mention, if you'd like to catch a very unplugged version of This Week 00:03:04.295 --> 00:03:10.775 in Bitcoin, This Week in Bitcoin episode 97 is an agent-friendly node management for 2026, 00:03:11.095 --> 00:03:14.835 where Brent and Wes both sat down with me for a special episode. 00:03:15.395 --> 00:03:18.115 So that's ThisWeekinBitcoin.show, and it's episode 97. 00:03:18.655 --> 00:03:20.155 I still have more node work to do. 00:03:20.255 --> 00:03:20.535 We do. 00:03:20.655 --> 00:03:21.375 That was a lot of fun, though. 00:03:21.815 --> 00:03:24.755 And then, just a reminder, LinuxFest Northwest, just around the corner, 00:03:24.935 --> 00:03:28.055 and we will have a live show. We'd love to see you there. We don't quite have 00:03:28.055 --> 00:03:29.255 all the details ironed out. 00:03:29.755 --> 00:03:34.355 But plans are already in the works, and I think it's going to be a really great event. 00:03:34.795 --> 00:03:39.835 And I'm really hoping we get the classic late April spring where it's just beautiful. 00:03:40.135 --> 00:03:42.915 Maybe you never know. Maybe if we did, maybe we'd do the episode outside. 00:03:43.095 --> 00:03:43.975 That could be a lot of fun. 00:03:44.635 --> 00:03:47.255 And we may have a hookup on speakers this year, too. I mean, 00:03:47.295 --> 00:03:50.575 not like people that speak, but speakers that we can put in the crowd so people 00:03:50.575 --> 00:03:53.955 can hear the show really well. How about that for getting fancy? 00:03:54.335 --> 00:03:55.235 Speakers for the speakers? 00:03:55.275 --> 00:03:59.535 I like that idea. We just need to prepare ourselves to implement it. 00:03:59.755 --> 00:04:00.995 Yeah, that's true. That's true. 00:04:04.335 --> 00:04:08.895 Big news this week. Canonical has announced big changes. 00:04:09.315 --> 00:04:13.335 Well, maybe you could call them minimal changes to Ubuntu 26.10's grub. 00:04:13.475 --> 00:04:16.595 They're calling it a minimal grub for secure boot. 00:04:16.855 --> 00:04:22.915 Their idea is to reduce the attack surface for grub and remove certain features 00:04:22.915 --> 00:04:24.455 that could be exploited. 00:04:24.995 --> 00:04:28.515 Some of those features are some of our favorite features. 00:04:28.755 --> 00:04:31.895 So, Wes, walk us through kind of the high level of this and then maybe we can 00:04:31.895 --> 00:04:33.575 get into what's getting removed. 00:04:33.575 --> 00:04:38.215 Yeah, well, we can talk about just sort of some of the stuff from the post itself. 00:04:38.395 --> 00:04:38.515 Yeah. 00:04:39.335 --> 00:04:43.975 Ubuntu Systems supports Secure Boot using Grub. And if you remember from, 00:04:44.675 --> 00:04:47.075 well, really the last, what, 10, 15 years? 00:04:47.315 --> 00:04:47.475 Yeah. 00:04:47.875 --> 00:04:53.615 Secure Boot is a new standard that came along with sort of our switch to UEFI booting of systems. 00:04:54.015 --> 00:04:58.675 And it provides ways to have the firmware have a set of cryptographic keys that 00:04:58.675 --> 00:05:02.935 it trusts and then verify that it's only going to boot into operating systems 00:05:02.935 --> 00:05:04.035 signed with those things. 00:05:04.355 --> 00:05:07.875 And on its own, as just that, as a primitive, like, that's one thing. 00:05:08.015 --> 00:05:11.275 It can be used for whatever, right? It's like a new tool that your computer can do. 00:05:11.555 --> 00:05:15.355 It can be very useful if you want to operate in a secure way and you want confidence that, like, 00:05:15.933 --> 00:05:19.133 Your machines only ever run code that you signed and no one else can, 00:05:19.253 --> 00:05:20.733 even if they have the hardware, can run stuff on it. 00:05:20.893 --> 00:05:24.193 So it's always made sense, like in the context of an important business laptop 00:05:24.193 --> 00:05:28.773 where you're out and about and you want to make sure your laptop hasn't been, you know, messed with. 00:05:28.973 --> 00:05:32.173 Or obviously in a data center where other people have access, things like that. 00:05:32.293 --> 00:05:35.893 And physical security is really important in these things because if somebody 00:05:35.893 --> 00:05:38.173 gets physical access, then they can essentially get root to the box. 00:05:38.233 --> 00:05:41.433 So you just want to verify that that chain is as secure as possible. 00:05:41.573 --> 00:05:42.873 I get that use case. All right. 00:05:43.033 --> 00:05:46.813 But of course, in the real world, what actually happened is also that Microsoft 00:05:46.813 --> 00:05:51.153 ended up being behind a lot of this and they wanted to push it out to like consumer laptops as well. 00:05:51.633 --> 00:05:53.613 And so you need some kind of key if you're going to do that, 00:05:53.673 --> 00:05:56.373 right? And you're going to want to run Windows and it's not an open source. 00:05:56.453 --> 00:05:57.873 Somebody has to sign it. Only Microsoft does that. 00:05:57.993 --> 00:05:58.073 Right? 00:05:58.333 --> 00:05:59.693 Yeah, Microsoft signs the key. 00:05:59.833 --> 00:06:02.353 And then it just worked out that it's not that you, in most situations, 00:06:02.453 --> 00:06:05.913 not all, in most situations, you can set up and enroll your own keys and sort 00:06:05.913 --> 00:06:07.213 of manage it as you would hope. 00:06:07.333 --> 00:06:09.633 That's not true for every single device, especially like Windows on ARM for 00:06:09.633 --> 00:06:10.733 a while, like all kinds of things. 00:06:10.733 --> 00:06:13.473 but it also means we live in a world where 00:06:13.473 --> 00:06:16.293 like if you want to just be able to have secure boot and boot 00:06:16.293 --> 00:06:19.073 a random iso on a random laptop you probably need it signed 00:06:19.073 --> 00:06:21.773 by that key and we have like a sort 00:06:21.773 --> 00:06:25.233 of complicated setup depending on the distro around like microsoft 00:06:25.233 --> 00:06:29.473 signs a tool called shim which then has its own set of signatures for various 00:06:29.473 --> 00:06:33.353 distros that then it has keys baked into that it trusts when it gets signed 00:06:33.353 --> 00:06:36.893 for like okay i can boot these ubuntu things right and then that's where like 00:06:36.893 --> 00:06:41.533 Ubuntu's system of assigned Grub2 comes in. And so that's where it's important 00:06:41.533 --> 00:06:42.633 to understand sort of the history. 00:06:42.773 --> 00:06:45.713 Like back in 2020, there was a vulnerability called boot hole. 00:06:45.953 --> 00:06:51.233 And this was actually a flaw where Grub had in parsing its own config that led to vulnerability. 00:06:51.833 --> 00:06:54.053 But the important part is like it just... 00:06:54.920 --> 00:06:59.540 It's a lot to deal with when that happens because you now need to go basically 00:06:59.540 --> 00:07:04.480 figure out how to like, you know, there's going to be old shims that trust vulnerable 00:07:04.480 --> 00:07:07.800 versions of Grub, but that are still trusted by the firmware. 00:07:08.040 --> 00:07:10.900 So if you want to do it properly, you have to get a new version of Grub that 00:07:10.900 --> 00:07:11.920 doesn't have the problem. 00:07:12.220 --> 00:07:16.260 Test that, make sure it's going to work everywhere, and then sign that, 00:07:16.420 --> 00:07:20.640 but with updated keys that aren't going to be trusted for the old ones, 00:07:20.720 --> 00:07:23.880 and then roll that up in the shim layer, and then coordinate with Microsoft 00:07:23.880 --> 00:07:26.380 to get the new version of the shim thing signed potentially. 00:07:26.680 --> 00:07:30.660 And then maybe even you need to go like add to the blacklist on the actual hardware 00:07:30.660 --> 00:07:33.420 things to say, you know, so it knows keys that it shouldn't trust anymore. 00:07:33.640 --> 00:07:35.600 And then you've got to get that pushed out to end users. 00:07:35.760 --> 00:07:35.880 Yeah. 00:07:36.080 --> 00:07:38.860 And they've got to do a successful update that's updating their bootloader. 00:07:38.960 --> 00:07:42.000 And then if you don't, then it just means sort of means like any old ISOs floating 00:07:42.000 --> 00:07:44.140 around are vulnerable and could have problems. 00:07:45.040 --> 00:07:47.520 And then there's potential attacks. I don't think this is the main concern necessarily, 00:07:47.640 --> 00:07:51.160 but like there are in theory some potential attacks where you could boot a Linux 00:07:51.160 --> 00:07:54.460 setup from like a vulnerable thing that let you then circumvent secure boot 00:07:54.460 --> 00:07:57.100 and use that to attack windows systems on the same laptop, 00:07:58.100 --> 00:08:01.960 so there's just a lot of sort of ecosystem implications that have happened in 00:08:01.960 --> 00:08:05.440 the past that i think they don't specifically mention that but i think there's 00:08:05.440 --> 00:08:07.120 a lot of that sort of history, 00:08:07.760 --> 00:08:11.860 behind this change so basically a bunch of supports grub for secure boot they 00:08:11.860 --> 00:08:17.340 use grub to boot things in 2610 they're proposing to remove the following features 00:08:17.340 --> 00:08:18.660 and if you've ever used grub you know that, 00:08:19.750 --> 00:08:24.010 It's existed long before the modern era of ESPs and UEFI and all that. 00:08:24.070 --> 00:08:25.350 So it supports a ton of different stuff. 00:08:25.490 --> 00:08:30.210 So they want to remove support for file systems for the slash boot drive. 00:08:30.390 --> 00:08:32.330 And actually, maybe it's worth talking about here too. 00:08:33.250 --> 00:08:37.510 Some Linux setups, they just have slash boot as like the ESP, the system partition. 00:08:37.910 --> 00:08:43.490 The EFI standard mandates like this VAT32 partition. And that's what the firmware interacts with. 00:08:43.870 --> 00:08:47.290 Linux often has its own sort of boot setup. And then so you have some setups 00:08:47.290 --> 00:08:51.150 that where you have the EFI system partition often mounted at slash boot EFI, 00:08:51.410 --> 00:08:55.270 but then you also have like a Linux boot partition that could be a different 00:08:55.270 --> 00:08:56.890 file system mounted at slash boot. 00:08:57.010 --> 00:09:00.330 And so you might have just the bare EFI stuff on the EFI partition, 00:09:00.330 --> 00:09:03.210 and then a lot more of the actual Linux boot stuff lives on the Linux side. 00:09:03.370 --> 00:09:09.690 That's how I do it. Is that how you do it? Well, I think boot EFI is its own thing if I'm using Grub. 00:09:09.850 --> 00:09:13.230 I almost use Grub almost on everything, except for like one system. 00:09:13.430 --> 00:09:15.290 See, I think I mostly use systemd boot. 00:09:15.290 --> 00:09:18.730 Brent, do you put it all under slash boot or do you break off boot slash EFI? 00:09:20.150 --> 00:09:24.830 Yes. I have so many systems that have like gone through our phases of, 00:09:25.010 --> 00:09:30.290 so these days it's like mostly systemd boot, but it's a little all over because I got systems all over. 00:09:30.510 --> 00:09:33.810 The reason I ask is because what I do, and I think this is going to impact me, 00:09:34.090 --> 00:09:36.270 is so slash boot EFI is FAT32. 00:09:37.315 --> 00:09:39.975 But Slash Boot, it's usually ButterFS. 00:09:40.235 --> 00:09:42.695 Right. And, you know, there's trade-offs like... 00:09:42.695 --> 00:09:44.795 And they're dropping ButterFS with this change. Like, we haven't gotten to that 00:09:44.795 --> 00:09:49.255 part. So I guess I interrupted you, but I just wanted to ask you that. 00:09:49.435 --> 00:09:53.335 So the changes here is happening at Slash Boot, but some people still have Slash 00:09:53.335 --> 00:09:54.795 Boot EFI, and there's that nuance there. 00:09:54.835 --> 00:09:56.555 Well, yeah, and you have to have the EFI partition. 00:09:56.735 --> 00:09:56.875 Yeah. 00:09:56.955 --> 00:09:58.195 The question is, do you, like... 00:09:58.195 --> 00:09:59.635 Make the whole thing FAT32 or... 00:09:59.635 --> 00:10:02.655 Right, and do you want to have stuff that exists on a separate Slash Boot? 00:10:02.795 --> 00:10:05.455 And, you know, there's a variety of different setups, and there's trade-offs, 00:10:05.555 --> 00:10:08.235 and, like, some ESPs are only so big, so you can only have so many generations 00:10:08.235 --> 00:10:12.075 of kernel and RAMFS, and there's a lot of variation here because Linux, right? 00:10:12.375 --> 00:10:16.135 So what they're proposing here in light of this because Grub supports a lot 00:10:16.135 --> 00:10:20.515 of stuff is for slash boot, they want to and basically this means removing it 00:10:20.515 --> 00:10:25.875 from signed Grub builds, and that's important here removing from signed Grub builds Okay. 00:10:25.875 --> 00:10:27.795 So on regular unsigned Grub builds? 00:10:28.575 --> 00:10:31.595 Yeah, you would still have access to these features Oh, okay, 00:10:32.175 --> 00:10:36.235 But remove ButterFS, HFS+, xfs 00:10:36.235 --> 00:10:40.135 and zfs retain ext4 00:10:40.135 --> 00:10:43.815 fat iso 9660 and squash 00:10:43.815 --> 00:10:46.895 fs also remove support for jpeg 00:10:46.895 --> 00:10:49.795 and png retain no support for images at 00:10:49.795 --> 00:10:54.995 all and then remove stuff for like i guess just remove support for apple partition 00:10:54.995 --> 00:10:58.295 tables which okay that seems reasonable i suppose in addition to these simpler 00:10:58.295 --> 00:11:01.755 changes we're also going to remove support for slash boot on complex partition 00:11:01.755 --> 00:11:07.475 setups such as lvm md raid except RAID 1 and Lux encrypted slash boot. 00:11:07.735 --> 00:11:11.655 These abilities were inherited by Debian but never tested in Ubuntu, 00:11:11.835 --> 00:11:15.355 and the Ubuntu installer always set up a bare ext4 partition. 00:11:15.715 --> 00:11:19.075 And then they sort of go into some of their reasoning here. As for encryption 00:11:19.075 --> 00:11:22.995 in particular, encryption of slash boot only provided security by obscurity, 00:11:23.235 --> 00:11:24.475 but not actual security. 00:11:24.695 --> 00:11:27.335 You want to ensure the integrity of those pieces. 00:11:27.695 --> 00:11:31.735 Our TPM FTE solution correctly implements integrity in the early boot stage, 00:11:31.735 --> 00:11:35.475 and we are committed to keep iterating and improve on it. 00:11:36.181 --> 00:11:39.321 Keep in mind these changes only affect slash boot. The file system, 00:11:39.421 --> 00:11:42.761 partition tables, Lux, LVM, RAID solutions continue working in the booted system. 00:11:42.901 --> 00:11:45.061 We are not removing them from the Linux kernel. 00:11:45.421 --> 00:11:48.761 Thank you, Wes. That was a really good breakdown. I think the biggest thing 00:11:48.761 --> 00:11:51.421 that's probably shocking here is the removal of Lux. 00:11:51.681 --> 00:11:56.561 I think most people can kind of understand reducing the file system scope, 00:11:56.601 --> 00:11:58.341 although I am sad to see Butter or Fesco. 00:11:58.501 --> 00:12:01.461 In particular, I think it's probably the least of the concerns here. 00:12:01.461 --> 00:12:05.821 And I think also distributions downstream are going to be really disappointed 00:12:05.821 --> 00:12:07.321 in the lack of image support. 00:12:07.741 --> 00:12:10.641 I've already seen some distributions talking about that. 00:12:11.461 --> 00:12:16.521 I will bring up just a friend of the show, Neil Gampa, was quick to comment 00:12:16.521 --> 00:12:20.621 in here, noting, suggesting, hey, can we please not drop ButterFS? 00:12:21.561 --> 00:12:25.661 It's a read-only file system driver that is actively supported by upstream developers. 00:12:25.801 --> 00:12:30.481 Users who want to leverage boot-to-snapshot setups with ButterFS need this support. 00:12:31.081 --> 00:12:31.681 That's exactly right. 00:12:31.881 --> 00:12:35.241 So there's some nuance here too. And then ZFS users are sort of bringing stuff up. 00:12:35.361 --> 00:12:39.501 Like there's the question of, is the obligation to sort of support this around 00:12:39.501 --> 00:12:43.541 what just the Ubuntu installer did or the wider array of setups people have 00:12:43.541 --> 00:12:49.061 crafted around running even secure boot Ubuntu on different disk configurations in the wild? 00:12:49.361 --> 00:12:52.981 I wouldn't be surprised if they have to walk the Lux decision back. 00:12:53.241 --> 00:12:57.201 I grant that they are saying that encryption of slash boot only provides security 00:12:57.201 --> 00:13:02.201 by obscurity, but not actual security. There's one other thing that Encrypted 00:13:02.201 --> 00:13:06.261 Lux provides that they didn't mention in that paragraph, and that's corporate compliance. 00:13:06.681 --> 00:13:12.081 And there's not a lot of nuance in a corporate policy that requires your entire 00:13:12.081 --> 00:13:15.181 laptop hard drive be encrypted. 00:13:15.421 --> 00:13:19.321 They don't generally allow for, well, your entire laptop should be encrypted 00:13:19.321 --> 00:13:21.081 except for your boot partition. 00:13:21.681 --> 00:13:23.941 That's not generally how the corporate policies are structured. 00:13:23.941 --> 00:13:28.561 And so I wouldn't be too surprised if the feedback from enterprise customers 00:13:28.561 --> 00:13:31.841 is, sorry, chief, but we've got to have luck. 00:13:32.101 --> 00:13:35.621 Even on Windows, you have the ESP can't be encrypted. 00:13:35.941 --> 00:13:36.221 Yeah, yeah. 00:13:37.414 --> 00:13:40.534 But I would still, I think they would still argue that there's value in having 00:13:40.534 --> 00:13:42.214 like the kernel images and all. I'm not saying. 00:13:42.334 --> 00:13:42.894 Yeah, fair enough. 00:13:43.094 --> 00:13:43.434 I'm not saying. 00:13:43.554 --> 00:13:47.054 There's often compliance drag and yeah, it takes a long time to get stuff updated. 00:13:47.114 --> 00:13:50.274 I think the analysis is technically true that it's security through obscurity, 00:13:50.434 --> 00:13:54.454 especially when you have their TPM backed solution for verifying all the other 00:13:54.454 --> 00:13:55.414 aspects of the boot chain. 00:13:55.534 --> 00:13:59.774 So when you have all other things being true, it is security through obscurity. 00:13:59.954 --> 00:14:02.534 But I don't think corporations are really thinking about it that hard. 00:14:02.654 --> 00:14:05.834 Yeah, that's fair. and it has to be what their auditors are willing to and that 00:14:05.834 --> 00:14:07.614 their standards already exist and support. 00:14:07.794 --> 00:14:11.994 That's the thing. But this is something they're working out now because this 00:14:11.994 --> 00:14:13.894 is going to be after the next LTS. 00:14:14.214 --> 00:14:17.174 So this is something they've got to figure out. They're going to have some time. 00:14:17.394 --> 00:14:19.254 This is an interim release where this would be landing. 00:14:19.474 --> 00:14:21.454 Yeah, it does seem like they've done some thinking too on that, 00:14:21.494 --> 00:14:24.714 like when they wanted this timing in terms of LTS releases and where they sort 00:14:24.714 --> 00:14:26.454 of strand people if there was a problem. 00:14:27.274 --> 00:14:32.274 So, you know, credit there at least. I think they thought it could be contentious 00:14:32.274 --> 00:14:38.554 and are attempting to engage with that thoughtfully, what the reception's like, how it goes, TBD. 00:14:38.774 --> 00:14:42.874 I saw some strong reactions to the lack of ZFS support too, just because people 00:14:42.874 --> 00:14:44.394 kind of went all in on that in some cases. 00:14:44.894 --> 00:14:46.794 That's what I saw on Reddit is people were like, what, what, 00:14:46.854 --> 00:14:49.974 wait, hey, I thought this was the distro I could use ZFS with, 00:14:50.054 --> 00:14:52.534 so I even made my boot ZFS, and I saw that a few times. 00:14:52.694 --> 00:14:57.654 I know, right? People do the bootstrap sort of arch install style to get pretty 00:14:57.654 --> 00:15:00.254 nice Ubuntu setups on ZFS. 00:15:00.254 --> 00:15:06.134 Um brent my one concern to be here and this is not really a big deal but couldn't 00:15:06.134 --> 00:15:09.314 you see like the internet guy hot take on this being that well ubuntu isn't 00:15:09.314 --> 00:15:12.474 the distro if you want to if you want to use encryption or ubuntu you don't 00:15:12.474 --> 00:15:15.074 want to use ubuntu because they don't let you fully encrypt your hard drive 00:15:15.074 --> 00:15:17.534 don't there could be narratives that come out of this kind of thing. 00:15:17.534 --> 00:15:24.494 Yeah at the same time ubuntu makes it arguably one of the easiest to encrypt your stuff so um, 00:15:26.196 --> 00:15:31.596 It's tricky. I would say my initial reactions was like the first one was emotional. 00:15:31.776 --> 00:15:33.476 Like, don't touch my grub, man. 00:15:33.716 --> 00:15:38.796 But I can see how they're coming at this as they describe from like a security posture point of view. 00:15:39.616 --> 00:15:44.216 And someone has to make those tough decisions. And like, we've seen many challenges 00:15:44.216 --> 00:15:49.756 with including images like JPEGs and things like that, that do get compromised quite often. 00:15:49.756 --> 00:15:52.696 so I could see how there 00:15:52.696 --> 00:15:55.456 was probably a lot of difficult conversations about what do we 00:15:55.456 --> 00:15:58.336 include what do we leave in here what do we take out what's a 00:15:58.336 --> 00:16:04.896 realistic expectation for the permutations of the whole boot sequence and how 00:16:04.896 --> 00:16:10.456 much they get used in the wild I don't envy them in making those choices and 00:16:10.456 --> 00:16:14.516 there's going to be backlash for sure but it might change the future of how 00:16:14.516 --> 00:16:17.176 we do things which maybe might be better and. 00:16:17.176 --> 00:16:21.196 To Wes's point I think they're like I am the things I'm the most sour about 00:16:21.196 --> 00:16:25.616 is the image removal butter fast removal and Lux although personally Lux isn't 00:16:25.616 --> 00:16:28.696 a big deal for me but I just think that's gonna be contentious the biggest one 00:16:28.696 --> 00:16:31.856 for me is butter fs obviously because I that's what I use for my boots, 00:16:33.317 --> 00:16:37.237 I think the thing that we have to keep in mind when we're evaluating this decision 00:16:37.237 --> 00:16:43.237 is the point Wes made earlier on is that the mechanisms that we have today to 00:16:43.237 --> 00:16:49.497 update grub in this entire stack when something does go wrong are pretty inadequate and pretty rough. 00:16:49.717 --> 00:16:55.417 And so the cost of fixing something once it's out in production in an LTS is very high. 00:16:55.537 --> 00:16:59.157 And so if you can minimize that attack surface today before it's in production, 00:16:59.417 --> 00:17:00.817 you reduce that future cost. 00:17:00.817 --> 00:17:04.537 And you know there are like you know other thing people are using system d boot 00:17:04.537 --> 00:17:08.137 for a lot of things you're also seeing a lot of systems use uk eyes which is 00:17:08.137 --> 00:17:12.937 where you roll like the kernel and the inner mfs into a single pe efi style 00:17:12.937 --> 00:17:17.197 executable and sign the whole thing yeah right so this is sort of like a transitionary 00:17:17.197 --> 00:17:19.477 step and i think they're to some extent trying to like, 00:17:20.197 --> 00:17:24.737 limit complexity so maintain grub support and for the unsigned stuff full like 00:17:24.737 --> 00:17:28.297 you know all the stuff without having to like swap to hey efi systems we're 00:17:28.297 --> 00:17:30.957 only going to support system d boot going forward or that would probably be. 00:17:30.957 --> 00:17:33.457 Maybe more controversial i'm not sure yeah. 00:17:33.457 --> 00:17:40.017 Well the natural question becomes are there workarounds to this and what should 00:17:40.017 --> 00:17:43.817 we be looking to implement in the future because like some grub installs i feel 00:17:43.817 --> 00:17:48.577 like are they i don't know they just feel deprecated whenever i do them so what's 00:17:48.577 --> 00:17:50.897 the better way what's the way to the future. 00:17:53.298 --> 00:17:55.558 Yeah, I would ask the audience right now, how are you booting? 00:17:55.758 --> 00:17:58.138 I bet the majority of them are using Grub. 00:17:58.858 --> 00:17:59.738 Yeah, probably, huh? 00:17:59.898 --> 00:18:04.138 I think so. And I'm wondering if any of them are even using assigned bootloader or secure boot. 00:18:04.298 --> 00:18:05.578 Yeah, good question. How many are? 00:18:05.978 --> 00:18:09.358 Or how many should be. Now I'm feeling like I could do it better. 00:18:09.778 --> 00:18:13.018 And does this make you want to move to systemd boot if you want Lux and ButterFS 00:18:13.018 --> 00:18:15.398 on your slash boot? Because I think that's the direction I'm going to go if 00:18:15.398 --> 00:18:16.618 I were on Ubuntu system, at least. 00:18:16.638 --> 00:18:18.378 So you don't get that with systemd boot? 00:18:18.378 --> 00:18:19.598 What? I thought I got ButterFS. 00:18:20.318 --> 00:18:22.678 So it's the whole point of the slash boot. 00:18:22.678 --> 00:18:25.098 Yeah. I don't get ButterFS with Systemd boot? 00:18:25.118 --> 00:18:28.198 Well, Systemd just works with the ESP. It's meant as a simpler, 00:18:28.378 --> 00:18:29.938 right? It's whole thing is just to let you... 00:18:29.938 --> 00:18:32.978 Well, I'm always going to have that be FAT32. Because thanks, 00:18:33.198 --> 00:18:36.558 world. That's what I have now, right? But my slash boot... 00:18:37.198 --> 00:18:39.878 You're saying my slash boot with Systemd boot can't be ButterFS? 00:18:40.138 --> 00:18:42.758 Well, Systemd doesn't have any file system support at all. 00:18:42.858 --> 00:18:43.858 I'm at it! Oh, okay. 00:18:44.418 --> 00:18:49.058 Like, it's just meant to be itself an EFI thing that lets you boot other EFI executables. 00:18:49.258 --> 00:18:49.438 Okay. 00:18:49.818 --> 00:18:52.178 So that's where, like, that's where maintaining Grub support. 00:18:52.178 --> 00:18:56.738 you could of course also you know like go through and have a setup where you've 00:18:56.738 --> 00:19:00.658 signed all this stuff yourself from your own role sorry. 00:19:00.658 --> 00:19:01.738 Yeah no totally yeah. 00:19:01.738 --> 00:19:04.278 I just don't know how easy or automated that is right so that's what essentially 00:19:04.278 --> 00:19:07.678 what i'm doing with this laptop on nix os it's just that there was an easy nix 00:19:07.678 --> 00:19:11.278 os setup to do that i don't know what the plumbing is like on a bunch of system 00:19:11.278 --> 00:19:14.378 if you did want to do that yourself i mean it's definitely possible it's just 00:19:14.378 --> 00:19:17.498 a question of like how painful is it and how much nobody's. 00:19:17.498 --> 00:19:20.878 Doing that right i mean not at scale Nobody's doing it. Corporations might be, 00:19:20.978 --> 00:19:23.298 but like nobody, no. Right? Except for you. 00:19:23.858 --> 00:19:29.838 Well, you know, the intersection of very security professionals who use desktop Linux, perhaps. 00:19:29.958 --> 00:19:32.738 Yeah, maybe. All right. Well, boost in and let us know because we've got some 00:19:32.738 --> 00:19:35.798 questions about this one. This seems like a high impact one. Yeah. 00:19:35.938 --> 00:19:38.498 I want to get a West prescription for what the rest of us should be doing. 00:19:39.898 --> 00:19:42.358 I don't know if they're, I mean, you have to have a, what's your goal? 00:19:42.538 --> 00:19:44.138 It's good. Yeah. You know what he's going to say. It depends. 00:19:44.278 --> 00:19:44.818 Yeah, I know. 00:19:46.218 --> 00:19:48.658 You should run Nix OS and then problem solved. 00:19:49.538 --> 00:19:50.878 Ha ha ha ha ha ha ha ha ha ha ha. 00:19:53.551 --> 00:19:57.331 Thank you to our members. You know, we are running lean these days. 00:19:57.791 --> 00:20:00.651 And if we hadn't set up the membership program and had people support us, 00:20:00.751 --> 00:20:02.071 we wouldn't have a show right now. 00:20:02.791 --> 00:20:05.871 And we really do appreciate it. It's an opportunity to get in there and keep 00:20:05.871 --> 00:20:07.411 us going while we transition. 00:20:07.871 --> 00:20:11.011 Really, where we're at now is we fought the good fight for a very, 00:20:11.111 --> 00:20:13.271 very long time. And we were able to do so because of our members. 00:20:13.471 --> 00:20:16.171 And now we have to adapt the business strategy a bit. And while we make that 00:20:16.171 --> 00:20:19.331 transition, the show survives through the memberships and the boosts. 00:20:19.531 --> 00:20:23.331 So thank you very much. You can go to linuxonplugged.com membership to support this show directly. 00:20:24.031 --> 00:20:26.971 Or if you want to support all the shows on the network, jupiter.party, 00:20:26.971 --> 00:20:30.131 and you get special access for all the shows. 00:20:30.251 --> 00:20:33.291 So that's linuxunplugged.com slash membership or jupiter.party. 00:20:33.531 --> 00:20:36.971 Thank you very much for your support. Or send us a boost and support each episode. 00:20:37.591 --> 00:20:40.811 And, you know, we'll read your message if it's above 2,000 cents. 00:20:41.011 --> 00:20:45.151 And we have a good time. And I appreciate you. Thank you very much. 00:20:48.510 --> 00:20:51.890 Well, Chris, as usual, when I was visiting at the farm and at the studio, 00:20:52.070 --> 00:20:55.990 we watched a heck of a lot of our favorite TV on your favorite project. 00:20:56.810 --> 00:20:59.690 But you kind of teased that that might be going away. 00:21:00.730 --> 00:21:04.390 This is this is sad, guys. You know, you get you get really, 00:21:04.570 --> 00:21:06.250 really happy with a piece of software. 00:21:06.710 --> 00:21:09.810 You get the whole family using it, which is not often a thing that happens. 00:21:09.950 --> 00:21:10.790 It's quite the rollout. 00:21:11.130 --> 00:21:15.290 Yeah. And then the developer burns out and he says it's time to move on. 00:21:15.550 --> 00:21:18.190 And this happened this week with ersatz TV. 00:21:19.070 --> 00:21:23.590 ersatz tv is such a full force multiplier if you have jellyfin or plex because 00:21:23.590 --> 00:21:28.890 it gives you the ability to set up your own live tv's channels and stations and it's so much fun. 00:21:28.890 --> 00:21:31.630 It's essentially like discoverability on top of your collection. 00:21:31.630 --> 00:21:36.110 Yeah it's like having your own private pluto tv and what i have star trek channels 00:21:36.110 --> 00:21:40.250 and bob's burgers and game shows and one of the things we'll do is we'll watch 00:21:40.250 --> 00:21:43.250 a tv show like say cheers and then when we're done we'll put it into a random 00:21:43.250 --> 00:21:46.090 rotation in ersatz tv and you'll just have a cheers channel you can tune into 00:21:46.090 --> 00:21:48.390 and while brend and I were working on the diesel heater. 00:21:48.530 --> 00:21:51.850 We'd have the start, one of the Star Trek channels. We're always going and it just plays. 00:21:52.450 --> 00:21:56.630 And I got, cause TNG is the best. I got one dedicated to TNG and then the other 00:21:56.630 --> 00:22:00.410 Star Trek channel biases DS nine. Cause let's be honest, DS nine is really good. 00:22:00.610 --> 00:22:03.410 So like I got DS nine, but then I got all the other tracks in there too. 00:22:03.530 --> 00:22:04.510 Well, the original tracks. 00:22:04.550 --> 00:22:09.610 You have like a second tier Trek like shows channel as well. I learned a lot. 00:22:09.690 --> 00:22:12.970 Yeah, it's good. It's, it's, it's been, I 00:22:12.970 --> 00:22:16.110 cannot describe to you the delight I have in the most like 00:22:16.110 --> 00:22:19.050 basic because you get a TV guide you get 00:22:19.050 --> 00:22:21.870 you get this live TV experience you can't 00:22:21.870 --> 00:22:24.630 rewind people say can you play that back nope can't play 00:22:24.630 --> 00:22:30.130 that back it's live it's broadcast yeah so great I know it doesn't sound it 00:22:30.130 --> 00:22:32.530 doesn't sound like one of these things that has been a continuous source of 00:22:32.530 --> 00:22:35.690 joy but I don't know what am I a year into this thing and I still just absolutely 00:22:35.690 --> 00:22:40.630 absolutely love it so grateful that the developer made it and he said in his 00:22:40.630 --> 00:22:44.530 wrap up he said it's time to announce the final release of ersatz TV in its current form, 00:22:45.327 --> 00:22:47.907 The existing repositories will be archived following this update. 00:22:48.247 --> 00:22:52.547 The project scope expanded beyond what was personally useful or sustainable 00:22:52.547 --> 00:22:56.567 to maintain in my free time. For now, I plan to step away in the future. 00:22:56.667 --> 00:23:00.207 I hope to reboot the project with significantly reduced and more focused scope. 00:23:00.307 --> 00:23:02.447 And they're also welcoming forks in the meantime. 00:23:02.747 --> 00:23:05.267 Yeah, that was quite devastating when we got the news. 00:23:05.387 --> 00:23:08.027 Yeah, I was legit sad. I was legit sad. 00:23:08.267 --> 00:23:10.607 I mean, it doesn't mean it's useless right away, right? It's still, 00:23:10.707 --> 00:23:13.127 it's open source, so it doesn't go away. You can still run it. 00:23:13.347 --> 00:23:13.947 I am, yeah. 00:23:14.627 --> 00:23:18.027 It's just you don't know what the maintenance will be like and if forks will 00:23:18.027 --> 00:23:21.987 develop and will it slowly decay and not support newer things and yeah. 00:23:22.227 --> 00:23:25.807 One begins to think perhaps it's time to start looking for an alternative. 00:23:26.407 --> 00:23:30.687 And so where the free software world closes a door, it opens a window. 00:23:31.047 --> 00:23:33.847 And we now have Tunar, which has been around for a little bit. 00:23:34.207 --> 00:23:38.947 And it's very similar to ersatz TV with a, I'd say actually a little nicer interface 00:23:38.947 --> 00:23:42.827 if I'm being honest with you. It allows you to create live TV channels from 00:23:42.827 --> 00:23:46.167 Plex, Jellyfin, MB, or just local files on your disk. 00:23:46.587 --> 00:23:49.447 It lets you build a custom TV channel out of your existing media. 00:23:49.667 --> 00:23:54.987 And then you can add the ability to spoof an HD home runner to it with a checkbox. 00:23:55.147 --> 00:23:59.767 And then it shows up automatically to Plex and Jellyfin or MB as a live network 00:23:59.767 --> 00:24:02.887 TV tuner. And then you can just pull in live TV into your Plex or Jellyfin. 00:24:03.595 --> 00:24:08.715 And then it gives you a drag and drop lineup editor. And they have this idea. 00:24:08.835 --> 00:24:09.495 Oh, that's nice. 00:24:09.695 --> 00:24:14.215 Yeah, it's nice. It is a really nice UI. They have this idea of sort of flex 00:24:14.215 --> 00:24:15.695 content or filler content. 00:24:16.395 --> 00:24:20.435 And you can have the thing round an hour out of programming by filling in content. 00:24:20.715 --> 00:24:24.335 So I went on archive.org and I got, I did this a little while ago. 00:24:24.395 --> 00:24:26.295 I got a bunch of 80s and 90s commercials. 00:24:26.795 --> 00:24:30.055 And then it knows the length of the commercials. So it knows which ones it can 00:24:30.055 --> 00:24:33.175 slot in. And then you can set rules on how often it replays the same commercials. 00:24:33.755 --> 00:24:38.475 and so on one of my channels when you tune in it fills out so the shows actually 00:24:38.475 --> 00:24:41.935 start and end on the hour and half hour block it's really cool does. 00:24:41.935 --> 00:24:42.875 It cut in the commercials. 00:24:42.875 --> 00:24:47.375 Or just afterwards after between you could actually have it sort of try to dynamically 00:24:47.375 --> 00:24:50.795 insert them but i just feel like that's going to be a disaster and so it's just 00:24:50.795 --> 00:24:54.895 at the in-between episodes it plays a couple of commercials from like the 80s or 90s. 00:24:54.895 --> 00:24:59.155 It'd be great if you could like index your jellyfin setup to pre-find those 00:24:59.155 --> 00:25:00.975 slots and then like surface them. 00:25:00.975 --> 00:25:03.075 Maybe this is too. 00:25:03.075 --> 00:25:04.495 Much work to insert fake ads but. 00:25:04.495 --> 00:25:07.395 It kind of does in a way when it does that when it does the tv guide it's kind 00:25:07.395 --> 00:25:08.955 of what it's doing you know because. 00:25:08.955 --> 00:25:12.015 As a kid did you ever think you could have your own uh cable network. 00:25:12.015 --> 00:25:17.655 Just no it's a lot of fun it is i it is silly i spent a lot of time trying to 00:25:17.655 --> 00:25:24.335 get um hardware transcoding working which is always a thing and uh i didn't quite like. 00:25:24.335 --> 00:25:25.435 A quick sync system. 00:25:25.435 --> 00:25:26.055 Or NVIDIA. 00:25:26.215 --> 00:25:26.275 Okay. 00:25:26.395 --> 00:25:31.315 Yeah, it's on my H-Droid H3+, which is using QuickSync. 00:25:31.515 --> 00:25:37.635 And both Tuner and EarthSats TV have hardware encoding and decoding support. 00:25:38.616 --> 00:25:42.016 However, Tunar is trying to be a little extra clever. 00:25:42.196 --> 00:25:45.936 And so, of course, I had to hit a very specific bug, probably because Brent 00:25:45.936 --> 00:25:47.176 was over when I was setting this up. 00:25:47.356 --> 00:25:47.816 You're welcome. 00:25:47.896 --> 00:25:54.496 So I've got the H3 Plus, and it's an Intel low-power CPU with its own version of QuickSync. 00:25:54.896 --> 00:26:00.956 And I'm watching my high-resolution 10-bit HVAC custom-ripped Blu-ray TNG, 00:26:01.356 --> 00:26:03.996 like, you know, 14 megabit files. 00:26:04.956 --> 00:26:06.396 That's a good stress test, huh? 00:26:06.456 --> 00:26:11.436 It is. Yeah, it is. And poor computer where ersatz could actually use quick 00:26:11.436 --> 00:26:13.096 sync and decode these files. 00:26:13.436 --> 00:26:16.776 Tuner was unable to, and this is an interesting test because it was same source 00:26:16.776 --> 00:26:21.076 file, same network clients and playback client, all of everything, 00:26:21.276 --> 00:26:22.756 just ersatz versus tuner. 00:26:23.176 --> 00:26:26.976 And what I discovered is that it wasn't a GPU or a driver problem, 00:26:26.996 --> 00:26:28.876 but it was actually the transcode pipeline. 00:26:29.536 --> 00:26:33.796 ersatz was doing a much simpler filter pipeline and didn't have to pass between 00:26:33.796 --> 00:26:35.336 hardware and software renders to do it. 00:26:35.336 --> 00:26:41.876 where TUNAR was trying to be a little fancier and was having to flip between hardware decode, 00:26:42.196 --> 00:26:46.816 hardware scale, and then software to get back to the right point and then do 00:26:46.816 --> 00:26:50.436 some color space normalization in software and then re-encode in hardware. 00:26:50.796 --> 00:26:56.356 And that popping in and out of hardware and software encode back and forth on 00:26:56.356 --> 00:27:01.616 my particular quick sync device with these crazy large TNG files hit the bug. 00:27:01.796 --> 00:27:05.456 And so I can't actually use TUNAR to watch my Star Trek. 00:27:06.436 --> 00:27:09.236 Of all the things. Of all the things, boys. 00:27:09.396 --> 00:27:12.476 Does it work if you didn't hardware offload? 00:27:12.636 --> 00:27:14.336 Yes, but then my little Odroid. 00:27:14.516 --> 00:27:16.236 Right, I'm not saying you want to. I'm just kind of curious. 00:27:16.456 --> 00:27:19.576 Yeah, yeah, it does. But then the Odroid's basically useless because it's just 00:27:19.576 --> 00:27:24.416 doing that. So bottom line, ersatz just has a cleaner, simpler FFmpeg pipeline. 00:27:24.956 --> 00:27:31.076 And so it was handling these 10-bit HVAC files where TUNAR was just trying to be a little more fancy. 00:27:31.516 --> 00:27:32.776 Is this a known issue, I wonder? 00:27:33.236 --> 00:27:34.476 I don't know if it's known actually, 00:27:35.372 --> 00:27:35.692 Yeah. 00:27:35.832 --> 00:27:39.032 Might be worth importing. Maybe you can get yourself, if this is going to be your future. 00:27:39.232 --> 00:27:43.632 It's a lot of edge cases, you know, because it's special high encoded Star Trek. 00:27:44.272 --> 00:27:47.672 Oh, Droid H3 using quick sync. I don't know. 00:27:47.672 --> 00:27:50.912 It'd be interesting to point, maybe a bot at the code base just to see what 00:27:50.912 --> 00:27:53.212 the, like compare the graph building sort of stuff. Maybe there's, 00:27:53.312 --> 00:27:55.092 maybe there's some future improvements. 00:27:55.232 --> 00:27:56.192 I said the same thing. 00:27:56.512 --> 00:27:57.572 So here's what I did. 00:27:57.732 --> 00:27:58.372 See, I like you, Brent. 00:27:59.552 --> 00:28:04.172 Because, you know, I got to have my Star Trek, but I got to start migrating offer sets. 00:28:05.072 --> 00:28:09.152 So this was not enough to say I'm not going to use Tunar. So you're using Tunar. 00:28:10.192 --> 00:28:13.692 But you're also not going to, I see what you mean. You're not going to not have Star Trek. 00:28:13.832 --> 00:28:17.552 What's a guy supposed to do? Do you stay with the Dying Project? 00:28:18.372 --> 00:28:22.012 God bless. Or do you half migrate? 00:28:22.992 --> 00:28:26.292 So, and I don't know, I almost never do this, but I did the half migrate. 00:28:26.512 --> 00:28:31.472 So I moved all the other TV channels to Tunar and I left the Star Trek channels on ersatz, 00:28:32.699 --> 00:28:34.739 Which is starting to get complicated now. Okay, boys. 00:28:35.699 --> 00:28:36.919 System D, Star Trek D. 00:28:37.039 --> 00:28:39.719 So what do you do when you got two competing standards? 00:28:40.519 --> 00:28:41.179 Use both. 00:28:41.399 --> 00:28:45.679 You create a new standard, Wes. That's what you do. So I then brought in Dispatcher, 00:28:45.839 --> 00:28:48.539 a third service. Remember Dispatcher? 00:28:48.699 --> 00:28:48.979 Yeah. 00:28:49.299 --> 00:28:55.479 Yeah, buddy. Dispatcher is an open source powerhouse for managing all IPTV streams. 00:28:55.599 --> 00:29:01.759 Oh, my goodness. Program channel data, on-demand video. And so I have probably 00:29:01.759 --> 00:29:03.479 like 100 IPTV channels in there. 00:29:03.579 --> 00:29:07.819 And so what I decided to do was consolidate all the ersatz and tunar from two 00:29:07.819 --> 00:29:09.679 different sources into Dispatcher. 00:29:09.799 --> 00:29:15.039 So Dispatcher brings them both together and then presents one TV guide to the IPTV client. 00:29:15.219 --> 00:29:18.439 So the client is totally unaware what server is feeding. 00:29:18.439 --> 00:29:18.619 That's pretty great. 00:29:18.899 --> 00:29:24.079 It works. It works. It's a weird stack, but it works really well. 00:29:24.259 --> 00:29:25.739 And Dispatcher is great software. 00:29:26.099 --> 00:29:30.719 And I have all my favorite IPTV channels in there. Plus now I have my own in their own section. 00:29:31.119 --> 00:29:34.519 It really is a lot cleaner than how I was doing it before. And I have groups and categories. 00:29:35.859 --> 00:29:40.939 It's better. I mean, on the back end, it's more, but on the front end, you wouldn't even know. 00:29:41.279 --> 00:29:41.559 Yeah. 00:29:41.699 --> 00:29:46.179 That's the, that's the great thing. But, uh, it's, it's this weird transition 00:29:46.179 --> 00:29:51.239 now because I actually think the solution is going to be me replacing my H droid. 00:29:51.739 --> 00:29:53.879 Uh, that would be interesting. Yeah. 00:29:53.979 --> 00:29:57.439 I think that's the solution is to get a higher end quick sync or some other. 00:29:57.439 --> 00:30:01.479 You should try that on another Quicksync box, too, just to see if you can get a source file. 00:30:01.859 --> 00:30:05.139 The only reason you're convincing yourself you need new hardware is because 00:30:05.139 --> 00:30:09.899 your TNG is encoded at ridiculous levels, right? You realize that? 00:30:09.939 --> 00:30:13.159 You mean my TNG is future-proofed and looks beautiful? Is that what you mean? 00:30:13.299 --> 00:30:15.459 You want to respect the film scans they did, Brent. 00:30:15.719 --> 00:30:16.919 You want to respect TNG. 00:30:17.339 --> 00:30:17.939 Well, that, too. 00:30:18.079 --> 00:30:20.899 I mean, like, a guy doesn't want to re-encode it every decade anymore. 00:30:20.899 --> 00:30:24.259 He's kind of done doing that. So I went, I got the Blu-rays, 00:30:24.619 --> 00:30:27.599 and some of the DVDs. I'll tell you what. I mean, just as an aside, 00:30:28.479 --> 00:30:31.839 sometimes, especially with Deep Space Nine, and some of these, the DVDs are actually, 00:30:32.940 --> 00:30:35.660 better quality than the blu-ray so you 00:30:35.660 --> 00:30:39.120 got to pick and choose i mean i picked and choose i'm picky with my star trek uh 00:30:39.120 --> 00:30:41.880 i really though i i want to just relay a couple things before i 00:30:41.880 --> 00:30:44.820 wrap this up i'm going to put links to 00:30:44.820 --> 00:30:47.820 this stuff dispatcher tunar ersatz in the show notes but 00:30:47.820 --> 00:30:51.940 i also want you to go play around with the awesome iptv list in the in the show 00:30:51.940 --> 00:30:55.660 notes i've mentioned this once before on the show and i don't normally do this 00:30:55.660 --> 00:30:58.560 unless it's something i really really think is great and so i'm mentioning it 00:30:58.560 --> 00:31:02.100 again you can play around with this at any level just I just want a web-based 00:31:02.100 --> 00:31:05.740 app to desktop applications to full host services like I'm doing. 00:31:06.620 --> 00:31:10.660 At the end of the day, there's a lot of good legal content out there that you 00:31:10.660 --> 00:31:12.060 can watch absolutely for free. 00:31:12.120 --> 00:31:15.220 And there's a lot of really good open source apps to play it in. 00:31:15.340 --> 00:31:17.740 What I've done is I've stacked a couple of things together. 00:31:17.900 --> 00:31:21.820 So just as a recap, what you have is a simpler version of this is Tunar. 00:31:22.700 --> 00:31:24.600 Tunar could feed directly into Jellyfin. 00:31:25.676 --> 00:31:28.536 You don't need all this other stuff. If you don't have these crazy files like 00:31:28.536 --> 00:31:31.896 I have, T-U-N-A-R-R, get yourself Tunar, 00:31:32.556 --> 00:31:37.056 and point it at your existing Plex or Jellyfin, and then your existing Plex 00:31:37.056 --> 00:31:41.876 or Jellyfin will see it show up as an HD Home Run network box, 00:31:42.436 --> 00:31:45.936 and you'll be able to stream your shows like a classic TV show, 00:31:46.096 --> 00:31:49.376 like a classic cable channel, whatever it might be, with a TV guide where you 00:31:49.376 --> 00:31:51.576 can see what's playing, and I think you'll find it quite delightful. 00:31:51.796 --> 00:31:54.996 It doesn't have to be a very complicated stack. I've gone kind of hardcore here 00:31:54.996 --> 00:31:58.936 because of my setup, but it's really just Tuner, Jellyfin, and Plex, 00:31:59.176 --> 00:32:00.676 and that's the entire stack. 00:32:00.876 --> 00:32:05.096 And then you can add on to that as you like. You could add Dispatcher with lots of IPTV if you wanted to. 00:32:05.436 --> 00:32:08.156 But I really want to encourage you to get started with this because it is a 00:32:08.156 --> 00:32:10.716 great gateway drug into self-hosting. 00:32:10.876 --> 00:32:12.896 And what you'll find is once you get something like this running, 00:32:13.076 --> 00:32:18.496 you're off to the races when it comes to a Sovereign stack. You will find it's 00:32:18.496 --> 00:32:24.636 a very, very fun, and it becomes just the first thing, and then from there it just takes off. 00:32:24.756 --> 00:32:30.796 If you want more info on some of the IPTV-specific stuff, that's in Linux Unplugged 645. 00:32:31.316 --> 00:32:35.736 I also imagine, Wes, you might have gone sneaky spelunking like I may have, 00:32:35.776 --> 00:32:42.316 but Chris, if you look around, you can find under the ersatz.tv GitHub organization 00:32:42.316 --> 00:32:44.836 something simply called Next. 00:32:45.756 --> 00:32:51.856 And it says, ersatz.tv next. This is an experiment and not intended for use by anyone at this point. 00:32:52.656 --> 00:32:57.136 Soon, trademark. And the last commit was 31 minutes ago. 00:32:57.436 --> 00:33:02.016 So keep your eye out. And it's written in 100% Rust. 00:33:03.648 --> 00:33:08.428 So I noticed that like the first commit was two weeks ago. So this has been cooking for a minute. 00:33:09.608 --> 00:33:13.728 MIT licensed cargo. Yeah. It's all right. It's a rust for sure. Huh? 00:33:14.468 --> 00:33:17.848 Yeah. I'm, you know, this is very early. There's nothing here yet other than 00:33:17.848 --> 00:33:19.748 channel.toml and lineup.toml. 00:33:20.388 --> 00:33:24.248 It's something you can see where this is going. And that's pretty exciting. 00:33:24.408 --> 00:33:28.028 Maybe he'll pop on his PayPal and send Jason a few thank you bucks. 00:33:28.028 --> 00:33:31.608 I don't, I don't see a flake.nix yet, but there's still time. 00:33:31.948 --> 00:33:32.928 Maybe we can contribute. 00:33:33.648 --> 00:33:36.868 I think what I realized partway into that segment, and I still haven't done 00:33:36.868 --> 00:33:42.828 it, is every time I've talked about these things, I'm trying to relay the deep 00:33:42.828 --> 00:33:45.068 happiness they bring me every time I use them. 00:33:45.308 --> 00:33:51.988 But I don't feel like I can successfully convey, like, this is a very rewarding thing to get working. 00:33:52.528 --> 00:33:56.708 There's something about, like, we've had experience now with things like Netflix 00:33:56.708 --> 00:33:58.668 and maybe Private Plex and Jellyfin instances. 00:33:58.848 --> 00:33:59.228 And Pluto TV. 00:33:59.248 --> 00:34:02.488 And a lot of folks have experienced, like, cable TV and network TV. 00:34:02.488 --> 00:34:06.948 but the thing that you build while it is shaped and is wearing the clothes of 00:34:06.948 --> 00:34:10.048 that it's not really the same thing because you have so much more control and 00:34:10.048 --> 00:34:12.588 it's stuff you've pre-approved my favorite shows and it's. 00:34:12.588 --> 00:34:16.168 Always my favorite show it's always an episode I generally well even with Star. 00:34:16.168 --> 00:34:18.468 Trek and there's only ads if you add ads in yeah. 00:34:19.248 --> 00:34:24.088 Also you introduced me to a lot of Star Trek canon while we were working on 00:34:24.088 --> 00:34:25.168 projects the last couple weeks. 00:34:25.168 --> 00:34:25.768 Oh that's great. 00:34:26.910 --> 00:34:30.290 So that's the thing. It's like there's a few things you can actually self-host 00:34:30.290 --> 00:34:31.490 and run that just give you this 00:34:31.490 --> 00:34:36.210 constant source of joy and play and new ideas that you can iterate on. 00:34:36.890 --> 00:34:41.290 Well, it's nice to see we have a little update here from Olympia Mike, who writes in. 00:34:41.450 --> 00:34:45.590 He says, hey, guys, I just got word from LinuxFest Northwest that they're giving 00:34:45.590 --> 00:34:50.750 me and my nonprofit, the Computer Upcycle Project, its own booth at the Fest. 00:34:51.350 --> 00:34:55.450 Not only will I have some upcycled Nix books for people to play with, 00:34:55.450 --> 00:34:58.950 but I have a ton of hardware to give out for free. 00:34:59.610 --> 00:35:01.650 Over the years, I've upcycled thousands 00:35:01.650 --> 00:35:04.890 of laptops that have gone into the hands of people who need them. 00:35:05.230 --> 00:35:09.410 However, there are often computers that just aren't good enough to go out to 00:35:09.410 --> 00:35:11.670 everyday users or missing something in particular. 00:35:11.850 --> 00:35:15.310 They still work, but aren't intended for those everyday users. 00:35:15.510 --> 00:35:20.670 I have boxes and boxes of this kind of stuff that I know the Linux community 00:35:20.670 --> 00:35:22.630 can absolutely find a use for. 00:35:22.890 --> 00:35:23.350 Yeah. 00:35:23.350 --> 00:35:28.390 So here's a list of what I already know I will have for sure at LinuxFest Northwest. 00:35:28.810 --> 00:35:33.910 Over 100 ARM Chromebooks that can be jailbroken to run post-market OS. 00:35:34.350 --> 00:35:37.750 And we'll include instructions for that. 00:35:38.010 --> 00:35:42.470 Several Intel Chromebooks that have already been jailbroken and running a Debian 13. 00:35:43.350 --> 00:35:48.010 At least 30 small form factor Lenovo ThinkCenters. Oh, those are going to go fast. 00:35:48.150 --> 00:35:49.690 Oh, those are going to go really fast. Yeah. 00:35:49.690 --> 00:35:53.310 Several half-top laptops with missing 00:35:53.310 --> 00:35:56.510 or broken screens, but still work perfectly when plugged into HDMI, 00:35:57.130 --> 00:36:03.030 tons of USB, HDMI cords, a handful of Intel iMacs running Nixbook OS, 00:36:03.550 --> 00:36:09.750 two keyboards and mice, lots of random Apple hardware, tons of DDR3 and DDR4 RAM in various sizes. 00:36:10.070 --> 00:36:15.370 That is right. I said I'm giving away RAM, Wi-Fi cards, and anything else that 00:36:15.370 --> 00:36:18.150 is interesting that I find between now and then. 00:36:18.690 --> 00:36:22.630 I'll also have a donation bin set up too so if you have some of these older 00:36:22.630 --> 00:36:24.090 laptops that are just sitting around, 00:36:25.084 --> 00:36:28.044 collecting dust please consider bringing it to the fest 00:36:28.044 --> 00:36:31.084 and doting it to the organization 00:36:31.084 --> 00:36:34.004 they're all securely wiped upgraded to 00:36:34.004 --> 00:36:37.124 nick's book os and given to someone local in need 00:36:37.124 --> 00:36:42.184 i'll be up there midday saturday and everything will be completely free first 00:36:42.184 --> 00:36:46.504 come first serve and finish off the whole weekend i'm giving a talk on sunday 00:36:46.504 --> 00:36:51.604 afternoon about the story of nick's book os and the computer upcycle project 00:36:51.604 --> 00:36:55.684 i cannot wait to see you guys all there Amazing. 00:36:56.024 --> 00:37:00.824 Go check out Crazy Olympia Mike's Hardware Blowout Saturday at Linux Fest Northwest. 00:37:01.224 --> 00:37:04.244 And bring some hardware. Maybe it's a good time to upcycle some of the stuff 00:37:04.244 --> 00:37:05.064 you're not going to use anymore. 00:37:05.144 --> 00:37:09.184 I can imagine, too, you might need some help. It's going to be a lot of stuff to carry around. 00:37:09.304 --> 00:37:13.424 Yeah, it's true. That's a lot of stuff. I'm going to ask him if you moved to Flakes yet. 00:37:15.764 --> 00:37:18.004 I'm not donating if you don't get Flakes. 00:37:18.524 --> 00:37:19.724 That's good to hear from you. 00:37:19.824 --> 00:37:23.584 Can I get a Nick's book, but with Flakes on it, please? Love you, Mike. 00:37:27.664 --> 00:37:35.404 Spooky Satcom is our baller booster this week, coming in with 133,333 sats. 00:37:44.848 --> 00:37:47.508 Spooky writes, what a great pre-show and discussion last week. 00:37:47.688 --> 00:37:49.008 Glad to be a Jupiter Party member. 00:37:49.748 --> 00:37:54.208 Wes, you were brutal, but well done. Hadn't laughed so hard driving home. So here's some value. 00:37:54.548 --> 00:37:57.208 I suppose that might be about the song about you. 00:37:57.468 --> 00:37:58.528 Yeah, that was right. 00:37:58.648 --> 00:38:02.868 Wes got a little musical last week. Thanks for that. It hurt a bit. 00:38:03.468 --> 00:38:08.868 Yeah, that pre-show discussion was, I feel like, I wish we could have captured that in the show. 00:38:09.128 --> 00:38:12.988 But I'm really glad the members enjoyed it. And we were really discussing the 00:38:12.988 --> 00:38:15.348 age verification issue that's coming to Linux. 00:38:16.228 --> 00:38:17.848 Chris07 comes in. Wes, you want to take that? 00:38:17.988 --> 00:38:21.108 Mm-hmm. 22,222 sets. 00:38:23.948 --> 00:38:25.348 First time booster. 00:38:25.668 --> 00:38:25.928 Hey! 00:38:26.088 --> 00:38:26.528 Nice. 00:38:27.268 --> 00:38:32.508 I've been playing around with Turnstone to manage my home lab with fully local 00:38:32.508 --> 00:38:35.148 models and loving it. Thanks for the show. 00:38:35.308 --> 00:38:40.848 Here's my value for value. And then we are included a link to Turnstone over on GitHub. 00:38:41.228 --> 00:38:43.768 Thank you for taking the time to set up the boost and supporting us. 00:38:43.908 --> 00:38:48.328 It means more than ever right now. An experimental multi-node AI orchestration platform. 00:38:48.488 --> 00:38:50.668 Deploy tool using AI agents across a cluster. 00:38:50.848 --> 00:38:54.768 You know, it's incredible that there are these that I've just never even heard 00:38:54.768 --> 00:38:58.168 of. There's so many of these, and they're just cooking right now. 00:38:58.608 --> 00:39:02.468 Five hours ago was the last. Like, when we check these projects out, 00:39:02.648 --> 00:39:05.928 they're committing while we're doing a live show on a Sunday. 00:39:05.928 --> 00:39:08.628 And it's not huge, but there's, you know, five contributors. 00:39:08.748 --> 00:39:09.588 Okay, one of those is Claude. 00:39:09.708 --> 00:39:13.928 But four contributors and 280 stars already. It just, yeah, stuff's moving. 00:39:14.148 --> 00:39:19.268 Works with any open AI compatible API. Very cool. I had not heard that. 00:39:19.468 --> 00:39:23.428 Appreciate the heads up on that kind of thing. And also, thank you very much 00:39:23.428 --> 00:39:24.948 for taking the time to get boosting. 00:39:25.888 --> 00:39:27.008 We really appreciate it. 00:39:27.048 --> 00:39:27.348 Yeah, we do. 00:39:27.988 --> 00:39:33.708 Well, tomato, or tomato, if you will, boosted in 21,346 sets. 00:39:38.648 --> 00:39:44.768 These are through a couple different messages, and one of them happens to be 12345satoshis. 00:39:50.264 --> 00:39:54.284 This is a minor time travel boost from episode 657. 00:39:54.924 --> 00:39:59.784 Thank you for putting in all of the time and effort for the planet Nix and scale coverage. 00:40:00.324 --> 00:40:05.244 Picking MTR in 2026 is also hilarious, but it's still a great tool. 00:40:06.124 --> 00:40:08.084 Yeah, we call that Pix Classic. 00:40:10.824 --> 00:40:16.004 They continue a good discussion on the members' feed about privacy and age verification last week. 00:40:16.004 --> 00:40:21.264 For my part, I'm drawing a hard line here. Free software has been through civil 00:40:21.264 --> 00:40:26.124 liberties fights in the past, and this is for me clearly another. 00:40:26.344 --> 00:40:30.084 This big corporation and governments are after my and my kids' privacy, 00:40:30.124 --> 00:40:32.624 and I will not compromise on this one. 00:40:32.764 --> 00:40:38.424 If my distro of choice implements an age verification API, collects ID information, 00:40:38.744 --> 00:40:42.564 implements a race or citizenship API, I will leave. 00:40:42.884 --> 00:40:46.004 If I need to run Arch or Gentoo, so be it. 00:40:46.004 --> 00:40:48.944 Leaving the distro. Leaving the distro. 00:40:48.944 --> 00:40:49.844 How do you feel about that? 00:40:50.264 --> 00:40:51.684 Mm-hmm. Mm-hmm. Mm-hmm. 00:40:51.824 --> 00:40:58.384 And there is a last boost here. In the past, we went so far as to have GPG developed 00:40:58.384 --> 00:41:00.784 in Europe when it was illegal in the US. 00:41:00.904 --> 00:41:03.784 We didn't roll over for Clinton and his clipper chip. 00:41:04.184 --> 00:41:09.044 This is non-negotiable. And for me as a parent, it's doubly upsetting. 00:41:09.264 --> 00:41:13.064 I want to protect my children from exactly this sort of privacy invasion. 00:41:13.464 --> 00:41:14.724 Man, I remember the clipper chip. 00:41:14.884 --> 00:41:15.084 Indeed. 00:41:16.004 --> 00:41:17.164 I don't know the Clipper chip. 00:41:17.764 --> 00:41:21.004 Good callback. Like a censorship built into the TV. 00:41:21.324 --> 00:41:26.424 So it could detect swear words or something like that and auto-mute them. 00:41:27.104 --> 00:41:30.304 The idea was that you'd build in a hardware-level thing. 00:41:31.144 --> 00:41:34.924 And there were commercial devices based around that for a little bit. 00:41:36.124 --> 00:41:38.404 Thank you very much. Appreciate the follow-up, Tamato. 00:41:38.564 --> 00:41:43.924 It's nice having real people's opinions on where they actually draw their lines. 00:41:43.924 --> 00:41:46.784 You know, regardless of if you disagree or agree, but just having it spelled 00:41:46.784 --> 00:41:48.404 out in the reasoning is really useful. 00:41:49.884 --> 00:41:52.184 Outdoor Geeks here with 5,000 Sats. 00:41:54.381 --> 00:41:59.341 Would you try a green boost and report back the open-source green boost NVIDIA? 00:41:59.881 --> 00:42:03.221 This is an article at Pharonix. Open-source green boost driver aims to augment 00:42:03.221 --> 00:42:07.681 NVIDIA GPUs, VRAM, with RAM and NVMe to handle larger LLMs. 00:42:08.781 --> 00:42:15.601 The issue is, of course, you have to have a relatively recent RTX card, which is... 00:42:15.601 --> 00:42:17.521 So the second we get one of those. 00:42:17.741 --> 00:42:19.621 Absolutely, we will be trying those. 00:42:21.141 --> 00:42:25.841 I just found a GTX 960 in the drawer. I don't think that's going to quite do 00:42:25.841 --> 00:42:30.001 it though I like that idea though Outdoor, it's on the radar officially Thank 00:42:30.001 --> 00:42:31.861 you for sending that our way Our. 00:42:31.861 --> 00:42:35.801 Buddy Hybrid Sarcasm comes in with 10,000 cents Oh! 00:42:38.501 --> 00:42:42.421 That song begging on Brantley's browser habits Was Jeff's Kiss. 00:42:42.421 --> 00:42:49.781 Brantley just He won't pin his tabs How dare you Brantley won't pin his tabs. 00:42:57.680 --> 00:43:00.420 If it wasn't so catchy, I'd be more angry. 00:43:01.820 --> 00:43:02.680 That's the trick. 00:43:03.600 --> 00:43:06.980 Well, E. Scott boosted in 2,500 sats. 00:43:07.840 --> 00:43:12.940 He has a list here of underpowered hardware, since Chris, you've been asking for it. 00:43:13.440 --> 00:43:19.780 Well, a pihole 0.1.3 running, or a pi 0.1.3 running pihole. 00:43:20.420 --> 00:43:21.800 Two zeros, actually. 00:43:21.960 --> 00:43:24.400 It's two zeros, actually. Yeah, yeah. It's a cluster. 00:43:24.780 --> 00:43:27.940 Here's what he's got running on it, though. All right. next cloud apache 00:43:27.940 --> 00:43:30.840 hdps wikipedia jellyfin java web 00:43:30.840 --> 00:43:33.780 server for work audio bookshelf navidrome fresh r 00:43:33.780 --> 00:43:39.520 says get t hdm hdm it's too much already homebox me tube paperless nginx pinch 00:43:39.520 --> 00:43:45.140 flat rom m sterling pdf sync thing tailscale trillium uptime kuma and hoogle 00:43:45.140 --> 00:43:52.180 as well as open claw that's impressive what on i mean open. 00:43:52.180 --> 00:43:54.100 Claw itself takes a fair bit. 00:43:54.100 --> 00:44:01.000 On four gigs of ram that might win the that might win it right there how do you beat that i. 00:44:01.000 --> 00:44:02.580 Think he scott does it so we don't have to. 00:44:02.580 --> 00:44:08.680 That's nuts well done i am impressed i didn't think i'd be impressed i am impressed, 00:44:10.384 --> 00:44:14.844 Okay. Adversary 17th here with 8,441 slits. 00:44:16.104 --> 00:44:18.464 Wes, what prompt did you use to create? 00:44:19.964 --> 00:44:22.944 Chris, it's okay. We're the recovering ricers. Understand your pain. 00:44:23.224 --> 00:44:25.624 The step to recovery is admitting you have a problem. Oh, he wants to. 00:44:25.644 --> 00:44:27.624 Oh, yeah. So context here. 00:44:27.784 --> 00:44:31.584 Wes created a roast song at the end of the membership bootleg last week that 00:44:31.584 --> 00:44:34.784 roasts me for using Hyperland and a tiling window manager. 00:44:35.264 --> 00:44:38.864 And the prompt you used, Wes, do you have it handy? Do you know what the prompt 00:44:38.864 --> 00:44:40.824 was? It wasn't very elaborate. 00:44:41.344 --> 00:44:47.484 I think I have the Brent one. This is a comedy album, party record style. 00:44:47.704 --> 00:44:50.724 It's a song that simulates a podcast as a funny trick. 00:44:50.924 --> 00:44:54.284 So it's a Linux podcast about ButterFS versus CFS. And also, 00:44:54.464 --> 00:44:57.604 it's a frustrated soapbox rant about how, so this is the Brentley one, 00:44:57.664 --> 00:45:01.704 how one of the hosts, Brentley, won't use pin tabs in Firefox for no good reason. 00:45:02.184 --> 00:45:05.604 Musical style is non-musical spoken word, no percussion, no instruments, 00:45:05.704 --> 00:45:07.244 ambient silence podcast audiobook. 00:45:07.464 --> 00:45:09.904 I think I just tweaked it for yours, So it's like, you know, 00:45:10.524 --> 00:45:14.584 some sort of seed of like Chris irrationally uses Tyler window managers. 00:45:14.744 --> 00:45:17.124 He won't use a reasonable desktop environment or something like that. 00:45:17.264 --> 00:45:20.504 What's funny is that really from that, it makes like a chorus and all of that. 00:45:20.824 --> 00:45:25.024 Yeah, unfortunately, that prompt works extremely well. And yeah, 00:45:25.484 --> 00:45:28.164 looking forward to more requests. Thanks. Maybe one about yourself. 00:45:28.904 --> 00:45:32.384 Well, you know, you have the prompt now. So I think you guys, 00:45:32.524 --> 00:45:34.084 that is totally fair game. 00:45:34.804 --> 00:45:36.424 Brantley, you want to take the one from your countryman? 00:45:36.944 --> 00:45:41.484 Oh, this is Rubikman. 3,222 satoshis. 00:45:44.589 --> 00:45:47.289 Oh, I see why you wanted me to take this one. You can't pronounce the name of 00:45:47.289 --> 00:45:50.709 this place. Greetings from Miramichi, New Brunswick in Canada. 00:45:50.909 --> 00:45:52.409 I think it's pronounced Miramachi. 00:45:52.949 --> 00:45:58.369 Is that Miramichi? I'm against the age verification laws, as it is just another 00:45:58.369 --> 00:46:02.529 way to track and catalog us under the guise of clutches, pearls, 00:46:02.769 --> 00:46:04.649 won't someone think of the children? 00:46:05.729 --> 00:46:09.749 It's not my responsibility to make sure that your kids don't look at porn. 00:46:09.749 --> 00:46:14.669 if the distros are forced to implement age verification for some areas it will 00:46:14.669 --> 00:46:20.089 be everywhere because i doubt they will maintain two or more versions and that 00:46:20.089 --> 00:46:25.769 will be the end of privacy because vpns won't protect you with that yeah. 00:46:25.769 --> 00:46:29.589 I do think that's probably true if it if it if it takes off you're they're probably 00:46:29.589 --> 00:46:31.809 just going to be everywhere it'll be just everywhere. 00:46:31.809 --> 00:46:34.489 And a flag in xos right yeah. 00:46:34.489 --> 00:46:39.469 Or something system d something like that trellion comes in with 16 000 sats, 00:46:40.389 --> 00:46:43.509 and just says boost thank you Trillian. 00:46:44.849 --> 00:46:48.409 Tarion Bronzewing comes in with a row of ducks. 00:46:48.409 --> 00:46:50.849 Love the. 00:46:50.849 --> 00:46:53.949 AI hacking open claw and local content keep it coming. 00:46:53.949 --> 00:46:54.629 Thank you. 00:46:56.829 --> 00:47:04.889 Our dear Gene Bean sends in a couple rows of ducks for a total of 5,781 Satoshis, 00:47:08.680 --> 00:47:11.900 Here's a little feedback on Cage kiosk, which I brought up last week. 00:47:12.060 --> 00:47:15.940 Cage is what I use for my two kiosks that show a Home Assistant dashboard. 00:47:16.400 --> 00:47:22.060 Here is one of them. Any links to a NixOS config? Chris, I know you like diving into those. 00:47:22.320 --> 00:47:23.660 I do. I'm looking at it right now. 00:47:24.220 --> 00:47:29.800 By the way, regarding building a NixOS image for the Pi, grab a temporary Ampere 00:47:29.800 --> 00:47:33.360 instance from Hetzner and use it as a remote build host. 00:47:33.800 --> 00:47:36.760 That's how I built mine. Very speedy. 00:47:37.400 --> 00:47:39.280 That's big brain thinking there, Gene. Thank you. 00:47:39.540 --> 00:47:44.080 Last boost here. Funny story. I went looking at my transactions after you mentioned 00:47:44.080 --> 00:47:48.640 it being a light week last week and realized I missed listening to an episode. 00:47:49.060 --> 00:47:50.960 Got to fix that in a little while. 00:47:52.060 --> 00:47:53.980 Thank you, Gene. You are the best. 00:47:54.120 --> 00:47:54.320 Thanks, Gene. 00:47:55.280 --> 00:48:01.960 A dude trying stuff comes in with 5,000 sats. I appreciate your struggles with the calendars. 00:48:02.100 --> 00:48:04.960 I've recently been looking to make my switch from macOS, and one of the last 00:48:04.960 --> 00:48:08.360 remaining applications was a native high quality client from my CalDev server. 00:48:08.660 --> 00:48:09.800 Also, I wanted to submit a pic. 00:48:10.400 --> 00:48:14.900 Planify. It's a very pretty task manager that works natively with CalDev. 00:48:15.240 --> 00:48:16.240 Thanks for the show, boys. 00:48:16.480 --> 00:48:16.840 Nice. 00:48:17.420 --> 00:48:19.360 Thank you, a dude trying stuff. Nice to hear from you. 00:48:19.660 --> 00:48:22.060 See, trying stuff, telling us about it. This is great. 00:48:22.460 --> 00:48:26.180 Thank you, everybody who supported the show with a boost. We had 18 of you stream 00:48:26.180 --> 00:48:30.640 sats as you listened and you collectively all stacked 29,701 sats. 00:48:30.760 --> 00:48:34.700 When you combine that with our boosters this week, We got a pretty good showing, 00:48:34.700 --> 00:48:35.800 especially compared to last week. 00:48:35.920 --> 00:48:42.820 We got 264,768 sats for episode 660 of your Unplugged program. 00:48:45.227 --> 00:48:48.827 Thank you, everybody who supports us with a boost. Fountain makes it really easy. 00:48:49.087 --> 00:48:52.947 There's also a self-hosted route with AlbiHub and lots of great apps you can 00:48:52.947 --> 00:48:54.227 integrate with, including Fountain. 00:48:54.467 --> 00:48:58.107 And, of course, thank you to our members who support us every single episode. 00:48:58.287 --> 00:49:01.487 Thank you, everybody. We really appreciate it. The show runs on your support 00:49:01.487 --> 00:49:04.247 right now more than ever. In fact, only on your support. 00:49:05.747 --> 00:49:09.687 Now, we got a smattering of picks, boys. A smattering. 00:49:09.867 --> 00:49:12.687 Because a couple of them actually came in from the feedback inbox this week. 00:49:12.827 --> 00:49:16.507 So they're listener picks. But let's start with Boar. 00:49:17.027 --> 00:49:21.987 This one, I believe, I'm going to guess, could be Brent, could be Wes, 00:49:22.187 --> 00:49:27.847 because I talked to both of you about it, so I can't remember which one he is. I'm going to say Wes. 00:49:28.047 --> 00:49:35.227 That's right. Actually, it helped us out behind the scenes a little bit, 00:49:35.287 --> 00:49:39.707 because we were trying to watch Big Buck Bunny with producer Jason. 00:49:40.007 --> 00:49:42.647 Right, remotely. We're all trying to do a group watch of Big Buck Bunny. 00:49:42.647 --> 00:49:45.327 Yeah, and unfortunately, he didn't have the file locally. 00:49:45.547 --> 00:49:45.687 No. 00:49:45.907 --> 00:49:48.847 And it was taking a really long time for him to be able to get it from the upstream. 00:49:48.947 --> 00:49:51.887 Yeah, because it was a real high-res version of the file. 00:49:52.107 --> 00:49:54.387 Yeah. But I had it locally. 00:49:54.527 --> 00:49:54.687 Yeah. 00:49:55.387 --> 00:50:00.427 So I was able to use Bore, which is a modern, simple TCP tunnel in Rust that 00:50:00.427 --> 00:50:04.947 exposes local ports to a remote server, bypassing standard NAT connection firewalls. 00:50:04.987 --> 00:50:07.287 That's all it does. No more, no less. 00:50:07.467 --> 00:50:09.827 So then he downloaded over like a link? Yeah. 00:50:10.099 --> 00:50:13.859 Like an HTTP link? Or does he use like a command on his end to pull it down? What's the other end? 00:50:13.919 --> 00:50:19.179 Yeah, so the other part was I just ran a Python HTTP server in the folder where 00:50:19.179 --> 00:50:21.279 the bigbuckbunny.mp4 file was. 00:50:21.399 --> 00:50:21.719 Yeah, of course, yeah. 00:50:21.799 --> 00:50:22.859 And then I could just send a link 00:50:22.859 --> 00:50:26.979 to HTTP web server. It just does like a listing of the files, et cetera. 00:50:27.219 --> 00:50:30.979 And then Bohr handles the part of taking that local port and publishing it on 00:50:30.979 --> 00:50:34.579 a public IP address, and then he could connect to it. And then we were able 00:50:34.579 --> 00:50:35.759 to watch it and enjoy it together. 00:50:35.939 --> 00:50:36.439 Yes, we were. 00:50:36.439 --> 00:50:41.919 You know and this took wes like a total of five minutes to deploy and i don't 00:50:41.919 --> 00:50:44.639 think you had used it previously and chris and i were just like i don't know 00:50:44.639 --> 00:50:48.339 talking about nothing and wes just solves this problem in five minutes with 00:50:48.339 --> 00:50:51.959 a brand new tool that he brings to the show so uh oh wait there's even more 00:50:51.959 --> 00:50:53.619 wes you didn't just use it. 00:50:53.619 --> 00:50:54.939 Oh there's more. 00:50:54.939 --> 00:50:59.439 Well so i had um i had used it a little bit before but this is probably the 00:50:59.439 --> 00:51:03.699 best stress test is like i wanted something essentially kind of similar to like a Cloudflare, 00:51:04.439 --> 00:51:10.139 tunnel sort of setup without all the fancy SSL kind of stuff and other layers on top of it. 00:51:10.559 --> 00:51:14.559 But just like an easy way, if I had stuff on one server that maybe even I didn't 00:51:14.559 --> 00:51:17.299 need it on, like to have it already on a mesh network that I needed, 00:51:17.359 --> 00:51:20.079 maybe it's a throwaway host, you know, maybe I'm spinning something up and I 00:51:20.079 --> 00:51:21.459 just want to provide access easily, 00:51:22.099 --> 00:51:25.979 then this seemed like a good solution and it's only, it's like 400 lines of 00:51:25.979 --> 00:51:29.799 safe, it's not even unsafe async Rust code, so it's like super trivial to set 00:51:29.799 --> 00:51:31.879 up. The only thing it was missing, it's already in Nix packages. 00:51:32.199 --> 00:51:35.679 It just didn't have a NixOS module. So I threw one of those together real quick, 00:51:35.719 --> 00:51:39.739 which is really just some options that render out a systemd service to run it 00:51:39.739 --> 00:51:45.519 because it basically just needs some port allocations and network access. And there you go. 00:51:46.118 --> 00:51:49.658 Well done, sir. All right, Bore, link in the show notes and link to the module as well. 00:51:49.838 --> 00:51:55.878 Our next pick is KD Connect SMS TUI and Scott Syntheson. 00:51:56.078 --> 00:51:59.478 He says, you all have expressed interest in both TUIs and KD Connect. 00:51:59.798 --> 00:52:03.078 And because Google is taking away QR code web pairing for messages, 00:52:03.438 --> 00:52:06.818 I worked with Cloud Desktop to develop KD Connect SMS TUI. 00:52:07.038 --> 00:52:10.478 Search conversations and messages, send and receive SMS and MMS, 00:52:10.718 --> 00:52:12.518 inline image display for KD. 00:52:12.718 --> 00:52:17.338 That's cool. I-Term 2 and a few other terminals. you have contact name resolution 00:52:17.338 --> 00:52:21.698 from synced v cards group conversation support in the tui with custom name wow 00:52:21.698 --> 00:52:26.018 multiple device switching with a pop-up selector archive and spam folders for 00:52:26.018 --> 00:52:31.658 hiding conversations 17 built-in themes with this is better than my. 00:52:31.658 --> 00:52:33.498 Sms messenger on my phone. 00:52:33.498 --> 00:52:36.658 And of course rust app, 00:52:37.730 --> 00:52:38.790 Of course, it's a Rust Ham. 00:52:39.130 --> 00:52:42.510 Amazing. Ooh, Ratatouille. And that's a Netflix Flake, too. Great. 00:52:43.010 --> 00:52:46.130 It's pretty slick, right? I mean, Scott's on fire with this one. 00:52:46.170 --> 00:52:50.250 He's got a whole series of hotkeys, so you can whip around this thing like a 00:52:50.250 --> 00:52:53.570 DOS Pro from the 80s and early 90s. 00:52:53.970 --> 00:52:58.870 I mean, treat it like it's your Vim. It's pretty cool. So that's... 00:52:58.870 --> 00:53:01.750 I will definitely be trying this, because I do have KDE Connect. 00:53:01.950 --> 00:53:02.030 Yeah. 00:53:02.110 --> 00:53:05.790 It was like, Wes, are you running it already? Well, the Netflix Flake is building. 00:53:06.270 --> 00:53:12.090 Thank you, Scott. And that is MIT licensed. Now, Andrew sent in our next one, 00:53:12.110 --> 00:53:14.850 and it's an alternative to what I talked about last week. 00:53:14.950 --> 00:53:17.630 This one's called BusyBridge, a complex calendar. 00:53:17.810 --> 00:53:19.750 It's a free, busy syncing across organizations. 00:53:20.030 --> 00:53:25.110 It says it's a self-hosted multi-user calendar synchronization service for consulting organizations. 00:53:25.370 --> 00:53:28.810 The service allows users to connect multiple client calendars from, 00:53:28.950 --> 00:53:32.530 say, client organizations to feed their main calendar, keeping availability 00:53:32.530 --> 00:53:37.710 in sync across all the calendars without duplicating event details that don't belong. 00:53:38.110 --> 00:53:40.670 Andrew says, I was listening and having a good laugh because I actually had 00:53:40.670 --> 00:53:43.150 to solve this problem so that way everybody can see what's going on. 00:53:43.290 --> 00:53:45.630 I've been using it for myself, self-hosted, and it's pretty nice. 00:53:45.750 --> 00:53:49.530 It lets you use one main calendar and see all your events color-coded on it. 00:53:49.830 --> 00:53:53.430 And so he sent me along the project that he found here. It's called Busy Bridge. 00:53:53.890 --> 00:53:58.250 This is cool. Python app, self-hosted calendar synchronization service. 00:53:58.410 --> 00:54:02.770 Yeah. Bidirectional sync, personal calendar sync, WebDAV, ICS, 00:54:02.890 --> 00:54:05.070 subscription, reoccurring events, smart busy blocks. 00:54:05.650 --> 00:54:08.450 RSVP propagation. That's some attention to detail. 00:54:08.570 --> 00:54:09.870 I know. I know. 00:54:10.010 --> 00:54:12.530 That's the part I probably wouldn't have bothered to do. You know what I mean? 00:54:12.610 --> 00:54:14.390 But like someone else has done that? That's great. 00:54:14.570 --> 00:54:19.070 Hourly consistency checks. Six-hour orphan scans. Automatic retry of missing busy blocks. 00:54:19.310 --> 00:54:23.370 Circuit breaker or auto-pause sync when all calendars fail. It's pretty smart. 00:54:23.790 --> 00:54:25.150 Auto backups as well? 00:54:25.310 --> 00:54:25.570 Yep. 00:54:25.750 --> 00:54:27.110 Self-healing? Yep. 00:54:27.550 --> 00:54:30.690 This is the real deal. So that's a real nice find. 00:54:31.190 --> 00:54:34.510 I like that a lot so thank you Andrew for sending that along he says I think 00:54:34.510 --> 00:54:35.350 it might do more of what you need 00:54:35.350 --> 00:54:39.530 it might be right it might be right it's often how it goes I you know I uh, 00:54:40.610 --> 00:54:42.750 I talk about something, somebody's like, you know, you could try this. 00:54:42.890 --> 00:54:45.070 That's how I found dispatcher, right? Is I found one thing, you're like, 00:54:45.110 --> 00:54:46.950 you should try dispatcher. I'm like, oh, great. 00:54:48.330 --> 00:54:51.410 All right. So we're going to wrap it up here. Let us know your thoughts on, 00:54:51.410 --> 00:54:53.590 you know, the future of booting your Linux box. 00:54:53.670 --> 00:54:57.850 So I want to know if you're using grubber systemd boot and if you use sign bootloaders. 00:54:57.870 --> 00:54:59.030 Those are the main things I want to know. 00:54:59.410 --> 00:55:01.990 Is secure boot turned on? Do you rely on that? What are your thoughts? 00:55:02.270 --> 00:55:05.050 Yeah. Let us know about that because I just would like to take a survey from 00:55:05.050 --> 00:55:09.490 the audience. You guys are pretty technical groups. So I think it'd be telling what your answer is. 00:55:09.930 --> 00:55:14.430 And yeah, let us know. Send in with Booster, linuxunplugged.com slash contact. 00:55:14.810 --> 00:55:20.250 Now, you can also get even more show by joining us live. You can make it a Linux Tuesday on a Sunday. 00:55:20.530 --> 00:55:23.770 Join us at Sunday, 10 a.m. Pacific, 1 p.m. Eastern. 00:55:27.270 --> 00:55:30.890 That'll be in your podcasting 2.0 app of choice, like Fountain FM, 00:55:31.310 --> 00:55:36.790 or over at jblive.tv. But Wes Payne, if they want more metadata or information 00:55:36.790 --> 00:55:38.090 around the show, we got that for him, too. 00:55:38.210 --> 00:55:44.010 Yeah, a podcast 2.0 compliant RSS feed, which means it has all kinds of fun goodies in there. 00:55:44.230 --> 00:55:48.530 Like, well, a good, but no, JSON Cloud Chapters. 00:55:48.630 --> 00:55:48.770 Yeah. 00:55:49.210 --> 00:55:52.370 And both VTT and SRT files if you want a transcript. 00:55:52.450 --> 00:55:56.210 I heard the developer of Overcast this week say, nobody has transcripts in their 00:55:56.210 --> 00:55:58.730 feeds. We've had it for two years now, buddy. 00:55:58.870 --> 00:55:59.350 Two types. 00:55:59.470 --> 00:55:59.730 That's right. 00:55:59.730 --> 00:56:03.790 And, you know, you don't even have to be like a full 2.0 client to use it. 00:56:03.870 --> 00:56:05.010 Stuff like Intendapod uses them. 00:56:05.110 --> 00:56:08.410 Yeah, there's also Secret, a video version in the feed, too, you could always find. 00:56:08.410 --> 00:56:09.750 That's right. Check that out. 00:56:09.850 --> 00:56:14.110 We're out of here. Thank you for joining us. We'll see you right back here next Tuesday, as in Sunday. 00:56:58.097 --> 00:57:00.097 Remember if someone has a van that 00:57:00.097 --> 00:57:04.297 needs rescuing we're looking for a half abandoned van we watch our van.