WEBVTT 00:00:11.436 --> 00:00:15.885 Hello, friends, and welcome back to your weekly Linux talk show. My name is Chris. 00:00:15.885 --> 00:00:16.718 My name is Wes. 00:00:16.834 --> 00:00:17.723 And my name is Brent. 00:00:18.367 --> 00:00:22.505 Hello, gentlemen. Coming up on the show today, how we are pulling the storage 00:00:22.505 --> 00:00:26.802 around our LAN into one giant, useful network drive. 00:00:27.301 --> 00:00:31.155 We have finally cracked it. Plus, our thoughts on the new Steam frame. 00:00:31.155 --> 00:00:34.715 Then we're going to round it out with some great boost picks and a lot more. 00:00:34.715 --> 00:00:38.395 So before we get to that, let's say time-appropriate greetings to our virtual 00:00:38.395 --> 00:00:39.863 lug. Hello, mumble room. 00:00:40.647 --> 00:00:43.183 Hello. Thank you for your service, and hello, Brent. 00:00:43.764 --> 00:00:44.625 Strong room today. 00:00:44.625 --> 00:00:48.225 Nice. Nice having you guys here. Thank you. And, of course, you can always join 00:00:48.225 --> 00:00:50.097 our mumble room. We've got details on our website. 00:00:50.469 --> 00:00:53.632 Hello, everybody watching live, too, making it a Tuesday on a Sunday. 00:00:54.050 --> 00:00:58.575 And good morning to our friends over at Defined Networking. Go meet Manage Nebula, 00:00:58.575 --> 00:01:01.636 defined.net slash unplugged. 00:01:02.385 --> 00:01:06.315 Nebula is my network hero. When it just comes to something as foundational as 00:01:06.315 --> 00:01:09.275 a mesh network, something I'm going to build on top of for a long time, 00:01:09.275 --> 00:01:10.668 I want to own the whole stack. 00:01:11.092 --> 00:01:13.983 I really like Manage Nebula because it's a great way for you to get started. 00:01:14.250 --> 00:01:18.305 100 hosts, absolutely free, and now they are throwing in a lighthouse as well. 00:01:18.305 --> 00:01:19.782 Plus, you can run your own lighthouse. 00:01:20.397 --> 00:01:24.293 So talk about something super robust, under your control, no big tech login. 00:01:24.687 --> 00:01:28.223 It's really great. And it is secure. It's fast. It's built to scale. 00:01:28.507 --> 00:01:31.769 It uses less network, less CPU than some of the competitors out there. 00:01:32.193 --> 00:01:34.353 It really is a different VPN experience. 00:01:34.782 --> 00:01:37.805 Go try it out. 100 hosts for free. You're really going to like it. 00:01:37.805 --> 00:01:41.139 for anything from a simple host-to-host to a large global mesh network. 00:01:41.452 --> 00:01:42.369 You're going to be impressed. 00:01:42.752 --> 00:01:48.035 Defined.net slash unplugged. And thank you to Defined for sponsoring the Unplugged program. 00:01:52.238 --> 00:02:00.747 Well, as you may have heard last week, we're officially going to Texas for Texas Linux Festival 2026. 00:02:00.747 --> 00:02:03.278 We hope you are or will consider doing it, too. 00:02:03.492 --> 00:02:06.807 Yes, November 6th through the 7th. We'd love to see you there because we'd love 00:02:06.807 --> 00:02:09.927 to have a little meetup. And we are asking if anybody out there wants to throw 00:02:09.927 --> 00:02:12.960 some sats or fiat our way via the Boost page. 00:02:14.447 --> 00:02:17.837 We are asking because the budget's tight. We're grateful for what we have, 00:02:17.837 --> 00:02:19.787 but a little bit more and we could maybe do a little meetup. 00:02:19.787 --> 00:02:21.070 And I think that'd be really great. 00:02:21.262 --> 00:02:23.433 Boost.jupiterbroadcasting.com. 00:02:23.671 --> 00:02:27.327 And if you can be there reach out let us know we do have that Texas Linux Fest 00:02:27.327 --> 00:02:30.079 Matrix chat room I think that's going to start warming up again, 00:02:30.747 --> 00:02:34.166 and there may even be an old Telegram group out there rattling around as well, 00:02:34.688 --> 00:02:37.747 perhaps we should dig for that but we'd love to see you there and then we're 00:02:37.747 --> 00:02:40.487 going to try to put together some coverage so if you can't make it you get a 00:02:40.487 --> 00:02:44.760 taste of what we think is one of the really special fests out there so that's also you know, 00:02:45.300 --> 00:02:49.485 probably why we're mentioning it so look forward to that coverage in the future in a way that only we do, 00:02:53.090 --> 00:02:56.948 Before we get into the storage situation that I'm very excited about, 00:02:57.076 --> 00:03:03.067 I think we should just mention for posterity that we now have the official details 00:03:03.067 --> 00:03:06.985 on Valve's SteamFrame and it is available for pre-order starting at, 00:03:07.872 --> 00:03:09.945 10,000, 10,000. 00:03:10.142 --> 00:03:10.927 It's a deal for that. 00:03:10.927 --> 00:03:14.792 Yeah, I wish. I wish that was a deal. I wish I was that rich. 00:03:14.995 --> 00:03:19.897 No, 1,059, which is probably actually slightly cheaper than I was expecting. 00:03:19.897 --> 00:03:24.759 Of course, if you want to bump that storage up to a terabyte, it's more like $1,300. 00:03:24.887 --> 00:03:26.344 Yeah, what, the base is 256? 00:03:26.535 --> 00:03:30.552 But I was prepping myself for $1,300 being the starting price, 00:03:30.779 --> 00:03:32.187 just with the supply chain what it is. 00:03:32.187 --> 00:03:35.927 Right, that's just it. It's both more than you'd like and realistically maybe 00:03:35.927 --> 00:03:36.927 a little better than you hoped. 00:03:36.927 --> 00:03:38.041 Brent, have you ordered yours? 00:03:38.418 --> 00:03:42.247 Not quite yet. Not quite yet. I think Jeff's picking me up one, though. Right, Jeff? 00:03:42.247 --> 00:03:43.161 Oh, okay. Yeah. 00:03:43.469 --> 00:03:44.117 Oh, I wish. 00:03:45.217 --> 00:03:46.963 You'd have pre-ordered one, though, right? Which one? 00:03:47.172 --> 00:03:52.667 I did get in the reservation queue. I have not gotten email to actually purchase that device yet. 00:03:52.667 --> 00:03:54.479 Oh, you're in the line to get in line? 00:03:55.228 --> 00:03:58.737 No, I'm in the line to purchase, not the line to get in line to purchase. 00:03:58.737 --> 00:03:59.377 Oh, there's another line. 00:03:59.457 --> 00:04:00.887 So I have one above that. Oh, my God. 00:04:00.887 --> 00:04:02.293 It's a several queue system. 00:04:02.821 --> 00:04:03.924 So supplies are limited. 00:04:04.586 --> 00:04:08.447 There's a reservation queue, which means that you will get the chance to purchase 00:04:08.447 --> 00:04:11.207 once it's ready to be purchased, whenever that may be. 00:04:11.207 --> 00:04:14.977 And then there is the waitlist queue, which means that you're in the next batch, 00:04:14.977 --> 00:04:18.216 essentially. So I'm in the reservation. I'm just waiting for that email to say, 00:04:18.611 --> 00:04:22.634 give me your money and I will give them my $1,300 for the one terabyte kit. 00:04:22.953 --> 00:04:24.033 Oh, that's exciting. 00:04:24.537 --> 00:04:27.051 I think the rest of us are in the envy queue at this point. 00:04:27.434 --> 00:04:30.357 Yeah, there is another queue. And you're right. 00:04:31.666 --> 00:04:36.187 the uh the funny thing is jeff is i mean i assume you're going to use it to 00:04:36.187 --> 00:04:37.581 game right that's why you're getting it. 00:04:38.324 --> 00:04:42.377 Yeah mainly gaming i mean it's linux on your face so i'm gonna have as much 00:04:42.377 --> 00:04:44.716 fun as i can with this thing i'm so excited for that. 00:04:45.076 --> 00:04:51.159 See for me that's the linux on the face thing is the really big thing is a persistent, 00:04:52.255 --> 00:04:58.247 workspace and workstation with your apps your environment and you just put it 00:04:58.247 --> 00:05:00.137 in your backpack and then you just slip it on your face. 00:05:00.137 --> 00:05:04.103 If you're on an airplane, you're in a car, you're sitting at home on the couch, 00:05:04.498 --> 00:05:08.538 to me, that just seems really powerful. And you combine it with something like a Bluetooth keyboard, 00:05:09.839 --> 00:05:12.340 And you could really get some work done. I've been experimenting. 00:05:12.944 --> 00:05:16.109 Just as this came out, I decided I'll fire up the old MetaQuest again. 00:05:16.109 --> 00:05:18.909 And I've been experimenting. And there's a lot of Android apps that are pretty 00:05:18.909 --> 00:05:22.989 good now. There's pretty good terminal apps. There's a lot of the work apps 00:05:22.989 --> 00:05:25.909 you need. And there's decent browsers. And you combine that with something like 00:05:25.909 --> 00:05:26.917 Sunshine and Moonlight. 00:05:27.503 --> 00:05:30.869 And it's a really compelling work environment. It's not quite there yet. 00:05:30.869 --> 00:05:32.902 And it's not as open as I would like. 00:05:33.929 --> 00:05:35.247 And, of course, it's attached to Meta. 00:05:36.362 --> 00:05:39.479 So that's why I'm very excited from a productivity standpoint about the frame. 00:05:39.479 --> 00:05:44.280 Right, having some other option out there that is even more just like exactly what you want. 00:05:44.848 --> 00:05:49.889 But I think if you're skeptical of what I'm saying, I invite you to check out Launch 84. 00:05:49.889 --> 00:05:53.059 We'll put a link in the show notes. My last quest, I decided to kind of do like 00:05:53.059 --> 00:05:57.999 an exit interview with the Oculus and where they're at with their Horizon OS and all of that. 00:05:57.999 --> 00:06:01.799 And I really do think there is something there, especially if you spend a lot 00:06:01.799 --> 00:06:05.420 of your day in a terminal and a web browser and a couple of chat apps. 00:06:06.006 --> 00:06:07.169 You get a lot of work done that way. 00:06:07.929 --> 00:06:11.229 It's nuts what these things are capable of. I mean, it's because it's the applications, 00:06:11.229 --> 00:06:14.662 it's the environment, it's your state in this headset. 00:06:15.132 --> 00:06:17.029 They just slip on and you just write back to work. 00:06:17.029 --> 00:06:19.599 It's not a whole desk. It's not a particular machine. 00:06:19.599 --> 00:06:19.863 Yeah. 00:06:21.529 --> 00:06:24.257 But it's going to be a while, I think, but people will get these and they'll 00:06:24.257 --> 00:06:26.987 start building. That'll be something. And Jeff, I hope you'll take a look at 00:06:26.987 --> 00:06:29.923 the desktop experience and give us a report when you do finally get it. 00:06:30.074 --> 00:06:34.097 Absolutely, we'll do so. Don't think it'll quite meet the needs for you. 00:06:34.097 --> 00:06:34.627 Yeah, not yet. 00:06:34.627 --> 00:06:36.105 Everything I've heard you talk, yeah. 00:06:37.197 --> 00:06:38.311 But it could be built. 00:06:38.985 --> 00:06:43.577 Exactly. It's Linux on your face. And we already have some decent implementations 00:06:43.577 --> 00:06:48.287 with like Plasma doing virtual desktops in terms of sending it to a different device. 00:06:48.287 --> 00:06:52.337 So with Wayland and everything like that, I don't see it being too long before 00:06:52.337 --> 00:06:57.027 we have a bunch of desktops around your head and having something similar than 00:06:57.027 --> 00:07:01.059 what you get with the Quest. I'm very excited. I cannot wait to get my hands on it. 00:07:02.517 --> 00:07:04.762 You know quite a bit about the frame. 00:07:07.102 --> 00:07:09.586 Since it's just running SteamOS, can you boot straight to the desktop? 00:07:11.148 --> 00:07:14.445 It doesn't do the back and forth like the deck does. 00:07:15.159 --> 00:07:18.047 it boosts you into a virtual environment and you can have the desktop floating 00:07:18.047 --> 00:07:21.587 next to your main environment so there's no like rebooting it or logging out 00:07:21.587 --> 00:07:23.321 it's just it's all in one it's pretty nice, 00:07:24.900 --> 00:07:29.267 so it'd be running like game scope on one side using the resources for the environment 00:07:29.267 --> 00:07:32.806 that you'd play games in and then the desktop could be rendered next to it, 00:07:33.503 --> 00:07:36.947 yep just a floating window your entire desktop whatever size you want right 00:07:36.947 --> 00:07:41.177 next to your game or whatever other thing you got going on in the main environment. 00:07:42.791 --> 00:07:46.927 Do you know for the desktop environment, it would also do the foveal rendering, 00:07:46.927 --> 00:07:51.868 the render what I'm looking at in high resolution and the other stuff in lesser resolution? 00:07:54.057 --> 00:07:59.475 Don't think it will do the foveated rendering i don't think you know it won't 00:07:59.475 --> 00:08:03.015 need to and and the reason i say that because it's not rendering 3d graphics 00:08:03.015 --> 00:08:06.235 necessarily like it would for a game and foveated rendering versus foveated 00:08:06.235 --> 00:08:07.485 streaming are different now, 00:08:08.045 --> 00:08:13.175 i suspect that if you're streaming your desktop with specifically with steam 00:08:13.175 --> 00:08:17.915 streaming from from you know your main computer it will be doing foveated streaming 00:08:17.915 --> 00:08:21.062 in that case so one thing that i do want to try is, 00:08:21.677 --> 00:08:26.405 streaming a very very high resolution desktop quote unquote like you know like 00:08:26.405 --> 00:08:31.345 a 4k desktop from my desktop and then zooming in having a giant one giant monitor 00:08:31.345 --> 00:08:33.606 with tiling and then the foveated uh 00:08:34.007 --> 00:08:37.725 streaming should handle the performance on that but i even then i don't think 00:08:37.725 --> 00:08:39.179 the performance is going to be a big deal 00:08:39.603 --> 00:08:42.151 with their dongle the streaming dongle they've got going on so, 00:08:42.830 --> 00:08:46.725 it's it's cool it's exciting i i really really can't wait to get my hands and the. 00:08:46.725 --> 00:08:50.625 Flexibility of being able to stream a large desktop or run the desktop directly 00:08:50.625 --> 00:08:54.065 on the device is going to be powerful. And then when people work on dedicated 00:08:54.065 --> 00:08:59.195 work environments for it, I'm sure eventually they'll replace the entire big 00:08:59.195 --> 00:09:01.365 picture experience and it'll be some custom thing. 00:09:01.665 --> 00:09:04.041 I mean, there's just going to be so much that happens with this, I imagine. 00:09:04.760 --> 00:09:06.305 It'll just take a little while and we have to get in our hands. 00:09:06.305 --> 00:09:08.766 The seeds are here, just waiting for things to bloom. 00:09:08.905 --> 00:09:11.865 And, I mean, what did you think of the price, Jeff? Was it just about where 00:09:11.865 --> 00:09:14.141 you expected? Was it a little bit more than you wanted to swallow? 00:09:14.472 --> 00:09:18.835 Yeah, I mean, I call it $1,300. I wasn't sure if that was going to be for the 00:09:18.835 --> 00:09:21.625 256 or the one terabyte. I'm glad it's for the one terabyte. 00:09:22.445 --> 00:09:26.075 Micro SDs are unfortunately at 200 bucks for the one terabyte cards. 00:09:26.075 --> 00:09:31.910 So yeah, I'd splurge for that. It's obviously soldered on. So unlike the deck, you can't replace it. 00:09:32.427 --> 00:09:36.549 You know, it's, it's where I expected it. Performance wise, we'll see, 00:09:37.402 --> 00:09:41.915 you know, everybody compares it to the, to the MetaQuest 3 because it basically 00:09:41.915 --> 00:09:46.596 is a MetaQuest 3 in terms of hardware, in terms of battery life, in terms of displays, 00:09:47.083 --> 00:09:51.495 a lot of people have complained about the lcds and this and that but yeah i 00:09:51.495 --> 00:09:52.675 don't know you know right now. 00:09:52.675 --> 00:09:54.572 I can work two to four hours a week in it. 00:09:55.953 --> 00:09:59.779 Yeah, okay. And given that you can just put a battery pack in your pocket, 00:09:59.779 --> 00:10:01.439 I don't think it's a big deal if you're gaming. 00:10:02.259 --> 00:10:07.159 My headset has a replaceable battery, and I can swap it out while I'm live, 00:10:07.159 --> 00:10:10.745 and then I just plug it into USB-C and it charges. It's very comfortable. 00:10:11.899 --> 00:10:15.379 And Valve claims we'll be getting that for the frame later on as well, 00:10:15.939 --> 00:10:22.679 a whole new kind of head strap with a removable battery and a more Steam Index-like headset. 00:10:22.679 --> 00:10:26.109 That's kind of why I was brought back to the quest and wanted to try this out 00:10:26.109 --> 00:10:30.249 recently because it's sort of, it's a lot in a lot of ways what I can expect 00:10:30.249 --> 00:10:34.059 from the frame, but some of the workflows are a little more mature around. 00:10:34.059 --> 00:10:37.030 It has an MCP and a CLI and all of that. 00:10:37.939 --> 00:10:41.029 So I think the frame will get there. And I just think it's like for travel, 00:10:41.029 --> 00:10:44.099 for work, for people that have small spaces they need to be in. 00:10:44.557 --> 00:10:45.898 It's going to be so great. 00:10:47.036 --> 00:10:49.299 And then it's going to game too, by the way. It's going to game. 00:10:49.299 --> 00:10:51.879 Yeah, then you also have a really great gaming experience right around the corner. 00:10:52.824 --> 00:10:55.111 Well, congrats, Jeff. I hope the queue doesn't last too long. 00:10:55.279 --> 00:10:59.039 Maybe, you know, maybe you'll know something by Christmas. It's probably going to be early next year. 00:10:59.759 --> 00:11:01.179 No, don't say that. 00:11:01.179 --> 00:11:01.779 No, I hate it. 00:11:01.779 --> 00:11:02.460 I hope not. 00:11:02.640 --> 00:11:05.889 It'd be amazing if they arrived in time for the holidays. That'd be really great. 00:11:05.889 --> 00:11:06.582 Don't prove us wrong. 00:11:06.703 --> 00:11:07.359 Yeah. 00:11:07.799 --> 00:11:11.389 I'm really hoping it'll be like within this month. They've claimed they'll be 00:11:11.389 --> 00:11:15.335 shipping before summer. So, you know, if you're in the reservation, 00:11:15.562 --> 00:11:16.729 hopefully we'll get it soon. 00:11:17.809 --> 00:11:21.240 Very good. Thank you, Jeff. Thank you. All right. So, Brentley, 00:11:21.641 --> 00:11:27.986 I have talked about, I want to see if you can recall, but I have talked about the ability to take, 00:11:28.618 --> 00:11:34.626 spare storage on the various computers around the LAN and try to pool it into one large disk. 00:11:34.963 --> 00:11:37.385 Like a virtual, mm-hmm, mm-hmm. 00:11:37.385 --> 00:11:39.796 Especially with storage getting as expensive as it is, right? 00:11:40.197 --> 00:11:42.655 It's getting expensive to go out there and buy hard drives. And if you've got 00:11:42.655 --> 00:11:46.325 machines sitting around with a terabyte, so this machine has like 200 gigs free 00:11:46.325 --> 00:11:49.705 here. This machine has two terabytes free over here, right? You know what I mean? 00:11:49.705 --> 00:11:53.475 You have a lot of stranded spare capacity, but, you know, being able to design 00:11:53.475 --> 00:11:57.435 and build from scratch the right sort of NAS or cluster is prohibitively expensive. 00:11:57.435 --> 00:12:00.213 And I have a feeling you know exactly how that feels, Brad. 00:12:00.439 --> 00:12:06.735 To me, this feels like your long-term plan to just sip away some of Wes and 00:12:06.735 --> 00:12:08.115 I's storage for your own works. 00:12:09.955 --> 00:12:12.735 I hadn't thought of that, but that is a great idea. You boys want to join the pool? 00:12:13.835 --> 00:12:15.275 What do we get? What do we get? 00:12:16.735 --> 00:12:20.780 One giant jellyfin share. One giant distributed jellyfin share. 00:12:21.203 --> 00:12:26.022 So this week, RustFS went 1.0. 00:12:27.589 --> 00:12:31.983 It's an open-source, S3-compatible, high-performance object storage system. 00:12:33.051 --> 00:12:37.508 And you can think it's all like MinIO, Ceph. There's some other. There's a lot of. 00:12:37.778 --> 00:12:37.998 Garage, mm-hmm. 00:12:38.318 --> 00:12:42.388 Yeah, there's some solutions out there. This one's nice because it's an open 00:12:42.388 --> 00:12:46.098 license. It just hit 1.0. They've put about two years of work into building 00:12:46.098 --> 00:12:49.618 something. Well, more than that, almost three years of work building something really impressive. 00:12:49.618 --> 00:12:53.820 Yeah, it's MIT, fresh implementation, Rust, of course. 00:12:54.163 --> 00:13:00.168 It supports more than just S3. It can also support WebDAV, FTPS, other things that... 00:13:00.278 --> 00:13:04.238 Yeah, some of those, I think, like SFTP is maybe compiled time. 00:13:04.238 --> 00:13:06.188 Some of them you have to, like, turn on. They're not there by default, 00:13:06.188 --> 00:13:07.718 but that kind of stuff is growing. 00:13:08.246 --> 00:13:12.304 1.0 also added some features that are just nice to have, like erasure coding, 00:13:12.634 --> 00:13:18.138 self-healing nodes, rebalancing of the pool, bucket replication, 00:13:18.138 --> 00:13:20.948 just stuff that's just quality of life you want to see before you really commit 00:13:20.948 --> 00:13:23.002 to something like this, and it landed in the 1.0. 00:13:23.641 --> 00:13:25.748 So that kind of caught our attention at that point. 00:13:25.748 --> 00:13:28.048 Yeah, it really seems like they're trying to signal, you know, 00:13:28.048 --> 00:13:31.108 okay, this can actually maybe be used now. If they didn't, you know, 00:13:31.108 --> 00:13:33.648 it wasn't rushed out after three months. They've spent, you know, 00:13:33.648 --> 00:13:36.618 more than two years sort of working and iterating, which makes sense because 00:13:36.618 --> 00:13:40.654 you really, you're going to build everything else on top of this. So it needs to work. 00:13:41.477 --> 00:13:45.773 So why object storage? Because I think when we say S3, people think Amazon. 00:13:45.912 --> 00:13:49.785 I mean, a lot of people probably think Amazon. So why would a person want to 00:13:49.785 --> 00:13:52.935 run object storage in their home lab or on their corporate LAN or something 00:13:52.935 --> 00:13:54.713 like that? What would be your pitch? 00:13:55.409 --> 00:13:59.505 Well, it turns out that you don't always need a file system. 00:13:59.505 --> 00:14:03.845 A file system comes with a lot of things, right? They kind of grew out of trying 00:14:03.845 --> 00:14:08.085 to be able to put stuff on disk and use it in a non sort of tape storage based 00:14:08.085 --> 00:14:10.119 way. We have random access. What can we build? 00:14:10.566 --> 00:14:14.535 you know, fat in the file allocation table. And obviously there's a lot of great 00:14:14.535 --> 00:14:17.065 stuff about having a file system. We love file systems here on the show. 00:14:17.905 --> 00:14:22.345 But these days, especially as we tried to, you know, distribute, 00:14:22.345 --> 00:14:25.723 we have distributed computers, distributed systems, the rise of the cloud. 00:14:26.965 --> 00:14:30.945 It turned out that we still needed to store files, blobs, backups, 00:14:31.345 --> 00:14:33.622 media, artifacts, all kinds of stuff. 00:14:33.994 --> 00:14:37.795 But we didn't actually need all of the traditional properties of a file system. 00:14:37.795 --> 00:14:42.835 And so if you if you take off some of those, those end up being like fewer constraints 00:14:42.835 --> 00:14:47.455 that you need and you can then optimize the core parts that you're doing, which is like, 00:14:47.763 --> 00:14:52.135 you know, being able to put and get something by like an object ID and maybe 00:14:52.135 --> 00:14:55.025 have it distributed, maybe have it replicated, all that kind of layer. 00:14:55.234 --> 00:14:58.105 You'll also find like a lot of the apps that you can self host these days, 00:14:58.105 --> 00:15:00.180 they have an S3 storage option. 00:15:00.563 --> 00:15:03.460 It's becoming very, very common for an S3 storage back end. 00:15:03.599 --> 00:15:07.945 Yeah, and it's been that way for a while, right? Like S3 has been here for a long time now. 00:15:08.485 --> 00:15:11.825 We're even already running our production Nextcloud that way. 00:15:12.305 --> 00:15:16.305 We have been for a long time, which is great because you don't really have to 00:15:16.645 --> 00:15:18.199 allocate space in the traditional way. 00:15:18.489 --> 00:15:21.695 It's great at storing blobs. You know, it's particularly good at that too. 00:15:21.695 --> 00:15:24.895 So there's some advantages if you have like images and media files and things 00:15:24.895 --> 00:15:26.442 like that, which we have a lot of. 00:15:27.971 --> 00:15:30.961 And it's been fairly robust. Any problems we really have had have been more 00:15:30.961 --> 00:15:35.456 in the application implementation layer. Never really an issue with the S3 storage itself. 00:15:36.291 --> 00:15:40.841 And it can turn a pile of otherwise separate storage into one programmable storage 00:15:40.841 --> 00:15:43.722 service, which is what I was interested in. 00:15:44.227 --> 00:15:47.471 So I wanted to build a little test environment to see how viable this was. 00:15:47.471 --> 00:15:54.961 So I set up four headless VMs, each with their own 50 gigs of disk to store. 00:15:56.051 --> 00:16:01.224 And then I set up a fifth VM that acts as kind of like a client that runs Jellyfin 00:16:01.503 --> 00:16:05.951 and a front end to those headless Nix servers, the little VMs. 00:16:05.951 --> 00:16:09.560 Because what I was picturing is four or five systems around my LAN, 00:16:10.889 --> 00:16:15.881 100 gigs over here, 50 gigs over here, a terabyte over there, that kind of setup. 00:16:15.881 --> 00:16:21.271 So I was just creating a couple of VMs, a few VMs, and a master client server 00:16:21.271 --> 00:16:22.168 that sat in front of that. 00:16:22.547 --> 00:16:28.401 And that VM, that master server that ran Jellyfin, used our clone to connect 00:16:28.401 --> 00:16:36.241 to RustFS over S3 and mount and expose what was a collection of my storage system. 00:16:36.241 --> 00:16:41.351 So that was the test setup. And the goal was, with this distributed object storage 00:16:41.351 --> 00:16:46.621 across multiple machines, would they behave well enough for something like a 00:16:46.621 --> 00:16:48.684 4K Jellyfin file to stream? 00:16:48.835 --> 00:16:51.891 And this is an example, right, where Jellyfin isn't necessarily designed around 00:16:51.891 --> 00:16:56.591 object storage. So you use an art clone to bridge the gap and make the S3 object 00:16:56.911 --> 00:16:59.701 storage dial back and show up as if it were part of the file system. 00:16:59.701 --> 00:17:03.901 Yeah. And one large disk, too. Not a bunch of individuals. I don't want to mess with that. 00:17:03.901 --> 00:17:04.207 Right. 00:17:04.445 --> 00:17:08.764 And I wanted to support one of them at least going offline because on a homeland, 00:17:09.228 --> 00:17:12.351 that's very likely that one of these nodes is going to turn off and you don't 00:17:12.351 --> 00:17:13.371 want the whole thing to blow up. 00:17:13.371 --> 00:17:16.461 Right. If you sort of turn this into a big distributed system and you don't 00:17:16.461 --> 00:17:19.801 add redundancy, then you've built yourself a super brittle waiting to fail state. 00:17:19.801 --> 00:17:22.080 Which is going to be so frustrating when you go hit that play button. 00:17:22.580 --> 00:17:26.486 So that's what the goal was. I'll tell you how it went on the other side. 00:17:36.278 --> 00:17:41.954 Well, I don't mean to be this guy, but it was very easy to do this via Nix because 00:17:41.954 --> 00:17:43.505 RustFS ships an upstream flake. 00:17:43.900 --> 00:17:46.064 There's even one in Nix packages, too, I believe. 00:17:46.104 --> 00:17:46.624 That's so great. 00:17:46.624 --> 00:17:50.354 But if you want a more fancy cluster like we were testing out, 00:17:50.354 --> 00:17:52.474 then the upstream flake is the good path. 00:17:52.474 --> 00:17:55.404 It was really nice for just deploying a bunch of VMs and testing this to see 00:17:55.404 --> 00:17:57.834 if it was viable because you didn't have to have a custom installer, 00:17:57.834 --> 00:17:59.057 though they do offer one. 00:17:59.475 --> 00:18:01.542 Or I didn't even have to set up a container. It was really nice. 00:18:01.826 --> 00:18:06.052 So, yeah, I set up just some Nix-based systems using their flake, enabled the service. 00:18:06.348 --> 00:18:08.780 And I pointed it at the VM's persistent storage. 00:18:09.349 --> 00:18:14.934 And then, you know, something I've been doing more is using something to manage 00:18:14.934 --> 00:18:16.654 the credentials, too, which I really like. Instead of, like, 00:18:16.654 --> 00:18:18.624 baking them into the NIC store or somewhere on your file system, 00:18:18.624 --> 00:18:20.007 I've been using, like, SOPS NICs. 00:18:20.964 --> 00:18:23.949 So that's been nice because there is some credential management you have to do. 00:18:25.064 --> 00:18:28.594 Yeah, it can use Systemd credentials, which I also really like as a way. 00:18:28.594 --> 00:18:32.464 So Systemd handles making sure that everything's provided securely. 00:18:32.464 --> 00:18:36.626 You don't have the fault, the downsides of using NVARs and that kind of thing. 00:18:37.078 --> 00:18:40.484 So it's nice to see that support because it means it plays nicely with ship 00:18:40.484 --> 00:18:41.960 secrets your own sidecar way. 00:18:42.094 --> 00:18:45.494 Use SOPSNICs or AGENICs. It just plays right in with all of this. 00:18:45.494 --> 00:18:49.588 It does. And so that part was quite easy. That whole setup was surprisingly smooth. 00:18:50.064 --> 00:18:54.006 Where it went wrong was in my own assumptions. 00:18:54.697 --> 00:18:58.004 I did not properly read the documentation, I will admit. 00:18:58.984 --> 00:19:02.264 I skipped right. You know, because they always have the splash page. 00:19:02.264 --> 00:19:05.749 for like the documentation splash page. And then like all the stuff you want 00:19:06.022 --> 00:19:09.772 is usually like in a subsection because I just want to know the one thing, right? So I jumped down. 00:19:10.573 --> 00:19:14.387 And then later on when I went back and read like the front page and I scrolled down, 00:19:15.507 --> 00:19:21.982 They had this big warning there that you want to use at least a minimum of four 00:19:21.982 --> 00:19:25.961 storage nodes, not the three that I had initially set up. 00:19:26.251 --> 00:19:29.092 Yeah, I was looking at it. It can technically go all the way down to two. 00:19:29.472 --> 00:19:32.412 But four is like what they bless for production. And it's what a bunch of their 00:19:32.412 --> 00:19:35.832 test infrastructure actually tests is sort of what they provide guidance on 00:19:35.832 --> 00:19:39.872 upgrade paths for. So it's really the like blessed setup. Or more. 00:19:40.312 --> 00:19:44.672 In my opinion, if that is a deal breaker for you, that's probably something 00:19:44.672 --> 00:19:48.914 to flag. Like, it's not the end of the world, but you're probably not using a blessed setup. 00:19:49.500 --> 00:19:53.092 Now, for me, that was just one more VM. And I also, I do have plenty of systems 00:19:53.092 --> 00:19:55.852 on my LAN to do that. I probably have more than five. 00:19:56.212 --> 00:19:59.412 And I believe part of the reason is, like, you don't get necessarily more node. 00:19:59.752 --> 00:20:02.662 Like, it doesn't protect you from more node failures in 3, but it does mean 00:20:02.662 --> 00:20:06.272 that as you're rebuilding things after 1, that you're in a more resilient setup. 00:20:06.752 --> 00:20:07.912 Yeah, it's really about redundancy. 00:20:07.912 --> 00:20:08.842 Yeah, operations. 00:20:08.842 --> 00:20:12.581 Yeah. So, and let's actually talk about that for a moment. 00:20:13.986 --> 00:20:18.090 So I took, in total, I had about 200 gigabytes of raw storage to work with. 00:20:19.272 --> 00:20:26.282 But when you consider the redundancy, what I got usable out of that 200 gigs was 91.7 gigabytes. 00:20:26.282 --> 00:20:31.300 Yeah, and you did like a racer code and sort of parody raid style setup. 00:20:31.456 --> 00:20:36.391 Yeah, and so I definitely ate it in the redundancy department. So that is very true. 00:20:37.692 --> 00:20:43.206 But the resiliency worked. I pulled the plug on a node and the system kept working. 00:20:43.595 --> 00:20:46.515 And then when you plug the node back in, it rebuilt and it caught up. 00:20:47.054 --> 00:20:52.172 And so, yes, it does mean you lose a lot of space. But if you have the space 00:20:52.172 --> 00:20:56.002 around your LAN and you have the nodes and you want to be able to survive a 00:20:56.002 --> 00:20:58.012 machine going out, it could be worth it. 00:20:58.452 --> 00:21:01.582 Yeah. And that's part of the neat stuff, right, is because it can sort of distribute, 00:21:01.582 --> 00:21:04.172 you know, it can parity it up. It can make the various chunks, 00:21:04.172 --> 00:21:06.002 distribute those chunks across the cluster. 00:21:06.240 --> 00:21:09.332 and then you only need the right, depending on the level, that number of chunks 00:21:09.332 --> 00:21:13.310 again to be able to read from across the cluster to be able to get the file back. 00:21:13.659 --> 00:21:16.552 The thing I was happy about is the idea, so I wasn't sure how this would work 00:21:16.552 --> 00:21:19.582 exactly on the implementation side because since Jellyfin doesn't have native 00:21:19.582 --> 00:21:23.242 S3 support, I had to trick Jellyfin into using the S3 storage. 00:21:23.625 --> 00:21:29.972 So RustFS presented one distributed S3 pool and then the R clone mount exposed 00:21:29.972 --> 00:21:32.326 all of that as one single mount point. 00:21:32.704 --> 00:21:34.933 Like I had like a slash mount Rust media. 00:21:35.252 --> 00:21:39.112 And then in Jellyfin, I presume, you can just then do the normal media library configuration path. 00:21:39.112 --> 00:21:40.622 It just looks at it like it's a file system path. 00:21:40.622 --> 00:21:40.900 Nice. 00:21:41.202 --> 00:21:44.505 So that made it surprisingly easy. 00:21:45.370 --> 00:21:52.942 And I could get sequential read speeds around 360 megabytes to 430 megabytes. 00:21:52.942 --> 00:21:59.662 So I'm sorry, 360 megabytes to 430 megabytes per second across that pool, 00:21:59.662 --> 00:22:00.643 which is I'm pretty happy with. 00:22:02.912 --> 00:22:07.068 There was definitely, though, a hidden cost in how I had Rclone set up. 00:22:07.068 --> 00:22:08.688 And this is, I think, the second gotcha. 00:22:09.036 --> 00:22:12.020 First gotcha is you've got to have four nodes to really be stable. 00:22:12.380 --> 00:22:16.774 The second gotcha is you're going to need to be careful how you configure Rclone. 00:22:17.279 --> 00:22:20.540 Because Rclone is going to need to do a lot of caching. 00:22:21.115 --> 00:22:24.938 And depending on how you configure that, you can eat up a lot of disks. 00:22:24.938 --> 00:22:26.450 You can spend a lot of time caching. 00:22:26.839 --> 00:22:30.138 There is a sweet spot that I played with where I could kind of get that right 00:22:30.138 --> 00:22:33.480 and I could store the cache in a specific place, which is also very useful. 00:22:34.170 --> 00:22:39.578 But that was an area where, you know, it took a one gigabyte client disk filled 00:22:39.578 --> 00:22:45.258 up and a two gigabyte upload, right? So it's just like it's, the caching doubles it. 00:22:45.479 --> 00:22:49.078 It is a problem. You need to plan for the caching if you're going to go with this setup. 00:22:49.484 --> 00:22:52.532 Obviously, the ideal would be that Jellyfin just had native S3 support. 00:22:52.793 --> 00:22:56.258 But there's a lot of applications that don't. And so I do think you could make it work. 00:22:57.007 --> 00:22:59.108 Yeah, this is kind of a test for that side of things, right? 00:22:59.108 --> 00:23:00.998 There's plenty of applications that do, but for the things that don't, 00:23:01.698 --> 00:23:02.702 can it still work for those? 00:23:02.835 --> 00:23:05.157 Or are you sort of blocking yourself from using those apps? 00:23:05.308 --> 00:23:07.625 And there could be a better way to mount an S3 file system. 00:23:08.729 --> 00:23:11.186 Yeah, ArcLine was just sort of the thing at hand here for some quick tests, 00:23:11.186 --> 00:23:12.966 and we used it a bunch of places already. 00:23:12.966 --> 00:23:15.836 But I feel like, you know, what I was able to kind of validate in the testing 00:23:15.836 --> 00:23:19.083 is spare disks spread across multiple machines, 00:23:19.925 --> 00:23:24.386 were turned into a usable media namespace that had redundancy when one of the 00:23:24.386 --> 00:23:29.277 machines went down, that I could bring up Jellyfin and I could play a 4K movie across that. 00:23:29.834 --> 00:23:32.261 And that was really the goal, and it works. 00:23:32.856 --> 00:23:35.206 And it speeds the same, I mean, you'll have to try it again off, 00:23:35.206 --> 00:23:38.526 you know, not virtual links and the real network links and stuff. 00:23:38.526 --> 00:23:41.336 but seemingly at speeds that might be totally workable. 00:23:41.336 --> 00:23:45.046 Yes, and I think if you use any kind of infrastructure management tool like 00:23:45.046 --> 00:23:49.705 Ansible or Nix or whatever, it's really easy to just deploy this across a few of your machines. 00:23:49.827 --> 00:23:54.456 Yeah, I think that stuck with me when trying it. It was really easy to get going. 00:23:54.456 --> 00:23:58.166 Sometimes these distributed system tools need a lot of bootstrapping and setup, 00:23:58.166 --> 00:24:01.448 and it takes a while to get the whole system online, and that was not the case here. 00:24:02.696 --> 00:24:07.996 Also, very friendly for agent deployments. If you did want to tie it in to an 00:24:07.996 --> 00:24:10.336 open claw or a Hermes agent... 00:24:11.374 --> 00:24:17.680 Really straightforward. Between just the way you set it up and it also includes 00:24:17.680 --> 00:24:19.829 a comprehensive command line client. 00:24:20.312 --> 00:24:23.560 There's a lot there plus these agents already understand S3 and all these things. 00:24:23.560 --> 00:24:27.140 Like it's pretty – you could have the agents manage the file system, 00:24:27.140 --> 00:24:31.790 manage health checks. It's really pretty extensive what you could do if you 00:24:31.790 --> 00:24:35.150 wanted to. It just sort of – it plugs right into an agentic workflow if you 00:24:35.150 --> 00:24:37.919 wanted to have them manage your storage. If you were crazy enough to do that. 00:24:38.517 --> 00:24:41.160 I thought that was, you know, interesting that if something's coming out today, 00:24:41.160 --> 00:24:42.240 where does it sit in that? 00:24:43.200 --> 00:24:44.030 Looking forward in that way. 00:24:44.030 --> 00:24:47.793 And they're looking forward. They're looking forward. So Rust FS hits version 1.0. 00:24:48.315 --> 00:24:51.110 And with the right set of tooling, there's a lot of ways to crack this. 00:24:51.110 --> 00:24:55.160 But with the right set of tooling, you can truly do storage pooling that supports 00:24:55.310 --> 00:24:58.225 failover on one of your devices. And that I was very pleased to see. 00:24:58.526 --> 00:25:02.898 It is worth noting it does not have the complete AWS S3 API. 00:25:03.240 --> 00:25:07.582 it doesn't have some of the same sort of strong consistency things around like 00:25:07.808 --> 00:25:12.480 uh write and then read ordering uh in particular there is no like consensus 00:25:12.480 --> 00:25:14.941 mechanism or raft or that kind of thing, 00:25:15.434 --> 00:25:18.284 instead they lean more to like eventual consistency and so you, 00:25:18.737 --> 00:25:22.570 it is it works really well for blob workflows in particular where you're doing 00:25:22.570 --> 00:25:25.990 like a write once you're not having multiple different actors all trying to 00:25:25.990 --> 00:25:29.610 write to the same key or use that for consensus or something instead you want 00:25:29.610 --> 00:25:30.446 something where you're just like, 00:25:31.340 --> 00:25:34.200 one process is going to dump it on there and then lots of stuff is going to 00:25:34.200 --> 00:25:40.384 be able to read because if you do have some sort of network partition or a node goes offline, 00:25:42.102 --> 00:25:45.092 you can have basically it has to get a lock, 00:25:46.040 --> 00:25:50.170 a quorum lock on the cluster and then it can write but if that lock expires 00:25:50.170 --> 00:25:53.393 there's no code right now there's a feature plan but there's no code right now 00:25:53.701 --> 00:25:58.800 to like stop so you can have two different writers both get success and then the later version wins. 00:25:58.800 --> 00:26:01.720 So one of them just silently has its rights not work anymore. 00:26:01.720 --> 00:26:03.761 So there are some things like that. But for most traditional, 00:26:04.039 --> 00:26:06.257 I think, S3-style workflows, it should work just great. 00:26:08.033 --> 00:26:10.700 I've got a couple of questions that I can throw at you boys. 00:26:12.061 --> 00:26:13.260 Can we do a little thought experiment? 00:26:13.260 --> 00:26:20.590 I'm curious if, you know, I've been setting up redundant RAID on various hard 00:26:20.590 --> 00:26:23.189 drives in remote locations recently. 00:26:23.711 --> 00:26:29.017 And I'm just wondering, could this tool kind of supersede that? 00:26:29.940 --> 00:26:32.850 You don't need RAID, but you can use something like this for the redundancy. 00:26:32.850 --> 00:26:39.080 It has some cool modern redundancy in it. and maybe you don't need to necessarily have both? 00:26:40.290 --> 00:26:45.090 Yeah, I mean, it basically copies, or not copies, but has a very similar implementation 00:26:45.090 --> 00:26:51.860 of its Reed Solomon sort of erasure coding stuff to ZFS or other modern file systems like that. 00:26:52.138 --> 00:26:57.320 So you do get per block hashes and it checks that before it reads it out and 00:26:57.320 --> 00:27:00.033 serves it over the API and that kind of thing. So I think it is designed to 00:27:00.236 --> 00:27:02.378 store your files durably well. 00:27:02.663 --> 00:27:07.220 What kind of defense in depth and like, you know, what file systems that you 00:27:07.220 --> 00:27:10.380 want have under for the servers you're running anyway, I think is probably more 00:27:10.380 --> 00:27:11.404 the operational question. 00:27:12.763 --> 00:27:15.248 Okay, next question. When can we expect this in the kernel? 00:27:15.880 --> 00:27:16.070 Yeah, 00:27:18.771 --> 00:27:19.596 I don't think so. 00:27:19.851 --> 00:27:23.700 No? Okay, all right. And then last question. Did you mention what this was written 00:27:23.700 --> 00:27:26.700 in? I didn't really hear any mic or anything. 00:27:26.700 --> 00:27:27.890 Oh, you didn't catch the? 00:27:28.190 --> 00:27:30.070 It's MIT licensed REST. 00:27:30.070 --> 00:27:31.966 Oh, very fancy. 00:27:33.278 --> 00:27:36.070 I think also, like, if you're still listening and you're kind of still asking 00:27:36.070 --> 00:27:39.948 yourself, why would I want object storage? Again, guys, why do I want object storage? 00:27:40.546 --> 00:27:43.580 This could be the project to play with to figure out why you might want object 00:27:43.580 --> 00:27:46.660 storage. This is what's really nice about this is this is very accessible to 00:27:46.660 --> 00:27:49.317 any of us to deploy this. And it's clean, it's simple. 00:27:50.043 --> 00:27:54.640 And it's pretty easy to get running on just about any distro you're likely to try it on. 00:27:54.756 --> 00:27:57.380 And it seems like they are trying to hit to this kind of case. 00:27:57.380 --> 00:28:01.150 Like there's other projects that kind of aim for like geo-distributed versions 00:28:01.150 --> 00:28:06.465 of this, or there's things like Ceph or like more file system semantics that are distributed. 00:28:07.070 --> 00:28:09.330 And this seems to be really targeting kind of exactly what you were hoping, 00:28:09.330 --> 00:28:13.640 which is be able to use a sort of diverse array of storage on something like 00:28:13.640 --> 00:28:16.950 a local or enterprise network and turn it into a single pool. 00:28:16.950 --> 00:28:19.760 Yeah. Now, there's probably a lot of ways you could solve that. 00:28:19.760 --> 00:28:23.310 And I would like to hear how you have solved it. Boost.JupyterBroadcasting.com. 00:28:23.310 --> 00:28:26.550 I'm not married to this approach, but I am kind of thinking about it. 00:28:26.550 --> 00:28:28.053 I was going to ask, are you keeping it? 00:28:28.267 --> 00:28:32.615 Yeah. I think, I mean, not this particular setup, but I think definitely at home. 00:28:33.510 --> 00:28:39.380 and possibly for a new self-hosted Jellyfin server I want to build in the future. 00:28:39.380 --> 00:28:41.230 That would be an interesting production use case. 00:28:41.230 --> 00:28:44.790 Yeah, especially if you had some internet links in there, which maybe there's 00:28:44.790 --> 00:28:48.030 also a better tool for that, but I'm not sure. Boost.JupiterBroadcasting.com 00:28:48.030 --> 00:28:48.997 if you've got any feedback on that. 00:28:49.328 --> 00:28:52.097 But I do think this is what I'll be using for that moving forward. 00:28:52.497 --> 00:28:55.840 And so I'll eventually get some serious, not just testing in the lab, 00:28:55.840 --> 00:28:59.109 but serious hands-on with it, probably in the pretty near future. 00:29:09.567 --> 00:29:14.274 I imagine with your new fancy state-of-the-art file system, you're going to 00:29:14.274 --> 00:29:17.537 be throwing some media files around of various machines. 00:29:18.251 --> 00:29:21.676 Is that your hope, Chris? You got new plans for this? 00:29:22.529 --> 00:29:27.783 You know, I am trying out a new box, and I would love some feedback on this from the audience. 00:29:28.061 --> 00:29:34.383 It's the Xiaomi TV Box S 3rd Gen 4K UHD. It's Google TV. 00:29:34.987 --> 00:29:44.153 It's got 32 gigs of storage, Wi-Fi 6, HDMI 2.0, 92 US dollars on Amazon. 00:29:44.402 --> 00:29:45.034 That's not bad. 00:29:45.034 --> 00:29:48.904 It also takes SD card slots. Like the Google TV is expensive. 00:29:48.904 --> 00:29:54.352 The Apple TV is expensive. They're all, you know, the Google TV is almost $200. This is under $100. 00:29:55.205 --> 00:29:58.313 And it's pretty powerful. Of course, it's the Google TV interface. 00:29:58.313 --> 00:30:01.307 And so the ask I wanted to put out there, if anybody else has this, 00:30:01.621 --> 00:30:05.752 and have they been able to reflash this or clean up the slop that's on this thing? 00:30:06.147 --> 00:30:10.233 Because it's loaded with the Google experience. Let me tell you, it's an experience. 00:30:10.616 --> 00:30:15.150 But for $92, I'm pretty impressed with the performance. It's not. 00:30:15.336 --> 00:30:17.853 And it has all the apps that you might need or want, right? 00:30:18.353 --> 00:30:21.373 It doesn't feel any worse or any better than my Shield, which has been kind 00:30:21.373 --> 00:30:24.933 of my benchmark for a long time. It feels probably about as fast. 00:30:24.933 --> 00:30:28.793 Because as we know, if you under-spec Android boxes, they can be a little slow. 00:30:29.407 --> 00:30:33.163 Did you consider any other boxes to solve this problem? Like maybe an old cell 00:30:33.163 --> 00:30:34.133 phone running Linux, maybe? 00:30:34.953 --> 00:30:39.123 Yeah, yeah, I did. But it's for my daughters, and, you know, 00:30:39.123 --> 00:30:40.533 they just, you know, I don't want to. 00:30:40.893 --> 00:30:44.463 If it was a TV for me, I would probably actually just get like a Roku or, 00:30:44.463 --> 00:30:45.557 yeah, like use an Android. 00:30:46.131 --> 00:30:47.879 Use my Paizel, potentially. 00:30:49.113 --> 00:30:51.716 But for them, I wanted something that was a little more appliance. 00:30:52.174 --> 00:30:56.013 and I felt like that was a pretty good price at $92 because when I look at the 00:30:56.013 --> 00:31:00.261 market, the only thing that gets close to that would be a Roku or a Fire Stick. 00:31:00.993 --> 00:31:04.909 And in that situation, I would just prefer to have the Android applications 00:31:05.298 --> 00:31:09.327 because then you get a good Jellyfin app, you get the good Plex app, that kind of stuff. 00:31:09.600 --> 00:31:12.013 There's stuff like Mesh VPN apps. 00:31:12.433 --> 00:31:14.913 That's the other big one is it has to be on the Mesh network. 00:31:16.953 --> 00:31:20.193 That was also a big deal. So I'm going to put a link to it in the show notes 00:31:20.193 --> 00:31:23.983 if you're curious. I don't have any affiliation. It's not even an affiliate 00:31:23.983 --> 00:31:24.809 link. I don't make a dime. 00:31:25.360 --> 00:31:29.533 But it is working for me. And if you out there have one like this and you've 00:31:29.533 --> 00:31:35.633 been able to make the experience better without all the Google crap on there, give me your tips. 00:31:35.993 --> 00:31:37.173 Help us hack Chris's TV. 00:31:37.213 --> 00:31:41.483 Yeah, but let me make it better. That's all I want. I just want it to not be 00:31:41.483 --> 00:31:45.543 so basically a constant commercial because that's what it feels like. 00:31:45.543 --> 00:31:48.232 But think of the advertisers and think about Google. 00:31:48.569 --> 00:31:50.113 Yeah, I need to know about their new experiences. 00:31:50.113 --> 00:31:50.531 Yeah. 00:31:55.053 --> 00:31:59.198 Speaking of experiences, we got some support this week, and we're going to start 00:31:59.198 --> 00:32:04.479 with Anonymous, who comes in as our baller booster at 75,000 sats. 00:32:08.333 --> 00:32:10.266 That ain't too shabby. 00:32:19.473 --> 00:32:24.589 Alright, so Anonymous writes, recently got a Mac SE30. I'll try to figure out 00:32:24.589 --> 00:32:25.999 how to boost over Apple Talk. 00:32:26.739 --> 00:32:29.479 Now this is such a classic machine. I use the crap out of these. 00:32:29.559 --> 00:32:32.012 I don't know who Anonymous is, but I do know they're my new best friend. 00:32:33.010 --> 00:32:36.012 I do know that. That is going to be such a fun project. 00:32:36.482 --> 00:32:40.359 Also, tell me if you're not tempted to get TCPIP working on that thing somehow. 00:32:41.139 --> 00:32:46.299 Come on, right? Come on. And then how great would it be if you could get some 00:32:46.299 --> 00:32:49.039 sort of SSH client? That's probably not going to happen. 00:32:49.099 --> 00:32:51.429 Just your thin client, that's what you're able to use to work on. 00:32:51.429 --> 00:32:53.485 I don't think the cryptography is going to happen on that old thing. 00:32:54.459 --> 00:32:56.989 You know, we're complaining about computer prices these days. 00:32:56.989 --> 00:33:03.857 Back then it was sold for $4,369 US dollars, which in today's dollars, $11,350. 00:33:05.379 --> 00:33:06.173 So not a bad deal? 00:33:06.417 --> 00:33:11.949 Yeah, that is the funny thing. If you look at 80s prices and value them by today's 00:33:11.949 --> 00:33:15.879 dollar, yeah, we were paying out the nose back then. That was one of the big 00:33:15.879 --> 00:33:16.703 controversies, really. 00:33:17.795 --> 00:33:21.359 So, yeah. Wow, that is a great boost. Thank you very much, Anonymous. Hope you have fun. 00:33:21.916 --> 00:33:25.279 Josh comes in with $24,690. 00:33:25.279 --> 00:33:25.707 All right. 00:33:28.319 --> 00:33:31.689 Oh, it's a double batch of 1, 2, 3, 4, 5. 00:33:31.689 --> 00:33:32.299 Oh, you know what? 00:33:32.299 --> 00:33:33.079 So we might need to... 00:33:33.179 --> 00:33:36.489 You might be going a little too fast. He needs to simmer down over there because 00:33:36.489 --> 00:33:37.654 it's going to get ludicrous. 00:33:40.864 --> 00:33:43.449 But mostly value. We just got a rocket ship and a thanks. 00:33:43.449 --> 00:33:46.227 Well, thank you very much. Going to put that towards the Texas budget. 00:33:47.748 --> 00:33:54.000 Greg the Lark came in again this week with a row of MegaDucks 22,222 sets. 00:33:54.413 --> 00:33:55.690 MegaDucks. 00:33:59.618 --> 00:34:02.608 Greg also just sent the value. No message on that one. So thanks, Greg. 00:34:03.241 --> 00:34:08.901 Thanks, Greg. Appreciate you. Get off my TTY42 also came in with a row of McDucks. 00:34:13.150 --> 00:34:17.335 Okay. In the pre-show, you celebrated more Home Assistant config removing from YAML. 00:34:17.869 --> 00:34:20.164 I can't reconcile that with the promotion of declarative systems, 00:34:20.164 --> 00:34:24.742 cough nicks. It seems like HA moving to click ops. Did we celebrate that? 00:34:26.310 --> 00:34:28.341 Hmm. I don't know if that's what you were trying to say. 00:34:28.568 --> 00:34:32.954 Yeah. I am a little torn on this particular issue myself, because this has recently 00:34:32.954 --> 00:34:36.393 just been changed with Modbus, which before had to be all done with YAML, 00:34:36.799 --> 00:34:40.317 which was a massive pain in the butt in the before time. 00:34:41.284 --> 00:34:44.934 And now it's funny that they're getting rid of YAML when it's easier than ever 00:34:44.934 --> 00:34:47.817 to generate YAML. That is, there is some irony there. 00:34:48.665 --> 00:34:52.824 Home Assistant EA continues, Home Assistant YAML is easier to grasp than Nix, 00:34:52.824 --> 00:34:57.069 and it's easy for an agent to write. What am I missing? I don't think you're missing anything. 00:34:57.615 --> 00:34:59.644 I suppose agents are at least very good with the API. 00:35:00.064 --> 00:35:06.595 There is that. I don't know. I don't think, and I really respect the Home Assistant team. 00:35:07.263 --> 00:35:10.564 I don't think they've wrapped their head around the fact that a lot of people 00:35:10.564 --> 00:35:13.114 are just going to use that as an agent API now. 00:35:13.462 --> 00:35:16.304 And they're not going to build dashboards. Like they're doing all this work 00:35:16.304 --> 00:35:18.484 around making dashboards really pretty and easy now. 00:35:19.703 --> 00:35:22.834 I have a Home Assistant instance. I've never even loaded the dashboard. 00:35:22.834 --> 00:35:23.929 I've never even logged into it. 00:35:24.289 --> 00:35:28.869 I just have the agent manage all of it. And if I want to know what the temperature is, I ask the agent. 00:35:28.973 --> 00:35:32.204 And if I want to know if the lights on or off, I ask the agent because it's, 00:35:32.204 --> 00:35:36.654 it's, it's, it's a chicken coop, you know, it's, it's like, I don't think they've 00:35:36.654 --> 00:35:38.824 wrapped their head around where this is going for them yet. 00:35:38.824 --> 00:35:44.074 And I, perhaps what you're witnessing here, get off my TTY is sort of a result 00:35:44.074 --> 00:35:47.264 of that because I kind of agree with you. Although I do like at the same time, 00:35:47.264 --> 00:35:49.041 like to see it easier for people to get mod bus working. 00:35:50.487 --> 00:35:51.299 I'm a complicated guy. 00:35:52.605 --> 00:35:57.126 Love Down Babylon comes in with 21,337 sets. 00:35:59.174 --> 00:35:59.902 It's Lurks! 00:35:59.902 --> 00:36:02.768 Hey, hey Chris. Sir Lurks a lot here. 00:36:03.000 --> 00:36:07.322 You, Adam Curry, and Dave Jones, and others inspired me to launch my own value-for-value 00:36:07.322 --> 00:36:09.622 podcast, Love Down Babylon. 00:36:10.002 --> 00:36:13.662 First episode, out now. A multifaceted adventure through personal healing, 00:36:13.662 --> 00:36:17.483 technology, platforms, big ideas, world problems, and hope for our future. 00:36:18.302 --> 00:36:23.182 Here is Elite Satoshi Boost as thanks for letting me sat-svertize my show. 00:36:24.382 --> 00:36:24.942 That's great. 00:36:25.962 --> 00:36:33.242 Oh, congrats, Lurks. Go check it out I think Love Down Babylon Go search for it on the index. 00:36:35.032 --> 00:36:37.876 Well Gene Bean is here With a row of ducks. 00:36:38.532 --> 00:36:40.698 Ooh Look at all those ducks. 00:36:41.336 --> 00:36:46.482 Gene Bean says bravo Tech Dev Looking forward to hearing the Texas Linux Fest. 00:36:46.482 --> 00:36:51.892 Coverage Thank you again to Tech Dev For becoming the elite sponsor Of our trip 00:36:51.892 --> 00:36:54.007 to Texas Linux Fest That was amazing. 00:36:55.934 --> 00:36:58.425 Geez Gene is here with another row of ducks. 00:37:01.333 --> 00:37:05.913 You mentioned Discord, and it reminded me, I'd like to get your take on Armada. 00:37:06.308 --> 00:37:12.328 The headline of their website is, Encrypted Open Source Discord Alternative. What do you think? 00:37:13.268 --> 00:37:14.740 This is one I don't think I've seen before, actually. 00:37:14.840 --> 00:37:15.680 I don't think I have. 00:37:15.680 --> 00:37:19.680 They have a web client. I like that. Zap Store. Google Play. Okay. 00:37:20.420 --> 00:37:21.517 Voice video calls. 00:37:21.674 --> 00:37:22.100 Lots of pink. 00:37:22.700 --> 00:37:23.970 Animated Jeff support. 00:37:23.970 --> 00:37:27.340 You know, it's a little frustrating that the UI already looks better than Element. 00:37:28.791 --> 00:37:31.066 Like they've already surpassed Element in the UI. 00:37:32.187 --> 00:37:36.087 One of their top features here that they're promoting is unbannable communities. 00:37:37.928 --> 00:37:38.770 Well, that is important. 00:37:38.770 --> 00:37:39.884 Self-hostable at every level. 00:37:40.209 --> 00:37:42.020 You don't want, because, you know, pretty soon those Canadians are going to 00:37:42.020 --> 00:37:43.895 get banned from communities, so you don't want that to happen. 00:37:44.226 --> 00:37:45.881 Self-hostable at every level, you say, huh? 00:37:46.293 --> 00:37:48.864 Interesting. Okay, should we put that on our list to check out? 00:37:49.213 --> 00:37:52.040 Oh, and it is interoperable with other Nostra apps. 00:37:52.400 --> 00:37:56.310 I feel like the only thing is, Gene, is we really seem to be at, 00:37:56.310 --> 00:37:57.762 like, a platform fatigue. 00:37:58.411 --> 00:38:01.280 Could you imagine us asking the audience? I like this cult soapbox. 00:38:01.534 --> 00:38:02.660 Could you imagine us asking the 00:38:02.660 --> 00:38:05.296 audience to sign up for another chat platform? Some of you would do it. 00:38:06.202 --> 00:38:09.270 It's a lot. And at the same time, I'd have to be asking myself, 00:38:09.270 --> 00:38:10.422 why don't we just go back to IRC? 00:38:11.479 --> 00:38:15.182 That would be that that's now it's competitor in my mind because IRC was so simple. 00:38:16.454 --> 00:38:17.010 It's easy. 00:38:17.010 --> 00:38:21.060 Right. There's a risk now that if we make any move, it will just default to IRC. 00:38:24.380 --> 00:38:27.141 I miss you, IRC. But thank you, Gene. I think that is worth looking at. 00:38:27.977 --> 00:38:32.325 Well, Gene sent a couple more messages. Really enjoyed the great Jellyfin information. 00:38:32.876 --> 00:38:37.724 And FYI, Stock Jellyfin is finally in the default Samsung Tizen store. 00:38:38.647 --> 00:38:41.990 He says he's looking forward to the tutorial on ARM that we promised. 00:38:41.990 --> 00:38:45.750 Did we promise something like that? Uh-oh. So he says, I tried it a while, 00:38:45.750 --> 00:38:50.656 but unsuccessful. So hopefully it shows what I missed. And last one here. 00:38:51.056 --> 00:38:53.830 Hold on a second. I feel like these last couple of booths, like you guys are 00:38:53.830 --> 00:38:57.010 like, I don't remember saying anything about the home assistant. 00:38:57.010 --> 00:38:59.470 Yeah, I don't remember saying anything about arm stuff. 00:38:59.470 --> 00:39:02.160 It's possible we've also forgotten a lot because that's usually true. 00:39:02.160 --> 00:39:03.240 It could be the B team. 00:39:03.880 --> 00:39:06.650 So you just need to give us more context so we can remember what we've promised. 00:39:06.650 --> 00:39:08.660 Yeah, it must have been Jeff's project. Okay, continue on. 00:39:08.660 --> 00:39:10.567 And provide proof too next time. Thanks. 00:39:10.811 --> 00:39:12.129 Yeah. Well, Jeff. 00:39:13.020 --> 00:39:18.000 Gene's last row of ducks here here's a pick for you Absorb is a new to me audio 00:39:18.000 --> 00:39:21.600 bookshelf client that works on both iOS and Android that seems to implement 00:39:21.600 --> 00:39:24.270 the entire API even the admin bits oh thank. 00:39:24.270 --> 00:39:26.571 You Gene thank you. 00:39:26.740 --> 00:39:32.850 Absorb the dev has a buy me a coffee link and I encourage anyone as impressed 00:39:32.850 --> 00:39:34.890 as I am to consider using that button. 00:39:35.697 --> 00:39:38.559 91% Dart 3% Kotlin. 00:39:39.626 --> 00:39:44.851 This looks really good. And I like the stats page, too. I am a huge audiobook 00:39:44.851 --> 00:39:46.191 shelf user. Use it every night. 00:39:47.026 --> 00:39:50.126 And use it on long drives. Love a new client. 00:39:50.956 --> 00:39:55.414 I'll give you a new client that I've been using this week. A little client called Listen. 00:39:56.697 --> 00:39:59.331 At least on Android. I don't know if it's available in other platforms. 00:39:59.331 --> 00:40:02.321 But I've been using that this week. Because same as you, Chris, 00:40:02.321 --> 00:40:06.331 it's your fault. Listen to audiobooks every night. And just a nicer interface. 00:40:06.331 --> 00:40:07.461 A little simpler. I like it. 00:40:07.461 --> 00:40:13.485 All right. Listen. Ironically, Google's original podcast app was called Listen. This is L-I-S-S-E-N. 00:40:13.944 --> 00:40:15.110 No T's around here. 00:40:15.958 --> 00:40:20.445 All right. Thank you, Gene. Appreciate you. That's some good boosting right there. 00:40:20.886 --> 00:40:24.503 Daja's here with 4,747 satushers. 00:40:26.529 --> 00:40:29.687 Plus one for Wizard. It also works with Audio Bookshelf. Oh. 00:40:32.421 --> 00:40:33.623 Did we promise that, too? 00:40:33.977 --> 00:40:36.471 No, no, but that's something I'm going to look into. Brent actually already 00:40:36.471 --> 00:40:39.491 used mine to create an account on my audiobook server when I recommended it. 00:40:39.491 --> 00:40:40.008 I sure did. 00:40:40.536 --> 00:40:44.401 ADHD is awesome. Super handy for when you want to invite people to all your 00:40:44.401 --> 00:40:49.341 platforms at once with a single invite code. It also does ROM. Yes, I have ROM. 00:40:49.341 --> 00:40:50.251 That's impressive. 00:40:50.251 --> 00:40:54.441 I love ROM. R-O-M-M. I want to talk about it on the show all the time, 00:40:54.441 --> 00:40:57.751 but I've done an episode on it, and we try not to overdo the gaming stuff, 00:40:57.751 --> 00:41:01.294 so I haven't mentioned it again, but that's my excuse. R-O-M-M. 00:41:01.845 --> 00:41:04.347 Love it. It's unbelievable what you can do in a web browser. 00:41:05.369 --> 00:41:06.936 Well, that is great. Thank you, Daja. 00:41:07.853 --> 00:41:10.936 Derivation Dingus boosts in with a double row of ducks. 00:41:13.810 --> 00:41:19.088 Plus one for Vicuña. I just set this up a few weeks ago, including an MCP server, 00:41:19.088 --> 00:41:21.270 and hooked up my personal assistant agent to it. 00:41:21.484 --> 00:41:24.698 It can display the same data as to-do lists, Kanban, Gantt charts, et cetera. 00:41:24.698 --> 00:41:25.158 Okay. 00:41:25.158 --> 00:41:28.578 I really like it. If you guys try it, I'd love to hear how you end up using it. 00:41:28.706 --> 00:41:30.528 I might now that I got the plus one on that. 00:41:30.528 --> 00:41:32.178 Mm-hmm, that's some good signal there. 00:41:32.178 --> 00:41:35.118 Is that a promise you're giving out there? We gotta, we gotta write these down. I should be careful. 00:41:35.118 --> 00:41:36.238 I want to try it as well, so. 00:41:36.558 --> 00:41:38.383 I do too, I do too. All right, Bren, get on it. 00:41:39.698 --> 00:41:41.308 And I think we got a little more signal here. 00:41:41.308 --> 00:41:41.598 Ooh, okay. 00:41:42.098 --> 00:41:45.798 I thought Herder was pretty nice, but I love Zellige and really miss some of 00:41:45.798 --> 00:41:47.078 its features when using Herder. 00:41:47.418 --> 00:41:51.758 But then I found ZJ-Radar. It's extremely similar to Herder, 00:41:51.758 --> 00:41:53.178 but it's just a Zellige plugin. 00:41:53.475 --> 00:41:57.538 I set up the alias Zerder, which launches Zellige straight into the Radar profile. 00:41:57.858 --> 00:42:00.911 I honestly haven't launched Herder since, since I got it installed. 00:42:01.143 --> 00:42:01.858 Highly recommend. 00:42:02.298 --> 00:42:07.407 There are people listening that have no idea what any of those words mean, but I am very grateful. 00:42:07.761 --> 00:42:11.429 I've been wondering about this because I have seen this Zellige plugin going around. 00:42:11.766 --> 00:42:15.338 It sets up a little sidebar, and then you have, like, it's aware of what your 00:42:15.338 --> 00:42:20.318 AI agent, you know, whatever you're using, your open codes, your clods, 00:42:20.318 --> 00:42:23.719 whatever, and it's kind of a context aware of when they need your help and stuff like that. 00:42:24.206 --> 00:42:26.248 But it gives that capability to Zellige. 00:42:26.248 --> 00:42:29.068 Yeah, to the terminal multiplexer maybe you already use and love. 00:42:29.068 --> 00:42:33.138 Yeah. Interesting, because I agree. There's things about Herder I like, 00:42:33.138 --> 00:42:36.262 but there's things about Herder that feel like it's not designed for a guy like me. 00:42:36.449 --> 00:42:39.268 Interesting to see, too, because I have used a lot of Zellige, 00:42:39.268 --> 00:42:42.658 but I have not yet tried a Zellige plug-in. So kind of curious on that experience. 00:42:44.138 --> 00:42:44.798 Fascinating. 00:42:44.798 --> 00:42:45.578 Thank you, Dingus. 00:42:45.793 --> 00:42:46.356 Appreciate you. 00:42:47.052 --> 00:42:49.757 Well, we got a digital farmer here with a row of ducks. 00:42:51.853 --> 00:42:56.478 Just has boosting from my new LND node running Nix OS. 00:42:57.101 --> 00:42:57.728 We got it. 00:42:57.728 --> 00:42:59.008 That's exciting. Nice work. 00:42:59.008 --> 00:43:04.142 Well done. Keep on farming. Thank you, sir. MRAM comes in with one, nope. 00:43:04.438 --> 00:43:08.178 Well, I guess one, one, one, one, one sats. There you go. That's sort of what 00:43:08.178 --> 00:43:09.634 I was trying to. Binary boost? 00:43:10.777 --> 00:43:12.095 Yeah. Okay, there you go. 00:43:14.313 --> 00:43:16.680 MRAM writes, hi, I listened to episode 331. 00:43:17.498 --> 00:43:19.478 Whoa, that is a time travel and boost. 00:43:19.478 --> 00:43:22.880 You are all so exalted over your Arch server. I enjoyed it big time. 00:43:23.275 --> 00:43:25.168 Wow, we've had the Arch server going since that long. 00:43:25.168 --> 00:43:26.078 Oh my goodness, no way. 00:43:26.218 --> 00:43:27.001 That's crazy. 00:43:27.460 --> 00:43:28.688 You can't use Arch as a server, though. 00:43:28.688 --> 00:43:29.368 No, I can't. 00:43:29.368 --> 00:43:31.888 I like the AI stuff, too. Wish I understood it better, though. 00:43:31.888 --> 00:43:34.198 Keep up the good work. Well, keep on listening, MRAM. You just might. 00:43:34.198 --> 00:43:35.148 Thank you for the boost. 00:43:35.148 --> 00:43:38.238 Wow, I love time travel boost. I had no, dang. 00:43:38.638 --> 00:43:39.758 That is a typo, though, right? 00:43:39.758 --> 00:43:43.898 That little server through every summer, every winter, out in that garage. 00:43:43.898 --> 00:43:45.298 Cottonwood disaster. 00:43:45.298 --> 00:43:51.074 Cottonwood, cats. Rats, probably. I don't know. Jeez. That, I am... 00:43:52.230 --> 00:43:55.654 I just feel... I'm so proud of that little server, guys. I'm so proud of it. 00:43:56.496 --> 00:44:00.107 A dude trying stuff boosts in 11,670, 00:44:03.821 --> 00:44:05.908 cents. Woo! See you at Texas Linux. 00:44:05.908 --> 00:44:06.908 Ah, yes. 00:44:06.908 --> 00:44:08.728 Had to work the dates into this boost. 00:44:08.728 --> 00:44:15.310 Oh. Clever. November 6th and 7th. Yep. Awesome. I'm a dude. Looking forward to it. 00:44:15.444 --> 00:44:18.502 Well, Pixie's here with a $5 Fiat boost. 00:44:22.659 --> 00:44:28.296 Putting some money up to get a chance to read Chris's Nix or SOPS config for the media stack. 00:44:28.749 --> 00:44:33.567 Plus, Jellar experience would be appreciated. I was just looking at that project. 00:44:34.037 --> 00:44:36.445 I completely blanked on that. I will try to get a version of that. 00:44:36.505 --> 00:44:37.855 Is this another promise you made? 00:44:37.855 --> 00:44:41.455 That's a good, I think so. Oh my gosh. This is why we're keeping us honest. 00:44:41.455 --> 00:44:44.142 Keeping us transparent and honest. 00:44:44.865 --> 00:44:47.712 We intend to be. We're just, you know, really fallible. 00:44:47.887 --> 00:44:50.965 Well, I got really excited with storage this week. I will be honest. 00:44:51.705 --> 00:44:55.345 Once I saw that 1.0, I'm like, can I build it? Can I build it? 00:44:55.345 --> 00:44:57.265 I got a little carried away. Thank you, Pixie, though. 00:44:58.254 --> 00:45:01.275 I need to export all that anyway, so as I sort of just decommission that test 00:45:01.275 --> 00:45:04.773 box, I'll try to capture that. And then I'll put a link in the show notes when we got it. 00:45:05.789 --> 00:45:10.189 Sam H. comes in with a free member boost, a time travel boost from 682. 00:45:10.532 --> 00:45:14.723 I also use Pi with my framework desktop. A simple Pi extension written by Pi 00:45:14.949 --> 00:45:19.100 helps select models from LlamaSwap and get the right reasoning level options. 00:45:19.408 --> 00:45:23.547 Prompt processing is slow on this GPU, so the smaller the system prompt of Pi 00:45:23.860 --> 00:45:25.655 helps things get started faster. 00:45:25.655 --> 00:45:27.198 Very nice. That makes a lot of sense. 00:45:28.045 --> 00:45:31.645 Another case where a little bit of a harness can be really helpful for that kind of stuff. 00:45:33.670 --> 00:45:38.125 Anonymous comes in with a free member boost just to say, great job, guys. 00:45:38.465 --> 00:45:42.155 I learned something new on every episode. And this one was for 684. 00:45:42.155 --> 00:45:43.525 I hope that is true. You're ready for this jelly. 00:45:43.525 --> 00:45:45.225 We definitely try, so I hope that is true. 00:45:45.225 --> 00:45:46.265 That is one of our goals for sure. 00:45:46.265 --> 00:45:48.565 Going for the value. Thank you, everybody who supported the show, 00:45:48.565 --> 00:45:52.155 Members, those of you who boosted below the 2,000 sat cutoff, 00:45:52.155 --> 00:45:56.315 Mayhem came in at 1,999 sats with a Zubbamoof. 00:45:57.597 --> 00:46:01.017 When you bring it all together, we had 16 of your stream sats, 00:46:01.284 --> 00:46:06.578 and collectively, you all stacked 29,371 satoshis. 00:46:07.594 --> 00:46:10.695 Thank you very much, sat streamers. When you bring it together with our Fiat 00:46:10.695 --> 00:46:15.221 boost and our regular boost and average it all at the current sat market value, 00:46:15.581 --> 00:46:21.479 our total this week was 254,069 Satoshis. 00:46:24.678 --> 00:46:27.905 Not too bad for an average week, but we are trying to get that up a little bit 00:46:27.905 --> 00:46:30.790 on the average to put that budget towards our Texas trip. 00:46:31.202 --> 00:46:33.625 Anything there would help. Boost.Jupiter Broadcasting for that, 00:46:33.625 --> 00:46:36.989 but we are grateful. And, of course, thank you to our members who do put their support on autopilot. 00:46:37.528 --> 00:46:39.725 All right, yeah, so thank you, everybody. We really do appreciate it. 00:46:40.085 --> 00:46:42.892 Of course, if you're a member, too, not only do you support the show automatically, 00:46:43.119 --> 00:46:45.885 but you do get a free member boost, so you can always send in that. 00:46:45.885 --> 00:46:48.673 And we like it. Boost.JupiterBroadcasting.com for that. 00:46:49.034 --> 00:46:51.454 Thank you. And we appreciate everybody who supports the show. 00:46:51.860 --> 00:46:54.985 we are still sort of struggling in the sponsorship department, 00:46:54.985 --> 00:46:58.763 still relying on the dynamic ads and all of that and so it does make a big difference, 00:47:00.458 --> 00:47:01.196 you know what I'm realizing, 00:47:02.292 --> 00:47:03.522 I didn't put my picks in the doc. 00:47:03.522 --> 00:47:04.302 I was wondering. 00:47:05.962 --> 00:47:09.275 I wonder if I could retrofix that. I wonder if I could retrofix that. 00:47:09.664 --> 00:47:11.162 Because I really liked those picks. 00:47:12.082 --> 00:47:14.192 I was going to say I got two backup picks. 00:47:14.192 --> 00:47:14.422 You do? 00:47:14.762 --> 00:47:14.987 Yeah. 00:47:15.550 --> 00:47:18.972 Gosh, mine were really good. And I never, you know, it's because I don't actually 00:47:18.972 --> 00:47:21.032 write in the web browser. I write. 00:47:21.032 --> 00:47:22.302 Yeah, you have a working document. 00:47:23.162 --> 00:47:25.430 All right, well, what are your backup picks? And then I'll save mine for next week. 00:47:25.570 --> 00:47:28.482 Well, I was just trying to, I wasn't sure if we had picks. So I was just trying 00:47:28.482 --> 00:47:30.622 to see what had been, you know, put in our pick. 00:47:30.622 --> 00:47:33.411 Yeah. Yeah, there's a few options. I could probably find it in there. 00:47:33.968 --> 00:47:36.882 This is my bad. I didn't put it in there. 00:47:37.039 --> 00:47:41.329 Okay, well, someone linked in our chat room, one of our chat rooms earlier today, Flakelit. 00:47:42.043 --> 00:47:47.582 Run systemd services from Nix Flakes and update them independently of the host system. 00:47:47.582 --> 00:47:51.502 That is such a West pick. That's a strong West pick. 00:47:51.502 --> 00:47:54.392 Normally, a Nix OS host has to be rebuilt to update one of its services. 00:47:54.392 --> 00:47:59.072 Flakelit takes the same approach as how the virtualization OCI container stuff 00:47:59.072 --> 00:48:02.502 does, but with flakes instead of container images. The host only declares which 00:48:02.502 --> 00:48:04.085 flake to run and which settings to pass. 00:48:04.305 --> 00:48:06.622 The machine itself resolves the flake, evaluates and builds it, 00:48:06.622 --> 00:48:10.122 and switches the system to units. There's no images and there's no registry. 00:48:10.122 --> 00:48:12.188 The units run straight out of the host's Nick store. 00:48:12.972 --> 00:48:16.912 Well, that's not too bad. Now what we need is a pick that checks our show notes 00:48:16.912 --> 00:48:19.706 to find out if we didn't put our picks in there. 00:48:20.118 --> 00:48:22.237 You got a sneaky pick you want to throw in, Brent? 00:48:22.521 --> 00:48:27.165 Well, I'm going to throw an opportunity here at Jeff Lee seems to have a pick. 00:48:27.635 --> 00:48:29.545 Oh, PJ Pick. All right. 00:48:31.088 --> 00:48:35.761 A sneaky little pick it's more for the android side of things but it involves 00:48:36.017 --> 00:48:40.150 the good old ai stuff there's a android app called chompus, 00:48:40.684 --> 00:48:46.396 it is a calorie counting slash health and food counting application, 00:48:47.058 --> 00:48:52.793 and it can use your local ai it can use whatever ai you point at it can use dang near anything, 00:48:53.530 --> 00:48:58.691 and it has a nice big registry built in for various foods as well so you can, 00:48:59.341 --> 00:49:03.252 do things like take a photo of the plate that's in front of your face with some 00:49:03.252 --> 00:49:05.802 kind of idea like a hand or a coin, 00:49:06.301 --> 00:49:09.452 and describe what you're going to eat and it does a pretty dang good job at 00:49:09.452 --> 00:49:13.587 calling your ai and saying okay you're consuming this many calories you're consuming 00:49:13.970 --> 00:49:18.042 this uh you know this much fat this much protein etc etc etc knock it. 00:49:18.042 --> 00:49:22.072 Off i would have i would have mine yell at me about it you know better stop it. 00:49:22.648 --> 00:49:29.672 There is a uh there is a coach thing as well so you can kind of chat with your AI and do that as well. 00:49:29.672 --> 00:49:33.442 And I don't do, I don't try it. I don't use it, but I have tried like, 00:49:33.442 --> 00:49:35.402 Hey, uh, what did last week look like? 00:49:35.402 --> 00:49:38.582 And it did, it did pull in that data and give me information about the last 00:49:38.582 --> 00:49:41.612 week of food, but I've been using it a lot with my local, uh, 00:49:41.972 --> 00:49:46.042 with my local hosted AI stuff. I think I'm using Gemma for specifically, 00:49:46.042 --> 00:49:47.330 and it's been working pretty good. 00:49:48.032 --> 00:49:51.922 All right. We'll put a link to that in the notes and then I'll toss in one last 00:49:51.922 --> 00:49:55.544 little extra bony pick here. It's called FF dash. Okay. 00:49:56.280 --> 00:50:02.548 It's a Rust app, and it's a terminal UI for batch, AV1, and VP9 video encoding. 00:50:02.548 --> 00:50:05.173 I am becoming a big fan of AV1. 00:50:05.876 --> 00:50:09.778 And so it'll use hardware acceleration if you got it. The TUI gives you nice 00:50:09.778 --> 00:50:13.398 real-time progress monitoring, full control over the settings, 00:50:13.398 --> 00:50:18.088 and it's made to work as a visible encoding dashboard over SSH. 00:50:18.908 --> 00:50:22.448 Yeah, this looks really nice. I haven't tried it yet, but it's in the queue to try for sure. 00:50:23.028 --> 00:50:29.068 I love the look of it. And for me, this was a hard requirement that it supported, 00:50:29.648 --> 00:50:33.988 QuickSync, and it does. It supports QuickSync, and it'll also support the NVIDIA 00:50:33.988 --> 00:50:36.008 stuff, if you got it, or the AMD. 00:50:36.432 --> 00:50:38.488 Nice. Yeah. Doesn't discriminate on platform. 00:50:38.488 --> 00:50:43.418 You got your VA API and your NVEX as well as the QSVs, Wes, which is what you 00:50:43.418 --> 00:50:50.184 want to see in there. So again, it's called FF-Dash, and it is MIT licensed, 00:50:50.294 --> 00:50:51.885 and it is written in Rust. 00:50:52.216 --> 00:50:55.458 So there you go. Not the picks I intended, but they were bangers and they're 00:50:55.458 --> 00:50:58.528 worth saving. So I'll save them for you. And instead, you got a bunch of nice 00:50:58.908 --> 00:51:00.548 surprise picks that we didn't even know. 00:51:00.548 --> 00:51:02.787 Yeah, so stay tuned next week for our real picks. 00:51:02.908 --> 00:51:05.408 When's the last time we've even left something out like that in the talk? 00:51:05.408 --> 00:51:06.358 It doesn't happen often. 00:51:06.358 --> 00:51:09.753 No, it does not. I'm going to blame Brent. He's our QC guy. 00:51:10.608 --> 00:51:15.408 Brent's QC guy. That's all right. Now, I will blame you out there for not visiting 00:51:15.408 --> 00:51:20.085 us on a Sunday and making it a Tuesday because you're missing out. It's a life experience. 00:51:21.020 --> 00:51:24.114 Well, okay. Maybe I'm overselling it a little bit, but it is a fun experience. 00:51:24.433 --> 00:51:28.268 You can make it a Tuesday on a Sunday over at jblive.tv, 10 a.m. 00:51:28.268 --> 00:51:32.013 Pacific, 1 p.m. Eastern. You know Batman. 00:51:34.085 --> 00:51:37.478 I mean, we got all kinds of ways to experience it, too. We got audio. 00:51:37.478 --> 00:51:40.638 We got video. We got, you know, we got the whole Mumble experience. 00:51:40.638 --> 00:51:43.258 You can just be in the chat room if you want. We're on the, like, 00:51:43.258 --> 00:51:45.138 proprietary platforms, if that's more your speed. 00:51:45.138 --> 00:51:51.111 That's true. Got them over on the tubes. And then we have a hand-crafted RSS feed. 00:51:51.453 --> 00:51:54.238 Beautifully designed, full of extra stuff, like? 00:51:54.658 --> 00:51:56.028 JSON cloud chapters. 00:51:56.028 --> 00:51:56.218 Boom. 00:51:57.658 --> 00:52:01.118 SVT, SRT, VTT. I made up a fake file format there for a second. 00:52:01.118 --> 00:52:01.778 Transcripts, though. 00:52:01.798 --> 00:52:02.658 That's right, transcripts. 00:52:02.658 --> 00:52:04.198 Transcripts. That's good. You like those? 00:52:04.638 --> 00:52:06.732 MPEG layer 4 and layer 3. 00:52:06.906 --> 00:52:09.768 If we got, if, you know what? Sometimes we might be showing a visual of what 00:52:09.768 --> 00:52:11.818 we're talking about, and you don't even know it because we're so good at the 00:52:11.818 --> 00:52:14.859 audio show. But it might be in there if you watch the video. A little extra. 00:52:15.010 --> 00:52:19.753 Yeah. And it's all, of course, linked over at linuxunplugged.com. 00:52:20.113 --> 00:52:25.301 And this was episode 685, so you could just go to linuxunplugged.com slash 685. 00:52:25.667 --> 00:52:28.698 Then when you're all done, head on over to Jupyter Broadcasting. 00:52:28.698 --> 00:52:32.818 Check out the launch for my last quest this week in Bitcoin and others coming 00:52:32.818 --> 00:52:35.030 soon. over there, jupiterbroadcasting.com. 00:52:35.378 --> 00:52:38.238 But that's it for us. Thank you so much for joining us on this week's episode 00:52:38.238 --> 00:52:39.848 of your Unplugged program. 00:52:40.307 --> 00:52:44.336 And I hope to see you next Tuesday, which is what we call Sunday. 00:52:45.247 --> 00:52:46.878 It's a Tuesday on a Sunday. 00:52:47.250 --> 00:52:47.911 See you next.