WEBVTT 00:00:11.389 --> 00:00:15.897 Hello, friends, and welcome back to your weekly Linux talk show. My name is Chris. 00:00:15.897 --> 00:00:16.817 My name is Wes. 00:00:16.817 --> 00:00:17.816 And my name is Brent. 00:00:18.402 --> 00:00:23.407 Hello, gentlemen. Coming up on the show today, just how smart can your security 00:00:23.407 --> 00:00:28.323 cameras get, even the cheap ones, if you kept everything local and didn't rely on the cloud? 00:00:28.729 --> 00:00:32.572 I took my Steam Deck on a little bit of a security duty tour, 00:00:32.938 --> 00:00:35.660 teaching it how to look at what happened around the property and the farm, 00:00:36.084 --> 00:00:37.930 and then report back all locally. 00:00:38.203 --> 00:00:40.497 Tell you about that. Then we're going to run it out with some great picks and 00:00:40.497 --> 00:00:42.144 boosts, some feedback, and a lot more. 00:00:42.632 --> 00:00:44.707 It's going to be a lot of fun. So before we get to all that, 00:00:44.707 --> 00:00:48.930 you know what we've got to do. We have to say time appropes to our virtual lug. Hello, Mumble Room. 00:00:49.447 --> 00:00:52.617 Hello, Chris. Hey, Chris. Hello, Brent. 00:00:53.117 --> 00:00:53.435 Aw. 00:00:53.580 --> 00:00:56.047 Hello, hello, hello. Hello from a lot. 00:00:56.047 --> 00:00:56.597 They're still going. 00:00:56.757 --> 00:00:56.977 Hello, everybody. 00:00:57.057 --> 00:00:57.517 They're still going. 00:00:58.131 --> 00:01:00.687 That's a good crew we got in there today. And so hello up there in the quiet 00:01:00.687 --> 00:01:02.141 listening and everybody watching live. 00:01:02.745 --> 00:01:06.217 Let's give it a live vibe. We appreciate that. And go say good morning to our 00:01:06.217 --> 00:01:07.911 friends over at Defined Networking. 00:01:09.368 --> 00:01:13.447 Defined.net slash unplugged. Go meet Manage Nebula from Define Networking, 00:01:13.447 --> 00:01:17.106 a decentralized VPN built on the open-source Nebula platform that we love, 00:01:17.512 --> 00:01:20.723 optimized for speed, simplicity, and industry-leading security. 00:01:21.048 --> 00:01:24.455 When it comes to your core infrastructure, I want to own my network. 00:01:24.728 --> 00:01:27.021 That's why I love Manage Nebula from Define Networking. 00:01:27.427 --> 00:01:30.747 It creates a fast, decentralized mesh where my machines connect directly instead 00:01:30.747 --> 00:01:33.267 of routing everything through a central server or control plane. 00:01:33.737 --> 00:01:36.489 I can run my own lighthouses, use their managed lighthouses, 00:01:36.814 --> 00:01:39.287 real control, and you don't sacrifice performance. 00:01:39.664 --> 00:01:42.300 Managed Nebula makes it super easy to deploy and get started. 00:01:42.660 --> 00:01:45.591 Get started with 100 hosts for free, no credit card required. 00:01:45.823 --> 00:01:49.469 Go to define.net slash unplugged and redefine your VPN experience. 00:01:49.753 --> 00:01:51.239 Define.net slash unplugged. 00:01:51.959 --> 00:01:56.156 Thank you to Defined. Keep an eye out on their blog, too. More to come. 00:01:58.354 --> 00:02:01.358 Well, we're letting you know ahead of time, Clanker Therapy 3, 00:02:01.358 --> 00:02:06.588 this Friday, October 16th, 12 p.m. Pacific, 3 p.m. Eastern, 1900 UTC, 00:02:06.588 --> 00:02:09.285 7 p.m. Over there in the UTCs. 00:02:09.668 --> 00:02:11.018 You're so thoughtful with your time zones. 00:02:11.990 --> 00:02:17.812 So for this, what have you been building? Tell us what your setup is. Ask us any questions. 00:02:18.126 --> 00:02:21.488 We'll play your uplink. So go to uplink.jupiterbroadcasting.com. 00:02:21.488 --> 00:02:23.855 Choose what have you been building, which I think is the default. 00:02:24.343 --> 00:02:26.818 And leave us a voice note and we'll play those and answer them. 00:02:26.818 --> 00:02:30.264 Plus, we'll cover some new projects. I have got some really fun stuff to share. 00:02:30.903 --> 00:02:35.738 And we may even have a random Brent show up and tell us about his current workflow, 00:02:35.738 --> 00:02:37.358 which both Wes and I have been dying to hear about. 00:02:38.223 --> 00:02:41.478 So it's going to be a good clanker therapy. Details are at meetup.com slash 00:02:41.478 --> 00:02:43.598 Jupyter Broadcasting. Meetup page not required for the stream, 00:02:43.598 --> 00:02:44.539 just for your information. 00:02:45.392 --> 00:02:49.148 It'll be this Friday. And we have the details at jupyterbroadcasting.com slash calendar. 00:02:49.908 --> 00:02:54.308 The thing to take away is uplink.jupyterbroadcasting.com. Leave us your voice 00:02:54.308 --> 00:02:56.750 notes so we can answer those on Friday's stream. 00:02:57.778 --> 00:03:01.648 And then last but not least, Brent wanted to make sure everybody is aware Texas 00:03:01.648 --> 00:03:03.578 Linux Fest is just around the corner. 00:03:03.578 --> 00:03:04.384 Coming right up. 00:03:06.096 --> 00:03:10.537 Texas Linux Festival 2026, Brent Lee. He's going to be there. We're going to be there. 00:03:10.949 --> 00:03:14.494 Looking forward to it. I've been on like my slowly ramp up the meat diet. 00:03:14.494 --> 00:03:19.093 So in preparation for, you know, what is usually an overload. So thank you everyone. 00:03:20.092 --> 00:03:24.564 Yes, I'm very much looking forward to it. We are in the early wrapping our head 00:03:24.564 --> 00:03:27.624 around meetup phase, but I think we'll probably have a meetup announced pretty 00:03:27.624 --> 00:03:29.299 soon for when, you know, we're all down there. 00:03:30.042 --> 00:03:32.684 And again, just super thankful for TechDev for making it possible. 00:03:32.684 --> 00:03:33.194 No kidding. 00:03:33.194 --> 00:03:35.704 We've had some more support come in this week via Boost. We'll talk about that 00:03:35.704 --> 00:03:38.744 later in the show, too. But November 6th through the 7th in Austin, 00:03:38.744 --> 00:03:44.955 Texas, as we record, 25 days, 13 hours, and 48 minutes until it's time. 00:03:45.495 --> 00:03:50.024 And then we got to go, boys. We got to go. So we're going to be flying this 00:03:50.024 --> 00:03:52.404 time. There won't be a race, but it's still going to be a little bit. 00:03:52.424 --> 00:03:56.454 Well, I mean, there still is a race. Who gets there first? Wait, 00:03:56.454 --> 00:03:58.316 you booked my flight. Oh, no. 00:03:58.456 --> 00:04:03.184 I don't know. You might beat us. The wife booked him, so I don't actually know. 00:04:03.184 --> 00:04:04.424 I don't even know what my flight is. 00:04:04.424 --> 00:04:05.484 I paid her off, so it's all good. 00:04:08.963 --> 00:04:13.264 I wanted to talk about this for a long time. We've maybe touched on it briefly. 00:04:13.711 --> 00:04:19.621 I am a big fan of the Frigate NVR project, an open source network video recorder for IP cameras. 00:04:20.242 --> 00:04:24.414 And it's really easy to get set up, and you can use it with all types of different 00:04:24.414 --> 00:04:29.855 cameras if you use a go-between, like, go-to RTC. So I've got multi-vendor cameras, 00:04:30.116 --> 00:04:33.680 Wi-Fi, Ethernet, all different kinds that come into Frigate. 00:04:34.470 --> 00:04:39.485 And, uh, it talks to your cameras over RTSP or O N I V F or O N V I F. 00:04:40.681 --> 00:04:45.637 And it's really great. It gives you a bird's eye dashboard where you can see 00:04:45.637 --> 00:04:46.951 what's going on around your home. 00:04:47.340 --> 00:04:49.429 You can have a record certain events and play them back. 00:04:49.987 --> 00:04:53.427 It can communicate with Home Assistant. So it can tag people and pass that along 00:04:53.427 --> 00:04:57.091 to Home Assistant. So Home Assistant can take actions like alerting and automations. 00:04:58.031 --> 00:05:01.247 It has some really great built-in support for detecting objects, 00:05:01.897 --> 00:05:05.781 which is really cool. It supports zones and masks. You can zone out certain things. 00:05:06.396 --> 00:05:09.777 And it has a great UI for going back and finding the things that happened. 00:05:09.777 --> 00:05:11.597 if you're looking for like a particular incident. 00:05:11.754 --> 00:05:15.647 It seemed just like a great open source project too. I think it started in 2019, 00:05:15.647 --> 00:05:18.830 but it's now at the point, right, where there's a person who didn't start it 00:05:19.138 --> 00:05:22.617 who has more commits than the founder, though both are still very active. 00:05:22.617 --> 00:05:25.177 So it's just one of the, you know, like it's grown into a community of folks 00:05:25.177 --> 00:05:28.907 who obviously use it, but are also there maintaining it and adding new features 00:05:28.907 --> 00:05:30.507 and sharing data and all that. 00:05:30.507 --> 00:05:33.377 And I imagine, you know, there's a lot of us out there, you would like some 00:05:33.377 --> 00:05:37.540 home security. You would like maybe monitoring what's going on with your pets. 00:05:38.115 --> 00:05:39.617 you know like i have i have uh this 00:05:39.617 --> 00:05:42.317 set up for my chicken coop for example because i just want to know and, 00:05:43.235 --> 00:05:47.817 it actually has been really great uh there has been times where we can't find 00:05:47.817 --> 00:05:50.368 a chicken and so you can go back to the frigate 00:05:50.733 --> 00:05:54.017 and and pull a section of video to find out what was the chicken in the hen 00:05:54.017 --> 00:05:58.277 house last night did the chicken make it in last night oh yep there's blue she's 00:05:58.277 --> 00:06:01.417 roosting okay so she's just out and about right now she's not she's not that 00:06:01.417 --> 00:06:03.917 lost you know just sort of peace of mind and then you can, 00:06:04.474 --> 00:06:06.997 there's an api here right so if you have an agent sitting in front of that you 00:06:06.997 --> 00:06:10.107 can say, go get me 30 minutes starting at 1 p.m. or something like that. 00:06:10.107 --> 00:06:11.225 Give me an active chicken count. 00:06:11.364 --> 00:06:14.517 Yeah, that kind of thing. So Frigate is really great, and there's a lot you 00:06:14.517 --> 00:06:16.130 can do with it out of the box. 00:06:16.595 --> 00:06:19.307 And I just think we probably haven't talked about it much because it is kind 00:06:19.307 --> 00:06:22.997 of a niche use case, but anybody that has some IP cameras that doesn't want 00:06:22.997 --> 00:06:28.698 to rely on the cloud or pay for a third party or have a third party get access to that information, 00:06:29.168 --> 00:06:32.077 or if you already have Home Assistant and you want to integrate with that and 00:06:32.442 --> 00:06:35.589 add some automations, you can also do MQTT support, 00:06:36.668 --> 00:06:37.724 It's really pretty powerful. 00:06:37.724 --> 00:06:41.094 It's got a very nice architecture too, right? Like it really prioritizes latency. 00:06:41.094 --> 00:06:45.024 There's ring buffers and shared memory going on to keep things efficient and 00:06:45.024 --> 00:06:48.324 trying to, they do some optimization around memory management to prevent things 00:06:48.324 --> 00:06:50.708 like accidental out of memory things kicking in. 00:06:50.935 --> 00:06:53.855 It's quite impressive. And then of course, like, you know, there's like the 00:06:54.127 --> 00:06:58.266 actual data channel versus like the metadata events that get written out. 00:06:58.679 --> 00:07:03.224 Yeah. And if you get it with something like a USB Coral accelerator or another 00:07:03.224 --> 00:07:04.176 type of Coral accelerator, 00:07:05.012 --> 00:07:08.674 it's pretty impressive the hardware you can run it on i run it on my o droid 00:07:08.674 --> 00:07:15.094 h3 at home that's doing 15 other things including jellyfin and media management 00:07:15.094 --> 00:07:19.751 and all kinds of other activities and frig it's just one of the things it does. 00:07:20.215 --> 00:07:21.804 Yeah it's not totally destroying your system. 00:07:21.804 --> 00:07:25.154 It's yeah so it's not like even a dedicated system it's just and it's not a 00:07:25.154 --> 00:07:29.938 particularly powerful box i do have a coral accelerator which you know does the detection lift. 00:07:30.194 --> 00:07:33.134 Right and that's where a lot of that architecture comes around right is making 00:07:33.134 --> 00:07:36.481 it's like how do you make it really cheap to do the quick evaluation and then, 00:07:37.067 --> 00:07:40.514 for the things that actually trigger the first layer you can then do more heavier 00:07:40.514 --> 00:07:43.110 filtering so you don't have to heavily filter every single frame. 00:07:43.773 --> 00:07:47.548 The Coral thing, I think I just have to mention, I really think this went from 00:07:47.548 --> 00:07:53.648 useful to actually real-time event-driven, like notifications about somebody 00:07:53.648 --> 00:07:57.680 is in the driveway with this license plate or stuff you can actually act on right away. 00:07:58.202 --> 00:08:02.098 So adding a Coral, I think, really made it much, much more useful. 00:08:02.220 --> 00:08:06.298 And then you essentially get cheap motion watching and cheap event watching 00:08:06.298 --> 00:08:10.295 where the CPU doesn't get that busy, and it offloads all of that to that processing device. 00:08:10.741 --> 00:08:16.218 Coral runs a quantized neural net and can do like bounding boxes like this is 00:08:16.218 --> 00:08:18.009 a dog. And it puts a little box around the dog. 00:08:18.416 --> 00:08:21.618 It can label. So it'll say this is 80% confidence that this is a dog. 00:08:21.618 --> 00:08:25.308 So you'll get an image with a bounding box around the dog. This is 80% confidence 00:08:25.308 --> 00:08:26.409 that I've identified a dog here. 00:08:27.458 --> 00:08:32.028 And that is really useful because all of that is happening locally within milliseconds. 00:08:32.168 --> 00:08:35.808 So you can get a real alert sent to your phone through Home Assistant as it's 00:08:35.808 --> 00:08:38.108 happening. You played around with the Coral last night. 00:08:38.108 --> 00:08:41.518 Yeah, I was, because it's a neat little bit of technology. 00:08:41.518 --> 00:08:45.478 There are limitations. You can't really do anything that needs attention, 00:08:45.478 --> 00:08:49.178 so LLMs aren't going to work there. But there's a bunch of audio applications, 00:08:49.178 --> 00:08:53.798 because that's even lower bandwidth a lot of the times than doing something like frame processing. 00:08:55.078 --> 00:09:01.058 One limitation or concern I had was that it uses a compiler from Google that 00:09:01.058 --> 00:09:05.516 hasn't really been developed much since 2021 and is closed source. 00:09:05.789 --> 00:09:06.318 Interesting. 00:09:06.318 --> 00:09:10.208 So I spent a while having OpenCode bang against that. 00:09:10.208 --> 00:09:10.485 Yeah. 00:09:10.688 --> 00:09:15.048 And it was able to build a little compiler for itself that seems to be basically 00:09:15.048 --> 00:09:16.918 byte identical to what Google's been doing. 00:09:16.918 --> 00:09:17.528 No kidding. 00:09:17.528 --> 00:09:21.821 Mm-hmm. Including running, building a YOLO model. 00:09:22.240 --> 00:09:22.868 No. Yeah. 00:09:24.684 --> 00:09:25.628 That runs on the Coral? 00:09:25.968 --> 00:09:29.478 Yeah. It's very, right now it's kind of basic and it's still trying to optimize 00:09:29.478 --> 00:09:36.039 it. But it was able to at least get it compiled after some surgery through its compiler. 00:09:36.741 --> 00:09:41.948 You are blowing my mind. So you built your own compiler and now you're getting 00:09:42.268 --> 00:09:45.523 the YOLO V9 model? Is that what it is? Because the YOLO models are pretty small. 00:09:46.405 --> 00:09:49.878 Yeah. It tried a few of them and it got various percentages because it was basically 00:09:49.878 --> 00:09:51.778 measuring how much would actually 00:09:51.778 --> 00:09:55.028 stay located running on the TPU and not get pushed back to the CPU. 00:09:55.028 --> 00:09:59.107 Sure, yeah. Huh. That is interesting. 00:09:59.608 --> 00:10:04.158 Basically trying to figure out like what more could you do just with like better 00:10:04.158 --> 00:10:07.512 tech on the side we control since it's just kind of been frozen for five years. 00:10:07.924 --> 00:10:10.948 Like glass breaking, if you were using this in a security context would be kind 00:10:10.948 --> 00:10:12.578 of interesting. Dogs barking. 00:10:12.578 --> 00:10:16.228 It sounds like there's already stuff out there for identifying bird calls. So that's pretty neat. 00:10:16.228 --> 00:10:17.618 You could use it for bird detection. 00:10:17.618 --> 00:10:17.918 Yeah. 00:10:17.918 --> 00:10:21.189 That's fun. I wonder if you could do it with the amount of birds around my place. 00:10:21.711 --> 00:10:25.168 And then there are some things you can offload there's other obviously if you've 00:10:25.168 --> 00:10:27.905 got like an nvidia gpu there's other ways you can do offloading, 00:10:29.148 --> 00:10:33.919 i i didn't i i have a coral and i don't i didn't create my own custom compiler, 00:10:34.401 --> 00:10:38.418 but i did want to do more with the images than frigate has built in so frigate 00:10:38.418 --> 00:10:42.618 will do license plate to do human it can even do like package detection to a 00:10:42.618 --> 00:10:43.926 degree and all that with the coral, 00:10:44.541 --> 00:10:50.258 and all locally and just within milliseconds but it can't it can't really describe 00:10:50.258 --> 00:10:54.238 a scene it can't it can't monitor events throughout the day and kind of compile 00:10:54.238 --> 00:10:59.384 together a more comprehensive this happened then this happened then this happened but, 00:11:00.058 --> 00:11:04.708 an llm could but you'd have to be a maniac to send your home footage up to a 00:11:04.708 --> 00:11:09.018 cloud llm like you know i don't know google gemini or cloud or whatever you really want. 00:11:09.018 --> 00:11:12.698 Them they have vision now they're just you can accurately describe everything going on. 00:11:12.698 --> 00:11:15.988 Not only get saved on the server somewhere not only would that be impractical 00:11:15.988 --> 00:11:19.358 from a bandwidth standpoint for what i'm thinking of right but it just be an 00:11:19.358 --> 00:11:22.708 absolute privacy nightmare and then i'm sure it would consume because you're 00:11:22.708 --> 00:11:27.451 just doing vision constantly i'm sure it would consume a fair amount of tokens it'd get expensive, 00:11:28.514 --> 00:11:32.589 All of the dynamics of that change if you could do all of it locally. 00:11:33.390 --> 00:11:37.210 And if you essentially can run image recognition locally unmetered. 00:11:38.242 --> 00:11:40.956 But I don't really have any hardware that's capable of doing that. 00:11:41.467 --> 00:11:44.497 Well, until I realized, I think it was TechDev that reminded me, 00:11:44.741 --> 00:11:49.635 Jeff's probably pointed out a thousand times, I've got a Steam Deck sitting right over here. 00:11:49.977 --> 00:11:52.079 A sneaky hidden GPU. 00:11:52.276 --> 00:11:57.425 With a decent CPU and a decent amount of RAM, and it's a shared memory model. 00:11:58.319 --> 00:12:00.331 It's already optimized for this kind of thing. 00:12:00.331 --> 00:12:05.871 Yes. It's not a lot of memory, but it's continuous shared memory, which these LMs love. 00:12:05.871 --> 00:12:07.143 Yeah, what are we working with on that? 00:12:08.691 --> 00:12:11.276 Jeff, do you remember? I think it's 16 gigs. It's not a ton. 00:12:11.831 --> 00:12:12.091 That's. 00:12:13.511 --> 00:12:15.161 But you can upgrade it too, I think. 00:12:15.161 --> 00:12:19.606 Yeah, it's 16 gigs. You can't upgrade the RAM, but you can change how much GPU gets in the BIOS. 00:12:19.861 --> 00:12:23.201 So you can tell it like, give me half. I think half, maybe only up to four. 00:12:23.201 --> 00:12:24.889 I set mine to four gigs for GPU though. 00:12:25.783 --> 00:12:32.391 So I started thinking, if I could take my Steam Deck and get this running a 00:12:32.391 --> 00:12:36.091 local model, this changes the dynamics of the privacy situation, 00:12:36.091 --> 00:12:37.316 of the economics and all of it. 00:12:37.792 --> 00:12:40.661 So first thing I had to do was get on the Steam Deck, right? 00:12:40.661 --> 00:12:44.481 So I jump in desktop mode, and there's nothing really set up in desktop mode. 00:12:44.481 --> 00:12:47.801 So I'm using the pads to, like, mouse around and getting console up and then 00:12:47.801 --> 00:12:51.341 using the virtual on-screen keyboard, which I've never been a huge fan of, 00:12:51.341 --> 00:12:52.920 to, like, type in with the trackpad. 00:12:53.425 --> 00:12:57.881 And, you know, of course, I do the right thing, and I go over to OpenCode's 00:12:57.881 --> 00:13:01.431 website, and I grab the curl shell command like a gentleman. 00:13:02.211 --> 00:13:06.391 paste that right into my terminal on the steam deck and just let her rip right 00:13:06.391 --> 00:13:08.564 you know just pull it down and let it rip right to shell, 00:13:09.191 --> 00:13:14.451 uh pipe that baby and uh sure enough it um installed i think in my home directory 00:13:14.451 --> 00:13:15.756 like the open code installer, 00:13:16.349 --> 00:13:20.851 detected that it was an immutable os and it like detected that you need to set 00:13:20.851 --> 00:13:24.601 everything up under my home directory nice and then i closed console and reopened 00:13:24.601 --> 00:13:27.741 it and typed in open code and bob's your uncle there we go and And then I just 00:13:27.741 --> 00:13:28.931 used one of the free models, 00:13:29.526 --> 00:13:33.771 and I just said, turn SSH on, do a couple other changes. 00:13:33.771 --> 00:13:34.811 Open this baby up. 00:13:34.811 --> 00:13:35.817 Yeah. And I hit enter. 00:13:36.851 --> 00:13:41.065 And I did all of that. And then I set up like an SSH key for myself and stuff. 00:13:41.384 --> 00:13:45.928 And then went over to my main box and just said, go inventory the heck out of 00:13:45.928 --> 00:13:47.961 this thing because we're going to bang on this. 00:13:48.414 --> 00:13:52.278 And so it, you know, SSH'd in, did a full inventory of the OS, 00:13:52.278 --> 00:13:55.498 figured out, you know, Steam Halo or whatever and did the whole thing. 00:13:55.498 --> 00:13:57.908 So we kind of created like this inventory and documentation. 00:13:57.908 --> 00:14:00.748 So we knew what we're talking about. We knew how to SSH in there and reserved 00:14:00.748 --> 00:14:04.188 an IP for it in DHCP. So that way I could, you know, always talk to the same IP. 00:14:04.278 --> 00:14:04.958 Like a gentleman. 00:14:04.958 --> 00:14:08.538 Right. I got to have these things organized, Wes. It can't be just random IPs. 00:14:08.538 --> 00:14:10.398 Well, because this is becoming infrastructure pretty quickly. 00:14:11.298 --> 00:14:11.458 Yeah. 00:14:11.458 --> 00:14:14.958 Is this thing going to be just on all the time? I'm like, I'm going back to 00:14:14.958 --> 00:14:17.358 the dock. I'm going to put this thing in the dock. I'll just turn the screen 00:14:17.358 --> 00:14:18.792 off and I'll just let it rip. 00:14:19.268 --> 00:14:23.993 So got them all loaded up. But like, you can't just go get any model. 00:14:24.701 --> 00:14:28.596 It needs to work on that hardware. It needs to work with the resources you got. 00:14:28.979 --> 00:14:30.976 It needs to be capable of the thing you're trying to do. 00:14:31.133 --> 00:14:35.958 I mean, even in the last three weeks, there has been just this embarrassment 00:14:35.958 --> 00:14:41.186 of riches of quantitized and smaller and smaller models that can do things that I thought, 00:14:41.755 --> 00:14:43.838 well, what we're seeing, what we're seeing, and it's something I kind of thought 00:14:43.838 --> 00:14:47.868 we'd always see, I think, is these models to be effective at a very specific 00:14:47.868 --> 00:14:49.847 task don't need the entire internet. 00:14:50.834 --> 00:14:53.622 in their weight. So they don't need to have a, you know, 10, 00:14:53.622 --> 00:14:57.974 20, 30 billion parameters, maybe 1 billion, maybe 4 billion parameters. 00:14:58.386 --> 00:15:01.572 And if they're just doing a very focused task, they don't need all of Reddit's 00:15:01.572 --> 00:15:05.042 thoughts on recipes and, you know, car reviews and everything like that. 00:15:05.042 --> 00:15:08.032 Yeah. And we have the ability to distill down now, right? So we can take like 00:15:08.032 --> 00:15:11.842 a broadly capable model that's developed that skill and then sort of try to 00:15:11.842 --> 00:15:14.482 train a smaller model that can just capture the stuff we want from. 00:15:14.482 --> 00:15:18.622 And what's awesome is this is where all the free stuff's at all this really 00:15:18.622 --> 00:15:23.284 cool hyper focused mission specific small enough you can run on real hardware 00:15:23.713 --> 00:15:28.132 it's all open source it's it's this is where like and this is where the most fun is at. 00:15:28.132 --> 00:15:30.402 It's a fun wacky creative sort of like. 00:15:30.402 --> 00:15:35.252 Crazy wild frontier yeah just models that you do very hyper specific things, 00:15:36.202 --> 00:15:42.872 it's really fun so i had a plethora chest yeah yeah and so job one was throw 00:15:42.872 --> 00:15:46.622 as many at this thing and see which ones produce what actually works because 00:15:46.622 --> 00:15:47.622 there's a lot to choose from. 00:15:47.942 --> 00:15:50.073 So that is what I did next. 00:15:53.039 --> 00:15:57.022 When I first started putting my work online, building a website always felt 00:15:57.022 --> 00:15:58.628 like a project in itself. 00:15:59.005 --> 00:16:02.761 Hosting domains, design, figuring out what tool to use. 00:16:03.075 --> 00:16:07.312 There was a lot of friction before you even got to the thing you actually wanted to share. 00:16:07.852 --> 00:16:11.912 So I tried Hostinger's AI Builder. And what surprised me is you can actually 00:16:11.912 --> 00:16:15.666 start building a mock-up before you even create an account. 00:16:16.033 --> 00:16:18.766 You can bring in your own assets and really dig into the design, 00:16:18.987 --> 00:16:20.404 or just prompt your way through it. 00:16:20.925 --> 00:16:24.450 I went the prompt route. And because I wanted to give it a real test, 00:16:24.727 --> 00:16:29.492 I built a website for my eight chickens with a page for each of them in just 00:16:29.492 --> 00:16:31.663 a few minutes. That's the part I like. 00:16:33.080 --> 00:16:37.573 You describe what you want, and Hostinger gets you a real starting point fast. 00:16:37.782 --> 00:16:39.326 No designer or developer required. 00:16:39.622 --> 00:16:42.019 Hostinger builds your vision step by step. 00:16:42.379 --> 00:16:47.392 Create your website today. Go to hostinger.com slash unplugged and use the code 00:16:47.392 --> 00:16:49.688 unplugged for 10% off now. 00:16:52.521 --> 00:16:55.557 So, Chris, you finally found a way to use your Steam Deck. 00:16:56.566 --> 00:17:00.823 What model did you load on here? Because I'm assuming that's not the easy part. 00:17:02.268 --> 00:17:05.542 You know, I did have an embarrassment of options, Brent. I really did. 00:17:05.664 --> 00:17:09.391 It was nice. So I call my deck Fish Deck. 00:17:10.486 --> 00:17:11.243 Oh, my goodness. 00:17:11.498 --> 00:17:17.676 I figured, you know, we'll go fishing. So I ultimately bounced between two models. 00:17:17.676 --> 00:17:20.736 I kind of narrowed it down to two probably within about 25 minutes. 00:17:20.736 --> 00:17:28.786 And it was a couple of options of different Quinn models and YOLO and YOLO 11 and is pretty new. 00:17:28.786 --> 00:17:35.086 And it won in what I did is I took a, I took a couple of images from frigate 00:17:35.086 --> 00:17:38.850 that I knew what was in them as test images, like a batch of six test images 00:17:39.146 --> 00:17:41.626 and would run them through the different models and then see what their results 00:17:41.626 --> 00:17:42.873 are. since I knew what the images were. 00:17:43.302 --> 00:17:46.077 And YOLO just won the most often there. 00:17:46.806 --> 00:17:54.071 People were at a 65% accuracy with 88% confidence, and cars it could detect with a 91% accuracy. 00:17:54.599 --> 00:17:57.476 But the other thing, it was a good job of, like, bouncing between CPU and GPU. 00:17:57.476 --> 00:18:01.872 So if I kept it warm, the first image was, like, 50 milliseconds to recognize, 00:18:02.244 --> 00:18:06.156 but then it would just be, you know, 10, 15, 20 milliseconds after that. 00:18:06.166 --> 00:18:06.976 That's not bad. 00:18:06.976 --> 00:18:10.272 For an image. All local, right? All local. 00:18:11.366 --> 00:18:14.346 Now, as soon as I finish this up, a brand new Quinn came out that might actually 00:18:14.346 --> 00:18:17.026 do this even better. I mean, this is how fast this is moving because I did this 00:18:17.026 --> 00:18:20.210 on this week and then Saturday or something, a new model came out. 00:18:21.010 --> 00:18:23.875 There's a couple of extra false positives. I think if I were sending it through 00:18:23.875 --> 00:18:26.885 a more sophisticated model, some of the things would be a little bit better. 00:18:26.885 --> 00:18:27.175 Right. 00:18:27.993 --> 00:18:31.214 Like, for example, it's frequently detecting the chickens as stuffed animals. 00:18:31.621 --> 00:18:33.020 I mean, this is true. 00:18:33.652 --> 00:18:38.255 It calls them fluffy stuffed animals. Fluffy stuffed animals sitting on a shelf 00:18:38.655 --> 00:18:39.555 is how it describes them. 00:18:40.355 --> 00:18:44.435 Have you customized any of the sort of, you know, system prompt or other context 00:18:44.435 --> 00:18:46.882 you inject in around what to expect in the images? 00:18:47.295 --> 00:18:50.265 Yeah. Okay. So I am starting to do that now, but initially I had not in the 00:18:50.265 --> 00:18:53.455 raw testing. But now that I've kind of landed, I'm trying that to see if I can. 00:18:53.455 --> 00:18:56.275 So are you going to push towards more stuffed animals? 00:18:59.015 --> 00:19:00.015 That's a good question. 00:19:00.015 --> 00:19:01.675 Describe as if a fantasy novel. 00:19:01.675 --> 00:19:06.358 The other thing that throws it is it's getting, okay, so I should probably describe the system. 00:19:06.764 --> 00:19:10.355 So what happens is there's a collection that's pulling these images from the 00:19:10.355 --> 00:19:13.893 Frigate API, and it's storing them into a queue on the deck. 00:19:14.473 --> 00:19:19.117 And then the deck runs every so often and just batch processes them, and then it cleans up. 00:19:19.703 --> 00:19:23.475 And since they're coming from Frigate, if the coral has assigned like a bounding 00:19:23.475 --> 00:19:26.262 box with a label, that comes through to the model. 00:19:26.564 --> 00:19:31.355 And so sometimes the model just cheats and reads what Frigate has labeled it 00:19:31.355 --> 00:19:36.537 as and calls it that. So Frigate labels my rooster boss as a dog. 00:19:37.001 --> 00:19:40.355 So every time now Yolo sees boss, because Frigate's labeled, 00:19:40.355 --> 00:19:42.855 oh, that's a dog. No, that one there, that's a dog. I know that one. 00:19:43.595 --> 00:19:46.724 You're like, no, buddy, that's not a dog. That's a rooster. That's a rooster right there. 00:19:47.495 --> 00:19:51.645 So that it goes in and does this batch processing. And then the thing that I 00:19:51.645 --> 00:19:54.725 think is probably going to be a little weird to some people, 00:19:54.725 --> 00:19:57.085 but this is what I'm building is –. 00:19:58.654 --> 00:20:02.923 A nightly summary report that comes to me in a web dashboard that summarizes 00:20:02.923 --> 00:20:05.899 the day's events around the RV and the farm and the chickens, 00:20:06.387 --> 00:20:11.103 with a top-level summary, which is in progress, and then a couple of key moment 00:20:11.103 --> 00:20:15.243 snapshots where I can see a description and a snapshot with a button to, 00:20:15.243 --> 00:20:16.226 you know, make a correction. 00:20:17.190 --> 00:20:21.193 And I also get, like, a three-line sentence summary sent to me in telegram of, 00:20:21.193 --> 00:20:24.023 like, this is what happened today. The chickens did this. We saw Levi do this 00:20:24.023 --> 00:20:25.710 today. And that kind of stuff. 00:20:27.085 --> 00:20:32.078 But to get there, I had to kind of put cameras all around the property. 00:20:32.507 --> 00:20:35.236 And we do have a couple of cameras inside our home. 00:20:35.729 --> 00:20:41.253 Now, the reason why I did cameras inside the home is we live in an RV that sometimes 00:20:41.253 --> 00:20:44.363 is in places where you need to know if somebody entered your home. 00:20:44.363 --> 00:20:46.323 Maybe you're parked at a Walmart. 00:20:46.520 --> 00:20:50.203 You know, your home, if you think about this, you put your home in a parking 00:20:50.203 --> 00:20:54.897 lot or at some random campground where you leave and you're not home. 00:20:56.209 --> 00:20:59.238 You want to know if somebody came in your home or not. So we have a couple of 00:20:59.238 --> 00:21:03.012 cameras inside the home, in the living room, and a couple of interior places. Not everywhere. 00:21:03.448 --> 00:21:05.793 Except for when Brent's there. Then we put him everywhere. 00:21:06.458 --> 00:21:10.578 And so we're able to kind of proactively turn those on and off when we're there 00:21:10.578 --> 00:21:11.743 or not using Home Assistant. 00:21:12.376 --> 00:21:14.938 But it does require you have cameras everywhere. And Wes is like, 00:21:14.938 --> 00:21:17.345 I don't know. That's a little creepy. He said, you're a bit of a creep. 00:21:17.920 --> 00:21:19.438 And your family probably hates you. 00:21:19.438 --> 00:21:20.578 I don't think that's what I said. 00:21:21.258 --> 00:21:22.475 I'm not sure that's what I said. 00:21:22.655 --> 00:21:24.818 Brent, is that what you heard? I kind of heard that's what I heard. 00:21:24.818 --> 00:21:27.958 Oh, yeah, definitely. it's the subtext for us you gotta pick up on. 00:21:28.798 --> 00:21:32.688 No I'm not I like what you're doing I think it's a neat setup and I think it's 00:21:32.688 --> 00:21:39.124 a lot of fun places you could take it but there was sort of a lizard brain part of me that. 00:21:39.321 --> 00:21:40.093 It's always watching. 00:21:40.407 --> 00:21:45.018 Yeah and I think you know we just live in a world where there are fewer and 00:21:45.018 --> 00:21:49.178 fewer unmonitored spaces you've talked a lot about like flock cameras at, 00:21:49.997 --> 00:21:53.288 on the launch of course but you know everywhere you know they go into any old 00:21:53.288 --> 00:21:56.928 store they have more and more fancy camera setups and more and more people out 00:21:56.928 --> 00:21:59.278 there do have sort of things like ring cameras and there's nothing wrong with 00:21:59.278 --> 00:22:01.880 that i'm not trying to impugn that it's just sort of the collective, 00:22:02.553 --> 00:22:07.508 part means you spend more time in a state where you know that you're being observed 00:22:07.508 --> 00:22:09.368 and then so if that also is sort of 00:22:09.809 --> 00:22:13.358 in your friend's houses or in your own house or in you know someone else has 00:22:13.358 --> 00:22:16.688 set it up and you're kind of always around it it just keeps a little part of 00:22:16.688 --> 00:22:18.580 the brain active and you don't i don't know. 00:22:19.067 --> 00:22:23.705 I think this becomes uh also much more of a consideration when you think about 00:22:23.868 --> 00:22:29.138 where i could take this already so uh very quickly within probably about 10 00:22:29.138 --> 00:22:31.060 minutes i could have a system where i say, 00:22:33.018 --> 00:22:36.778 how many times today did you see abby or how many times did you see the chickens 00:22:36.778 --> 00:22:38.705 what were the what did the chickens do all day today. 00:22:38.821 --> 00:22:40.258 Map the movement across the whole day. 00:22:40.638 --> 00:22:46.304 Yeah and that i could probably do in the next 10 minutes um and then with probably, 00:22:47.360 --> 00:22:52.364 six months of work and just learning to use this system i could probably evolve this into, 00:22:53.549 --> 00:22:58.897 Where did I put this box? Where did I set this down? You know, those kinds of things. 00:22:58.897 --> 00:23:01.237 Historical locations of things and how that's changed. 00:23:01.237 --> 00:23:03.387 Now that's a whole level of monitoring 00:23:03.387 --> 00:23:06.610 to get there, right? And that means cameras in all kinds of places. 00:23:07.068 --> 00:23:12.392 And it would be completely inconceivable if this was going offsite to a cloud provider. 00:23:12.827 --> 00:23:16.728 Completely inconceivable. It's something you can begin to kind of think about. 00:23:17.359 --> 00:23:21.257 But I think the family acceptance factor and your comfort level. 00:23:21.257 --> 00:23:25.737 like so for us like there's no cameras in the kids spaces and there's no cameras 00:23:25.737 --> 00:23:29.267 in bedrooms or bathrooms obviously yeah we do have a camera in the living room 00:23:29.267 --> 00:23:35.448 that activates though uh when we leave so the kids know that if Hedir or I leave um, 00:23:36.783 --> 00:23:39.867 and if they're not on the wi-fi there is a possibility that the cameras could 00:23:39.867 --> 00:23:41.317 be on yeah when we're not home. 00:23:41.595 --> 00:23:42.517 That seems like a good way to. 00:23:42.517 --> 00:23:45.147 Do it we had a conversation around that and when I so a couple years when I 00:23:45.147 --> 00:23:48.805 put them in ago because I mentioned at the beginning about being concerned about 00:23:49.002 --> 00:23:50.709 the RV's security yeah um, 00:23:51.596 --> 00:23:56.205 We had a conversation about, you know, there's a real difference between privacy 00:23:56.472 --> 00:23:59.334 that you have control over and privacy that you're essentially handing over 00:23:59.334 --> 00:24:00.424 to a company that you trust. 00:24:01.564 --> 00:24:04.361 And so that was the first time a couple of years ago, like we had a really concrete 00:24:04.791 --> 00:24:07.363 discussion about cloud versus private and local. 00:24:07.955 --> 00:24:11.444 And so that was something that like I had to get family buy off on before I 00:24:11.444 --> 00:24:12.657 could put that camera there. 00:24:12.947 --> 00:24:16.057 But the majority of the cameras are on the outside around the farm, 00:24:16.744 --> 00:24:18.855 which they do show up on from time to time, but we all know about them. 00:24:19.314 --> 00:24:21.994 and that to me is even more useful because I want to know when people came and 00:24:21.994 --> 00:24:24.684 went but mostly I want to know if like coyotes show up and stuff like that. 00:24:24.684 --> 00:24:25.354 Yeah, absolutely. 00:24:25.354 --> 00:24:29.676 But I do have to like, if I want to take it further, I have to give consideration to that or like. 00:24:30.419 --> 00:24:33.104 I think it is that it's, part of it is the capability thing. 00:24:33.104 --> 00:24:35.224 It's like, it's not like I wouldn't go in the space or you know, 00:24:35.224 --> 00:24:39.554 like I don't really care but it just felt like the combination of how available 00:24:39.554 --> 00:24:43.414 it is and how powerful it's just sort of growing and that from the outside, 00:24:43.414 --> 00:24:44.544 it doesn't really change, right? 00:24:44.544 --> 00:24:48.734 Like what was just sort of one level of monitoring can become a whole other thing. 00:24:48.734 --> 00:24:49.774 Yes, yes. 00:24:49.774 --> 00:24:52.004 And like I have – I trust you. I'm not worried about what you're going to do with it. 00:24:52.144 --> 00:24:54.804 No, but that is a really interesting aspect of this, all these capabilities, 00:24:54.804 --> 00:24:56.784 is these things that have just been doing one thing for all these years are 00:24:56.784 --> 00:24:58.515 now capable of so much more with this tooling. 00:24:59.484 --> 00:25:02.924 And the thing that's crossed my mind in this experiment – because now it's been 00:25:02.924 --> 00:25:04.394 about three days – when did I start doing this? 00:25:04.394 --> 00:25:05.284 Yeah, sometime this week. 00:25:05.284 --> 00:25:08.214 About three days I've been getting these dashboard reports. And each night I'm 00:25:08.214 --> 00:25:09.184 kind of tweaking it a little bit. 00:25:10.810 --> 00:25:13.538 But it crossed my mind. It's like what if I wanted to walk around on my underoos? 00:25:14.430 --> 00:25:17.029 You know, and I'm doing it in a space now that I've turned on for this testing. 00:25:17.029 --> 00:25:19.596 I don't know if I'll always leave it on in the space, but for these three days I've had it on. 00:25:20.159 --> 00:25:23.759 I'm like, what kind of summary am I going to get? Am I going to get a snapshot 00:25:23.759 --> 00:25:26.999 of myself and my underoos if I walk around, you know, with, you know, 00:25:26.999 --> 00:25:30.999 fat guy walks around in messy RV? 00:25:32.419 --> 00:25:36.839 But it's interesting because you're the architect of the system and you are 00:25:37.199 --> 00:25:41.229 questioning whether you should walk around naked in your own space, right? Right. 00:25:41.229 --> 00:25:45.429 I mean, that's why I don't, I don't know. again that camera would not normally 00:25:45.429 --> 00:25:49.057 be on so it's not normally something i have to think about i've turned it on 00:25:49.324 --> 00:25:53.339 just to see how this process goes like and there's been the flip side too like 00:25:53.339 --> 00:25:55.448 last night we were just having a chill moment, 00:25:55.982 --> 00:25:59.199 with like some music playing and the lights were kind of dim and hadia and i 00:25:59.199 --> 00:26:03.180 were chilling on the couch we all had a great day and abby was in the kitchen 00:26:03.558 --> 00:26:07.220 making cookies she's got this great cookie recipe that she makes from scratch and, 00:26:07.859 --> 00:26:10.989 it's just a everyday moment but then when i got the summary and i was looking 00:26:10.989 --> 00:26:13.859 at this morning i was like oh that was actually, that was a really sweet moment. 00:26:14.219 --> 00:26:17.689 I was nostalgic for a moment that happened last night that at the moment I don't 00:26:17.689 --> 00:26:21.619 think I took in how nice it was just to be a simple moment of all of us together 00:26:21.619 --> 00:26:24.559 with, you know, our daughter making cookies while we chill on the couch. Like, that's great. 00:26:25.679 --> 00:26:27.709 And then to see it this morning, I'm like, oh yeah, that was really nice. 00:26:27.709 --> 00:26:30.189 I'd actually like to save that. And I thought, I should build in a save feature. 00:26:30.189 --> 00:26:31.239 I want to save that photo. 00:26:31.939 --> 00:26:32.589 Good idea, yeah. 00:26:32.589 --> 00:26:36.409 So there's a flip side to it too where it's like, I don't remember anything 00:26:36.409 --> 00:26:40.549 and every day blurs together and I lose all of these moments. 00:26:40.549 --> 00:26:42.043 that I just don't hold them at all. 00:26:43.210 --> 00:26:46.484 And I noted when I vlogged for like 10 minutes, 16 years ago, 00:26:47.007 --> 00:26:50.403 how much more of those moments I retained because I could watch them back. 00:26:51.053 --> 00:26:53.015 So like we have more of a memory of those moments. 00:26:54.089 --> 00:26:56.009 An automated moment capture. 00:26:56.009 --> 00:27:01.379 Yeah. And if I could recreate something that's more like that and less the creepy, 00:27:01.379 --> 00:27:03.150 that would be the direction I'd like to take it. 00:27:03.504 --> 00:27:06.149 Yeah, it gives you a little more agency over your own life, the stuff, 00:27:06.149 --> 00:27:09.240 data you're already generating that you do want to have access to. 00:27:09.918 --> 00:27:11.328 And it makes me wonder... 00:27:12.843 --> 00:27:17.378 What else could I use that deck for? Like if I'm not using it for this or when 00:27:17.378 --> 00:27:19.048 it's not doing batch image processing. 00:27:19.048 --> 00:27:22.248 It's a networked GPU inference provider at this point, more than a deck. 00:27:22.248 --> 00:27:26.282 It's not huge, it's not powerful, but there's so many great little models now. 00:27:26.787 --> 00:27:29.648 Like I just saw a really small, fantastic image generation model. 00:27:29.648 --> 00:27:31.428 Totally, yeah. We should try that. 00:27:31.428 --> 00:27:35.168 Music generator, you know? I mean, just all kinds of things that I could do 00:27:35.168 --> 00:27:39.718 on that deck now along with this. And it's more exciting than playing video 00:27:39.718 --> 00:27:40.742 games on it for me right now. 00:27:41.137 --> 00:27:44.278 I was going to say, have you wired it into production in a way where you have 00:27:44.278 --> 00:27:47.308 to take like a downtime in order to play some video games? 00:27:49.188 --> 00:27:49.988 It's only been a few days. 00:27:49.988 --> 00:27:52.660 We're on Coyote Watch. High warning today. 00:27:54.007 --> 00:27:58.378 Sorry, kids. Coyotes are out. Actually, you know what I'd really like to get 00:27:58.378 --> 00:28:02.128 cameras for is, first of all, it's going to be bird season, but we've got two 00:28:02.128 --> 00:28:03.568 albino deer on the property and 00:28:03.568 --> 00:28:06.448 they show up in the evenings and it'd be really neat to just catch them. 00:28:06.568 --> 00:28:07.277 Find them, yeah. 00:28:08.188 --> 00:28:12.976 So it was pretty fun. I tried out Moondream 2 as well, which works great. 00:28:13.446 --> 00:28:19.681 Quen 2.5 VL 3 billion parameter, which worked pretty well. But the winner was YOLO. 00:28:20.366 --> 00:28:24.578 The AMD APU wasn't as useful as I was hoping. A lot of the stuff ended up working 00:28:24.578 --> 00:28:28.081 on CPU a lot better. So a lot of times I was just doing CPU loaded stuff. 00:28:28.848 --> 00:28:31.138 Yeah. And then bringing it all together, that dashboard was nice. 00:28:31.138 --> 00:28:35.018 Put a little SQLite database behind it. And then those images get saved with 00:28:35.018 --> 00:28:36.788 kind of like a 30-day cleanup retention period. 00:28:36.974 --> 00:28:40.091 You know, we just don't give enough love to Sequel Light. It really sure is handy. 00:28:41.259 --> 00:28:45.366 Per Snickety in the chat here has a question for you. Why not use the Hacks 00:28:45.366 --> 00:28:47.830 Frigate add-on for this system that you built? 00:28:48.457 --> 00:28:51.206 Well, this goes way beyond. So you're getting, not only are you getting like 00:28:51.206 --> 00:28:54.576 a, you can have it detect anything you want, right? 00:28:54.576 --> 00:28:59.956 But you're also then getting sort of this rich context summary that ties together, 00:28:59.956 --> 00:29:02.736 like the chickens did this, and then they went out and did this, 00:29:02.736 --> 00:29:04.595 and then they went out and did this in a summary. 00:29:05.077 --> 00:29:10.206 And then a hyper summary on top of that that brings it all together to where 00:29:10.206 --> 00:29:13.550 I was like, yeah, I can track, I already do track dogs, packages, and faces with Frigate. 00:29:14.188 --> 00:29:17.916 But this is such a whole other level where tomorrow if I decide, 00:29:17.916 --> 00:29:21.556 okay, I want to know when this happens, I can just go to it and ask it. 00:29:21.556 --> 00:29:26.496 And it's a little tiny model with vision that can just go find that stuff. 00:29:26.496 --> 00:29:29.711 So it's like an events inventory almost that you can tap into? 00:29:30.193 --> 00:29:35.116 And all of this feeds Home Assistant, right? So Home Assistant is a key piece 00:29:35.116 --> 00:29:36.480 that kind of glues it all together. 00:29:36.851 --> 00:29:41.936 Home Assistant is helping with the – like if it knows where we're at, 00:29:41.936 --> 00:29:43.366 like all the location assigned stuff. 00:29:43.366 --> 00:29:47.266 So wind cameras should be active or alerting is done or triggering an agent 00:29:47.266 --> 00:29:48.176 for something that's more urgent. 00:29:48.176 --> 00:29:52.116 So there's another tier in here where if it observes an image that is an urgent 00:29:52.116 --> 00:29:57.111 thing like a security issue like a coyote or some rando with a van on the property, 00:29:57.749 --> 00:30:01.576 then it can break out and take a different path using Home Assistant and send 00:30:01.576 --> 00:30:06.226 me a telegram with the image attached through – or I'm sorry, not a telegram. 00:30:07.066 --> 00:30:11.529 a push notification. So I get a push notification alert that uses Home Assistant for that. 00:30:11.744 --> 00:30:12.423 That's pretty nice. 00:30:12.539 --> 00:30:15.176 It's very good. So this just sort of sits on top of that and gives me even more 00:30:15.176 --> 00:30:18.706 flexibility. And again, like if I had to send it all up to Claude or whatever 00:30:18.706 --> 00:30:21.646 to do this or to Gemini or to ChatGyppity or whatever. 00:30:21.646 --> 00:30:22.169 It'd be a nightmare. 00:30:22.419 --> 00:30:25.966 Yeah, and it'd be a major bandwidth suck. But because this is running locally 00:30:25.966 --> 00:30:27.638 on the deck, already on the LAN, 00:30:28.816 --> 00:30:32.392 It's just like such a why not situation. There's so much more you can do. 00:30:32.392 --> 00:30:36.102 So this is my question to you guys out there is, is anyone else trying this 00:30:36.102 --> 00:30:37.489 kind of stuff on their decks? 00:30:37.976 --> 00:30:41.942 Are you using your deck for anything weird? LLM models, you know, 00:30:41.942 --> 00:30:45.462 self-hosting. What have you found the deck is great for beyond just gaming? 00:30:45.462 --> 00:30:46.552 As a Linux computer. 00:30:46.552 --> 00:30:50.012 Yeah. It's a good little Linux box. So I want to know what has worked and hasn't 00:30:50.012 --> 00:30:53.383 worked. Boost.jupiterbroadcasting.com. You can tell us about that. 00:31:06.478 --> 00:31:12.157 Got a little feedback here from kenneth hey guys just heard episode 687 that's 00:31:12.157 --> 00:31:17.948 the last one and wanted to share some gold regarding the apple and google tv topic, 00:31:18.697 --> 00:31:26.137 go buy a raspberry pi 5 and a case with nvme ssd support write liberalec to 00:31:26.137 --> 00:31:32.612 the ssd and boot it up then you go and add jellyfin as a repo and install Jellyfin. 00:31:33.337 --> 00:31:36.426 Then in Jellyfin, install the Kodi Sync plugin. 00:31:37.035 --> 00:31:44.157 LiberLec can do much more. I have the older Pi 4 and an Argon 1 M.2 case, 00:31:44.157 --> 00:31:49.586 but with some overclocking and higher memory to GPU, everything seems to work just fine. 00:31:50.717 --> 00:31:54.862 Well, Kenneth, this is the thing. And it really upsets me to no end. 00:31:56.610 --> 00:32:01.577 it looks like the just use a raspberry pi and and open elec or cody guys were 00:32:01.577 --> 00:32:05.127 right all along i've tried to fight it for so many years, 00:32:07.040 --> 00:32:11.017 and they've they've just they've just had this it's just worked for them for 00:32:11.017 --> 00:32:15.028 all these years they haven't had these problems and i just didn't want to hear it. 00:32:15.486 --> 00:32:17.277 Especially i suppose a lot of folks. 00:32:17.277 --> 00:32:19.016 I need an app. 00:32:19.137 --> 00:32:20.627 Where it falls down is that if you do want. 00:32:21.167 --> 00:32:26.367 I don't need a Netflix app. I just need a TV that works. You know? Kenneth is right. 00:32:27.653 --> 00:32:31.107 And you know how I know I've capitulated? Because guess who was in Cody last 00:32:31.107 --> 00:32:35.043 night? Playing around with Cody. Seeing what I could make. Yep. Yep. Yep. 00:32:35.293 --> 00:32:36.419 I don't like you anymore. 00:32:36.663 --> 00:32:40.128 However, I did it on a Google TV. And... 00:32:41.288 --> 00:32:44.598 This is this quick rant. I'll try to make this quick. This is really disappointing 00:32:44.598 --> 00:32:46.738 because it was one of those moments where it's like, I was like, 00:32:46.738 --> 00:32:49.428 hey, why? If you want to watch TV in bed tonight, you know, we'll do a little 00:32:49.428 --> 00:32:51.338 bit of it because the kids are out and about. I was like, well, 00:32:51.338 --> 00:32:53.078 just chill out in bed, watch some TV. 00:32:53.694 --> 00:32:57.171 She's like, yeah, we haven't done that in ages. Like, you're right. We haven't. 00:32:57.670 --> 00:33:01.052 So I'll go fire up the old shield TV right now. And this is the good one. 00:33:01.389 --> 00:33:04.648 I'll fire up the shield TV right now. I'll make sure all the updates are done. 00:33:04.648 --> 00:33:07.728 So it doesn't prompt us to do updates. And I'll make sure jellyfin works. 00:33:07.728 --> 00:33:09.377 So we don't have any issues with jellyfin. 00:33:09.679 --> 00:33:12.438 and whatever we want to do, YouTube, Netflix, make sure it all loads, 00:33:12.438 --> 00:33:15.348 make sure it all go into the Play Store. I'll make sure all the updates are 00:33:15.348 --> 00:33:17.081 done, and then we'll call it good. 00:33:17.377 --> 00:33:21.238 So the first thing I do is, you know, NVIDIA still, bless their hearts, 00:33:21.238 --> 00:33:23.298 updating this thing 25 years later. 00:33:23.818 --> 00:33:26.898 So I start a download. Of course, it's like 7 gigabytes or 3 gigabytes. 00:33:27.698 --> 00:33:30.708 So I go start that in the background, and I go do all the other little app updates. 00:33:30.708 --> 00:33:33.258 By the time they're done, the download is updated, and it's ready. 00:33:34.088 --> 00:33:38.908 Would you like to restart? Yes. It restarts, and for 15 minutes, 00:33:38.908 --> 00:33:41.938 I'm at just the Android boot loop screen, which is Android sitting there flashing. 00:33:41.938 --> 00:33:44.898 And I realized that it has failed to update at that point. 00:33:45.362 --> 00:33:47.498 I look it up. I'm like, it's 15 minutes. I'm like, yeah, 15 minutes. 00:33:47.498 --> 00:33:48.038 You're probably screwed. 00:33:48.738 --> 00:33:53.378 So I have to, after an update, which is always a good idea, unplug the device. 00:33:53.378 --> 00:33:54.768 That's always what they recommend you do. 00:33:54.768 --> 00:33:56.718 I think they tell you to do it in red letters. 00:33:56.758 --> 00:33:58.218 They always say, be sure to disconnect power. 00:33:58.578 --> 00:34:00.188 At a random time during this process. 00:34:00.188 --> 00:34:02.388 So I'm like, boy, I sure hope they have an AB boot environment. 00:34:02.388 --> 00:34:04.923 Boom. I pull the power, plug it back in. It boots up. 00:34:06.108 --> 00:34:09.731 Update's still available. So I go ahead and do the install again. 00:34:10.776 --> 00:34:14.990 This time it works fine. Okay. So good. All right. We're all set. 00:34:15.309 --> 00:34:19.856 We're good. Everything's been logged in. Fresh update. The updates are done. Turn the TV off. 00:34:20.716 --> 00:34:23.477 Comes around time. Okay, let's go watch some TV. I turn the TV on. 00:34:24.036 --> 00:34:27.346 Go to the Jellyfin app. Hit enter. Jellyfin crashes. 00:34:27.346 --> 00:34:28.156 No. 00:34:28.800 --> 00:34:32.794 Okay. Click it again. Jellyfin comes up. Completely logged out. 00:34:33.636 --> 00:34:37.236 No server entry. I don't have a keyboard hooked up to this thing I don't even 00:34:37.236 --> 00:34:39.676 have my phone paired to it at this point Because it's been so long So like I'd 00:34:39.676 --> 00:34:43.786 have to like bang out my jellyfin username and password And URL and everything 00:34:43.786 --> 00:34:45.056 just using the on-screen keyboard, 00:34:46.360 --> 00:34:50.156 And we bailed I'm like that's not what we came here for And that was my Google 00:34:50.156 --> 00:34:51.236 TV experience last night, 00:34:52.339 --> 00:34:55.236 So I'm not a big fan Yeah well, 00:34:55.936 --> 00:34:59.426 I mean like the idea is like I thought like Okay the issue is I'm not using 00:34:59.426 --> 00:35:03.406 these things enough And I just need to give them a little TLC And like I would 00:35:03.406 --> 00:35:06.276 a device I use daily Just get it, you know, and then, of course, 00:35:06.276 --> 00:35:08.784 it was probably the update, probably something like the Jellyfin app, 00:35:09.474 --> 00:35:11.651 was suspended. It rebooted. I don't know. 00:35:13.415 --> 00:35:17.490 Blumen Strong wrote in, here's a little Kickstarter for using Jellyfin MPV shim. 00:35:18.042 --> 00:35:22.820 It's a cage in NixOS to have a dedicated Jellyfin client. 00:35:23.144 --> 00:35:26.541 It's been working for me for at least six months without issue using Jellyfin 00:35:26.541 --> 00:35:27.585 app to control the client. 00:35:27.904 --> 00:35:31.991 The key thing is to make the cage wait for Jellyfin server to be accessible 00:35:32.149 --> 00:35:35.102 before allowing it to start the MPV shim. 00:35:35.300 --> 00:35:37.281 Yeah, cage is like a kiosk oriented. 00:35:37.601 --> 00:35:38.481 So sidecar things? 00:35:38.901 --> 00:35:40.664 Wayland. No, it's like a Wayland compositor. 00:35:41.261 --> 00:35:51.441 Oh. oh there you go oh that's awesome so he is setting up yeah provides a based 00:35:51.441 --> 00:35:53.231 dedicated kiosk jellyfin yep, 00:35:54.292 --> 00:35:56.311 well that's exactly what i asked for. 00:35:56.311 --> 00:35:57.759 Yep here in nix os. 00:35:58.373 --> 00:36:03.931 Blooming strong tell you what although i don't know if you notice at the. 00:36:03.931 --> 00:36:07.071 Bottom uh-huh i expect a full report from brent on something for the texas. 00:36:07.071 --> 00:36:10.951 Trip i was just thinking this morning i'm gonna we're gonna get to Austin and 00:36:10.951 --> 00:36:15.353 I am going to feel like such a jerk for once again not having some solution for this. 00:36:17.094 --> 00:36:19.861 So we need some hardware, right? What do we want to use for hardware? 00:36:19.861 --> 00:36:21.701 We need something small and portable to run this on. 00:36:21.701 --> 00:36:22.725 Like the deck, you mean? 00:36:25.686 --> 00:36:30.789 I mean, maybe. We'll put Cody on the deck. Yeah, there you go. 00:36:31.741 --> 00:36:34.470 That's really great though, Bloom. Thank you very much for that. 00:36:35.055 --> 00:36:39.009 Wow. I gotta think about that. We gotta think about getting some hardware together for that. 00:36:40.245 --> 00:36:42.801 We probably have something, but they're all pie-based. They're really interesting. 00:36:45.581 --> 00:36:46.625 It doesn't have to be super small. 00:36:46.645 --> 00:36:47.795 It doesn't have to be crazy, right? 00:36:47.795 --> 00:36:49.232 I know Brent wants to use an Android phone. 00:36:50.145 --> 00:36:51.577 No, I didn't say Android. 00:36:53.387 --> 00:36:54.008 Oh. 00:36:54.380 --> 00:36:56.105 Yeah, it's the phone part that's the sickness. 00:36:56.105 --> 00:36:59.725 It's the phone he can't find anything else to do with because it's not really a phone. 00:36:59.725 --> 00:37:04.655 No, I just, I don't want that phone. I want, like, a phone format because it's 00:37:04.655 --> 00:37:06.285 easy to pack and travel with or whatever. 00:37:06.605 --> 00:37:08.521 But you don't want it to be an Android phone or an iPhone? 00:37:09.014 --> 00:37:12.352 No, just give me Linux, man. Right? Can't we have that? 00:37:12.985 --> 00:37:13.915 Don't you have a Linux phone? 00:37:13.925 --> 00:37:16.857 You have the popular Linux phones that are on commercial offer, you know? 00:37:18.445 --> 00:37:21.193 I mean, you got one. Didn't seem like it worked last time we tried. 00:37:21.564 --> 00:37:25.615 Oh, yeah. Well, that's because it was, how old? No, I don't even remember. 00:37:25.615 --> 00:37:30.404 It's been that old. So, but it was exciting and entertaining, wasn't it? 00:37:30.876 --> 00:37:31.745 It was that. 00:37:31.745 --> 00:37:32.055 Yeah. 00:37:32.055 --> 00:37:33.305 So, stage one, success. 00:37:33.305 --> 00:37:35.445 But we're not always in the mood for the Brent show. 00:37:35.445 --> 00:37:37.285 We just want to watch Baywatch or Star Trek. 00:37:37.285 --> 00:37:37.615 Yeah. 00:37:37.615 --> 00:37:38.245 You know? 00:37:38.245 --> 00:37:39.785 And your Klingon is not very good. 00:37:40.165 --> 00:37:40.545 Yeah, you're right. 00:37:40.545 --> 00:37:41.705 I agree with that. It's true. 00:37:41.725 --> 00:37:44.789 I'll polish that. So if anyone has hardware suggestions. 00:37:45.243 --> 00:37:45.823 Send it in. 00:37:50.189 --> 00:37:54.245 You could boost it in like our baller booster did. Is everybody sitting down? 00:37:54.245 --> 00:37:54.668 Yeah. 00:37:55.620 --> 00:37:56.131 Are you ready? 00:37:56.560 --> 00:37:56.755 No. 00:37:56.805 --> 00:38:00.815 Blackhost is our baller this week. Blackhost knows we're going to Texas and 00:38:00.815 --> 00:38:07.625 came in with an incredible 1,234,567 satoshis. 00:38:07.625 --> 00:38:09.035 Oh my goodness. 00:38:16.506 --> 00:38:19.524 That is, Blackhost, that is very much appreciated. And Blackhost says, 00:38:19.524 --> 00:38:22.265 sending over a couple of sats for the Texas Fund. 00:38:22.381 --> 00:38:22.994 Just a few. 00:38:22.994 --> 00:38:26.334 After all, that brisket goes best with more brisket. 00:38:26.334 --> 00:38:26.674 Oh. 00:38:27.974 --> 00:38:31.514 That's very insightful, Blackhost. That is true. Nothing washes down the brisket 00:38:31.514 --> 00:38:32.900 like some brisket or some ribs. 00:38:33.544 --> 00:38:36.324 Thank you very much. We will put that there towards the Texas Fund. 00:38:36.324 --> 00:38:37.194 We've got to get that meetup. 00:38:37.594 --> 00:38:39.234 You've got the lean and you've got the fatty. 00:38:39.574 --> 00:38:42.786 Oh, the fatty. I honestly was not initially a fatty guy either. 00:38:43.058 --> 00:38:46.334 Let me tell you what. Now, with that boost right there, we've got to get our 00:38:46.334 --> 00:38:49.034 act together on the meetup. It's official right there. Thank you very much, 00:38:49.034 --> 00:38:50.360 Blackhost. It's happening. 00:38:50.656 --> 00:38:54.005 Well, Greg, the lawyer boosts in with $22,222. 00:38:57.813 --> 00:38:59.784 Putting this in the barbecue fund. 00:38:59.784 --> 00:39:03.944 Ah, very good, you guys. Thanks, Greg. 00:39:03.944 --> 00:39:04.494 Going right there. 00:39:05.034 --> 00:39:11.989 Mm-hmm. Mm-hmm. Barbecue. Mm-hmm. Not sure boosted in? 5,555 Satoshis. 00:39:14.735 --> 00:39:19.664 I've set up Muse to monitor local Facebook groups and Instagram posts in Kauai 00:39:19.664 --> 00:39:22.508 to keep track of the rebuild efforts before my trip. 00:39:23.088 --> 00:39:25.753 It's great, especially since I don't have an Instagram account. 00:39:26.920 --> 00:39:28.054 Yeah, that is handy. 00:39:28.534 --> 00:39:32.184 I feel like if they're going to give you a free compute, why not use their free 00:39:32.184 --> 00:39:35.337 compute to interact with their services that you don't want to have to use? 00:39:35.470 --> 00:39:37.254 That's actually, it makes a lot of sense. 00:39:38.114 --> 00:39:42.754 I think i want to use it to just like scour facebook marketplace you know the 00:39:42.754 --> 00:39:46.794 face bag space for just everything that i want to buy use because they've destroyed 00:39:46.794 --> 00:39:52.402 every other used locals platform that i used to use so screw them. 00:39:52.878 --> 00:39:57.654 Yeah just a face bag uh bot that just goes through muses through and finds you the deals on the bag. 00:39:58.254 --> 00:39:58.964 I like the idea that. 00:39:58.964 --> 00:40:02.614 It's a linux vps as an interface for facebook and instagram. 00:40:04.174 --> 00:40:11.350 And the chatbot yeah well you know it's their own fault Daja comes in with 6,858 Satoshis, 00:40:12.923 --> 00:40:17.544 I'm so happy a lot of projects are finally getting out of the AI is good, AI is bad rut. 00:40:18.095 --> 00:40:21.048 I have ended up somewhere similar for my engineers at work. At the end of the 00:40:21.048 --> 00:40:23.442 day, they're responsible for their code, period. 00:40:23.900 --> 00:40:28.010 People have to be making slop. People have been making slop for decades anyways. 00:40:28.417 --> 00:40:31.981 So if they submit a PR with GPL code in it or security flaws or anything else, 00:40:32.521 --> 00:40:36.248 it's not mergeable and needs to be sent back regardless if AI was involved or 00:40:36.248 --> 00:40:40.137 not. The biggest benefit we have seen from this is finally upping our CI game. 00:40:41.188 --> 00:40:46.660 I bet that is true for a lot of people. I certainly had up my CI game, so I bet that is true. 00:40:47.348 --> 00:40:52.168 I was just reflecting on that earlier this week about how I've had to adopt 00:40:52.168 --> 00:40:56.674 a lot more developer workflows that I've never bothered, could never have been arsed. 00:40:56.877 --> 00:40:59.788 You're a software factory now, whether you like to admit it or not. 00:41:00.987 --> 00:41:04.348 We've also been putting a couple of lines in our agents.md file to have the 00:41:04.348 --> 00:41:08.718 agent do something trivially obvious to a human, but been surprisingly good 00:41:08.718 --> 00:41:11.958 at filtering out the AI made this without a human looking at it whatsoever, 00:41:12.243 --> 00:41:15.169 and automatically sending it back to the contributor to fix and resubmit. 00:41:15.354 --> 00:41:16.817 Hey, sounds like what system he was doing. 00:41:16.945 --> 00:41:20.628 Yeah, that's an interesting approach. We talked about that recently. 00:41:20.628 --> 00:41:23.618 It's not bulletproof by any means, but it's good enough to catch most people 00:41:23.618 --> 00:41:25.623 who don't really care about the quality of their submissions. 00:41:26.007 --> 00:41:27.609 They don't care enough to perform a simple task. 00:41:28.265 --> 00:41:30.047 I was eating some fries and felt compelled to boost. 00:41:30.343 --> 00:41:30.848 Nice. 00:41:32.828 --> 00:41:36.374 That's a little nod to the bootleg there for one of our songs. 00:41:36.554 --> 00:41:37.578 Thank you for the boost. 00:41:37.578 --> 00:41:38.429 Thank you very much. 00:41:39.016 --> 00:41:42.284 A-A-B-M-A-T-E-B-U-S-N with 6,000 sats. 00:41:47.797 --> 00:41:52.528 Hey guys, you've given me so many good picks that I thought I would send one back to you. 00:41:52.923 --> 00:41:56.485 Kitchen Owl is what we've been using as a self-hosted grocery list. 00:41:56.965 --> 00:42:02.228 It integrates with Home Assistant, so we just use our voice to add items in the list when we run out. 00:42:02.344 --> 00:42:05.333 I like the UI too. It looks like it's got a really good mobile UI. 00:42:05.903 --> 00:42:09.195 It also sorts the list by Algo, so when you walk through the store checking 00:42:09.195 --> 00:42:13.075 items off of the list, it can learn where the items are and orders the list 00:42:13.075 --> 00:42:14.705 that way for subsequent visits. 00:42:14.705 --> 00:42:15.745 Stop it! 00:42:15.745 --> 00:42:18.545 That way you don't get halfway across the store and have to double back to the 00:42:18.545 --> 00:42:21.735 dairy section for something that was lower on the list. Cheers. 00:42:21.735 --> 00:42:22.825 Caesar's ghost. 00:42:23.345 --> 00:42:23.745 Thank you. 00:42:24.105 --> 00:42:26.551 And it is AGPL3 as well. 00:42:26.678 --> 00:42:28.555 This looks like a heck of a pick. 00:42:28.555 --> 00:42:32.695 That's a really good pick. KitchenOwl. KitchenOwl.org. 00:42:32.695 --> 00:42:33.315 Thank you, Abe. 00:42:33.315 --> 00:42:35.595 Get your KitchenOwl. KitchenOwl. 00:42:37.545 --> 00:42:41.226 Bamham182 sent in a 2,500 sat boost. 00:42:44.759 --> 00:42:48.655 regarding google tv i found the experience to be a bit better if you enable 00:42:48.655 --> 00:42:54.135 apps only mode it doesn't fully remove the idiocracy style ad bloat but it does 00:42:54.135 --> 00:42:56.456 make the whole experience slightly more streamlined, 00:42:57.223 --> 00:43:01.875 i was really excited about trying to get a steam machine to replace my on 4k 00:43:01.875 --> 00:43:06.515 google tv but i just can't justify that cost right now yeah understandable. 00:43:06.515 --> 00:43:09.945 Yeah it'll be a nice side benefit when you can get the steam machine that it 00:43:09.945 --> 00:43:14.595 could also possibly do that okay app only mode i will look into that i do have 00:43:14.595 --> 00:43:20.268 to say um on my shield i have the projectivity launcher and that i really do think is quite great, 00:43:21.405 --> 00:43:24.152 i'm quite happy with projectivity but you have to replace the launcher to get there, 00:43:25.812 --> 00:43:28.465 cgba came in with 10 000 sats, 00:43:36.136 --> 00:43:39.316 I normally stream my sats, but I forgot to top my fountain wallet off. 00:43:39.316 --> 00:43:42.466 So here's a boost. Since I'm here, I just want to let you know that I've been 00:43:42.466 --> 00:43:45.769 experimenting with a lot of self-hosted LLMs and Hermes thanks to you. 00:43:46.158 --> 00:43:50.456 Also bringing an old topic back, my password manager of choice is pass. 00:43:51.092 --> 00:43:53.193 Why no one has mentioned it? I don't know. It's the standard. 00:43:53.634 --> 00:43:55.556 I even recently set up a YubiKey to unlock the password. 00:43:55.556 --> 00:43:58.656 Very nice. Maybe we should take another pass and pass. 00:43:58.656 --> 00:44:03.021 Especially these days. Keep us posted on the local LLMs. And I'd love to know, 00:44:03.172 --> 00:44:05.215 CG, what hardware you're using too. 00:44:06.260 --> 00:44:08.056 Oh, hey, another boost here from 00:44:08.056 --> 00:44:15.618 Danja. I noticed this one says OpenCode somewhere in the boost metadata. 00:44:16.196 --> 00:44:19.484 Have some fries, guys. You sent me down the Muse rabbit hole this week. 00:44:20.296 --> 00:44:24.926 So this boost was sent via OpenCode using my Muse model via a custom OpenAI 00:44:24.926 --> 00:44:27.216 compatible wrapper and AlbiHub. 00:44:27.216 --> 00:44:27.681 Okay. 00:44:28.035 --> 00:44:28.406 Okay. 00:44:28.406 --> 00:44:37.896 So Muse is using the VM to drive open code where he has Boost CLI set up connected to his AlbiHub. Wow. 00:44:38.216 --> 00:44:42.096 Or I think, you see, maybe open code's talking to and controlling the Muse model. 00:44:42.576 --> 00:44:47.898 Oh, oh, oh, maybe. Plus AlbiHub also has like, you know, you can, yeah. Yeah, okay. 00:44:48.142 --> 00:44:51.576 All running via Nix on the free Muse compute. V0 is on my GitHub. 00:44:51.576 --> 00:44:55.276 Very much a rough proof of concept, but at least gets you SSH via tail scale 00:44:55.276 --> 00:44:57.157 and the OpenAI wrapper with a single prompt. 00:44:57.616 --> 00:45:01.610 Beautiful. That's got to be one of the nerdiest boosts we've gotten in a very long time. 00:45:03.014 --> 00:45:07.492 Well done, sir. Wow. Wow. Muse VMHacks. 00:45:07.492 --> 00:45:09.172 And it actually sent the stats. 00:45:09.172 --> 00:45:13.822 That's incredible. That's, think about the layers there. Think about the layers 00:45:13.822 --> 00:45:16.900 there. That's amazing. That's, that's great. 00:45:18.252 --> 00:45:21.962 I think we might have a live boost. We may want to include, or you want to include that? 00:45:21.962 --> 00:45:23.682 Oh yeah. Coming in hot right now. 00:45:23.682 --> 00:45:28.462 I think so. I don't know if Wes has the means, but we can continue here if you want to grab him. 00:45:28.462 --> 00:45:32.916 Bearded tech. It came in via the web boost. Why don't we grab while Wes pulls that. 00:45:33.578 --> 00:45:36.768 Why don't we grab Tech Geek, who came in with $25? 00:45:37.547 --> 00:45:38.662 Just cuz, he says. 00:45:40.662 --> 00:45:45.432 That's brilliant. Oh, man. That's good. Thank you. I appreciate you. 00:45:45.432 --> 00:45:47.042 I appreciate you. Thank you very much. 00:45:47.042 --> 00:45:48.437 Well, Wes is working away. 00:45:48.849 --> 00:45:50.242 Did I stall long enough for you to... 00:45:50.982 --> 00:45:53.662 Let's see here. Do we have it? I don't know if we do. 00:45:54.002 --> 00:45:57.032 Well, I can tell you the amount, and we can read the message in the next one 00:45:57.032 --> 00:45:58.137 if we want to be fair about it. 00:45:58.433 --> 00:46:03.193 Bearded Tech came in with a Spaceballs boost, one, two, three, four, five sats. 00:46:08.046 --> 00:46:12.243 Thank you, Bearded Tech. Appreciate you. And we'll have that message as well. 00:46:13.439 --> 00:46:14.932 Prosno Link? What do you think? 00:46:14.932 --> 00:46:15.692 Prosonic. 00:46:16.252 --> 00:46:22.031 Oh, that's way better. That's way better than what I said. They came in with $10. 00:46:25.159 --> 00:46:28.892 Boosting for Texas and the Muse episode. Ignored the corporate agents until 00:46:28.892 --> 00:46:31.592 the last episode. Signed up immediately, wondering like you guys, 00:46:31.592 --> 00:46:34.184 what can I actually do with all the positive things with this? 00:46:34.416 --> 00:46:35.962 Also, first-time booster. 00:46:35.962 --> 00:46:36.352 Nice. 00:46:36.392 --> 00:46:39.252 Like many, I came from self-hosted. And now I'm here for unplugged. 00:46:39.252 --> 00:46:40.772 Oh, thank you very much. 00:46:41.858 --> 00:46:46.892 Put that towards the Texas fund. Um, yeah, the idea of just free compute, 00:46:46.892 --> 00:46:49.792 like I'm not going to use it for anything super private, but it's also going 00:46:49.792 --> 00:46:53.312 to be interesting to watch how they try to compete and what they keep rolling 00:46:53.312 --> 00:46:54.577 out. You know, they're not done yet. 00:46:56.464 --> 00:47:01.282 Whereas the line came in with a free members boost, long time booster or long 00:47:01.282 --> 00:47:04.602 time member, first time booster. There you go. I got it. Thank you very much. 00:47:05.130 --> 00:47:07.822 Uh, as you react to the feedback about discoverability of the, 00:47:07.822 --> 00:47:10.782 boost your oil, I tried to find it. Now it's easy, so keep up the good work. 00:47:10.782 --> 00:47:11.172 Nice. 00:47:11.172 --> 00:47:15.632 All the talk about Jellyfin fits my home lab perfectly, as I'm simplifying to a true NAS. 00:47:15.632 --> 00:47:16.272 Uh-huh. 00:47:16.272 --> 00:47:19.184 Uh-huh. The free as x86 box for the... 00:47:19.817 --> 00:47:22.672 This frees a x86 box for the TV. 00:47:23.052 --> 00:47:26.592 I do sometimes just think life would be a lot easier if I just did x86 everywhere. 00:47:26.592 --> 00:47:30.916 Right. Yeah. It might not be exciting, but it might also work. 00:47:31.090 --> 00:47:32.414 X86 maxi over here. 00:47:32.877 --> 00:47:35.152 DeBrown Chico comes in with a member boost. 00:47:35.152 --> 00:47:36.418 Hey, another long-timer. 00:47:36.975 --> 00:47:39.263 Long-time supporters since the self-hosted day is here. 00:47:40.679 --> 00:47:44.608 I get the buzz around Omarchi and its million-dollar funding. 00:47:44.608 --> 00:47:47.368 I think it's like $21 million now or something like that. 00:47:47.728 --> 00:47:51.308 But the creator can be a bit polarizing. Could we maybe pivot the spotlight 00:47:51.308 --> 00:47:56.480 away from him and focus more on the tech itself, like the security and privacy of an agent-driven OS? 00:47:57.386 --> 00:47:58.715 Have we talked about DHH much? 00:48:00.368 --> 00:48:02.604 I think we've just mentioned some of the updates, mostly in the pre-show, though. 00:48:02.947 --> 00:48:07.308 Yeah, I think the comment this might be in response to, and maybe I didn't make 00:48:07.308 --> 00:48:11.328 the point well enough, is I think what I'm saying is remove the person, 00:48:11.328 --> 00:48:14.408 even remove the project and just ask yourself, why have they raised $22 million? 00:48:15.346 --> 00:48:19.018 And why haven't other projects raised $22 million? What is that? 00:48:19.018 --> 00:48:23.478 What is the signal? Now, that does require taking the emotions and putting it 00:48:23.478 --> 00:48:27.678 aside and just asking yourself, what signal could the free software world be 00:48:27.678 --> 00:48:32.458 taking who struggles to raise money, who struggles with funding every single day? 00:48:32.928 --> 00:48:36.928 Why was this project within three or four months able to raise $22 million? 00:48:37.659 --> 00:48:42.158 They just announced now, and it's just kicked off, three years of funding Hyperland 00:48:42.158 --> 00:48:43.298 development and a couple of other 00:48:43.298 --> 00:48:46.500 projects. And they have like a full-time staff of like five people now. 00:48:48.308 --> 00:48:52.098 So I think the question that we have to ask ourself is, what can we separate 00:48:52.098 --> 00:48:55.168 a signal from that and internalize? And that's all. I don't really think you 00:48:55.168 --> 00:48:57.268 have to talk about DHH much there. I don't think. 00:48:57.268 --> 00:48:59.518 Yeah, I think you're kind of aligned with maybe what the booster's asking. 00:48:59.518 --> 00:49:03.058 It may not have been a reaction. It might be sort of trying to express a similar thing. 00:49:03.058 --> 00:49:07.201 Yeah, I think we're on the same page then. Brett, you want to take DeckBot? 00:49:07.840 --> 00:49:09.976 DeckBot sends in a member boost here, 00:49:10.870 --> 00:49:16.658 Working on the back catalog and headed several listeners mention Automatic Ripping Machine. 00:49:17.298 --> 00:49:18.228 Yes, yes. 00:49:18.228 --> 00:49:20.358 We are the Automatic Ripping Machine show now. 00:49:21.358 --> 00:49:24.908 Well, I wanted to pile on and mention that I once got it running on an 8 gig 00:49:24.908 --> 00:49:32.005 Raspberry Pi 4 running Ubuntu server, a USB hard drive, and a USB Blu-ray drive. 00:49:32.399 --> 00:49:35.679 DVDs took about a week, and it never finished a Blu-ray. 00:49:39.598 --> 00:49:43.638 You know i can almost do a week it's a little slow but like who cares right 00:49:43.638 --> 00:49:48.350 you're just letting it go yeah but never finishing the blu-ray is a bit tough that's a bit tough. 00:49:48.560 --> 00:49:48.898 What were you. 00:49:48.898 --> 00:49:51.504 Saying you'll fall asleep halfway through anyway. 00:49:51.794 --> 00:49:57.078 Love x86 uh so last comes in uh with a member of boost hello jb trying this 00:49:57.078 --> 00:50:00.568 member boost thingy just to say thank you for the last 16 years you gotta be 00:50:00.568 --> 00:50:03.338 kidding me you gotta be kidding me is, 00:50:05.128 --> 00:50:09.108 that 2010 then listening to you literally got me from help desk into college 00:50:09.108 --> 00:50:12.368 into a wonderful career trajectory where i have used what taught me at what 00:50:12.368 --> 00:50:16.698 you taught me at every turn you guys make a real tangible difference never stop well thank you. 00:50:17.018 --> 00:50:17.538 Yeah thank you. 00:50:17.858 --> 00:50:21.638 You think it's cialis uh silas silas thank you silas very much i hope we get 00:50:21.638 --> 00:50:27.290 a chance to shake your hand one day 16 years is no joke that's uh older than two of my kids. 00:50:27.749 --> 00:50:33.198 Encoded member boosts in i've been a listener for two years and giving value back by joining as a. 00:50:33.198 --> 00:50:34.062 Member hey thank you. 00:50:34.674 --> 00:50:38.528 I look forward to listening to new episodes every week my two cents on clanker 00:50:38.528 --> 00:50:44.248 safety i have mine used trash cli and not rm and i found it helps also stating 00:50:44.248 --> 00:50:49.348 it in my clanker.md file can't wait to see y'all in austin at texas lunch fest. 00:50:49.348 --> 00:50:50.289 Cheers to that encoded. 00:50:50.422 --> 00:50:52.697 Yeah i like that trash cli is a good idea okay. 00:50:52.959 --> 00:50:54.228 Okay trash cli huh. 00:50:54.228 --> 00:50:57.548 Why not and you just sort of have a delete queue you can review it go delete 00:50:57.548 --> 00:50:59.718 things yeah put it on a schedule if you way safer. 00:51:00.538 --> 00:51:02.020 As long as they use it but yes. 00:51:02.358 --> 00:51:09.438 As long as that big uh caveat there well monty boosted a members boost clinker 00:51:09.438 --> 00:51:14.106 therapy volume two was great and i'm glad to hear there will be more coming, 00:51:15.395 --> 00:51:20.453 This week, Friday, check it out. This open code V2 with the server client setup 00:51:20.453 --> 00:51:24.486 and an API for the clanker is going to change the way I do projects. 00:51:24.695 --> 00:51:25.023 Yeah. 00:51:25.023 --> 00:51:29.433 Also like the idea of having the agent create a project dashboard for tracking 00:51:29.433 --> 00:51:31.780 progress. Thank you guys. 00:51:32.332 --> 00:51:35.683 Yep. Could use Zola for that too. Actually. You are onto it, 00:51:35.683 --> 00:51:38.703 Monty. You are in the right lane. You are in the fast lane, sir. 00:51:39.043 --> 00:51:42.823 Good luck with open code too. So worth it. Especially if you have a persistent 00:51:42.823 --> 00:51:45.079 system, you can leave it running on. It's great. 00:51:45.555 --> 00:51:48.313 Nefora92 comes in and says, thanks for the show. Thank you for being a member, 00:51:48.313 --> 00:51:51.337 Nefora. Thank you, everybody, who boosted. 00:51:52.163 --> 00:51:56.583 We have J-Moon, who came in with 1,999 sets, just below the 2,000 set cutoff, 00:51:56.583 --> 00:52:00.904 but wanted to recommend the self-hosted app Nostalgia TV, I think is it? 00:52:01.066 --> 00:52:03.473 Yeah, Nostalgia TV server on Docker Hub. 00:52:03.473 --> 00:52:06.263 Yeah, I saw this come in live, and I wanted to pull this one up. 00:52:06.263 --> 00:52:08.190 I thought this was great. It's a connector for Jellyfin. 00:52:08.590 --> 00:52:12.423 It generates a programmable schedule, but only plays the files directly from 00:52:12.423 --> 00:52:14.883 your Jellyfin library on demand to match the lineup. 00:52:15.869 --> 00:52:17.193 That's a really fun idea. 00:52:17.193 --> 00:52:18.963 Clever. Kind of minimal, clean. 00:52:18.963 --> 00:52:20.343 It kind of gets me my ersatz. Right. 00:52:21.118 --> 00:52:22.513 But without the ersatz. 00:52:22.513 --> 00:52:25.760 Yeah. But still gets you the TV guy jumping around thing. 00:52:26.143 --> 00:52:29.263 I understand that you're hating on Google TV right now, but a dedicated Android 00:52:29.263 --> 00:52:32.903 app can connect to the server or even run independently and works flawlessly 00:52:32.903 --> 00:52:38.600 on my on-branded 4K Pro, three gigabyte of RAM, 32 gig storage box from Walmart for $60. 00:52:39.227 --> 00:52:41.659 Now he got cut off. He said, combined with Pro something, and he got cut off there. 00:52:42.423 --> 00:52:44.903 J-Moon, I wanted to pull that up because that's a great tip there. 00:52:44.903 --> 00:52:48.573 And thank you very much. That might be just an easier route to go in the future. 00:52:48.573 --> 00:52:50.320 I'm going to definitely look into that. All right. 00:52:51.134 --> 00:52:53.474 Let's wrap it all up. You know this is going to be a good one. 00:52:53.926 --> 00:52:57.110 We had some really great boosts coming in. We started off with Blackhost coming 00:52:57.110 --> 00:52:59.950 in with that incredible baller boost. And, of course, Greg coming in with a 00:52:59.950 --> 00:53:01.630 nice big fatty McDuck and all of that. 00:53:02.111 --> 00:53:05.680 So thank you, everybody, who streamed sats. We had 10 of you stream sats. 00:53:05.680 --> 00:53:11.765 This has been tricking down slowly, but we still got 20,418. Thank you very much. 00:53:12.317 --> 00:53:16.830 When you combine it all together and you take the fiat boost, 00:53:16.830 --> 00:53:19.400 too, you convert them to current market sats. Get ready, boys. 00:53:19.400 --> 00:53:21.111 Are you ready? Get ready for this. 00:53:21.599 --> 00:53:28.940 We stacked a grand total of 1,363,320 Satoshis. 00:53:30.240 --> 00:53:30.473 Wow. 00:53:32.980 --> 00:53:37.212 We are going to Texas. We are going to have a meetup. That's my job this week is to get that sorted. 00:53:38.267 --> 00:53:39.787 Buy some extra comments. We're going to need them. 00:53:39.787 --> 00:53:43.017 Yeah. Let's keep an eye on the meetup page for that. Thank you, 00:53:43.017 --> 00:53:46.327 everybody. Boost.JupiterBroadcasting.com is how you can get a message in, 00:53:46.327 --> 00:53:49.942 send Sats or Fiat Fund coupons, or put your support on Autopilot. 00:53:50.523 --> 00:53:54.857 This year has been devastating financially, and your support has been the only 00:53:54.857 --> 00:53:58.047 thing keeping us going because the sponsors, they're kind of moving on. 00:53:58.047 --> 00:54:02.167 We've got a couple of nibbling these days, but we have dug ourselves quite the 00:54:02.167 --> 00:54:04.697 hole, And without you, we would not be here at all. 00:54:04.697 --> 00:54:08.207 And we're chugging in now on the 13-year mark. That's no small thing. 00:54:08.207 --> 00:54:11.717 And there's really only you out there as an audience that cares about a show 00:54:11.717 --> 00:54:14.323 like this. It's not going to be a mass market thing. Never will be. 00:54:14.538 --> 00:54:16.338 And we're totally happy as long as you're happy. 00:54:16.709 --> 00:54:19.240 And you can let us know at boost.jupiterbroadcasting.com. 00:54:21.102 --> 00:54:27.607 Wes, you found such a cool network troubleshooting visualizer for the TUI. 00:54:27.987 --> 00:54:30.587 I was wondering if you were going to find and notice this one. 00:54:30.587 --> 00:54:33.727 Oh, I noticed this one as soon as it came in. And I'm like, oh, 00:54:33.727 --> 00:54:36.707 yeah, we're doing this. Because I've actually been kind of trying to figure 00:54:36.707 --> 00:54:38.268 out an ideal Wi-Fi setup for me. 00:54:38.691 --> 00:54:43.086 So this is an app that gives you a live visual network path and diagnostics, 00:54:43.898 --> 00:54:49.667 that, I mean, how do you describe it? It's like it shows you kind of the path 00:54:49.667 --> 00:54:51.777 your data is taking and where it's hitting issues. 00:54:51.777 --> 00:54:58.927 Yeah, exactly. It's called WTFI2, or WhatTheFInternet, a live visual network 00:54:58.927 --> 00:55:03.926 path diagnostic that pinpoints exactly where your connection dies and tells you how to fix it. 00:55:04.396 --> 00:55:09.173 It's, I guess, actually a ground-up rewrite of the archived WTFI v1. 00:55:09.562 --> 00:55:12.993 The old version printed a flat checklist and left you to correlate it. 00:55:13.243 --> 00:55:16.987 This one draws a fancy diagram, streams every hop live, reasons about the root 00:55:16.987 --> 00:55:18.948 cause, so the answer is one line. 00:55:19.406 --> 00:55:22.677 Yeah, it has a very shiny little two-ie going on. Of course, it's written in Rust. 00:55:22.677 --> 00:55:23.580 Oh, of course. 00:55:23.923 --> 00:55:24.695 Ratatouille. 00:55:26.575 --> 00:55:27.493 It's written in Rust. 00:55:27.615 --> 00:55:31.353 It does seem like a nice place to start to, like, you're on some network, 00:55:31.353 --> 00:55:33.623 it's not working, you don't want to do a bunch of troubleshooting, 00:55:34.283 --> 00:55:37.573 answer a bunch of your first troubleshooting questions that you could run several 00:55:37.573 --> 00:55:39.619 different commands to try to get all at once. 00:55:40.774 --> 00:55:41.773 Is this the year of the TUI? 00:55:42.400 --> 00:55:43.009 Yes. 00:55:43.387 --> 00:55:44.063 It seems like. 00:55:44.063 --> 00:55:44.803 Every week. 00:55:44.803 --> 00:55:46.203 Well, don't rule out 2027. 00:55:46.203 --> 00:55:48.739 Every week we've got another great TUI app. 00:55:50.983 --> 00:55:51.723 This is incredible. 00:55:51.723 --> 00:55:55.173 You know, you were musing about local mail clients. 00:55:55.173 --> 00:55:55.432 Yeah. 00:55:55.606 --> 00:55:57.943 And I was thinking to myself when you're saying that, I think I would want a 00:55:57.943 --> 00:56:01.301 TUI if I was going to do that. Or I might, I might. 00:56:01.777 --> 00:56:06.193 Huh, huh. All right, well, let's break that trend with a full-on desktop application. 00:56:06.193 --> 00:56:10.903 Boys, we're going to talk about SpaceScan. And I admit I have a soft spot for 00:56:10.903 --> 00:56:15.183 these fast disk usage analyzers that actually visualize it in a decent way. 00:56:15.183 --> 00:56:18.973 And this one's called a Starburst chart, keyboard-driven, and it outputs in 00:56:18.973 --> 00:56:22.691 text, CVS, JSON as well. So if you want to throw it into something else. 00:56:23.312 --> 00:56:27.793 It's just really great fast disk usage analyzer with a sunburst chart and colors 00:56:27.793 --> 00:56:29.976 that mean something for space usage and things like that. 00:56:30.319 --> 00:56:33.243 Really easy to identify where all your space is either on your whole system 00:56:33.243 --> 00:56:34.197 or in your home directory. 00:56:34.551 --> 00:56:38.393 You can measure by bytes or number of files, and it takes pride in getting accurate 00:56:38.393 --> 00:56:42.283 numbers with support for fuse file systems over the network and things like that as well. 00:56:42.474 --> 00:56:46.788 Updates live as you go, filters by large things like ISOs, MP4s, things like that. 00:56:47.066 --> 00:56:52.193 Also accurate numbers, real disk usage like DU does, handle sparse files correctly, 00:56:52.193 --> 00:56:54.648 hard links, count ones, things like that, which is nice. 00:56:55.147 --> 00:56:58.663 And it says they have what they call safe cleanup. So you can move files to 00:56:58.663 --> 00:57:01.097 the trash or delete them permanently, always with a confirmation. 00:57:01.428 --> 00:57:06.503 SpaceScan refuses to delete anything that is or contains a mounted file system. 00:57:07.023 --> 00:57:07.453 Mm-hmm. 00:57:08.800 --> 00:57:10.089 I do like to let you clean it up too. 00:57:10.089 --> 00:57:13.089 Yeah, because you're already doing the work. That's why I have to go open some 00:57:13.089 --> 00:57:14.359 other thing just to go clean up 00:57:14.359 --> 00:57:16.380 the stuff, which is probably what you were looking for in the first place. 00:57:16.705 --> 00:57:19.997 I thought we should give a quick mention. This is a packed pick segment. 00:57:20.502 --> 00:57:25.389 We should give a quick mention to Vermouth, a lightweight Linux game launcher. 00:57:25.389 --> 00:57:28.359 It's really designed for the Plasma desktop, but would probably work on any 00:57:28.359 --> 00:57:30.788 desktop. It's native C++ and Qt. 00:57:31.293 --> 00:57:37.089 It lets you launch Windows games from Steam and GOG and Retro Games in a two megabyte app. 00:57:37.449 --> 00:57:42.529 Zero bloat kde first native yeah c++ yeah seems like if you just all you're 00:57:42.529 --> 00:57:44.796 looking for is nice launcher you're not kind of, 00:57:45.678 --> 00:57:48.729 what you want is something that works really well can use and find all your 00:57:48.729 --> 00:57:51.879 games and has a single place to launch them and get out of your way without 00:57:51.879 --> 00:57:55.409 a whole having to install you know games enough are already hundreds of gigabytes so. 00:57:55.409 --> 00:57:59.489 And there's folks that uh you know they want a plasma native feel when they're 00:57:59.489 --> 00:58:03.239 on the plasma desktop this would get to that too now normally i would spend 00:58:03.239 --> 00:58:06.299 a little more time on that app pick it does have. 00:58:06.299 --> 00:58:06.918 A flank too. 00:58:07.214 --> 00:58:12.809 Oh we do have to talk about this app pick it's kind of mandatory that we cover, 00:58:13.889 --> 00:58:20.530 one of these at least and uh this is part of a group of applications that have essentially re, 00:58:21.726 --> 00:58:26.609 cloned recreated the functionality of the adobe creative suite and this one 00:58:26.609 --> 00:58:34.978 is like raw mackies how would you say ramakasi ramakasi which is an open source lightroom replacement, 00:58:35.983 --> 00:58:41.648 And all of these are moving quick, and it even opens Lightroom files. 00:58:42.124 --> 00:58:45.629 It's a fast, non-destructive raw photo editor developed for Linux, 00:58:45.629 --> 00:58:48.969 macOS, and Windows written in all of these are written in Rust. 00:58:51.411 --> 00:58:59.353 And the UI, the UI not only looks like Lightroom, but if you were to take Lightroom 00:58:59.550 --> 00:59:03.439 and put it side by side with this application, it would look almost identical. 00:59:04.055 --> 00:59:08.722 And if you opened up a project file, all of the sliders, all of the color settings, 00:59:08.855 --> 00:59:11.593 everything is restored identical to the way it is restored in Lightroom. 00:59:11.977 --> 00:59:15.440 Yeah, it seems like that was basically the ask and a whole team of folks, 00:59:15.440 --> 00:59:20.150 mostly clankers, turn loose to go work on. although now there's been more contributors 00:59:20.150 --> 00:59:21.561 getting involved and kind of taking off. 00:59:21.788 --> 00:59:26.530 I couldn't help myself but to run this thing and you know nixos makes it so 00:59:26.530 --> 00:59:28.881 easy so you just get it going like nothing um, 00:59:29.880 --> 00:59:33.910 and i like chris you asked me like hey brent did you use lightroom you know 00:59:33.910 --> 00:59:38.510 when you were a professional photographer and that was the main piece of software 00:59:38.510 --> 00:59:42.616 that i used for most of my career because it was when it came around like, 00:59:43.731 --> 00:59:47.510 uh everybody was using photoshop which was pretty powerful doing digital. 00:59:48.680 --> 00:59:49.780 Corrections and things like that. 00:59:49.780 --> 00:59:54.500 You should have seen the automations and macros and stuff that us photographers 00:59:54.500 --> 00:59:58.295 were using. It was, let's say, a little bit. 00:59:59.359 --> 01:00:04.368 Clanky. And when Lightroom came around, it just completely changed overnight, 01:00:04.850 --> 01:00:06.975 the workflow that photographers took. 01:00:07.108 --> 01:00:13.799 And it was like, you can't do photography without it after having used it. 01:00:14.229 --> 01:00:18.875 So when I moved to Linux in about 2010, that's what I was looking for was like 01:00:18.875 --> 01:00:21.415 a perfect Lightroom replacement. 01:00:21.415 --> 01:00:24.495 And I used Darktable at the time, which is an amazing project. 01:00:24.495 --> 01:00:27.445 They do some really cool stuff, and I used that for many years. 01:00:27.445 --> 01:00:33.443 But this Remakase looks and feels exactly like Lightroom. 01:00:33.942 --> 01:00:39.045 It does, yeah. Like a one-to-one twin, almost. And Darktable did very close 01:00:39.045 --> 01:00:45.215 to that, but also had its own features and stuff that were very advanced and really cool. 01:00:45.215 --> 01:00:47.955 So there were some advantages there that Lightroom didn't have. 01:00:47.955 --> 01:00:53.946 But if you just want a one-to-one replacement that is very fast and really cool, 01:00:54.446 --> 01:00:55.585 this would be the way to go. 01:00:55.585 --> 01:01:00.344 And so I've got it loaded up here, and I've just been using it on some old photos that I had. 01:01:00.959 --> 01:01:03.105 It's sweet. It does an amazing job. I have zero. 01:01:03.865 --> 01:01:07.425 Like, I've only used it for 10 minutes, so, you know, bear in mind. 01:01:07.805 --> 01:01:11.915 But you should start here. Like, anybody who's just starting with Lightroom 01:01:11.915 --> 01:01:14.994 and hasn't used it before, don't use Remakase. 01:01:15.778 --> 01:01:18.345 You know, there's probably some bugs or whatever. but this is a great little 01:01:18.345 --> 01:01:22.407 piece of software. This is exactly what I wanted back in 2010 was like. 01:01:22.883 --> 01:01:24.595 Give me, this would have been huge right back then. 01:01:24.595 --> 01:01:29.305 Give me, yeah. Give me exactly the proprietary software, but don't give me the 01:01:29.305 --> 01:01:32.025 subscription and stuff and make it open source. 01:01:32.025 --> 01:01:37.185 So I could, you know, follow my ideals and contribute to like something that 01:01:37.185 --> 01:01:42.555 everybody can use. And this gets me thinking about like, is this the beginning 01:01:42.555 --> 01:01:44.890 of the end for proprietary software? Yeah. 01:01:45.737 --> 01:01:48.408 Well, they're going, I mean, this feels a bit like a statement. 01:01:48.884 --> 01:01:53.043 This is the quintessential, right? Because all of this, not that they, 01:01:53.043 --> 01:01:55.403 I don't know if they would have accepted it, but all this clanker time could 01:01:55.403 --> 01:01:58.590 have been spent on GIMP or Blender or Darktable. 01:02:00.443 --> 01:02:03.933 And again, just as a side comment, it does make me want to revisit that conversation 01:02:03.933 --> 01:02:07.733 one day that if these projects reject AI development, they're just going to 01:02:07.733 --> 01:02:10.523 get replaced so fast. So fast. 01:02:11.743 --> 01:02:15.083 But that's a separate conversation. I think also you have to consider Adobe 01:02:15.083 --> 01:02:18.023 is probably going to come after these people or try to. I don't know. 01:02:18.023 --> 01:02:20.856 It's open source. I mean, this cat is out of the bag. 01:02:21.419 --> 01:02:23.051 The Photoshop one is crazy, too. 01:02:23.515 --> 01:02:27.953 I think, too, we've already seen sort of fights over folks like relicensing 01:02:27.953 --> 01:02:31.483 their tests or making tests private. And this is sort of an output driven, 01:02:31.483 --> 01:02:37.163 right? Like try to build it and compare the two things and do a clean room implementation 01:02:37.163 --> 01:02:38.503 just from running the program. 01:02:38.503 --> 01:02:39.403 They do say it's a clean room. 01:02:40.199 --> 01:02:44.314 And I think it shows the power of that approach now that we can just grind against it. 01:02:44.732 --> 01:02:48.533 There is a double-edged sword to this type of project. And that is, 01:02:48.533 --> 01:02:50.810 it's moving really fast. 01:02:51.129 --> 01:02:52.935 The last commit was two hours ago on a Sunday. 01:02:53.318 --> 01:02:56.040 There's been 21 releases since September 26. 01:02:56.598 --> 01:02:58.705 There's been six in the past week. 01:02:59.643 --> 01:03:03.123 Substantial additions are coming in like batch export, experimental local AI 01:03:03.123 --> 01:03:04.851 mass, improved catalog handling. 01:03:05.344 --> 01:03:08.102 There's been Intel and NVIDIA driver fixes that have landed. 01:03:09.205 --> 01:03:12.313 most of it though is actually coming from the original developer there's been 01:03:12.313 --> 01:03:15.983 24 outside contributions that have been merged there's been plenty that are 01:03:16.343 --> 01:03:21.003 contributed but 24 that have been merged still early yeah like this one. 01:03:21.003 --> 01:03:22.723 Doesn't have a lot of support yet so there's still. 01:03:22.723 --> 01:03:28.048 Something one other important thing in the readme notes that before the 1.0 the file format, 01:03:28.959 --> 01:03:31.907 could change like how the edits render could change just as an FYI sorry go ahead. 01:03:32.227 --> 01:03:36.067 The other really cool thing about this is that they have the capacity to just 01:03:36.067 --> 01:03:41.337 import your Lightroom catalogs yeah I didn't get to test this because I had to scour very old hard. 01:03:41.337 --> 01:03:46.027 Drives to try to find find some and that's a killer. 01:03:46.027 --> 01:03:49.517 Feature because you just migrate quite quickly assuming you know it all works 01:03:49.517 --> 01:03:52.498 and stuff but very very thoughtfully implemented. 01:03:53.282 --> 01:03:56.197 What's neat too I think is right we can take this like I've already experimented 01:03:56.197 --> 01:03:57.996 a little bit with make myself kind of like a, 01:03:58.692 --> 01:04:02.477 version of you know kind of like instagram style filter editor for photos just 01:04:02.477 --> 01:04:05.077 because i didn't need the full stuff i just wanted basic stuff but you could 01:04:05.077 --> 01:04:08.357 now take you know they've got versions of a bunch of algorithms and filters 01:04:08.357 --> 01:04:11.003 and effects and capabilities that you could also take and, 01:04:11.474 --> 01:04:15.037 stick on mobile if you wanted or render in a web ui or you're not limited to 01:04:15.037 --> 01:04:18.428 making only using the clone aspect because it's mit licensed. 01:04:18.805 --> 01:04:21.767 The big ones i think we still need to see will we see an after effects will 01:04:21.767 --> 01:04:26.847 we see premiere pro will those come and how will we as a community feel because 01:04:26.847 --> 01:04:32.732 these are open source but they are essentially competing with acadian live or a blender. 01:04:32.853 --> 01:04:36.517 It also shows right that the other capability exists right proprietary folks 01:04:36.517 --> 01:04:40.767 can clone gpl we are we already seen stuff going gpl to mit with clones could. 01:04:40.767 --> 01:04:44.817 You even argue that because they sat on their butts and didn't do this themselves 01:04:45.143 --> 01:04:46.095 the market did it for them. 01:04:46.651 --> 01:04:49.316 There's that there is certainly there is certainly that interpretation. 01:04:49.508 --> 01:04:52.777 I wonder this is wild to me and i've also i haven't seen these yet But I've 01:04:52.777 --> 01:04:57.787 also read online that the, I think it's Word and Excel. 01:04:57.787 --> 01:05:00.067 I'm not sure about PowerPoint, but I think Word and Excel have essentially been 01:05:00.067 --> 01:05:04.927 cloned as well from the Office 365 versions of them as local apps that will run on Linux. 01:05:05.487 --> 01:05:11.547 Looks like VectorCraft. PJ and a few folks are linking that. So you're. 01:05:12.027 --> 01:05:13.527 What's VectorCraft? Is that the Office? 01:05:13.527 --> 01:05:17.439 Open source vector art tool. So Illustrator sort of thing. 01:05:17.637 --> 01:05:18.167 Wow. 01:05:18.978 --> 01:05:23.053 Yeah. Yeah, everything's getting cloned very quickly, so... 01:05:24.202 --> 01:05:24.817 Merry Christmas. 01:05:25.857 --> 01:05:26.969 99% Rust. 01:05:30.472 --> 01:05:31.604 Other 0.3. 01:05:32.881 --> 01:05:38.119 Yeah. Vectorcraft, Vector Illustrator, an open-source cleanroom implementation 01:05:38.119 --> 01:05:41.629 of Adobe Illustrator rebuilt in pure Rust, a fast open-source cleanroom take 01:05:41.878 --> 01:05:43.765 on Adobe Illustrator workflow. 01:05:44.444 --> 01:05:46.569 They're at least going to have to stop saying Adobe Illustrator. 01:05:46.569 --> 01:05:47.149 Yeah, that's good. 01:05:48.792 --> 01:05:50.557 Jeff, stop sending me. There's too many. 01:05:51.132 --> 01:05:58.559 Oh my gosh. it's it's a it's there's this is a thing you guys ah effect craft no after effects. 01:05:58.559 --> 01:06:00.343 It's just like compositing tool. 01:06:02.235 --> 01:06:06.159 No way they've done after effects. 01:06:06.554 --> 01:06:10.264 Okay why not i mean the start of it anyway right how how done is it. 01:06:10.769 --> 01:06:11.379 Should we just do a. 01:06:11.379 --> 01:06:12.371 Picture looks nice. 01:06:14.402 --> 01:06:20.869 Jesus coming so fast what's also crazy these all are supporting linux they're 01:06:20.869 --> 01:06:25.925 all open source they all support Linux they're all Rust which is interesting too but, 01:06:27.522 --> 01:06:31.161 holy crap Aftercraft like. 01:06:31.889 --> 01:06:37.483 On this Effectcraft 53 contributors right now like there are probably a couple robots in there. 01:06:37.977 --> 01:06:39.672 Hey this one supports FreeBSD too. 01:06:40.020 --> 01:06:41.454 So the last commit was three hours ago, 01:06:43.723 --> 01:06:47.869 they can create an application and improve it faster than their legal department 01:06:47.869 --> 01:06:49.509 even knows this is happening oh yeah, 01:06:51.752 --> 01:06:52.228 Wow. 01:06:55.193 --> 01:06:56.028 Totally slumped. 01:06:56.028 --> 01:06:59.098 Just a moment of silence for proprietary software. Yeah. 01:07:00.138 --> 01:07:04.798 Like, yikes. I mean, it's a new world. It is really wild. Like that's, 01:07:04.798 --> 01:07:07.649 Adobe is sort of like the quintessential moat. 01:07:09.327 --> 01:07:13.018 I mean, my mom has worked in the graphics industry for my whole life. 01:07:13.018 --> 01:07:16.636 Like I just imagine like telling her that she could just go use a free version of Photoshop now. 01:07:17.268 --> 01:07:20.258 And it's 95% feature complete at some point down the road or something. 01:07:21.138 --> 01:07:23.818 Most people only use 5 to 10% of the features anyway. 01:07:23.818 --> 01:07:26.754 I mean, some people are paying $1,000 a year for Creative Cloud. 01:07:27.473 --> 01:07:28.315 Not anymore. 01:07:28.565 --> 01:07:32.748 And when it's open source, and if you're a shop, you clone that down, 01:07:32.748 --> 01:07:34.308 and you clank in your own features. 01:07:34.308 --> 01:07:34.978 Right, of course. 01:07:34.978 --> 01:07:37.957 You clank in your own workflows. You clank in your own automations. 01:07:38.491 --> 01:07:39.693 And you just maintain your own fork. 01:07:40.698 --> 01:07:43.977 You can submit stuff if you want. You can keep it yourself. Whatever. 01:07:44.250 --> 01:07:48.658 This really is going to shake stuff up. And Adobe's going to have to fight this, 01:07:48.658 --> 01:07:49.985 but it's a futile effort. 01:07:50.809 --> 01:07:52.330 Because it's all MIT-licensed. 01:07:53.782 --> 01:07:54.821 You can clone it down now. 01:07:55.336 --> 01:07:56.228 A lot of people have. 01:07:56.228 --> 01:07:56.578 Uh-huh. 01:07:57.257 --> 01:08:01.768 Like, trying to replicate Photoshop is not a new thing, right? 01:08:01.768 --> 01:08:04.228 We've had the GIMP for decades now. 01:08:05.077 --> 01:08:09.558 But this happens, like, in a week now. You know? The GIMP has been around for 01:08:09.958 --> 01:08:11.298 decades trying to do this and 01:08:11.298 --> 01:08:14.497 adding features and stuff. This happens in a week, and it's done. Yeah. 01:08:16.914 --> 01:08:20.332 You can see why people that have been working on something for 30 years might 01:08:20.332 --> 01:08:21.342 hate something like this a little bit. 01:08:21.342 --> 01:08:23.050 Yeah, I could see that. 01:08:24.472 --> 01:08:28.822 I'm curious about sort of the engineering side of what the stack looks like 01:08:28.822 --> 01:08:32.492 to run the test to make it as automated as possible. Because there's a huge 01:08:32.492 --> 01:08:36.192 coverage, right? That's part of the power here is you can not only write the code, but... 01:08:36.302 --> 01:08:38.042 You can handle some of the commits that are coming in. 01:08:38.042 --> 01:08:41.342 And actually do all of the edge cases of exploring a UI like that. 01:08:41.342 --> 01:08:41.725 Yeah. 01:08:42.342 --> 01:08:45.272 There must have been a lot of that kind of testing. 01:08:45.469 --> 01:08:46.632 Automated ui testing. 01:08:46.632 --> 01:08:50.932 I'm sure because like you are not the human did not spec out the entirety of 01:08:50.932 --> 01:08:54.082 photoshop right like you had to discover that and then test against it probably 01:08:54.082 --> 01:08:56.732 as part of i'm just curious about that level of the harness set up. 01:08:56.732 --> 01:08:58.242 Test a lot of it automatically though. 01:08:59.109 --> 01:09:02.174 But you got to put in the work to build the stuff to make that all run smoothly. 01:09:02.713 --> 01:09:04.522 But once you've done that you could probably apply it to other. 01:09:04.522 --> 01:09:07.592 Applications exactly now you have a not maybe not fully generic but getting 01:09:07.592 --> 01:09:11.212 close to something like a useful machine to make software from other software. 01:09:11.212 --> 01:09:15.862 It's gonna be a wild year boys it's gonna be a wild year and And how long have 01:09:15.862 --> 01:09:17.112 people wanted Photoshop on Linux? 01:09:17.112 --> 01:09:19.972 And now it's here and I feel a little weird about it. I don't feel like it's 01:09:19.972 --> 01:09:21.622 not a total dubs for some reason. 01:09:21.622 --> 01:09:26.062 I don't know what it is, but it's both amazing. Like seemed like it was After 01:09:26.062 --> 01:09:28.732 Effects. Like I just assumed it's already happened. I thought that would not 01:09:28.732 --> 01:09:32.452 happen for a while. It's already happened. Like my mind keeps getting blown. 01:09:32.743 --> 01:09:36.002 And now I can have After Effects-ish on Linux. Are you kidding me? 01:09:36.002 --> 01:09:37.462 Like that could up our game. 01:09:38.159 --> 01:09:40.492 At the same time, like, I don't know, man. I don't know. 01:09:40.492 --> 01:09:45.322 It's a little weird. For these projects, I always love to dive into their agents 01:09:45.322 --> 01:09:48.372 MD if they've got it in the GitHub repo. Yeah, that's a good idea. 01:09:48.822 --> 01:09:53.632 And for EffectCraft, I think the first instruction is really important compared 01:09:53.632 --> 01:09:55.793 to Photoshop and the Adobe software. 01:09:56.368 --> 01:09:58.132 Number one, never crash. 01:09:59.122 --> 01:10:02.980 People trust after... Almost, geez, that was a Pavlovian. 01:10:03.328 --> 01:10:08.854 People trust EffectCraft with hours of work. Don't malform any... 01:10:10.050 --> 01:10:14.015 Any extensions, no bad expressions, no bad scripts. Don't break anything. 01:10:14.015 --> 01:10:19.605 That's the first, yeah, if only the proprietary software I did that a while ago. 01:10:19.605 --> 01:10:23.558 It's weird that you can kind of get a sense of the developer ethos through the agents file. 01:10:24.435 --> 01:10:24.679 Yeah. 01:10:25.195 --> 01:10:26.977 Number two, no Adobe artwork. 01:10:27.761 --> 01:10:31.275 Oh, yeah. Yeah, avoid that. Avoid the Adobe branding. What were you going to say there? 01:10:31.275 --> 01:10:34.175 I was going to say on that first one, when you build the harness to sort of 01:10:34.175 --> 01:10:36.275 do this testing stuff we were talking about, it also works for that, 01:10:36.275 --> 01:10:39.185 right? Because maybe now if you have programmatic control of your whole interface, 01:10:39.185 --> 01:10:42.035 you can do sort of fuzz testing against it, just trying to manipulate the UI, 01:10:42.035 --> 01:10:43.278 get into weird situations. 01:10:44.265 --> 01:10:44.996 That's my job. 01:10:46.314 --> 01:10:49.634 Yeah. Well, Brent, you still need somebody like you at the end of the day. 01:10:50.219 --> 01:10:53.726 I bet if you spent too much time with it, you'd probably find a couple of things. Something tells me. 01:10:54.550 --> 01:10:57.481 I still have faith in you. All right. Well, there you go. 01:10:57.923 --> 01:11:00.115 There's a lot in there this week, and we'd love to hear from you. 01:11:00.115 --> 01:11:03.365 Boost.JupiterBroadcasting.com We're just around the corner to Texas. 01:11:03.365 --> 01:11:08.385 And then don't forget, this Friday, October 16th, Clanker Therapy. 01:11:08.385 --> 01:11:08.535 Yeah. 01:11:09.015 --> 01:11:11.615 Number three, and we want to hear from you, answer your questions. 01:11:11.615 --> 01:11:14.575 Meetup.com slash Jupyter Broadcasting for the timing and all that. 01:11:14.575 --> 01:11:18.325 Yep, and uplink.jupyterbroadcasting.com for the voice note. Send us a voice 01:11:18.325 --> 01:11:19.192 note, about two minutes long. 01:11:20.115 --> 01:11:22.685 All right, before we get out of here, Wes, you want to give the power users 01:11:22.685 --> 01:11:27.195 any pro tips? Some secret sauce in the RSS feed? You got anything for us? 01:11:27.195 --> 01:11:30.795 Yeah, well, if you want to find out what we talked about or maybe get a summary 01:11:31.155 --> 01:11:34.315 or like find out which section of the show had that pick and what the name was 01:11:34.315 --> 01:11:37.385 because you kind of forgot, the VTT has all that. 01:11:37.385 --> 01:11:38.485 That's true. That's true. 01:11:38.485 --> 01:11:41.472 There's also chapters, which is like our attempt at a first take. 01:11:41.878 --> 01:11:44.035 And actually, really, it's not our attempt. It's Drew's take. 01:11:44.035 --> 01:11:44.815 That's why it's really good. 01:11:45.435 --> 01:11:48.545 Because you get Drew's interpretation of what we just did with the show. 01:11:48.545 --> 01:11:50.225 So that's a little extra metadata and flavor on it. 01:11:50.255 --> 01:11:53.086 If you've got a podcast app that supports chapters, which most of them do, 01:11:53.735 --> 01:11:55.005 take a look at it. He's usually got a funny one. 01:11:55.005 --> 01:11:55.935 Even if you don't need to jump away. Yeah. 01:11:56.155 --> 01:11:56.165 That's true. 01:11:57.335 --> 01:11:58.583 It's like a little extra. 01:11:58.700 --> 01:12:02.005 There's even an MP4 in that RSS feed, if you please, if you want to see a visual 01:12:02.005 --> 01:12:04.899 of what we talked about. And you can find out when we're live. 01:12:08.196 --> 01:12:11.694 You can make it a Linux Tuesday on a Sunday. Join us 10 a.m. 01:12:11.694 --> 01:12:15.301 Pacific, 1 p.m. Eastern over at jblive.tv. 01:12:16.183 --> 01:12:20.287 Or wherever you like to watch it, in your podcast app, on the YouTube. 01:12:21.489 --> 01:12:23.881 We don't care. We're just glad you're there. That's truly it. 01:12:24.450 --> 01:12:26.954 A podcast wouldn't be here if it didn't have listeners and viewers and if you 01:12:26.954 --> 01:12:27.967 didn't tell people about it. 01:12:28.350 --> 01:12:31.526 So thank you so much for listening to this here show. We really do appreciate 01:12:31.804 --> 01:12:33.749 you newcomers and you long timers. 01:12:33.975 --> 01:12:36.750 And, of course, our supporters, the boosters, and the members out there. 01:12:37.151 --> 01:12:40.071 Thank you so much for listening to this week's episode of Linux Unplugged. 01:12:40.390 --> 01:12:44.709 We'll see you right back here next Sunday, as in Tuesday, on a Sunday.