WEBVTT 00:00:31.752 --> 00:00:35.961 Why not make it a Linux Tuesday on a Sunday? Join us Sunday, 00:00:35.961 --> 00:00:37.610 10 a.m. Pacific, 1 p.m. Eastern. 00:00:37.935 --> 00:00:42.411 And remember, if you want more show, we got that LUP-LUG every Sunday before 00:00:42.411 --> 00:00:45.330 the show, getting together, LUP-LUG details at our website. 00:00:46.369 --> 00:00:49.591 And of course, links to everything we talked about today. Technically, 00:00:49.777 --> 00:00:51.199 everything we've talked about in the past, too. 00:00:51.965 --> 00:00:56.586 And how to contact us, Mumble Room, Matrix, all that, linuxunplugged.com. 00:00:57.497 --> 00:01:00.061 Don't forget you can support us at boost.jupiterbroadcasting.com. 00:01:00.061 --> 00:01:01.771 Thank you so much for joining us this week. 00:01:01.771 --> 00:01:05.891 Whoa, whoa, you're not going to tell them? We got all kinds of special stuff 00:01:05.891 --> 00:01:09.241 in the feed. We got JSON. We got cloud chapters. We got transcripts. 00:01:09.561 --> 00:01:13.561 We got an MP4 file in there. Who put that in there? A whole giant MP4 file. 00:01:13.581 --> 00:01:14.101 It's actually not that big. 00:01:14.161 --> 00:01:14.713 Did you put that in there? 00:01:15.021 --> 00:01:15.441 Yeah. 00:01:15.441 --> 00:01:19.114 All right. All right. We'll see you next Tuesday, as in Sunday. 00:01:19.485 --> 00:01:20.838 And don't forget about that live stream. 00:01:25.133 --> 00:01:28.407 All right. Normally, I think we'd be done right here. But before we wrap up, 00:01:28.529 --> 00:01:31.571 I just want to say thank you to our friends over at Define Networking. 00:01:31.571 --> 00:01:33.249 Define.net slash unplug. 00:01:33.672 --> 00:01:36.081 Go over there and check out Manage Nebula from Define Networking. 00:01:36.121 --> 00:01:39.698 It's built on the open source Nebula platform that we love and use right now. 00:01:40.087 --> 00:01:43.061 And now you can take advantage of their automatic lighthouse or you can add 00:01:43.061 --> 00:01:44.493 your own or combo it all up. 00:01:45.341 --> 00:01:48.161 That's the thing. It's control. And that's what's big for me because it's my 00:01:48.161 --> 00:01:50.402 infrastructure. It's my network infrastructure. 00:01:51.661 --> 00:01:55.714 I can own the entire stack. I can turn it on. I can turn it off. I control it. 00:01:56.196 --> 00:01:59.074 and I can use their lighthouse if I want. I think that's fantastic. 00:01:59.474 --> 00:02:01.931 And Nebula is lightweight on systems that are sitting there idle. 00:02:01.931 --> 00:02:03.660 It uses very little CPU and network. 00:02:04.014 --> 00:02:07.776 Some of the other solutions, real chatty, constantly chatty. 00:02:08.408 --> 00:02:11.841 And that matters a lot when you're running it across your entire home lab on 00:02:11.841 --> 00:02:15.305 your remote systems. Maybe you're on a Starlinkle. It matters. 00:02:16.390 --> 00:02:18.781 And the great thing about Nebula is it's built for scale from day one. 00:02:18.781 --> 00:02:21.821 With strong encryption, decentralized by design, it stays resilient. 00:02:21.821 --> 00:02:24.151 So get started. 100 hosts for free. No credit card required. 00:02:24.151 --> 00:02:28.931 Go to Define.net slash unplug. That is Define.net slash unplug. 00:02:28.931 --> 00:02:30.369 Big thank you to Define Networking. 00:02:32.036 --> 00:02:35.826 All right, boys, before we run, we've got some picks to get to. 00:02:36.395 --> 00:02:41.190 And I wanted to hit you with a strange one. This is a big one. It's LAN Orangutan. 00:02:41.591 --> 00:02:45.965 And it is a lightweight network scanner that goes through and labels your network. 00:02:45.965 --> 00:02:49.898 But it is easy and simple, but yet efficient. 00:02:50.971 --> 00:02:53.225 Take a look at it. What do you think? What was your first impression? 00:02:53.225 --> 00:02:57.635 Yeah, it's clean. So, like, we've talked a lot about tools vaguely in this camp. 00:02:57.635 --> 00:03:02.505 But, and sometimes I like this, but often you kind of get information overload. 00:03:02.505 --> 00:03:02.755 Right? 00:03:02.755 --> 00:03:05.625 You're like all kinds of details, hardware stuff that I probably don't need 00:03:05.625 --> 00:03:06.925 for whatever it is the task I'm actually trying to do. 00:03:07.245 --> 00:03:09.755 And maybe I don't need it for like ever, right? I just want to know for a little 00:03:09.755 --> 00:03:11.375 while so I can spin up real quick. 00:03:11.375 --> 00:03:14.815 Whereas this just looks like a very clean dashboard you could take a quick glance 00:03:14.815 --> 00:03:16.335 at and get a sense for what's going on. 00:03:16.335 --> 00:03:19.485 Here you go, Brentley. So when you get moved, when you get your network going, 00:03:19.485 --> 00:03:21.755 I want you to pop this thing up and take a screenshot for us, 00:03:21.755 --> 00:03:24.923 all right? It's a self-hosted network discovery tool for home labbers, 00:03:25.312 --> 00:03:27.146 and it has tailscale support as well. 00:03:27.541 --> 00:03:30.175 Oh, and there's a CLI. I like that. 00:03:30.175 --> 00:03:34.443 Auto-discovers your devices, password protected. What do you think? 00:03:34.582 --> 00:03:35.865 When you get your new LAN online? 00:03:36.289 --> 00:03:40.995 It looks like it's been around a while, too, yeah. I mean, I have not really 00:03:40.995 --> 00:03:44.025 done very good network monitoring, I have to say. 00:03:44.765 --> 00:03:49.035 And just last week, I was like, huh, I should probably know what's happening 00:03:49.035 --> 00:03:52.775 on the network here, wherever I am. You know, I'm kind of in charge of the network 00:03:52.775 --> 00:03:54.649 wherever I seem to end up, so... 00:03:55.502 --> 00:03:58.431 I should do better. And this is maybe a tool that can help me do that. 00:03:58.431 --> 00:04:00.280 So thank you for the picks. 00:04:00.599 --> 00:04:01.221 Do better. 00:04:01.221 --> 00:04:04.701 I like they have a philosophy in here, actually, which we kind of touched on 00:04:04.701 --> 00:04:06.398 without maybe even fully realizing. 00:04:07.205 --> 00:04:10.191 Lan Orangutan isn't trying to be the most powerful scanner out there. 00:04:10.191 --> 00:04:13.931 And that's the point. It's built to be the simplest and the fastest one to reach for. 00:04:14.291 --> 00:04:17.143 There's a bunch of already excellent, deeply capable tools in this space. 00:04:17.439 --> 00:04:20.191 And they're the right choice when you need everything they offer. 00:04:20.811 --> 00:04:23.082 Lan Orangutan is for the other times. 00:04:23.296 --> 00:04:27.941 Also, you know, you could, if you're a Clanker user, you could have the CLI 00:04:27.941 --> 00:04:31.391 kind of do these audits and it'll do the output as JSON and the Clanker can 00:04:31.391 --> 00:04:35.251 take that in. You could just spin up this thing, do a little network scan and 00:04:35.251 --> 00:04:36.160 then get a Clanker report. 00:04:36.311 --> 00:04:38.442 Even CSV if you have like an enterprise Clanker. 00:04:39.611 --> 00:04:42.841 I'm going through like the docs here trying to figure out where the naming comes 00:04:42.841 --> 00:04:46.411 from. I don't think I found anything. So, listener, if you have any ideas or 00:04:46.411 --> 00:04:52.981 theories or, I don't know, make up some reason why the orangutan is the land expert, let us know. 00:04:52.981 --> 00:04:57.179 Maybe it's a reference to another tool. I don't know. MIT license on that one. 00:04:57.498 --> 00:05:00.351 And then really quickly, this isn't going to surprise anyone. 00:05:00.351 --> 00:05:04.441 I just had to give it a shout because it saved my bacon a couple of times in just the last week. 00:05:05.770 --> 00:05:08.341 I'm kind of embarrassed. It's called local send. I don't know why. 00:05:08.341 --> 00:05:12.581 It's just there are so many of these stupid open source send a file from one 00:05:12.581 --> 00:05:16.446 computer to the other that it almost feels embarrassing to even have a pick. 00:05:18.117 --> 00:05:24.824 But I like LocalSend because it's a local app on every OS. So like on the desktop, 00:05:24.824 --> 00:05:27.764 it's a desktop application. On iOS, it's an iOS application. 00:05:27.764 --> 00:05:29.130 On Android, it's an Android application. 00:05:30.041 --> 00:05:33.594 I did a little spelunking. And it's interesting that it's finally landed because 00:05:33.594 --> 00:05:37.264 we talked about it ages and ages ago on the show. And you and Alex talked about 00:05:37.264 --> 00:05:38.708 it on a self-hosted episode. 00:05:38.952 --> 00:05:41.084 But it felt like maybe it was one of those picks where it's like, 00:05:41.084 --> 00:05:43.924 oh, this is cool and seems useful. But then if you never actually deploy it, 00:05:43.924 --> 00:05:47.174 you don't quite use it. So what changed that you're using it? 00:05:47.174 --> 00:05:51.274 So I was taking pictures of the chickens and whatnot, and I wanted to transfer 00:05:51.274 --> 00:05:54.924 them to the desktop. And there's just not, from the iPhone at least, 00:05:54.924 --> 00:05:58.362 not a lot of great options here. If I were on Android, I might use KDE Connect. 00:05:59.343 --> 00:06:03.954 But so I set this up. But then because it works across Android, 00:06:03.954 --> 00:06:07.987 it works across Linux and iOS, then it's like, well, let's all just use this. 00:06:08.457 --> 00:06:10.982 And it'll queue up downloads too. The desktop app's pretty nice. 00:06:11.724 --> 00:06:14.774 You can auto-accept files from certain favorite people and things like that, 00:06:14.774 --> 00:06:17.664 which is really nice. Like I just grabbed this and I just want to blast it over 00:06:17.664 --> 00:06:19.649 to the machine. I don't have to be at my desktop and approve it. 00:06:20.704 --> 00:06:23.602 And so it's like one of these things where I, you know, I've actually been using this. 00:06:23.974 --> 00:06:26.344 And I don't know if we've made an implicit pick, but we have talked about it 00:06:26.344 --> 00:06:31.024 before. And it also, it's all local, right? So there's no like routing through 00:06:31.024 --> 00:06:34.005 the internet or anything like that. So it's as fast as your LAN can blast the file. 00:06:34.678 --> 00:06:37.494 This is one of those apps that since the last time we talked about it, 00:06:37.494 --> 00:06:39.200 it's been installed on my phone. Yeah. 00:06:40.263 --> 00:06:45.638 I guess, and my laptop, which I, is it? And on my phone, every time I go like, 00:06:45.638 --> 00:06:47.658 you know, do some spring cleaning on my phone, I'm like, well, 00:06:47.658 --> 00:06:51.058 I only use this once, maybe twice a year. 00:06:51.058 --> 00:06:51.516 Yeah. 00:06:51.644 --> 00:06:54.848 And then I will always land with, well, you never know, I'm going to keep it. 00:06:54.848 --> 00:06:57.356 So this has been installed for a very long time for me. 00:06:57.896 --> 00:07:02.038 Used it a couple of times. It's saved my bacon, but it's nice. 00:07:02.048 --> 00:07:05.518 What I appreciate about it is like, if I'm doing, if I'm transferring some drone 00:07:05.518 --> 00:07:08.538 footage or I took some pictures of the kids or the chickens and I want to do 00:07:08.538 --> 00:07:11.568 a batch, It's really good at a whole bunch of files, too. And then on the desktop, 00:07:11.568 --> 00:07:16.013 I get, like, a visual status progress of all the files transferring and stuff. 00:07:16.756 --> 00:07:21.968 So I like LocalSend, and it's available on Flathub, and it is Apache 2.0. 00:07:21.968 --> 00:07:26.625 I figured out what's going on here. Well, it's 17.5% rust. 00:07:26.991 --> 00:07:29.127 Oh. Do you think that justifies? 00:07:29.237 --> 00:07:33.568 Well, the rest of it, it's Dart. I know you're a big Dart guy. 00:07:33.568 --> 00:07:34.148 Big Dart guy. 00:07:34.148 --> 00:07:35.638 Huge Dart and Flutter fan, so. 00:07:35.638 --> 00:07:40.638 Make a lot of choices in life on that, you know? That ATM uses Flutter, 00:07:40.638 --> 00:07:43.008 I'm picking that bank. That's how I roll. 00:07:43.512 --> 00:07:46.488 Before we get out of here, I have a sneaky pick for you guys. 00:07:46.488 --> 00:07:49.868 Yeah, I want to know about this. You snuck it in, we don't have any idea about it. 00:07:51.208 --> 00:07:52.868 Yeah, the council didn't get to approve it. 00:07:53.608 --> 00:07:55.927 Usually when that happens, it means it's a banger, so we'll see. 00:07:56.130 --> 00:08:01.454 Hasn't even been vetted by the bot. I've been toying with this one for the last couple of weeks. 00:08:02.488 --> 00:08:07.098 I, you know, we've been on the show really enjoying open code on the desktop 00:08:07.098 --> 00:08:12.547 to do a great variety of things. And I have deeply integrated that into my everyday workflow. 00:08:13.133 --> 00:08:14.642 I wanted something similar on the phone. 00:08:15.594 --> 00:08:20.902 On the phone, it's often like just the chat app kind of interaction that at least I've found. 00:08:22.346 --> 00:08:25.352 But I wanted something simple and yet powerful. And maybe that's asking too 00:08:25.352 --> 00:08:30.382 much. But I came across something called Oxproxion, which surprisingly... 00:08:30.442 --> 00:08:30.922 Say that again? 00:08:31.442 --> 00:08:32.642 Oxproxion. 00:08:33.042 --> 00:08:34.385 It's a fun name to say. 00:08:34.565 --> 00:08:39.062 Surprisingly, I only like read it once. And then it's a very memorable name 00:08:39.062 --> 00:08:42.466 for some reason for me. It might not be for other people. Sounds kind of dark, maybe. 00:08:43.282 --> 00:08:49.047 But it's just an Android LM chat interface, but it supports OpenRider, which we love. 00:08:49.582 --> 00:08:52.742 And you can also have it support a bunch of locally served models, 00:08:52.742 --> 00:08:58.469 like OLAMA, LMStudio stuff, LAMA CPP, and also, Chris, Hermes Agents. 00:08:58.660 --> 00:09:00.482 Hey, oh, really? I like that. 00:09:01.824 --> 00:09:06.102 So it's kind of like a nice mobile interface to your favorite providers, 00:09:06.482 --> 00:09:09.214 but it also has some pretty powerful features in there. 00:09:09.336 --> 00:09:13.892 And some of it is, and I haven't played with all of these, but some Android 00:09:13.892 --> 00:09:17.445 tools. So it can do stuff like read files, make files on your Android. 00:09:18.782 --> 00:09:23.432 But also take control of like timers and alarms and calendar events and stuff like that. 00:09:23.432 --> 00:09:24.313 On your local Android? 00:09:24.487 --> 00:09:25.722 Mm-hmm. 00:09:25.722 --> 00:09:28.252 Now that is promising. 00:09:28.252 --> 00:09:31.906 All right. So you can use it to automate like a calendar event on your phone? 00:09:32.097 --> 00:09:35.603 That's what I'm thinking. Now this has not been tested or vetted by me yet. 00:09:35.824 --> 00:09:37.822 I see this could be super useful. 00:09:38.462 --> 00:09:42.472 I do hesitate slightly because I don't know. But it seems very promising. 00:09:42.472 --> 00:09:44.437 So I've been using this for the last couple of weeks. 00:09:45.422 --> 00:09:50.872 I will say the interface is all symbols, and therefore you need to just trip 00:09:50.872 --> 00:09:55.362 over what the symbols mean and try to figure it out. But once you do, it's pretty powerful. 00:09:55.982 --> 00:09:57.777 What do you mean? I see tons of text. What are you talking about? 00:09:58.126 --> 00:09:59.882 Like all the model selection is text and everything. 00:09:59.882 --> 00:10:03.612 Yeah, that's like kind of one of the back interfaces once you hit one of the buttons. 00:10:03.612 --> 00:10:04.452 Ah, ah. 00:10:04.452 --> 00:10:08.562 Yeah, yeah. So that's my only gripe about it, I would say. Other than that, 00:10:08.562 --> 00:10:12.252 you can save conversations and bring them back up and continue them. 00:10:12.252 --> 00:10:15.953 And I assume you're able to install this with Obsidian, I assume? 00:10:17.165 --> 00:10:21.565 Um, you are able to install this with. 00:10:22.117 --> 00:10:22.558 Obsidian. 00:10:22.918 --> 00:10:26.311 No, not Obsidian. What's it called? I always remember this one. 00:10:26.311 --> 00:10:28.901 I do that all the time. I do that all the time. 00:10:28.901 --> 00:10:29.891 I see an APK on GitHub. 00:10:29.891 --> 00:10:33.171 Which is usually a good. They even kind of have semi-similar icons with my theme. 00:10:33.171 --> 00:10:33.531 It's the worst. 00:10:33.951 --> 00:10:36.397 Because I have like an all-black icon theme. It's, ah, yeah. 00:10:36.629 --> 00:10:40.581 So, Obtainium grabs basically APKs straight from GitHub. It's awesome. 00:10:40.581 --> 00:10:43.466 You can definitely do that here. It's also an FDroid. That's where I found it. 00:10:43.884 --> 00:10:48.061 It also will connect, obviously, to a local Olama instance. because it's LLM 00:10:48.061 --> 00:10:50.401 Studio. It's model agnostic, which is right. 00:10:50.401 --> 00:10:50.914 Mm-hmm. Mm-hmm. 00:10:53.329 --> 00:10:54.051 Oxproxion? 00:10:54.491 --> 00:10:55.411 Oxproxion. 00:10:57.323 --> 00:11:03.451 Mostly written in Kotlin, and it is Apache 2.0 licensed. Well, there you go. 00:11:03.451 --> 00:11:06.076 This seems like giving a try. Good find, Brent. 00:11:06.291 --> 00:11:09.001 Look at him. He's fully immersed now. There's no getting him back. 00:11:09.001 --> 00:11:09.331 It's your fault. 00:11:09.331 --> 00:11:11.801 Now all we need is, like, audio support maybe in this thing? 00:11:11.801 --> 00:11:12.221 Yeah. 00:11:12.221 --> 00:11:12.851 Web RTC? 00:11:13.211 --> 00:11:13.751 Indeed. 00:11:13.751 --> 00:11:14.131 Hmm. 00:11:18.906 --> 00:11:21.671 Well, we're going to start out with a heck of a baller boost, 00:11:21.671 --> 00:11:24.978 boys, so get your seatbelt on because I'm glad we got them retrofitted. 00:11:25.454 --> 00:11:26.945 Lutris, um... 00:11:27.178 --> 00:11:27.771 Lucidropy. 00:11:28.451 --> 00:11:28.551 Yeah. 00:11:29.031 --> 00:11:29.848 Kind of like entropy. 00:11:30.039 --> 00:11:30.961 But with Lutris. 00:11:30.961 --> 00:11:36.094 Yeah. Right. Comes in with 314,659 sats. 00:11:41.172 --> 00:11:41.278 Oh! 00:11:45.897 --> 00:11:50.448 Wow, that is great. That is great. Cool. He says, Py for your efforts. 00:11:50.448 --> 00:11:56.758 Thanks for all you do. Been trying out Hermes with Open Router using Nemetron's super, super, super. 00:11:57.098 --> 00:11:58.552 Nemetron's gotten surprisingly good. 00:11:59.115 --> 00:12:02.638 And popular. Trying to find a cost-effective models that are also good at network 00:12:02.638 --> 00:12:05.298 management, say like an OpenWRT, and playing with NixConfig, 00:12:05.298 --> 00:12:08.996 the NixOS MCP, and troubleshooting on Arch and Ubuntu occasionally, 00:12:09.326 --> 00:12:13.628 and writing some basic Python bash scripts to automate tasks with occasional small coding projects. 00:12:13.941 --> 00:12:16.498 I've been using Cloud Code for most of this, but want to move away from that. 00:12:16.498 --> 00:12:18.957 Any suggestions? I prefer it open source. 00:12:20.176 --> 00:12:23.273 So, Wes, this is probably a best question for you because you've even gone as 00:12:23.273 --> 00:12:26.473 far as renting some GPU and running some models directly in the open source 00:12:26.473 --> 00:12:28.837 space. So you probably have the most hands-on experience. 00:12:29.005 --> 00:12:31.503 It kind of depends on, yeah, are you trying to run it yourself? 00:12:31.503 --> 00:12:34.633 Then you're going to be mostly constrained by what token rate do you need and 00:12:34.633 --> 00:12:36.203 how much RAM or VRAM you have. 00:12:36.203 --> 00:12:37.793 Sounds like he's open to open router, though. 00:12:37.793 --> 00:12:41.723 Yeah. And so for there, I mean, one version is just go take, 00:12:42.283 --> 00:12:43.993 you can curl their API or have the bot do it. 00:12:43.993 --> 00:12:49.153 And then it's pretty easy to check out, like, what are good prices and what 00:12:49.153 --> 00:12:52.967 are currently free. and then you can easily sample all of those. 00:12:53.823 --> 00:12:57.273 Obviously, there's like the latest version 731 of DeepSeek that's been quite 00:12:57.273 --> 00:12:59.556 popular and works very nicely. 00:13:00.543 --> 00:13:03.763 QEN 3.7 has been pretty good. There's also a new QEN 3.8 Max, 00:13:03.763 --> 00:13:04.903 I think, floating around. 00:13:05.384 --> 00:13:10.243 And there's a bunch of like more interesting ones like Ling or Laguna or Longcat 00:13:10.243 --> 00:13:15.883 that kind of pop around that show you what smaller labs can do that I think can be fun to evaluate. 00:13:15.883 --> 00:13:19.993 But I probably get the most use in terms of open weight models that I pay for 00:13:19.993 --> 00:13:23.423 per token out of DeepSeek. And then I also like Memo a lot because it's pretty 00:13:23.423 --> 00:13:24.883 good and it's got vision. 00:13:25.376 --> 00:13:30.450 I would also add, maybe hang on to the Cloud subscription for a couple of weeks, 00:13:30.607 --> 00:13:33.453 try these out, and then audit what they produce with the Cloud code. 00:13:33.453 --> 00:13:33.873 There you go. 00:13:33.873 --> 00:13:36.443 And then when you find something that you like, yeah, you stick with it. 00:13:36.443 --> 00:13:39.992 And then you can wrap up the Cloud code subscription. I think that's probably a decent way to go. 00:13:40.718 --> 00:13:42.691 Can I suggest maybe a wild card here? 00:13:43.295 --> 00:13:45.383 Yeah, you got a wild card? Go for it, you wild man. 00:13:45.383 --> 00:13:49.779 So I've been doing a lot of these very tasks. 00:13:49.913 --> 00:13:54.063 OpenWRT configurations, check, Nix configs. Yep, check, check. 00:13:55.103 --> 00:13:58.133 Troubleshooting Arch and Ubuntu. Well, yes, very occasionally. 00:13:58.133 --> 00:14:02.521 Unfortunately, I still have a system I'm dealing with. But it's made that system way better. 00:14:03.177 --> 00:14:08.503 So I think I fit really well in this one. And I have found an insane amount 00:14:08.503 --> 00:14:14.688 of value and speed out of DeepSeq v4 Flash. And... 00:14:16.041 --> 00:14:17.850 It is so cheap. It's super fast. 00:14:17.850 --> 00:14:18.282 Yeah. 00:14:18.491 --> 00:14:22.510 And it's like with a little bit of structure around it, you know, 00:14:22.510 --> 00:14:23.669 with your own skills and stuff. 00:14:24.040 --> 00:14:29.970 Super, super powerful. So if you don't want to spend a ton, that is a huge recommendation for me. 00:14:30.450 --> 00:14:34.910 I don't think it would maybe beat any of the other ones. But if you're looking 00:14:34.910 --> 00:14:35.777 for something really simple. 00:14:36.694 --> 00:14:40.560 Get a good harness, get some good skills and go deep seek. See how it goes. I think it's a good tip. 00:14:42.151 --> 00:14:47.250 Well our buddy adversary 17 comes in with 56 000 and 17 sets. 00:14:48.430 --> 00:14:51.218 Oh thank you so. 00:14:52.338 --> 00:14:56.977 Reverse linux process is restoring a backup you should go in depth about backups. 00:14:57.139 --> 00:15:04.160 Backups sorry i fell i fell asleep but i that isn't a horrible idea that is i think. 00:15:04.160 --> 00:15:05.890 Adversaries You mentioned it earlier in the show. 00:15:06.430 --> 00:15:11.970 This is a very on-topic boost because you may have noticed things are a little 00:15:11.970 --> 00:15:13.155 different this episode. 00:15:13.532 --> 00:15:17.920 I think actually the reverse Linux here would be to do a recovery from your 00:15:17.920 --> 00:15:22.937 backups because most of us don't really do that part, and that's the most important part, isn't it? 00:15:23.610 --> 00:15:25.650 Sure, sure, sure. 00:15:25.650 --> 00:15:28.720 Right, and it's because it's kind of going backwards in time when you do that. 00:15:28.720 --> 00:15:28.870 Mm-hmm. 00:15:29.190 --> 00:15:31.050 Yeah. Okay, well, we got a bunch 00:15:31.050 --> 00:15:34.405 more from adversaries, including adversaries has gone to plaid. Yeah. 00:15:40.750 --> 00:15:43.370 And it's a time travel booth, which makes sense given the sound effects. 00:15:43.370 --> 00:15:47.300 A little bit behind, but I just converted my desktop PC to Nix OS. 00:15:47.440 --> 00:15:48.190 Oh, all right. 00:15:48.190 --> 00:15:51.210 I used Nix to build a custom installer ISO so that I could verify everything 00:15:51.210 --> 00:15:54.800 was hunky-dory before doing the needful and having Disco wipe the Pop! 00:15:54.800 --> 00:15:56.970 OS install. Now that's the way to do it. 00:15:58.943 --> 00:16:00.570 In fact, just to celebrate, I mean, 00:16:00.570 --> 00:16:03.630 the Nix boost really fits because it's boosty, boosty, boosty, boost. 00:16:03.630 --> 00:16:09.300 Oh, hold on. That's a special request. You don't just boast those out everywhere. 00:16:09.706 --> 00:16:11.238 Actually, but for the occasion. 00:16:13.281 --> 00:16:13.680 There you go. 00:16:15.880 --> 00:16:20.520 Adversaries choose to run the Zen kernel. Performance, baby. So we got a Zen friend. 00:16:20.520 --> 00:16:21.141 Yes. 00:16:21.500 --> 00:16:24.460 And on top of that, thank you for covering all the kernel stuff. 00:16:24.460 --> 00:16:26.422 I know it's a lot of work, but I love hearing about it. 00:16:26.731 --> 00:16:30.150 That AMD regression in 7.2 would affect me since that's what my desktop runs, 00:16:30.150 --> 00:16:32.256 so I'll keep an ear open for the fix. 00:16:32.419 --> 00:16:34.830 I assume also you're very concerned about AppleTalk getting removed. 00:16:34.830 --> 00:16:35.740 Well, naturally. 00:16:35.740 --> 00:16:37.660 We have a sticker for that. Badge? 00:16:37.660 --> 00:16:37.760 Yeah. 00:16:38.080 --> 00:16:39.160 Yeah, we call it a badge. 00:16:39.160 --> 00:16:40.400 Yeah, a sticker. 00:16:40.400 --> 00:16:44.850 And the final adversary message here, the backwards show idea sounds so fun. 00:16:44.850 --> 00:16:47.810 All you got to do is read everything backwards and then have Drew reverse the track. 00:16:47.810 --> 00:16:49.740 You know, this backwards show, we're never going to do that. 00:16:49.740 --> 00:16:51.380 That's too cliche. We would never do that. 00:16:54.066 --> 00:16:54.400 All right. 00:16:54.400 --> 00:16:54.700 What are we doing? 00:16:54.700 --> 00:16:55.940 Thank you, adversaries. Nice to hear from you. 00:16:57.136 --> 00:17:02.007 We have booze here from Greg the Lawyer, 53,403 Satoshis. 00:17:02.135 --> 00:17:02.889 All right. 00:17:08.089 --> 00:17:12.339 Uh, Greg's in the chat, 52 years old, and says, this is a zip code boost. 00:17:12.722 --> 00:17:13.495 Hey, it's been a minute. 00:17:14.095 --> 00:17:14.550 Whoa! 00:17:15.874 --> 00:17:16.884 Did you bring the, uh... 00:17:17.064 --> 00:17:17.705 You know I did. 00:17:17.705 --> 00:17:22.579 Oh, good. Here we go. Nice. Why do you... We get you the tablet. 00:17:22.991 --> 00:17:24.395 Why does it make paper sounds? 00:17:24.395 --> 00:17:25.455 Uh, Wes, you're holding the mirror on. 00:17:25.455 --> 00:17:27.763 I hacked those in there. I had to jailbreak it. Yeah. 00:17:29.259 --> 00:17:30.255 Wes, are you holding the mirror backwards? 00:17:30.989 --> 00:17:33.565 There's still gravy on here from the Canada trip. 00:17:33.565 --> 00:17:34.035 Where is he? 00:17:34.055 --> 00:17:36.805 Uh, well, this will explain it. 00:17:36.805 --> 00:17:37.625 Okay. All right. 00:17:37.625 --> 00:17:41.625 Zip code 53403. Let me double check one more time. 00:17:41.625 --> 00:17:42.875 Yep, 53403. 00:17:42.875 --> 00:17:48.315 I got to check the index. Uh-huh. That is located. Is this right? I got to be sure. 00:17:49.055 --> 00:17:49.611 Oh, my God, Wes. 00:17:50.499 --> 00:17:52.125 Racine, Wisconsin. 00:17:52.125 --> 00:17:56.245 Hey, hello, Wisconsin. Thanks, Greg. 00:17:56.245 --> 00:18:00.095 I mean, on the map here, I see a Mount Pleasant nearby, so it's got to be nice. 00:18:00.855 --> 00:18:03.816 Oh. Let us know if we got it right. Good to hear from you. 00:18:04.228 --> 00:18:06.985 And thanks for helping test out the old ZapRite stuff. 00:18:06.985 --> 00:18:07.245 Yes. 00:18:07.275 --> 00:18:09.012 Just letting us know when it was not working. 00:18:09.615 --> 00:18:13.015 Dajag comes in with 4,747 sats. 00:18:14.317 --> 00:18:17.755 You guys, you blew my mind with Noster. I played around with it back when you 00:18:17.755 --> 00:18:21.434 first started talking about it, but I don't think I'd ever really understood what it actually was. 00:18:21.991 --> 00:18:25.341 I just thought it was ActivityPub with keys. But I think I was missing the point. 00:18:25.881 --> 00:18:28.365 I don't know if I'm going to use Buzz long-term, but I am setting it up now. 00:18:28.365 --> 00:18:31.165 And if nothing else, this was an eye-opener to the catalyst of connecting all 00:18:31.165 --> 00:18:33.665 the dots. Thank you. Well, thank you, Dajag. 00:18:33.665 --> 00:18:34.515 Awesome. That's amazing. 00:18:34.515 --> 00:18:37.345 I think it also kind of did a little bit of that for us in a way, too. 00:18:37.345 --> 00:18:40.793 I agree. It was like, oh, yeah, it's kind of what we were thinking. Here we go. Yeah. 00:18:41.170 --> 00:18:44.461 Daja, I would love to hear if you stick with Buzz. Let us know how it goes. 00:18:45.123 --> 00:18:48.089 Marcel Bussin, 17,000 and 14 cents. 00:18:51.532 --> 00:18:54.568 You made the torrent analogy again, and I have to push back. 00:18:55.009 --> 00:18:58.561 I see a huge difference between individuals stealing from companies for entertainment 00:18:58.561 --> 00:19:01.447 and companies stealing from individuals at scale for profit. 00:19:01.871 --> 00:19:05.471 It also especially stings because Dario is promising to replace developers with 00:19:05.471 --> 00:19:07.658 a model trained on open source developer contributions. 00:19:08.302 --> 00:19:11.797 Nobody sets up the R stack to train a model to replace VFX artists. 00:19:12.029 --> 00:19:15.611 Now, I'm not arguing that torrenting is ethical, and I don't let the way the 00:19:15.611 --> 00:19:18.833 model was trained prevent me from using it. The cat is out of the bag. 00:19:19.082 --> 00:19:21.329 The people who trained it are benefiting. Why shouldn't I? 00:19:21.991 --> 00:19:26.421 Okay, so I think we're just sort of both talking past each other. 00:19:26.421 --> 00:19:29.161 What I've talked about before is, you're right, they are not comparable. 00:19:29.161 --> 00:19:31.431 The tech companies stealing is worse. 00:19:31.431 --> 00:19:35.361 However, the moral alignment remains the same. If you've stolen content yourself, 00:19:35.361 --> 00:19:37.501 you really don't have the moral authority to condemn another. 00:19:37.501 --> 00:19:41.551 But additionally, torrenting the TV shows and the movies does undercut the ability 00:19:41.551 --> 00:19:44.524 for the industry to produce future movies and TV shows. 00:19:44.803 --> 00:19:48.240 So there is a similar impact at the end of the day. So I still think it stands, 00:19:48.692 --> 00:19:52.101 that if you have a raw stack or you've torrented TV shows before, 00:19:52.101 --> 00:19:56.561 you don't really, really have a lot of moral authority to stand on and be concerned 00:19:56.561 --> 00:19:58.932 that Anthropic is scanning books or something like that. 00:19:59.879 --> 00:20:02.978 You cannot like it and you can think what they're doing is worse and I would agree with you. 00:20:04.081 --> 00:20:07.837 But at the same time, you know, it's a nuanced issue. So, Everett to each their own. 00:20:08.075 --> 00:20:12.411 I would also, I think, extend the frame to be like, that's one particular sort 00:20:12.411 --> 00:20:15.233 of test case, which can be a useful model to have. 00:20:15.540 --> 00:20:19.571 But the larger issue is sort of like around what do we think about information 00:20:19.571 --> 00:20:22.981 and the commons and copyright protections and that kind of thing. 00:20:22.981 --> 00:20:24.241 Yes, yes, yes. 00:20:25.244 --> 00:20:28.001 Probably that's where to fight to have a consistent framework that we kind of 00:20:28.001 --> 00:20:32.152 agree on because the current rules we have, I don't think really anyone thinks are optimal. 00:20:33.348 --> 00:20:36.881 Yeah like i'd like to see a revolt that steals the rights of star trek away 00:20:36.881 --> 00:20:43.361 from paramount let's let's turn it to the people that's right that's right. 00:20:45.713 --> 00:20:48.522 Well gene bean boosts in three rows of ducks, 00:20:51.153 --> 00:20:54.998 Here's a quick note for others in the community with kids in Scouts. 00:20:55.378 --> 00:21:00.258 I just got back from Cub Scout Overnight Camp at Cherokee Scout Reservations 00:21:00.258 --> 00:21:03.140 in Yanceyville, North Carolina. 00:21:03.755 --> 00:21:06.848 It was really good and well worth the seven plus hour drive. 00:21:06.848 --> 00:21:10.402 I'd highly recommend others check it out. CSR.camp. 00:21:11.337 --> 00:21:12.828 That is a recommendation indeed. 00:21:12.828 --> 00:21:15.249 Yeah, listen to podcasts while you do that seven hour drive. It's good for the kids. 00:21:16.283 --> 00:21:21.802 About Linux Unplugged 677. In addition to the BBS you talked about in this episode, 00:21:22.162 --> 00:21:24.798 check out TC Squared BBS. 00:21:26.978 --> 00:21:29.314 It has some code here. It links to it. 00:21:30.248 --> 00:21:34.328 Yeah, we got a repo, GPL3, a BBS server for MeshTastic for posting bulletins, 00:21:34.328 --> 00:21:36.668 sending mail to users, and a channel directory. 00:21:36.668 --> 00:21:39.038 Could somebody give us a gift of setting this up so we could play with it? 00:21:40.587 --> 00:21:41.738 Careful what you wish for there. 00:21:41.738 --> 00:21:45.168 Chris. No, I mean, we work on a lot of the shows. We never really ask for that. 00:21:45.168 --> 00:21:47.748 But it would be really great if somebody wanted to set this up and then just 00:21:47.748 --> 00:21:50.918 kind of show it to us and treat us. That'd be fun. 00:21:51.838 --> 00:21:52.598 You can have a clanker. 00:21:52.598 --> 00:21:52.828 Do it. 00:21:52.828 --> 00:21:53.962 That's fine. 00:21:54.078 --> 00:21:56.798 Well, our dear Gene has a last question here for us. 00:21:57.520 --> 00:22:00.938 Do you all have any suggestions for making the information in many years of 00:22:00.938 --> 00:22:03.064 Slack conversations available to an agent? 00:22:06.018 --> 00:22:10.938 Oh, man. It's such adding agents to Slack is why buzz is a thing. 00:22:10.938 --> 00:22:12.944 Yeah, really, really. 00:22:14.000 --> 00:22:15.748 Because that's what you got to do. You got to add it to Slack. 00:22:15.748 --> 00:22:19.705 You got to do all the API crap, and then you can add it to every single freaking room. 00:22:20.292 --> 00:22:23.098 Maybe if you pay for Slack, they let you export in a format you can ingest. 00:22:23.098 --> 00:22:23.858 That's what I was going to say. 00:22:23.858 --> 00:22:24.078 I would know. 00:22:24.078 --> 00:22:25.138 That would be your other action. 00:22:27.298 --> 00:22:30.318 Escape it now, and then you'd search on the future things. 00:22:31.358 --> 00:22:34.278 Gene, if you could tell us, let us know. 00:22:34.378 --> 00:22:35.698 If you find out, we're hearing. 00:22:35.698 --> 00:22:40.679 Yeah, please do. Thank you, Gene. Magnolia Mayhem comes in with 2,000 sats. 00:22:43.308 --> 00:22:47.507 Forgot to boost. So he's coming in hot with a boost. Thank you very much, 00:22:47.507 --> 00:22:48.613 Mayhem. Nice to hear from you. 00:22:48.863 --> 00:22:50.287 Time for our member boost. 00:22:50.287 --> 00:22:51.317 Let's do it, boys. 00:22:51.317 --> 00:22:54.467 We got some anonymous member boosters coming in. 00:22:54.467 --> 00:22:55.266 That's always interesting. 00:22:55.730 --> 00:22:57.060 I thought this was from anonymous. 00:22:58.534 --> 00:23:00.037 Maybe we just have a member that goes by anonymous. 00:23:00.037 --> 00:23:00.477 That could be. 00:23:00.477 --> 00:23:00.807 Yeah. 00:23:00.807 --> 00:23:05.777 We can't really tell. Great coverage as always. That's one. And then a second anonymous boost. 00:23:05.777 --> 00:23:06.097 Yes. 00:23:06.457 --> 00:23:12.727 In the same vein as your OBD2 AI-assisted diagnostics, I've connected my oscilloscope 00:23:12.727 --> 00:23:17.597 to my agent via its ethernet interface and standard control protocol SCPI, 00:23:19.337 --> 00:23:23.597 now I can have my agent watch waveforms and decode serial connections you guys 00:23:23.597 --> 00:23:30.600 got my wheels turning thank you and then we got a scope ID an SDS 1104X0-E, 00:23:32.497 --> 00:23:35.257 I would love to have an oscilloscope this is great, 00:23:37.557 --> 00:23:41.117 maybe we help with the wheel turning if so, thank you So now you're getting 00:23:41.117 --> 00:23:42.757 our wheels turning. That's how this works. 00:23:42.757 --> 00:23:46.037 I'll tell you what I would like to do. And this is, I'd have to have money to 00:23:46.037 --> 00:23:52.130 burn and time to burn. But maybe in a few years, I want to do a totally agent-managed fish tank. 00:23:54.017 --> 00:23:54.887 And then we live stream it, right? 00:23:54.887 --> 00:23:58.227 Managing the levels of pH, everything in there. The temperatures, 00:23:58.227 --> 00:24:03.200 the water flow, the filtration, the feed, everything. Fully managed. Automated fish tank. 00:24:03.578 --> 00:24:05.458 It books people online to come clean it? 00:24:05.755 --> 00:24:08.497 Right. I think a lot of it would probably be home assistant driven. 00:24:08.497 --> 00:24:12.537 And like all the sensors and all the data and all of the actuations would probably 00:24:12.537 --> 00:24:14.706 be home assistant driven, managed by an agent or something like that. 00:24:15.953 --> 00:24:17.067 I think that could be a thing. 00:24:17.607 --> 00:24:19.677 We have a members boost here from Anton. 00:24:21.270 --> 00:24:21.891 Hello, Anton. 00:24:22.042 --> 00:24:26.577 Sorry for the late feedback on Buzz. It was very interesting to me since I'm 00:24:26.577 --> 00:24:31.678 trying to find a way to create and use AI assistants at work and share them with my team. 00:24:32.021 --> 00:24:35.427 I sent a message a few weeks ago about using Hermes at work. 00:24:35.427 --> 00:24:39.620 Do you know if Buzz can be a full replacement for Hermes? 00:24:41.268 --> 00:24:44.485 Yeah, I mean, it's not feature complete, right? But it is essentially an agent 00:24:44.485 --> 00:24:47.005 orchestration platform, or you could connect a Hermes agent. 00:24:47.005 --> 00:24:51.055 Yeah, true. That might be the most easy way to go. I think the main thing was 00:24:51.055 --> 00:24:55.715 that we hadn't quite gone super far into getting a bunch of MCPs configured 00:24:55.715 --> 00:24:58.665 and that kind of stuff, and that'll be the thing probably if you're trying to 00:24:58.665 --> 00:25:00.275 do it at an organization that'll really matter. 00:25:00.275 --> 00:25:04.435 I do think, Anton, though, that is the scenario for it, because people, 00:25:04.435 --> 00:25:05.475 especially that are new to agents, 00:25:07.595 --> 00:25:10.505 why not start with something like Buzz, And then if you need something more 00:25:10.505 --> 00:25:12.290 advanced from a Hermes system, you just bring it in later. 00:25:12.447 --> 00:25:15.645 Yeah, because really it's like where it's lacking is sort of on the harness 00:25:15.645 --> 00:25:20.715 side. But what it has from the start is the identity layer from Noster and being 00:25:20.715 --> 00:25:22.605 built with agents and humans co in mind. 00:25:22.605 --> 00:25:24.195 And the group chat stuff. Right. Yeah. 00:25:25.721 --> 00:25:29.620 My turn. Jimmy comes in with a free member boost. Can we ask the video game 00:25:29.620 --> 00:25:32.110 correspondent why GOG doesn't get more love? 00:25:32.630 --> 00:25:33.410 We sure can. 00:25:34.290 --> 00:25:37.720 I think that'd be you, PJ. DRM free means you own it forever, 00:25:37.720 --> 00:25:39.484 and they've got a preservation program. 00:25:39.641 --> 00:25:43.190 I like Steam, but there's some real overhead there. Just yesterday, 00:25:43.190 --> 00:25:47.400 I wanted to add a game to my wish list, but couldn't be done without 486 megabyte 00:25:47.400 --> 00:25:48.870 download. Really, just to your wish list? 00:25:48.870 --> 00:25:49.649 That seems small. 00:25:50.311 --> 00:25:54.066 PJ, why don't you think GOG gets more love in the Linux community? 00:25:55.134 --> 00:25:56.946 is it just steam sucks all the oxygen out of the room. 00:25:57.218 --> 00:26:01.520 I would say because of convenience and because of all the hard work that valve 00:26:01.520 --> 00:26:07.890 is doing to bring gaming to linux in such massive force with hardware software etc, 00:26:08.637 --> 00:26:12.653 gog has been around forever i love drm free games i've got a bunch of them but 00:26:12.809 --> 00:26:15.921 the convenience of steam on all of our systems can't beat it. 00:26:16.211 --> 00:26:21.169 Yeah yeah yeah i think i think there's a big part of it and then there's branding 00:26:21.569 --> 00:26:25.040 and then also it's there's got to be a factor of people coming from windows 00:26:25.040 --> 00:26:29.560 true very steam focused not that gog doesn't run great on windows but yeah maybe 00:26:29.560 --> 00:26:31.025 we should give it more love jimmy thank you for that. 00:26:31.229 --> 00:26:35.204 It's not talked a ton about either but valve has given uh, 00:26:35.930 --> 00:26:40.350 a lot of information to people or how do i put this they've come out and said 00:26:40.350 --> 00:26:43.030 you know we understand we're a software platform 00:26:43.466 --> 00:26:47.530 but we're going to ensure these games work even after we're gone um i actually 00:26:47.530 --> 00:26:50.740 have faith that they're going to do that so if Valve ever shuts down Steam for 00:26:50.740 --> 00:26:54.060 whatever reason, I do believe they're going to make your games still accessible 00:26:54.060 --> 00:26:56.771 and playable somehow, someway. They've come out and said this stuff before. 00:26:58.797 --> 00:27:01.270 All right. Thank you, Game Correspondent PJ. You want to take a... 00:27:01.810 --> 00:27:05.790 Digital Jote boost in with what I'm going to say is a controversial boost. 00:27:05.790 --> 00:27:06.715 Oh, here we go. Hot boost. 00:27:07.742 --> 00:27:10.330 I don't understand the issue with Brent's tabs. 00:27:10.330 --> 00:27:10.783 What's that? 00:27:11.750 --> 00:27:13.076 Brent's tabs. 00:27:18.225 --> 00:27:19.672 I think the song explains the problem. 00:27:20.448 --> 00:27:20.802 Yeah. 00:27:20.802 --> 00:27:25.672 Well, Digital here says every time I start Firefox, I open my previous session. 00:27:26.212 --> 00:27:28.792 It's currently 712 tabs over 18 windows. 00:27:30.090 --> 00:27:32.859 I'll occasionally trim it down, but this is pretty normal. 00:27:33.091 --> 00:27:34.711 My goodness. 00:27:34.966 --> 00:27:37.792 Is that more or less than you, Brent? Do we have a new king? 00:27:37.792 --> 00:27:40.092 And, like, what is the oldest tab there? A year old? 00:27:40.719 --> 00:27:42.275 That's a fascinating question. 00:27:42.774 --> 00:27:45.132 At what point is it, like, stuff like when you move and you just leave it in 00:27:45.132 --> 00:27:48.692 a box? and you never open it. And then you come back to that box five years 00:27:48.692 --> 00:27:49.955 later and you're like, oh, I can probably just get rid of this. 00:27:51.452 --> 00:27:52.072 But it's a whole window. 00:27:52.952 --> 00:27:57.342 712 tabs over 18 windows. Does that sound on par, Brent, or kind of a little 00:27:57.342 --> 00:27:58.422 bit beyond what you're doing? 00:27:58.422 --> 00:28:02.801 I would say it depends what you're measuring. 18 windows, not unusual in any way. 00:28:04.172 --> 00:28:06.792 712 tabs has only happened maybe a couple times. 00:28:08.396 --> 00:28:09.642 Is that because low or high? 00:28:09.642 --> 00:28:10.872 Wild. Oh, very high. 00:28:12.941 --> 00:28:15.832 I feel like we need to stage an intervention. To me, it's just absurd. 00:28:16.452 --> 00:28:20.652 So maybe it's, is it the windows the real problem here? We've been so focused 00:28:20.652 --> 00:28:22.272 on the tab thing that's the windows. 00:28:22.612 --> 00:28:26.662 No, it's like when you discover that a loved one is a massive hoarder and you 00:28:26.662 --> 00:28:29.022 go in there and you're like, oh, this room's pretty bad, but it's probably just 00:28:29.022 --> 00:28:31.772 this one room. And then you go in the next room's like that and the next room's 00:28:31.772 --> 00:28:34.048 like that. That's like this is, but it's a digital version. 00:28:35.793 --> 00:28:39.113 I think I can answer the question, at least. We haven't quite answered the question yet. 00:28:39.333 --> 00:28:39.803 Oh, okay. 00:28:39.803 --> 00:28:40.693 Was there a question? 00:28:40.693 --> 00:28:41.653 Yeah, I didn't know there was a question. 00:28:41.653 --> 00:28:46.083 Oh, wait. No, there's just a bunch of statements saying I'm doing it wrong, but yes. 00:28:46.083 --> 00:28:49.563 No, I think they agree with you. No, I think they're on your page. 00:28:49.563 --> 00:28:53.853 Oh, oh, oh. I thought they meant what's Brent's issue with the tabs, but they're... 00:28:54.253 --> 00:28:55.553 No, they're normalizing your behavior. 00:28:55.553 --> 00:28:56.353 Oh, Jode, I like you. 00:28:57.193 --> 00:28:58.323 This is why we have a problem. 00:28:58.323 --> 00:29:00.652 This is disturbing. No, no, no. You guys are doing it wrong. 00:29:01.494 --> 00:29:04.993 mostly my issue is window management and slow. 00:29:05.433 --> 00:29:09.983 Boot up times i'll take uh greg the lawyer uh free member boost because greg 00:29:09.983 --> 00:29:13.713 was also our baller boost tesla model y update i'm still rocking the factory 00:29:13.713 --> 00:29:16.033 lts software release oh yeah right, 00:29:16.643 --> 00:29:19.683 there's when you get the car there's like a delay they don't want to like change 00:29:19.683 --> 00:29:23.573 anything i see yeah i'm already blown away by fsd and i'm anxiously awaiting 00:29:23.573 --> 00:29:25.461 my first official rolling release update 00:29:25.850 --> 00:29:29.843 and other nudes and other nudes i have always bounced off terminal multiplexers 00:29:29.843 --> 00:29:34.696 but i'm really enjoying herder h-e-r-d-r and it's agent awareness i'll have to look that up. 00:29:35.283 --> 00:29:38.943 Yeah that's what i've been looking at as well it's kind of nice the runtime 00:29:38.943 --> 00:29:43.439 your coding agents live on apache 2.0 license written mostly in rust. 00:29:44.135 --> 00:29:45.471 She's i like the ui, 00:29:47.109 --> 00:29:50.975 Yeah, love FSD. It's going to be a shocker once people try it out. 00:29:52.653 --> 00:29:55.103 It's the number one feature of the car. Thanks, Greg. Congratulations. 00:29:55.103 --> 00:29:56.931 Thanks for the report and for the pick. 00:29:57.563 --> 00:30:03.363 SensorSmile has a member's boost here. I couldn't wait, so I just spent several 00:30:03.363 --> 00:30:05.944 hours during vacation last week learning Hermes. 00:30:07.353 --> 00:30:12.123 Ended up pushing me to tune a Llama CPP quite a bit, as well as spinning up 00:30:12.123 --> 00:30:16.623 a second Llama 3B for compressing context window. So I've been working on a 00:30:16.623 --> 00:30:19.162 side project I never thought I would get to. 00:30:19.319 --> 00:30:21.566 Thank you for convincing me to do this. 00:30:22.193 --> 00:30:24.753 Dude, you're doing it great, too. I think that's a pretty good strat, 00:30:24.753 --> 00:30:28.493 having a separate agent just monitoring your context and doing compression for 00:30:28.493 --> 00:30:30.047 you and probably being really smart about it. 00:30:30.714 --> 00:30:33.993 Paul comes in about copyright. For books, audiobooks, and music from mostly 00:30:33.993 --> 00:30:36.032 small local indie brands, I handle it this way. 00:30:36.426 --> 00:30:39.468 Can I buy it in a way I fully own it, physical media, DRM-free? 00:30:39.869 --> 00:30:42.051 Then I pay and vote with my wallet. Otherwise, I don't. 00:30:42.533 --> 00:30:45.558 With games, I prefer DRM-free, but often buy on Steam. as well. 00:30:46.318 --> 00:30:51.183 Yeah, it does get tricky when living in a small space to have that kind of stuff, 00:30:51.183 --> 00:30:54.538 but I have quite a bit of books just sort of scattered around the RV, 00:30:54.892 --> 00:30:58.073 and then I may still end up grabbing the audio version, too, or something. 00:30:59.066 --> 00:31:02.619 But I've been an Audible customer since forever. 00:31:04.207 --> 00:31:05.667 I probably put one of their kids through college by now. 00:31:06.207 --> 00:31:08.197 I kind of wish that, you know, in the RV you just had a big, 00:31:08.197 --> 00:31:10.147 dedicated rack of cassettes. Took 00:31:10.147 --> 00:31:13.047 up a huge amount of space in the limited area, but you insisted on it. 00:31:13.047 --> 00:31:13.347 Yeah. 00:31:13.347 --> 00:31:14.347 Dragging it around the country. 00:31:14.727 --> 00:31:17.385 Sorry, kids. No road trips anymore. We got to keep dad's tapes. 00:31:18.030 --> 00:31:22.217 Hey, what did we find? We found a really nice physical media and all my stuff 00:31:22.217 --> 00:31:22.957 when we were moving me out. 00:31:23.007 --> 00:31:25.037 Oh, yeah. You did have a good collection. Yeah, you did. 00:31:25.037 --> 00:31:29.007 What was that? It was a seven, like a video disc? No, that big, huge. 00:31:29.407 --> 00:31:30.507 Oh, yeah. Yeah. 00:31:32.896 --> 00:31:33.587 The laser disc. 00:31:34.527 --> 00:31:35.057 Jackets. 00:31:35.057 --> 00:31:36.087 Bags, and laser discs. 00:31:36.087 --> 00:31:41.354 That's what Brent collects If anyone wants to pay me a lot of money for a video disc Please reach out. 00:31:41.546 --> 00:31:42.827 You want to take our last one there Wes? 00:31:42.827 --> 00:31:47.297 So hey M.G Remember Bootsin If other professions like doctors, 00:31:47.297 --> 00:31:50.577 electricians, or civil engineers screw up They face scrutiny, 00:31:50.577 --> 00:31:52.117 sanction, and possibly a ban 00:31:52.117 --> 00:31:56.347 from their profession But if the computer people pull a crowd strike U.S. 00:31:56.347 --> 00:32:01.241 East 1 or Cold Guard They say oops And it's largely forgotten Is licensure overdue? 00:32:01.601 --> 00:32:03.847 The duct tape is coming apart Mmm. 00:32:04.627 --> 00:32:09.187 Hot take, hot take. I don't know. It's tough to say, right? Because you never 00:32:09.187 --> 00:32:12.677 really know, especially in free software, how someone's going to use it and 00:32:12.677 --> 00:32:16.077 what conditions it might be under and then what edge cases might get exposed. 00:32:16.077 --> 00:32:18.174 Like, it's tricky pretty, pretty quick. 00:32:18.911 --> 00:32:21.547 But I've always wondered if one day we won't be at some like, 00:32:21.918 --> 00:32:24.767 this has been, this software was written by a certified human, 00:32:24.767 --> 00:32:25.927 you know, something like that. 00:32:26.587 --> 00:32:29.767 And I mean, I suppose you've seen more with things that do get like security 00:32:29.767 --> 00:32:34.267 audits or other, you know, I wonder how much sort of curation or... 00:32:35.798 --> 00:32:39.676 post hoc verification will become, you know, a necessary prerequisite. 00:32:39.676 --> 00:32:42.456 Right, right. There'll probably be entire specialties around it. 00:32:43.217 --> 00:32:46.316 All right, that's all the boosts above the 2,000-sat cutoff and our member boosts. 00:32:46.346 --> 00:32:50.226 Thank you, everybody. Also, you sat streamers out there, 16 of you stream sats, 00:32:50.226 --> 00:32:54.281 and collectively stacked 28,069 satoshis. 00:32:54.809 --> 00:32:58.396 Thank you very much. When you combine that with our fiat boosts and our regular 00:32:58.396 --> 00:33:02.286 boosts, I think it was all regular sats actually this week, we stacked a grand 00:33:02.286 --> 00:33:06.540 total of 454,606 Satoshis. 00:33:06.974 --> 00:33:10.176 Thank you, everybody. This show really does live and die on our memberships 00:33:10.176 --> 00:33:12.926 and our value for value. If you hear dynamic ads, that means we're scraping 00:33:12.926 --> 00:33:14.521 by and we need your support. 00:33:14.969 --> 00:33:17.996 And then we have quite the hole to dig ourselves out of. In the meantime, 00:33:17.996 --> 00:33:21.685 you can boost at boost.jupiterbroadcasting.com. We always love your participation 00:33:22.026 --> 00:33:25.496 because this is, for us, the most fun segment of the show. And we really have 00:33:25.496 --> 00:33:26.537 no idea what you're going to bring up. 00:33:26.973 --> 00:33:29.576 And, of course, it's a great way to get a message in, too, while sending a little 00:33:29.576 --> 00:33:32.221 value our way. boost.jupiterbroadcasting.com. 00:33:45.200 --> 00:33:48.504 Well, you boys helped me move out of my place recently, and I've been jumping 00:33:48.504 --> 00:33:52.094 around all over the place and thinking, how many computers do I own? 00:33:52.094 --> 00:33:55.549 So some decommissioning has happened on my side, or at least thinking about it. 00:33:56.646 --> 00:34:02.374 But the studio has far more systems than I even can count over there. 00:34:02.374 --> 00:34:06.125 And so we've been thinking about changing things up a little bit. 00:34:06.525 --> 00:34:11.604 It has become time to decommission an old box. A beloved box. 00:34:12.406 --> 00:34:14.964 A box that's still technically working just fine. 00:34:14.964 --> 00:34:19.474 It's one of those things, right? You're kind of like, well, you're not actively 00:34:19.474 --> 00:34:22.594 making yourself a problem. You're not the thing that's preventing the show. 00:34:22.594 --> 00:34:25.548 You're not constantly getting in our way. And yet. 00:34:25.891 --> 00:34:26.314 And yet. 00:34:26.314 --> 00:34:27.284 We find ourselves here. 00:34:27.986 --> 00:34:32.244 Yeah, it's the problem is it just is an old Linux box with sort of forgotten 00:34:32.244 --> 00:34:34.584 services that's been running for years. 00:34:35.004 --> 00:34:38.594 I think it's, you know, it's a four and a half year old box install, 00:34:38.594 --> 00:34:41.504 but the hardware itself is extremely old. 00:34:41.504 --> 00:34:50.225 It's a Dell T5400 with quite the energy budget. It has a Xeon processor in it, 00:34:50.486 --> 00:34:55.094 and it also has eight 4-gigabyte modules, so 32 gigs of ECC RAM. 00:34:55.094 --> 00:34:58.324 How many secret Xeons you got running around in this studio? 00:34:58.324 --> 00:34:59.824 That's right, baby. I love ECC. 00:34:59.824 --> 00:35:01.424 I knew about this box, but I didn't know it was a Xeon. 00:35:01.884 --> 00:35:07.794 Yeah, an E5430, so that gives you an idea of the age, at 2.66 gigahertz. 00:35:07.794 --> 00:35:15.360 Now, if you didn't have it fully loaded up, it would approximately use 1,120 kilowatt hours a year. 00:35:17.031 --> 00:35:20.294 But it is loaded up, so it probably uses more than that. So it's got a pretty 00:35:20.294 --> 00:35:22.535 serious steady power drain. 00:35:23.162 --> 00:35:29.084 The hardware is old. It produces quite a bit of heat. The BIOS is dated August 21st, 2008. 00:35:29.084 --> 00:35:30.884 Great vintage for BIOSes, yeah. 00:35:30.884 --> 00:35:36.094 The root file system was created January 5th, 2022. So it's about four years 00:35:36.094 --> 00:35:38.475 and seven months old. So this is the box. 00:35:38.864 --> 00:35:41.708 Something tells me it's got a real new kernel on there probably, right? 00:35:43.387 --> 00:35:49.731 Okay, so it's running Ubuntu 20.04.6, which is no longer supported, running Linux 5.4. 00:35:51.791 --> 00:35:53.650 That's so ancient in our computers. 00:35:54.282 --> 00:35:59.031 I know. This is just a bygone era. So much has changed in four years on how we manage systems. 00:35:59.031 --> 00:35:59.413 Yes. 00:36:03.231 --> 00:36:07.311 So I think the job is to figure out what's using this that we don't know about 00:36:07.311 --> 00:36:09.688 or anything weird about this system that maybe we've forgotten. 00:36:09.897 --> 00:36:10.711 Because it's probably a lot. 00:36:11.171 --> 00:36:15.491 Yeah. and then see if we can safely decommission it. Now, the role that this 00:36:15.491 --> 00:36:18.494 machine plays, and Wes, I don't know, can you SSH into it? 00:36:18.738 --> 00:36:20.904 Are you able to SSH? You'd have to be on my tail net. 00:36:21.269 --> 00:36:22.901 Yeah, let's take a peek here. 00:36:22.901 --> 00:36:24.191 Otherwise, I can SSH in. 00:36:24.191 --> 00:36:27.021 I have quite a fond connection to this box, I will say. 00:36:27.021 --> 00:36:28.451 Uh-huh. I was wondering if you remember. 00:36:28.451 --> 00:36:32.521 Uh-huh. I didn't know it existed until this very moment, and somehow it just 00:36:32.521 --> 00:36:37.251 showed up ready for the job. But this was, what, five years ago, 00:36:37.251 --> 00:36:40.471 something like that, it feels like. Chris and I sat down. 00:36:40.471 --> 00:36:41.211 Four years, seven months. 00:36:41.211 --> 00:36:48.101 Four to seven months ago. Chris and I sat down one winter and came up with some crazy ideas. 00:36:48.101 --> 00:36:53.191 And the boosts came out of this very moment where we just loaded a box. 00:36:53.191 --> 00:36:56.991 This was a temporary box. We were just doing a little bit of testing and see how things would go. 00:36:56.991 --> 00:37:03.163 And here we are many years later. And this box has been critical for the show 00:37:03.511 --> 00:37:09.311 in many ways. I think the, don't the boosts i don't know somehow this the boost 00:37:09.311 --> 00:37:11.181 read off this thing it's been. 00:37:11.181 --> 00:37:13.591 Important that's one of the things we got to look into is if this is in the 00:37:13.591 --> 00:37:18.881 boost scraper pipeline we got to look that up we got to figure that out because 00:37:18.881 --> 00:37:21.331 it may be powering some of the back end infrastructure stuff there. 00:37:22.011 --> 00:37:26.031 So for me it was like a new era when this box got turned on. 00:37:27.230 --> 00:37:28.896 Oh we learned so much that yeah. 00:37:29.302 --> 00:37:29.941 Yeah we did. 00:37:29.941 --> 00:37:33.540 You're right though i forgot this was temporary this was going to be a temporary Well. 00:37:34.196 --> 00:37:35.431 What is temporary, you know? 00:37:35.451 --> 00:37:41.458 All right. So that's the system. It's time to shut her down. 00:37:43.808 --> 00:37:49.852 I'm expecting, when we log in, we're going to see a handful of containers. I think... 00:37:50.712 --> 00:37:50.912 Oh. 00:37:51.695 --> 00:37:52.275 Oh, yeah? 00:37:52.827 --> 00:37:55.729 I recall. Oh, there's memories around this thing. 00:37:56.332 --> 00:37:59.706 We're going to see plenty of free space. I don't think that's going to be an issue. 00:38:01.132 --> 00:38:04.642 But I bet, you know... In fact, I bet it even has enough RAM. 00:38:04.642 --> 00:38:08.472 The problem with this thing is that the disks are slow, slow disks. 00:38:08.472 --> 00:38:09.792 All right, so, Wes, what is the... 00:38:09.852 --> 00:38:14.472 It sounds like you've already found something fun. What are you spelunking into over there? 00:38:14.472 --> 00:38:16.812 Would you like to guess how many containers we are running? 00:38:16.812 --> 00:38:18.340 Well, okay, I could, yeah, I could. 00:38:19.007 --> 00:38:22.062 You take a guess, and then I'll, you know, stay and listen for a while. 00:38:22.062 --> 00:38:24.372 So you got, let's see. 00:38:24.372 --> 00:38:24.743 Or, 00:38:29.392 --> 00:38:30.532 okay, let's hand one done. 00:38:30.892 --> 00:38:36.112 Okay, so I'm going to say, this thing should be able to do everything in seven or eight containers. 00:38:36.112 --> 00:38:36.272 No. 00:38:36.272 --> 00:38:38.454 Everything you need should be done in, okay, what do you think, Brent? 00:38:38.680 --> 00:38:44.590 Well, I have memories around you troubleshooting containers specifically on this box. 00:38:44.892 --> 00:38:48.872 And it was, I've never seen you more angry at a computer. 00:38:49.772 --> 00:38:53.912 Well, because the issue here is it's like this, they bring this node management 00:38:53.912 --> 00:38:56.892 software called Umbral brings their own like Docker orchestration layer. 00:38:56.892 --> 00:38:58.004 Seems like a great idea. 00:38:58.683 --> 00:39:02.068 Their bash scripts. And then they have a monitoring script called Karen. 00:39:02.335 --> 00:39:05.332 And I don't know if they call it this anymore, but it's still on my system called Karen. 00:39:05.772 --> 00:39:09.092 And then Karen starts screaming about issues because she's like a system monitor. 00:39:09.347 --> 00:39:12.322 And so you have their Docker manager scripts, their start and stop scripts, 00:39:12.322 --> 00:39:14.912 and their Karen scripts. And that's how they managed everything. 00:39:14.912 --> 00:39:16.464 And you had to use that to interact with it. 00:39:17.654 --> 00:39:20.862 And that's how they did like boot dependency resolution and all kinds of stuff. 00:39:20.862 --> 00:39:23.262 So what do you think? What do you think the number is, Brent? Give us a number. 00:39:23.639 --> 00:39:30.959 Well, I recall it being surprisingly multiplicity. So I'm going to say... 00:39:32.451 --> 00:39:37.838 18. All right. All right. It should be doable in seven containers. 00:39:38.941 --> 00:39:41.948 He says 18. What do we got, West Payne? What is our counter? 00:39:42.816 --> 00:39:43.296 59. 00:39:46.716 --> 00:39:52.596 What is it doing? That's 50 more containers than it needs. What is it doing? What is happening? 00:39:53.417 --> 00:39:55.636 Can you give me an overview of what some of that is? 00:39:56.136 --> 00:39:56.639 Wow. 00:39:57.856 --> 00:40:00.996 So a lot of it is like sidecar tour. 00:40:00.996 --> 00:40:04.876 Tour for everything. Everything has its own Tor sidecar. Oh, my. 00:40:04.876 --> 00:40:10.116 So there's AppProxy. There's L&D, of course. A bunch more Tor. Lightning Terminal. 00:40:11.256 --> 00:40:12.816 Tor is just not the way to self-host stuff. 00:40:12.876 --> 00:40:16.056 Electrum Wallet. Oh, my God. Elements Web. 00:40:16.056 --> 00:40:16.976 Sure, got to have that. 00:40:16.976 --> 00:40:19.026 Something we'll just call, oh, Mempool's front end. 00:40:19.026 --> 00:40:19.746 Yeah, got to have Mempool. 00:40:19.746 --> 00:40:22.216 You got to have a Mempool widget server. 00:40:22.216 --> 00:40:23.696 Uh-huh. You got to have a widget server. 00:40:24.096 --> 00:40:26.366 Restarting 54 seconds ago. 00:40:26.366 --> 00:40:27.156 Oh, yeah, that one's not good. 00:40:27.156 --> 00:40:30.676 Mempool backend. Yeah, got to be. I2PD. 00:40:30.676 --> 00:40:32.536 All right, all right. 00:40:32.536 --> 00:40:33.176 I get it. I get it. 00:40:33.176 --> 00:40:35.856 It's a lot of stuff. God. Just the Tor containers alone are going to have that. 00:40:35.876 --> 00:40:38.470 Something from CryptoSharks131. 00:40:38.667 --> 00:40:38.836 What? 00:40:41.176 --> 00:40:43.896 That wouldn't surprise me at all. Oh, wow. Okay. 00:40:44.266 --> 00:40:45.776 You were right, though, in terms of, 00:40:47.996 --> 00:40:53.336 usage of things on here. And Prox shows for free dash H here. 00:40:53.336 --> 00:40:58.507 We got 20 gigs available, 31 total, 10 use. So we're sitting pretty nice there. 00:40:59.192 --> 00:41:07.306 and uh on disk we got 450 uh 460 gigs on the root drive okay but only 34 use 00:41:07.306 --> 00:41:10.808 so there's that's only at eight percent use of tons of space on root and then, 00:41:11.273 --> 00:41:16.857 on slash serve where all the app data lives that's a 7.3 t setup, 00:41:17.333 --> 00:41:21.016 uh and only 1.1 t's used so that's a 15 percent fall so there's tons of. 00:41:21.616 --> 00:41:23.097 Wait a minute wait a minute wait a minute. 00:41:24.073 --> 00:41:25.021 You've been looking for disk. 00:41:25.021 --> 00:41:25.292 Yeah. 00:41:27.794 --> 00:41:31.601 I want to turn this thing off because it's loud and hot and uses a lot of power, 00:41:31.601 --> 00:41:34.754 but I don't also just want to throw away 7 terabytes almost of disk. 00:41:35.462 --> 00:41:39.221 It's ButterFS, too, if I recall. So, you know, there's that. 00:41:39.221 --> 00:41:41.291 There's another one of our mini ButterFS. 00:41:41.291 --> 00:41:42.041 Yes, that's right. 00:41:44.081 --> 00:41:46.014 SDB1 is a ButterFS array. 00:41:46.228 --> 00:41:48.971 So cancel the segment. We're going to keep it on. Is that what we're doing? 00:41:48.971 --> 00:41:50.779 Wait a minute. Hold on. It's only one disk? 00:41:51.783 --> 00:41:55.201 It looks like. I just see an SDB, SDB1, yeah. 00:41:56.881 --> 00:41:59.428 Yeah, we found this disk in one of your drawers in the studio. 00:41:59.835 --> 00:42:02.541 Yeah, that's why this is only going to be, one of the reasons it's only going to be temporary. 00:42:02.541 --> 00:42:03.251 Right, we meant to... 00:42:03.481 --> 00:42:06.720 So we did a single disk setup for something that's kind of central to the... 00:42:07.219 --> 00:42:07.731 Sorry, guys. 00:42:07.731 --> 00:42:11.515 And then forgot about that. That honestly is a little bit of a surprise to me. 00:42:14.141 --> 00:42:16.561 I don't normally, for these kinds of systems, just do a single disk setup. 00:42:16.561 --> 00:42:18.266 I'm pretty sure we had a to-do list somewhere. 00:42:20.542 --> 00:42:21.111 Probably. 00:42:21.256 --> 00:42:21.680 Yeah. 00:42:21.796 --> 00:42:24.088 Probably. I mean, it feels like, you know, looking at this box, 00:42:24.088 --> 00:42:28.867 it's like ancient Linux archaeology here. 00:42:29.488 --> 00:42:31.848 I mean, look at this. 180 pending security updates. 00:42:32.708 --> 00:42:35.278 Seven pending security updates that are covered by ESM apps. 00:42:35.278 --> 00:42:39.588 And by the way, these are just what's in the extended support. 00:42:40.157 --> 00:42:42.678 So not even really everything that's in the repo. These are just what they're 00:42:42.678 --> 00:42:46.748 willing to patch through extended support. 180 pending for infra. 00:42:47.048 --> 00:42:48.558 Seven pending from apps. and then 00:42:48.558 --> 00:42:52.932 six ordinary packages from the repo need upgraded. Docker is old as crap. 00:42:53.634 --> 00:42:55.888 I mean, like I said earlier, it's on a kernel 5.4. 00:42:56.171 --> 00:42:59.509 For some reason, there's a folder in your home dir called Cardano. 00:42:59.700 --> 00:43:02.301 Yeah, yeah, yeah. Well, I thought Cardano was an interesting product. 00:43:02.464 --> 00:43:03.567 Like, well, what's the date on that? 00:43:04.528 --> 00:43:05.128 Good question. 00:43:06.724 --> 00:43:10.548 A while ago. And I looked at that and I'm like, that alone was like, oh my God, what a mess. 00:43:10.688 --> 00:43:11.577 January 2022? 00:43:12.708 --> 00:43:15.101 Yeah, it was a real mess. It's not still running, right? 00:43:16.100 --> 00:43:19.508 I didn't see anything running. I was just taking a peek in the home. 00:43:19.808 --> 00:43:25.138 That would be funny if that was running all these years Oh my god It's a mystery box to me really. 00:43:27.710 --> 00:43:32.180 Been up for 180 days. That's not bad. 2.72 load average. 00:43:33.219 --> 00:43:34.650 Yeah, yeah. It's really just... 00:43:34.870 --> 00:43:36.040 Yeah, 2008 era Xeon. 00:43:36.040 --> 00:43:39.950 It's disk IO bound, right? It's about 12% of, like, the system pressure is just 00:43:39.950 --> 00:43:42.762 disk IO. Is really, like, what I saw when I went in there. 00:43:43.145 --> 00:43:48.830 Oh. ButterFS reports device missing. Looks like a multi-device ButterFS volume 00:43:48.830 --> 00:43:50.390 that may be missing a member disk. 00:43:51.470 --> 00:43:51.933 Nothing. 00:43:54.230 --> 00:43:57.222 Wait, did we put two disks in here and you stole one out of it? 00:43:57.889 --> 00:44:02.000 I don't know, man. I can't remember. Honestly, this is one of the things that's 00:44:02.000 --> 00:44:07.700 changed that really strikes me is today the system would be designed in such 00:44:07.700 --> 00:44:09.168 a way that it's self-documenting. 00:44:10.289 --> 00:44:13.040 And you would just go look at that and you would understand how it works. 00:44:13.040 --> 00:44:16.230 But this was thrown together while we were just doing a project. 00:44:16.230 --> 00:44:19.170 It was going to be temporary and there wasn't really any documentation. 00:44:19.170 --> 00:44:21.870 And we were trying to even just figure out how it works. Yeah, 00:44:21.870 --> 00:44:23.650 boosts, lightning, all of it. 00:44:24.604 --> 00:44:25.457 This is a real problem. 00:44:26.154 --> 00:44:28.970 I guess I have a big question here. How in the world are we going to figure 00:44:28.970 --> 00:44:31.030 out what is using this box? 00:44:34.147 --> 00:44:35.390 Do you think the boost scraper is using it? 00:44:35.750 --> 00:44:42.470 Well, it must be for doing the check to see if there's any unique boost that came in on that node. 00:44:43.034 --> 00:44:48.010 So we'll want to make sure that wherever we migrate that split to, 00:44:48.670 --> 00:44:50.600 we are also checking in the scraper. 00:44:50.600 --> 00:44:53.850 And we're going to need to collaboratively close the channels on it because 00:44:53.850 --> 00:44:56.095 we're moving to a different system. 00:44:57.130 --> 00:44:59.460 So that's something. And then I think, yeah, we'll just have to monitor the 00:44:59.460 --> 00:45:02.666 traffic and see. It's a real problem. 00:45:03.950 --> 00:45:06.690 But we already have the host to migrate to. We're moving to a service for it. 00:45:07.467 --> 00:45:09.430 And so it's really just a matter of spinning down the channels, 00:45:09.430 --> 00:45:13.310 I think, letting the fun settle, and then us kind of monitoring what uses it. 00:45:15.118 --> 00:45:19.559 Shut down some of the services, but leave the box online for a bit. Monitor it maybe. 00:45:20.945 --> 00:45:22.785 I think we'll probably plan for later this week. 00:45:23.000 --> 00:45:26.652 Yeah, we could probably do a network cut or something if we want, 00:45:26.652 --> 00:45:28.852 just to sort of take it offline and see what barks at us. 00:45:28.852 --> 00:45:29.872 Yeah, see what breaks for a little bit. 00:45:30.532 --> 00:45:32.410 Jeff did that to us one time, if you remember. 00:45:32.915 --> 00:45:34.402 I do recall, and some things broke. 00:45:34.402 --> 00:45:38.254 Yes. Yeah, he just cut the power to this box, not thinking it was important or anything. 00:45:38.364 --> 00:45:39.072 Right? A couple times. 00:45:39.432 --> 00:45:39.932 Oh, yeah, right, right. 00:45:40.112 --> 00:45:41.972 You guys also remember you blew the circuit that one time. 00:45:41.972 --> 00:45:44.312 Well, you've got to blow a circuit or two to get progress. 00:45:47.832 --> 00:45:51.008 Yeah, but it was a tough call, Because like Wes said at the start, 00:45:52.112 --> 00:45:55.652 there's other things that are also not working as well that could maybe be fixed sooner. 00:45:56.412 --> 00:45:59.712 But it just feels like now is the time to start pruning older infrastructure 00:45:59.712 --> 00:46:01.126 that you're not actively maintaining. 00:46:01.381 --> 00:46:05.776 Right. And like a lot of the value was we didn't know what we were doing. 00:46:05.938 --> 00:46:08.352 We needed something that could set up the pieces because we didn't even know 00:46:08.352 --> 00:46:10.742 what all the pieces were or which ones were necessary. 00:46:10.742 --> 00:46:11.145 Yeah. 00:46:11.534 --> 00:46:14.852 We understand a lot of that better now, right? And so like we would never set 00:46:14.852 --> 00:46:18.372 it up this way. We don't really want to operate it in this setup. 00:46:18.372 --> 00:46:18.703 Right. 00:46:18.918 --> 00:46:23.283 It actively goes against most of the things we'd prefer to have it do. 00:46:23.742 --> 00:46:26.032 So it's nice to retire it, but it is, you're right. It was like, 00:46:26.032 --> 00:46:29.088 it's sort of nostalgic too. And I'm really glad it held up. 00:46:29.721 --> 00:46:33.106 It was also very early in the like boost ecosystem. 00:46:33.355 --> 00:46:36.472 I remember for a couple of weeks there, we were changing things pretty quickly 00:46:36.792 --> 00:46:42.513 on this box just because all of the developers were evolving things and it was a really exciting time. 00:46:43.344 --> 00:46:48.452 Is this where we were doing a little, we were trying out some of the IPFS podcasting maybe too, right? 00:46:49.897 --> 00:46:52.406 It's good times. It was a lot of fun and that box was very educational, 00:46:53.096 --> 00:46:55.023 but it is time to wind her down. 00:47:05.838 --> 00:47:09.927 Well, we live in a world where more than ever, we're close to being able to, 00:47:10.387 --> 00:47:12.327 summon software out of the void. 00:47:12.327 --> 00:47:15.787 And whether you should trust that software or not is a separate discussion. 00:47:15.787 --> 00:47:21.107 But one thing I find fun about that is you can kind of, you can try out more 00:47:21.107 --> 00:47:25.317 ideas. Because in theory, you could get some help to make it happen if the idea 00:47:25.317 --> 00:47:29.667 made any sense. And I think that means thinking about new ideas is what we should be doing. 00:47:30.051 --> 00:47:34.310 And I was just musing, if you could just add one feature to the kernel, 00:47:34.583 --> 00:47:37.737 you know, That Linux kernel you're running, not that you needed other people 00:47:37.737 --> 00:47:41.227 to run, not that you're endorsing is a good idea, but something that 00:47:41.607 --> 00:47:45.821 you would love to see put into kernel space and taken out of user space. What would it be? 00:47:46.827 --> 00:47:49.612 Or if you want to take something out, that could work too. 00:47:50.320 --> 00:47:53.007 Or another way to phrase it, like if I was king of the kernel for a day, 00:47:53.007 --> 00:47:54.977 I mean, you could just fork it, right? And add your own thing too. 00:47:54.977 --> 00:47:57.170 You don't have to be king of the kernel. It's a fun idea. 00:47:57.692 --> 00:48:01.647 I'll tell you what I would do. I know right away exactly what I would do. 00:48:01.647 --> 00:48:02.157 Really? 00:48:02.157 --> 00:48:06.767 I could. Oh, yeah. Oh, it's so obvious. First of all, I'd rip out Samsung's 00:48:06.767 --> 00:48:12.917 SMB server that I've never liked, and I would use that hole to put in something 00:48:12.917 --> 00:48:15.241 way more useful. Ready for this, boys? 00:48:16.216 --> 00:48:22.869 Kernel SSH. I call it K-SSHD. Thank you very much. Thank you. Thank you. 00:48:23.847 --> 00:48:27.717 And you might think this is crazy, and we get close. There are projects like 00:48:27.717 --> 00:48:33.386 Drakkut SSHD and others that get very early, so like even before the disk is decrypted. 00:48:34.065 --> 00:48:37.949 but not at the kernel level. However, this is actually quite possible. 00:48:38.355 --> 00:48:42.738 In fact, there's a project out there called Wolf SSH, Wolf SSH, 00:48:43.202 --> 00:48:46.947 which is probably the most realistic existing implementation you could already 00:48:46.947 --> 00:48:49.239 use and port it into a Linux kernel module. 00:48:49.559 --> 00:48:54.497 It's designed to be an embeddable SSH v2 library rather than a Unix daemon. 00:48:54.497 --> 00:48:55.107 Oh. 00:48:55.727 --> 00:48:59.717 Works without file system support and is designed for embedded configurations 00:48:59.717 --> 00:49:04.025 where there's no file system or they have to use their own virtual custom IO 00:49:04.437 --> 00:49:08.303 and the cryptographic library WolfCrypt already in the Linux kernel. 00:49:09.354 --> 00:49:13.603 It's already in the Linux kernel. And so what Samsung did for KSMBD, 00:49:14.491 --> 00:49:18.083 and I think this is what I would do, is they divided SMBD into two pieces. 00:49:18.083 --> 00:49:21.483 The kernel stuff has the protocol, the crypto signing, session management, 00:49:21.483 --> 00:49:26.963 open read write handling, locking of files, VFS operations. That lives in KSMBD 00:49:27.323 --> 00:49:28.661 in your Linux kernel right now. 00:49:29.078 --> 00:49:32.723 And then in the user space, they manage the user accounts, the Samba config, 00:49:32.723 --> 00:49:37.187 your share info, RPC protocol, policy type operations is in user space. 00:49:37.721 --> 00:49:42.424 And KSMBD creates a real TCP server entirely inside the kernel. 00:49:42.952 --> 00:49:46.946 It maintains generic netlink interface between the kernel and the KSMBD mounts. 00:49:47.700 --> 00:49:51.813 And it manages the protocol between the kernel and user space, 00:49:51.813 --> 00:49:58.813 which includes things like login response and RPC requests and crypto authentication 00:49:58.813 --> 00:50:01.359 and signing. All the things you need for SSH. 00:50:01.864 --> 00:50:07.393 So you could take KSSHD, put it in this space, break it up like they broke up 00:50:07.393 --> 00:50:09.893 Samba, where the SSH framing, the key stuff, 00:50:10.334 --> 00:50:13.614 all the channels, the host keys, pubkey verifies, handled by the kernel daemon, 00:50:13.945 --> 00:50:17.523 which then drops to user space for user lookup, authorized key, PAM. 00:50:18.603 --> 00:50:25.531 PTY creation, all that policies, environment, your user stuff is in the user space. And... 00:50:26.768 --> 00:50:31.322 It would be dramatically smaller than KSMBD. I had the clanker do a little mock-up comparison. 00:50:32.251 --> 00:50:33.372 When's version one? 00:50:33.372 --> 00:50:39.358 So my idea would make the kernel leaner and probably be more useful for all of us. 00:50:40.077 --> 00:50:45.562 And the Benny would be SSH remains available when your user space is totally 00:50:45.562 --> 00:50:51.298 crapped out, and it is even theoretically possible you could SSH in and monitor the init process. 00:50:51.867 --> 00:50:54.992 So you're basically tired of forgetting to turn SSH on? You're just like, 00:50:54.992 --> 00:50:57.632 if I build it in at the kernel level, then it's always on. 00:50:58.192 --> 00:51:01.972 Well, I just got thinking, like, think about for, like, provisioning at scale 00:51:02.292 --> 00:51:07.197 or even, like, IoT devices, some sort of, like, LAN-based SSH. 00:51:08.072 --> 00:51:12.412 I just think it could be really useful. Like, the little tiny microserver you 00:51:12.412 --> 00:51:15.942 could deploy that has a little tiny secure SSH by default. 00:51:15.942 --> 00:51:19.182 Or you could get Disco to sort of get into the kernel right there and then take 00:51:19.182 --> 00:51:20.472 things over and make sure it's a Nix machine. 00:51:20.512 --> 00:51:21.042 That's what I'm saying. 00:51:21.042 --> 00:51:21.652 Every time it boots. 00:51:22.292 --> 00:51:24.212 That's obviously it. That's obviously it. 00:51:24.212 --> 00:51:28.802 You know, this would have helped me recently. When we were together, 00:51:28.802 --> 00:51:31.952 I was like, remember I was pounding that server with just backups? 00:51:31.952 --> 00:51:32.227 Yeah. 00:51:32.680 --> 00:51:37.249 And I did something, I don't even remember what, but SSH just dropped out. 00:51:37.812 --> 00:51:40.772 And I was remote and I was trying to do a bunch of backups like in the middle 00:51:40.772 --> 00:51:44.662 of the night. And I couldn't do it because like I'm not going to go to the other 00:51:44.662 --> 00:51:47.682 place where people are sleeping and like hit the on-off button or whatever. 00:51:47.682 --> 00:51:51.802 And SSH just dropped out. But everything else was fine. Like the kernel is still up and all that. 00:51:51.852 --> 00:51:53.612 IPMI? No, my. 00:51:53.612 --> 00:51:53.902 No. 00:51:53.902 --> 00:51:55.492 I got SSH built in, right? 00:51:56.092 --> 00:51:57.351 Boom! Nailed it. 00:51:58.036 --> 00:52:00.736 Okay, Wes, if you could add a feature to the kernel. 00:52:01.159 --> 00:52:05.442 Yeah, I was just thinking, okay, you know, for a long time, the kernels had 00:52:05.442 --> 00:52:09.312 the ability to, like, migrate virtual machines over the network, right? 00:52:09.632 --> 00:52:12.427 And it can, like, handle keeping the memory in sync. 00:52:13.571 --> 00:52:17.978 Why don't we have that for applications? I want the kernel to be able to just 00:52:17.978 --> 00:52:22.588 take my app from one machine I got and then just poof, make it show up on the 00:52:22.588 --> 00:52:25.018 other machine. Why do I got to be syncing everything? 00:52:25.018 --> 00:52:27.128 This feels right. This feels really right. 00:52:27.128 --> 00:52:31.738 You know, like App Teleport is part of the kernel. They form a little kernel 00:52:31.738 --> 00:52:35.228 mesh. They auto-discover AppleTalk style and put that back in. 00:52:35.228 --> 00:52:38.678 You wonder, too, could you do something like where maybe you identify an application, 00:52:38.678 --> 00:52:42.278 you migrate all of its processes to a namespace, you isolate that namespace, 00:52:42.278 --> 00:52:44.760 and then you can somehow group it up and move it. 00:52:45.201 --> 00:52:45.448 Yeah. 00:52:45.448 --> 00:52:46.718 And you start a new namespace on the system. 00:52:46.938 --> 00:52:49.508 Some of its storage is, you know, shared network mount or something already. 00:52:49.508 --> 00:52:52.968 Yeah, right. You'd have to do something with storage. But if you could transport 00:52:52.968 --> 00:52:54.791 the memory content securely. 00:52:55.273 --> 00:52:58.538 Why not? And, you know, we'll have everything on a NIC store so, 00:52:58.538 --> 00:53:00.088 like, the binaries will be available. 00:53:00.088 --> 00:53:03.470 Stop it. If it's not there, just run it. Oh, that's good. All right. 00:53:03.679 --> 00:53:06.368 I'm not sure which one I like more. I think I might like that one more. 00:53:06.368 --> 00:53:08.248 I think I would use that maybe more in my day-to-day. 00:53:08.248 --> 00:53:11.498 Well, I was going to say put, you know, like a Lisp REPL in the kernel, 00:53:11.498 --> 00:53:12.758 but I thought this might be more useful. 00:53:13.623 --> 00:53:18.098 Okay, Brent, if you could add something to the kernel, what do you think you'd add? 00:53:18.958 --> 00:53:21.298 Are we saying tab management? Is that the appropriate thing? 00:53:22.778 --> 00:53:23.858 Firefox accelerator. 00:53:26.352 --> 00:53:27.971 Like a scheduler for my tabs. 00:53:28.818 --> 00:53:29.748 Kernel space Firefox. 00:53:29.748 --> 00:53:34.018 There you go. There you go. I was thinking just like a lot of the essential 00:53:34.018 --> 00:53:36.998 tools that we seem to use on every single machine. 00:53:37.805 --> 00:53:42.598 Things like R-Sync has been around forever. I don't know. It's as close as I 00:53:42.598 --> 00:53:46.408 feel an application is feature complete. Like, let's just throw it in there. 00:53:46.408 --> 00:53:48.258 Every single person should be 00:53:48.258 --> 00:53:51.232 using it on their Linux box. I don't know if they are, but I certainly do. 00:53:51.923 --> 00:53:56.422 So I don't know. Maybe I'm just tired of installing stuff. I just want it all in one neat little box. 00:53:57.229 --> 00:53:59.411 You know, I got a big idea for you. 00:54:01.936 --> 00:54:03.196 K systemd. 00:54:03.991 --> 00:54:04.745 Whoa. 00:54:05.405 --> 00:54:05.665 Right? 00:54:06.065 --> 00:54:08.035 That's like KDBus to a whole new level. 00:54:08.035 --> 00:54:11.945 Bring it all together. One giant kernel. I mean, you know that's where it's 00:54:11.945 --> 00:54:13.303 going anyways. Let's do it. 00:54:13.906 --> 00:54:16.931 Yeah, but we're still kind of waiting for systemd to have a good text editor, right? 00:54:17.035 --> 00:54:20.123 Yeah, we do need that. You're right about that. We need systemd editd. 00:54:20.697 --> 00:54:25.025 All right, Boost in. Let us know which one of our features you would vote for 00:54:25.025 --> 00:54:28.876 if you had to back one of us and what you would add or take out of the Linux kernel yourself. 00:54:29.865 --> 00:54:31.105 Boost.JupyterBroadcasting. 00:54:31.105 --> 00:54:34.625 I mean, code submissions for a compilable module do get extra points. 00:54:34.625 --> 00:54:34.945 It's true. 00:54:35.825 --> 00:54:38.525 I like your thinking there, Wes. Boost.jubitabroadcasting.com. 00:54:38.825 --> 00:54:40.155 That way we can put it in our kernel. 00:54:42.174 --> 00:54:45.611 Well, I just want to mention, if you haven't joined our Matrix community, 00:54:45.611 --> 00:54:48.941 it's still going. And if you have become disillusioned with Discord, 00:54:48.941 --> 00:54:51.126 go to jupiterbroadcasting.com slash Matrix. 00:54:51.590 --> 00:54:55.071 We have a couple of chat rooms going all the time in there. The JB chat, 00:54:55.071 --> 00:54:56.083 kind of our general chat. 00:54:56.362 --> 00:54:59.201 We have an agent operations chat, if you're into that kind of thing. 00:54:59.201 --> 00:55:03.891 And we have also chats in there for, like, the launch, the Linux Unplugged dedicated 00:55:03.891 --> 00:55:07.397 chat. But you can get started at jupiterbroadcasting.com slash Matrix. 00:55:07.803 --> 00:55:13.001 And then just for your extended calendar planning, Texas Linux Fest is on our 00:55:13.001 --> 00:55:17.261 radar. We don't have our details locked down yet, but it's October 3rd through 00:55:17.261 --> 00:55:18.681 the 4th. Oh, this is the old website. 00:55:19.141 --> 00:55:20.271 I believe it's November now. 00:55:20.271 --> 00:55:21.182 Yeah, yeah. 00:55:21.344 --> 00:55:23.921 November 6th through the 7th, 2026. 00:55:23.921 --> 00:55:27.931 Oh, man. See, here's what happened to me is if you Google for the Texas Linux 00:55:27.931 --> 00:55:31.335 Fest, the first result is the 2025. Come on, Googs. 00:55:32.050 --> 00:55:35.701 What are you using all these AI GPUs for? Figure it out. 88 days, 00:55:35.701 --> 00:55:37.551 13 hours, 13 minutes, 40 seconds. 00:55:37.741 --> 00:55:39.221 That's getting to be sounded soon. 00:55:39.221 --> 00:55:41.851 That's why I wanted to mention it. We're planning to be there. 00:55:41.851 --> 00:55:45.471 We don't know how we're going to get there, but we may ask for help, 00:55:45.471 --> 00:55:46.161 but we'll tell you more about that. 00:55:46.161 --> 00:55:46.921 Something fuel lines. 00:55:46.921 --> 00:55:49.771 Maybe we start putting a plan together and we actually get our crap together, 00:55:50.241 --> 00:55:51.101 soon. Maybe that's what I do. 00:55:51.101 --> 00:55:52.961 We say that every time. Maybe this time. 00:55:53.481 --> 00:55:57.141 We should be starting our home lab holidays. 00:55:57.661 --> 00:55:58.941 Oh, right, right, right. 00:55:58.941 --> 00:55:59.341 Right. 00:56:01.741 --> 00:56:03.581 Speaking of stuff we are behind on already. 00:56:04.061 --> 00:56:07.361 How do we get it so bad? How do we get it so bad? You're right about that. 00:56:07.361 --> 00:56:10.391 All right. Maybe, can we just do an episode where we catch up on stuff? 00:56:10.391 --> 00:56:12.696 Would that be fun for anybody? Would that be? I don't know. 00:56:14.947 --> 00:56:18.726 But before we go any further, I want to say time-appropriate greetings to our 00:56:18.726 --> 00:56:21.169 virtual lug. Hello, Mumble Room. 00:56:22.649 --> 00:56:24.496 Hey, Chris. Hey, Russ. And hello, Brent. 00:56:24.496 --> 00:56:25.556 Hello, guys. 00:56:25.556 --> 00:56:27.876 Hello. Thanks for sticking around. 00:56:28.356 --> 00:56:33.076 Hope you've been enjoying the episode so far. We're just about out of here, as they say. 00:56:33.076 --> 00:56:33.696 Just about to get started. 00:56:33.716 --> 00:56:38.412 You know, today on the show, we're going to throw you for a loop because it 00:56:38.412 --> 00:56:41.826 turns out we're actually going to do it in reverse. We'll tell you about decommissioning 00:56:41.826 --> 00:56:45.585 a system, about the kernel features we'd like to add, and then we'll wrap it up. 00:56:45.718 --> 00:56:49.085 Well, actually, we'll start it with some boosts and some picks. So there you go. 00:56:49.579 --> 00:56:52.197 That's it. Hope you enjoyed the Reverso episode. 00:56:54.078 --> 00:56:54.734 We'll see you next week. 00:57:00.150 --> 00:57:00.968 I'm Brent. 00:57:01.491 --> 00:57:03.023 We're out of here. No, we're done.