WEBVTT 00:00:11.159 --> 00:00:15.999 Hello, friends, and welcome back to your weekly Linux talk show. My name is Chris. 00:00:16.239 --> 00:00:16.939 My name is Wes. 00:00:17.219 --> 00:00:18.199 And my name is Brent. 00:00:18.539 --> 00:00:23.479 Well, hello, gentlemen. Coming up on the show this week, a simple network monitoring 00:00:23.479 --> 00:00:26.999 tool that does a lot more than just flag unknown devices. 00:00:27.459 --> 00:00:31.019 Then we're going to take things a step further using that data to detect family 00:00:31.019 --> 00:00:34.379 presence at home and trigger automations based on that. 00:00:34.719 --> 00:00:37.279 Then we're going to round it out with some great feedback, some boosts, 00:00:37.299 --> 00:00:38.979 some picks, and a lot more. 00:00:39.159 --> 00:00:44.459 It's a big show. So before we start, let's say time-appropriate greetings to our mumble room. 00:00:45.779 --> 00:00:51.219 Hello, Chris. Hey, Wes. Hello, Brian. Andrea. Happy New Year, by the way. 00:00:51.619 --> 00:00:52.059 Happy New Year. 00:00:52.059 --> 00:00:53.259 That's a strong crowd. 00:00:53.359 --> 00:00:55.919 Got a good group up there and quite listening, too. Hello, everybody. 00:00:56.099 --> 00:00:56.979 Thank you for joining us. 00:00:58.199 --> 00:01:02.779 Happy 2026. Can you believe it? It's our first episode. We're back. 00:01:03.039 --> 00:01:08.559 And I spent the holiday season building out the home lab. And I'm going to share 00:01:08.559 --> 00:01:11.099 just the tip of the iceberg this week. 00:01:11.379 --> 00:01:16.239 So let's start by saying good morning to our friends over at Defined Networking. 00:01:16.339 --> 00:01:19.719 Go check out ManageNebula at defined.net slash unplug. 00:01:19.939 --> 00:01:25.039 This is a decentralized VPN that's like no other. It's built on the Nebula project, 00:01:25.059 --> 00:01:27.519 which we trust. It's fully open, been around since 2017. 00:01:28.139 --> 00:01:33.459 Something you can really look at, go through, self-host the whole shebang from 00:01:33.459 --> 00:01:38.079 top to bottom. And I think this is something that I like to emphasize at this 00:01:38.079 --> 00:01:40.179 moment because it really makes Nebula stand out. 00:01:40.619 --> 00:01:45.239 Their free tier isn't competing with some other product that's going to eat away at their business. 00:01:45.479 --> 00:01:48.179 They're not trying to just do a sales funnel thing here. In fact, 00:01:48.279 --> 00:01:50.299 you could completely self-host all of the infrastructure. 00:01:50.579 --> 00:01:55.199 What's nice about the managed Nebula from Defy Networking is they take care 00:01:55.199 --> 00:01:58.639 of a lot of the infrastructure for you. But at any point, you can swap back and forth. 00:01:58.819 --> 00:02:01.919 You own the network, the identity, the routing, the control. 00:02:01.919 --> 00:02:06.639 It all stays with you. not a third-party control plane that you don't actually control. 00:02:07.119 --> 00:02:11.039 And Nebula's decentralized design means that there is no single point of failure. And... 00:02:12.355 --> 00:02:16.015 Not everybody accomplishes this, let me tell you from firsthand experience. 00:02:16.355 --> 00:02:20.315 And if you want to self-host the Lighthouse so that way you can do all of the 00:02:20.315 --> 00:02:23.875 node discovery, all of that is under your control. You absolutely can. 00:02:24.295 --> 00:02:28.035 Or hit the easy button and check out Manage Nebula. And you can get 100 hosts 00:02:28.035 --> 00:02:31.895 for free when you go to defined.net slash unplug. No credit card required. 00:02:32.175 --> 00:02:37.775 No lock-in. Just a fantastic open source product turned into a package that's easy for you to use. 00:02:38.555 --> 00:02:42.835 Defined.net slash unplug. Support the show. Go say good morning and check them out. 00:02:43.295 --> 00:02:46.735 And thank you to Define.net for sponsoring the Unplugged program. 00:02:49.071 --> 00:02:53.551 Now, just a touch of housekeeping to let you know about, Scale and Planet Nix 00:02:53.551 --> 00:03:01.611 are just around the corner, and Planet Nix's call for proposals closes January 15th. So get them in. 00:03:01.811 --> 00:03:04.431 Yeah, let's see, 11 days from when we record. 00:03:04.851 --> 00:03:08.951 You going to do one? You thinking about one? I mean, you could just kind of, 00:03:09.111 --> 00:03:12.451 there's so many things you tinker with, you could probably come up with a talk pretty quick. 00:03:13.151 --> 00:03:15.511 Well, now you've suggested it. So now I have to consider it. 00:03:15.551 --> 00:03:16.551 I don't know. Yeah, maybe. 00:03:16.851 --> 00:03:19.591 Well, you see, the only trade-off is always there's so much stuff we're always 00:03:19.591 --> 00:03:22.291 trying to do in the short time that we're there there's a lot of nicks to take 00:03:22.291 --> 00:03:23.431 in so you got to balance it. 00:03:23.431 --> 00:03:26.711 That is true yeah the event will have two parallel tracks that take place over 00:03:26.711 --> 00:03:31.211 two days speakers can submit proposals for talks or workshops or both and each 00:03:31.211 --> 00:03:34.151 day they're gonna have a mix of both talks and workshops and these are pretty awesome. 00:03:34.151 --> 00:03:37.171 Because you know sometimes what's happened before is someone from our excellent 00:03:37.171 --> 00:03:41.511 audience is given a talk at the same time my talk is at and that's oh. 00:03:41.511 --> 00:03:46.031 That's rough so we're talking march 5th through the 6th at Pasadena. 00:03:46.931 --> 00:03:49.711 You will want, the way that this works is you're going to want to register for 00:03:49.711 --> 00:03:52.131 scale and that gets you into Planet Nix. 00:03:52.571 --> 00:03:55.931 I'm hoping next week we'll have a promo code for you that'll take a nice little 00:03:55.931 --> 00:03:57.311 chunk of that registration off. 00:03:57.411 --> 00:03:59.731 We don't have it yet just because it's the holidays and, you know, 00:03:59.771 --> 00:04:00.771 they're just getting back to work. 00:04:01.091 --> 00:04:04.311 But it's my expectation that we'll have one for you soon and then you can sign 00:04:04.311 --> 00:04:05.311 up and you get a nice chunk off. 00:04:05.791 --> 00:04:08.411 And if you can make it to Planet Nix or just scale on the weekend, 00:04:08.571 --> 00:04:09.271 we'd love to see you there. 00:04:09.611 --> 00:04:13.871 We actually don't have it locked in that we're going to be there so at this 00:04:13.871 --> 00:04:19.071 moment in time don't base your travel plans on us base it on scale and if we 00:04:19.071 --> 00:04:22.291 can make it work if we can find somebody to help us get there and cover planet 00:04:22.291 --> 00:04:25.811 nix and scale then we are going to go with bells on, 00:04:26.929 --> 00:04:28.089 But that isn't locked in yet. 00:04:28.229 --> 00:04:29.089 A declarative belt. 00:04:29.229 --> 00:04:32.629 But it is an event we strongly recommend, both Planet Nix and Scale itself. 00:04:32.629 --> 00:04:35.729 And what's really great is this combo is at the same venue. 00:04:35.949 --> 00:04:38.929 There's some overlap there. So you can just kind of bang it all out at once 00:04:38.929 --> 00:04:42.189 and dip in from all. It's just great. It's a really nice setup. 00:04:42.269 --> 00:04:45.169 You get like a talk about a bunch of server. You get into Nix talk. 00:04:45.309 --> 00:04:47.569 You go learn more about Postgres. All in the same day. 00:04:47.729 --> 00:04:51.229 Go out to lunch. There's always, if you want to socialize, there's always opportunities. 00:04:51.329 --> 00:04:54.189 If you don't want to socialize, you don't have to. You can just be heads down 00:04:54.189 --> 00:04:57.369 and learn. It works for both the introvert and the extrovert, 00:04:57.369 --> 00:05:00.229 or if the introvert wants to flex their extrovert muscles for a couple of days. 00:05:01.429 --> 00:05:05.969 So check it out. We'll have a link, Planet Nix, 2026, March 5th through the 00:05:05.969 --> 00:05:09.029 6th in Pasadena Convention Center. Don't miss it. 00:05:12.889 --> 00:05:17.809 Gentlemen, if you'll indulge me, I'd love to tell you about my NetAlert X setup. 00:05:18.329 --> 00:05:22.549 Now, this is a network intruder and presence detector that scans for devices 00:05:22.549 --> 00:05:27.309 that are connected to your network and then alerts you if a new or unknown device is discovered. 00:05:27.829 --> 00:05:31.349 It's kind of handy, especially if you live in a neighborhood where people might 00:05:31.349 --> 00:05:34.189 be scanning Wi-Fi or, you know, you're just a little concerned. 00:05:35.729 --> 00:05:38.909 And it's not like a typical dashboard that you stare at. 00:05:38.989 --> 00:05:43.289 What it is is it's building a memory of your network. This is all local first. 00:05:43.429 --> 00:05:45.029 It's all self-hosted. It's open source. 00:05:45.269 --> 00:05:49.149 There's no account you have to create. There's no SAS brain processing it. There's no telemetry. 00:05:50.109 --> 00:05:53.769 Your network is essentially the way the design of network X is. 00:05:53.929 --> 00:05:59.469 Your network is a fluid moving thing where things change. 00:06:01.121 --> 00:06:05.881 Um, new things update and ports open, hopefully not a lot, but over the course 00:06:05.881 --> 00:06:06.981 of a year, these things happen. 00:06:07.321 --> 00:06:12.501 And the idea is, is that network X, we use multiple different network discovery methods. 00:06:12.501 --> 00:06:15.661 So not just like dumb pings, but all kinds of different methods. 00:06:15.661 --> 00:06:19.641 And there's a lot of plugins to enable different kinds and get an understanding 00:06:19.641 --> 00:06:24.941 of, okay, this device went from this IP to this IP. 00:06:25.341 --> 00:06:28.181 This device has been on your network for this amount of time. 00:06:28.501 --> 00:06:30.601 And you can go in there and you can assign devices to people. 00:06:30.601 --> 00:06:32.281 Well, there's a dashboard to help you do some of that if you want. 00:06:32.721 --> 00:06:36.961 Yeah, I'm interested to see that. You bring up this memory aspect because I 00:06:36.961 --> 00:06:39.101 got it set up. Oh, you did? I did, yeah. 00:06:39.301 --> 00:06:43.501 I was able to just pull it in as a container and have it just run as an OCI 00:06:43.501 --> 00:06:45.241 container on NixOS pretty easily. 00:06:45.581 --> 00:06:49.261 So we can have just a little basic config I'm using for that linked. 00:06:49.641 --> 00:06:53.901 But I've only just started, so I've got the initial setup of the devices that 00:06:53.901 --> 00:06:56.961 I've found, but I haven't used it long enough to see really things evolve yet. 00:06:57.101 --> 00:07:00.901 Right, because initially everything's new. Everything that gets detected is new and whatnot. 00:07:01.621 --> 00:07:04.721 It will also, as it learns more about your network, it'll start to kind of visualize 00:07:04.721 --> 00:07:09.141 what's connected to what node and kind of give you a rough layout of your network. 00:07:09.221 --> 00:07:10.121 Which is fun. That's exciting. 00:07:10.361 --> 00:07:13.021 And it's one of those things where you could put very little into it if you 00:07:13.021 --> 00:07:14.841 just – you want to know when things change. 00:07:14.981 --> 00:07:18.301 Or you can put more into it and you can tell this device is owned by this user 00:07:18.301 --> 00:07:19.481 and it's connected to this device. 00:07:19.481 --> 00:07:23.061 And a lot of times, you know, using MAC address lookup and whatnot, 00:07:23.181 --> 00:07:27.901 it'll identify the device in the manufacturer and it can categorize TV set-top 00:07:27.901 --> 00:07:31.681 boxes, Wi-Fi access points, smart plugs, PCs. 00:07:32.963 --> 00:07:36.223 Tablets it can it can figure a lot of that out on its own and then 00:07:36.223 --> 00:07:39.463 in a very kind of piehole style dashboard at the 00:07:39.463 --> 00:07:43.903 top it gives you how many devices are on your network how many new devices how 00:07:43.903 --> 00:07:47.643 many devices are down it's very it's like i almost wonder if they if the dashboard 00:07:47.643 --> 00:07:52.603 ui isn't actually forked from piehole but it works it's nice and you have that 00:07:52.603 --> 00:07:56.323 to look at and you could never take any further than that you could then if 00:07:56.323 --> 00:07:59.223 you wanted to you could hook it up to say telegram notifications. 00:07:59.603 --> 00:08:05.003 I hooked it up to notify or NTFY. And so when a new device that is unknown on 00:08:05.003 --> 00:08:10.103 my network shows up, I get a notify message sent to my phones to tell me about that. 00:08:10.843 --> 00:08:17.343 And they think when you, when you add the plugins, it really starts to get very, 00:08:17.483 --> 00:08:20.823 very powerful because if you have special devices on your network, 00:08:20.863 --> 00:08:23.723 or say you want to integrate home assistant, or you want to do these other things, 00:08:23.743 --> 00:08:26.363 like I mentioned pie hole, they have plugins for this. 00:08:26.523 --> 00:08:29.843 And so one of the sources of truth for my 00:08:29.843 --> 00:08:33.183 network alert x system is my 00:08:33.183 --> 00:08:38.723 pie hole via the api this is one of the plugins and what's so powerful here 00:08:38.723 --> 00:08:45.843 is now net alert x is in sync with my dhcp dns server so when i issue a new 00:08:45.843 --> 00:08:52.403 client lease or client lease expires or a new dns name shows up the two are in 00:08:52.543 --> 00:08:57.923 patico they know about it that kind of coordination so nice i. 00:08:57.923 --> 00:09:00.503 Just took a look and there's 45 available plugins. 00:09:00.503 --> 00:09:05.043 Yeah yeah yeah yeah any that jump out to you in particular i'm for me i ended 00:09:05.043 --> 00:09:09.303 up using one of the mqtt plugins obviously but yeah there's you know what i 00:09:09.303 --> 00:09:12.163 didn't see was a tectidium no i was taking. 00:09:12.163 --> 00:09:13.823 A look at what it would take to make one. 00:09:13.823 --> 00:09:14.363 Yeah because. 00:09:14.363 --> 00:09:18.523 There's definitely an api so i mean yeah there's a bunch of piehole and piehole 00:09:18.523 --> 00:09:22.403 api there's a specific support for pulling data out of Unify. 00:09:22.403 --> 00:09:26.543 If you have Unify systems on there, I think some Microtech or Microtech stuff as well. 00:09:27.592 --> 00:09:28.612 There's a lot of potential. 00:09:28.832 --> 00:09:31.572 Tiny in the chat room noticed there's a Prometheus endpoint, 00:09:31.572 --> 00:09:36.472 so you can have long-term retention of your data as well and just tie it into 00:09:36.472 --> 00:09:39.752 some of your existing alerting workflow, if that's your thing. 00:09:40.432 --> 00:09:42.992 So it sounds like pretty mature, considering. 00:09:43.512 --> 00:09:47.952 And I feel like it's already appliance level. You just set it up, 00:09:48.072 --> 00:09:50.832 and it does its working. It alerts me. 00:09:51.132 --> 00:09:54.172 And then using MQTT, I'm populating Home Assistant as well. 00:09:54.232 --> 00:09:57.192 So Home Assistant's aware of some of these things. But what I like about it 00:09:57.192 --> 00:10:01.432 is it's event driven. So it alerts, it logs, it feeds automations automatically. 00:10:02.312 --> 00:10:06.192 And you could think of it also as a bit of an event bus. So it has these different 00:10:06.192 --> 00:10:11.452 plugins like Notify and Home Assistant and MQTT and Prometheus and others where 00:10:11.452 --> 00:10:16.212 it's helping them stay current and up to date when they rely on network state information. 00:10:17.132 --> 00:10:21.192 This helps them with that. Like, did that speaker IP address change? Things like that. 00:10:21.432 --> 00:10:24.972 And it assumes that you might have a bit of a messy home lab. 00:10:25.012 --> 00:10:26.852 It's not a perfect network from the start. 00:10:27.132 --> 00:10:30.772 And it assumes there's going to be random ESP devices and things like that that 00:10:30.772 --> 00:10:33.532 it's going to need to figure out. Like, it goes in with that mindset. 00:10:33.952 --> 00:10:36.852 And then you have, once you're done, and it only takes you 20 minutes, 00:10:36.932 --> 00:10:38.332 10 minutes, depending on your configuration. 00:10:39.197 --> 00:10:42.957 comfortable comfortably with docker compose and your network layout you have 00:10:42.957 --> 00:10:45.817 something that tattles when your friends when your kids have a friend show up 00:10:45.817 --> 00:10:48.657 and they put their device on the wi-fi network you know about it it's that i love. 00:10:48.657 --> 00:10:52.157 I was impressed it was very easy to get started um 00:10:52.157 --> 00:10:55.177 working is i mean it is um containerized so 00:10:55.177 --> 00:10:58.777 that's nice you do need to put it in uh host networking right that helps which 00:10:58.777 --> 00:11:02.277 kind of obviously makes sense and i did do some poking around to look there's 00:11:02.277 --> 00:11:05.937 a lot of python so i gave it a quick stab just to see if i could get it building 00:11:05.937 --> 00:11:09.777 with nix uh there's a little too much going on oh yeah for me to like think 00:11:09.777 --> 00:11:12.717 it was worth it in time for the show but it would definitely be possible. 00:11:12.717 --> 00:11:13.517 Container that's probably. 00:11:13.517 --> 00:11:15.157 So the container i thought was easiest 00:11:15.157 --> 00:11:17.977 um but that said i mean it totally worked and all i really had to do, 00:11:18.477 --> 00:11:23.197 before it was actually like to get to minimum viable useful was just go in the 00:11:23.197 --> 00:11:26.197 settings and make sure it was scanning the right networks i actually cared about 00:11:26.197 --> 00:11:29.657 because by default and all it just wanted to scan was like the local container network. 00:11:29.657 --> 00:11:30.857 Ah yeah sure. 00:11:30.857 --> 00:11:34.397 So i just go say like oh yeah well this one is it could see my local name but 00:11:34.397 --> 00:11:37.277 land just tell it like oh yeah here's what you should go scan that's the one 00:11:37.277 --> 00:11:41.797 you care about yeah but even out of the box it auto detected like what the the 00:11:41.797 --> 00:11:44.577 internet connection was and a few things so. 00:11:44.577 --> 00:11:49.477 Net alert x sounds really amazing from an observation and alerting standpoint 00:11:49.477 --> 00:11:52.277 but i'm curious what happens next like okay you get alerted, 00:11:52.937 --> 00:11:57.817 does it have the means of i don't know tying into some ways of blocking some 00:11:57.817 --> 00:12:05.097 of these hosts or making some decisions or helping you automate some security? Did you get that far? 00:12:06.077 --> 00:12:08.957 That is the key question, right? Is now that you have this data, 00:12:09.177 --> 00:12:12.157 what do you do with it? Besides, I mean, just it is nice getting an alert on 00:12:12.157 --> 00:12:13.817 my phone. Oh, something new is on my network. 00:12:14.117 --> 00:12:19.497 And there is something nice to, I know other commercial products can do that, 00:12:19.557 --> 00:12:21.197 but I'm not using a commercial product. 00:12:21.357 --> 00:12:26.837 Nothing's leaving my private LAN or my mesh net. It's all getting processed locally. 00:12:27.726 --> 00:12:32.386 And the alerting even and the push notifications are all also happening locally. 00:12:32.526 --> 00:12:35.186 Yeah, that's a good point, right? It is something you might get with a fancier 00:12:35.186 --> 00:12:37.946 sort of, oh, I bought this commercial provider that just provides all of my 00:12:37.946 --> 00:12:40.266 network and routing and Wi-Fi all in one thing. 00:12:40.346 --> 00:12:44.246 And it has this fancy, you know, analytics for me. You get a little bit more of that. 00:12:44.726 --> 00:12:47.026 And especially for you, right, you're kind of tying together. 00:12:47.606 --> 00:12:50.946 The DNS side or the DHCP side kind of gives you one picture, 00:12:51.086 --> 00:12:52.326 but it's never really the complete picture. 00:12:52.406 --> 00:12:54.906 There might be devices that aren't doing that, have hard coded things that just 00:12:54.906 --> 00:13:00.446 skip some of that setup and having something that can do active ARP and even 00:13:00.446 --> 00:13:04.066 NMAP scans gives you a lot more capabilities to kind of fill in the blanks. 00:13:04.706 --> 00:13:09.386 But, you know, Brent brings up a great point. It's once you do have this information, 00:13:09.786 --> 00:13:11.326 could you take greater action on it? 00:13:11.406 --> 00:13:14.626 And I actually think that's where it gets really powerful. 00:13:14.806 --> 00:13:19.126 You could stop right here and just have really easy network observability and 00:13:19.126 --> 00:13:21.486 an easy way to alert yourself when something happens. 00:13:21.726 --> 00:13:25.506 But why not take that data and take proactive action based on it. 00:13:25.646 --> 00:13:27.926 And that's, I think, where it really gets powerful. 00:13:30.810 --> 00:13:36.390 Join crowdhealth.com and use the promo code unplugged. The health insurance process is confusing. 00:13:36.710 --> 00:13:40.670 It leaves me feeling like I was taken advantage of and it was extremely hard 00:13:40.670 --> 00:13:45.710 to navigate and even make an economically reasonable choice with my wife and 00:13:45.710 --> 00:13:47.030 I both being self-employed. 00:13:47.110 --> 00:13:49.510 And every year, the rates keep going up. 00:13:49.630 --> 00:13:53.150 And the system itself is fundamentally twisted. It's in the States, 00:13:53.150 --> 00:13:56.710 it's attached to employment, which is just really complicated. 00:13:56.870 --> 00:14:01.810 And honestly, some of us, like myself, have just opted out. 00:14:01.950 --> 00:14:05.250 And for over three years, I have been a member of CrowdHealth. 00:14:05.690 --> 00:14:08.850 Making informed decisions, especially about your health, isn't easy. 00:14:08.950 --> 00:14:12.950 And so it took me a bit of time and research before I came to this decision. 00:14:13.130 --> 00:14:16.570 But more than three years in, I'm really glad I did. 00:14:17.170 --> 00:14:21.270 CrowdHealth isn't regular insurance. It's not like that at all. 00:14:21.390 --> 00:14:25.170 It's a community of people funding each other's medical bills directly. There's no middleman. 00:14:25.430 --> 00:14:26.970 There's nobody constantly taking 00:14:26.970 --> 00:14:29.690 more and more profit. There's no networks that you have to be inside. 00:14:29.870 --> 00:14:33.610 There's just no nonsense at all. It's health care for under $100. 00:14:34.070 --> 00:14:38.610 That's CrowdHealth, the health insurance alternative. You get access to a team 00:14:38.610 --> 00:14:41.970 of health bill negotiators, low-cost prescriptions, lab testing tools, 00:14:42.030 --> 00:14:46.050 and a database of low-cost, high-quality doctors that have been vetted by CrowdHealth. 00:14:46.150 --> 00:14:46.890 They've worked with them. 00:14:47.070 --> 00:14:50.470 It's really smooth. They have a fantastic app to navigate it all, 00:14:50.670 --> 00:14:54.570 plus great customer service, people you can chat with on the phone or via text. 00:14:55.190 --> 00:14:59.650 And when something major happens, you pay the first $500 and then the crowd 00:14:59.650 --> 00:15:01.270 steps in and helps fund the rest. 00:15:01.850 --> 00:15:05.610 It's sort of like the options we used to have before it all got messed up and 00:15:05.610 --> 00:15:08.010 seemed to get worse every single year. 00:15:08.410 --> 00:15:12.530 So you'll join the crowd, a group of members just like me, who want to help 00:15:12.530 --> 00:15:14.590 pay for each other's unexpected medical events. 00:15:14.730 --> 00:15:17.670 And people are incentivized to take care of each other in this incentive and 00:15:17.670 --> 00:15:18.730 take care of themselves. 00:15:20.397 --> 00:15:22.597 The system's betting that you're just going to stay stuck, and you're just going 00:15:22.597 --> 00:15:25.717 to keep paying the same more and more overpriced, complicated mess. 00:15:26.377 --> 00:15:29.437 And this year, it's getting even worse because a lot of the subsidies are expiring, 00:15:29.617 --> 00:15:31.777 and so the costs are going to go up even more. 00:15:32.057 --> 00:15:35.877 So far, CrowdHealth members have saved $40 million in health care expenses because 00:15:35.877 --> 00:15:39.817 they refuse to overpay. I, myself, have saved somewhere around $3,200. 00:15:41.057 --> 00:15:44.417 It's really powerful stuff, and it's time to take your power back. 00:15:44.417 --> 00:15:49.317 Join CrowdHealth at joincrowdhealth.com and use our promo code unplugged today 00:15:49.317 --> 00:15:51.957 for your first three months at only $99. 00:15:52.837 --> 00:15:57.617 That's right. Joincrowdhealth.com promo code unplugged. CrowdHealth, it's not insurance. 00:15:57.857 --> 00:16:01.117 It's time to opt out and take your power back. This is how we win. 00:16:01.297 --> 00:16:05.237 It's joincrowdhealth.com and use that promo code unplugged. 00:16:07.777 --> 00:16:11.457 Chris Given, you were playing with this over the holidays, and I imagine that 00:16:11.457 --> 00:16:16.377 means you were in Lady Joops, and JOOPS is pretty much completely run by Home Assistant. 00:16:17.077 --> 00:16:22.037 Is that one of the ways that you're triggering some actions based on this information? 00:16:22.337 --> 00:16:25.817 It is, and I love the power of this. 00:16:26.097 --> 00:16:30.857 So let me give you just a quick diversion, if you will, boys, 00:16:30.877 --> 00:16:37.017 a quick story, and that is I wanted to refine the home and away automations. 00:16:37.597 --> 00:16:43.057 My goal was to trigger automations when the home is empty or if someone arrives home. 00:16:43.397 --> 00:16:46.677 And so, for example, maybe turn off our water pump so we don't have a water 00:16:46.677 --> 00:16:51.617 leak, turn off the lights, turn the heat down, arm and disarm the cameras, big one. 00:16:52.117 --> 00:16:56.777 And some of this I had in different dispersed automations where they came up 00:16:56.777 --> 00:16:58.597 with their own solutions to figure out the state. 00:16:59.955 --> 00:17:04.155 And some of it I didn't have figured out beyond using just like crappy, 00:17:04.175 --> 00:17:05.455 crappy scripts and whatnot. 00:17:06.015 --> 00:17:09.655 And then, of course, I wanted the ability to turn the lights on when we return 00:17:09.655 --> 00:17:15.395 home, turn the cameras off so they're not recording when we return home, when we enter the RV. 00:17:15.655 --> 00:17:21.035 And then also, ideally, start warming it up. So maybe even have like a five-mile radius zone. 00:17:21.175 --> 00:17:25.975 When we haven't been in that five-mile radius zone all day and we enter that, start heating again. 00:17:26.775 --> 00:17:31.975 And the complications in this are a little bit trickier than a standard home. 00:17:32.275 --> 00:17:36.835 Number one, JOOPS moves, so it can't just be based on location. That's going to break. 00:17:36.895 --> 00:17:38.355 You just like to make things difficult. 00:17:38.575 --> 00:17:41.715 And that kind of breakage sucks because it's the exact kind you forget you've 00:17:41.715 --> 00:17:43.115 set up in the first place. 00:17:43.275 --> 00:17:46.695 And then you go out on a trip, and you're like, oh, why isn't, oh, my God. 00:17:46.695 --> 00:17:50.295 It needs to be dynamic to take that into account from the start. Yeah. 00:17:50.615 --> 00:17:56.495 And I have made much, much, much work towards getting Joop's location aware. 00:17:56.695 --> 00:17:58.455 So she auto, so that would just, I can't do that. 00:17:59.435 --> 00:18:03.695 Can't be just Wi-Fi SSD because every now and then our home internet gets crappy. 00:18:03.695 --> 00:18:05.935 So we turn off the Wi-Fi on our phones or something. 00:18:06.175 --> 00:18:08.255 So you can't just be well if they're on the Wi-Fi, which would be, 00:18:08.355 --> 00:18:10.315 which would be another easy one if that works for you. 00:18:11.515 --> 00:18:15.995 And Apple has this technology called iBeacon. Ironically, I can't use it with 00:18:15.995 --> 00:18:18.095 Home Assistant and iPhones. You can with Android. 00:18:18.295 --> 00:18:20.795 So you could do something like Bluetooth presence awareness, 00:18:20.815 --> 00:18:23.915 but I can't because my kids are on iPhones and the wife. 00:18:24.175 --> 00:18:27.715 So I needed a way to do all of this presence awareness. 00:18:28.515 --> 00:18:31.015 And my wife and I are the only ones with the Home Assistant apps. 00:18:31.135 --> 00:18:32.955 The kids don't have the Home Assistant apps on their phones. 00:18:33.255 --> 00:18:36.215 So I needed something that even accounted for, say, we go for a walk around 00:18:36.215 --> 00:18:38.795 the property, but the kids are still home in the morning. I mean, 00:18:39.575 --> 00:18:41.975 I don't want the system to shut off on them. I need to know they're home. 00:18:43.295 --> 00:18:49.315 Well, this is where NetAlertX comes in because NetAlertX supports MQTT and Home 00:18:49.315 --> 00:18:53.575 Assistant integration, and it can supply a collection of stats such as the number 00:18:53.575 --> 00:18:56.675 of devices that are online to Home Assistant. 00:18:57.315 --> 00:18:59.855 And then in Home Assistant, with a little bit of work... 00:19:00.575 --> 00:19:03.955 You can turn on presence awareness and then assign them to persons. 00:19:03.995 --> 00:19:07.695 So I can say, when this device is on the network, consider this person home. 00:19:07.895 --> 00:19:09.195 It's really easy to do in Home Assistant. 00:19:10.435 --> 00:19:14.935 And the beautiful thing about this is their IPs can change, et cetera, 00:19:15.095 --> 00:19:18.395 but it's still associated to them and it knows when they're on the network or not. 00:19:18.475 --> 00:19:23.435 And it's supplying Home Assistant with a home or not kind of status. Very powerful. 00:19:24.135 --> 00:19:30.455 And there is a NetAlertX dashboard to assign, okay, this is my kid's devices. 00:19:30.575 --> 00:19:33.255 my wife's device so you can kind of sort all that out ahead of time and. 00:19:33.255 --> 00:19:35.835 Then that gets auto exposed i think you said via mqtt. 00:19:35.835 --> 00:19:36.475 Yeah and. 00:19:36.475 --> 00:19:38.575 Then that's what sort of sorts it through home assistant. 00:19:38.575 --> 00:19:40.435 I finally broke down yeah i. 00:19:40.435 --> 00:19:42.215 Mean we gotta you kind of burying the lead here. 00:19:42.215 --> 00:19:47.095 Yeah i have avoided this since i've home assistant set up since the very beginning 00:19:47.095 --> 00:19:49.595 so many things want to use mqtt you're. 00:19:49.595 --> 00:19:50.515 A broker bro now. 00:19:50.515 --> 00:19:53.915 But it's the native way that net alert x communicates with home assistant, 00:19:54.755 --> 00:19:58.915 and uh because it's an event-driven system they're just perfect for each other 00:19:58.915 --> 00:20:03.555 and the moment a device is detected it shoots it off over mqtt to home assistant 00:20:03.555 --> 00:20:08.375 home assistant is running the mosquito mqtt broker and immediately is aware 00:20:08.375 --> 00:20:10.475 of a state change it's just instant beautiful it's beautiful yeah. 00:20:10.475 --> 00:20:12.455 So did you is that like a plug-in you just added from. 00:20:12.455 --> 00:20:16.055 Home assistant for this one yeah yeah you could run mqtt uh 00:20:16.055 --> 00:20:18.955 server on anything right it could be i could run mosquito 00:20:18.955 --> 00:20:21.635 on anything but there is just a real easy add-on that integrates it 00:20:21.635 --> 00:20:24.495 all and if you use home assistant's add-on then it uses 00:20:24.495 --> 00:20:28.695 the home assistant authentication because a lot of mqtt brokers now you have 00:20:28.695 --> 00:20:31.795 to authenticate to and you have to go set up user accounts for but if you use 00:20:31.795 --> 00:20:34.655 the home assistant add-on it'll just use your local home assistant user database 00:20:34.655 --> 00:20:40.495 and so yeah that is that is a convenience so you set that up and let net alert 00:20:40.495 --> 00:20:42.095 x auto discover all your devices, 00:20:42.715 --> 00:20:47.435 they all then populate in home assistant as net alert x discovers them you set 00:20:47.435 --> 00:20:50.235 up a you don't even have to create a user account home assistant there's a difference 00:20:50.235 --> 00:20:51.195 between a user account and a, 00:20:53.221 --> 00:20:56.681 Then you add this device that's now being monitored by NetAlertX to their person. 00:20:57.861 --> 00:21:02.001 And then Home Assistant, when that shows them online, considers them home. 00:21:02.341 --> 00:21:07.441 And you can create all kinds of automations based on this because it consolidates 00:21:07.441 --> 00:21:10.081 it all down into your zone.home or whatever it might be called. 00:21:10.461 --> 00:21:14.061 And this just ends up being a counter of X amount of people home. 00:21:14.241 --> 00:21:19.741 So there's a default sensor, essentially, in Home Assistant that aggregates 00:21:19.741 --> 00:21:23.841 down the data of who's home into just a number. one person home five people home. 00:21:23.841 --> 00:21:26.481 Nice and then you can use that for even more downstream stuff. 00:21:26.481 --> 00:21:27.281 Yes oh. 00:21:27.281 --> 00:21:28.581 That's that's so great. 00:21:28.581 --> 00:21:34.141 It is so wonderful and seamless especially if you do a few niceties like in 00:21:34.141 --> 00:21:37.481 your automation maybe you had a five minute delay so when people leave you wait 00:21:37.481 --> 00:21:40.841 five minutes just in case there's like somebody dropping off for a bit and they come back, 00:21:41.481 --> 00:21:45.321 and when you do that it's so seamless to the family they every time they show 00:21:45.321 --> 00:21:48.621 up and right it's dark every time they show up all the lights are on for them 00:21:48.621 --> 00:21:52.321 the heat's been coming on and it's the water tongue like they don't even know 00:21:52.321 --> 00:21:54.861 the water's off while they're gone right nobody even knows it just it's all 00:21:54.861 --> 00:21:56.761 seamless to them ideally they. 00:21:56.761 --> 00:21:57.501 Never have to know. 00:21:57.501 --> 00:22:00.301 They don't have to worry like as soon as they come home the camera shut off 00:22:00.301 --> 00:22:03.841 so they're not getting recorded and i'm not getting a bunch of alerts and because 00:22:03.841 --> 00:22:08.021 home assistant knows people are home or not i can also just based i can say 00:22:08.021 --> 00:22:12.621 um for notifications i can say don't alert me on these things when someone's home oh. 00:22:12.621 --> 00:22:15.241 That is a nice extra detail to set as a flag. 00:22:15.241 --> 00:22:15.841 Right yeah i. 00:22:15.841 --> 00:22:17.221 Do not need to care about these things. 00:22:18.621 --> 00:22:19.401 It's so great. 00:22:19.681 --> 00:22:21.181 We're not in yellow alert mode. 00:22:21.341 --> 00:22:27.381 No. No, we don't need to be in armed mode, essentially. And there is actually, boys... 00:22:29.006 --> 00:22:32.026 An even easier way to do this, if you didn't want NetAlertX at all, 00:22:32.126 --> 00:22:35.046 but you still wanted all this fancy presence awareness I'm talking about, 00:22:35.886 --> 00:22:42.626 step one, set your clients to use a reserved address or set a static address for them. 00:22:43.246 --> 00:22:45.946 Remember iPhones and some Androids, they rotate their Mac address. 00:22:46.126 --> 00:22:48.386 You can go into the Wi-Fi settings for that particular AP. 00:22:48.546 --> 00:22:52.146 You can turn that off or set it to just a fixed Mac address that it generates. 00:22:52.626 --> 00:22:56.306 And once you have your family devices or your own devices, whoever it might 00:22:56.306 --> 00:22:59.106 be, on static IPs, the ones you want to track for awareness, 00:22:59.406 --> 00:23:03.966 there's actually a very simple ping integration that comes built into Home Assistant. 00:23:04.086 --> 00:23:07.466 You don't have to install anything, no MQTT, no additional NetAlertX, 00:23:07.866 --> 00:23:09.786 no crazy community add-ons. 00:23:09.926 --> 00:23:13.086 It's just built into Home Assistant integration called ping. 00:23:13.466 --> 00:23:18.086 And when you add it, it asks for the host IP that you want to ping or the name. 00:23:18.086 --> 00:23:22.586 and when the ping succeeds, Home Assistant considers that device home. 00:23:22.786 --> 00:23:25.566 And when the ping fails, Home Assistant considers that device gone. 00:23:25.726 --> 00:23:26.826 That is pretty simple and easy. 00:23:27.006 --> 00:23:30.926 Yep. And you can go into entities in there and you can, if you filter on disabled 00:23:30.926 --> 00:23:34.866 entities, you can actually turn on the device state tracker setting for the 00:23:34.866 --> 00:23:38.426 ping integration devices and then boom, you add them to your persons. 00:23:38.626 --> 00:23:42.246 And now it's very simple. It's very rudimentary. But if all you need is just 00:23:42.246 --> 00:23:44.906 to be able to ping their device and their IP doesn't change, 00:23:45.126 --> 00:23:49.066 you essentially get presence awareness and you can base all the automations 00:23:49.066 --> 00:23:50.626 around that, which is something that simple. 00:23:50.806 --> 00:23:52.186 And then maybe sub it out later if you need to. 00:23:52.706 --> 00:23:55.926 Yeah, it's so nice, right? Because you could then later go to NetAlertX and 00:23:55.926 --> 00:23:59.686 go a lot more sophisticated and do other kinds of things. But a simple ping 00:23:59.686 --> 00:24:00.526 integration could do it. 00:24:00.906 --> 00:24:05.906 Now, did you consider like an embedded Bluetooth tracker in yourself? 00:24:06.686 --> 00:24:07.026 Well... 00:24:07.657 --> 00:24:11.577 I did actually originally try to go the Bluetooth route. 00:24:12.257 --> 00:24:15.137 That felt just more passive, plus then it wouldn't need the network monitoring 00:24:15.137 --> 00:24:16.337 infrastructure, right? 00:24:16.517 --> 00:24:18.657 Because you could add a whole biohacking angle to this. 00:24:18.837 --> 00:24:21.457 That's true. Just put it in my arm. Or you don't need to. Everybody's walking 00:24:21.457 --> 00:24:23.557 around with phones and, you know, Bluetooth devices. 00:24:23.777 --> 00:24:27.697 And there is an ESP presence firmware project, I think based on ESP Home, 00:24:27.757 --> 00:24:29.077 that you can flash on an ESP. 00:24:29.297 --> 00:24:32.397 And then they're basically little Bluetooth monitoring nodes that you connect 00:24:32.397 --> 00:24:36.977 to Home Assistant. And it can even track the signal strength, 00:24:36.977 --> 00:24:41.097 essentially giving you what room they're in based on monitoring the other way. 00:24:41.417 --> 00:24:43.077 Oh, that is neat. 00:24:43.197 --> 00:24:45.397 That is neat, right? And you don't really have to do anything else other than 00:24:45.397 --> 00:24:46.597 just walk around with something that got Bluetooth. 00:24:47.977 --> 00:24:50.837 So I thought about that. In fact, I kind of wanted to put this out to the audience 00:24:50.837 --> 00:24:54.277 and ask them other ways to do this because I believe there's also hardware sensors, 00:24:54.637 --> 00:24:57.137 like millimeter wave hardware sensors you could do this with. 00:24:57.217 --> 00:24:58.917 You could probably do this with motion sensors. 00:25:00.037 --> 00:25:05.237 I like the network monitoring approach. This is working for us because it solves a couple of edge cases. 00:25:05.437 --> 00:25:09.737 But I wonder if if I supplemented it with another type of presence awareness, 00:25:09.757 --> 00:25:12.357 like a sensor of some kind, if I could make this even better. 00:25:12.717 --> 00:25:15.117 And so I'm putting the question out there to anybody in the audience, 00:25:15.257 --> 00:25:19.037 boost in and let me know if you've solved presence awareness in another way 00:25:19.037 --> 00:25:21.837 with a hardware detection of some kind or motion sensors, 00:25:22.097 --> 00:25:26.337 something I could add to this to kind of really refine and make sure no one 00:25:26.337 --> 00:25:28.437 is in the RV, not even a guest or anybody. 00:25:28.437 --> 00:25:31.517 right because that could be the edge edge edge case is 00:25:31.517 --> 00:25:34.377 a guest of somebody is over that i don't 00:25:34.377 --> 00:25:37.277 know about and for some reason they get left in the rv 00:25:37.277 --> 00:25:39.997 or maybe they're over house i 00:25:39.997 --> 00:25:42.637 don't know i don't know why i mean then they wouldn't have water and lights and 00:25:42.637 --> 00:25:46.477 heat so i gotta figure i gotta figure these edge cases out so boost and let 00:25:46.477 --> 00:25:50.877 me know if you have a way to solve that or go to linuxunplugged.com contact 00:25:50.877 --> 00:25:56.217 and tell me how you're doing it because right now i think that could be the 00:25:56.217 --> 00:26:00.277 gotcha and maybe I'm missing other edge cases too you can tell me about but 00:26:00.277 --> 00:26:01.217 I'm really happy with the results. 00:26:04.179 --> 00:26:07.799 Well, we don't have a sponsor here, but if anybody out there would like to sponsor 00:26:07.799 --> 00:26:11.699 the Unplugged program, we are in the process of finalizing ad deals for Q1. 00:26:12.179 --> 00:26:14.299 Email me, chris at jupiterbroadcasting.com. 00:26:15.099 --> 00:26:19.959 Best audience out there. Really great audience. And we can speak from some authority on the topic. 00:26:20.199 --> 00:26:22.579 We can speak from some authority on the topic. So let me know, 00:26:22.699 --> 00:26:28.019 chris at jupiterbroadcasting.com. I'd love to have somebody from the community sponsor the show. 00:26:28.339 --> 00:26:30.379 Wouldn't that be nice? That'd be really nice. 00:26:30.519 --> 00:26:31.199 That would be wonderful. 00:26:31.319 --> 00:26:31.779 Kind of give it back. 00:26:34.939 --> 00:26:37.319 Well, our dear Olympia Mike writes 00:26:37.319 --> 00:26:42.179 in with, I think, a rather big question here. Guys, I need your help. 00:26:42.419 --> 00:26:47.279 The next project is getting more and more attention and adoption, which is great. 00:26:47.619 --> 00:26:51.719 However, the question of how this project is licensed keeps coming up. 00:26:51.899 --> 00:26:56.179 I'll admit I'm a developer, not a lawyer, so I never paid too much attention 00:26:56.179 --> 00:26:58.439 to licenses and the nuances between them. 00:26:58.579 --> 00:27:03.919 I was just kind of assumed there was some proprietary or open license. 00:27:04.579 --> 00:27:08.979 I have people telling me, go MIT or unlicense, as it helps with adoption. 00:27:09.199 --> 00:27:12.739 But then I have other people telling me, you absolutely should go GPL. 00:27:13.319 --> 00:27:17.959 And others saying, well, use anything except GPL. On top of all of that, 00:27:18.139 --> 00:27:20.919 what can I even license in this project? 00:27:21.159 --> 00:27:23.939 It's mostly just Nix configs with some scripts. 00:27:24.499 --> 00:27:28.559 However, I am working on some Python and GTK apps to pair with it. 00:27:28.819 --> 00:27:32.419 Still, Nixbook relies on other projects to work almost entirely. 00:27:33.019 --> 00:27:36.519 I know you guys always mention how a project is licensed when you do the picks, 00:27:36.679 --> 00:27:41.319 and I guess it's a pretty boring topic, perhaps, but can you all shed some light 00:27:41.319 --> 00:27:45.099 on the differences and what a project like Nick's book should be under? 00:27:45.659 --> 00:27:48.939 Licenses feel like one of those super important topics we should care about, 00:27:49.099 --> 00:27:52.259 and yet, few people really understand them, so help. 00:27:52.779 --> 00:27:56.559 This is a big question, boys. And, you know, Olympia Mike's been working on 00:27:56.559 --> 00:27:57.979 this project for a while. We've watched it grow. 00:27:58.139 --> 00:28:02.259 It's really neat to see the way that these reclaimed, refurbished, 00:28:02.279 --> 00:28:05.239 you know, notebooks can be turned into systems for people that they still get. 00:28:05.359 --> 00:28:06.659 I mean, I'm using one still myself. 00:28:07.499 --> 00:28:11.339 It's a big question that I think really impacts perhaps future adoption the 00:28:11.339 --> 00:28:14.459 most. And how these things get shared is how I look at it. 00:28:14.939 --> 00:28:16.919 So I think that's the big consideration. What do you think, Wes? 00:28:16.959 --> 00:28:17.839 Am I missing something there? 00:28:17.839 --> 00:28:22.019 Well, there's also, like, as the Genesis... 00:28:22.826 --> 00:28:25.506 main chief maintainer one way to 00:28:25.506 --> 00:28:28.766 think about this is you know from mike's perspective 00:28:28.766 --> 00:28:31.626 like what what are you worried about what are you trying to protect 00:28:31.626 --> 00:28:34.926 for yourself and for downstream users 00:28:34.926 --> 00:28:39.386 or people who might want to either use the project directly or use the code 00:28:39.386 --> 00:28:45.166 and so one thing you check out is choose a license.com they've kind of got like 00:28:45.166 --> 00:28:47.826 a nice little it's not like everything that it's not going to answer the question 00:28:47.826 --> 00:28:50.206 for you but it kind of gives you some ways to look at the problem, 00:28:50.366 --> 00:28:51.946 it's a decent starting point. 00:28:52.286 --> 00:28:55.126 If you think about sort of MIT 00:28:55.126 --> 00:28:59.626 versus GPL as representative of the largest difference in terms of like, 00:28:59.666 --> 00:29:03.266 do you go with a copy left license like the GPL or do you go with an open source 00:29:03.266 --> 00:29:07.546 license that is more on the permissive side, like a BSD kind of license or MIT? 00:29:07.546 --> 00:29:10.186 There's more nuances there, but just to start with... 00:29:11.397 --> 00:29:15.377 One way to think about it is like if you're making like a library for a programming 00:29:15.377 --> 00:29:18.377 language, I'm going to make this utility that, you know, does X. 00:29:18.557 --> 00:29:20.777 It computes things. It draws a triangle, whatever. 00:29:21.377 --> 00:29:25.337 And you want that to be widely adopted. You want that just to be used by anyone. 00:29:25.337 --> 00:29:29.197 You want to make it easy to use yourself maybe in contracting work or just like 00:29:29.197 --> 00:29:33.217 to bring it into whatever person you're working for without having to worry about it. 00:29:33.817 --> 00:29:37.477 Then a permissive license makes all of that super easy, simple. 00:29:37.717 --> 00:29:41.117 So I think it does get used a lot for those kinds of things. 00:29:41.397 --> 00:29:45.217 For an end user application, or especially I would argue something that you 00:29:45.217 --> 00:29:47.317 think of maybe as like a commons application, 00:29:47.517 --> 00:29:50.737 like something like LibreOffice, where it's like, this is something you want 00:29:50.737 --> 00:29:55.097 people to have sort of by default as people who, you know, are using computers, 00:29:55.117 --> 00:29:57.817 they should have a way to use this, it should be theirs. 00:29:58.297 --> 00:30:01.997 That's where something like the GPL makes more sense. Now you might think, 00:30:02.117 --> 00:30:06.597 you might worry, one thing to consider then is, do you want people to be able 00:30:06.597 --> 00:30:09.397 to make proprietary things and not share the code? 00:30:09.857 --> 00:30:14.317 Right? They can sell GPL code, they can stuff, but you have to provide the source along with it. 00:30:14.437 --> 00:30:19.017 So are you okay imposing that on people downstream? Are you more concerned about 00:30:19.017 --> 00:30:23.077 the rights to have code for anybody using a Nixbook derivative? 00:30:23.357 --> 00:30:27.997 Or are you more worried about enabling people to build the next Chrome OS competitor or whatever? 00:30:28.517 --> 00:30:31.597 I was, yeah, to kind of double down on what you're saying there. 00:30:31.717 --> 00:30:33.437 It's like, do you want this to be a reference platform? 00:30:34.117 --> 00:30:37.837 Do you want this to be something the community takes over and builds on for 00:30:37.837 --> 00:30:43.237 you? and then you kind of take a supervisor role, do you want it resistant to capture maybe? 00:30:44.057 --> 00:30:48.617 And also, is it worth considering a split licensing, like MIT for the configs 00:30:48.617 --> 00:30:53.637 and GPL3 for apps that are created that are maybe like Python GTK apps and stuff 00:30:53.637 --> 00:30:56.317 like that? Brent, do you have thoughts on this question? 00:30:56.897 --> 00:31:02.117 Well, I think one of the things that becomes obvious here is don't rush into a license. 00:31:02.357 --> 00:31:06.077 Just because people are asking for it doesn't necessarily mean you have to choose 00:31:06.077 --> 00:31:09.277 one today. make an informed decision because you're going to be living with 00:31:09.277 --> 00:31:12.197 it for a while if you choose certain licenses. 00:31:14.157 --> 00:31:16.797 That said, your community has a huge amount of input, right? 00:31:16.897 --> 00:31:21.017 These are the people that are wanting to work with your code or maybe wanting 00:31:21.017 --> 00:31:24.377 to use your project, but they need some kind of license to make sure that it 00:31:24.377 --> 00:31:27.357 fits into their goals as well. 00:31:27.757 --> 00:31:31.857 Maybe one of the best ways to do it is go chat with other open source developers 00:31:31.857 --> 00:31:35.997 of projects that you use and love, or even some that are part of the Nixbook 00:31:35.997 --> 00:31:40.257 project, maybe upstream and see what their advice is. 00:31:40.457 --> 00:31:44.617 They have more experience with this than most of us do, and that would be likely 00:31:44.617 --> 00:31:46.417 a good place to start and start a good discussion. 00:31:46.817 --> 00:31:51.937 Yeah, I think too something maybe worth considering is this isn't really an 00:31:51.937 --> 00:31:55.057 open versus closed because you can make an argument for MIT or GPL. 00:31:55.177 --> 00:31:56.177 I think both camps are right. 00:31:56.357 --> 00:31:59.857 So I think maybe the way to frame this, Mike, and then take your decisions from 00:31:59.857 --> 00:32:03.697 there would be who benefits if this project becomes more successful down the 00:32:03.697 --> 00:32:05.877 road and who would benefit more than I expected. 00:32:06.497 --> 00:32:09.237 And just think about that and think about who you want to contribute. 00:32:09.557 --> 00:32:13.597 And I think that's the essence of what you have to get to to make your decision 00:32:13.597 --> 00:32:17.397 on the license because it's a hard choice to make. And I'd say both groups are technically right. 00:32:18.757 --> 00:32:22.097 And I do like the idea of chatting with some other Nix folks because a lot of 00:32:22.097 --> 00:32:24.537 this is based on Nix, right? So I think that's a great idea too. 00:32:25.777 --> 00:32:29.477 Good question. And there is an active discussion happening on GitHub, right? 00:32:29.617 --> 00:32:33.877 So we'll put a link in the show notes if people out there want to jump in and 00:32:33.877 --> 00:32:36.597 help them think about this. It's a hard choice to make. 00:32:36.757 --> 00:32:39.737 And I will also say, not to take away from that, 00:32:39.837 --> 00:32:43.857 but just also whichever way you go, it won't be the end of the world like it's 00:32:43.857 --> 00:32:48.237 still going to be open source and it almost some of this is academic to the 00:32:48.237 --> 00:32:52.677 folks who uh at least at the start are even just using it and benefiting it at the end of the day it. 00:32:52.677 --> 00:32:53.777 Is academic to the end users. 00:32:53.777 --> 00:32:57.377 I mean it is important i yeah it is very important but just you know like it's 00:32:57.377 --> 00:33:01.437 not even if ultimately you came to inclusion that you wasn't you viewed wasn't 00:33:01.437 --> 00:33:05.977 quite optimal in three years the consequences aren't going to be the end of the. 00:33:08.804 --> 00:33:12.604 Because once people start pestering you about the license, that means you have 00:33:12.604 --> 00:33:15.284 reached a certain level of success in adoption where it matters now. 00:33:15.784 --> 00:33:16.944 So true. Congrats, Mike. 00:33:17.364 --> 00:33:17.904 So true. 00:33:19.684 --> 00:33:20.204 Amen. 00:33:20.484 --> 00:33:20.644 Yeah. 00:33:25.504 --> 00:33:29.564 Well, boys, I'll start us off with our baller booster this week, 00:33:29.564 --> 00:33:31.784 and it is our podcast. He's back. 00:33:31.984 --> 00:33:34.004 Get ready for this, gentlemen. Brace yourselves. 00:33:34.504 --> 00:33:36.424 850,000 sats. 00:33:48.494 --> 00:33:52.094 Thank you, Eric. He says, hello, Chris, Wes, and Brent. Here's a little virtual 00:33:52.094 --> 00:33:54.054 stocking stuffer for my favorite Linux podcast. 00:33:54.574 --> 00:33:58.114 This boost is a little way for me to share the immense value LUP and self-hosted 00:33:58.114 --> 00:34:03.574 have provided me in my journey in self-hosting on my home server, powered by NixOS. 00:34:03.794 --> 00:34:04.194 Oh, yeah. 00:34:04.594 --> 00:34:07.634 One of these days, I'll get Boosy like going as my next achievement. 00:34:10.974 --> 00:34:16.634 Bonus, my wife's laptop, which is a Dell XPS 137390, is now running NixOS with 00:34:16.634 --> 00:34:18.274 Plasma, and she doesn't hate it. 00:34:19.034 --> 00:34:19.894 Sounds like a win. 00:34:19.894 --> 00:34:22.794 That is a win that is a win i i 00:34:22.794 --> 00:34:27.874 heard a opposite story over the holidays and they tried to uh get the significant 00:34:27.874 --> 00:34:32.774 other on linux desktop and did not go well so oh no not hating it is a definite 00:34:32.774 --> 00:34:36.554 win thank you eric we really really appreciate that it's a great way to start 00:34:36.554 --> 00:34:40.154 the new year and a great way to start our first episode of the new year thank you sir. 00:34:40.154 --> 00:34:45.774 Thumbs comes in with three hundred and thirty three thousand and two hundred cents. 00:34:45.774 --> 00:34:53.114 What are you serious not bad either boys thank you thumbs a. 00:34:53.114 --> 00:34:57.994 Long time no boost still trying my best to get caught up on episodes but there's 00:34:57.994 --> 00:35:00.294 so much amazing content in the members feed that it takes a. 00:35:00.294 --> 00:35:06.334 While yeah even at 2x speed it's a lot yeah I. 00:35:06.334 --> 00:35:09.314 Wanted to bring some holiday cheer to the team Thanks for all that you do every 00:35:09.314 --> 00:35:12.594 week to provide content that's not only educational, but entertaining. 00:35:12.954 --> 00:35:18.534 Also, a special shout out to Thumbs because Thumbs had to go through a bit of 00:35:18.534 --> 00:35:22.174 a process because we had liquidity issues on my node and Brent's node, 00:35:22.314 --> 00:35:23.394 and he worked with me over email. 00:35:23.514 --> 00:35:27.214 And I really appreciate him taking the extra time just to do the one-on-one. So thank you, Thumbs. 00:35:30.274 --> 00:35:31.474 That is some lightning love. 00:35:31.734 --> 00:35:34.034 That is. We really appreciate that. Thank you very much. 00:35:34.814 --> 00:35:38.394 Well, we have a kangaroo paradox here with a massive micboost. 00:35:38.714 --> 00:35:40.334 Two, that, two, two hundred. 00:35:40.954 --> 00:35:44.154 Two, what? That's a lot of twos. A lot of twos, basically. Six twos. 00:35:44.554 --> 00:35:47.754 Two hundred and twenty-two thousand, two hundred and twenty-two SATs! 00:35:52.022 --> 00:35:53.182 Wow. Thank you, Kangaroo. 00:35:53.662 --> 00:35:56.962 Kangaroo says, I love hearing about the JB community setups. 00:35:57.182 --> 00:36:00.422 I hope you guys revisit this content sometime in the future. 00:36:00.642 --> 00:36:02.222 Keep those home labs coming. 00:36:02.842 --> 00:36:06.662 This episode and the Nix configs were some of my favorite episodes as of late. 00:36:06.982 --> 00:36:08.942 Enjoy the holidays and thanks for all that value. 00:36:09.242 --> 00:36:12.642 I'm glad you enjoy it because I really like seeing people's setups and configs 00:36:12.642 --> 00:36:14.162 too. And I thought about it. 00:36:14.962 --> 00:36:19.042 What if, and this would be the only time I think we ever do this, but I have a crazy idea. 00:36:19.522 --> 00:36:23.502 And I know I always say this and we never do it. But what if we did a mid-year 00:36:23.502 --> 00:36:28.822 home lab just so that way we could work the kinks out one more time and that 00:36:28.822 --> 00:36:31.962 way when we go to do it in the winter, we've really got it figured out? 00:36:32.022 --> 00:36:36.662 Because part of the issue is we learn by doing and we do it once a year. 00:36:36.822 --> 00:36:40.182 And so that was our first go at it. And what we learned afterwards is we should 00:36:40.182 --> 00:36:43.982 have had the audience rate some of these and rank some of these because it became 00:36:43.982 --> 00:36:49.702 an emotional chore of unbelievable proportions because we love every single one of them. 00:36:49.702 --> 00:36:51.842 How do you bake the jewels out of a stack of all jewels? 00:36:52.102 --> 00:36:55.462 It was like not the problem we expected to have. And it was very hard. 00:36:55.702 --> 00:36:58.062 We wanted all of them to be winners. And we still felt like, 00:36:58.122 --> 00:37:00.422 can we do more? Because like we want to feature some that didn't make it on 00:37:00.422 --> 00:37:01.382 air because they're just so great. 00:37:01.702 --> 00:37:04.902 And so what we realized is we need to come up with a way for the audience to 00:37:04.902 --> 00:37:06.202 vote on them and be able to review them. 00:37:07.222 --> 00:37:10.302 And I'd like to just work the kinks out one more time. So I don't know. 00:37:10.422 --> 00:37:12.042 Maybe we could talk ourselves into doing an extra. 00:37:12.762 --> 00:37:17.402 But we'll see. Thank you, Kangaroo. I really appreciate the signal on those episodes. 00:37:17.522 --> 00:37:21.002 It's good for us to hear that too. So it gives us a solid direction to go. 00:37:21.622 --> 00:37:29.462 Well, look at this gentleman. The dude abides his back with 252,777 sats. Wow. 00:37:32.992 --> 00:37:37.052 How about that? Thank you, sir. That is amazing. Really appreciate that. 00:37:37.472 --> 00:37:39.792 He writes, it seems the fountain was having some troubles. Yeah, 00:37:39.832 --> 00:37:43.692 we were having troubles over the weekend. So I'm sending the rest via my Albi hub. 00:37:43.952 --> 00:37:46.292 Isn't it nice having your own self-hosted backup route? 00:37:46.492 --> 00:37:50.192 And so that is, in fact, why we should have flipped the last two in terms of 00:37:50.192 --> 00:37:54.272 proper boosts, ball of boost count here. But I kind of had to hand aggregate. 00:37:54.452 --> 00:37:57.632 Coming in with the hand math. It's all right. We appreciate that. 00:37:58.032 --> 00:38:00.712 He says, thanks for featuring my rack. I enjoyed the Homelab episode. 00:38:00.712 --> 00:38:03.812 I didn't think I'd win the Boosties since I'm already a member I'll pass the 00:38:03.812 --> 00:38:06.952 gift to someone else I'm already talking to Hybrid Sarcasm and we'll let you 00:38:06.952 --> 00:38:07.752 know probably next week. 00:38:07.872 --> 00:38:07.992 What? 00:38:08.152 --> 00:38:11.432 Happy 2026 Look at that initiative, appreciate it Amazing. 00:38:12.292 --> 00:38:16.052 And they're gonna gift it to somebody else. That's really cool And can you believe 00:38:16.052 --> 00:38:21.132 the dude won the Boosties and he's also already a member Thank you the dude abides That's. 00:38:21.132 --> 00:38:26.612 A lot of support Uphab comes in with 33,333 cents, 00:38:30.818 --> 00:38:34.798 Here's my prediction. Act one, PC component prices keep hiking. 00:38:34.998 --> 00:38:35.358 Oh, no. 00:38:35.578 --> 00:38:39.838 Personal computers become prohibitively expensive. Act two, the cloud is the 00:38:39.838 --> 00:38:42.998 only way to access decent processing power, and the companies hoarding hardware 00:38:42.998 --> 00:38:44.718 for AI become the obvious providers. 00:38:45.298 --> 00:38:49.178 Act three, the Microsoft 365 Link model takes off. 00:38:49.358 --> 00:38:54.118 AI companies finally become profitable, and personal computing is officially a thing of the past. 00:38:54.418 --> 00:38:58.938 Maybe not for 2026, but who knows? Let's hope never. Happy holidays. 00:38:59.838 --> 00:39:00.178 Wow. 00:39:00.358 --> 00:39:03.398 This is dark. Good holidays to you, too, there, buddy. Thanks, Pat. 00:39:03.498 --> 00:39:05.478 Well, it's a reminder of what we fight for on the show. 00:39:05.578 --> 00:39:05.918 It is. 00:39:06.038 --> 00:39:06.678 Which is not that. 00:39:06.898 --> 00:39:11.658 Yeah. I mean, yeah, I'm really feeling like I missed the boat by not building 00:39:11.658 --> 00:39:12.958 my HomeLab server last year. 00:39:13.738 --> 00:39:14.658 That's super dark. 00:39:14.858 --> 00:39:16.258 It is dark. It is dark. Hello, Neil. 00:39:16.258 --> 00:39:16.858 Also, hi. 00:39:17.078 --> 00:39:22.238 Hello, Neil. Hello. Hello. I hope that I'm hopeful that somebody comes along 00:39:22.238 --> 00:39:23.658 and says, we're going to get in the RAM game. 00:39:23.938 --> 00:39:26.718 And they, you know, get supply ramped up, at least by the end of 2026. 00:39:27.458 --> 00:39:32.758 I mean, I wound up panic buying a desktop because of this. i wonder how many others. 00:39:32.758 --> 00:39:34.318 Have yeah because. 00:39:34.318 --> 00:39:35.078 Like right now. 00:39:35.078 --> 00:39:38.998 Idea it's one of the best ways to get a machine with ram is just to buy a pre-built one. 00:39:38.998 --> 00:39:42.638 Yeah well i mean the last time i did this was 10 years ago and it was because 00:39:42.638 --> 00:39:45.558 of the hard drives are flooded and i want like the hard drive manufacturer i 00:39:45.558 --> 00:39:49.558 remember that right and it took like what three years for them to recover from that, 00:39:50.158 --> 00:39:56.118 uh and so i wound up buying a pre-built desktop pc last time too so i don't 00:39:56.118 --> 00:39:57.878 get to win here like Like, 00:39:58.798 --> 00:40:02.418 I mean, at least this time around, I actually managed to get a, 00:40:02.578 --> 00:40:07.598 right now, with a lot of the inventory that's still left from pre-insanity, 00:40:07.798 --> 00:40:09.878 you can get a pretty good deal. 00:40:09.878 --> 00:40:14.678 I got one where the desktop came with an NVIDIA 5090. 00:40:15.138 --> 00:40:26.938 It has 64 gigs of RAM and four terabytes of total NVMe storage for five grand with a... 00:40:28.331 --> 00:40:35.651 With a Ryzen 9 9550X3D or something like that. 00:40:35.811 --> 00:40:37.531 Storage alone is like $1,200 right now. 00:40:37.671 --> 00:40:40.551 Right, I know, right? I was like, geez, between the RAM and the storage, 00:40:40.611 --> 00:40:41.671 the computer paid for itself. 00:40:41.891 --> 00:40:42.951 Yeah, crazy. 00:40:43.851 --> 00:40:48.791 And then the CPU just adds a cherry on top. I mean, the computer's going to 00:40:48.791 --> 00:40:51.511 come with Windows, of course, because that's what happens with these things. 00:40:51.671 --> 00:40:54.771 But at least it's a reasonably powerful computer. 00:40:54.771 --> 00:40:58.491 it's made uh i can the the 00:40:58.491 --> 00:41:01.611 design of the computer is that the parts internally are not proprietary 00:41:01.611 --> 00:41:06.411 and they're easily replaceable uh so that means i did not buy a dell and uh 00:41:06.411 --> 00:41:11.851 it'll be fine right like i also don't really mess around with the desktop once 00:41:11.851 --> 00:41:15.691 i have it for a long time and it's just it's been time for a while for me to 00:41:15.691 --> 00:41:20.011 buy a new computer it's just i hate buying computers yeah i really i hate building. 00:41:20.011 --> 00:41:21.511 Them so that's just how it goes. 00:41:21.511 --> 00:41:27.211 All right good good news um Hybrid Sarcasm says, Gene Bean is the one getting the JB Party gift. 00:41:27.211 --> 00:41:29.511 No way, really? That's great. I love to hear that. 00:41:29.611 --> 00:41:30.851 That's great. 00:41:31.291 --> 00:41:34.371 Thank you for the update, Hybrid. All right, take PJ over there, Mr. Westpain. 00:41:35.091 --> 00:41:41.451 Oh, yep. The one, the only producer animated. Jeff comes in with 22,222 sats. 00:41:43.769 --> 00:41:48.629 All you Homelabbers are far more creative than I. Love to hear about it. Thanks. 00:41:48.829 --> 00:41:50.569 That's not true. That's not true. 00:41:50.569 --> 00:41:51.329 Jeff is very creative. 00:41:51.429 --> 00:41:55.369 Jeff was the only one whose Homelab is also attached to his Media Center PC, 00:41:55.509 --> 00:41:58.809 I believe, right? Maybe, as far as I know, is the only one. So that's pretty creative. 00:41:58.929 --> 00:42:02.709 That's a creative reuse of hardware right there, I'd say. All right? I'm impressed. 00:42:03.329 --> 00:42:09.069 Well, Tomato boosted in with a row of McDucks, 22,222 sets. 00:42:10.549 --> 00:42:15.149 Happy New Year, lads. Thank you for a great year of programming on Linux Unplugged. 00:42:15.729 --> 00:42:19.589 Lup is at the top of my queue when an episode comes out, and your quote-unquote 00:42:19.589 --> 00:42:23.889 worst episodes are still among my favorite podcast episodes this year. 00:42:24.189 --> 00:42:29.929 Here's to a 2026 full of independent Linux and open source content. 00:42:30.269 --> 00:42:33.489 Wait a minute. We have bad episodes now? Is that what I'm— Uh-oh. 00:42:33.649 --> 00:42:35.829 I guess nobody ever boosts in and says bad episode, do they? 00:42:35.869 --> 00:42:36.569 Well, actually, they do. 00:42:38.129 --> 00:42:44.429 Yeah. It does happen. Shabby Analyst comes in with 9,811 cents, 00:42:45.669 --> 00:42:49.689 says cheers to the new year and thanks for the great shows thank you thank you 00:42:49.689 --> 00:42:54.509 also to Tomato appreciate that oh look boys look who's back it's been a minute A.A. 00:42:54.529 --> 00:43:02.229 Ron's here with a row of ducks says my new year's resolution is going to be the year of Nixxar nice, 00:43:03.069 --> 00:43:07.349 as a DevOps engineer it's everything I want out of an operating system but I've 00:43:07.349 --> 00:43:10.769 been too afraid to really deep dive into it I'm currently in the middle of installing 00:43:10.769 --> 00:43:16.489 it on my daily driver with a heavy influence from configs from the config confessions episode. 00:43:16.909 --> 00:43:19.669 Me too. I was actually just referring back to that this weekend. 00:43:19.889 --> 00:43:22.149 So, ha-ha, this is Happy New Year as well. 00:43:22.249 --> 00:43:25.449 Yeah, maybe go join the Nixnerd's Matrix chat if you want to. 00:43:25.929 --> 00:43:26.589 Great advice. 00:43:27.349 --> 00:43:28.709 And let us know how it goes. 00:43:28.869 --> 00:43:31.849 Following examples helps a lot, too. It really does. All right, 00:43:31.869 --> 00:43:33.349 you want to take SWAT there, Mr. Payne? 00:43:33.409 --> 00:43:36.769 Oh, yeah, SWAT comes in with $5,874. 00:43:39.570 --> 00:43:43.550 cleaning out my fountain app wallet since i cannot seem to export or import 00:43:43.550 --> 00:43:46.290 or backup and restore the app with wallet and settings. 00:43:46.290 --> 00:43:46.890 But i'm. 00:43:46.890 --> 00:43:49.090 Moving to the new fairphone 6 oh. 00:43:49.090 --> 00:43:51.710 Well i'll tell you what the i guess you don't 00:43:51.710 --> 00:43:55.650 have it yet but the beta ui for the new fountain wallet uh has a secret thing 00:43:55.650 --> 00:43:58.570 in there that i can't tell you about yet but it also has a totally revamped 00:43:58.570 --> 00:44:03.190 import export trans transact really nice but whenever you send us your stats 00:44:03.190 --> 00:44:07.290 we appreciate it thank you for thinking of us and uh good luck with the fairphone 00:44:07.290 --> 00:44:09.130 would love to have a report on that. 00:44:09.630 --> 00:44:13.350 Always curious about Fairphone. Fairphone 6. Not the 5. 00:44:13.630 --> 00:44:14.030 Get it right. 00:44:14.570 --> 00:44:15.210 Yeah, not the 5. 00:44:15.530 --> 00:44:20.870 Well, Marcel boosted in a total of 19,232 SATs across two boosts. 00:44:20.990 --> 00:44:25.510 Hey! Wait a minute there. Thank you, Marcel. It's good to hear from you. Let's hear it. 00:44:26.771 --> 00:44:30.571 Marcel says, I hope you do the holiday home lab thing again, 00:44:30.591 --> 00:44:35.371 and I hope you add a category for a best dumpster rescue like Chris's final prediction. 00:44:35.771 --> 00:44:39.171 My submission was the NAS I found in the street and fixed up. 00:44:39.331 --> 00:44:43.671 I find it extremely satisfying to breathe new life into parts others give up on. 00:44:43.851 --> 00:44:47.371 I know I'm not alone because you mentioned this theme a few times with other 00:44:47.371 --> 00:44:51.051 submissions, but there was no dedicated category for it. 00:44:51.191 --> 00:44:54.631 Did the holiday home lab have something to do with that prediction? 00:44:56.191 --> 00:45:01.631 Hmm you know i i felt the vibe coming actually but the dumpster pc really was 00:45:01.631 --> 00:45:04.631 the definitive machine right we gotta we gotta pull that one up there's a few 00:45:04.631 --> 00:45:05.631 we should pull back out because. 00:45:05.631 --> 00:45:07.291 That really stood out to all of. 00:45:07.291 --> 00:45:11.931 Us yeah i mean talk about the definitive like reviving i make it into a home 00:45:11.931 --> 00:45:16.131 lab machine too it's just so good nice to hear from yourself and thank you for 00:45:16.131 --> 00:45:20.731 your submission and also thank you for the signal on the home lab episode hey gene beans here, 00:45:21.351 --> 00:45:25.031 with a row of ducks, 2,222 sats. And he says, happy new year. 00:45:25.271 --> 00:45:27.731 Well, happy new year to you, Gene. Nice to hear from you. 00:45:28.031 --> 00:45:29.271 And happy new membership. 00:45:29.571 --> 00:45:30.591 Yes. Enjoy. 00:45:31.791 --> 00:45:35.431 A scuffed comes in with 4,576 sats. 00:45:35.471 --> 00:45:35.831 All right. 00:45:36.591 --> 00:45:40.871 You teased a Podverse rebuild last week. Can you tell us more? 00:45:41.031 --> 00:45:45.931 Yes, I can. Very exciting news. In fact, Mitch, the lead developer, 00:45:46.071 --> 00:45:50.311 was just on the podcasting 2.0 podcast for the most recent episode as of last 00:45:50.311 --> 00:45:53.371 Friday. So that would be what, Wes? That would be the third? 00:45:53.591 --> 00:45:57.871 No, the second. So Friday the 2nd of January, you can go hear about the new 00:45:57.871 --> 00:45:59.511 Podverse rebuild. It's really exciting. 00:45:59.771 --> 00:46:02.911 They do need some help with the mobile development if anybody is interested. 00:46:02.911 --> 00:46:07.271 But what I love about Podverse is that it's a GPL 3, I believe, 00:46:07.411 --> 00:46:10.091 might be 2, but it's a GPL podcasting app. 00:46:10.331 --> 00:46:13.271 There's not a lot of those out there and even fewer that support all the 2.0 00:46:13.271 --> 00:46:16.311 standards, which are also open source. So it's really a nice combination. 00:46:17.471 --> 00:46:22.071 And Mitch has been working on this for a while. Podverse is also cross-platform, 00:46:22.131 --> 00:46:25.311 which makes it a little extra tricky. But it's pretty exciting to see it coming along. 00:46:26.251 --> 00:46:28.271 alpha.podverse.fm if you want to check it. 00:46:29.428 --> 00:46:32.788 Hey, did we get more from Gene? Is Gene Bean back? Coming in hot? 00:46:32.968 --> 00:46:34.508 Oh, yeah, now there's more Gene Bean. 00:46:34.788 --> 00:46:39.868 Yeah, 10,345 sats. I loved hearing from Kent. Is there a way to easily convert 00:46:39.868 --> 00:46:42.008 other systems to BcacheFS? 00:46:43.368 --> 00:46:46.968 That is something I want to do more of. I think you can convert Extended 4 and 00:46:46.968 --> 00:46:48.848 Butter. I'm not positive about Butter. 00:46:48.948 --> 00:46:50.328 Yeah, I actually have never converted one. 00:46:50.488 --> 00:46:53.268 Yeah, I think we should try it. I think we should try it. 00:46:53.588 --> 00:46:57.388 Gene also says, I noticed recently that my Raspberry Pi Home Assistant, 00:46:57.548 --> 00:47:00.528 it's Pi 4 with 4 gigs of RAM, was out of memory pretty often. 00:47:00.568 --> 00:47:05.228 So I upgraded to the Pi 5 with 8 gigs and was amazed at how good the restore 00:47:05.228 --> 00:47:07.168 from Nebukasa actually worked. 00:47:07.328 --> 00:47:11.148 It was super simple and everything came back as if nothing had changed. It was so slick. 00:47:11.488 --> 00:47:15.108 By the way, this boost amount is the Home Assistant port number, which is 8123. 00:47:15.288 --> 00:47:15.928 Oh, that's nice. 00:47:16.028 --> 00:47:17.028 Good touch, good touch. 00:47:17.548 --> 00:47:19.848 And nice to hear the experience report that went well. 00:47:20.028 --> 00:47:24.088 Yeah, the restore and backup features are kind of what make me want to use their 00:47:24.088 --> 00:47:26.908 whole Home Assistant package because they really do that well. 00:47:26.908 --> 00:47:30.508 Doornail 7887 comes in with a Rodex. 00:47:32.008 --> 00:47:36.588 100%. Signal is still the go-to cross-platform chat call app out there. 00:47:36.708 --> 00:47:40.368 I saw a couple of plus ones to that. People still really love and trust Signal. 00:47:40.568 --> 00:47:42.128 At least if you want to talk to our audience. 00:47:42.328 --> 00:47:43.068 Yeah, I guess so. 00:47:43.068 --> 00:47:43.608 Which you should want to. 00:47:43.908 --> 00:47:44.928 All right. All right. 00:47:45.888 --> 00:47:49.108 Well, there's a dude trying stuff here with a Rodex. 00:47:51.408 --> 00:47:55.908 Sadly, hardware shipping delays started piling up, and I was not able to make the deadline. 00:47:55.908 --> 00:48:01.808 who knew rack nuts came in multiple sizes rest assured i will link what the 00:48:01.808 --> 00:48:06.088 progress i've made in the new year really love the look uh at the community 00:48:06.088 --> 00:48:11.208 you all are consistently bringing together on the show happy holidays well. 00:48:11.208 --> 00:48:17.468 Thank you that's a nice same to you keep on trying stuff anonymous came in with 4035 sats, 00:48:18.841 --> 00:48:22.841 Altitude boost. If you want to know exactly where I'm at, add the current hour 00:48:22.841 --> 00:48:30.221 in your time zone to 42.42 north and subtract an hour in my time zone from 23.33 east. 00:48:30.581 --> 00:48:31.961 Use the time of the boost to the 00:48:31.961 --> 00:48:35.201 24-hour format. Extra points if you can pronounce the name of the place. 00:48:35.581 --> 00:48:39.021 Otherwise, Minimech might be able to help out. Hint. All right. Okay. 00:48:39.321 --> 00:48:39.721 So... 00:48:39.721 --> 00:48:40.581 Did you catch all that? 00:48:40.821 --> 00:48:45.021 Well, look, I do zip codes. I never signed up to be the altitude boost guy. Oh, come on. 00:48:45.021 --> 00:48:46.901 You can't figure that out? Come on. 00:48:46.901 --> 00:48:49.021 Well, isn't Brent the altitude? He's always been. 00:48:49.881 --> 00:48:50.801 No, these are coordinates. 00:48:50.821 --> 00:48:51.501 That's why we hired him. 00:48:51.501 --> 00:48:55.501 Wes, Wes, Wes. These are coordinates. So your little calculator on your map, 00:48:55.561 --> 00:48:57.081 that's exactly why you designed it that way. 00:48:57.141 --> 00:48:57.301 Isn't it? 00:48:57.401 --> 00:49:01.981 I mean, why did we go and spend $5,000 on your fancy map if it can't do this? 00:49:01.981 --> 00:49:03.061 What was that money spent on? 00:49:03.121 --> 00:49:06.881 Oh, well, that's because I own a piece of the company that makes them. 00:49:08.381 --> 00:49:09.921 So it's mostly kickbacks to me. 00:49:11.301 --> 00:49:12.721 Do you need a map upgrade? 00:49:13.221 --> 00:49:16.661 So, I mean, Minimac, did you catch this at all? 00:49:16.661 --> 00:49:20.041 did you says okay so it's 4035 sets 00:49:20.041 --> 00:49:23.401 and it's an altitude boost if you want to know exactly where i am at add the 00:49:23.401 --> 00:49:29.081 current hour in your time zone to 42.20 north and subtract the hour in my time 00:49:29.081 --> 00:49:35.301 zone from 23.33 east and use the time of the boost 24 hour format extra points 00:49:35.301 --> 00:49:39.621 if you can pronounce the name of the place you got any idea is is i. 00:49:39.621 --> 00:49:41.301 Think we have to take this as homework maybe. 00:49:41.301 --> 00:49:44.641 I mean try to come back next week do you think the machine could figure it out. 00:49:45.121 --> 00:49:45.961 It's worth a shot. 00:49:46.181 --> 00:49:49.701 Should I ask the machine? I mean, because we'll probably get a wrong answer. 00:49:49.861 --> 00:49:51.121 That feels like a roll of the dice. 00:49:51.281 --> 00:49:54.121 You know, often when you optimize, you have to start with a bad guess and then 00:49:54.121 --> 00:49:54.801 we'll get better guesses. 00:49:55.561 --> 00:49:58.321 We do have the time of the boost. I don't know if it's accurate, 00:49:58.461 --> 00:50:00.761 how accurate it is, but we have the Unix timestamp. 00:50:00.861 --> 00:50:02.961 Right, but that would be the time it hit the node, not necessarily the exact 00:50:02.961 --> 00:50:04.981 time it was sent. But here, I'm going to try the machine. 00:50:07.870 --> 00:50:15.250 Okay, here's what it says. The clues kind of point to, oh boy, Zurich, Switzerland. 00:50:17.030 --> 00:50:22.530 Zurich, which is roughly pronounced Tsu-kerik. Tsu-ri-k. Tsu-ri-k. 00:50:23.130 --> 00:50:24.410 You mean Zurich? 00:50:25.010 --> 00:50:26.990 Well, it says Tsu-ri-k. 00:50:27.130 --> 00:50:28.230 You're almost like, keep trying. 00:50:28.410 --> 00:50:33.610 Tsu-ri-k is how it says it's pronounced. It's T-S-O-O dash R-I-K-H is how you pronounce it. 00:50:33.890 --> 00:50:37.110 And it's got some information about umlauts, but that's lost on me. 00:50:38.690 --> 00:50:40.850 Just say Zurich like a normal person. 00:50:41.110 --> 00:50:45.030 Well, it says to Zurich is how you're supposed to say it. Not Zurich, 00:50:45.090 --> 00:50:46.210 but I don't know if that's right or not. 00:50:46.710 --> 00:50:49.610 There you go. That's my guess based on what the machine told me. 00:50:49.750 --> 00:50:51.990 But that's a pretty big roll of the dice. 00:50:52.290 --> 00:50:55.350 We're going to have to tool up so we can handle these more. 00:50:55.490 --> 00:50:55.990 Yeah, clearly. 00:50:56.330 --> 00:50:59.810 I'm thinking like a big 3D globe sort of we have on the desk. 00:50:59.990 --> 00:51:03.150 Yes. Yes. With like things we can project onto it. 00:51:03.170 --> 00:51:03.370 Uh-huh. 00:51:03.510 --> 00:51:03.770 Yes. 00:51:03.970 --> 00:51:06.250 Spin it around and zoom in, zoom out. 00:51:06.250 --> 00:51:08.770 There's got to be a movie set somewhere where we can get that from, 00:51:08.930 --> 00:51:10.230 like a war planning movie set. 00:51:10.410 --> 00:51:12.310 When you unfold that, Wes, does it sound differently? 00:51:12.750 --> 00:51:15.590 Oh, yeah. It's more like an EV kind of sound, you know? 00:51:16.170 --> 00:51:17.630 All right, let's round it out with Moon Knight. 00:51:20.270 --> 00:51:24.750 10,101 sats. My prediction for 2026 of the Linux adoption on the desktop goes 00:51:24.750 --> 00:51:29.990 exponential, thanks to Steam machines and gamers overall getting sick of Windows. 00:51:30.470 --> 00:51:33.350 6% of Linux users are on Steam now, according to their own metrics. 00:51:33.950 --> 00:51:35.610 I'll say it's double what it is today. 00:51:35.610 --> 00:51:37.810 Well, I hope that happens. 00:51:37.830 --> 00:51:39.810 I hope so. I do feel like there is more. 00:51:40.090 --> 00:51:44.330 I think I discounted the Windows dissatisfaction more than I should have. 00:51:45.330 --> 00:51:48.610 So there is that. I hope you're right, Moon Knight. I hope you're right. 00:51:49.090 --> 00:51:52.690 All right. I'll take this last one just to finish this up here. Are you ready for this? 00:51:54.250 --> 00:51:58.090 Starfleet Computer Scientist boosts in with 17,514 sats. 00:52:00.889 --> 00:52:04.109 And this was also their first boost ever. 00:52:04.609 --> 00:52:06.729 Congratulations. Nice. Welcome to the club. 00:52:06.929 --> 00:52:11.029 Thank you for getting that set up. That is not a small task, 00:52:11.029 --> 00:52:12.169 and we appreciate you doing that. 00:52:13.789 --> 00:52:17.609 They write, long-time listener, first-time booster. I listened back in last, 00:52:17.749 --> 00:52:19.549 and the faux show, and of course, beer is tasty days. 00:52:20.169 --> 00:52:23.289 Rediscovered Linux Unplugged about a year ago. Became a core contributor this 00:52:23.289 --> 00:52:26.729 year, and after decades of using Linux on a secondary machine, 00:52:26.869 --> 00:52:28.749 finally made the switch on my primary one. 00:52:28.909 --> 00:52:32.389 Keep up the great work. I don't know if this is a thing, but please accept this 00:52:32.389 --> 00:52:34.149 as an Enterprise D boost. 00:52:34.529 --> 00:52:34.889 Nice. 00:52:35.489 --> 00:52:36.449 1704. Aha. 00:52:37.329 --> 00:52:38.529 It's absolutely a thing. 00:52:38.689 --> 00:52:39.349 Nicely done. 00:52:39.489 --> 00:52:42.189 See, I can take those too, that kind of boost where I can easily process. 00:52:42.529 --> 00:52:46.029 Ah, yeah. Well, come in and strong with your first boost. 00:52:47.089 --> 00:52:50.289 Speaking to our Star Trek love. And also, thank you for the long time. 00:52:50.389 --> 00:52:51.509 Listen, I'm glad you're back on board. 00:52:52.069 --> 00:52:54.649 I think, you know, once you're over a year, you're no longer a noob. 00:52:54.969 --> 00:52:57.929 I think, did we decide that? Just over a year, it's no longer a noob. 00:52:58.609 --> 00:53:02.769 This was a banger. We combined some boosts from this week and the week when we were off. 00:53:02.929 --> 00:53:06.689 So that's why there was a lot and a mini boost to get through this week. 00:53:06.829 --> 00:53:09.349 So next week will probably be a little tighter and shorter. So if you would 00:53:09.349 --> 00:53:11.189 like to support us, it would be a great week to step up. 00:53:11.389 --> 00:53:14.769 We had 22 people stream sats as they listened to us. 00:53:14.929 --> 00:53:17.949 Look at these maniacs here. Thank you very much. They just put it on autopilot 00:53:17.949 --> 00:53:22.669 and collectively they stacked 34,665 sats. 00:53:22.829 --> 00:53:27.069 Not too bad at all. Thank you, everyone. When you combine that with our boosters, 00:53:27.329 --> 00:53:32.269 this episode, episode 648, stacked a grand total of 720. 00:53:32.269 --> 00:53:33.969 You got to go farther. Sorry. 00:53:34.149 --> 00:53:37.169 Oh, I got to go down further. You're right because we have the combo from the previous week. 00:53:37.409 --> 00:53:40.589 Right. So we actually stacked more than that. Thank you, Wes. Good catch. 00:53:40.789 --> 00:53:48.989 We stacked a grand total for both episodes of 1,826,819 sats. 00:53:49.869 --> 00:53:52.769 Wow. Thank you, everyone, very much. That's incredible. 00:54:03.287 --> 00:54:06.127 And that matters more than you might know, because those of you paying attention 00:54:06.127 --> 00:54:09.747 might know that it is the beginning of the new year. Our sponsorship contracts 00:54:09.747 --> 00:54:10.807 are under renegotiation. 00:54:11.007 --> 00:54:15.627 We don't have a full boat at all. And so the memberships and the boosts actually 00:54:15.627 --> 00:54:18.067 make all of the difference right now. 00:54:18.207 --> 00:54:21.447 Not just a little bit, not some of the difference, all of it. 00:54:21.527 --> 00:54:23.227 So thank you, everyone, who supported this episode. 00:54:23.387 --> 00:54:26.187 You literally made it possible, either through a membership or a boost. 00:54:26.467 --> 00:54:29.907 And it means a lot to us, because we love doing this, and we want to show up 00:54:29.907 --> 00:54:33.627 every single week and keep making Linux Unplugged for you. We really do appreciate it. 00:54:35.508 --> 00:54:38.968 All right, I got a couple of picks that are going to be kind of obvious why 00:54:38.968 --> 00:54:40.928 I'm including them this week. They are on theme. 00:54:41.648 --> 00:54:44.088 First two I'll get through pretty quickly in case you don't care about. 00:54:44.208 --> 00:54:48.768 They are two different options for figuring out MQTT. 00:54:49.088 --> 00:54:53.568 If you're new to MQTT and you don't know really what it is and what it does, 00:54:54.248 --> 00:54:59.708 these are toolboxes that will let you listen in to a topic from MQTT and see 00:54:59.708 --> 00:55:04.328 it come in either through like a messaging style, and you get a real visceral 00:55:04.328 --> 00:55:09.208 understanding of what the message queue is and what it's sending back and forth. 00:55:09.368 --> 00:55:15.028 And so the two I'm going to talk about is MQTTX, which is kind of like an all-in-one 00:55:15.028 --> 00:55:15.828 app. It's a little bit bigger. 00:55:16.388 --> 00:55:19.588 And then the other one is MQTT5 Explore. 00:55:20.388 --> 00:55:24.368 And this is a little tighter. This one is GPL licensed. The other is Apache 00:55:24.368 --> 00:55:27.048 licensed. They're both available on Flathub and packaged for Linux. 00:55:27.688 --> 00:55:32.608 And they make it really easy to connect to an MQTT server or a client and observe 00:55:32.608 --> 00:55:34.888 the topics it's sending and understand what they are. 00:55:35.448 --> 00:55:40.608 And from that, you could write scripts. You could just learn. It's really nice. 00:55:40.788 --> 00:55:45.588 Now, I haven't tried either of these, but I do notice that MQTT5 Explorer has 00:55:45.588 --> 00:55:48.168 the Arch Linux logo in there, ReadMe. 00:55:48.328 --> 00:55:50.788 So that's a good sign. Yeah, good sign. 00:55:51.248 --> 00:55:57.708 I'd say it's the most, the MQTT5 Explorer is the most native desktop app. 00:55:58.308 --> 00:56:03.308 And MQTTX is a cross-platform Electron app that works on Linux, 00:56:03.448 --> 00:56:06.148 Windows, Web, Mac OS, can run in a Docker container. 00:56:06.388 --> 00:56:08.288 So it sort of depends on what you're trying to accomplish. 00:56:08.728 --> 00:56:13.408 And they just make understanding what the hell this is that you're trying to set up a lot simpler. 00:56:13.648 --> 00:56:17.088 And it's a nice way to demystify something that was a little opaque. 00:56:18.551 --> 00:56:20.851 I noticed you're not calling it MQt? 00:56:21.131 --> 00:56:26.371 Yeah, should have. Now, a couple of others for those of you that don't care about MQTT. 00:56:27.011 --> 00:56:30.971 This is something that you'll see different commercial Electron apps take a 00:56:30.971 --> 00:56:34.931 crack at, so it's nice to see a GPL version of this. It's called Unify. 00:56:35.331 --> 00:56:40.911 It's what you could consider a web app aggregator. Now, this one is built in Qt and Qt 6. 00:56:40.911 --> 00:56:45.791 It uses WebEngine and Karagami to organize different web-based services into 00:56:45.791 --> 00:56:51.191 workspaces and open each in its own web view with desktop-friendly integrations 00:56:51.191 --> 00:56:52.851 like notifications and whatnot. 00:56:53.091 --> 00:56:58.491 So, you know, just relegate all of your web-based style Electron apps to one 00:56:58.491 --> 00:57:01.211 master app that keeps them all organized. We've seen other takes on this, 00:57:01.311 --> 00:57:02.051 commercial ones at that. 00:57:02.311 --> 00:57:05.471 But this one's all based on modern KDE platform technologies, 00:57:05.471 --> 00:57:07.871 and it's GPL3. So that's great. 00:57:08.871 --> 00:57:13.471 Unify, don't confuse it with other things named Unify. And that one is Qt-based. 00:57:13.671 --> 00:57:17.671 Now, if you're more of a GTK person, then there is Web App Hub. 00:57:17.831 --> 00:57:21.071 Web App Manager or whatever, it's labeled both things. 00:57:21.251 --> 00:57:24.571 It's written in Rust and GTK. 00:57:24.791 --> 00:57:29.631 And it's designed in Nidwadia. And it's a Web Hub App Manager, 00:57:29.671 --> 00:57:34.811 just like the Unify application, to do essentially the same thing but do it in a GTK-first world. 00:57:35.071 --> 00:57:37.271 And it gives you easy browser switching. 00:57:37.791 --> 00:57:41.371 It makes it super easy to manage and isolate apps into their own things. 00:57:41.671 --> 00:57:47.731 It can go pull their web icons for you. It can do custom browser profile configs to launch that app. 00:57:48.591 --> 00:57:51.691 It's more than just containing all in one app. It's kind of a little bit more 00:57:51.691 --> 00:57:53.931 than that. It more integrates with the GNOME desktop. So it kind of depends 00:57:53.931 --> 00:57:54.571 what you're looking for. 00:57:55.151 --> 00:58:00.891 But myself, so many dang things are web-based now. I mean, on this machine right 00:58:00.891 --> 00:58:07.571 here, I have 1, 2, 3, 4, 5, 6, 7, 8, 9, 10, 11 pinned web apps. 00:58:07.711 --> 00:58:12.331 I have 11 pinned tabs for different web apps I need to manage the live stream 00:58:12.331 --> 00:58:14.051 and the recording of this episode. 00:58:14.211 --> 00:58:16.711 Those are just 11 different web-based applications. 00:58:16.991 --> 00:58:19.191 And they're all running under the Firefox process. 00:58:20.011 --> 00:58:24.111 I get a little skeeved out by that. I would like to have something else separate 00:58:24.111 --> 00:58:27.371 so that way if my browser crashes, like this morning Brent went to help about 00:58:27.371 --> 00:58:28.891 and his browser crashed. 00:58:29.371 --> 00:58:33.471 Well, then 11 of my apps I used to manage this stream and this show would destroy it. Gone. 00:58:33.991 --> 00:58:37.011 So I like to separate it out into its own process. And there used to be a lot 00:58:37.011 --> 00:58:39.371 of ways. I mean, hell, browsers used to have some of this crap built in for 00:58:39.371 --> 00:58:40.571 a while. God, that was nice. 00:58:41.531 --> 00:58:44.231 And then there was other things like Natifier and other things that came along 00:58:44.231 --> 00:58:46.491 for the Linux desktop, but then they faded. 00:58:46.731 --> 00:58:50.371 So now it's nice to see these two, both for Plasma desktops or GNOME desktops, 00:58:50.911 --> 00:58:51.811 whatever your flavor is. 00:58:51.931 --> 00:58:53.751 Rust, C++, but take your pick. 00:58:53.831 --> 00:58:57.811 Pick your pick. Both open source, both available on the FlatHub or probably 00:58:57.811 --> 00:58:59.391 packaged in a distro near you. 00:59:01.391 --> 00:59:04.351 Enjoy it. And then, of course, the MQTT apps. In fact, everything we talked 00:59:04.351 --> 00:59:09.311 about today will be linked at linuxunplugged.com slash 648. 00:59:09.531 --> 00:59:12.351 And, you know, Wes, it's possible we mentioned something that they'd like to 00:59:12.351 --> 00:59:15.951 catch again. We'd like to look up the name of something. We have a power tip for them, don't we? 00:59:16.171 --> 00:59:20.051 Oh, yeah. Well, we have a website. Is that what you mean? Like a community-powered 00:59:20.051 --> 00:59:22.771 open source? I feel like you go website. 00:59:22.951 --> 00:59:25.551 There's probably, you could do that. There's probably even a way to get, 00:59:25.631 --> 00:59:28.651 like, more rich metadata from the podcast app itself. 00:59:28.851 --> 00:59:31.771 Oh, well, yeah. we do we do have hdmail descriptions. 00:59:31.771 --> 00:59:36.091 In the feed no no i'm not with all the links in it oh and tags we've got a great 00:59:36.091 --> 00:59:40.031 set of tags but no i'm thinking more west like could they get even richer context 00:59:40.031 --> 00:59:43.811 they could even plug into like language models and things like that is there more they oh. 00:59:43.811 --> 00:59:47.671 You're thinking like cloud chapters and um transcripts. 00:59:47.671 --> 00:59:48.591 You got it buddy you're. 00:59:48.591 --> 00:59:49.731 Thinking vtt files. 00:59:49.731 --> 00:59:55.691 Srts maybe even speaker diarization if we could all of it in there uh more and 00:59:55.691 --> 00:59:58.051 more apps Even Apple Podcasts now support all of that. 00:59:58.151 --> 01:00:01.191 And, of course, the podcasting 2.0 apps, which over at podcastapps.com, 01:00:01.311 --> 01:00:04.331 have been supporting it for years. And it's nice to see that standard spread. 01:00:04.611 --> 01:00:07.571 And, of course, one other thing you should know about our gosh darn live stream. 01:00:11.091 --> 01:00:16.131 Make it a Tuesday on a Sunday. Join us over at jblive.tv, 10 a.m. Pacific, 1 p.m. 01:00:16.311 --> 01:00:20.431 Eastern. Of course, in your local time zone at jupiterbroadcasting.com slash calendar. 01:00:20.691 --> 01:00:24.331 We've got our low latency Opus mumble room going, whatever you want to call it. 01:00:24.391 --> 01:00:28.391 It's a mumble room. it's a live stream but it's a mumble room you can catch 01:00:28.391 --> 01:00:32.291 that you can join our chat room or don't worry about it become a member and 01:00:32.291 --> 01:00:35.291 get the bootleg and we'll deliver it to you all processed and ready to go so 01:00:35.291 --> 01:00:36.451 you don't miss a single thing. 01:00:37.051 --> 01:00:41.831 Last but not least tell a friend it's a great way to support the podcast just 01:00:41.831 --> 01:00:45.011 right there tell somebody about the show it's the number one way people learn 01:00:45.011 --> 01:00:48.691 about new podcasts so we really appreciate that too thanks so much for listening 01:00:48.691 --> 01:00:52.831 to this week's episode of your unplugged program we'll see you right back here next Sunday.