WEBVTT 00:00:11.519 --> 00:00:16.039 Hello, friends, and welcome back to your weekly Linux talk show. My name is Chris. 00:00:16.259 --> 00:00:17.139 My name is Wes. 00:00:17.499 --> 00:00:18.659 And my name is Brent. 00:00:19.159 --> 00:00:23.679 Hello, gentlemen. Well, coming up on the show today, we have some big news stories to dig into. 00:00:24.579 --> 00:00:29.499 Then I'm going to tell you how my hyper-tuned play toy has turned into something 00:00:29.499 --> 00:00:31.479 that's maybe the real deal. 00:00:31.659 --> 00:00:35.959 And then we'll round out the show with some great boosts, a whole rack of picks, 00:00:36.099 --> 00:00:39.419 too many picks, and a lot more. So before we go any further, 00:00:39.639 --> 00:00:43.159 let me say a time-appropriate greeting to our mumble room. Hello, VirtualLug. 00:00:43.859 --> 00:00:47.939 Hello, Chris. How are you? And hello, Brent. Hello. Hello, Dave. 00:00:48.839 --> 00:00:51.899 Nice to see you. Everybody camping out there in the quiet listening. 00:00:52.059 --> 00:00:55.499 And shout out to our live matrix as we go along, too. 00:00:56.239 --> 00:01:01.299 And, of course, Define.net slash unplugged. Go meet Managed Nebula from Define Networking. 00:01:01.579 --> 00:01:07.539 It is a decentralized VPN built on the open-source Nebula platform that we love. 00:01:07.539 --> 00:01:10.379 And I'll get more into that in just a moment. But Nebula is really something special. 00:01:10.539 --> 00:01:14.779 It's super fast. It's simple. And it has industry-leading security. 00:01:15.639 --> 00:01:18.839 Nebula's decentralized design means that your network is resilient in a way 00:01:18.839 --> 00:01:21.959 that the other providers just cannot offer or manage. 00:01:22.219 --> 00:01:26.339 And you can go from just a home lab all the way up to a global enterprise. 00:01:26.559 --> 00:01:30.759 It was originally developed back in 2017 to securely connect Slack's global 00:01:30.759 --> 00:01:32.579 infrastructure, which is all over the place. 00:01:33.239 --> 00:01:37.159 And they've got, like, the world's trade secrets in their system. 00:01:37.159 --> 00:01:38.339 So they had to have it secure. 00:01:38.499 --> 00:01:41.579 Nebula was engineered to scale, perform, and be secure from day one. 00:01:42.279 --> 00:01:47.999 And this, okay, what I love is that it's truly top to bottom an open source platform. 00:01:48.639 --> 00:01:51.559 Right? So if you're building your whole network infrastructure on this, 00:01:51.699 --> 00:01:54.079 you could do all of it yourself, open source. 00:01:54.439 --> 00:01:57.599 But it also means that you can watch development and see where things are going. 00:01:58.901 --> 00:02:02.901 And there's an issue that has been in the works since October of 2022. 00:02:04.241 --> 00:02:08.421 And it's a nice little win for the Nebula community because they've begun testing this upstream now. 00:02:08.601 --> 00:02:13.681 And it allows Nebula to support multiple UDP source ports, i.e. multiport support. 00:02:14.201 --> 00:02:17.581 And this is no small feat. Like this has been challenging for WireGuard in general. 00:02:17.801 --> 00:02:20.861 And this week the work was finished upstream. Now it's not shipping. 00:02:21.001 --> 00:02:22.161 They're still looking at it. 00:02:22.821 --> 00:02:26.761 But what it means is this new multiport support means that you can tunnel a 00:02:26.761 --> 00:02:29.661 whole range of UDP source ports instead of just one. 00:02:29.981 --> 00:02:32.281 And that spreads the traffic across multiple flows. 00:02:32.941 --> 00:02:36.721 So if you've got like a cloud provider that's limiting you, or maybe you're 00:02:36.721 --> 00:02:41.261 on a connection like Starlink that's throttling you, you can kind of spread that out now. 00:02:41.881 --> 00:02:45.321 They're running through the test. It's not shipping, but oh man, 00:02:45.381 --> 00:02:48.521 does it look good. And the payoff is better reliability on these connections too. 00:02:48.861 --> 00:02:52.861 And in the thread of the PR, there's some massive gains noted. 00:02:53.581 --> 00:02:57.161 They write, I suspect that Verizon was throttling individual UDP streams. 00:02:57.781 --> 00:03:03.521 So this proved that to be true. I went from 50 megabits to one gigabit by using 00:03:03.521 --> 00:03:05.481 a 4X multiport configuration. 00:03:05.821 --> 00:03:06.201 Whoa. 00:03:07.121 --> 00:03:12.081 Yeah. So it's one of those things where as somebody who's planning their infrastructure, 00:03:12.821 --> 00:03:14.721 it's really nice to see this stuff coming. 00:03:14.841 --> 00:03:19.181 You can watch this from 2022 all the way to today where they're working it out. 00:03:19.281 --> 00:03:21.181 They're testing it. They're documenting the results. 00:03:21.561 --> 00:03:26.501 They're discussing if they should ship it. It's all right there for the world to see. 00:03:27.161 --> 00:03:30.221 And you can trust it when you build on top of that because it's open source 00:03:30.221 --> 00:03:31.921 and that's all just out there in the open. 00:03:32.561 --> 00:03:35.121 And they make it completely hassle-free with their managed product. 00:03:35.541 --> 00:03:37.741 Nothing else has the resilience, speed, or scalability. 00:03:37.921 --> 00:03:40.821 Get started with up to 100 hosts, absolutely free, no credit card required. 00:03:40.821 --> 00:03:43.941 Go to defined.net slash unplugged. 00:03:44.241 --> 00:03:46.461 That's defined.net slash unplugged. 00:03:49.204 --> 00:03:53.024 Okay, so we are planning our Texas road trip. We're still looking for anybody 00:03:53.024 --> 00:03:54.884 who would like to help us go there and do our coverage. 00:03:55.024 --> 00:03:57.924 So reach out to me, Chris at JupyterBroadcasting.com if you'd like to work together. 00:03:59.184 --> 00:04:05.364 And we have been considering a just after the fest meetup. 00:04:05.784 --> 00:04:10.144 And I want to know if there's interest because it's specifically for people that are road tripping. 00:04:10.824 --> 00:04:13.984 We haven't really figured this out, but we figure towards the end of Texas Linux 00:04:13.984 --> 00:04:17.984 Fest or the day that we're leaving, as we're going out of town or something 00:04:17.984 --> 00:04:21.124 like that, We set up for a breakfast and we have one last goodbye. 00:04:21.864 --> 00:04:24.564 We usually do these things like before the events or during the event, 00:04:24.644 --> 00:04:25.684 but I thought, wouldn't it be kind of fun? 00:04:25.824 --> 00:04:30.624 So if you want to join us, reach out, boost in or send us an email and say you'd 00:04:30.624 --> 00:04:34.504 be interested in doing like a after the festival meetup kind of thing. 00:04:34.624 --> 00:04:38.964 And if we get a few bites, we'll put something together like Brent over there. 00:04:39.064 --> 00:04:40.244 He's putting something together right now. 00:04:40.244 --> 00:04:43.324 Sure am i've been thinking the last couple weeks that 00:04:43.324 --> 00:04:46.784 i might consider crashing the september 20th 00:04:46.784 --> 00:04:49.864 meetup of the jb crew in toronto but i 00:04:49.864 --> 00:04:54.344 want to know would people show up if i end up in that neck of the woods maybe 00:04:54.344 --> 00:04:59.804 i can convince i don't know other jb friends to show up too so uh let us know 00:04:59.804 --> 00:05:06.864 if you'd be interested in a brent crashing september 20th in toronto and uh if so, 00:05:07.744 --> 00:05:13.204 please go to our jb colony events website there's a little posting there of 00:05:13.204 --> 00:05:17.124 the location and uh if if you don't mind register your attendance and let us 00:05:17.124 --> 00:05:18.824 know if that would be interesting to you. 00:05:18.824 --> 00:05:21.364 I guess we got to get some tickets huh chris. 00:05:21.364 --> 00:05:26.724 Yeah we better i mean i don't think actually we were technically invited yet west so true. 00:05:26.724 --> 00:05:30.924 Let us know if you'd like us to invite chris and maybe. 00:05:30.924 --> 00:05:36.304 Don't uh but yeah colony events.com and we will have a link in those show notes, 00:05:39.650 --> 00:05:43.710 All right, so let's do a news update. It's been a minute, and there is a story 00:05:43.710 --> 00:05:49.730 that we sort of have a midway update on, and it's BcacheFS's inclusion in the Linux kernel. 00:05:50.490 --> 00:05:54.510 And while things are still very much in development and the situation is fluid, 00:05:54.770 --> 00:05:59.690 as things stand right now, it is possible that Linux may lose out on the next 00:05:59.690 --> 00:06:04.250 big file system, not because of code issues, but over a clash of personalities. 00:06:05.630 --> 00:06:10.630 And Linux 6.17 is out, but without the BcacheFS updates. 00:06:10.950 --> 00:06:15.890 Yeah, just to be clear, it's not that 17's out totally, but we're in the RC phase now. 00:06:16.030 --> 00:06:21.070 So that merge window has closed and no poll for BcacheFS. 00:06:21.390 --> 00:06:26.390 And it's all kind of unfortunate timing because BcacheFS core developer Kent 00:06:26.390 --> 00:06:28.410 Overstreet passed guest on this program. 00:06:28.410 --> 00:06:33.550 Well, he mentioned that he'd planned for BcacheFS to actually shed that experimental 00:06:33.550 --> 00:06:37.030 label in 6.18, the next kernel. 00:06:38.450 --> 00:06:44.410 But, unfortunately, disagreements over his criticisms on the LKML about the 00:06:44.410 --> 00:06:49.470 ButterFS file system, well, that ended up turning into a rather heated exchange 00:06:49.470 --> 00:06:51.270 on the mailing list this past week. 00:06:52.010 --> 00:06:56.050 Meta's Yosef Bacik has done a ton of great work on ButterFS, 00:06:56.790 --> 00:07:01.970 called Kent's behavior unacceptable, and the ext4 maintainer Ted So went further, 00:07:02.110 --> 00:07:07.270 saying, many developers see him as, quote, toxic, and want his code removed. 00:07:07.550 --> 00:07:11.170 And Ted was clear, not for technical reasons. It seems like actually most of 00:07:11.170 --> 00:07:15.050 the folks in this thread respect Kent's technical chops and BcacheFS, 00:07:15.290 --> 00:07:16.770 you know, just as a code base. 00:07:17.310 --> 00:07:21.890 But for Kent's style of communication and his conduct, and in particular here, 00:07:22.330 --> 00:07:24.670 criticizing other file systems in the kernel. 00:07:25.090 --> 00:07:31.390 Now, Kent has promised to stop criticizing ButterFS, but the fallout makes it 00:07:31.390 --> 00:07:36.970 even more likely that BcacheFS won't be seeing any advances or maybe even not 00:07:36.970 --> 00:07:39.550 continued acceptance in the kernel. 00:07:40.805 --> 00:07:44.305 You know, it kind of seems like this dispute is highlighting a long-running 00:07:44.305 --> 00:07:48.425 issue we've seen for years in the development of Linux, which is sometimes, 00:07:48.805 --> 00:07:51.265 you know, it's not just about the technical decisions. 00:07:51.445 --> 00:07:55.365 That can actually be overshadowed by personality clashes, politics, 00:07:55.585 --> 00:08:01.485 and just people having to try to work together in the open across the world, 00:08:01.685 --> 00:08:03.545 maybe without really even knowing each other. 00:08:03.805 --> 00:08:07.405 And that can actually leave users in a lurch. You know, you might not get the 00:08:07.405 --> 00:08:11.365 tool you want, not to technical reasons, but because of people. 00:08:11.805 --> 00:08:15.165 Now, we thought Liam over at the register put it pretty well. 00:08:15.385 --> 00:08:19.145 It looks likely that Overstreet has upset too many important, 00:08:19.465 --> 00:08:21.945 influential people and hurt too many feelings. 00:08:22.145 --> 00:08:28.065 And as a result, Linux is not going to get a new next-gen copy-on-write file system. 00:08:28.305 --> 00:08:33.045 It's a significant technological loss, and it's all down to people not getting 00:08:33.045 --> 00:08:37.025 along, rather than the shared desire to create a better OS. 00:08:37.525 --> 00:08:41.245 I think that is well put. I'm on the record of thinking this is an extremely 00:08:41.245 --> 00:08:42.585 important file system for Linux. 00:08:43.465 --> 00:08:48.705 And my takeaway is, and I say this, I don't like saying this at all because 00:08:48.705 --> 00:08:51.425 I have so much respect for the individuals involved. They're really titans. 00:08:51.845 --> 00:08:55.225 We stand on their shoulders and, you know, they're smarter than me. 00:08:55.325 --> 00:08:56.585 They've accomplished more than me. 00:08:57.405 --> 00:09:00.465 They're great individuals. And yet, 00:09:00.825 --> 00:09:07.765 as happens to anyone who is in a position of power and maybe some comfort for 00:09:07.765 --> 00:09:12.005 a while, they lose touch with the people on the ground and they become more 00:09:12.005 --> 00:09:13.405 and more out of touch over time. 00:09:13.725 --> 00:09:17.065 And I think we're seeing the signs of that right here. And I get no joy in saying 00:09:17.065 --> 00:09:20.645 this, but they don't have the hunger to make Linux competitive anymore. 00:09:21.185 --> 00:09:25.925 And they don't understand the situation out here on the ground or facing because 00:09:25.925 --> 00:09:27.325 they don't deal with these things anymore. 00:09:28.065 --> 00:09:31.045 I would bet you if you polled them, most of them are probably using Extended 4. 00:09:32.418 --> 00:09:35.558 So the people that are probably perfectly comfortable with the way things are 00:09:35.558 --> 00:09:40.258 right now are put in a position to make a decision over personality conflict. 00:09:41.058 --> 00:09:45.358 And it makes the operating system less competitive. There will be ways to run 00:09:45.358 --> 00:09:48.858 BcacheFS, and no doubt we will cover those ways and we will use those ways. 00:09:49.278 --> 00:09:54.398 But when you don't include it in the kernel, you are going to always exclude 00:09:54.398 --> 00:09:59.038 a certain niche of users, maybe embedded systems or something like that. 00:10:00.098 --> 00:10:04.218 And it doesn't provide the level of guarantee that a file system built into 00:10:04.218 --> 00:10:07.718 the kernel does when you do upgrades and, you know, update your bootloaders 00:10:07.718 --> 00:10:08.898 and your kernels and your whatnots. 00:10:09.338 --> 00:10:14.218 So it's a downgrade in functionality for what is a very competitive and impressive file system. 00:10:15.858 --> 00:10:20.958 And this was going to be one of the answers to not having ZFS in the kernel. 00:10:22.218 --> 00:10:25.278 This is another issue that the kernel developers have been ignorant, 00:10:25.458 --> 00:10:26.678 arrogant, and out of touch on. 00:10:27.918 --> 00:10:32.118 And so Bcash FS was a solution to this that took the pressure off of the ZFS issue. 00:10:33.618 --> 00:10:37.098 But they're too blind by their own egos to appreciate the stakes here. 00:10:38.298 --> 00:10:43.358 We literally are making decisions based on feels now. And my last point on this. 00:10:44.598 --> 00:10:48.798 The tone is set from the top. You set the tone from the top. 00:10:49.098 --> 00:10:53.998 And Kent is being persecuted for things that are no worse than have been said 00:10:53.998 --> 00:10:55.418 by Ted or Linus themselves. 00:10:55.418 --> 00:11:00.938 Just two weeks ago Linus told an individual that their code made the world a 00:11:00.938 --> 00:11:06.298 worse place you set the tone from the top so how do you persecute Kent who hasn't 00:11:06.298 --> 00:11:07.678 even said anything that hostile, 00:11:08.438 --> 00:11:13.418 when the leadership acts like that all the time and if we zoom out over the 00:11:13.418 --> 00:11:15.698 30 years of which Kent is familiar with, 00:11:16.498 --> 00:11:19.218 the dialogue was even more let's say robust, 00:11:20.078 --> 00:11:24.378 so we have 30 years of the tone being set from the top. 00:11:26.308 --> 00:11:30.988 And then all of a sudden, we just shut the door on that. And as a result, 00:11:31.248 --> 00:11:34.628 everyone listening to this podcast loses out. 00:11:36.188 --> 00:11:40.868 Everyone running Linux. And there's not even a good technical reason. 00:11:42.408 --> 00:11:43.648 This is where we're at now. 00:11:45.228 --> 00:11:49.528 It's pretty embarrassing. That's my take, at least. Hopefully this gets worked out. 00:11:49.628 --> 00:11:53.948 It's still, you know, it's an in-fluid situation. 00:11:54.628 --> 00:11:55.988 It's a dynamic situation. 00:11:56.308 --> 00:12:01.148 So there was some talk in it. I guess to hear Kent talk, it almost happened 00:12:01.148 --> 00:12:05.468 that for 6.17, he was able to find an intermediary, you know, 00:12:05.548 --> 00:12:08.448 to sort of be the person interacting with the mailing list that wasn't Kent. 00:12:08.648 --> 00:12:12.668 But of course, that's a tough job between being acceptable to Kent and knowing 00:12:12.668 --> 00:12:15.668 and being able to work well with the upstream Linux community. 00:12:15.668 --> 00:12:19.888 So that might be something we see in a future somewhere. And I saw over on the 00:12:19.888 --> 00:12:24.988 BcacheFS subreddit, a ZFS dev coming over and chatting with folks there and 00:12:24.988 --> 00:12:26.248 offering a lot of really constructive, 00:12:26.448 --> 00:12:31.048 concrete advice about, you know, if DKMS or similar is going to be the main 00:12:31.048 --> 00:12:34.508 way to run this file system for a while. There are advantages to that. 00:12:35.028 --> 00:12:38.068 There are some tips were shared, which is great. It's not like this is pure 00:12:38.068 --> 00:12:41.228 antagonism between all of these file system developers. I don't want that to 00:12:41.228 --> 00:12:42.648 be the picture people get here. 00:12:43.008 --> 00:12:45.928 And Kent has committed, it sounds like, to being, you know, pretty aggressive. 00:12:45.928 --> 00:12:52.028 Of so there won't be a ton of lag issues so you know 6.17.0 or whatever you 00:12:52.028 --> 00:12:56.448 know one of the first kernels that you might actually run should have good support. 00:12:56.448 --> 00:13:01.488 Yeah so we can now have a long distance relationship with bcachefs i will. 00:13:01.488 --> 00:13:04.728 Say too i just want to be clear like i don't think we're trying to say kent 00:13:04.728 --> 00:13:08.008 hasn't done you know hasn't had issues here i'm not trying to defend all of 00:13:08.008 --> 00:13:11.848 the statements by kent or say that there couldn't be a lot of improvements on that side too. 00:13:11.848 --> 00:13:12.688 I agree but. 00:13:12.688 --> 00:13:14.528 The end result is is definitely disappointing. 00:13:14.528 --> 00:13:19.508 Yeah there's some frustration too that Kent couldn't have adapted his approach 00:13:19.508 --> 00:13:23.868 and communication style much earlier in all of this there has been several off-ramps 00:13:23.868 --> 00:13:27.948 along the way that he could have taken here and that I think is on Kent and 00:13:27.948 --> 00:13:32.328 that's just my opinion so it's not all the kernel developers but there is just this, 00:13:32.928 --> 00:13:35.588 I don't I'm gonna I'll punt it to the audience to tell me if you think I'm off on this but 00:13:35.588 --> 00:13:38.708 I just think there is this extreme irony 00:13:38.708 --> 00:13:42.948 in individuals who have been called toxic and are 00:13:42.948 --> 00:13:47.768 now calling someone else toxic and it's just they're doing to someone what has 00:13:47.768 --> 00:13:51.448 been attempted to be done to them and it's i don't like it i don't know boost 00:13:51.448 --> 00:13:54.748 in you know my thoughts on bcashfs have been clear how do you feel about this 00:13:54.748 --> 00:13:59.008 entire situation let us know because uh it's got me fired up. 00:14:00.314 --> 00:14:02.894 I am hopeful that there will be either some sort of, like Wes said, 00:14:02.954 --> 00:14:06.534 intermediary or a pretty straightforward approach. 00:14:06.774 --> 00:14:10.414 Kent is all over the kernel development cycle, so I have no doubt, 00:14:10.414 --> 00:14:14.634 like, the day that the kernel ships stable, he'd probably have an update. It's a solution. 00:14:15.434 --> 00:14:19.694 It's one I shouldn't have to use, but it's a solution. Let's talk about something 00:14:19.694 --> 00:14:22.874 kind of fun. This is interesting. 00:14:23.474 --> 00:14:27.974 Ubuntu has committed to developing a new dangerous desktop image. 00:14:28.574 --> 00:14:33.434 Yeah, they're calling it the Dangerous Edition. It's daily builds, 00:14:33.454 --> 00:14:38.954 and all the applications are snaps pulled from the edge channel for the snap. 00:14:39.594 --> 00:14:43.734 So it's the absolute newest, raw, most experimental snap versions. 00:14:44.354 --> 00:14:50.534 And the idea here is to make it easier for devs to seed snaps during what they 00:14:50.534 --> 00:14:54.194 call their spike development, kind of like their sprints, which can last for like six weeks. 00:14:54.934 --> 00:14:59.854 And then they can focus deeply on one thing and this could be a time to get that stuff involved 00:15:00.274 --> 00:15:04.114 recently that was done with tpm full disk encryption work and the next spike 00:15:04.114 --> 00:15:08.334 is the desktop prompting client i suppose i think this is really interesting 00:15:08.334 --> 00:15:11.114 obviously it's not meant for end users to run on the daily but, 00:15:13.072 --> 00:15:17.392 I like that they're calling it the dangerous version, the Ubuntu Dangerous Desktop. 00:15:17.392 --> 00:15:18.892 I think that's a great name. 00:15:19.032 --> 00:15:22.672 And it really conveys like, hey, don't run this as your daily driver. 00:15:22.832 --> 00:15:27.472 But if you need access or if you're working on something developing, this is where to go. 00:15:27.832 --> 00:15:30.912 I think it's neat, too, because previously, right, this was all kind of work 00:15:30.912 --> 00:15:34.032 that I'm sure many developers, people hacking on this stuff, 00:15:34.232 --> 00:15:36.272 were doing already in various different ways. 00:15:36.472 --> 00:15:40.212 So the more you do it faster and make it available upstream so that you have 00:15:40.212 --> 00:15:43.252 a common shared base to start development from that's refreshed often, 00:15:43.792 --> 00:15:46.692 I mean, that's just less work for more people, which is great. 00:15:46.972 --> 00:15:50.792 We did get some more details here. Canonical engineer Tim Anderson of the Ubuntu 00:15:50.792 --> 00:15:56.132 release management team had a nice summary of these new dangerous desktop images, 00:15:56.312 --> 00:16:01.072 saying, quote, we're currently working on building what we're calling dangerous images. 00:16:01.392 --> 00:16:04.632 They'll be the same as daily desktop images for the Devel series, 00:16:04.832 --> 00:16:08.392 but all of the snaps will be on their respective edge channels. 00:16:08.832 --> 00:16:12.172 This work is ongoing, and there's going to be some more news soon. 00:16:12.552 --> 00:16:16.772 These images are intended to help developers who work on our seeded snaps. 00:16:17.252 --> 00:16:21.092 During the TPM full disk encryption spike earlier this year, 00:16:21.412 --> 00:16:24.632 all the snaps for daily builds were switched to edge to help those developers. 00:16:24.952 --> 00:16:29.472 And these dangerous images will remove the need to do this in future spikes, 00:16:29.732 --> 00:16:31.492 one of which starts on Monday. 00:16:32.092 --> 00:16:37.192 For those who are unaware, within Canonical, we've started doing spikes this cycle. 00:16:37.452 --> 00:16:42.292 Spikes are segments of the whole cycle, six weeks long, where members of varying 00:16:42.292 --> 00:16:46.872 teams join together to focus on one topic, partially or entirely, 00:16:47.352 --> 00:16:49.292 leaving behind their regular daily duties. 00:16:49.992 --> 00:16:54.412 There was a spike just after the Frankfurt sprint, working on TPM-based full 00:16:54.412 --> 00:16:57.092 disk encryption, and the next spike, which starts this week, 00:16:57.232 --> 00:16:59.872 focuses on the desktop prompting client. 00:17:00.472 --> 00:17:04.792 You know, imagine that for a moment. You know, you're going about your daily 00:17:04.792 --> 00:17:10.452 job and then there's this six week period where you sort of leave behind the 00:17:10.452 --> 00:17:14.012 daily grind and just focus on one thing. 00:17:15.495 --> 00:17:18.315 It kind of sounds incredible, actually. I think I would love that. 00:17:18.555 --> 00:17:21.095 Yeah, you know, you get some diversity in your workload. Plus, 00:17:21.375 --> 00:17:24.595 I mean, it seems to make a lot of sense where normally these sort of cross-cutting 00:17:24.595 --> 00:17:27.075 concerns, you know, you have to have new emails or, you know, 00:17:27.195 --> 00:17:30.835 DM messages or team channels to try to pull people out of their daily work. 00:17:30.955 --> 00:17:34.775 So this is some blessed time where everyone across the stack can focus on one 00:17:34.775 --> 00:17:36.715 thing, which I mean, that seems pretty useful. Right. 00:17:36.875 --> 00:17:39.875 You would presume everybody's on board with the idea so you could actually pull 00:17:39.875 --> 00:17:42.915 it off, which is, that's probably the secret trick. 00:17:43.095 --> 00:17:45.355 But we have a little bit more Ubuntu news, Brantley. 00:17:45.495 --> 00:17:49.275 Indeed, from Pharaonics this time, we get a few extra details. 00:17:49.375 --> 00:17:53.855 Knuckle is sticking to the promise of always shipping the latest upstream kernel. 00:17:54.295 --> 00:18:04.255 That means Ubuntu 25.10 will launch with Linux 6.17, even if it is still an unstable RC release. 00:18:04.995 --> 00:18:09.835 Now, this timing is tight. Ubuntu's kernel freeze is September 25th, 00:18:09.955 --> 00:18:15.135 while Linux 6.17's stable release is expected September 28th. 00:18:15.135 --> 00:18:21.715 So just a few days later, the kernel team says it'll likely ship the near final RC, 00:18:22.035 --> 00:18:27.215 which should still be, they say, very close to stable and highlights in 6.17 00:18:27.215 --> 00:18:33.235 include Intel's XC3 graphics by default on Panther Lake and other major hardware improvements. 00:18:33.535 --> 00:18:39.855 So once 6.17 goes stable, Ubuntu will push it out as quickly as a stable update. 00:18:40.735 --> 00:18:46.835 And we got a bit more from Brett Grombois on behalf of the Canonical Kernel team, 00:18:47.195 --> 00:18:53.255 saying, With the recent release of Linux 6.16, we now have a much clearer idea 00:18:53.255 --> 00:19:00.535 of when 6.17 is likely to be released, as of this writing being tentatively September 28th, 2025. 00:19:01.055 --> 00:19:06.075 The current 25.10 release schedule has kernel freeze set at September 25th, 00:19:06.195 --> 00:19:11.015 which means that there is a strong possibility that linux 617 will still be 00:19:11.015 --> 00:19:17.675 in a final rc state at the time the kernel needs to be frozen for the 2510 final release they're. 00:19:17.675 --> 00:19:18.275 Sticking to it. 00:19:18.275 --> 00:19:22.955 Yeah it's impressive especially because you know i i feel like five years ago 00:19:22.955 --> 00:19:25.675 you wouldn't imagine this would really even be possible. 00:19:27.640 --> 00:19:32.060 This does feel quite bold from Ubuntu, which I like. I like this new flavor. 00:19:32.360 --> 00:19:35.740 I think they're pushing the envelope a little bit compared to what's been done 00:19:35.740 --> 00:19:39.680 in the last several years. And I'm looking forward to what's coming out of this. 00:19:39.980 --> 00:19:44.280 I also think it speaks well for the kernel development process, right? 00:19:44.340 --> 00:19:48.980 This is canonical saying we trust the kernel team enough to ship these RCs, 00:19:49.040 --> 00:19:51.720 knowing that we can ship a stable and there's not going to be big regressions. 00:19:52.060 --> 00:19:56.600 Yeah, that's true. Good point. And they're also, though, committing to shipping 00:19:56.600 --> 00:20:00.840 that stable release basically as fast as they can, which does mean you're going 00:20:00.840 --> 00:20:04.020 to get a new system installed, and then a few days later, you'll get an update. 00:20:04.240 --> 00:20:08.060 So you might just wait a week or two and then upgrade. But I like that they're 00:20:08.060 --> 00:20:11.860 doing this, and it is combined with a series of data points we're seeing come 00:20:11.860 --> 00:20:17.140 out of Canonical, where there definitely seems to be a bit more focus behind the desktop now. 00:20:17.860 --> 00:20:22.480 And pushing, like, we see this dangerous release, and now we see them committing to, okay, 00:20:23.120 --> 00:20:25.920 you know, we're not going to hit the stable, so we're going to ship the RC, 00:20:26.020 --> 00:20:31.480 but that means, you know, if you're using Intel Z83 graphics or whatever on 00:20:31.480 --> 00:20:33.200 Panther Lake, you're going to be good to go here. 00:20:33.280 --> 00:20:38.600 And when these are midterm releases between LTSs, I think that's a really smart strategy. 00:20:38.820 --> 00:20:41.100 So props to see them follow through with it. 00:20:41.880 --> 00:20:46.320 You know what? Promise made, promise kept. Now, one of my favorite tools that 00:20:46.320 --> 00:20:50.900 I've been using for almost a decade, I think, just finally hit 2.0. 00:20:51.600 --> 00:20:56.060 And that project is SyncThing. Yes, that's right, the thing secretly running 00:20:56.060 --> 00:20:57.960 pretty much all of Chris's infrastructure. 00:20:58.540 --> 00:21:02.760 It's finally hit version 2.0, the first release in a new series. 00:21:03.300 --> 00:21:08.080 And, well, like any first release in a new series, users should probably expect 00:21:08.080 --> 00:21:12.000 a few rough edges, because there are big changes under the hood. 00:21:12.200 --> 00:21:16.540 For one, the database backend now uses SQLite instead of LevelDB, 00:21:16.820 --> 00:21:21.440 and that means a one-time migration at first launch of this new release and 00:21:21.440 --> 00:21:24.180 that might take a while if you've got a big database. 00:21:24.540 --> 00:21:24.960 Uh-oh. 00:21:25.120 --> 00:21:29.500 Logging has also been overhauled, structured entries per package log levels, 00:21:29.520 --> 00:21:32.500 and a new warning level between info and error. 00:21:32.640 --> 00:21:36.800 So that's going to be nice. But if you have filters or alerts based on the existing 00:21:36.800 --> 00:21:39.200 logging format, those are going to need to be updated. 00:21:39.540 --> 00:21:42.500 You know, what's funny is it seems like all these tools too are, 00:21:43.260 --> 00:21:47.820 they're reinvesting in the command line interface again just after the two-week challenge? 00:21:48.220 --> 00:21:53.280 Yeah, what's the deal with that? The command line interface has been modernized in SyncThing 2.0. 00:21:53.460 --> 00:21:58.700 Long options now require double dashes. Some are renamed. Others got moved to subcommands. 00:22:00.343 --> 00:22:03.723 Here's a nice change, too. Deleted files are no longer stored forever. 00:22:03.963 --> 00:22:08.763 By default, they're forgotten after six months, though you can change that in a setting. 00:22:09.543 --> 00:22:14.143 There's also no more default folder on First Startup, and SyncThing now uses 00:22:14.143 --> 00:22:18.183 three parallel connections by default between devices. I mean, 00:22:18.323 --> 00:22:19.523 that sounds like a good thing. 00:22:20.223 --> 00:22:24.643 That's the way to do it. That is the way to do it. I have heard some reports. 00:22:24.843 --> 00:22:28.743 I have not verified because I don't do this, but I've heard some reports that 00:22:28.743 --> 00:22:32.663 SyncThing 2.0 might not be compatible with SyncThing on Android right now. 00:22:33.303 --> 00:22:37.063 So verify that before you upgrade. I've heard some people report that. 00:22:37.263 --> 00:22:38.483 I have not verified that. 00:22:38.803 --> 00:22:40.803 Something else that might not 00:22:40.803 --> 00:22:45.523 be so great, some older platforms are losing official pre-built binaries. 00:22:45.663 --> 00:22:48.183 I don't know if this is like totally dropping support, they're just no longer 00:22:48.183 --> 00:22:51.943 going to build these, but that includes Dragonfly BSD, Illumos, 00:22:52.083 --> 00:22:57.483 Solaris, NetBSD, OpenBSD on 32-bit in ARM and Windows on ARM. 00:22:57.763 --> 00:23:03.203 So maybe if you're on one of those, do your homework before trying to switch to 2.0. 00:23:03.903 --> 00:23:09.283 There's also some new features here, including ED25519 keys for secure connections, 00:23:09.743 --> 00:23:14.663 bandwidth limits for your LAN, and quick UDP port mapping support. 00:23:15.063 --> 00:23:15.823 That's nice. 00:23:16.243 --> 00:23:19.383 And of course, like any release, you've got dozens of bug fixes, 00:23:19.603 --> 00:23:22.943 you've got other performance improvements, you've got all of that database work, 00:23:23.083 --> 00:23:27.123 improvements to file syncing, improvements to the GUI and the TUI as we talked 00:23:27.123 --> 00:23:31.723 about so maybe don't commit your whole infra to switching to it right away but 00:23:31.723 --> 00:23:34.263 do go start playing with it and check it out. 00:23:34.263 --> 00:23:38.043 Yeah I think I need to look at I think I need to look at it because I do run 00:23:38.043 --> 00:23:42.383 it on a lot of systems one of the things I've done if I have also I've deployed 00:23:42.383 --> 00:23:46.023 it I don't sync everything to it but I've deployed one on a VPS that I kind 00:23:46.023 --> 00:23:50.303 of use as a go-between and then do multiple connections off of that because 00:23:50.303 --> 00:23:51.603 the VPS as a super fast connection. 00:23:52.682 --> 00:23:56.922 I really, really appreciate the Sync Thing project, and there really isn't a 00:23:56.922 --> 00:23:59.702 lot of opportunity to talk about it because they don't have a lot of major releases, 00:23:59.922 --> 00:24:01.482 which is sort of what generates the news cycle. 00:24:01.622 --> 00:24:06.382 So it's nice to take a moment here and just appreciate something that's worked for me for over a decade. 00:24:07.142 --> 00:24:10.502 I found it in the wake of BitTorrent Sync, and it's just been fantastic ever since. 00:24:10.682 --> 00:24:14.902 It really has. And I think as, you know, folks who listen to the member stream 00:24:14.902 --> 00:24:19.362 can attest, the fact that we haven't really heard you complaining about it in 00:24:19.362 --> 00:24:22.662 the past five years says a lot about the project. 00:24:23.262 --> 00:24:30.882 That's a good point. Well, boys, my week was really made when the Open Home 00:24:30.882 --> 00:24:34.902 Foundation and Home Assistant made some big, big news. 00:24:35.042 --> 00:24:39.002 So a little backstory here. I love Z-Wave. It's a wireless communications protocol, 00:24:39.102 --> 00:24:45.102 and one of the reasons I really like it is it operates at the 800 to 900 megahertz range. 00:24:45.262 --> 00:24:49.442 Here in the U.S. and Canada, it's 908.42 megahertz specifically. 00:24:50.162 --> 00:24:52.802 And a lot of the alternatives, which are better in some ways, 00:24:52.842 --> 00:24:55.962 like licensing, are worse in other ways that really matter. 00:24:56.082 --> 00:25:00.862 Like they use the 2.4 gigahertz frequency, as we all know, a very busy frequency. 00:25:01.422 --> 00:25:05.442 Even just turning on your microwave kind of blasts it out. It also doesn't travel 00:25:05.442 --> 00:25:10.002 through walls as well as 900 megahertz does and doesn't quite reach the same distance. 00:25:10.442 --> 00:25:14.122 But it really hasn't gotten much attention lately. They kind of made the QT 00:25:14.122 --> 00:25:18.822 mistake where they had sort of a aggressive license and certification process at first. 00:25:19.142 --> 00:25:23.602 And then they've rectified that over the years. But it left a window of opportunity 00:25:23.602 --> 00:25:26.342 for competitors like Matter and Zigbee and others to emerge. 00:25:26.962 --> 00:25:30.002 And I thought, OK, we're not hearing about it much lately. 00:25:30.602 --> 00:25:33.862 These other things are out. They're open source. I really should start to adopt 00:25:33.862 --> 00:25:36.702 them. And I started getting more and more gear there on these other protocols. 00:25:37.342 --> 00:25:42.482 Started slowly accepting that my beloved Z-Wave was fading away. 00:25:43.202 --> 00:25:46.762 But it turns out the truth is actually quite the opposite. 00:25:47.062 --> 00:25:49.942 There was a big old Z-Wave Alliance member meeting in Austin, 00:25:50.102 --> 00:25:52.722 Texas. And the news out of there is good, boys. 00:25:53.302 --> 00:25:55.662 Home Assistant has a blog that shares a lot about the event. 00:25:55.782 --> 00:25:57.982 But I pulled some highlights that I thought were interesting. 00:25:58.702 --> 00:26:05.382 10% of all Home Assistant users use Z-Wave. which is more than 1.7 million active devices. 00:26:06.082 --> 00:26:09.282 And that's just a small percentage that actually submit their stats. 00:26:09.442 --> 00:26:10.022 Of course. 00:26:10.682 --> 00:26:14.322 And I think the key takeaway from the Z-Wave event is it isn't going anywhere. 00:26:14.322 --> 00:26:15.962 In fact, it's seemingly thriving. 00:26:16.642 --> 00:26:20.682 But the Home Assistant team in Polis, they really encourage them to open up further, 00:26:21.911 --> 00:26:25.391 just really participate more in the community and they 00:26:25.391 --> 00:26:28.271 put their money where their mouth is and they have released an 00:26:28.271 --> 00:26:31.491 incredible piece of hardware for z-wave users and 00:26:31.491 --> 00:26:34.311 if you're looking at home automation tap the brakes and 00:26:34.311 --> 00:26:37.851 look at the home assistant connect zwa2 it is 00:26:37.851 --> 00:26:40.971 their z-wave antenna and it is brilliant 00:26:40.971 --> 00:26:43.911 first of all it's big but they have engineered the 00:26:43.911 --> 00:26:46.831 absolute snot out of this thing the results are 00:26:46.831 --> 00:26:50.251 incredible so it's 69 us 59 euros 00:26:50.251 --> 00:26:53.911 it's designed to really give you the absolute optimal range 00:26:53.911 --> 00:26:59.591 possible they've had some incredible incredible experiments now of course there's 00:26:59.591 --> 00:27:03.051 two to tango so your device you're communicating to us to have a decent antenna 00:27:03.051 --> 00:27:09.611 and this also supports the z-wave long range protocol which is extremely fast 00:27:09.611 --> 00:27:12.151 and it's built on the new Z-Wave 800 chip. 00:27:13.051 --> 00:27:17.771 Which is, it's like a whole new SoC, essentially. It's not quite the same thing, but it's way faster. 00:27:18.491 --> 00:27:22.511 And the nice thing is, is because it's made by Home Assistant, it's a seamless setup. 00:27:22.611 --> 00:27:25.991 You plug it in, Home Assistant detects it, it knows your region automatically, 00:27:26.191 --> 00:27:29.431 it guides you through a setup, it'll guide you through migrating to the new one. 00:27:30.191 --> 00:27:34.131 It's open, it's hackable, it's absolutely all offline, privacy first. 00:27:34.371 --> 00:27:40.031 Open firmware files, you'll get over-the-air updates to it, no cloud reliance at all. 00:27:40.371 --> 00:27:43.491 You buy it once, and then you own it, and it looks great. 00:27:43.951 --> 00:27:48.071 The base looks a lot like their voice preview box, and then it goes up into 00:27:48.071 --> 00:27:51.491 this antenna where they've built this really powerful antenna inside, 00:27:51.531 --> 00:27:53.951 and then on the top it has a little LED light that tells you the status, 00:27:53.971 --> 00:27:54.891 which you can also turn off. 00:27:55.431 --> 00:27:58.491 It really, I think, is going to up the reliability of a Z-Wave network, 00:27:58.551 --> 00:28:01.531 and this is going to slow my role on all the other protocols so much. 00:28:01.531 --> 00:28:06.251 I was starting to really start going to Zigbee and Z-Wave, and I could not make 00:28:06.251 --> 00:28:07.671 Zigbee as reliable as Z-Wave. 00:28:08.491 --> 00:28:12.911 It's just not the same level. And then I started putting more devices on Wi-Fi, 00:28:13.051 --> 00:28:13.831 which isn't great either. 00:28:14.810 --> 00:28:18.210 So to be able to rely on Z-Wave again, to see their investment in this, 00:28:18.290 --> 00:28:20.590 to see this hardware, I pulled the trigger immediately. 00:28:20.990 --> 00:28:25.270 It may arrive today, actually, during the show. And I was recently talking on 00:28:25.270 --> 00:28:28.430 the podcast here about wanting to redo my Home Assistant setup. 00:28:29.130 --> 00:28:32.430 And I was concerned about the Z-Wave migration. Well, problem solved. 00:28:32.570 --> 00:28:34.010 I'm going to plug this into my Home Assistant. 00:28:34.170 --> 00:28:37.510 I'm going to migrate to this thing. And then I'll unplug it and plug into the new Home Assistant. 00:28:38.290 --> 00:28:42.790 And it's a gorgeous piece of engineering. And they have some YouTube videos, 00:28:42.810 --> 00:28:46.410 which I'll link in the show notes. The range demonstrations are absolutely bonkers. 00:28:46.570 --> 00:28:51.010 So if you have a large garden or even a farm, you could actually put sensors 00:28:51.010 --> 00:28:54.850 and devices way out there and they'll still communicate with this thing, 00:28:54.930 --> 00:28:56.030 especially in long range mode. 00:28:56.310 --> 00:28:58.810 They were seen in testing up to 1.5 kilometers. 00:28:59.730 --> 00:29:04.070 Really incredible. And to see the whole combination, they support the open source 00:29:04.070 --> 00:29:05.450 community, the open development. 00:29:05.730 --> 00:29:08.790 They're paying for one of the developers to continue to contribute to that. 00:29:08.790 --> 00:29:14.670 And now they've released this piece of hardware that is open and hackable, all offline. 00:29:16.190 --> 00:29:19.030 Love to see this kind of stuff. This is it. 00:29:19.270 --> 00:29:24.530 And the Home Assistant platform is going from fantastic win to fantastic win, 00:29:24.650 --> 00:29:27.310 both in software features and hardware devices. 00:29:27.450 --> 00:29:29.650 They're selective about the hardware they release. 00:29:29.970 --> 00:29:33.870 They're super laser targeted. And every time it makes a ton of sense. 00:29:34.130 --> 00:29:37.670 And every time it's just validating to be in this ecosystem when I see this kind of stuff. 00:29:38.290 --> 00:29:41.850 And they've gotten to the point now where it's like they release a piece of hardware. 00:29:42.090 --> 00:29:44.430 I know it's going to be great. I know it's going to work with Home Assistant 00:29:44.430 --> 00:29:47.270 super easy. And it's not like they're using their own private, 00:29:47.330 --> 00:29:50.050 you know, a la AirPod style way to connect it. 00:29:50.130 --> 00:29:53.990 Like the technology they use to make this work tremendously seamlessly with 00:29:53.990 --> 00:29:57.010 Home Assistant is available to any vendor in any hardware device. 00:29:57.130 --> 00:29:58.130 And it's all open standards. 00:30:00.002 --> 00:30:01.562 I don't know if you can tell, but I'm kind of excited. 00:30:02.182 --> 00:30:05.582 Whatever happened to Matter, can I ask? Because I thought for a minute you were 00:30:05.582 --> 00:30:09.562 checking that out too. And I haven't heard much after kind of some initial excitement. 00:30:10.002 --> 00:30:16.082 You know, it's still, it's, you know, it's still, you know, it's out there. It's been slow to adopt. 00:30:16.722 --> 00:30:21.982 And most of the implementations, although not required, most implementations just use 2.4 gigahertz. 00:30:22.722 --> 00:30:26.782 So it's kind of like just a new version of Zigbee. And it has a lot of the core 00:30:26.782 --> 00:30:28.522 problems that 2.4 gigahertz has. 00:30:30.082 --> 00:30:32.062 And so at the end of the day, like there's other ways to do it. 00:30:32.162 --> 00:30:34.642 There's a thread pro. There's other ways they can implement it with Matter. 00:30:34.882 --> 00:30:37.682 The spec allows for that. But you can even use Bluetooth. 00:30:37.882 --> 00:30:41.242 But it's up to manufacturers to actually choose to go that route. 00:30:41.402 --> 00:30:43.862 And with Z-Wave, you kind of get that by default. Okay. 00:30:44.102 --> 00:30:47.242 Yeah. And, you know, this whole stack, right? It's all open source. 00:30:47.542 --> 00:30:51.422 It's a lot of it's Python based. And then it's running on top of Linux. 00:30:51.662 --> 00:30:53.462 And then the hardware you connect is open. 00:30:53.922 --> 00:30:58.022 And it's backed by the Open Home Foundation, who has the super long-term view of this. 00:30:58.022 --> 00:31:03.842 So it's the exact 180 from buying some cloud-connected smart device off of Amazon 00:31:03.842 --> 00:31:06.722 or from Costco that lasts for three years, and then you've got to throw it away, 00:31:06.822 --> 00:31:09.622 and you have to sign up with their app and their cloud service. 00:31:09.622 --> 00:31:13.722 It's the 180 of all of that, and it's exactly the kind of thing you want to put in your home. 00:31:13.782 --> 00:31:17.022 You want to put something in your home that's going to last a decade, right? 00:31:17.722 --> 00:31:20.502 If you put that in the wall or you put that somewhere where it automates that 00:31:20.502 --> 00:31:22.662 thing, you want it to last as long as the house lasts. 00:31:22.762 --> 00:31:25.062 That's my goal. Everything I'm building that I put into Joops, 00:31:25.562 --> 00:31:28.362 I don't ever want to tear out again. I want it to last forever. 00:31:28.762 --> 00:31:31.522 So everything has over-the-air updates now. 00:31:32.202 --> 00:31:36.602 Nothing requires a cloud account. Nothing requires an internet connection to function. 00:31:36.962 --> 00:31:40.162 All of it works offline. All of it works without me having to open up any other 00:31:40.162 --> 00:31:42.602 apps other than Home Assistant. No other apps on my phone. 00:31:43.162 --> 00:31:46.382 And it's not that hard to get there anymore with these hardware devices they're 00:31:46.382 --> 00:31:49.662 releasing. It's powerful stuff, boys. It's a good time to get into Home Assistant. 00:31:52.951 --> 00:31:55.871 1password.com slash unplugged that's 00:31:55.871 --> 00:31:59.591 the number one password.com slash unplugged all 00:31:59.591 --> 00:32:04.071 lowercase go take the first steps to better security for your team by securing 00:32:04.071 --> 00:32:09.071 credentials and protecting every application so go learn more at 1password.com 00:32:09.071 --> 00:32:14.271 slash unplugged if you are in security if you are in it if this is your world 00:32:14.271 --> 00:32:17.771 then you know about the mountain of assets that you have to protect more than 00:32:17.771 --> 00:32:19.171 ever, devices, identities, 00:32:19.491 --> 00:32:21.471 and applications. 00:32:21.871 --> 00:32:25.031 And the more applications, the more security risks you have. 00:32:25.691 --> 00:32:30.471 That's where 1Password Extended Access Management comes in. This is a growing 00:32:30.471 --> 00:32:31.591 problem. You're not the only one. 00:32:32.131 --> 00:32:36.551 Over half of ITPro surveyed said that when they were asked what their biggest 00:32:36.551 --> 00:32:39.631 concern was, it was SaaS sprawl. 00:32:39.711 --> 00:32:45.031 It was securing these SaaS applications, especially the ones they don't even know about. 00:32:45.871 --> 00:32:47.571 That quickly becomes your responsibility. 00:32:48.471 --> 00:32:52.531 Well, Trelica by 1Password can discover and secure access to all your apps, 00:32:52.651 --> 00:32:54.891 the managed and the unmanaged apps. 00:32:55.251 --> 00:32:59.611 Trelica by 1Password inventories every app in use at the company. 00:32:59.791 --> 00:33:04.011 And then it has pre-populated app profiles that it can assess the different SaaS risks. 00:33:04.651 --> 00:33:08.471 It lets you manage access, optimize spend, and enforce security best practices 00:33:08.471 --> 00:33:10.671 across every app your employees use. 00:33:10.811 --> 00:33:15.111 Yes, you can manage shadow IT. When I used to show up as a contractor to these 00:33:15.111 --> 00:33:18.971 companies and get on their network, I mean, nine out of ten times, 00:33:19.171 --> 00:33:22.751 the IT would be completely ignorant to the fact that a new device was on their 00:33:22.751 --> 00:33:23.591 network wrecking havoc. 00:33:23.831 --> 00:33:26.351 I mean, of course, I was supposed to be wrecking havoc. 00:33:27.451 --> 00:33:31.571 This is the difference, though, now. We have this whole new generation with 00:33:31.571 --> 00:33:34.791 1Password Extended Access Management and Trelica by 1Password. 00:33:35.471 --> 00:33:38.911 It's a complete solution for SaaS access governance. And it's just one of the 00:33:38.911 --> 00:33:40.151 ways that extended access management 00:33:40.151 --> 00:33:43.991 helps teams strengthen compliance and security at the same time. 00:33:44.471 --> 00:33:46.331 One does not have to take away from the other. 00:33:47.331 --> 00:33:50.051 1Password's award-winning password manager, which is trusted by millions, 00:33:50.491 --> 00:33:54.931 over 150,000 businesses like IBM and Slack, well, now they're securing more 00:33:54.931 --> 00:33:58.711 than just passwords with 1Password Extended Access Management and Trelica. 00:33:58.971 --> 00:34:02.111 So go check it out. Go to 1Password.com slash unplugged. 00:34:02.171 --> 00:34:06.611 Be the IT hero in your corporation. Take the first step to better security for 00:34:06.611 --> 00:34:10.571 your team by securing credentials and protecting every application, 00:34:10.871 --> 00:34:12.371 even the unmanaged shadow IT. 00:34:12.851 --> 00:34:17.511 Go learn more. Support the show. Go to 1Password.com slash unplugged. 00:34:18.091 --> 00:34:21.611 That's 1Password.com slash unplugged. 00:34:25.101 --> 00:34:30.641 Now, Chris, last week you featured your brand new desktop, all riced up and looking delicious. 00:34:31.721 --> 00:34:35.301 And I feel like you weren't quite done with that. 00:34:35.981 --> 00:34:40.341 Based on our private chats this week, it sounds like most of your free time 00:34:40.341 --> 00:34:42.641 went towards continuing that project. 00:34:43.401 --> 00:34:44.921 What is going on over there? 00:34:45.481 --> 00:34:48.301 Yeah, remember how I said I was not going to mess with it anymore and I was 00:34:48.301 --> 00:34:51.681 done and I was just, you know, I got it out of my system and I was just going to move on. 00:34:52.601 --> 00:34:57.881 That wasn't true. No, no, no, that was not true at all. In fact, it's getting serious. 00:34:58.401 --> 00:35:01.301 I'm ready to take this thing home to mom and dad for dinner. 00:35:01.961 --> 00:35:06.001 Whoa, whoa, whoa. Yeah. What is that? Okay, so when we were at Red Hat Summit, 00:35:06.381 --> 00:35:11.441 you kind of bailed ship. You went whole hog on a U-Blue lifestyle. 00:35:12.721 --> 00:35:14.561 What does that mean? 00:35:15.681 --> 00:35:19.981 I think it means the grand experiment, which was a lot of fun. 00:35:20.461 --> 00:35:22.321 The days on Bluefin are over. 00:35:24.921 --> 00:35:29.701 I liked it but i think when you hear where i ended up everyone will understand 00:35:29.701 --> 00:35:34.441 i kind of you know i i want to take a moment and i want to blame two people 00:35:34.441 --> 00:35:36.721 specifically if i could for this i'm. 00:35:36.721 --> 00:35:37.981 Not taking the blame on this one. 00:35:37.981 --> 00:35:42.421 Because i was happy i was living in this blissful world where i didn't need 00:35:42.421 --> 00:35:46.061 to tweak my system much i didn't need to worry about performance that much yeah. 00:35:46.061 --> 00:35:48.261 That's because soltros os did all the work for you. 00:35:48.261 --> 00:35:52.241 Right soltros os comes along and does the work and I'm like oh man you can move 00:35:52.241 --> 00:35:56.761 the needle on some of this stuff you know you can make a few adjustments here 00:35:56.761 --> 00:35:59.681 and make a noticeable improvement in like the application launch time like oh 00:35:59.681 --> 00:36:03.761 of course that makes me start wanting to tweak it a little bit more and then 00:36:03.761 --> 00:36:05.881 DHH comes along with his Alma Archie, 00:36:06.441 --> 00:36:09.101 and finally shows me a Hyperland that I can appreciate, 00:36:10.308 --> 00:36:15.128 And I just, I think I just slipped into this, I'm going to build a Hyperland 00:36:15.128 --> 00:36:16.268 desktop that works for me. 00:36:16.348 --> 00:36:19.908 And it also coincided with after a summer of travel, I finally set up my home 00:36:19.908 --> 00:36:23.588 desktop PC again, which still runs an XOS because it's just been packed away. 00:36:24.328 --> 00:36:27.348 And if you caught last week's episode, you know I ended up vibe-ricing my way 00:36:27.348 --> 00:36:30.808 into a pretty, pretty sweet Hyperland desktop. 00:36:31.688 --> 00:36:37.508 And since last week, I went from like a silly, couldn't I even do this MVP self-challenge 00:36:37.508 --> 00:36:40.528 to like, now it's my dream distribution. 00:36:40.728 --> 00:36:44.748 And I think it's actually worth wider testing and other people should try it. 00:36:45.148 --> 00:36:49.648 I've been using it and refining it for over a week. And I actually think there's 00:36:49.648 --> 00:36:51.288 even a market fit for a distribution like this. 00:36:51.348 --> 00:36:55.188 And I know I'm going crazy here, but I have been seeing post after post recently 00:36:55.188 --> 00:36:59.468 on the Mastos and the Xs about how people wish somebody would come along and 00:36:59.468 --> 00:37:02.908 do an opinionated Oma Archie style Hyperland setup on NixOS. 00:37:03.168 --> 00:37:07.788 And I'm seeing a couple of people take a stab at it, But I think I might have the best one. 00:37:08.328 --> 00:37:13.688 Humbly I say, because it's not only the best-in-class open-source desktop applications 00:37:13.688 --> 00:37:17.528 that are through just years and years of us looking at all the different apps 00:37:17.528 --> 00:37:20.468 and using all the different things and reviewing all the different desktop environments, 00:37:20.788 --> 00:37:24.568 all the thousands of hours that I've done all that, that have gone into just 00:37:24.568 --> 00:37:27.328 the decisions on the apps that I'm picking with this Hypervibe, 00:37:27.488 --> 00:37:31.748 but I have done just bonkers out-of-the-box 00:37:31.748 --> 00:37:34.648 performance that I've been slowly building on for the 00:37:34.648 --> 00:37:37.468 last year um like for example i'm using 00:37:37.468 --> 00:37:41.168 the zen kernel which just as a quick aside is 00:37:41.168 --> 00:37:43.908 a great desktop kernel that i don't understand why more 00:37:43.908 --> 00:37:48.188 desktop distributions don't ship it's optimized with low latency patches to 00:37:48.188 --> 00:37:51.708 reduce input output processing delays which improve the overall feel of your 00:37:51.708 --> 00:37:55.388 desktop and gaming experience it makes it feel like your desktop more responsive 00:37:55.388 --> 00:38:00.088 it's using the bfq the budget fair queuing scheduler which gives you smoother 00:38:00.088 --> 00:38:02.288 multitasking in a desktop environment Also. 00:38:03.068 --> 00:38:05.408 Disk I.O. is better optimized for a desktop environment. 00:38:06.541 --> 00:38:10.241 And it's tweaked to have a more responsive CPU process scheduler that benefits 00:38:10.241 --> 00:38:11.201 multitasking workloads. 00:38:11.701 --> 00:38:14.821 It has preemption and real-time support if you need that. 00:38:15.161 --> 00:38:17.661 And there's a lot of little kernel parameters that have been tuned in there 00:38:17.661 --> 00:38:21.481 that just favor multimedia playback and desktop performance out of the box that 00:38:21.481 --> 00:38:24.721 you just get by using the Zen kernel. 00:38:24.901 --> 00:38:27.281 It also supports ZRAM, which I'll get to in a moment. 00:38:27.441 --> 00:38:30.881 I'm so glad you're finally here because we did, I don't remember exactly when, 00:38:30.941 --> 00:38:33.501 sometime in the last year, we did some dabbling. We were trying the licorice 00:38:33.501 --> 00:38:37.881 kernel and a few other, you know, tweaks, especially looking at getting low 00:38:37.881 --> 00:38:41.321 latency audio because, you know, we do a lot of audio work here. 00:38:41.841 --> 00:38:47.081 So since then, I've been just using the Zen kernel. I've seen no reason to switch off. 00:38:47.261 --> 00:38:51.001 And like you're talking about with the IO stuff, I mean, I've used desktop Linux 00:38:51.001 --> 00:38:54.141 long enough to know like you're doing some big transfers or other stuff with 00:38:54.141 --> 00:38:57.801 a lot of file operations and your desktop can get kind of laggy. 00:38:57.941 --> 00:39:02.421 And OK, it's not a huge deal, but that is just almost totally gone with Zen. 00:39:02.921 --> 00:39:06.241 Yeah. Yeah. And so that's just the kernel, right? 00:39:06.341 --> 00:39:11.081 And then in there, I've also utilized BPF to do auto-tuning, which is really nice. 00:39:11.281 --> 00:39:15.041 And then there's just some housekeeping items that automatically happen. 00:39:15.241 --> 00:39:18.241 The Nick store auto-optimizes and garbage collects every week. 00:39:18.481 --> 00:39:21.201 I have out of memory for certain things ready to go. 00:39:21.721 --> 00:39:25.201 Butter FS with FS trim and auto-scrub is set up even on root. 00:39:25.401 --> 00:39:28.301 And the governor is set to performance mode at a default, but you can change 00:39:28.301 --> 00:39:32.021 it. It's a Wayland-based system, and it comes completely loaded with Steam. 00:39:32.761 --> 00:39:35.481 All wired up with game scope, which if you know what that is, 00:39:35.521 --> 00:39:36.621 you realize why that's a big deal. 00:39:36.941 --> 00:39:40.281 What? Oh, I missed this in our notes. Oh, okay. 00:39:40.421 --> 00:39:43.201 Oh, yeah. Yep. Oh, yeah. I got the Lutris in there. 00:39:43.281 --> 00:39:47.121 I got all the wine stuff you need to play 64-bit and 32-bit wine games, 00:39:47.121 --> 00:39:49.141 and it has Vulkan support for all that stuff. 00:39:49.321 --> 00:39:52.461 Has UDEV rules for the controllers you might want to use with it. 00:39:53.101 --> 00:39:57.501 Steam with hardware support out of the box, ready to go, all optimized. 00:39:57.941 --> 00:39:59.401 Now, right now, the way it's built, it's, 00:40:00.371 --> 00:40:04.571 It's tilted towards AMD, but it really wouldn't be much work to make it work with NVIDIA or Intel. 00:40:05.311 --> 00:40:08.871 Got LibVert, Invert Manager out of the box. Docker's there with weekly auto 00:40:08.871 --> 00:40:13.051 prune ready to go. And then it's a Hyperland desktop that I have customized the hell out of. 00:40:13.231 --> 00:40:17.371 And so you have to build the entire thing. Everything from the toolbar to the 00:40:17.371 --> 00:40:19.371 file manager to the launcher, everything. 00:40:19.891 --> 00:40:22.911 So in here, Thunder's available, but I went with Dolphin. 00:40:23.131 --> 00:40:26.211 And to make Dolphin really, truly functional, you don't need just Dolphin. 00:40:26.331 --> 00:40:28.631 You need the KIO extras. You need the Fuse support. 00:40:29.011 --> 00:40:34.451 You need the arc package or extractor and you need u-disc so that way you can 00:40:34.451 --> 00:40:37.711 mount network shares all of that works so when you get dolphin it's a fully 00:40:37.711 --> 00:40:40.991 functional dolphin clipboard support you know i had to add the right clipboard 00:40:40.991 --> 00:40:43.911 manager right and a screenshot manager so you have all of that. 00:40:43.911 --> 00:40:48.111 You're doing a lot of work just to get back to what plasma gets you out of the gate but. 00:40:48.111 --> 00:40:48.971 It gives you a really. 00:40:48.971 --> 00:40:52.451 Nice you know look at like what pieces do you want you can swap those out in 00:40:52.451 --> 00:40:56.371 a lot easier way and you know since you got the vibe help you kind of can get 00:40:56.371 --> 00:40:58.871 a nice set out of the gate and then tweak it from there right. 00:40:58.871 --> 00:41:03.431 And it's a smaller subset right it's just you know a handful of the plasma packages 00:41:03.431 --> 00:41:08.191 which is a lot smaller of a moving target this entire thing even after all this 00:41:08.191 --> 00:41:13.111 work is so much leaner and meaner than a full genome cinnamon or plasma desktop 00:41:13.111 --> 00:41:17.931 and so because of that there's a lot less that breaks and so, 00:41:19.667 --> 00:41:23.607 less to break and the fact that we have rollbacks i have 00:41:23.607 --> 00:41:26.387 gone all the way to the edge with this system it is 00:41:26.387 --> 00:41:29.887 on nix os unstable and it is pulling straight 00:41:29.887 --> 00:41:33.407 from hyperland's github yeah they have a flake so 00:41:33.407 --> 00:41:36.367 they make that nice and easy and so this thing is 00:41:36.367 --> 00:41:39.587 the absolute freshest packages and desktop 00:41:39.587 --> 00:41:43.067 environment possible something goes wrong you roll back but so far two weeks 00:41:43.067 --> 00:41:49.587 nothing's gone wrong and the terminal environment is an actual chef's kiss now 00:41:49.587 --> 00:41:53.227 i know wes thinks it's a little weird but i have combined fish shell with a 00:41:53.227 --> 00:41:57.527 tuin which i picked up from bluefin and it is. 00:41:58.567 --> 00:42:01.747 A command line history tool that syncs across 00:42:01.747 --> 00:42:04.527 your systems so you can have the same command history 00:42:04.527 --> 00:42:07.827 if you want with support for multiple systems and all of that and 00:42:07.827 --> 00:42:11.027 it displays in a really nice list anyways that is 00:42:11.027 --> 00:42:14.227 combined with fish shell to have just a fantastic tool 00:42:14.227 --> 00:42:17.167 set on the command line i've designed it so your secrets 00:42:17.167 --> 00:42:21.887 like your github token they exist outside the github repo they exist outside 00:42:21.887 --> 00:42:27.447 the config and i've put a lot of polish into waybar to put media controls in 00:42:27.447 --> 00:42:34.467 their bluetooth integration brightness control network mount information gpu cpu load, 00:42:35.307 --> 00:42:37.207 All that kind of stuff is laid out in there. 00:42:37.467 --> 00:42:40.587 A playback, you can play and pause media controls and get a list of what's playing. 00:42:40.727 --> 00:42:43.907 You get open window notifications. And there's a system tray. 00:42:44.507 --> 00:42:48.187 I even have a system tray. So if you've got a chat app or something like that 00:42:48.187 --> 00:42:50.467 that has a system tray icon, it actually shows up in there. 00:42:51.347 --> 00:42:57.247 And it's so fast. It's between the optimizations I've done at the core and Hyperland, 00:42:57.287 --> 00:43:00.907 which was built from day one to just be as smooth as possible on Wayland. 00:43:02.087 --> 00:43:06.147 And then you combine it with a high refresh rate monitor it's and then fully 00:43:06.147 --> 00:43:11.827 vulcan accelerated desktop i mean it's it is the nicest setup i've ever had 00:43:11.827 --> 00:43:15.947 and it's on like a 300 b-link it's ridiculous i cannot imagine how great this 00:43:15.947 --> 00:43:17.447 would be on a brand new high-end system. 00:43:17.447 --> 00:43:21.127 Okay so i'm just going to ask about that you've kind of been developing this 00:43:21.127 --> 00:43:24.807 on one system have you made any attempts or do you have any plans to use this 00:43:24.807 --> 00:43:28.687 like you know on your office workstation or on a studio machine or, 00:43:28.727 --> 00:43:29.907 you know, some of your other setups. 00:43:30.607 --> 00:43:33.827 Absolutely. And I'm trying to build it to be machine agnostic. 00:43:33.967 --> 00:43:36.747 So there is a per machine configuration support in this. 00:43:37.027 --> 00:43:40.947 So you'd like, right, I have my machine at home. I call it RVB because it's a B-link in the RV. 00:43:41.407 --> 00:43:44.967 And that's just dropped inside a host folder. And you can put your different 00:43:44.967 --> 00:43:48.447 hosts in there. And then you just on that machine, your configuration gets pointed to that. 00:43:48.927 --> 00:43:52.527 But I would love ideas because I'm seriously think other people should try this. 00:43:53.187 --> 00:43:58.847 Because this is probably the opposite of Bluefin. It is everything turned up to 11. 00:43:59.087 --> 00:44:02.467 It is the absolute latest packages. It's using all the latest technology to 00:44:02.467 --> 00:44:04.647 put all this together. You've got rollbacks in here. 00:44:04.867 --> 00:44:08.467 You've got massive performance optimations that squeeze every bit of performance 00:44:08.467 --> 00:44:11.827 out of your system that it can possibly provide, optimized for a desktop session. 00:44:13.437 --> 00:44:17.137 And last but not least, built on top of Hyperland and the way Waybar works, 00:44:17.317 --> 00:44:23.677 I've been able to recreate a lot of the functionality of GNOME extensions without GNOME extensions. 00:44:24.497 --> 00:44:27.997 They're really just like Bash or Python on the back end, and they're really 00:44:27.997 --> 00:44:31.837 simple, and they just put out plain text that gets inserted into the Waybar, 00:44:31.877 --> 00:44:36.457 and there's essentially a CSS-style layout that you tell where to go in the Waybar. 00:44:37.277 --> 00:44:42.457 And why I bring that up is because it's nearly unbreakable, at least compared to GNOME extensions. 00:44:43.037 --> 00:44:47.277 Clearly, the Waybar developers could mess it up. 00:44:47.717 --> 00:44:52.757 But it's just so simple that it's likely to persist through upgrade after upgrade 00:44:52.757 --> 00:44:56.317 because we're just executing bash on the back end and then just getting text output. 00:44:56.537 --> 00:45:00.157 You might not be able to do technically as much with whatever the deep hooks 00:45:00.157 --> 00:45:02.517 into GNOME that you could do with extensions, but for all the stuff, 00:45:02.637 --> 00:45:04.517 you just kind of want to display stuff in a bar. 00:45:04.717 --> 00:45:07.397 Yeah, right? You don't have to deal with all the interface changes that can 00:45:07.397 --> 00:45:09.037 happen between GNOME releases anymore. 00:45:09.397 --> 00:45:14.357 You know, like an example is I like having just a small little icon in my bar 00:45:14.357 --> 00:45:15.857 that is a screen sleep inhibitor. 00:45:16.097 --> 00:45:19.057 So I can hit that if I know my system is going to be going for a while and my 00:45:19.057 --> 00:45:19.997 system won't go to sleep. 00:45:20.137 --> 00:45:23.017 And then I can come back and hit it again. And now regular, you know, 00:45:23.097 --> 00:45:24.517 screen and sleep modes are back enabled. 00:45:25.157 --> 00:45:27.637 And to do that, you need to get an extension in Gnome. 00:45:28.317 --> 00:45:31.937 But that's actually, it's just commands. There's just commands getting executed. 00:45:32.057 --> 00:45:34.817 And if you could just, you can just do that with a bash script and then put 00:45:34.817 --> 00:45:36.537 an icon in the way bar for it with an emoji. 00:45:36.757 --> 00:45:40.617 That is a great example. Yeah. You just need a thing that you can click and 00:45:40.617 --> 00:45:42.377 then it runs a command. I mean, exactly. 00:45:43.272 --> 00:45:47.232 Yeah, like player CTL is another great example. Like player CTL is a command 00:45:47.232 --> 00:45:50.252 line tool to control any of the playback on your system. 00:45:50.672 --> 00:45:54.872 And player CTL can pull metadata from applications like Firefox and, 00:45:54.872 --> 00:45:57.972 you know, other applications of what's now playing and whatnot. 00:45:58.212 --> 00:46:02.132 So if you just ran player CTL, and I think it's like dash dash metadata or whatever 00:46:02.132 --> 00:46:05.312 you can get the, you know, commands, it'll tell you what's actively playing 00:46:05.312 --> 00:46:07.572 on your system and what it knows about it. 00:46:07.952 --> 00:46:12.172 And you can just capture that information and display it. You know, 00:46:12.252 --> 00:46:15.912 it doesn't have to be a big complicated JavaScript mess that's tying in with 00:46:15.912 --> 00:46:16.672 all this different stuff. 00:46:16.812 --> 00:46:20.352 It can just be using player CTL on the command line. And so it's just a lot 00:46:20.352 --> 00:46:25.052 more robust in the sense that it's going to survive upgrade after upgrade after upgrade. 00:46:25.292 --> 00:46:31.312 So it's a system that's designed to just continue to run, regardless if you 00:46:31.312 --> 00:46:33.912 update it every day or if you update it every month. 00:46:34.532 --> 00:46:37.932 And I really think it's at a point where I just need more people looking at 00:46:37.932 --> 00:46:40.672 it and finding the things that make it unique to my system. 00:46:40.672 --> 00:46:45.652 Or finding the things that make it hard to distribute because it's about probably 00:46:45.652 --> 00:46:50.012 two hours away from making it easily to distribute, maybe three or four hours 00:46:50.012 --> 00:46:52.592 at most, and it could be universally distributable, 00:46:53.112 --> 00:46:55.972 ideally like with an ISO image and an installer. 00:46:56.332 --> 00:46:59.992 But there are things like I have my username and a couple of paths, 00:47:00.072 --> 00:47:02.352 and there's a few other things that I have in my home. 00:47:02.452 --> 00:47:06.332 There's a couple of things in there that are specific to my system that would 00:47:06.332 --> 00:47:09.872 need variables and replaced or whatever on individual systems. 00:47:09.872 --> 00:47:14.452 Yeah, I think if we combine like some refactoring on your upstream stuff, 00:47:14.452 --> 00:47:18.932 and then I started taking a little look at how the NixOS ISO stuff is put together. 00:47:19.492 --> 00:47:22.272 And I think we could get something where you could just, you know, 00:47:22.612 --> 00:47:26.812 have the same graphical install experience, but at the end of the day, get HyperFive. 00:47:26.812 --> 00:47:32.492 I love it. And it has also been a process of learning to use Hyperland and leaning 00:47:32.492 --> 00:47:33.772 into the Hyperland workflow. 00:47:34.372 --> 00:47:40.712 And then finally using a desktop environment that feels like my computers from 2025 and not 1998. 00:47:41.392 --> 00:47:47.792 It's so smooth. And it really, because it's, I think, like everything that you 00:47:47.792 --> 00:47:51.912 just think should work, works. Like, say you've got a game playing full screen in one desktop session. 00:47:52.152 --> 00:47:56.312 You know, if I swap over to the other virtual desktop, nothing gets messed up. 00:47:56.432 --> 00:47:59.552 I don't have weird stuff getting moved around or the game doesn't weird out. 00:48:00.192 --> 00:48:02.872 Like, the mouse doesn't get stuck. Like, everything just... 00:48:03.879 --> 00:48:07.739 Works like it should on a computer and it totally is irrelevant that i'm using 00:48:07.739 --> 00:48:11.759 wayland is a benefit in this case because it's so performant i really am happy 00:48:11.759 --> 00:48:15.079 with this and there's just no way i could use anything else and i want to move 00:48:15.079 --> 00:48:19.739 it to my other systems i do have a couple of odd bugs that i also could use 00:48:19.739 --> 00:48:22.699 help tracking down i created really basic prs for both of them is. 00:48:22.699 --> 00:48:26.159 There like a term because these are vibe bug like is it a bug is there. 00:48:26.159 --> 00:48:28.939 Yeah yeah i think so 00:48:28.939 --> 00:48:32.059 so well i've kind of gone more manually editing now too now that i'm getting 00:48:32.059 --> 00:48:36.339 more serious about it i've been making more manual tweaks oh you're taking over 00:48:36.339 --> 00:48:39.719 maintenance huh a little bit some of them yeah so yeah yeah more and more yeah 00:48:39.719 --> 00:48:43.119 it's funny because if you look at my github activity you can see when i'm really 00:48:43.119 --> 00:48:45.639 jamming there's like there's periods where i'm just like commit after commit 00:48:45.639 --> 00:48:48.719 after commit because i'm like oh this is great this is great i'm done now one more thing. 00:48:48.719 --> 00:48:54.999 Wes can we take a moment here and just congratulate chris on like some ups on 00:48:54.999 --> 00:49:01.399 sophistication here like he just said he's committing all of his versions to github this is. 00:49:01.399 --> 00:49:02.619 The first time yes. 00:49:02.619 --> 00:49:03.679 You've done this with your. 00:49:03.679 --> 00:49:06.279 Next os i'm. 00:49:06.279 --> 00:49:12.939 Seeing this like it's a flake with multi-host support this is fancy it's like 00:49:12.939 --> 00:49:18.179 this whole week you've just like skipped a ton of steps towards uh getting way 00:49:18.179 --> 00:49:20.399 more sophisticated i applaud you. 00:49:20.399 --> 00:49:22.739 Before you know it he'll be a nix packages committer. 00:49:22.739 --> 00:49:25.559 Necessity is also quite frequently the 00:49:25.559 --> 00:49:28.639 mother of invention like like well if i'm gonna make this 00:49:28.639 --> 00:49:31.919 usable by the audience i need to make this multi-host and 00:49:31.919 --> 00:49:35.699 if i'm gonna be making these kinds of changes and i want other people to try 00:49:35.699 --> 00:49:40.239 it i need to do version control and i need to have this up on a spot where other 00:49:40.239 --> 00:49:43.379 people can see it and review it and then i was like i need to have a serious 00:49:43.379 --> 00:49:46.319 readme too so then i went and redid to put a bunch of information in the readme 00:49:46.319 --> 00:49:49.679 put a screenshot in there so people know how freaking rad it looks and. 00:49:49.679 --> 00:49:52.799 You even have like a table here of key bindings. 00:49:52.799 --> 00:49:54.459 This is really sweet. 00:49:54.639 --> 00:49:58.799 You should do most of your like testing with the audience in mind. This is really great. 00:49:58.999 --> 00:50:02.659 But I have a couple of bugs I need help tracking down. So I'm trying to do the 00:50:02.659 --> 00:50:04.299 Hyperland desktop in a declarative way. 00:50:04.439 --> 00:50:07.919 So you make your changes in one spot, which is in my home directory, 00:50:07.919 --> 00:50:11.999 and then you build it and it deploys it to the proper locations where Hyperland 00:50:11.999 --> 00:50:13.839 config and your Waybar config is supposed to be. 00:50:13.959 --> 00:50:16.419 And the idea is, you know, you can centrally manage that. 00:50:16.559 --> 00:50:18.719 And then next time you build, it just gets a new version. 00:50:18.899 --> 00:50:22.419 It doesn't work. You just roll back. However, every now and then, 00:50:22.579 --> 00:50:24.839 especially after I do a build and then reboot, 00:50:25.579 --> 00:50:31.219 I come in and my key bindings have reverted to like one of the very early iterations, 00:50:31.759 --> 00:50:34.219 that's almost more Ama Archie inspired. 00:50:35.179 --> 00:50:38.019 I haven't like extensively tested this, but then if I build again, 00:50:38.259 --> 00:50:41.939 I don't do like an upgrade, but I just do another build and boot and reboot 00:50:41.939 --> 00:50:46.159 again and come back in, my config is back. It's the weirdest thing. 00:50:47.524 --> 00:50:49.684 And I tried and tried to track it down. I'm not sure where it's at. 00:50:49.784 --> 00:50:54.044 And the other issue that I could use some help tracking down is if I leave the machine for a while. 00:50:54.444 --> 00:50:56.484 Like say I leave it on overnight. 00:50:56.924 --> 00:50:59.204 Screen goes to sleep. Doesn't really matter if the screen goes to sleep or not. 00:50:59.264 --> 00:51:02.304 But say the screen goes to sleep. I come back in the morning. I wake it up. 00:51:03.124 --> 00:51:06.144 There's like a console output on the top. You can't highlight this text. 00:51:06.764 --> 00:51:12.304 But there's just a series of errors on the top that seemingly are very helpful. 00:51:12.424 --> 00:51:17.024 This is config error. And it says the path to my config file on line 69. 00:51:17.024 --> 00:51:21.524 And it says config option declarative drop shadow does not exist. 00:51:22.164 --> 00:51:28.984 And then same on line 70. However, I go in there, I fix it, or I look at it, I don't see an error. 00:51:29.644 --> 00:51:31.864 And I check the logs, there's no error in any of the logs. 00:51:32.824 --> 00:51:35.984 So I'm not sure where this error is actually coming from. It's very bizarre. 00:51:36.444 --> 00:51:41.084 So these are the two issues. Other than that, I'm using it for work during the 00:51:41.084 --> 00:51:44.044 day, and then my son is literally gaming on it all night long. 00:51:44.584 --> 00:51:49.164 And we are I know this is not a huge deal because it's just Geometry Dash but 00:51:49.164 --> 00:51:53.524 he's getting 300 he's maxing the game out at 360 frames per second at a 200 00:51:53.524 --> 00:51:58.824 hertz refresh rate on a little B-Link and we're playing, 00:51:58.844 --> 00:52:01.164 I'm playing Star Trek Resurgence or whatever it's called, 00:52:01.784 --> 00:52:06.584 Star Trek Online on this thing we're playing multiple games on this tiny little 00:52:06.584 --> 00:52:11.444 thing and it is absolutely keeping up with this Thaleo right now it's wild and 00:52:11.444 --> 00:52:15.764 it did not start that way It did not start that way. 00:52:16.004 --> 00:52:19.324 The frame rate was low. The screen was a little jerky, even though I had the 00:52:19.324 --> 00:52:21.184 new monitor. It was having stuttering issues. 00:52:21.884 --> 00:52:24.584 There was all kinds of little performance, like legs, that would happen, 00:52:24.624 --> 00:52:27.564 and then it would speed back up again. And it was frustrating, the boy. 00:52:29.024 --> 00:52:34.884 So, you know, while he was AFK, I set off on a mission to see if I could really 00:52:34.884 --> 00:52:36.024 optimize the hell out of this thing. 00:52:36.324 --> 00:52:40.024 And now it's, I mean, it's flawless in the gaming performance. 00:52:40.364 --> 00:52:43.164 You know, within reason. It's a tiny little AMD chip in there. 00:52:43.164 --> 00:52:44.964 But it's incredible what I'm getting out of this thing. 00:52:45.204 --> 00:52:50.144 And so he's massively pounding on it. I'm pounding on it during the day, all day long. 00:52:51.284 --> 00:52:53.744 And these are the two things that I've come up with that are issues so far. 00:52:54.104 --> 00:52:57.484 Plus, it needs help with portability. And ultimately, it needs an ISO image. 00:52:57.644 --> 00:53:02.804 But that is a few hours of work. And this is something really special. 00:53:03.744 --> 00:53:08.924 While a little wild, is a hell of a Linux experience and only something you can do on Linux. 00:53:09.444 --> 00:53:14.724 And it's going to be my distro now for my desktops. So it's not a server distro, it's a desktop distro. 00:53:15.324 --> 00:53:18.164 And my next move is like, I got to get it working with multi monitors. 00:53:18.384 --> 00:53:23.044 I suspect that's going to be pretty easy in Hyperland, but I got to get that working. 00:53:23.064 --> 00:53:27.144 And I got to figure out a way to expand it to multiple machines that works reliably. 00:53:27.424 --> 00:53:29.444 And then eventually I want to deploy it here in the studio too. 00:53:30.644 --> 00:53:31.744 I have a couple of questions. 00:53:33.675 --> 00:53:41.155 First one, last week you leaned heavily on some, let's say, AI help to design 00:53:41.155 --> 00:53:44.235 this whole thing, but you just sort of teased that you slowed down on that and 00:53:44.235 --> 00:53:47.175 you're making some manual changes. 00:53:47.595 --> 00:53:53.055 Do you see yourself using more vibing to modify this thing, or think you're 00:53:53.055 --> 00:53:58.055 slowing way down just permanently and doing just manual changes from now forward? 00:53:58.055 --> 00:54:01.875 I may be at the limits. Well, two things, you know, so I was on a free, 00:54:01.975 --> 00:54:05.075 like, try it out. And there, you know, no API limits. 00:54:05.955 --> 00:54:08.115 That's over now. So, yeah. 00:54:08.775 --> 00:54:10.355 Our paper vibe is back. 00:54:10.595 --> 00:54:14.075 Yeah. So I'm not going to do a lot of paper vibing. 00:54:14.195 --> 00:54:17.935 But looking up little things, you know, like maybe the syntax to do a hyperlink 00:54:17.935 --> 00:54:20.815 config file on multi-monitor, I might use an LLM for that. 00:54:21.235 --> 00:54:25.375 But I think I'm at the point now where I need humans to look at it with multiple 00:54:25.375 --> 00:54:27.455 different systems and sort of beyond 00:54:27.455 --> 00:54:30.995 what the tool can do, which is fine because I got pretty far with it. 00:54:31.295 --> 00:54:34.915 And now it's really iterative stuff. So I'm totally happy with that. 00:54:35.015 --> 00:54:38.555 But for just probably technical lookups, you know, that kind of stuff, 00:54:38.695 --> 00:54:41.515 I could see it. Or like if I were to try to get it working on a video system. 00:54:41.875 --> 00:54:47.555 Are you going to do official versions with fun, you know, Linux kernel style version names? 00:54:49.315 --> 00:54:53.175 Well the whole thing's really all rolling so that's tricky you know the whole 00:54:53.175 --> 00:54:54.815 thing is i mean but i kind of do. 00:54:54.815 --> 00:54:56.535 It whenever you want right you just say yeah. 00:54:56.535 --> 00:55:00.175 Right that's true yeah and it would really be like an update to the configs 00:55:00.175 --> 00:55:03.035 you know major new things to the configs yeah you could see it. 00:55:03.035 --> 00:55:04.815 Yeah you change a theme out i don't know. 00:55:04.815 --> 00:55:07.675 I've never done the release thing on github but that could be kind of fun right 00:55:07.675 --> 00:55:10.395 like the main repo is all the current stuff and then every now and then i just 00:55:10.395 --> 00:55:14.055 carve a release when something major has been accomplished or like i've you 00:55:14.055 --> 00:55:17.375 know Or maybe we re-based on a new version of Hyperland or something. I don't know. 00:55:17.535 --> 00:55:19.195 Chris is going to learn about branches, everybody. 00:55:19.335 --> 00:55:22.455 Yeah. Woo. Here we go. It has been a lot. 00:55:22.655 --> 00:55:26.835 Like any good distribution, you need a good name. Have you come up with a name for this thing? 00:55:27.015 --> 00:55:28.975 I'm kind of embracing the Hypervibe. 00:55:29.902 --> 00:55:33.682 You know, because it's Hyperland and it's a vibe. You know, I'm just going with 00:55:33.682 --> 00:55:36.062 Hypervibe. You know, I don't know. 00:55:36.362 --> 00:55:37.202 Are you locking it in? 00:55:37.362 --> 00:55:39.982 I could lock it. Do you think it's okay? I mean, what do you boys think? 00:55:40.082 --> 00:55:42.002 Well, I think it's quick and snappy and memorable. 00:55:42.522 --> 00:55:45.782 Yeah? Wes? Could you live with Hypervibe? 00:55:45.922 --> 00:55:47.622 Heck yeah. It's good vibes to me. 00:55:48.482 --> 00:55:51.802 Locked in, then. Locked in. So we'll have a link to the GitHub repo, 00:55:51.962 --> 00:55:56.362 chrislass slash Hypervibe, if you want to check it out. if you have any suggestions 00:55:56.362 --> 00:56:00.202 on making it more portable or if you try it and run into any bugs. 00:56:00.482 --> 00:56:03.502 Right now, I'd say it's probably for the more advanced Nix user, 00:56:03.582 --> 00:56:05.962 but I'd like to take it to somebody that just wants to, you know, 00:56:06.242 --> 00:56:09.762 try a nice image and run with it. I'm not sure how well it would run in a VM. 00:56:10.842 --> 00:56:13.922 It probably comes down to how well Hyperland works in a VM, which is probably 00:56:13.922 --> 00:56:15.762 doable, but you'd want to have some 3D acceleration. 00:56:16.462 --> 00:56:19.682 It's been a lot of fun. I never thought I would actually really do this either. 00:56:20.882 --> 00:56:22.082 But I'm going for it, boys. 00:56:28.082 --> 00:56:33.302 Go Unleash your hardware and celebrate 20 years of Unraid OS. What a milestone. 00:56:33.862 --> 00:56:38.022 What a milestone. And to really kind of mark it, now is your opportunity to 00:56:38.022 --> 00:56:43.042 get 20% off the starter or Unleash licenses. So if you've been thinking about it, do it. 00:56:43.322 --> 00:56:46.322 Also, if you're ready for an upgrade, you get some off that. 00:56:46.322 --> 00:56:49.262 And if you want to grab some of the new merch to show off your HomeLab pride, 00:56:49.702 --> 00:56:51.402 you can get 20% off that too. 00:56:51.942 --> 00:56:55.042 Every day, they have giveaways, free licenses, merch bundles, 00:56:55.062 --> 00:56:59.282 and they're even giving away a link station, which looks like a sweet rig. 00:56:59.542 --> 00:57:02.482 So if you've got a great Unraid setup, submit it to them. 00:57:02.642 --> 00:57:05.542 They have a Show Us Your System competition for a chance to win prizes. 00:57:05.702 --> 00:57:09.562 You get bragging rights and, of course, get featured in that birthday bash stream 00:57:09.562 --> 00:57:11.462 that I mentioned last week, which will be on August 31st. 00:57:12.327 --> 00:57:15.347 That's the thing to do, really. Go mark your calendars for that big event. 00:57:15.827 --> 00:57:19.727 Unraid's founder and guest will be joining to celebrate 20 years of Unraid and 00:57:19.727 --> 00:57:21.647 to reveal the show your system winners. 00:57:21.867 --> 00:57:24.307 So you'll want to put August 30th on your calendar. 00:57:24.587 --> 00:57:28.027 You'll learn more by going to unraid.net slash unplugged. But giveaways, 00:57:28.827 --> 00:57:33.407 merch, special guests, which I have a hint who a couple of them are, 00:57:33.907 --> 00:57:37.287 and of course celebrating 20 years of Unraid, which is what I love. 00:57:37.407 --> 00:57:41.387 I love that they have been with this for so long. and having spoken to them, 00:57:41.527 --> 00:57:45.867 you know, I would have had the sense they're just a few years into this with the energy they have. 00:57:46.247 --> 00:57:49.127 I mean, incredible energy and direction for Unraid as well. 00:57:49.607 --> 00:57:53.287 So check it out. If you've got storage sitting around, maybe a machine you could 00:57:53.287 --> 00:57:56.087 throw this on or you've been thinking about building one and you want to try 00:57:56.087 --> 00:57:58.847 out all the applications we talk about all the time on this show, 00:57:59.467 --> 00:58:02.947 Unraid will get you going in like a Saturday, right? That's the thing. 00:58:03.047 --> 00:58:06.287 Like you could build all this from scratch and have like this crazy bespoke 00:58:06.287 --> 00:58:10.447 system or you could let Unraid do the heavy lift with the Linux curation, 00:58:10.587 --> 00:58:14.127 the VM curation, all the applications, of course, the container management, 00:58:14.187 --> 00:58:15.587 and you supply the hardware. 00:58:15.787 --> 00:58:18.807 And then you get up and running right away. And then they're already 20 years 00:58:18.807 --> 00:58:19.827 in and they're still going strong. 00:58:20.547 --> 00:58:23.827 So that's something that's going to last for a long time. Go check it out. 00:58:24.007 --> 00:58:26.787 Find more about the celebration and support the show. 00:58:26.947 --> 00:58:32.807 Go to unraid.net slash unplugged. That's unraid.net slash unplugged. 00:58:36.407 --> 00:58:40.807 Well, this has been a great week for shout outs. And we want to welcome aboard 00:58:40.807 --> 00:58:41.907 all sorts of new members. 00:58:42.187 --> 00:58:48.607 We've got Zach, Anders, Trevor, Nicholas, Hanji, Alejandros, Adam, and Timothy. 00:58:49.027 --> 00:58:52.087 So a huge thank you to these new members. 00:58:52.487 --> 00:58:52.667 Woo! 00:58:53.027 --> 00:58:56.647 And Chris, do we have any of those discount slots left? 00:58:57.367 --> 00:59:02.707 Four left. There are four slots left for the bootleg promo code that takes 15% 00:59:02.707 --> 00:59:07.147 off your jupiter.party membership, which is a great deal, or your core contributor membership. 00:59:07.147 --> 00:59:10.627 Either plan gets you the bootleg or 00:59:10.627 --> 00:59:13.567 the nice and tight version fully produced version of 00:59:13.567 --> 00:59:17.147 the show and the party membership supports all the shows and the whole network 00:59:17.147 --> 00:59:19.927 and the core contributor goes right here to this show and gets you all them 00:59:19.927 --> 00:59:27.447 features thank you everybody that got on board this week hi yeah whoo whoo four 00:59:27.447 --> 00:59:32.607 left use the promo code bootleg linuxunplugged.com membership or jupyter.party. 00:59:34.057 --> 00:59:38.737 Now we have a little ask here from Fergus, who asks about the safety of BitChat. 00:59:39.177 --> 00:59:43.917 He says, I heard you discussing Dorsey's new messaging app that is based on Bluetooth. 00:59:44.537 --> 00:59:48.297 Has anyone considered the implications of creating a, quote, 00:59:48.537 --> 00:59:52.717 secure peer-to-peer Bluetooth network in contrast with the Bluetooth surveillance 00:59:52.717 --> 00:59:55.337 networks that are currently deployed by, say, 00:59:55.897 --> 01:00:01.117 Apple with AirTags, Google, Tile, and the Amazon Sidewalk stuff? 01:00:01.117 --> 01:00:07.717 I doubt that the target audience are Graphene OS users with an eSIM purchased in Monero. 01:00:08.037 --> 01:00:13.957 My concern is that this opens another channel for tracking that would otherwise be inactive. 01:00:14.317 --> 01:00:16.977 I would be interested in hearing your guys' thoughts. 01:00:17.337 --> 01:00:23.997 I think the threat is not in so much the use of Bluetooth, it is in having Bluetooth enabled. 01:00:24.237 --> 01:00:26.617 Like, if you have Bluetooth on, you're going to get tracked. 01:00:26.777 --> 01:00:26.917 Right. 01:00:27.497 --> 01:00:30.277 Right. So I don't think BitChat increases that risk. 01:00:30.697 --> 01:00:34.437 Yeah, it will. It is pretty good. Like when you, I have my Bluetooth set to 01:00:34.437 --> 01:00:36.157 just auto go off if I'm not using it. 01:00:36.277 --> 01:00:40.337 And BitChat's good if when you open the app, it'll prompt you to turn it back on. 01:00:40.697 --> 01:00:43.897 And it's a pretty slick, it doesn't, it's not super much of a fuss because I 01:00:43.897 --> 01:00:45.477 was doing that at DEF CON constantly checking. 01:00:45.637 --> 01:00:48.817 I didn't get many hits or anything, but you know, it was easy enough that it 01:00:48.817 --> 01:00:50.397 wasn't a big pain to keep opening it, 01:00:50.477 --> 01:00:53.157 turning it on just while I was using Bluetooth and then turn it all off. 01:00:53.157 --> 01:00:59.897 I, just as an aside, have been getting three or four or maybe even more messages 01:00:59.897 --> 01:01:03.357 a day on my Mesh-tastic TDEC out at the farm I'm staying at. 01:01:03.657 --> 01:01:03.957 Oh. 01:01:04.837 --> 01:01:09.317 The Mesh-tastic traffic is increasing. That's been pretty neat to see. 01:01:09.517 --> 01:01:11.477 I need to get mine set up again. I'm slacking. 01:01:11.997 --> 01:01:17.217 Yeah, I'd love to see if we could eventually connect. Quinn wrote in and shared his Nix setup with us. 01:01:17.277 --> 01:01:20.457 He says, hey, Unplugged team, loving the new bootleg, and I just wanted to drop 01:01:20.457 --> 01:01:24.317 my Nix OS configs. They're not finished, at least by my standards, 01:01:24.557 --> 01:01:28.177 but right now it is multi-host and sets a host name based on a folder name. 01:01:29.142 --> 01:01:31.462 It's split across four repos, and I love the name of these repos, 01:01:31.542 --> 01:01:32.642 and I'll put the links in the show notes. 01:01:33.582 --> 01:01:37.382 Repo 1, the formatter. Repo 2, the home. 01:01:38.182 --> 01:01:43.502 Repo 3, the shared. And then the last repo, Repo 4, the host. 01:01:44.642 --> 01:01:45.662 They're just great names. 01:01:47.222 --> 01:01:49.662 And I'm going to have to take a look at it. I love it when people share their 01:01:49.662 --> 01:01:52.902 configs. And maybe there's something we could steal in there for Hypervibe. 01:01:53.162 --> 01:01:55.922 I like the idea of setting the host name based on a folder. That makes a lot 01:01:55.922 --> 01:01:57.422 of sense. Thank you, Quinn. 01:01:58.262 --> 01:02:03.302 That was good to see. now i want more i can look at configs like as a pastime 01:02:03.302 --> 01:02:06.142 you know if we just had like something that just filtered them as they came 01:02:06.142 --> 01:02:10.522 in and i just went to like some sort of offline reader and i could just read 01:02:10.522 --> 01:02:13.542 through people's configs as like a short pastime before bed like. 01:02:13.542 --> 01:02:14.842 The configs chronicles. 01:02:14.842 --> 01:02:18.162 Oh yeah you spin the spin the dice and one up config pops up. 01:02:18.162 --> 01:02:18.782 With a credit. 01:02:18.782 --> 01:02:19.522 Oh that'd be Great. 01:02:25.902 --> 01:02:28.902 Yeah, it is. And we got some great boosts this week. 01:02:29.022 --> 01:02:34.802 In fact, Anonymous came in during the live show and is our baller booster with 71,000 sets. 01:02:38.342 --> 01:02:39.642 That is great. 01:02:42.722 --> 01:02:46.382 Coming on Podversus. Hi there, I finally caught up with the last episode today. 01:02:46.502 --> 01:02:49.442 So I'll be hopefully live with you tonight. after hearing about 01:02:49.442 --> 01:02:52.282 your summer bis dip what is 01:02:52.282 --> 01:02:55.042 that what's a boost boost boost oh the boost dip yeah 01:02:55.042 --> 01:02:58.642 we had the summer yeah the summer lull i thought i'd send some love and some 01:02:58.642 --> 01:03:03.342 sets so chris i wanted to know about setting up hyperland on nyx why are so 01:03:03.342 --> 01:03:07.862 many revisions why so many revisions and they all need a full rebuild how did 01:03:07.862 --> 01:03:11.982 you get this done without spending so much time waiting for builds this is one 01:03:11.982 --> 01:03:13.422 of the i'm glad you asked this, 01:03:14.535 --> 01:03:18.115 This is actually one of the things that drew me away from Bluefin to Nix OS. 01:03:19.255 --> 01:03:27.755 And it was the time for iteration. Not that it is super arduous to iterate on a uBlue base, 01:03:28.235 --> 01:03:32.595 but it is a longer process, and the images are large, and they take a long time 01:03:32.595 --> 01:03:34.815 to pull down, and then it actually does assemble them pretty quickly. 01:03:35.335 --> 01:03:40.355 Whereas with Nix, I make a line config change, and I can do a rebuild, 01:03:40.515 --> 01:03:44.955 and if you have a fast SSD and a fast CPU, and you're not changing very much, 01:03:45.515 --> 01:03:46.815 it can take literal seconds. 01:03:47.415 --> 01:03:50.415 And so you can build and build and build really quickly, deploy that, 01:03:50.515 --> 01:03:54.275 and with Nix, you can also choose to switch to the system or you can choose to boot. 01:03:54.715 --> 01:03:58.935 And so depending on the level of change, sometimes I would do a switch and sometimes I would do a boot. 01:03:59.115 --> 01:04:03.415 And every time I would do a build, I'm also deploying a new version of my Hyperland 01:04:03.415 --> 01:04:08.235 config, my Waybar config, and some of the ancillary tools that make all of that 01:04:08.235 --> 01:04:10.535 work. That's all included and managed by Nix. 01:04:10.715 --> 01:04:13.495 Right, and Nix is pretty good about, you know, You still have to do the full 01:04:13.495 --> 01:04:17.555 evaluation step on your config every time, but after that, it's able to do a 01:04:17.555 --> 01:04:22.295 diff to see what actually needs to get rebuilt and what actually needs to get restarted. 01:04:22.395 --> 01:04:25.255 So if you're doing it, especially as you work kind of incrementally, 01:04:25.455 --> 01:04:28.275 each time there's not that many components that are changing. 01:04:28.475 --> 01:04:32.735 And I like that sanity check. For me, it's a nice thing to have in there, 01:04:32.835 --> 01:04:35.635 to make sure everything's looking right and whatnot. 01:04:36.715 --> 01:04:42.175 And then after I would do several and I would test them, I would then do a push to GitHub. 01:04:42.795 --> 01:04:46.875 But usually for like one push to GitHub, there was probably five or 10 little 01:04:46.875 --> 01:04:49.235 smaller things. And then, all right, this is enough. I'm going to push it now. 01:04:49.835 --> 01:04:53.375 And you can kind of just see that going and going and going for a bit. Thank you, Anonymous. 01:04:53.655 --> 01:04:56.335 Appreciate that boost. And if you want to boost in and let us know who you are, 01:04:56.895 --> 01:04:58.075 we'd always love that too. 01:04:59.195 --> 01:05:05.175 Adversaries 17 boosts in with 57,344 sats across three boosts. 01:05:05.475 --> 01:05:05.795 Woo! 01:05:12.409 --> 01:05:16.209 Haven't boosted in a while since I switched to Fountain. Unfortunately, 01:05:16.409 --> 01:05:19.189 it doesn't look like Fountain supports boosting the member feeds. 01:05:19.649 --> 01:05:23.749 And, uh, re your extreme makeover home assistant edition. 01:05:24.309 --> 01:05:27.169 When are y'all coming to my place? 01:05:28.169 --> 01:05:30.189 We would love to do that. 01:05:31.769 --> 01:05:32.669 Keep boosting. 01:05:33.029 --> 01:05:39.609 Okay, and then, uh, one last boost here. Responding to Chris's KYC society in the outro. 01:05:40.489 --> 01:05:43.349 Definitely agree with you on how that's going to go down. 01:05:43.609 --> 01:05:47.169 Unfortunately, that's how all governments eventually go. Just look at history. 01:05:47.369 --> 01:05:49.469 People say, they won't take away my freedom. 01:05:49.849 --> 01:05:53.569 Well, they already have. You just haven't gotten caught in the crosshairs yet. 01:05:54.069 --> 01:05:57.789 Once you're in the crosshairs, the agenda pushers will stop at nothing to rid 01:05:57.789 --> 01:05:59.669 you of everything you ever knew. 01:06:00.429 --> 01:06:04.189 Woo! Adversary is keeping it real. Keeping it real. 01:06:04.609 --> 01:06:08.289 Yeah, I'm sorry about the, uh, it's so ironic that the members can't boost and 01:06:08.289 --> 01:06:09.509 the members want to boost. That's so amazing. 01:06:09.609 --> 01:06:16.289 But it's probably not going to really get resolved until we can swap out memberful. 01:06:16.769 --> 01:06:20.969 That might be what it takes. I'm not quite sure there, but well, 01:06:21.009 --> 01:06:23.029 the real problem is that it's a private feed actually. 01:06:24.029 --> 01:06:27.509 And a fountain looks up the value splits via the podcast index API. 01:06:27.729 --> 01:06:31.509 And so if the podcast isn't published on the index, which it's not for a private 01:06:31.509 --> 01:06:33.709 member feed, there is nothing to look up via the API. 01:06:34.009 --> 01:06:38.049 It is something that really bugs us too though. So we can solve it. 01:06:38.049 --> 01:06:39.669 But we will definitely do so. 01:06:40.309 --> 01:06:42.549 Thank you for the boost. It's nice to hear from you. Missed you. 01:06:43.169 --> 01:06:47.369 Well, Mick ZP came in with two boosts for a total of 40,000 sets. 01:06:55.176 --> 01:07:00.056 Mick says, I just hate hearing that damn lowered expectation soundbite. 01:07:00.256 --> 01:07:01.236 I'm not going to play it. 01:07:03.736 --> 01:07:05.636 It's only when we don't meet expectations. 01:07:05.896 --> 01:07:09.116 Well, I think we're meeting expectations a little more this week, 01:07:09.296 --> 01:07:11.576 thanks to Mick ZP's boost. 01:07:11.756 --> 01:07:13.736 Yeah, we need a meeting expectations boost. 01:07:14.156 --> 01:07:17.716 Yeah, yeah. Well, that's what all the other sounds are, are meeting expectations. 01:07:17.796 --> 01:07:18.796 Okay, we'll pick one of those. 01:07:19.316 --> 01:07:22.536 Do you have a special meeting expectations boost there? 01:07:27.096 --> 01:07:34.876 How's that there you go there you go oh is that it okay that's it huh thank 01:07:34.876 --> 01:07:38.836 you it's nice to hear from you mixip and uh i love that boost hey there's hybrid 01:07:38.836 --> 01:07:40.716 sarcasm coming in right now, 01:07:43.856 --> 01:07:49.136 25 000 sats i hear boosts are on sale so get them while they're hot by the way 01:07:49.136 --> 01:07:55.416 how are the 2025 boosties looking oh i don't know if we want to talk about that right now yeah. 01:07:55.416 --> 01:07:59.556 I'm way behind but maybe maybe sometime in the next couple of weeks i can uh 01:07:59.556 --> 01:08:04.396 get caught up and um do a preliminary take take a look at uh that doesn't see 01:08:04.396 --> 01:08:05.676 at least who's in the front running. 01:08:08.636 --> 01:08:11.676 It's you know it's one of those things where i 01:08:11.676 --> 01:08:15.816 actually think the overall total number of sats will be probably significantly 01:08:15.816 --> 01:08:20.036 down from last year because like last year we did uh i think it was last year 01:08:20.036 --> 01:08:24.916 we did the uh you know scale trip i think maybe i don't know but my point being 01:08:24.916 --> 01:08:29.396 i think the total amount of sats boosted in may be down but the value may be up. 01:08:29.396 --> 01:08:30.936 Yeah yeah true. 01:08:30.936 --> 01:08:34.576 Not sure we'll find out thank you for checking and it's it's nice to hear from 01:08:34.576 --> 01:08:36.856 your hybrid appreciate you retro. 01:08:36.856 --> 01:08:40.056 Gear boosts in with 20 000 sats, 01:08:43.201 --> 01:08:47.921 I've been playing with Libre NMS for a work project to monitor radio repeater 01:08:47.921 --> 01:08:50.421 sites via a microwave network. 01:08:50.821 --> 01:08:55.301 The monitoring also includes the radio repeater devices and DC power equipment. 01:08:55.801 --> 01:08:59.201 Alert notifications are excellent with many platforms to choose from. 01:08:59.441 --> 01:09:03.601 I wonder what your thoughts are, or have you used it? I did have a quick look 01:09:03.601 --> 01:09:05.641 at Zabbix, but the UI seemed clunky. 01:09:06.041 --> 01:09:11.641 Keep up the great work, team. I wouldn't be doing what I am now without LUP and self-hosted. P.S. 01:09:11.881 --> 01:09:14.141 Don't forget about those ham radio licenses. 01:09:16.581 --> 01:09:17.541 Good reminder. 01:09:17.541 --> 01:09:20.921 Don't worry we haven't I was just chatting with a family member this week about 01:09:20.921 --> 01:09:24.261 ham radio came up and I was like yeah I'm definitely gonna get it eventually 01:09:24.261 --> 01:09:26.581 the audience wouldn't wouldn't forgive us if we didn't. 01:09:26.581 --> 01:09:32.381 I took a quick look at Libre NMS and it looks pretty good better than I expected 01:09:32.381 --> 01:09:35.081 I don't know what I expected but for some reason it looked better than I expected 01:09:35.081 --> 01:09:37.681 I am down to get some decent monitoring going, 01:09:38.181 --> 01:09:40.541 I don't think there's a lot of content in that. Other than once you have it 01:09:40.541 --> 01:09:41.821 all set up, I guess we can have some takeaways. 01:09:42.581 --> 01:09:46.201 But I would very much be interested to know what people are using these days. 01:09:46.361 --> 01:09:51.661 Back in my day, Libre NMS did not exist. But I wonder if it might be based on 01:09:51.661 --> 01:09:54.201 a project that I'm familiar with. Because it does look vaguely familiar. 01:09:54.561 --> 01:09:57.501 Yeah, it looks like good stuff. I had the same. I didn't ever get to quite use 01:09:57.501 --> 01:10:02.001 it. I think maybe it had just started when I last took a peek at these kinds of things. 01:10:02.181 --> 01:10:06.721 But hey, we need more Libre options in this space. So glad to see it. I'm curious. 01:10:07.721 --> 01:10:08.721 Thank you for the boost. 01:10:09.501 --> 01:10:12.681 Well, Otterbrain boosted in 15,000 sets. 01:10:15.441 --> 01:10:19.061 Sorry for the late boost. I'm listening live. Just got back from the wilderness 01:10:19.061 --> 01:10:21.721 and gearing up for that academic year. 01:10:22.381 --> 01:10:28.521 Hey! Thank you, Otterbrain. Nice to hear from you. Thanks for the check-in and thanks for the update. 01:10:28.781 --> 01:10:33.021 The academic year is nigh, isn't it? That's the thing in my household, too. 01:10:33.841 --> 01:10:36.681 Good luck. Once you get started, let us know how it's going. 01:10:37.781 --> 01:10:41.401 Well, PJ's here with 6,666 sets. 01:10:44.441 --> 01:10:49.221 He says, Darn near every boosted-in app and JB app pick has piqued my interest 01:10:49.221 --> 01:10:53.301 this episode. Thanks for opening a few more permanent tabs on my phone browser. 01:10:53.741 --> 01:10:56.961 Also, I've recently tried FFShare, and I've tried it a number of times, 01:10:57.161 --> 01:11:00.381 and it typically makes my files even bigger. 01:11:00.621 --> 01:11:04.841 That one time I sent a WebM was from my laptop. Oh, because we called him out. 01:11:05.261 --> 01:11:06.961 And now he's got to defend himself on a web. 01:11:07.981 --> 01:11:14.141 That one time I sent a WebM from my laptop. It was using a quick cut editor. You recommend it. 01:11:14.641 --> 01:11:15.661 So it's our fault? 01:11:16.361 --> 01:11:20.721 Telegram rented a fine on the desktop, just not on mobile. I do love a good 01:11:20.721 --> 01:11:24.301 roast, though. Put some mac and cheese on there for me if you would, too. You got it, PJ. 01:11:26.486 --> 01:11:29.806 Yeah, I wonder, I'll have to play more with FFShare just because I wonder if 01:11:29.806 --> 01:11:32.106 you can change like your Q values or other things. 01:11:32.326 --> 01:11:34.926 That's what I always do on the command line. It's just kind of turn the quality 01:11:34.926 --> 01:11:37.366 down somewhere reasonable, at least for things you don't really, 01:11:37.426 --> 01:11:41.246 you know, need precise quality on. I don't know what it defaults to in its settings. 01:11:41.906 --> 01:11:43.786 But thank you for the experience report, PJ. 01:11:44.326 --> 01:11:44.646 Yeah. 01:11:45.066 --> 01:11:49.246 I'm thinking PJ doesn't understand what FFShare is for. It takes what you've 01:11:49.246 --> 01:11:51.546 got and it boosts up the quality, doesn't it? 01:11:51.686 --> 01:11:55.266 Yeah, make it, you know, make it better. And you can always add bits, you know. 01:11:55.266 --> 01:11:59.306 They might be you hands you ai enhance boom get. 01:11:59.306 --> 01:12:00.946 Into the modern world there pj. 01:12:02.106 --> 01:12:05.926 It might be ai that imagines the bits that it adds but you can always add bits. 01:12:07.086 --> 01:12:11.826 Galactic starfish boosts in with 7777 sets 01:12:11.826 --> 01:12:14.826 i am not quite a 01:12:14.826 --> 01:12:19.886 completionist but i'm not that far from it occasionally i take breaks from podcasts 01:12:19.886 --> 01:12:24.186 all together but when the big when the breaks become too lengthy i compromise 01:12:24.186 --> 01:12:29.306 and skip all but the most interesting one to five in the gap per podcast that 01:12:29.306 --> 01:12:32.206 said i'm never late to twib hey. 01:12:32.206 --> 01:12:33.046 There we go. 01:12:33.046 --> 01:12:42.086 Up 616 sre rip 148 launch 29 keep up the good work and thanks for all you do. 01:12:42.086 --> 01:12:44.026 Nice check-in oh. 01:12:44.026 --> 01:12:45.906 You got the deets on that one. 01:12:46.726 --> 01:12:49.566 Appreciate that thanks galactic good to hear from you. 01:12:49.566 --> 01:12:55.266 Well tomatoes here with three boosts for a Total of 9,999 sets. 01:12:57.686 --> 01:13:02.686 Well, I jumped ahead to listen to 626 and 627 while catching up, 01:13:02.946 --> 01:13:04.026 throwing in some support. 01:13:04.766 --> 01:13:08.586 I agree, we need a good modern in-kernel file system. 01:13:08.846 --> 01:13:16.706 I'm also still frustrated at the BZF attitude of the kernel devs with regard to ZFS. 01:13:16.706 --> 01:13:21.126 If they'd embrace it as an external project with a special status, 01:13:21.126 --> 01:13:24.406 this, the file system story would have been so much better. 01:13:25.306 --> 01:13:27.986 I think you and I are on the same page there, Tomato. Like, 01:13:28.046 --> 01:13:31.926 I'm not expecting them to make allowances for something that's not licensed 01:13:31.926 --> 01:13:36.986 properly, but also not really understanding the user's perspective and never 01:13:36.986 --> 01:13:40.386 coming to a middle at all on it has been frustrating for those of us that want 01:13:40.386 --> 01:13:41.426 to run these things in production. 01:13:42.006 --> 01:13:44.426 Thank you for the boost. Nice to hear from you, Tomats. 01:13:45.546 --> 01:13:46.726 I think this is a new one. 01:13:48.046 --> 01:13:51.026 Doornail7887, I think, maybe new, comes in with a row of ducks. 01:13:52.903 --> 01:13:55.803 You guys mentioned a boost barn previously. Does that exist? 01:13:56.183 --> 01:13:57.923 Is there a place where you post the messages to? 01:13:58.363 --> 01:14:03.083 That was a self-hosted thing because we didn't put all of the boosts above 2,000 sats on the show. 01:14:04.143 --> 01:14:07.723 However, you have Podverse, so it's a little tricky. But if you go to, 01:14:07.943 --> 01:14:11.523 I think you can get on the Fountain FM website, either in the Fountain app or 01:14:11.523 --> 01:14:13.623 in the Fountain FM website. You can read all the boosts. 01:14:14.403 --> 01:14:18.343 To Brent's help and call out in episode 627, I'm not a Knicks user, 01:14:18.503 --> 01:14:22.883 but it got me wondering if there wasn't some sort of interesting combination of Pixie Boot and Knick. 01:14:22.903 --> 01:14:25.563 That might make deploying these machines a lot easier to manage. 01:14:26.463 --> 01:14:26.863 Yes. 01:14:27.163 --> 01:14:30.083 Yeah, he said, I'm going to grow that. I'm going to add that to my growing half-baked 01:14:30.083 --> 01:14:33.143 ideas stash. I actually think it's not half-baked at all, actually. 01:14:33.143 --> 01:14:34.103 That's a good idea. 01:14:34.403 --> 01:14:37.303 Pixie and Nix are a match made in Linux distro heaven. 01:14:38.023 --> 01:14:41.223 And Pixie is so nice, and you have less things to fail in the machine. 01:14:41.403 --> 01:14:46.243 This is also exactly the reason we ask for your ideas, is that you come up with 01:14:46.243 --> 01:14:50.203 something that we had never even considered that's probably an even better idea. So thank you. 01:14:50.403 --> 01:14:53.683 Yeah, that's a good one. i'd like i actually would like to do that for the machines 01:14:53.683 --> 01:14:56.963 in the studio why you know except for the recording machine why do they need 01:14:56.963 --> 01:15:02.343 local hard drives totally right one day one day distro. 01:15:02.343 --> 01:15:06.083 Stew boosts in with 11 100 and 11 sets, 01:15:12.289 --> 01:15:17.469 Yes, to Flatpak. It's not the best, but it's really getting there. 01:15:17.689 --> 01:15:21.729 I generally try to install as much as I can through Flatpak. 01:15:21.889 --> 01:15:25.749 Then if it doesn't work there, I fall back to the native package manager. 01:15:26.049 --> 01:15:28.729 This really speeds up my Nix updates too. 01:15:29.109 --> 01:15:30.429 True. That is true. 01:15:30.729 --> 01:15:34.649 But what about terminal or server apps? Snap is the closest thing I can think 01:15:34.649 --> 01:15:38.169 of in that direction, but I've not really dabbled what do y'all think. 01:15:38.169 --> 01:15:43.149 I think this is the realm of containers that's why flat pack doesn't really 01:15:43.149 --> 01:15:47.209 bother with it and while it is handy to have snap packages on server i mean 01:15:47.209 --> 01:15:51.289 i like that i think outside of that ecosystem wouldn't you say it's people use 01:15:51.289 --> 01:15:52.549 containers for that type of job. 01:15:52.549 --> 01:15:56.829 Yeah probably so i mean obviously for the server side stuff containers are pretty 01:15:56.829 --> 01:16:03.289 much king and more and more you do see i mean you know you can just run a terminal app from, you know, 01:16:03.389 --> 01:16:08.589 a Podman run or Docker run command, or you could use something like Toolbox or Distrobox too. 01:16:08.869 --> 01:16:10.949 So there are a lot more options there now. 01:16:11.089 --> 01:16:13.109 Yeah, when we were doing the TUI challenge, there was a couple of times where 01:16:13.109 --> 01:16:16.929 it's like a Podman runs essentially a one-liner, and then I've got the application up and going. 01:16:17.149 --> 01:16:19.149 That's how I was running my web browser with the whole TUI challenge, 01:16:19.189 --> 01:16:21.369 actually. So it worked for me that way. 01:16:21.589 --> 01:16:24.089 And actually, you know, it's not quite contained in the same way, 01:16:24.189 --> 01:16:27.149 but Nix can work well for TUI apps too, if you're willing to have that on your system. 01:16:28.149 --> 01:16:32.289 Well, Marcel sends in a row of ducks. i 01:16:32.289 --> 01:16:35.029 particularly liked this past episode i'm not 01:16:35.029 --> 01:16:39.309 sure why it didn't get the usual support though i don't boost often because 01:16:39.309 --> 01:16:44.209 i put my support on autopilot as you like to say with the that jupiter.party 01:16:44.209 --> 01:16:48.769 membership but since you mentioned the low boost numbers i wanted to write in 01:16:48.769 --> 01:16:52.469 and vote for more content like this keep up the good work. 01:16:52.469 --> 01:16:57.369 Well thank you marcel message received i I appreciate that signal. 01:16:57.389 --> 01:16:58.789 We can count on it right there. 01:16:59.229 --> 01:17:03.689 Just like kangaroo paradox, who's it's been a minute. I'll be dead boys. 01:17:04.709 --> 01:17:10.849 He's back. And he came in with 12,345 sats. 01:17:15.510 --> 01:17:18.790 Well, I've built behind on the shows these past weeks, slowly catching up as 01:17:18.790 --> 01:17:22.530 time rolls on, and I wanted to give a shout-out to the bootleg version of Unplugged, 01:17:22.570 --> 01:17:27.570 where you can hear Chris, uh-oh, admitting that Vim's superiority to Nano. 01:17:27.810 --> 01:17:30.350 It's in episode 618, The Tooey Challenge. 01:17:30.630 --> 01:17:33.750 And Wes enjoying the situation just all too much. 01:17:34.650 --> 01:17:35.050 Confirmed. 01:17:35.450 --> 01:17:39.090 He says, I teased the time, but it's well worth the dime. Oh, 01:17:39.150 --> 01:17:41.810 he says, I teased, but it's well worth the dime. Thank you. 01:17:41.850 --> 01:17:42.610 Oh, you're so sweet. 01:17:42.730 --> 01:17:44.930 I kind of vaguely recall that conversation. 01:17:44.930 --> 01:17:47.010 Oh, I very much recall that conversation. 01:17:48.150 --> 01:17:53.310 What you don't see in the audio version of the podcast is the pipe that Wes 01:17:53.310 --> 01:17:56.230 brought to the studio that day. It seems to have worked in this case. 01:17:58.450 --> 01:18:01.950 Oh, man. Thanks, kangaroo. You outed my secret. 01:18:02.430 --> 01:18:05.890 Turd Ferguson boosts in with 13,000 sets. 01:18:08.790 --> 01:18:12.430 I'm curious if Brent was going to make his own distribution, 01:18:12.850 --> 01:18:17.170 Brunch OS, obviously, what would the focus be and what would it be based. 01:18:17.170 --> 01:18:21.170 On oh yeah oh goodness good question 01:18:21.170 --> 01:18:24.230 oh turd i have never 01:18:24.230 --> 01:18:27.590 considered doing this i guess now i should start thanks so 01:18:27.590 --> 01:18:30.550 much for that burden and i think brunch 01:18:30.550 --> 01:18:37.230 os would clearly have some like deep privacy implications so that would be one 01:18:37.230 --> 01:18:42.930 of its main focuses you know we would try to be bug free but that's you know 01:18:42.930 --> 01:18:49.130 always a hard thing but it would clearly and obviously be based on Gentoo. 01:18:50.430 --> 01:18:54.810 Oh, there you go. I would love to try that, actually. I would love to try that. 01:18:55.650 --> 01:18:57.410 Thank you, turd. Appreciate the boost. 01:18:59.950 --> 01:19:03.250 Leclament comes in with 15,000 sets. 01:19:06.804 --> 01:19:12.804 My AI companion is OpenCode, which allows me to keep NeoVim as my main editor. 01:19:13.144 --> 01:19:20.164 I migrated a significant part of my home lab from floating Docker Compose to a monorepo Nix OS. 01:19:20.844 --> 01:19:22.744 This is a perfect setup for AI. 01:19:23.924 --> 01:19:24.444 Cool. 01:19:24.884 --> 01:19:29.904 How about that? So you can still use NeoVim. That's nice. That's really nice. 01:19:30.064 --> 01:19:31.504 I love hearing about these setups. 01:19:31.664 --> 01:19:35.624 Also, look at that, boys. They boosted from their own self-hosted AlbiHub. 01:19:35.764 --> 01:19:38.184 Boom. Oh, how can they? Well, there, you don't get the claps then. 01:19:39.044 --> 01:19:41.204 No, this was from Fountain, but it sounds like there's interest, 01:19:41.344 --> 01:19:42.704 which we should applaud, I think. 01:19:42.824 --> 01:19:46.204 Yes, that's true. Okay, all right, okay, that's fine. 01:19:47.344 --> 01:19:51.344 Step one is go listen to This Week in Bitcoin episode 68. I have the co-founder 01:19:51.344 --> 01:19:53.284 of Albie on there just so you get some broader context. 01:19:53.564 --> 01:19:56.244 And then, you know, getalbie.com to get started. 01:19:57.264 --> 01:20:01.424 I think it's even easier if you have a system that allows you to deploy, 01:20:01.444 --> 01:20:04.744 like, application containers because it's packaged up for a lot of those, 01:20:04.824 --> 01:20:08.504 like Start9 and Umbral and Unraid and all kinds of stuff. 01:20:08.584 --> 01:20:11.604 So if you have a system like that already in place, it's just a one-click away 01:20:11.604 --> 01:20:14.344 to get going. But you can also just run it as a container image too. 01:20:14.644 --> 01:20:17.444 It's really amazing how straightforward they've made it. 01:20:17.944 --> 01:20:22.464 And I bet if you, just going by what you've got going for your home lab, 01:20:22.524 --> 01:20:23.824 I think you'd probably get it running pretty quickly. 01:20:24.004 --> 01:20:27.204 And then from there you want the Albi extension, right? 01:20:27.284 --> 01:20:32.104 And then you could use an app like Podverse that can call out to that to then talk to your node? 01:20:32.584 --> 01:20:33.884 Or Podcast Index. 01:20:34.324 --> 01:20:34.584 Right. 01:20:34.904 --> 01:20:39.544 Or Cast-O-Matic if you're on iOS is really good. So there's a few options there. 01:20:39.664 --> 01:20:42.624 You get kind of like this universal backend. Good question and good luck. 01:20:43.244 --> 01:20:44.824 Let us know. Let us know. 01:20:45.464 --> 01:20:48.844 Chlorophor comes in with a row of ducks. 01:20:51.304 --> 01:20:54.264 Started AlbiHub instance 14 days ago and learned quite a lot. 01:20:54.424 --> 01:20:58.444 I even did an open direct channel to Chris's node to decrease fees and to help us with liquidity. 01:20:58.724 --> 01:21:01.624 More to come. But no channels for Brent or Drew. 01:21:02.564 --> 01:21:05.964 Zero zero zero zero is not a good routable ip address for a node. 01:21:05.964 --> 01:21:10.684 Yeah i think this is a bug in a particular version of lb it might might be fixed 01:21:10.684 --> 01:21:14.884 now but i noticed that early on too is that the the public address they were 01:21:14.884 --> 01:21:19.524 reporting was that but uh props that you're doing direct connects i mean that's 01:21:19.524 --> 01:21:22.024 awesome thanks for the boost you. 01:21:22.024 --> 01:21:26.984 Know thank you thank you for that and these really because brent and drew are 01:21:26.984 --> 01:21:30.344 taking advantage of the subwall feature they're not their actual own node so 01:21:30.344 --> 01:21:33.484 that's why that bug crops up nice spot good job. 01:21:33.484 --> 01:21:38.444 The one the only the gene bean comes in with 2048 sets, 01:21:40.397 --> 01:21:43.957 The challenge with everything being Flatpaks, though solvable, 01:21:44.297 --> 01:21:49.177 is that things like 1Password's Firefox extension don't properly work with the 01:21:49.177 --> 01:21:51.977 desktop app. This has been painful. 01:21:52.897 --> 01:21:54.977 That's good to know. Right, like anytime you do containerization, 01:21:55.177 --> 01:21:58.557 you got to get all the right holes poked through and plumbing put in, 01:21:58.657 --> 01:22:01.377 and sometimes, you know, those aren't all ready in all the places. 01:22:01.737 --> 01:22:04.777 We need another portal. That's what we need. Another portal. 01:22:04.917 --> 01:22:05.657 The password portal. 01:22:06.377 --> 01:22:08.777 Yeah, or something. The browser extension portal? I don't know. 01:22:09.157 --> 01:22:10.757 Something. Yeah, that's painful. 01:22:11.297 --> 01:22:17.097 And then Gene goes on replying to LUP625 regarding who could filter or test 01:22:17.097 --> 01:22:19.877 Flatpaks, talking about like the future of Flatpaks and Fedora. 01:22:20.497 --> 01:22:26.357 Get the package maintainers from distros to help with that, which you are saying as I type this. 01:22:28.257 --> 01:22:32.457 I love it. This was a live boost, you know, to local to Gene being as Gene was 01:22:32.457 --> 01:22:33.297 listening, which is rad. 01:22:33.777 --> 01:22:36.537 Gene, that's one of the things I love about the boost is that button's right 01:22:36.537 --> 01:22:38.897 there on the player, right? So as you're listening, you can hit the button and 01:22:38.897 --> 01:22:41.097 send us the feedback while it's fresh in your mind. You don't lose it. 01:22:41.237 --> 01:22:43.497 And that's exactly what Gene does. And I really appreciate that. 01:22:44.177 --> 01:22:47.457 Thank you, everybody who boosted in. And thank you to you sat streamers who 01:22:47.457 --> 01:22:49.057 set that sat stream while you listen. 01:22:49.497 --> 01:22:54.137 We had 27,189 sats come in. 01:22:54.197 --> 01:22:57.897 And that is not too bad right there. It's a decent little boost all in itself. 01:22:58.057 --> 01:23:02.057 When you combine that with everybody who sent a message, including the folks 01:23:02.057 --> 01:23:09.337 below the 2000sat cutoff, We stacked a grand total of 340,145 sats. 01:23:14.977 --> 01:23:18.677 This is a value for value podcast and what that means is we put the show out 01:23:18.677 --> 01:23:22.697 there for free and if you enjoy it you send some value back that could be your 01:23:22.697 --> 01:23:26.457 time participating in our community could be talent maybe you'd like to help 01:23:26.457 --> 01:23:31.717 us make some texas linux festival swag or it can be in treasure with a boost 01:23:31.717 --> 01:23:33.357 or a membership this is an 01:23:33.377 --> 01:23:36.437 independent podcast that is focused on making the best product for its audience. 01:23:36.477 --> 01:23:40.037 And we always want our audience to be our number one partner, 01:23:40.237 --> 01:23:44.397 not an advertiser, not dynamic ads, but the people consuming the content. 01:23:44.677 --> 01:23:49.137 It's a radical idea, but I think it's the best way to have genuine good content on the internet. 01:23:49.297 --> 01:23:53.717 There's not a lot of people doing it. And so we appreciate everybody who's helping make it possible. 01:23:54.237 --> 01:23:58.177 You can do a boost with Fountain FM. They make it real easy or self-host with AlbiHub. 01:24:09.536 --> 01:24:12.556 All right, we've got to let everybody know that I think we're going to be going 01:24:12.556 --> 01:24:17.856 into a wee bit of overtime here because we got too many picks. 01:24:19.496 --> 01:24:23.536 And this one I'm putting out there to get feedback from the audience. I'll start with this. 01:24:23.676 --> 01:24:28.856 It's called Papera, and it's a minimal document archiving platform. 01:24:29.196 --> 01:24:31.456 This is something I struggle with. I'm sure a lot of people do. 01:24:31.616 --> 01:24:34.976 You want to archive your documents in a digital way that makes them easy to 01:24:34.976 --> 01:24:37.996 tag and retrieve later on. This is a project under active development, 01:24:38.136 --> 01:24:40.836 but the core functionality is stable and ready for use. 01:24:40.976 --> 01:24:43.176 And it has lots of features and more coming. 01:24:44.256 --> 01:24:48.156 It organizes your documents. You know, you can categorize family, friend, business. 01:24:48.416 --> 01:24:51.676 You can share certain categories with colleagues. It makes it super easy to 01:24:51.676 --> 01:24:53.696 quickly share the documents with full text search. 01:24:53.836 --> 01:24:57.036 It has user authentication. It has a responsive design so you can use it on mobile. 01:24:57.396 --> 01:25:01.556 Yes, it is open source. It's AGPL 3.0. You can self-host it. 01:25:01.596 --> 01:25:02.676 You can tag your documents. 01:25:02.776 --> 01:25:06.616 It has email integration. It has content extraction. It can automatically extract 01:25:06.616 --> 01:25:11.756 the text from images or scan documents, making it available for search. 01:25:12.136 --> 01:25:12.556 Ooh. 01:25:13.036 --> 01:25:13.436 Huge. 01:25:13.816 --> 01:25:14.736 This looks nice. 01:25:14.996 --> 01:25:18.516 It has a command line interface, if you want. It has an API. It has webhooks. 01:25:19.096 --> 01:25:22.176 I mean, it's got a lot of the stuff, Wes. I know there's PaperlessNG, 01:25:22.316 --> 01:25:23.436 and there's other ones out there. 01:25:23.716 --> 01:25:27.676 This is something I'd be very interested in adopting, and I'm really curious 01:25:27.676 --> 01:25:33.536 if anybody has input. and paper a p-a-p-r-a which i'll have linked in the show 01:25:33.536 --> 01:25:37.056 notes as well as the demo looks like a real contender here boys i. 01:25:37.056 --> 01:25:39.656 Like how they call out self-hosting right like they've got a. 01:25:39.656 --> 01:25:40.636 Yeah under. 01:25:40.636 --> 01:25:45.616 200 meg docker image compatible with x86 arm 64 and arm v7. 01:25:45.616 --> 01:25:50.216 You know you should be thanking me brent you should be thanking me for this 01:25:50.216 --> 01:25:53.576 pick i'm doing the lift here for you because you're living the hashtag van life now. 01:25:53.576 --> 01:25:59.096 Ah and you want me to live kind of efficient and keep all those documents stored somewhere safe. 01:25:59.096 --> 01:26:02.936 Are you gonna bring are you gonna bring all of your records all of your cat's 01:26:02.936 --> 01:26:06.336 vet records all their stuff with you everywhere you go forever as you just collect 01:26:06.336 --> 01:26:10.316 more and more as you become an old man and then god forbid what happens if something 01:26:10.316 --> 01:26:13.736 happens to the rig and you lose your documents you know i. 01:26:13.736 --> 01:26:17.676 Appreciate how you're slowly trickling in the problems to solve with this van 01:26:17.676 --> 01:26:21.436 life uh new lifestyle that you've somehow yeah. 01:26:21.436 --> 01:26:24.356 Where he didn't say this back in california did he. 01:26:24.356 --> 01:26:27.776 I might have left that bit out yeah but you know through the pick segment i 01:26:27.776 --> 01:26:29.456 can help you along you know i appreciate. 01:26:29.456 --> 01:26:36.096 It i also think maybe if you consider uh like perhaps this project might be canadian it's paper a. 01:26:36.096 --> 01:26:40.916 Paper a maybe paper a paper a it. 01:26:40.916 --> 01:26:41.636 Is a gpl. 01:26:41.636 --> 01:26:48.096 Paper a i i don't have the natural positive canadian up talk with the a yeah 01:26:48.096 --> 01:26:52.596 i really have to work on that i'm not big on the up talk thing so that's fine. 01:26:52.596 --> 01:26:53.536 We'll get happy. 01:26:54.731 --> 01:26:58.611 Well, Canadians. From the category of where was this during the TUI challenge, 01:26:58.611 --> 01:27:02.551 we have Lou, which is a terminal e-book reader with text-to-speech. 01:27:03.011 --> 01:27:05.451 And isn't it pretty? I mean, look at that interface. 01:27:06.811 --> 01:27:11.371 It's beautiful. I really do actually wish I knew about this sooner because I 01:27:11.371 --> 01:27:14.591 could see even if you're just reading a manual that's in an e-book format or 01:27:14.591 --> 01:27:17.891 something or, you know, some book related to what you're working on. 01:27:18.091 --> 01:27:20.791 It supports EPUBs, PDF, text, docx. 01:27:21.491 --> 01:27:23.911 Obviously, doc files, HTML, RTF, markdown. 01:27:24.731 --> 01:27:29.091 All just automatically detected. The text-to-speech system is modular. 01:27:29.091 --> 01:27:31.911 You don't have to have it. It can run locally if you do want it. 01:27:33.031 --> 01:27:36.631 It saves your place. It switches between reading and speaking, 01:27:36.631 --> 01:27:38.611 and it saves your place. It's GPL3. 01:27:38.831 --> 01:27:41.771 It's got nice intuitive keyboard shortcuts. 01:27:42.111 --> 01:27:45.011 Including Vim-like shortcuts, if you'd like. 01:27:45.291 --> 01:27:51.051 Oh, good. Good. And I guess surprisingly smooth scrolling and transitions for 01:27:51.051 --> 01:27:53.811 a terminal app, which I think is just a funny thing to actually call out. 01:27:53.811 --> 01:27:57.431 But there it is hey that looks so good and. 01:27:57.431 --> 01:27:59.491 Of course it uses our beloved ffmpeg. 01:27:59.491 --> 01:28:03.731 Under the hood yeah yeah and then if you're going to try out hypervibe and you 01:28:03.731 --> 01:28:07.531 want to take it to the absolute max i guess i do have my limits i didn't do 01:28:07.531 --> 01:28:14.551 this out of the box i have my limits it's called wlg block wayland gameboy locker. 01:28:14.551 --> 01:28:21.171 Yeah this project replaces the usual password screen with a gameboy emulator 01:28:21.171 --> 01:28:25.651 running a patched pokemon game so to unlock your session you have to solve a 01:28:25.651 --> 01:28:29.851 little challenge kind of like a mini escape room built into your os. 01:28:29.851 --> 01:28:35.651 Yeah a pokemon puzzle kind of thing and then you unlock the screen uh you got 01:28:35.651 --> 01:28:37.971 a lot of time on your hands if you're using this and. 01:28:37.971 --> 01:28:42.791 You can tell um something this crazy clearly came from a nix user and yes there 01:28:42.791 --> 01:28:47.211 is a flake in there and there's a nix os logo in the little demo video so we're 01:28:47.211 --> 01:28:48.451 we're just that type aren't we. 01:28:48.451 --> 01:28:54.271 My goal is to get you to try out the Hypervibe setup on your ancient laptop 01:28:54.271 --> 01:28:58.251 and see if you notice a performance difference. And then I think you should get this going. 01:28:58.451 --> 01:29:00.931 Oh yeah, that sounds like a good homework item from this show. 01:29:01.031 --> 01:29:07.011 I mean, I'd love to see it. Not a temporary K exec. I'm on to you. 01:29:08.431 --> 01:29:12.291 I'm on to you. I think you should try to convert your base to Nick system. 01:29:12.431 --> 01:29:13.591 Full swap, okay. 01:29:13.851 --> 01:29:16.891 Go all in. Go all in and see if you can make Hyperland work. 01:29:17.051 --> 01:29:19.871 See if you notice the performance improvement. see if your fans run more give 01:29:19.871 --> 01:29:22.711 me feedback on it you know in fact i extend that to everybody 01:29:22.711 --> 01:29:26.171 go try it out and give me feedback and let me know also i 01:29:26.171 --> 01:29:29.071 want you to boost in and tell me if you think i'm off guard on the bcash fs 01:29:29.071 --> 01:29:32.411 situation and what your resolution could be i 01:29:32.411 --> 01:29:35.351 mean if you had a magic wand for one day and could solve this how would you 01:29:35.351 --> 01:29:39.651 solve it it's not necessarily an easy problem people problems well they matter 01:29:39.651 --> 01:29:44.431 right it's right now we're in a situation where it's feels over features but 01:29:44.431 --> 01:29:47.971 it's a project of people so boost in maybe i'm off i'd love to hear your take 01:29:47.971 --> 01:29:49.231 on it, even if you disagree with me. 01:29:49.851 --> 01:29:54.291 And of course, we will be live at the same time on the same bat channel next week. 01:29:58.507 --> 01:30:01.607 It's on a Sunday, so you can make it a Tuesday on a Sunday when you come and 01:30:01.607 --> 01:30:04.587 join us. We start at 10 a.m. Pacific, usually a little earlier than that even. 01:30:05.207 --> 01:30:08.067 1 p.m. Eastern, local time at jblive.tv. 01:30:08.727 --> 01:30:11.847 Now, Wes, there's something really important we need to remind the audience 01:30:11.847 --> 01:30:14.427 about an extra set of features they have. 01:30:14.767 --> 01:30:18.647 It's that they can watch us live in their podcasting app, right? 01:30:19.127 --> 01:30:22.447 That's one of them. And we got transcripts, too. We got chapters. 01:30:22.887 --> 01:30:27.727 Yeah, we do. Cloud chapters, magic JSON, floating in the clouds, ready for you. 01:30:27.727 --> 01:30:27.927 That's right. 01:30:27.927 --> 01:30:28.567 For you. 01:30:29.067 --> 01:30:31.727 Not just crammed in there, but JSON chapters. It's beautiful. 01:30:32.007 --> 01:30:35.787 Links to what we talked about today at linuxunplugged.com slash 628. 01:30:36.107 --> 01:30:38.027 Thanks for joining us. See you next Sunday.