Skip to main content
LawHub
Sign In
About LawHub Advantage Thinking About a Career in Law Applying to Law School Thriving in Law School and Beyond Listen to I Am The Law Podcast Trends Sign In
Search

Self-Hosted Location Tracking

May 11, 2025
Listen to this episode

We test-drive a self-hosted alternative to Google Location History. Plus, we cover the week's Linux news highlights, then spill the beans on our upcoming TUI challenge.

Sponsored By:

Support LINUX Unplugged

Links:

Transcript

WEBVTT 00:00:11.519 --> 00:00:16.059 Hello, friends, and welcome back to your weekly Linux talk show. My name is Chris. 00:00:16.219 --> 00:00:16.859 My name is Wes. 00:00:17.019 --> 00:00:17.739 And my name is Brent. 00:00:17.879 --> 00:00:21.699 Hello, gentlemen. Well, coming up on the show today, we'll show you and tell 00:00:21.699 --> 00:00:26.359 you and test a self-hosted alternative to Google Maps location tracking. 00:00:26.759 --> 00:00:29.979 It's a hotspot of where you've been and everywhere you go, and the three of 00:00:29.979 --> 00:00:31.119 us have been trying it out. 00:00:31.379 --> 00:00:34.299 Plus, we'll catch up on some news that we've missed while we're on the road, 00:00:34.299 --> 00:00:38.619 and we'll share the details on an upcoming TUI challenge. And then we'll round 00:00:38.619 --> 00:00:42.379 it all out with some great booths, some picks, and a lot more. 00:00:42.499 --> 00:00:46.379 So before we go any further, let's say time-appropriate greetings to our virtual 00:00:46.379 --> 00:00:47.419 lug. Hello, Mumble Room. 00:00:48.159 --> 00:00:50.719 Hello. Hey, Chris. Hello, Bunt. 00:00:51.959 --> 00:00:52.719 Hello, everybody. 00:00:53.239 --> 00:00:54.819 We got him excited today in there. 00:00:54.939 --> 00:00:58.099 Nice to have you. If you want details, jupiterbroadcasting.com slash mumble. 00:00:58.599 --> 00:01:00.559 You get to hang out and get the whole stream. Or, of course, 00:01:00.599 --> 00:01:03.219 you can become a member. And you get the bootleg. 00:01:03.739 --> 00:01:07.499 And a big good morning to our friends at Tailscale. tailscale.com slash 00:01:07.499 --> 00:01:10.399 unplugged go there to get tailscale for free up to 100 00:01:10.399 --> 00:01:13.459 devices and three users because that's the easiest way 00:01:13.459 --> 00:01:17.419 to connect devices directly to each other applications services servers 00:01:17.419 --> 00:01:22.519 your desktop a vm whatever it might be maybe it is just an application you're 00:01:22.519 --> 00:01:25.639 running on your system and you want to put that directly on your tail net it's 00:01:25.639 --> 00:01:31.779 modern networking that builds out a flat mesh network protected by a world that's 00:01:31.779 --> 00:01:37.379 right so you get secure remote access to your systems that is really fast, intuitive, 00:01:37.679 --> 00:01:43.159 programmable, and also easy to integrate with your company's ACLs and authentication infrastructure. 00:01:43.439 --> 00:01:46.799 It's easy to deploy. It's easy to configure. It really is no fuss. 00:01:46.819 --> 00:01:50.759 If you've got five machines, you can probably get it running in three minutes on all of them. 00:01:50.879 --> 00:01:53.679 And the personal plan will always be free. So you can try it out, 00:01:53.759 --> 00:01:57.419 get it on 100 devices, build out your home lab, and it's so great. 00:01:57.859 --> 00:02:00.819 None of my personal data for my phone, my thinking anything goes 00:02:00.819 --> 00:02:03.739 over the internet i have no inbound ports anymore and i 00:02:03.739 --> 00:02:08.159 love it so much that not only am i a personal user but now jb uses it and it's 00:02:08.159 --> 00:02:11.399 integral to our back-end infrastructure and thousands of other companies use 00:02:11.399 --> 00:02:15.739 tailscale as well for individuals or businesses you get started and support 00:02:15.739 --> 00:02:20.939 the show by going to tailscale.com slash unplugged that's tailscale.com slash 00:02:20.939 --> 00:02:23.479 unplugged get it for free on 100 devices support the show. 00:02:26.831 --> 00:02:30.071 Well, we've got to start by saying Happy Mother's Day to the moms out there. 00:02:30.231 --> 00:02:31.751 Indeed, Happy Mother's Day. 00:02:31.871 --> 00:02:36.571 Appreciate all of you and a special appreciation to all the ones in our lives. 00:02:37.831 --> 00:02:41.111 It's nice that they let us sneak off on this important day and do a podcast. 00:02:41.411 --> 00:02:42.631 So we appreciate that too. 00:02:43.551 --> 00:02:48.491 Also, we have some details about our upcoming Terminal User Interface Challenge. 00:02:48.731 --> 00:02:50.091 You've been hard at work over there. 00:02:50.251 --> 00:02:53.311 Yeah, and I have a first public draft. And what we're going to do is get this 00:02:53.311 --> 00:02:57.011 posted up on the Jupyter Broadcasting GitHub so you can take a look at it. 00:02:57.231 --> 00:03:02.811 It is, on the high level, going to be a seven-day challenge with different points 00:03:02.811 --> 00:03:07.111 awarded for what you get completed. There is a bonus round if you want to skip 00:03:07.111 --> 00:03:12.011 one of the seven-day challenges and go past one of them. There's also some bonus points for creativity. 00:03:12.331 --> 00:03:16.271 There's details on how you submit your information to the show to let us know how you did. 00:03:16.311 --> 00:03:19.311 And the idea is we're trying to come up with a way at the end where you can 00:03:19.311 --> 00:03:20.531 sort of tally up a total score. 00:03:20.591 --> 00:03:23.851 So you can say, guys, I got an 85, or I got a 62, or I got a 100. 00:03:24.051 --> 00:03:24.751 Something to compare. 00:03:25.231 --> 00:03:29.331 Something we can compare at the end. And so all of that is sort of outlined 00:03:29.331 --> 00:03:32.411 in what I've put together, but I think it could use a little finessing. 00:03:32.531 --> 00:03:35.331 So we're all off to Red Hat Summit next week. 00:03:36.131 --> 00:03:40.011 So we figured we'd put this out there, let people look at it for a couple of 00:03:40.011 --> 00:03:42.931 weeks, make some suggestions on our GitHub, and then we'll put it together and 00:03:42.931 --> 00:03:45.731 we'll actually launch the challenge officially after we've gotten some community 00:03:45.731 --> 00:03:47.291 input to really kind of make this thing nice. 00:03:47.431 --> 00:03:50.391 Now I'm feeling nervous because I think Brent's going to smoke us somehow and 00:03:50.391 --> 00:03:51.951 there's going to be numbers to prove it. 00:03:52.351 --> 00:03:56.411 I actually feel far more nervous than I think you feel, so we'll see how it goes. 00:03:56.651 --> 00:03:58.771 See, I'm feeling pretty good because A. 00:03:58.931 --> 00:03:59.891 You've been doing research. 00:03:59.891 --> 00:04:01.311 I've been stacking 2E apps. 00:04:01.471 --> 00:04:01.751 You've been pre-gaming. 00:04:01.951 --> 00:04:06.491 I've been stacking 2E apps. B, I got that Knicks book from Olympia Mike, 00:04:06.531 --> 00:04:09.351 and I think I'm going to make that a dedicated 2E machine. 00:04:10.011 --> 00:04:12.791 Going all in. So the only thing that loads is the terminal. 00:04:14.231 --> 00:04:19.871 Boom. So I'm in it to win it, boys. I'm in it to win it. We'll see how I do, but I am. 00:04:20.611 --> 00:04:24.151 So we'll have the link, hopefully in the show notes, when this episode publishes 00:04:24.151 --> 00:04:25.831 at linuxunplugged.com slash 614. 00:04:25.851 --> 00:04:29.931 We'd like you to take a look at the challenge rules in the outline and make 00:04:29.931 --> 00:04:32.991 any suggestions for improvements, additions, removals, anything like that, 00:04:33.031 --> 00:04:34.851 because it really is just a draft one. 00:04:35.231 --> 00:04:38.151 And I think it's a good chance for everybody to have some input on there. 00:04:39.031 --> 00:04:44.131 And while we're in the housekeeping section, I want to follow up on a topic from last week. 00:04:45.431 --> 00:04:47.551 We're officially back from the van rescue trip. 00:04:48.171 --> 00:04:48.931 We made it. 00:04:49.031 --> 00:04:51.751 We made it. We're here. We're alive. 00:04:52.031 --> 00:04:53.171 Welcome back, boys. 00:04:53.171 --> 00:04:57.071 There was definitely some adventures, a couple of detours we didn't expect, 00:04:57.211 --> 00:05:00.871 but to celebrate the fact that we actually made it, the van survived and we 00:05:00.871 --> 00:05:03.631 survived, we're cracking open some ciders. 00:05:05.431 --> 00:05:07.571 Yes. Cheers, gentlemen. 00:05:07.671 --> 00:05:08.331 Cheers, gents. 00:05:08.651 --> 00:05:09.211 To the bus. 00:05:09.351 --> 00:05:09.971 To the bus. 00:05:10.451 --> 00:05:12.671 And all those who help her along her way. 00:05:13.231 --> 00:05:17.351 Which is, the engines run like a champ, but we continue to be working out systems. 00:05:18.851 --> 00:05:22.691 Electrical is one of the major systems right now. Generator is another major system. 00:05:24.033 --> 00:05:27.353 The frustrating thing is the systems I thought were cool. Somehow, 00:05:27.513 --> 00:05:29.273 now that we're in Washington, are very not cool. 00:05:29.433 --> 00:05:30.873 And the systems we thought might be a problem. 00:05:31.033 --> 00:05:31.573 Yeah, totally fine. 00:05:31.653 --> 00:05:32.253 Probably going to be fine. 00:05:32.393 --> 00:05:34.873 Do you think if you were to drive back to California, you'd swap back? 00:05:35.133 --> 00:05:38.433 Oh, I don't know if I want to drive back to California. Sorry, Jeff. 00:05:39.413 --> 00:05:43.573 But it's good to be back. It was really a hell of an adventure. 00:05:44.233 --> 00:05:48.653 You know, roughly, you said 1,500 miles, but I thought it was roughly 1,800 miles. 00:05:48.653 --> 00:05:55.173 You know um the maps tend to always want to take the i5 and we tend to not ever want to take the. 00:05:55.173 --> 00:05:56.633 I5 we took very much the long route i. 00:05:56.633 --> 00:05:58.633 Think my estimates were quite off. 00:05:58.633 --> 00:06:02.213 I think it was 1800 miles based on the app i used to track us yeah. 00:06:02.213 --> 00:06:05.453 I i reset the odometer but i don't know it didn't give us the right reading. 00:06:05.453 --> 00:06:10.053 Uh yeah the odometer didn't seem to be reading it was on zero right yeah um 00:06:10.053 --> 00:06:14.213 we did have one cop out of 18 pull us over we'll have this story about that um, 00:06:14.733 --> 00:06:17.333 and more details in the launch we covered we talked about some of this last 00:06:17.333 --> 00:06:22.113 week and then And of course, we had to make the drive since we were in episode 613. 00:06:22.273 --> 00:06:24.413 That's when we actually had to make the drive all the way back to Washington 00:06:24.413 --> 00:06:28.713 here to the studio. So we're going to cover all the details in the launch 21, 00:06:29.033 --> 00:06:32.013 which will be out on May 14th, weeklylaunch.rocks. 00:06:33.193 --> 00:06:36.893 And yeah, there's a lot. There's a lot more projects to continue to. 00:06:37.733 --> 00:06:40.893 We may have fried the home assistant machine already. 00:06:41.393 --> 00:06:43.253 It's not good. It's not good. 00:06:43.413 --> 00:06:45.333 We don't know for sure. We got to do further testing. Like everything, 00:06:45.373 --> 00:06:46.333 you got to test a few times. 00:06:46.333 --> 00:06:48.073 I think Jeff has a spare one under his bed. 00:06:48.253 --> 00:06:49.813 Yeah, PJ, we might need that spare. 00:06:50.033 --> 00:06:50.313 Thanks. 00:06:50.613 --> 00:06:54.593 I don't know if he does have it. Yeah, we were testing the electrical system. 00:06:54.793 --> 00:06:57.833 Although I think, wasn't PJ saying maybe a Knicks book would be a good fit? 00:06:58.173 --> 00:06:58.973 We got options. 00:06:59.153 --> 00:07:00.853 We got, yeah. We have disagreements. 00:07:02.233 --> 00:07:02.853 I see. 00:07:03.053 --> 00:07:04.193 I'm not a big fan of the home assistant. 00:07:04.213 --> 00:07:05.073 I'm poking my head somewhere here. 00:07:05.073 --> 00:07:07.833 I'm not a fan of home assistant's laptop. I get the built-in battery and all 00:07:07.833 --> 00:07:10.353 of that, but yeah. All right, but anyways. 00:07:11.181 --> 00:07:13.901 Yeah, so we may have fried the machine. We'll see how. We'll see how that goes. 00:07:13.921 --> 00:07:16.841 He claims they're bulletproof, but I don't know. Leave it to me. 00:07:17.001 --> 00:07:18.141 Yeah, give Brent a week. 00:07:19.021 --> 00:07:20.461 Actually, it was only a couple days. 00:07:20.461 --> 00:07:24.161 This is literally an industrial piece of equipment that's meant to be embedded 00:07:24.161 --> 00:07:28.001 in a very rough terrain, hard, core, hot. 00:07:28.081 --> 00:07:34.501 Here's what happens. You see the superstructure of the van. It concentrates the bug field. 00:07:35.201 --> 00:07:36.301 Yeah, the metal walls. 00:07:36.421 --> 00:07:36.961 Yeah, exactly. 00:07:37.141 --> 00:07:38.041 Oh, it sure feels that way. 00:07:38.181 --> 00:07:40.001 So it's like a Brent-a-day cage is what you're saying. 00:07:40.041 --> 00:07:41.041 That's absolutely right. 00:07:41.181 --> 00:07:42.801 Oh, God. I hadn't thought about that. 00:07:42.901 --> 00:07:45.701 Yeah, don't put your sensitive production systems anywhere near there. 00:07:45.721 --> 00:07:49.521 Like, what happens to me? Is there, like, a cross-contamination? Do I get affected? 00:07:49.521 --> 00:07:52.001 Yeah, we should probably hang out for a bit. I'll try to decontaminate it. 00:07:52.001 --> 00:07:53.541 Counterbalance, thank you, Wes. Yeah. Yeah, you better watch out, 00:07:53.561 --> 00:07:55.221 too. Yeah, you better watch out. 00:07:55.461 --> 00:07:59.401 But we made it. We're back. Projects will continue. We may have fried the Home Assistant box. 00:07:59.561 --> 00:08:02.581 We'll have details once we get that tested. And, of course, check out the Launch 00:08:02.581 --> 00:08:06.161 21 when it comes out on May 14th. Weekly launch.rocks. 00:08:06.781 --> 00:08:10.501 We'll have all of that, hopefully, figured out. I don't know. 00:08:10.501 --> 00:08:11.821 But it's been so much fun. 00:08:12.301 --> 00:08:15.781 That's the key takeaway. We really enjoyed it. I wish I could do that once a 00:08:15.781 --> 00:08:17.481 quarter. You know, go rescue something like that. 00:08:17.661 --> 00:08:21.721 We could find a way. You know, we can crowdsource a bunch of crazy projects 00:08:21.721 --> 00:08:25.521 for us to go find somewhere in the continent. Even off continent. 00:08:25.521 --> 00:08:27.521 Anybody else have a semi-functional van need rescued? 00:08:28.161 --> 00:08:29.561 Chris has been looking along the way. 00:08:29.641 --> 00:08:30.561 What's your rate? 00:08:30.701 --> 00:08:34.341 I have never loved another man's vehicle as much as I love this van. 00:08:34.541 --> 00:08:36.901 Like, you know, my blood, sweat, and tears have gone into this too. 00:08:37.101 --> 00:08:39.361 And then, you know, you do that driving along the coast. 00:08:39.361 --> 00:08:41.721 Are you the, is there like a godfather sort of concept? 00:08:41.981 --> 00:08:42.081 I'll take that. 00:08:42.221 --> 00:08:45.041 Yeah, I'll take that. I'm not, I can't give that away. That's his to distribute. 00:08:45.201 --> 00:08:47.941 I mean, I would take it. I would be honest. You asked me a question. 00:08:48.021 --> 00:08:50.961 What was it? Do you remember? No? Okay. I don't remember either, 00:08:51.001 --> 00:08:52.221 but I'm sure it was really important. 00:08:53.161 --> 00:08:55.581 I have a question. One last thing before we get out of housekeeping. 00:08:57.427 --> 00:09:01.027 How do I sound today? So I'm using the headset in studio just to get more practice with it. 00:09:02.027 --> 00:09:05.387 I want to know, do you think this could be a forever mic? Does it sound okay 00:09:05.387 --> 00:09:08.987 compared to the boys? Boost him, let me know how you think it sounds. Be honest. 00:09:09.567 --> 00:09:13.047 Give me the harsh feedback or give me the good feedback. Just trying to, 00:09:13.067 --> 00:09:15.987 you know, learn how to use these fancy new headsets that y'all helped us get, 00:09:16.187 --> 00:09:17.247 which we appreciate very much. 00:09:20.167 --> 00:09:23.007 So the Gnome Foundation, or I guess Gnome. 00:09:23.507 --> 00:09:24.267 Gnome for some. 00:09:24.587 --> 00:09:29.807 Has a new executive director. Steven Diobald, I believe is maybe not how you 00:09:29.807 --> 00:09:33.027 say it, but he's been appointed as a new executive director of the Gnome Foundation. 00:09:33.707 --> 00:09:39.887 There was an intern director who sat in for Holly Millen, who stepped down last year. 00:09:40.747 --> 00:09:43.707 Now, here's what stood out to me, Brent. I thought you'd like this, 00:09:43.847 --> 00:09:45.727 is he's a Canadian free software advocate. 00:09:46.067 --> 00:09:46.427 Oh. 00:09:46.887 --> 00:09:50.227 Yeah, he's Canadian. He's been a Gnome user since 2002. 00:09:51.367 --> 00:09:58.847 and he does have some experience in the IT industry and also in the fundraising part of the industry. 00:09:59.147 --> 00:10:00.367 It's actually quite a nice mix, I would imagine. 00:10:00.667 --> 00:10:01.987 It seems like it very well could be. 00:10:02.227 --> 00:10:07.187 You know, here's some cred from the intro bio over on blogs.gnome.org. 00:10:07.507 --> 00:10:13.887 I built a graphical mud before the term MMORPG was coined. So, yeah, right? Hey. 00:10:14.527 --> 00:10:18.867 That's probably a good sign in terms of general nerdery. 00:10:18.967 --> 00:10:22.607 I want to play the Star Trek mud. I've seen it. I think I've never played it, though. 00:10:23.147 --> 00:10:26.007 Yeah, so there's a welcome post that we will link in the show notes. 00:10:26.367 --> 00:10:32.027 And what stood out to me is this is somebody who's taking the reins of GNOME 00:10:32.027 --> 00:10:37.547 at GNOME, GNOME, at a time where they're having some financial troubles. And... 00:10:40.919 --> 00:10:44.999 It feels like it's really a shame that probably the most widely deployed free 00:10:44.999 --> 00:10:49.179 software desktop, even our most successful free software desktop project, 00:10:49.399 --> 00:10:51.159 is having troubles raising funds. 00:10:51.719 --> 00:10:55.979 And I wish maybe there's a way to leverage that position. And maybe this new 00:10:55.979 --> 00:10:59.179 director has an opportunity to improve that situation. 00:10:59.499 --> 00:11:03.719 Because there's a lot of big corporations that are getting a lot of benefit from the GNOME desktop. 00:11:03.859 --> 00:11:06.239 And I know they contribute developer time. And I know there's ways that they 00:11:06.239 --> 00:11:12.339 contribute now. But it's just such a shame that such a user-forward desktop 00:11:12.339 --> 00:11:14.619 for Linux is struggling. 00:11:14.839 --> 00:11:20.039 And I hope that Steven has an opportunity to improve that situation. Not an easy job. 00:11:20.659 --> 00:11:22.379 I don't know who would want that position. 00:11:22.719 --> 00:11:26.639 I'm hopeful. I mean, it does seem like, you know, he's got a long history with 00:11:26.639 --> 00:11:30.599 open source and the tools and communities around it. 00:11:30.739 --> 00:11:35.079 So if anyone can, this seems like a good candidate. So here's hoping for the best. 00:11:35.079 --> 00:11:39.099 NixOS now has a dedicated hardware team. The steering committee is launching 00:11:39.099 --> 00:11:43.659 a new hardware team to own the NixOS hardware repo, drive hardware enablement, 00:11:43.799 --> 00:11:46.239 and expand partnerships. 00:11:46.739 --> 00:11:47.139 Ooh. 00:11:47.679 --> 00:11:50.399 Oh, I would totally be interested in the Nix First laptop. 00:11:50.799 --> 00:11:51.859 That's fascinating. 00:11:52.339 --> 00:11:56.099 So they want to streamline device enablement. So it makes it easier to, 00:11:56.299 --> 00:11:57.799 I guess, say this works with NixOS. 00:11:58.099 --> 00:12:02.259 I think that's a great idea. And I mean, it is one of the easiest first ways 00:12:02.259 --> 00:12:03.779 you can demonstrate that like, hey, 00:12:04.479 --> 00:12:07.899 the community already figured this out and documented it as code and you just 00:12:07.899 --> 00:12:12.639 need to add two lines somewhere and now you have the approved way to make sure 00:12:12.639 --> 00:12:13.359 your hardware is optimized. 00:12:14.885 --> 00:12:18.745 We've seen some self-organizing around that, but part of this is to clarify 00:12:18.745 --> 00:12:23.245 ownership and also to sort of ensure that those things are done consistently 00:12:23.245 --> 00:12:26.345 and not as ad hoc, which I'm not slamming. 00:12:26.425 --> 00:12:28.765 I'm very grateful for, but, you know, that's part of what they want to do is 00:12:28.765 --> 00:12:30.525 make that kind of a consistent experience too. 00:12:30.805 --> 00:12:34.625 Right. And that's exactly the kind of next stage of formalities, 00:12:34.725 --> 00:12:37.725 maybe not the right word, process, structure, just organization in terms of 00:12:37.725 --> 00:12:42.265 having a foundation and a sort of longer term outlook on supporting the project 00:12:42.265 --> 00:12:44.125 for real world use cases. And that's nice. 00:12:44.885 --> 00:12:50.045 If it does go to the next stage, I think, but I'm not sure. I'm curious to hear what you boys think. 00:12:50.405 --> 00:12:55.245 I think I would like to see the NixOS hardware project still be used as the 00:12:55.245 --> 00:12:57.345 central sort of hardware management. 00:12:57.345 --> 00:13:02.545 So if we see a bunch of bigger companies committing to that repo, 00:13:02.645 --> 00:13:05.545 that'd be really nice to see. But I don't know if you think that's best practice. 00:13:05.545 --> 00:13:12.985 Hmm i was picturing i was picturing uh sort of like a maintainer role where 00:13:12.985 --> 00:13:16.685 you'd still have community contributing their fixes their patches their configs 00:13:16.685 --> 00:13:18.805 but then you would have sort of, 00:13:19.445 --> 00:13:24.465 maintainers that are taking that in and making sure that it is a certain standard 00:13:24.465 --> 00:13:28.285 format and things like that but you know if i was just also thinking if i could 00:13:28.285 --> 00:13:32.785 be in charge of hardware for you know, a year at NixOS, 00:13:33.285 --> 00:13:36.905 quote unquote, at the NixOS Corporation, deploying the NixOS software. 00:13:37.245 --> 00:13:38.565 So this is getting pretty out there. 00:13:39.505 --> 00:13:40.005 Um... 00:13:40.905 --> 00:13:45.345 But I do wonder, would it be a big impact to say, work with a ThinkPad or a 00:13:45.345 --> 00:13:52.325 System76 and try to focus on the DevOps engineer software developer market that 00:13:52.325 --> 00:13:55.045 is particularly trying to deploy software? 00:13:55.645 --> 00:13:59.265 I'd focus in on a couple of scenarios that I felt like I could really solve. 00:13:59.265 --> 00:14:03.605 Or maybe, you know, is there room for a company that does this, 00:14:03.645 --> 00:14:07.705 and they work with a company like Phlox to produce an out-of-the-box, 00:14:07.765 --> 00:14:12.185 really friendly developer experience based on Phlox's technology and NixOS to manage the OS. 00:14:12.325 --> 00:14:18.325 Ooh, here's your, like, super streamlined, boots-to-Phlox, ready-to-go dev setup. 00:14:18.565 --> 00:14:18.785 Yeah. 00:14:19.045 --> 00:14:19.945 Something like that. Hmm. 00:14:20.065 --> 00:14:22.145 Chromebook, but more powerful, not as restricted. 00:14:22.385 --> 00:14:25.245 Meant for the super user, or at least the professional user. 00:14:25.245 --> 00:14:29.265 Good hardware, good battery life, decent build-out, reliability, good keyboard. 00:14:29.445 --> 00:14:32.145 I mean, I know this is, but there's a market for this. You know, 00:14:32.185 --> 00:14:33.745 this is what the Sputnik thing was all about. 00:14:34.265 --> 00:14:36.345 And I don't know if they've drifted from that as much or not. 00:14:36.425 --> 00:14:38.405 I think, you know, they're just kind of constrained to what the designs are. 00:14:39.585 --> 00:14:42.645 And there's so much potential here. And right now, my options are, 00:14:42.785 --> 00:14:44.805 if I buy a laptop with Fedora or Pop! 00:14:44.865 --> 00:14:48.385 OS, I know I've got a good chance that's going to run Nix OS just fine. 00:14:48.865 --> 00:14:52.865 But I would totally be more inclined to just buy something with NixOS preloaded 00:14:52.865 --> 00:14:58.025 just because I would assume even when I reload Nix myself, it's going to work great. 00:14:58.205 --> 00:15:01.185 Yeah, you know the hardware stuff's just going to detect or you can import it 00:15:01.185 --> 00:15:02.665 and it'll have your model ready to go. 00:15:03.365 --> 00:15:06.965 While we're on the subject, just a very quick micro selfish shout out. 00:15:07.105 --> 00:15:13.185 I did see some folks attempting to organize or seek interest for a Seattle NixOS 00:15:13.185 --> 00:15:18.245 users meetup group over on the Discord. course so if you happen to be in that 00:15:18.245 --> 00:15:20.685 area and are interested maybe go chime in. 00:15:20.685 --> 00:15:23.945 Oh something like that got rolling i think we'd pop i think we would exactly 00:15:23.945 --> 00:15:25.045 yeah that'd be pretty great, 00:15:31.185 --> 00:15:37.605 well it looks like sudo rs is in 2510 it's going to be default ubuntu will adopt 00:15:37.605 --> 00:15:44.705 sudo rs a rust-based memory safe re-implementation of the traditional sudo application This, 00:15:44.985 --> 00:15:48.545 you know, I'm surprised to see pushback. 00:15:49.878 --> 00:15:54.198 I mean, good code is good code, right? And these tools are tools. 00:15:54.418 --> 00:15:58.678 And if the functionality is good and it does what they need and they think it's 00:15:58.678 --> 00:16:01.278 going to make it easier for them to maintain LTSs and whatnot, 00:16:01.518 --> 00:16:04.498 I have a hard time finding the bad in this. 00:16:04.558 --> 00:16:07.358 But it has definitely seen some pushback, more than I expected, 00:16:07.658 --> 00:16:09.698 especially after we had our chat. 00:16:09.938 --> 00:16:15.618 Can you give a sense of what the pushback is? Just like people who are traditionalists? 00:16:15.718 --> 00:16:19.498 Yeah, it's sort of the two-track. You get a lot. It already works. 00:16:20.178 --> 00:16:23.778 compatibility with older systems, you get that argument. And then you also get 00:16:23.778 --> 00:16:28.738 the sort of like, well, it's Rust, and so there's a pushback because people 00:16:28.738 --> 00:16:31.798 don't want to just arbitrarily replace everything with Rust just because it's Rust. 00:16:32.138 --> 00:16:36.058 There's also a whole social aspect to Rust that people want to push back on 00:16:36.058 --> 00:16:37.598 and say, well, you could use something like Go instead. 00:16:37.898 --> 00:16:40.778 So there's just these different, there's three or four different camps that 00:16:40.778 --> 00:16:43.218 kind of come together to push back on an announcement like this. 00:16:44.098 --> 00:16:48.778 But I have to side with Canonical on this one. 00:16:48.778 --> 00:16:51.238 And I think some of these things do need to be pushed forward. 00:16:51.238 --> 00:16:55.418 And when we're talking about maintaining these, what are essentially forks of 00:16:55.418 --> 00:17:00.678 Linux for a decade plus, which is honestly, in my personal opinion, irresponsible. 00:17:00.718 --> 00:17:03.378 And these companies should not be doing this and they should be forcing their 00:17:03.378 --> 00:17:06.258 customers to upgrade, which would enforce the vendors to upgrade. 00:17:06.258 --> 00:17:11.598 But since they won't, instead, they'll just take a check and they'll pay developers 00:17:11.598 --> 00:17:18.058 to toil away for a decade to port old patches and fixes to these ancient releases 00:17:18.058 --> 00:17:22.938 of Linux and anything you can do to make that easier to support, 00:17:23.038 --> 00:17:25.738 to make that more maintainable and to make that safer and secure, 00:17:26.038 --> 00:17:31.758 not today, but 10 years from now, seems like a pretty good action to take. 00:17:31.878 --> 00:17:33.518 And when you consider how long... 00:17:35.108 --> 00:17:39.208 Some of these customers will take before they even get this stuff in the next LTS. 00:17:40.208 --> 00:17:44.648 We're going to still see another five to ten years before most of the companies 00:17:44.648 --> 00:17:48.008 that are running these things on these long-term systems even adopt this stuff. 00:17:48.508 --> 00:17:52.088 There's also an aspect I think that's easy to not necessarily appreciate, 00:17:52.228 --> 00:17:55.748 which I did not until we talked with John Seeger, VP Engineering for Ubuntu, 00:17:55.908 --> 00:18:00.048 who's had some great blog posts on this effort and was on episode 607, 00:18:00.048 --> 00:18:02.088 if you want more of the deeper rationale. 00:18:02.088 --> 00:18:04.828 now um but you know they know here in 00:18:04.828 --> 00:18:07.788 this discourse post that the pseudo rs team 00:18:07.788 --> 00:18:10.508 is collaborating with todd miller the maintainer of 00:18:10.508 --> 00:18:13.268 the original pseudo for over 30 years yeah so it's not 00:18:13.268 --> 00:18:16.048 i guess in some considerations really a fork in 00:18:16.048 --> 00:18:18.908 the road i mean it is a different project but you know 00:18:18.908 --> 00:18:22.528 it it's attempting to keep in line be 00:18:22.528 --> 00:18:26.028 pretty much a drop in replacement they've also contributed changes 00:18:26.028 --> 00:18:29.388 and enhancements to pseudo right so like they're both still healthy 00:18:29.388 --> 00:18:32.188 and going onwards for the most part 00:18:32.188 --> 00:18:35.108 if you're just doing you know the basic stuff that we 00:18:35.108 --> 00:18:38.128 all do or regular bog standard 00:18:38.128 --> 00:18:41.268 um pseudo configuration it should be a drop replacement 00:18:41.268 --> 00:18:44.648 but it is probably worth noting that it's 00:18:44.648 --> 00:18:48.208 not a quote-unquote blind re-implementation the 00:18:48.208 --> 00:18:53.408 developers are taking a less is more approach meaning some of the features that 00:18:53.408 --> 00:18:59.528 if they are only serve quite niche audiences or maybe are just like things you 00:18:59.528 --> 00:19:03.188 wouldn't do today from a security perspective if you were going to develop the 00:19:03.188 --> 00:19:05.748 software now some of those features are gone so. 00:19:06.688 --> 00:19:10.048 If the thing you relied on for your workflow is gone that's reasonable to be 00:19:10.048 --> 00:19:15.208 concerned but you know if you can drop it in and you don't notice win. 00:19:22.184 --> 00:19:28.224 So, BcacheFS has had some new patches introduced aimed at significantly improving 00:19:28.224 --> 00:19:30.964 snapshot deletion performance. 00:19:31.704 --> 00:19:35.364 These enhancements are part of an ongoing effort to refine the file system's 00:19:35.364 --> 00:19:40.564 capabilities, but there is an actual but with this particular patch. 00:19:40.764 --> 00:19:45.764 The implementation necessitates an update to the incompatible on-disk format, 00:19:45.964 --> 00:19:49.604 and then must be explicitly enabled by users to make that happen. 00:19:49.604 --> 00:19:51.824 Obviously, for safety reasons, I don't want to surprise you. 00:19:52.304 --> 00:19:56.204 And the new ONDIS format is not backwards compatible, meaning once you enable 00:19:56.204 --> 00:19:58.624 it, you're not going to be able to revert. 00:19:58.724 --> 00:20:02.884 Now, of course, BcacheFS is like ultimate beta, should not be using it. 00:20:02.964 --> 00:20:04.644 It's not even released as stable in the kernel. 00:20:04.944 --> 00:20:07.864 We're not actually suggesting you should have it in production or on your system. 00:20:07.904 --> 00:20:09.764 So, of course, Wes is using it. 00:20:10.064 --> 00:20:11.864 That's right, on several of my systems, actually. 00:20:12.164 --> 00:20:14.544 So does this impact you at all? 00:20:14.544 --> 00:20:19.204 No i mean i'm don't have a crazy ton of snapshots to delete so i don't have 00:20:19.204 --> 00:20:23.324 any pressure to opt in necessarily for the in the first place um what. 00:20:23.324 --> 00:20:28.324 As a user of bcfs what um is the impact to you when there's an on disk format change. 00:20:28.324 --> 00:20:31.044 Uh well so there are some that are 00:20:31.044 --> 00:20:33.724 like you know the bigger ones uh that are 00:20:33.724 --> 00:20:36.764 slowing down and maybe stable um are ones 00:20:36.764 --> 00:20:40.484 that is sort of like you know pretty much everyone's doing so like you upgrade 00:20:40.484 --> 00:20:44.484 to the new kernel and it's like or you do some new operation and it needs to 00:20:44.484 --> 00:20:48.864 upgrade the file system then there are incompatible features right so there's 00:20:48.864 --> 00:20:51.744 like the actual on just format that new kernel puts up and like you have to 00:20:51.744 --> 00:20:53.884 make some change to all of the data structures and. 00:20:53.884 --> 00:20:57.444 So does it just run through a process at the next boot is it just something 00:20:57.444 --> 00:21:00.684 that's sort of like on the screen for a few minutes while your system boots for the first time. 00:21:00.684 --> 00:21:03.544 Yeah or i mean there's probably various ways to do you can probably trigger 00:21:03.544 --> 00:21:08.164 it from like a user space tool as well i don't know all the details but that 00:21:08.164 --> 00:21:10.384 has happened right where You've had to do these upgrades. 00:21:10.924 --> 00:21:14.064 This is not that, right? This is not just like automatically happen. 00:21:14.304 --> 00:21:17.444 This is not necessary to continue using the file system on a new version, 00:21:17.444 --> 00:21:19.924 except if you opt in and then you can't go backwards. 00:21:20.144 --> 00:21:22.364 So this is an incompatible features. 00:21:22.764 --> 00:21:26.764 So if you do opt in, it does change the disk format, but it's not like a feature 00:21:26.764 --> 00:21:29.064 that is expected of all BcacheFS file systems. 00:21:29.524 --> 00:21:32.284 As Kent was trying to clarify in some of the Pharonix comments, 00:21:32.984 --> 00:21:36.044 this is pretty common that file systems do in terms of like, 00:21:36.224 --> 00:21:39.604 oh, if you want to opt into this optimization, we need to make a change to the 00:21:39.604 --> 00:21:44.364 structure of your disk and maybe that'll be something that will be default in future file systems, 00:21:44.984 --> 00:21:50.104 that get created or maybe sometimes they remain as sort of niche versions that 00:21:50.104 --> 00:21:52.804 doesn't make sense for everyone to enable but does depending on your workload. 00:21:53.304 --> 00:21:57.464 You always know I love ButterFS. So this is said with no judgment I mean I got ButterFS everywhere, 00:21:58.642 --> 00:22:04.482 But it feels like BcacheFS is working this stuff out in this alpha-beta stage 00:22:04.482 --> 00:22:07.122 before it's stable in the kernel, before it's been unleashed to users. 00:22:07.342 --> 00:22:12.542 The ButterFS kind of was working out in the public once we already had ButterFS 00:22:12.542 --> 00:22:15.082 on our file systems. And we'd already formatted our disk, right? 00:22:15.202 --> 00:22:20.022 It felt like ButterFS was making these iterations years into already being out in production. 00:22:20.202 --> 00:22:24.202 Again, no shame to that game. I love ButterFS. It's in a great place right now. 00:22:24.202 --> 00:22:29.402 but this particular type of stuff this big stuff if this is the time to do it 00:22:29.402 --> 00:22:32.822 is before we all have it really seriously deployed in production unlike wes well. 00:22:32.822 --> 00:22:35.602 And as we know with butterfs like some people got burnt in the early days and 00:22:35.602 --> 00:22:39.022 it's really hard to come back to a file system once you've been burnt that hard. 00:22:39.022 --> 00:22:42.362 Yeah i think ken's aware of that too based on our chat with him i got the sense 00:22:42.362 --> 00:22:44.282 he is very much aware of trying to avoid that. 00:22:44.282 --> 00:22:48.722 Yeah definitely and as you say right i mean it's useful between being able to 00:22:48.722 --> 00:22:52.502 learn from the development of butterfs and zfs and other modern file systems. 00:22:52.942 --> 00:22:55.862 And, right, there are some users out there with petabyte file systems and who 00:22:55.862 --> 00:22:58.922 are making a bunch of snapshots. So, hopefully, and this is a good reason to 00:22:58.922 --> 00:23:00.622 run it on systems where you can. 00:23:01.422 --> 00:23:05.622 You know, Kent's pretty active. There's ways to communicate and share bug reports or test new features. 00:23:05.842 --> 00:23:10.742 And if we work them out now, hopefully it'll be a reliable file system for decades to come. 00:23:14.686 --> 00:23:18.166 Onepassword.com slash unplugged. That's the number one password, 00:23:18.426 --> 00:23:20.446 unplugged, all lowercase. 00:23:20.886 --> 00:23:23.766 Imagine your company's securities like the quad of a college campus. 00:23:23.926 --> 00:23:27.366 You have your nice brick pass between the buildings. Those are the company-owned 00:23:27.366 --> 00:23:30.786 devices you could sort of think of as the stuff IT is approved of, 00:23:31.006 --> 00:23:35.646 the employee identities that have been managed, the things and accounts you know about. 00:23:35.806 --> 00:23:38.286 And then you have those pass that people actually use. 00:23:38.846 --> 00:23:42.466 The shortcuts that get worn through the grass, that's the actual straightest 00:23:42.466 --> 00:23:43.846 line from point A to point B. 00:23:44.046 --> 00:23:50.186 Those are the unmanaged devices, shadow IT apps, and non-employee identities like contractors. 00:23:50.506 --> 00:23:53.966 Most security tools, they only work on the happy brick pass. 00:23:54.206 --> 00:23:58.926 But, and I know you know this, a lot of security problems take place on those shortcuts. 00:23:59.206 --> 00:24:02.746 That's where extended access management comes in from 1Password. 00:24:02.866 --> 00:24:05.886 It's the first security solution that brings all these unmanaged devices, 00:24:06.126 --> 00:24:08.826 apps, and identities under your control. 00:24:09.346 --> 00:24:13.206 So you ensure that every user is strong, every credential is protected, 00:24:13.366 --> 00:24:16.806 every device is known and healthy, and every app is visible. 00:24:16.966 --> 00:24:20.286 That's what 1Password Extended Access Management solves. It's problems that 00:24:20.286 --> 00:24:23.306 traditional IAMs and MDMs just don't touch. 00:24:23.506 --> 00:24:27.646 It's security for the way we actually work today, and it's generally available 00:24:27.646 --> 00:24:31.866 for companies with Okta or Microsoft Entra, and it's in beta for Google Workspace 00:24:31.866 --> 00:24:33.546 customers to go check it out. 00:24:33.806 --> 00:24:36.586 You know 1Password changed the game when it came to password hygiene. 00:24:37.026 --> 00:24:40.466 Now imagine taking your game all the way to the next level. Every identity, 00:24:40.466 --> 00:24:41.866 every app, every device. 00:24:42.146 --> 00:24:46.206 That's what 1Password does, and they back it up with great supports and regular 00:24:46.206 --> 00:24:47.786 third-party audits as well. 00:24:47.946 --> 00:24:52.386 Go secure every app, every device, and every identity, even the unmanaged ones. 00:24:52.386 --> 00:24:56.626 Go to 1Password.com slash unplugged. That's all lowercase. 00:24:56.806 --> 00:25:00.086 It's 1Password.com slash unplugged. 00:25:02.786 --> 00:25:06.486 Well, Chris, you threw over the fence for us this mapping application, 00:25:06.486 --> 00:25:10.106 and I have not used too many map tracking applications. 00:25:10.406 --> 00:25:12.806 This is one of them that got our attention. 00:25:13.726 --> 00:25:19.846 The name is a little, I'll give it a swing. Here we go. I think it's Dwarwich. 00:25:20.806 --> 00:25:23.406 Yeah, I'm going to go with something like Dwarwich or something like that, 00:25:23.406 --> 00:25:26.066 or maybe we'll just call it the witch. I'm not sure. 00:25:27.006 --> 00:25:31.146 This is such a neat idea. And Google offers a similar location history service 00:25:31.146 --> 00:25:35.446 where you can pull up your location history and it'll overlay it on Google Maps with some hotspots. 00:25:35.646 --> 00:25:39.426 But of course, You're constantly sending all of your location information to Google. 00:25:39.726 --> 00:25:43.406 Years ago, I had a similar thing that was tracking everything I did. 00:25:43.466 --> 00:25:47.186 It was connected to the ODB2 port of my car, and it was called the automatic. 00:25:47.446 --> 00:25:47.966 Oh, right. 00:25:48.566 --> 00:25:50.546 Why the ODB2? That's crazy. 00:25:50.826 --> 00:25:55.246 Well, the idea was it had a little cellular chip in it. And so as soon as your 00:25:55.246 --> 00:25:57.326 car started, it would start tracking your travel. 00:25:58.476 --> 00:26:02.496 And what you would get is a map with, and I use this thing for multiple years, 00:26:02.496 --> 00:26:06.336 like my trip to New York for the Ubuntu Dev Summit and all over. 00:26:06.476 --> 00:26:07.856 So I just had this massive map 00:26:07.856 --> 00:26:11.496 of everywhere we had gone. So I got one for the RV. I got one for my car. 00:26:11.636 --> 00:26:14.496 And then, of course, they went out of business because they couldn't make money 00:26:14.496 --> 00:26:15.956 just selling my data, I guess. 00:26:16.776 --> 00:26:20.856 But the functionality turned out to be really useful because you could go back 00:26:20.856 --> 00:26:23.536 in time and be like, oh, yeah, this was the spot we really loved. 00:26:23.636 --> 00:26:27.356 Or look how much time we spent here. And it wasn't something I initially found 00:26:27.356 --> 00:26:31.156 valuable, but like two years later, I found extremely valuable. 00:26:31.556 --> 00:26:36.136 And I've always wanted something like this. And we've experimented with live 00:26:36.136 --> 00:26:39.596 trackers for our Linode on the Road Denver trip. 00:26:39.736 --> 00:26:40.056 Oh, yeah. 00:26:40.556 --> 00:26:44.956 And there's a lot of ways you can solve this. But this is a newer project that 00:26:44.956 --> 00:26:48.396 is actively maintained that lets you visualize your location history, 00:26:48.616 --> 00:26:52.656 track your movements, and analyze your travel patterns. and it gives you total 00:26:52.656 --> 00:26:55.516 privacy and control and it can be completely self-hosted. 00:26:55.716 --> 00:26:57.736 It is also GPL3. 00:26:58.056 --> 00:27:02.656 And the idea is you get an interactive map with timelines and travel statistics 00:27:02.656 --> 00:27:03.796 about everywhere you've been, 00:27:03.956 --> 00:27:07.456 everything you've done, the speeds and timelines and stuff like that. 00:27:07.956 --> 00:27:13.956 And it works by using multiple different apps or clients that are available for your mobile device. 00:27:14.096 --> 00:27:17.256 And once your mobile device detects that you're really moving, 00:27:18.036 --> 00:27:21.556 it's using the background location services. once the background location services 00:27:21.556 --> 00:27:25.156 realize you're moving, it can start tracking and reporting to your own server 00:27:25.556 --> 00:27:27.056 and giving you all of this data. 00:27:27.236 --> 00:27:31.136 And so if you go on like a family road trip or you go on a work trip or you 00:27:31.136 --> 00:27:34.136 want to go for a nice long drive and you want to come back and have a map of 00:27:34.136 --> 00:27:37.796 the route you took and everywhere you stopped, this is perfect for that. 00:27:37.976 --> 00:27:41.916 And of course, we've been on a lot of trips recently, so this has been on the front of our mind. 00:27:42.196 --> 00:27:45.736 And Brent, you probably got the most time with this because you got it set up first. 00:27:46.216 --> 00:27:49.476 And we went on a nice little scenic route with it. 00:27:50.316 --> 00:27:53.596 And, um, I'm just, I don't know. I'm wondering if you're seeing the value in 00:27:53.596 --> 00:27:55.116 something like this and what your thoughts were using it. 00:27:55.336 --> 00:27:58.636 Well, like I mentioned, I haven't really explored this space for myself just 00:27:58.636 --> 00:28:02.236 primarily because I didn't really have a use or maybe I just didn't have people 00:28:02.236 --> 00:28:06.776 who cared where I went, but I actually have gotten really fascinated by the 00:28:06.776 --> 00:28:10.136 whole, cause this does like heat maps as well of where you spend the most time. 00:28:10.296 --> 00:28:14.856 And as we'll see later, it can also bring in other data from other sources, 00:28:14.996 --> 00:28:15.776 which is really interesting. 00:28:16.336 --> 00:28:20.976 I am surprised I got it working first, just, you know, noting that for you guys. 00:28:21.256 --> 00:28:26.296 And you did, you've not, have you used the Google version or any of the other sort of proprietary? 00:28:26.296 --> 00:28:29.116 No, I've been pretty, I have some allergies I'd like to mention. 00:28:29.276 --> 00:28:31.716 And one of them is tracking by these large corporations. 00:28:32.356 --> 00:28:32.716 Yeah. 00:28:33.196 --> 00:28:35.376 I did for years. I think I've turned it off now. 00:28:35.536 --> 00:28:36.416 Same. I did for years. 00:28:36.436 --> 00:28:39.316 But I have turned it off. I mean, I did not like the tracking aspect and I don't 00:28:39.316 --> 00:28:41.096 especially need anyone knowing all of that. 00:28:42.716 --> 00:28:48.656 I mean, as a sort of virtual journal wannabe, it's pretty great for, 00:28:48.656 --> 00:28:51.436 you know, remembering past trips, seeing where you were. 00:28:51.836 --> 00:28:54.676 Well, I was thinking for Brent. He's technically on a trip right now. 00:28:54.956 --> 00:28:57.436 And a year or two from now, you can look back at this and be like, 00:28:57.496 --> 00:29:00.436 what did I do when I was in Washington? Where have I not been? 00:29:02.056 --> 00:29:03.196 Oh, I like your thinking. 00:29:03.196 --> 00:29:04.936 What route have I not taken yet? 00:29:05.256 --> 00:29:05.536 Okay. 00:29:05.916 --> 00:29:08.976 That kind of stuff. I think you would find that particularly interesting as 00:29:08.976 --> 00:29:12.296 somebody who likes to explore and take new routes. you could actually have a 00:29:12.296 --> 00:29:17.416 map, almost like a video game, of everywhere your character has been on the 00:29:17.416 --> 00:29:19.296 map, and you can pick new quests now. 00:29:19.956 --> 00:29:22.276 I mean, just that kind of stuff. Do you think this is something you would keep using? 00:29:22.536 --> 00:29:26.716 I really think it is. And I didn't think that going into this. 00:29:27.216 --> 00:29:32.216 So it's changed my perspective of, we unfold maps on the show here from time 00:29:32.216 --> 00:29:36.256 to time, but it's changed, I don't know, my relationship to wanting to track 00:29:36.256 --> 00:29:40.916 the history, especially using open formats that you can import and export elsewhere. 00:29:41.996 --> 00:29:45.016 So this might be here to stay for me because I've done, I don't know, 00:29:45.096 --> 00:29:46.836 how many trips in the last 10 years? 00:29:47.536 --> 00:29:50.596 Like ridiculous all over the continent, Europe as well. 00:29:51.516 --> 00:29:54.296 And yeah, actually, I would have liked to know where I've been. 00:29:54.456 --> 00:29:55.856 Everywhere you've been, even the small places. 00:29:56.036 --> 00:29:56.136 Yeah. 00:29:56.456 --> 00:30:00.196 Okay. So you got it running first. So maybe you can tell us how you set it up. 00:30:01.556 --> 00:30:06.556 Wes. Well, we asked Wes very nicely to take a look at this while we were working on the van. 00:30:06.596 --> 00:30:07.456 I meant the client. 00:30:07.676 --> 00:30:10.356 It's a quick message to Wes and poof, magic. 00:30:10.356 --> 00:30:11.836 I'm not that self-serving. 00:30:11.996 --> 00:30:15.216 That was amazing, though. If that was your angle, that was so good. 00:30:15.416 --> 00:30:17.776 I was like, nicely done, sir. Savage moment. 00:30:19.696 --> 00:30:22.876 Yeah, so actually, that is a good question, though. You and I have it running 00:30:22.876 --> 00:30:24.376 very differently on our client devices. 00:30:24.876 --> 00:30:33.636 We do. I decided to try to stay as open as possible using clients that are well-loved by the community. 00:30:33.976 --> 00:30:37.656 So I decided to use OwnTracks, which has been around for a long time. 00:30:37.656 --> 00:30:41.016 Now, Chris, you mentioned you were using it in the past for a bunch of tracking. 00:30:41.216 --> 00:30:42.976 So I knew it had a good history. 00:30:43.116 --> 00:30:45.936 We liked it, right? That's what we use for Linode on the road tracking. Indeed, yeah. 00:30:46.856 --> 00:30:51.956 And OwnTracks, I think, is really flexible in that it can support a bunch of backends. 00:30:52.276 --> 00:30:56.516 And this support is built right into Vavarach. 00:30:56.856 --> 00:31:01.996 And so I thought I'm going to go this route, see how that works. 00:31:01.996 --> 00:31:06.316 It's also, if you're somebody who likes log output, or you want to be able to 00:31:06.316 --> 00:31:09.276 export your config and import it to another device, and you want to get the 00:31:09.276 --> 00:31:13.076 debug details, OwnTrax is the client that will actually expose all of that to you. 00:31:13.236 --> 00:31:19.296 Yeah, I will say it did feel a little heavy on the tech user when I was first 00:31:19.296 --> 00:31:20.836 setting it up. That's fine for us. 00:31:20.836 --> 00:31:23.496 Yeah. I mean, it starts, it assumes you're going to use MQTT. 00:31:23.776 --> 00:31:25.996 You've got to put it into HTTP mode. 00:31:26.136 --> 00:31:30.996 Did you have to import an SSL cert or were you just, are you just raw dog plain 00:31:30.996 --> 00:31:32.676 text sending your location information? 00:31:33.915 --> 00:31:35.075 Probably the second one. 00:31:35.255 --> 00:31:40.695 Okay, good. Are you plain texting? You're using own tracks? 00:31:41.295 --> 00:31:45.255 No, to our little self-hosted instance? 00:31:45.335 --> 00:31:46.755 Yeah, our private self-hosted instance. 00:31:46.915 --> 00:31:48.895 I did set up Let's Encrypt. 00:31:49.135 --> 00:31:51.295 You did, but you're not using that on the client, are you? 00:31:51.395 --> 00:31:52.055 I think I am. 00:31:52.255 --> 00:31:56.235 Are you? Because it seems like it just defaults to HTTP. 00:31:57.175 --> 00:32:00.955 Well, good question, actually, then. That would be a major issue. 00:32:01.095 --> 00:32:02.455 Wes and I are currently frantically... 00:32:02.935 --> 00:32:07.075 I mean, if we put this on our own private lands, we would be doing this over tail scale anyways. 00:32:07.335 --> 00:32:10.335 It's true, yeah. Okay, the mode is called HTTP. 00:32:10.815 --> 00:32:11.215 Okay, yeah. 00:32:11.595 --> 00:32:14.295 But the URL I'm using, it has a cute little S. 00:32:14.355 --> 00:32:15.115 It does have the S in it. 00:32:15.515 --> 00:32:17.755 It can also do MDT, which is interesting. 00:32:17.895 --> 00:32:21.255 Yeah, yeah, yeah, yeah. Yeah, that would probably be a yes. So you got the S too? 00:32:21.315 --> 00:32:21.715 I got it. 00:32:21.975 --> 00:32:24.115 All right, good. I was just curious because I did look at that. 00:32:24.195 --> 00:32:26.315 That's not the way I set it up. Yeah, so I... 00:32:26.315 --> 00:32:29.855 I did leave the other server we're running, which we'll get into the integration. 00:32:30.035 --> 00:32:31.215 That one's totally unprotected though. 00:32:31.215 --> 00:32:35.475 I will say, I think own tracks, if you're willing to go through the configuration 00:32:35.475 --> 00:32:40.175 is the more pro route to go with this because you do get the config export. 00:32:40.775 --> 00:32:44.315 You might get a little more granularity, but if you're on iOS or you want to 00:32:44.315 --> 00:32:49.555 dedicate an iOS device for this, they, they actually make a dedicated app that is very simple. 00:32:49.655 --> 00:32:54.635 You give it the URL of your server and your API key and that's it. And it just goes. 00:32:55.535 --> 00:32:58.535 is really nice. It's really simple to set up and, 00:33:00.535 --> 00:33:03.755 as accurate as iOS location can be. 00:33:04.975 --> 00:33:10.395 So I did two setups. I tested two different setups. One of the first routes 00:33:10.395 --> 00:33:15.175 I took is you can actually install a Home Assistant integration and then you 00:33:15.175 --> 00:33:18.755 can use Home Assistant to get the location from any of the devices that you 00:33:18.755 --> 00:33:19.755 track in Home Assistant. 00:33:20.235 --> 00:33:24.475 So I selected a device, fed that into home assistant then home assistant gives 00:33:24.475 --> 00:33:29.495 that to the big d witch to track my location and i don't have to cool yeah i 00:33:29.495 --> 00:33:31.595 don't run anything else on my phone except for the home assistant app, 00:33:32.835 --> 00:33:37.475 so you can reduce battery usage this way however it it's going to be as accurate 00:33:37.475 --> 00:33:42.055 as your location updates are to home assistant and i found when i was driving 00:33:42.055 --> 00:33:46.575 using ios there were sometimes five minute gaps and you would just get like 00:33:46.575 --> 00:33:49.895 these sharp and if you guys zoom in on your maps actually you might see this too. 00:33:49.955 --> 00:33:52.535 I don't know, but I will have these moments where it's like, 00:33:52.595 --> 00:33:54.935 I drove through a house on the map. 00:33:55.255 --> 00:33:56.135 That's impressive. Yeah. 00:33:57.489 --> 00:34:01.069 I get them less with the dedicated app. I still get them. So it really comes 00:34:01.069 --> 00:34:04.229 down to how you fine-tune, how often it updates, how often it uploads, 00:34:04.269 --> 00:34:05.809 and you can tweak all of those settings. 00:34:06.089 --> 00:34:08.989 But if you're looking for just something that's kind of basic and you want to 00:34:08.989 --> 00:34:12.229 minimize battery usage and you already have Home Assistant, that integration 00:34:12.229 --> 00:34:14.149 will work, and it was pretty accurate. 00:34:14.309 --> 00:34:18.509 If you want something better, I think OwnTracks or their dedicated app on iOS is the way to go. 00:34:18.629 --> 00:34:22.209 I do like that OwnTracks lets you toggle your, you know, how much battery do 00:34:22.209 --> 00:34:24.349 you want versus accuracy. Because, yeah, I noticed the same. 00:34:24.529 --> 00:34:28.429 It would miss some sections of my trip if it wasn't moving enough. 00:34:28.789 --> 00:34:33.029 What I extra liked, I'm not sure if you caught this, Wes, is that in the actual 00:34:33.029 --> 00:34:36.169 notification for OwnTracks, which is like a persistent notification. 00:34:36.429 --> 00:34:37.189 You can pause. 00:34:37.329 --> 00:34:41.169 You can pause, but you can also quickly change the style of reporting. 00:34:41.509 --> 00:34:46.089 You just tap the button and it allows you to cycle through how aggressive the reporting is. 00:34:46.169 --> 00:34:48.169 I thought you were going to say you can pause because one of the nice things 00:34:48.169 --> 00:34:50.889 with OwnTracks is it makes it a little bit easier to say, stop tracking. 00:34:51.069 --> 00:34:54.389 I'm going to the adult shop. Stop, whatever you do. I don't know what you guys do. 00:34:54.869 --> 00:34:57.989 Pause. And then it's just right there to resume. That's really nice too, 00:34:58.029 --> 00:34:59.249 because you can just tap it and then get in the app. 00:34:59.389 --> 00:35:02.649 Their app makes that possible as well, but there's not like that Android persistent 00:35:02.649 --> 00:35:05.309 notification aspect that gets you there quicker. 00:35:06.409 --> 00:35:09.969 You could run this. I think the ultimate setup would be for people that are 00:35:09.969 --> 00:35:14.069 trying to track a road trip would be maybe it's a container on an existing machine 00:35:14.069 --> 00:35:18.049 or a little Raspberry Pi that you power up when you're on the road. 00:35:18.069 --> 00:35:21.109 And it just powers up and it starts tracking and reporting immediately. 00:35:21.689 --> 00:35:25.509 And when you turn the engine off, the Raspberry Pi turns off and it stops tracking. 00:35:25.749 --> 00:35:30.629 And you could build your own self-hosted, totally private tracker to track everywhere 00:35:30.629 --> 00:35:33.729 you drive your vehicle to capture all of the cool spots. 00:35:33.869 --> 00:35:36.569 And then when you go back into the application, and this is still... 00:35:38.213 --> 00:35:41.433 This is still very much under work, and it needs a lot more work. 00:35:41.493 --> 00:35:44.833 But when you go back to the application, if you have, and Brent, 00:35:44.953 --> 00:35:50.733 you probably have the best, you can go to MyData and Visits and Places, 00:35:50.753 --> 00:35:56.213 and it will have a list of what it thinks are significant places that you visited. 00:35:56.433 --> 00:35:59.813 And then you can add a note and save them and mark them. 00:36:00.633 --> 00:36:04.513 So you could go back in a day and review and save some of the significant places you stayed at. 00:36:04.593 --> 00:36:08.193 Now, you have to collect them for a bit to get there. But that's also really 00:36:08.193 --> 00:36:11.113 nice for somebody who found a great campground or for somebody who found a great 00:36:11.113 --> 00:36:13.273 restaurant or for somebody who found a new route. 00:36:13.553 --> 00:36:15.913 And it's just really nice because you can mark it and save that for later. 00:36:16.033 --> 00:36:20.773 And they have a UI where they have some suggested places that you could look at. 00:36:20.953 --> 00:36:24.533 They have the ones you've confirmed or ones you want to save or ones you can decline. 00:36:24.673 --> 00:36:26.813 Now, it's a little hard to go through right now because it's just kind of a 00:36:26.813 --> 00:36:29.613 raw list. But I think as they work on that UI, it's going to get a lot better. 00:36:29.793 --> 00:36:32.813 It does have a button now, at least. So it'll pull it up on the map. 00:36:33.773 --> 00:36:35.993 Oh, yeah. Nice. Okay, good. 00:36:35.993 --> 00:36:39.653 It is kind of a zoomed-in map, so you probably have to have some idea of where 00:36:39.653 --> 00:36:41.133 it's showing you, but there's zoom control. 00:36:41.673 --> 00:36:45.653 In OwnTracks, they have something similar called waypoints, and I've been marking 00:36:45.653 --> 00:36:48.093 a few waypoints as we've gone through this experiment. 00:36:49.153 --> 00:36:52.813 But I definitely expected them to show up in the big D-Witch, 00:36:53.013 --> 00:36:55.053 and no go. Not yet, anyway. 00:36:55.053 --> 00:36:57.173 Yeah, I don't think those make it up. Yeah, that's the thing. 00:36:57.293 --> 00:36:59.413 You've got to mark them in the D-Witch if you want to save them. 00:36:59.513 --> 00:37:03.653 It'd be great to have, if they ever make a data app for Android and on the iOS 00:37:03.653 --> 00:37:05.153 one, it would be great to say, oh, save this. 00:37:05.993 --> 00:37:08.813 So you boys got to play with something that I didn't mess around with, 00:37:08.893 --> 00:37:12.173 even though I'm a big fan of Image, the self-hosted Google Photos alternative. 00:37:12.793 --> 00:37:17.153 You, Wes, and Brent played around a little bit with Image integration with the Big D Witch. 00:37:17.513 --> 00:37:22.713 Yeah, I believe it supports both Image and Photo Prism, if you're a Photo Prism user. 00:37:23.233 --> 00:37:29.073 And you go into your user settings, and you just give it the URL string that 00:37:29.073 --> 00:37:33.173 you need, as well as the API key, and then it can start pulling in, 00:37:33.966 --> 00:37:37.186 I think it just sucks through all the various photos in your image and looks 00:37:37.186 --> 00:37:41.606 for GPS data and then converts that to point information and feeds that into 00:37:41.606 --> 00:37:43.466 the trip stuff you were talking about, etc. 00:37:44.146 --> 00:37:48.246 Yeah, in fact, image stores in the database location information separately, 00:37:48.246 --> 00:37:50.266 so it can probably just pull that right from the database. 00:37:50.486 --> 00:37:52.466 So what did you see after this process was done? 00:37:52.926 --> 00:37:56.066 Well, it does process a little bit, so it's not instant. I mean, 00:37:56.186 --> 00:37:59.186 Wes and I were a little... We were going to dinner when we were doing this. 00:37:59.266 --> 00:38:01.486 And we were a little impatient. You got a big database, Wes? 00:38:01.866 --> 00:38:02.586 You know it. 00:38:02.706 --> 00:38:03.726 A lot of dog photos in there. 00:38:04.186 --> 00:38:08.066 But the nice thing is that then in Devarich on the map. 00:38:08.186 --> 00:38:08.666 I'm sorry, what? 00:38:09.426 --> 00:38:10.746 DeWitch, I think we're calling it. 00:38:12.766 --> 00:38:17.486 You end up with these little photo circles, little sort of. 00:38:17.986 --> 00:38:18.826 Overlaid on the map. 00:38:19.226 --> 00:38:23.306 But also the photo preview itself overlaid on the map, which is a nice touch. 00:38:23.606 --> 00:38:29.446 And you can hover over them and get like the photo itself and a bunch of metadata, which was nice. 00:38:29.666 --> 00:38:33.386 And it also, Chris, allows you to click and see everything else on that date. 00:38:33.966 --> 00:38:34.926 Or that location, sorry. 00:38:35.106 --> 00:38:35.726 Oh, really? 00:38:35.826 --> 00:38:36.586 In that location, yeah. 00:38:36.646 --> 00:38:37.926 That was a functionality we 00:38:37.926 --> 00:38:41.286 were particularly hoping to get out of Google Photos, which it does not. 00:38:41.546 --> 00:38:45.686 It's not necessarily, I think, super optimized. A lot of this is pretty new in beta. 00:38:46.006 --> 00:38:49.766 So, like, we were noticing, as we were bootstrapping the image, 00:38:49.766 --> 00:38:53.246 I just started syncing all of the photos to my phone. But so I decided that 00:38:53.246 --> 00:38:54.666 was probably not a tenable idea. 00:38:55.406 --> 00:38:55.986 Yeah, yeah, yeah. 00:38:56.046 --> 00:38:59.706 So, you can see it sort of, you know, I'd just taken a trip to visit my folks. 00:38:59.866 --> 00:39:01.966 Or we were doing it at LinuxFest Northwest, and some of those got there. 00:39:01.966 --> 00:39:03.906 So you can see like the various regions populating. 00:39:04.126 --> 00:39:07.386 So you have a ton of photos right now. It seems to like load them, 00:39:07.566 --> 00:39:13.426 not necessarily in like one optimized batch, but it was actually quite useful to see. 00:39:13.606 --> 00:39:18.746 And I think maybe it would be less useful in the neighborhood you're in all 00:39:18.746 --> 00:39:23.126 the time, but especially for going on trips and just seeing little reminders of like, oh, right. 00:39:23.206 --> 00:39:27.286 There was that waterfall from that hike that we did over in these mountains or that seems great. 00:39:27.506 --> 00:39:30.726 Yeah, I agree. So can you tell us a little bit about how you did set it up? 00:39:30.726 --> 00:39:32.586 I know they have a Docker Compose. 00:39:32.726 --> 00:39:35.426 It looks like it's pretty straightforward, although it's kind of a kitchen sink 00:39:35.426 --> 00:39:38.466 application. I say that with love, but it's a big Docker Compose. 00:39:38.566 --> 00:39:42.066 Yeah, it's a Ruby app. We haven't had one of those for a minute. 00:39:42.746 --> 00:39:50.286 It's also powered by Postgres and PostGIS for that GPS processing geospatial 00:39:50.286 --> 00:39:51.506 data handling, which is great. 00:39:52.066 --> 00:39:54.866 There's a Redis container in there too, app container. 00:39:55.566 --> 00:39:59.386 It is quite built out. They've set up a lot of nice things. I will say right 00:39:59.386 --> 00:40:05.046 there's health checks for a lot of these guys and it's kind of pre-figured out 00:40:05.046 --> 00:40:08.706 a fair amount of spots you can put in like oh here's how you know you want to make sure that you're, 00:40:09.679 --> 00:40:12.619 Maybe you wanted to respond on localhost, but you also wanted to know that it 00:40:12.619 --> 00:40:15.319 is proxy behind this domain name that you're serving it from. 00:40:15.439 --> 00:40:17.599 So there's already some, like, nvars set up for that. 00:40:17.699 --> 00:40:21.959 Which worked for us because you had Nginx in front of this as a reverse proxy, which was fantastic. 00:40:22.559 --> 00:40:25.319 NixOS, indeed. Yeah, so it was really easy. 00:40:25.419 --> 00:40:30.719 So NixOS just built up some Nginx to quickly play Let's Encrypt Proxy. 00:40:30.939 --> 00:40:34.179 And then this thing was just powered by Podman. 00:40:34.639 --> 00:40:37.839 So it works just fine with Podman, Podman Compose, if you want to use their 00:40:37.839 --> 00:40:40.439 standard Docker Compose thing. or Docker, obviously. 00:40:40.679 --> 00:40:42.939 I just love it because it's like, yeah, there's a Docker Compose available, 00:40:43.139 --> 00:40:44.799 Wes. And Wes is like, great. Yeah, I'll take a look at this. 00:40:44.959 --> 00:40:47.859 Okay, I got it running in Podman. Like, okay, let's go. 00:40:48.159 --> 00:40:52.179 Chris, you did notice that someone's working on a NixOS module for this. 00:40:52.359 --> 00:40:56.419 Yes, although it's been a month, but there does seem to be a module in the works, 00:40:56.419 --> 00:41:01.639 which would be really, really great because this is definitely something I'm keeping after the show. 00:41:02.139 --> 00:41:05.819 I'm going to keep this running. I'm going to put it on my rig directly and I'm 00:41:05.819 --> 00:41:07.999 going to track every road trip I take with this thing. 00:41:08.599 --> 00:41:15.559 I love it. And they do also offer a hosted version, which is €5 a month, 00:41:15.559 --> 00:41:19.959 which works out to be about €60 a year, which is an early access discount. 00:41:20.719 --> 00:41:23.539 But, you know, you can run on anything. Like I said, it's a Docker container. 00:41:23.539 --> 00:41:25.839 You can put it on a Raspberry Pi. You can put it on a VPS. 00:41:26.959 --> 00:41:30.019 You can fire it up when you need it and export the data when you don't because 00:41:30.019 --> 00:41:31.919 it does have import and export options there. 00:41:33.059 --> 00:41:35.659 Right now, was it a little tricky to get multi-user working? 00:41:35.779 --> 00:41:37.759 I had a sense you had to do some finagling. 00:41:37.959 --> 00:41:44.559 Oh, yes. a good point there. It didn't, it came with the default user, like a demo user. 00:41:44.719 --> 00:41:47.539 It was not necessarily clear how to make more. 00:41:47.939 --> 00:41:50.879 Admittedly, I did not read all of the documentation, surely. 00:41:51.319 --> 00:41:55.379 But what I ended up doing was just manually inserting some more rows into the 00:41:55.379 --> 00:42:01.119 user table, which did mean for a little bit I did not manage to give us each 00:42:01.119 --> 00:42:02.919 unique API keys, which caused some confusion. 00:42:03.039 --> 00:42:05.359 You know, if you go into the settings, there's an add user button. 00:42:05.519 --> 00:42:05.959 Is that right? 00:42:06.179 --> 00:42:10.579 Yeah, yeah. Jesus, Wes. Oh, my God. 00:42:10.779 --> 00:42:14.439 Anyways, yeah, so be aware. Depending on how you create the user account, 00:42:14.519 --> 00:42:15.639 you need to generate new API keys. 00:42:15.639 --> 00:42:15.719 Oh, I see. Yeah, you're right. 00:42:18.959 --> 00:42:20.339 Well, then don't do like I do. 00:42:22.419 --> 00:42:25.219 It worked, though. Yeah, so we actually have... 00:42:25.219 --> 00:42:26.419 I should have made you the administrator. 00:42:26.679 --> 00:42:32.479 We have four users on this system. Wes, you have 1,017 points of locations tracked. 00:42:32.479 --> 00:42:37.439 I have 2,535 and Brent, you have 1,376. 00:42:37.619 --> 00:42:39.179 I'm surprised I beat you actually. 00:42:39.979 --> 00:42:44.339 I wonder why that is because I moved around a lot more than you did. 00:42:44.439 --> 00:42:45.179 And we're tracking sooner. 00:42:45.319 --> 00:42:48.679 And I was trying to have it report quite aggressively because I figured. 00:42:48.879 --> 00:42:54.559 Well, so do I. I maxed it. I wonder why. Maybe it's because for a little bit 00:42:54.559 --> 00:42:56.259 I fed home assistant in. I don't know. 00:42:56.819 --> 00:43:01.139 But I'll take that as a win. That means I'm the winner of the points of tracking. 00:43:01.139 --> 00:43:02.819 Is that how we're measuring this? 00:43:03.059 --> 00:43:03.179 Yay! 00:43:06.682 --> 00:43:10.442 There's not many podcasts out there that are trying to go at it full-time making 00:43:10.442 --> 00:43:14.242 a great Linux podcast, and we take it very seriously, but we need your support. 00:43:14.362 --> 00:43:15.322 Now you can become a sponsor. 00:43:15.602 --> 00:43:18.402 If you think you want to reach the greatest Linux audience in history, 00:43:18.562 --> 00:43:20.762 email me, chris at jupiterbroadcasting.com. 00:43:20.902 --> 00:43:23.202 I'll make a great deal for somebody that listens to this show, 00:43:23.262 --> 00:43:26.742 but of course you can be a sponsor if you're a listener by boosting us using 00:43:26.742 --> 00:43:31.702 Fountain FM or something like that, or by becoming a member at linuxunplugged.com slash membership. 00:43:32.062 --> 00:43:35.002 That's a pretty sweet deal because you get the bootleg version which 00:43:35.002 --> 00:43:37.922 right now is clocking in at a healthy one hour and 16 00:43:37.922 --> 00:43:41.122 minutes and it's not just random chit chat we get extra 00:43:41.122 --> 00:43:45.042 content just for our members you also get a shorter version if that's your speed 00:43:45.042 --> 00:43:50.182 with no ads and all of the production quality of our editor drew so you have 00:43:50.182 --> 00:43:53.582 options as a member or you can support each production with a boost and send 00:43:53.582 --> 00:43:59.102 a message or reach the greatest audience in linux history email me chris at 00:43:59.102 --> 00:44:00.462 jupiterbroadcasting.com. 00:44:03.122 --> 00:44:08.502 Well we have some feedback this week Wes you went to a little meetup. 00:44:08.502 --> 00:44:11.922 Yes so Tailscale hosted 00:44:11.922 --> 00:44:16.602 a Seattle meetup I guess the first sort of community meetup they've done but 00:44:16.602 --> 00:44:21.742 it sounds like they're hoping to do more big shout out to the team Natasha and 00:44:21.742 --> 00:44:26.642 the rest of the Tailscale folks for putting it on great meetup I thought well 00:44:26.642 --> 00:44:29.562 attended well run there was snacks drinks, 00:44:30.202 --> 00:44:32.962 and folks giving little talks, including myself. 00:44:33.542 --> 00:44:37.882 And it reminded me a lot of a JB meetup in the sense that there was just a diverse 00:44:37.882 --> 00:44:42.082 array of folks from folks who were, you know, doing some serious tail scale 00:44:42.082 --> 00:44:48.122 at work with like massive network traffic to folks doing neat stuff with IPv6 in their home web. 00:44:48.362 --> 00:44:48.782 Oh, really? 00:44:48.942 --> 00:44:49.262 Oh, yeah. 00:44:49.642 --> 00:44:51.762 That's fun. Did you run into any listeners? 00:44:52.522 --> 00:44:55.682 Yes, definitely some listeners. And then some folks who maybe, 00:44:55.842 --> 00:44:58.242 hopefully, are listening now or thought Maybe they might check it out. 00:44:58.362 --> 00:44:59.642 Well, hello to them. Thanks for listening. 00:45:00.602 --> 00:45:04.222 And Tailscale's own Brad Fitzpatrick gave a sort of gripe fest of things they 00:45:04.222 --> 00:45:07.722 wanted to fix. They know our issues in Tailscale. So that was fascinating. 00:45:08.062 --> 00:45:09.662 Oh, that's great. Brad was there. That's great. 00:45:09.822 --> 00:45:14.262 And then folks were able to sort of, you know, quiz him on, are you considering this feature? 00:45:14.462 --> 00:45:17.842 How about that? Could it ever work? So you got a little Tailscale nerdery. 00:45:17.922 --> 00:45:19.162 A lot of folks sharing stories. 00:45:19.702 --> 00:45:24.202 Some folks from Cumulo told a story of how Tailscale saved them during like 00:45:24.202 --> 00:45:27.062 a big outage they were having. and their tailscale backdoor was the only way 00:45:27.062 --> 00:45:28.882 they had access to that remote data center. 00:45:29.122 --> 00:45:34.442 So a lot of great nerding out about fun networking and home lab and all kinds 00:45:34.442 --> 00:45:37.482 of crazy stuff you can do with tailscale. Here's how you know. 00:45:37.642 --> 00:45:42.482 I talked with another presenter there and we were just sharing tailscale stories. 00:45:42.602 --> 00:45:45.882 And I was like, yeah, you know, it really, it's surprising how well it runs in an initramfs. 00:45:47.359 --> 00:45:50.299 Not surprised at all. Dude was like, yeah, yeah, it really does. It's great. 00:45:50.959 --> 00:45:54.459 That's what I love about JB meetups and these type of meetups, 00:45:54.559 --> 00:45:55.999 is you can say something like that. 00:45:56.099 --> 00:45:59.039 And it doesn't go right over somebody's head. They know exactly what you're talking about. 00:45:59.699 --> 00:46:02.719 And also, it's nice to know people are doing crazier things than we are. 00:46:03.119 --> 00:46:06.119 Yeah, we're not the only ones doing wild stuff. Well, that's neat. 00:46:06.159 --> 00:46:07.919 We were on the road. I'm glad you could make it. 00:46:08.639 --> 00:46:12.199 So, yeah, I don't have any insider details or anything, but do keep an eye out 00:46:12.199 --> 00:46:16.239 if you're a Tailscale fan. And maybe they'll do a meetup in an area near you sometime. 00:46:16.239 --> 00:46:19.199 I really would love to do more meetups in general. So we should keep an eye 00:46:19.199 --> 00:46:21.819 out for other meetups. We should do more of our local meetups. 00:46:22.979 --> 00:46:25.679 You know, maybe somebody out there wants to be part of the crew one day, 00:46:25.759 --> 00:46:28.159 and the meetups seem to be a great way to discover new people as well. 00:46:28.459 --> 00:46:29.739 Isn't that how Wes showed up? 00:46:29.999 --> 00:46:33.099 That is. And you kind of did too. I mean, LinuxFest essentially was a meetup. 00:46:33.179 --> 00:46:33.219 Right? 00:46:33.219 --> 00:46:33.419 That's true. 00:46:33.599 --> 00:46:33.899 Good point. 00:46:34.099 --> 00:46:37.739 Oh, I definitely met a few folks who had just gone to LinuxFest Northwest there too. 00:46:37.879 --> 00:46:38.019 No kidding? 00:46:38.239 --> 00:46:38.519 Absolutely. 00:46:38.779 --> 00:46:41.819 That's great. Yeah. Boy, LinuxFest. It feels like it was just yesterday. 00:46:42.599 --> 00:46:44.419 And I already miss it too. It was a good one. 00:46:44.559 --> 00:46:45.839 To me, it feels like it was a month ago. 00:46:45.979 --> 00:46:49.999 Really? It feels like we just went to Linux Fest and then we were on our trip. 00:46:50.179 --> 00:46:51.039 Well, that is true. 00:46:51.339 --> 00:46:53.299 Yeah, that is true. That is how it kind of went, isn't it? 00:46:54.439 --> 00:46:58.999 Well, we got a baller booster here, our dear PJ. 00:47:03.359 --> 00:47:07.899 Jeff, you sent in 68,382 sets. 00:47:09.119 --> 00:47:14.219 Here's your little message. I've used both a laptop and that small PC for home 00:47:14.219 --> 00:47:18.659 assistant. The power use is about the same, but the laptop is significantly 00:47:18.659 --> 00:47:23.779 faster, has way more RAM, and can be used for more than just Home Assistant. 00:47:24.059 --> 00:47:30.479 With the laptop, I was able to actually use the voice stuff and ESB Home builds in less than a minute. 00:47:30.679 --> 00:47:32.839 I like that you call it a little message. Did you catch that? 00:47:33.219 --> 00:47:36.159 It's a little message. It's our baller boost, buddy. 00:47:36.299 --> 00:47:40.879 I also like that he's addressing it to Jeff. As if we read all of the boosts to Jeff. 00:47:40.879 --> 00:47:46.759 I've spent so much time with Jeff. I mean, we've been under vehicles together in the last couple days. 00:47:46.839 --> 00:47:49.799 I feel like we've moved to a new level in our friendships. 00:47:50.019 --> 00:47:52.819 Yeah, he farted in front of us. So there's that. 00:47:53.219 --> 00:47:54.659 Like I said, new friendship. 00:47:54.839 --> 00:47:57.519 Now, this is where PJ and I have a disagreement. 00:47:58.843 --> 00:48:01.943 Technically, he is right. It is a better machine, it is faster, 00:48:02.143 --> 00:48:05.643 it can do more things, and it has a built-in battery screen and keyboard. 00:48:05.683 --> 00:48:07.783 So it's basically everything you'd want, right? 00:48:08.203 --> 00:48:12.363 And when Brent is unwilling to reboot his framework, it could be a backup show machine. 00:48:12.523 --> 00:48:17.883 Oh, that's true too. However, as somebody who has lived for 10 years in a tiny 00:48:17.883 --> 00:48:23.223 rig, I can tell you there are certain things that are absolutely just invaluable. 00:48:23.223 --> 00:48:26.563 And one of them is as small as possible. 00:48:26.763 --> 00:48:31.783 No monitor, no keyboard, nothing. A laptop, if you can believe it, is too big. 00:48:32.583 --> 00:48:37.723 It is too big. I know. And so what you do is you, and also I'm a big believer 00:48:37.723 --> 00:48:41.143 in integrating home assistant into everything. 00:48:41.203 --> 00:48:44.763 So your water pump, your water heater, everything you do in your RV, 00:48:44.863 --> 00:48:46.603 your lights is going to be run by home assistant. 00:48:47.223 --> 00:48:50.143 Maybe even the ignition one day, the generator star is going to be home assistant. 00:48:50.303 --> 00:48:52.823 It's going to be home assistant for everything. It's going to be crazy, 00:48:52.963 --> 00:48:57.263 Brent. And you're going to use it for just absolutely everything we can possibly think of. 00:48:57.463 --> 00:48:59.643 And so we want this to be its own dedicated machine. 00:48:59.783 --> 00:49:01.523 Do I start my engine through Home Assistant? 00:49:01.843 --> 00:49:05.143 I actually would be totally down for figuring that out. If you think about it, 00:49:05.223 --> 00:49:06.043 it could be really genius. 00:49:06.323 --> 00:49:08.463 I mean, it probably pre-warms the shower for you. 00:49:08.603 --> 00:49:11.663 Well, like a lot of losers, when they get remote start, they have like some 00:49:11.663 --> 00:49:13.863 sort of remote system. You know, what is that? 00:49:14.083 --> 00:49:14.783 Proprietary for sure. 00:49:14.983 --> 00:49:18.403 You could remote start from anywhere. And there's actually valuable. 00:49:18.703 --> 00:49:22.043 There's actually value in that because maybe your batteries are getting low. 00:49:22.043 --> 00:49:23.503 You want a little bit of alternator charge. 00:49:23.803 --> 00:49:26.023 You know what? You bring up the old Home Assistant app, you hit the button, 00:49:26.103 --> 00:49:28.503 and ESP connects a relay. Boom, your engine started. 00:49:28.623 --> 00:49:31.603 It's a pretty short list of folks that have remote started over WireGuard. 00:49:31.743 --> 00:49:32.703 So you could be on that list. 00:49:32.703 --> 00:49:34.803 I think we could do it. And I'm saying, when I say everything, 00:49:34.963 --> 00:49:37.943 I mean, you really need to think about it because it changes your life. 00:49:37.943 --> 00:49:40.443 And so you want this to be its own dedicated appliance. 00:49:41.583 --> 00:49:44.903 Hard, solid, only does one thing, and that's automate your life. 00:49:46.243 --> 00:49:50.163 So you're not going to run Graphana on this thing. You're not going to run VS Code. 00:49:50.283 --> 00:49:52.703 Well, maybe you'll run VS Code, but you're not going to even do voice stuff 00:49:52.703 --> 00:49:55.683 on this thing. You're only going to run your automations and your home assistant 00:49:55.683 --> 00:49:57.283 and your controls and your dashboard, and that's it. 00:49:59.007 --> 00:50:03.887 Is there an argument for, you know, Olympia Mike who just keeps supplying them 00:50:03.887 --> 00:50:05.627 with backup Xbox for decades? 00:50:06.307 --> 00:50:09.467 So I'm just actually, you know, I'm having some fun. But my point is really, 00:50:09.747 --> 00:50:12.987 I find it super valuable to have a dedicated machine. 00:50:13.107 --> 00:50:18.427 And I've gotten by on a Raspberry CM4 with two gigs of RAM for two, three years now. 00:50:18.787 --> 00:50:20.747 Weren't you just saying this morning you really want to upgrade? 00:50:20.747 --> 00:50:21.807 I do. I think it needs more memory. 00:50:21.947 --> 00:50:22.367 Oh, okay. 00:50:22.387 --> 00:50:23.087 But you have eight gigs. 00:50:23.267 --> 00:50:24.247 Oh, that's true. 00:50:24.487 --> 00:50:27.187 Yeah. So, you know, yes. and then i think the way 00:50:27.187 --> 00:50:30.407 you do the other stuff like uh voice analysis locally 00:50:30.407 --> 00:50:33.147 um you know whatever services like 00:50:33.147 --> 00:50:36.567 jellyfin you might want to run whatever else that's an odroid that's something 00:50:36.567 --> 00:50:39.387 else that's also very small or it's a raspberry pi whatever it is but it's very 00:50:39.387 --> 00:50:45.767 small it's dedicated to just a few things also dc power um that's at least my 00:50:45.767 --> 00:50:50.467 thoughts so i mean he's right and i feel like i'm right it's just a it's just your point of view and. 00:50:50.467 --> 00:50:54.627 You do have to consider if you want the support contract from Chris Lasko. 00:50:54.627 --> 00:50:55.367 Industries. Yeah, right. 00:50:55.367 --> 00:50:58.667 You probably do have to go with his recommendations for the document you signed. 00:50:58.907 --> 00:51:00.527 Yeah, let's we'll review the contract. 00:51:02.247 --> 00:51:07.047 Turd Ferguson boots in with 27,333 sats. 00:51:09.527 --> 00:51:15.147 Starting off here too, Boos, sending sats and good vibes for the van rescue. 00:51:15.667 --> 00:51:17.167 Mmm, I think those vibes helped. 00:51:17.467 --> 00:51:19.287 Thank you, Turd. It did, certainly. 00:51:19.527 --> 00:51:20.827 I think we could have used those 00:51:20.827 --> 00:51:24.267 vibes a little sooner, but once we got to Oregon things turned around. 00:51:24.427 --> 00:51:26.347 Could he use those vibes for like restaurant choosing? 00:51:26.687 --> 00:51:29.907 Yeah, and some of the gas tank work, and some of the electrical, 00:51:30.147 --> 00:51:33.127 and that exhaust leak that we fixed and then unfixed. 00:51:33.727 --> 00:51:34.767 I don't remember that one. 00:51:34.807 --> 00:51:36.507 We'll get into that. We'll get into that later. 00:51:36.647 --> 00:51:39.307 Yeah, that's because of the exhaust. It does stuff to the old memory. 00:51:39.507 --> 00:51:43.027 It does make you very sleepy. But that's for the launch. Thank you, Turd. 00:51:43.227 --> 00:51:47.807 Okay, and then second boost here. Did you know, in May of 92, 00:51:48.407 --> 00:51:56.167 SLS not Slackware was the first Linux distro, making installs way easier and 00:51:56.167 --> 00:51:57.987 sparking the distro boom. 00:51:58.727 --> 00:52:06.087 SLS in 1992, not Slackware. Do you remember what SLS stands for? I think. 00:52:06.567 --> 00:52:07.347 Linux trivia. 00:52:07.747 --> 00:52:14.287 I think it's soft landing Linux. The idea was making it easy to get started with Linux, if I recall. 00:52:14.607 --> 00:52:15.647 Way back in 92. 00:52:15.967 --> 00:52:16.967 Yeah, isn't that something? 00:52:17.187 --> 00:52:18.867 I think we can still install it today. 00:52:19.007 --> 00:52:24.967 I do not. have you tried maybe in camu maybe we could do it in camu thank you 00:52:24.967 --> 00:52:26.067 turd appreciate the boost. 00:52:26.567 --> 00:52:30.427 Well fabian sent in 10 000 sats oh i think it's fabine, 00:52:33.626 --> 00:52:38.186 Trying to prep for the TUI challenge, I've been trying to find a good way to watch YouTube. 00:52:38.606 --> 00:52:44.086 All those YouTube TUIs seem to be based on NVIDIAs, which gets blocked all the time. 00:52:44.566 --> 00:52:48.926 So I created my own based on the YouTube API, and we'll just show you a list 00:52:48.926 --> 00:52:51.046 of videos by your subscriptions in the TUI. 00:52:51.186 --> 00:52:54.946 It's not real YouTube subs, but then it opens an MPV. 00:52:55.166 --> 00:52:57.566 This saves so many gigs of RAM. 00:52:58.586 --> 00:53:02.526 You know, I would rather just have a UI that shows me my subscriptions anyways. 00:53:03.246 --> 00:53:08.346 but raises I think one of our first gray areas that we need the listeners to 00:53:08.346 --> 00:53:13.646 help us clarify does launching MPV from the terminal count since that is technically 00:53:13.646 --> 00:53:15.586 a graphical application right. 00:53:16.606 --> 00:53:20.746 I think one can make the argument that if you're controlling it from the terminal 00:53:20.746 --> 00:53:25.486 and it's something that the terminal can't reasonably provide in a realistic 00:53:25.486 --> 00:53:28.306 sense maybe but you gotta. 00:53:28.306 --> 00:53:30.986 Boost in to tell us or contribute Yeah, because I feel like maybe that's the 00:53:30.986 --> 00:53:33.246 line. If the terminal can't do it, you can't do it. 00:53:34.126 --> 00:53:36.766 There must be a terminal out there that does it, right? 00:53:37.206 --> 00:53:40.566 Well, there's LibCaca. That's the bargain basement version. 00:53:40.886 --> 00:53:41.466 I'm sorry? 00:53:41.646 --> 00:53:44.006 Are you okay? Yeah, I mean, look it up. 00:53:44.106 --> 00:53:45.906 Do you need to lay down? Are you all right? 00:53:46.126 --> 00:53:46.986 Well, that's a separate matter. 00:53:47.286 --> 00:53:51.906 Okay. It can't be done. I mean, maybe, because couldn't I just launch Chrome 00:53:51.906 --> 00:53:53.726 from my terminal if this is okay? 00:53:54.626 --> 00:53:56.766 Oh, yeah, I don't think that would be okay. 00:53:56.966 --> 00:53:58.846 Right, so where do we draw the line here? well. 00:53:58.846 --> 00:54:01.486 You know Chrome's a full featured thing this is literally. 00:54:01.486 --> 00:54:04.026 Just launching not a full featured thing compared. 00:54:04.026 --> 00:54:04.806 To a web browser. 00:54:04.806 --> 00:54:07.606 Well okay I'll give you that web browser's practically an operating system. 00:54:08.786 --> 00:54:09.866 Just needs a good text. 00:54:09.866 --> 00:54:14.286 Out of it okay well why couldn't I launch you know Zed or VS Code or Gedit. 00:54:15.408 --> 00:54:17.748 Yeah, I mean, there's a slippery slope to be pointed out here. 00:54:17.748 --> 00:54:19.568 I feel like it's too slippery. You see what I'm saying? 00:54:19.988 --> 00:54:20.988 So we need... 00:54:20.988 --> 00:54:24.788 We need the listeners to either boost in or participate in the GitHub and clarify 00:54:24.788 --> 00:54:26.128 this particular gray area. 00:54:26.268 --> 00:54:31.148 Because I don't know how to... Because I want to watch videos. So I want this. 00:54:31.408 --> 00:54:35.608 But I recognize it opens up the door to cheating. It really does, boys. 00:54:35.728 --> 00:54:37.668 Do we have like a pre-approved shortlist or something? 00:54:38.008 --> 00:54:42.588 Hmm. Hmm. An approved list. Like MPV and VLC, maybe? 00:54:42.788 --> 00:54:46.428 Or like for specific carve-outs, right? You can't do a browser, but you can. 00:54:46.588 --> 00:54:49.568 If you're just playing videos, that's fine as long as you launch it from the 00:54:49.568 --> 00:54:51.268 terminal. But I don't know. 00:54:51.268 --> 00:54:55.448 I don't have the answers here. I don't know. I don't know. Because you can't 00:54:55.448 --> 00:54:56.408 watch videos in a terminal. 00:54:56.988 --> 00:54:59.608 Unless, like Minimek tells us, you use Enlightenment. Then you could. 00:54:59.828 --> 00:55:01.428 Maybe I'll just use Enlightenment. I don't know. 00:55:01.548 --> 00:55:06.068 No, no. It's a standalone. It's a standalone application. You need the AFL libraries. 00:55:06.128 --> 00:55:10.688 You just install terminology, and then you're in. It's part of every distribution. 00:55:11.908 --> 00:55:14.528 Well, look at that. A little Enlightenment technology saving the day. 00:55:14.528 --> 00:55:18.148 So I feel like if the terminal is natively capable of doing the task. 00:55:18.868 --> 00:55:20.488 Then you should do it there. Yeah, agreed. 00:55:20.728 --> 00:55:25.448 Yeah, then that's okay. Ooh, maybe that's the line. We got to figure this out. 00:55:25.588 --> 00:55:29.648 I have a prediction. Okay. I think we're going to find several other gray spots 00:55:29.648 --> 00:55:30.748 that we're going to have to figure out. 00:55:30.908 --> 00:55:31.888 Oh, great. Thanks, Brent. 00:55:32.028 --> 00:55:32.408 Oh, you're welcome. 00:55:32.588 --> 00:55:35.788 Oh, my God. Oppie 1984 comes in with 4,000 sats. 00:55:38.708 --> 00:55:42.808 Brett, if you plan on doing any traveling with the van and why have a van if 00:55:42.808 --> 00:55:46.128 you're not going to travel, then I suggest a GMRS radio. 00:55:46.628 --> 00:55:51.288 Most truckers have switched from the old CB to GMRS, and while you need a license 00:55:51.288 --> 00:55:56.348 to transmit, you can listen without a license, and I know you like to listen. 00:55:56.668 --> 00:56:01.128 Also, you have to build a meshtastic node because, well, reasons, Brent. I mean, Brett. 00:56:01.568 --> 00:56:04.788 Well, I will say I did bring my meshtastic node on this trip. 00:56:04.888 --> 00:56:05.128 Uh-huh. 00:56:05.528 --> 00:56:10.408 I mostly forgot to check it, and also I don't think it picked up very much, 00:56:10.408 --> 00:56:12.448 or I'm using it wrong, or Jeff saved me. 00:56:13.108 --> 00:56:15.708 But I do think it's a great idea to put some radios in there. 00:56:15.828 --> 00:56:21.348 I'd be curious to hear why the truckers have moved from CB to this new GMRS. 00:56:21.928 --> 00:56:25.688 Yeah, I would actually like to know that too. Because the CB is such a classic thing. It is. 00:56:25.828 --> 00:56:31.268 I do know that when I did my research in GMRS does seem to be a lot more popular, so I'd plus one that. 00:56:31.428 --> 00:56:35.848 But I think what you'd want is kind of like a dedicated MeshTastic node built in. 00:56:36.948 --> 00:56:39.808 Maybe even something that has its own power source. Put a little solar panel 00:56:39.808 --> 00:56:40.908 for it. I don't know. I'm just saying. 00:56:40.908 --> 00:56:44.848 You know, if you just stick to CB, you could be CB Brent and, 00:56:44.848 --> 00:56:48.168 you know, sort of big fish, small pond, right? 00:56:48.208 --> 00:56:51.448 You're the guy on the CB all the time. So anyone who's listening, they're getting you. 00:56:51.808 --> 00:56:54.988 He's already buying tapes. Right. You went to the thrift store and bought a bunch of tapes. 00:56:54.988 --> 00:56:55.248 I did. 00:56:55.548 --> 00:56:57.028 So he's kind of got a retro vibe going. 00:56:57.128 --> 00:56:57.908 Diana Ross. Pretty good. 00:56:58.148 --> 00:56:58.508 Yeah. Yeah. 00:56:58.888 --> 00:57:04.048 I think maybe coming near you, CB Radio will feature Linux Unplugged maybe next week. 00:57:04.248 --> 00:57:08.768 The one, the only, the genius bean himself, Gene Bean, comes in with a row of ducks. 00:57:10.145 --> 00:57:14.885 Just wanted to say that I'm amazed at how nice the headsets you used at LinuxFest sound. 00:57:15.105 --> 00:57:15.405 Oh, good. 00:57:16.245 --> 00:57:19.465 On another note, I love hearing what y'all are doing with Home Assistant. 00:57:19.725 --> 00:57:26.185 I am way, way, way down that rabbit hole and would be happy to help if you want. 00:57:26.345 --> 00:57:30.765 Oh, that's great. Gene is a great resource. I'm pretty far down that hole myself. 00:57:30.965 --> 00:57:33.505 I wonder, Gene, like, where are you and I at? Because I'm sure you followed 00:57:33.505 --> 00:57:34.605 my journey on Self-Hosted. 00:57:34.925 --> 00:57:39.025 I loved giving folks a tour of Lady Joops' Home Assistant system at LinuxFest. 00:57:39.025 --> 00:57:42.525 There was like three or four different distinct batches of people I brought 00:57:42.525 --> 00:57:44.465 through the RV to show them how things worked. 00:57:45.045 --> 00:57:48.985 And it controls everything. Thank you, Gene Bean. It's good to hear from you. 00:57:49.205 --> 00:57:51.065 Well, son of BoomBus comes in. 00:57:53.525 --> 00:57:56.365 4,444 sats across two booths. I think that's a bunch of ducks. 00:57:59.985 --> 00:58:04.885 What's the least useful Home Assistant integration you have but refuse to delete? 00:58:05.105 --> 00:58:06.365 This does become a problem. 00:58:06.985 --> 00:58:10.545 There's a lot of integrations. I'm seeing as I get more integration set up. 00:58:10.685 --> 00:58:14.025 I don't have any that fit yet, I don't think, because I'm still just still getting 00:58:14.025 --> 00:58:15.505 them configured to my next config, but. 00:58:15.665 --> 00:58:19.225 There's a lot of community repos too, so you can add even more than the built-in 00:58:19.225 --> 00:58:21.065 ones. So you can really go crazy. 00:58:22.365 --> 00:58:26.065 Mine, I think, might be a surprise. I think it's the Jellyfin integration. 00:58:26.365 --> 00:58:31.165 And when I had Plex, because I thought I'd really use that and I'd maybe build 00:58:31.165 --> 00:58:34.125 automations, like we're going to watch a movie and we'll have the lights turn off, 00:58:34.145 --> 00:58:37.685 or I'll have a card that shows what's currently being played and I can hit pause, 00:58:37.685 --> 00:58:43.745 Or I can track how much we watch the TV with the statistics and Home Assistant. Look at me, everybody. 00:58:44.305 --> 00:58:48.145 But the reality is never use it. Never use it for Plex. 00:58:48.265 --> 00:58:51.425 Never use it for Jellyfin. What I found much more useful is a remote control 00:58:51.425 --> 00:58:55.665 and just be able to use the functions of the television via Home Assistant and 00:58:55.665 --> 00:58:56.865 launch any application. 00:58:57.185 --> 00:58:59.725 Now that you've expressed this to yourself, will you delete it? 00:58:59.805 --> 00:59:03.385 No, I think I'll keep it. Great. I mean, it works. 00:59:06.585 --> 00:59:10.145 There you go. Thank you, son of a boom bus. Boom bus isn't a bad name. 00:59:10.225 --> 00:59:12.405 We need people to boost in names for the van. 00:59:12.605 --> 00:59:14.845 Van or bus. Because bang bus isn't sitting well with people. 00:59:15.545 --> 00:59:18.065 Bang bus is not sitting well. They took it in the wrong direction. 00:59:18.725 --> 00:59:22.485 Plus, this way we can make a series of bang bus swag. That'll be the legacy 00:59:22.485 --> 00:59:23.945 swag, limited production run. 00:59:24.045 --> 00:59:24.265 Okay. 00:59:24.405 --> 00:59:25.965 And then we'll have the new swag for the new name. 00:59:26.045 --> 00:59:29.665 Because we're still on top of our swag game. But we need new names. It could be a van. 00:59:29.905 --> 00:59:32.505 It doesn't have to be a bus. It's technically a van. It's a beautiful, 00:59:32.685 --> 00:59:35.945 big, juicy van, really, is what it is. And so just keep that in mind. 00:59:36.085 --> 00:59:37.605 Yes, we call it the bang bus. but it's really, 00:59:40.585 --> 00:59:41.905 a big juicy van. 00:59:46.195 --> 00:59:53.355 Well, Tomato sent in 5,000 SATs. Hearing about the state of the engine ceiling 00:59:53.355 --> 01:00:00.535 in that van, here's some SATs from MQ7 so Brent can get carbon monoxide monitoring going. 01:00:00.895 --> 01:00:04.155 Ooh, now, PJ, you're up to date on the MQ7. 01:00:04.375 --> 01:00:09.815 You've been having some long-term project plans around building an MQ7 sensor, 01:00:10.015 --> 01:00:11.515 right? For carbon monoxide? 01:00:11.775 --> 01:00:15.135 I got a couple of them sensors already. You just need to get some MOSFETs to 01:00:15.135 --> 01:00:18.695 create tiny little heaters on them, and then we can use them with ESP devices. 01:00:19.255 --> 01:00:20.355 Wait, did you say a heater? 01:00:20.915 --> 01:00:21.275 Yep. 01:00:21.615 --> 01:00:25.415 Oh, I feel like I'm going to get in a territory I'm not ready for. 01:00:25.495 --> 01:00:30.055 Yeah, buddy. Yeah, buddy. All right. Thank you, Tomato. It's nice to hear from 01:00:30.055 --> 01:00:32.055 you. Otter Brain came in with a row of ducks. 01:00:33.155 --> 01:00:37.395 He says, thank you, guys. Thanks to you guys, I got three Raspberry Pis going. 01:00:37.535 --> 01:00:42.355 One for Home Assistant, one for NextCloud, and one, of course, for PiHole. 01:00:42.355 --> 01:00:46.295 it's been so much fun learning how to set these up but here's my question any 01:00:46.295 --> 01:00:51.675 suggestions on keeping your headless pies tidy do you have a way of tucking them away, 01:00:52.935 --> 01:00:57.475 here's what I've done I have since destroyed this but what I originally did 01:00:57.475 --> 01:01:01.215 and I really I loved it so much I took pictures you know and I like favorite, 01:01:03.475 --> 01:01:09.255 but I bought a bunch of little sticky pads off of Amazon that have routing for 01:01:09.255 --> 01:01:12.935 wires in them and you can snap wires into them and they have a little 3M backing. 01:01:13.335 --> 01:01:17.975 And I just routed the wires along a wall and just kind of embraced the wires 01:01:17.975 --> 01:01:19.155 but did them nice and tidy. 01:01:19.335 --> 01:01:23.175 And so like the remote disks and like the, I have my Z-Wave and Zigbee sticks 01:01:23.175 --> 01:01:26.135 there off on their own little USB extension cords and those were tidy and put 01:01:26.135 --> 01:01:28.115 there. And I thought that made it look really nice. 01:01:28.375 --> 01:01:31.455 And then for some of my systems, I also threw a Pi KVM on there. 01:01:31.475 --> 01:01:33.815 So I kind of did the same thing for that and just kind of embraced it. 01:01:33.855 --> 01:01:38.915 And I got that also the double-sided 3M Velcro off of the Jungle Store. 01:01:39.095 --> 01:01:42.295 And I just put that on the devices and I stick that to the wall, too. 01:01:42.515 --> 01:01:45.555 And then it makes it really easy to pop them off and change something and pop 01:01:45.555 --> 01:01:48.955 it back on. And you just embrace the wires, but you make them look good. 01:01:49.315 --> 01:01:51.835 And then it looks engineered and not messy. 01:01:52.515 --> 01:01:55.815 It would be sweet if there was, like, a Raspberry Pi backplane you could just 01:01:55.815 --> 01:01:58.495 kind of plug them into. Wouldn't that be sweet? 01:01:58.615 --> 01:02:00.195 I mean, folks have that. 01:02:00.415 --> 01:02:00.935 Do they? 01:02:01.095 --> 01:02:03.575 Well, versions of it. There's, you know, various enclosures, 01:02:03.695 --> 01:02:06.595 especially for mounting, like, a bunch with built-in switches and then. 01:02:07.435 --> 01:02:11.135 Yeah, I like that. I love that. I should build something like that and just 01:02:11.135 --> 01:02:15.215 you know, you would, oh man wouldn't it be great if the CM4 platform had gone 01:02:15.215 --> 01:02:16.315 that way with carrier boards? 01:02:16.835 --> 01:02:19.215 Oh, that'd be a way. That would be a way. 01:02:20.495 --> 01:02:23.675 The dude abides us 15,000 cents. 01:02:26.871 --> 01:02:31.831 I'm always reminded to boost live on Sundays when that Matrix notification pops up. 01:02:31.951 --> 01:02:32.831 Aw, thank you, dude. 01:02:32.971 --> 01:02:33.231 Yeah. 01:02:33.551 --> 01:02:36.031 Nice Home Assistant interview, too. More of those, please. 01:02:36.271 --> 01:02:41.351 I really like Polis. I think Polis is good people. And I really respect the 01:02:41.351 --> 01:02:45.511 trajectory they've taken, because I've been following them for a little bit over five years now, 01:02:45.551 --> 01:02:49.571 and they've just been taking the right step after the right step to make sure 01:02:49.571 --> 01:02:51.471 that if you deploy something using Home Assistant, 01:02:51.771 --> 01:02:54.351 it's not going to get clouded up, it's not going to get identified, 01:02:54.431 --> 01:02:55.631 it's going to be supported. 01:02:55.631 --> 01:02:58.511 And I really appreciate the direction they've taken things. Thank you. 01:02:59.511 --> 01:03:03.071 We also are very sensitive to not overdoing the interviews. 01:03:03.211 --> 01:03:06.111 We know not every guest is dynamic and interesting, but we think Paulus is one 01:03:06.111 --> 01:03:08.991 of those. So we do monitor the feedback on the interviews. Those types of things 01:03:08.991 --> 01:03:10.851 are always signals that we're looking for from you guys. 01:03:11.051 --> 01:03:13.051 We want to make the show you want to listen to. 01:03:14.251 --> 01:03:18.751 Well, Odyssey Westra sent in a live boost. That's actually a live road ducks. 01:03:20.091 --> 01:03:24.431 Live tracking for me is super important for my job. I use it to keep track of 01:03:24.431 --> 01:03:29.271 when and where I've been and track my miles for my job. Oh, that's actually brilliant. 01:03:29.871 --> 01:03:34.331 Plus, it helps with billing for multi-day projects. So self-hosting this, 01:03:34.351 --> 01:03:39.171 he means Devarich, will be an important step in de-googling myself. 01:03:39.551 --> 01:03:41.331 Love y'all and live meep. 01:03:41.691 --> 01:03:47.891 Yes. Nice. Honestly, that's so cool to hear. I hadn't even thought about it for tax accounting. 01:03:48.091 --> 01:03:48.671 That's brilliant. 01:03:49.451 --> 01:03:53.531 That is so brilliant. and you know it does have the ability to go in there and 01:03:53.531 --> 01:03:56.811 mark trips and so you could go in and say this was a work trip you. 01:03:56.811 --> 01:03:58.851 Might want the high fidelity mode for that part. 01:03:58.851 --> 01:04:04.271 Oh Wes I always have the high fidelity mode on I always do I'm. 01:04:04.271 --> 01:04:07.611 Gonna add a feature request for fuel station integration. 01:04:07.611 --> 01:04:12.411 Oh that would be amazing how would you do that I guess you could look up fuel 01:04:12.411 --> 01:04:16.811 stations yeah some way somebody could somebody could figure that out right there's. 01:04:16.811 --> 01:04:18.211 A whole ecosystem here I think. 01:04:18.951 --> 01:04:23.151 All right. Well, GC boosted him with 7,777 sats. 01:04:27.031 --> 01:04:30.591 He's coming in with a Grafonicon 2025 report. 01:04:30.971 --> 01:04:35.091 Oh, my God. Reading my mind. Some value for value right here. 01:04:36.651 --> 01:04:41.311 I received the Golden Grot Award for Best Professional Dashboard and presented 01:04:41.311 --> 01:04:45.291 my use case on an industrial system monitoring of a wastewater treatment facility. 01:04:46.271 --> 01:04:47.631 I would like to see this. 01:04:47.631 --> 01:04:48.311 That's amazing. 01:04:48.911 --> 01:04:52.311 Is there a video of this? Approximately 2,000 metrics at one second resolution. 01:04:52.571 --> 01:04:53.591 Yeah, definitely want to see this. 01:04:53.811 --> 01:04:57.051 Definitely want to see this. Great networking opportunity for data nerds. 01:04:57.211 --> 01:04:59.111 I also plugged the show a ton. 01:04:59.211 --> 01:04:59.891 Oh, you. 01:05:00.211 --> 01:05:00.971 Oh, wow. 01:05:03.564 --> 01:05:06.804 A NixOS sticker on my laptop brought out the NixOS lovers as well. 01:05:06.804 --> 01:05:10.904 I met someone who uses Proxmox with a NixOS LXC containers on board. 01:05:11.824 --> 01:05:14.844 Talescale was a sponsor. Unfortunately, I had to leave before Talescale community 01:05:14.844 --> 01:05:18.124 events started where they had some local celebrity named Wes. 01:05:18.484 --> 01:05:22.784 Oh, sorry not to have you there. But GC, thanks for the report. 01:05:23.084 --> 01:05:26.444 And are you local? Were you just here for the conference? 01:05:26.804 --> 01:05:27.044 Yeah. 01:05:27.244 --> 01:05:28.924 There's several things we should follow up on. 01:05:29.064 --> 01:05:34.084 And this is something I extremely appreciate. If you attend a tech event, 01:05:34.464 --> 01:05:38.484 an industry event, especially if it's adjacent to the show, please do send these reports in. 01:05:38.744 --> 01:05:41.744 It's so great just to keep in these, not only for our radar, 01:05:41.744 --> 01:05:44.744 so we kind of know what these events are going on, but so the other folks listening 01:05:44.744 --> 01:05:48.044 get an idea of what's going on out there too and what's actually worth attending. 01:05:49.044 --> 01:05:50.204 Man, thank you, everybody. 01:05:50.504 --> 01:05:56.164 I do have a final question here for GC. You mentioned 2,000 metrics, one second resolution. 01:05:56.724 --> 01:06:00.224 Are you running this off a little laptop in a bus? Is that what you're using 01:06:00.224 --> 01:06:01.744 or some kind of industrial PC? 01:06:04.604 --> 01:06:08.184 All right, thank you everybody who supported the show, either our members or 01:06:08.184 --> 01:06:10.004 by supporting each individual production. 01:06:10.324 --> 01:06:17.924 Those of you who stream sats, we had 28 of you, and we stacked 40,555 sats. Not too bad. 01:06:18.144 --> 01:06:21.644 Thank you everybody who stream sats as you listen. We see you, and we appreciate you. 01:06:21.764 --> 01:06:25.804 When you combine that with those of you who boosted, we had a very humble but 01:06:25.804 --> 01:06:33.164 yet very appreciated 189,657 sats. It's not our biggest episode ever. 01:06:33.424 --> 01:06:34.944 Maybe people don't like Home Assistant. 01:06:35.664 --> 01:06:38.204 I don't know what's going on there. Or maybe people are having problems boosting. 01:06:38.364 --> 01:06:39.744 Now you're just trolling. 01:06:40.104 --> 01:06:42.744 Maybe. But we do appreciate everyone who supports each production, 01:06:43.264 --> 01:06:44.984 either through the free Value to Value 01:06:44.984 --> 01:06:48.404 Network or through a membership at linuxunplugged.com slash membership. 01:06:48.964 --> 01:06:51.744 You're the greatest, and we appreciate you. 01:06:59.815 --> 01:07:05.255 All right, we have two picks this week, and one of them was cooked up by our very own Wes Payne. 01:07:05.495 --> 01:07:08.975 Yeah, it's sneaky. You know, you're kind of one of the users I have in mind 01:07:08.975 --> 01:07:11.495 for this, actually. So it's a little gift to you, maybe. 01:07:11.715 --> 01:07:12.015 All right. 01:07:13.175 --> 01:07:18.035 Well, we all know how great the Docker tail scale sidecar pattern is, 01:07:18.095 --> 01:07:19.835 right? So you're running something in Docker. 01:07:20.055 --> 01:07:22.855 You want it to be exposed to your whole gosh darn tail net. 01:07:23.375 --> 01:07:27.355 So you do the sidecar. So in the same network namespace, you've got your application 01:07:27.355 --> 01:07:30.395 running. maybe it's Dwarich, maybe it's something else. 01:07:30.595 --> 01:07:35.015 And then a tail scale runs there too. And so to that app, it gets access to 01:07:35.015 --> 01:07:37.475 the tail net with its very own tail net name. 01:07:37.655 --> 01:07:38.095 And IP. 01:07:38.335 --> 01:07:38.855 And IP. 01:07:39.055 --> 01:07:44.455 Which is really handy for applications like VS Code. So if I just go to code.whatevermydomain.com 01:07:44.455 --> 01:07:49.215 is, I'm actually just accessing a Docker container that is just right there 01:07:49.215 --> 01:07:52.995 on that IP with that just served up directly from the Docker container. 01:07:53.055 --> 01:07:55.735 I'm not going through Nginx. I'm not going through reverse proxy at all. 01:07:55.735 --> 01:07:59.755 And it's nice in the sense that okay maybe you still want tail scale on your 01:07:59.755 --> 01:08:03.995 host for the host to access and other things but it decouples those so even 01:08:03.995 --> 01:08:05.595 if you decide later to move, 01:08:06.155 --> 01:08:10.215 that application stack to a different host nothing else on your tail that has 01:08:10.215 --> 01:08:11.775 to care because they never knew where it was in the first place. 01:08:11.775 --> 01:08:14.875 And when the application starts up it's the same IP the same name all that stuff. 01:08:14.875 --> 01:08:15.595 Even on. 01:08:15.595 --> 01:08:16.135 A different host. 01:08:16.135 --> 01:08:20.195 Yep so that's great but as you probably know from listening to the show we're 01:08:20.195 --> 01:08:21.795 all running a bunch of stuff with Nix OS now, 01:08:22.675 --> 01:08:25.395 and there is no built in automatic sort of 01:08:25.395 --> 01:08:28.295 do the same easy sidecar system because one of the advantages 01:08:28.295 --> 01:08:31.075 of NixOS depending on what you're doing is you don't 01:08:31.075 --> 01:08:33.955 have to isolate everything to run all 01:08:33.955 --> 01:08:36.735 these things at the same time so by default they're not totally off in their 01:08:36.735 --> 01:08:42.595 own world like you get by default with Docker so I am working on a NixOS module 01:08:42.595 --> 01:08:48.615 to just wrap systemd services and NixOS services basically so that they run 01:08:48.615 --> 01:08:51.675 in their own network namespace with their own tail scale just like happens with Docker. 01:08:51.675 --> 01:08:55.675 So without a container but you're still taking advantage of network namespaces. 01:08:55.675 --> 01:08:59.715 It's basically me sort of uh re-implementing a 01:08:59.715 --> 01:09:02.775 bunch of the stuff that docker compose does with networking so there's a bridge 01:09:02.775 --> 01:09:07.375 on the host and then we use virtual ethernet pairs into namespaces per service 01:09:07.375 --> 01:09:12.055 and a tiny little dhcp server if i'm honest to tie it all together and then 01:09:12.055 --> 01:09:18.355 yeah so then they're able to get a natted firewalled outbound connection and then tailscale that. 01:09:18.355 --> 01:09:20.655 Is really slick and to be totally 100 transparent, 01:09:21.768 --> 01:09:24.748 We don't get paid for any of this. In fact, we're giving the milk away for free 01:09:24.748 --> 01:09:28.808 right now. The only thing Tailscale pays for is the spot at the top. We just really use it. 01:09:29.188 --> 01:09:32.648 And this makes it possible to essentially have every application you want to 01:09:32.648 --> 01:09:37.128 run via Nix get its own Tailnet IP and name and all of that. 01:09:37.308 --> 01:09:40.768 And there's initial support for doing Netbird as well. 01:09:40.868 --> 01:09:43.088 In theory, you should be able to do this stuff. I haven't tried Nebula or anything, 01:09:43.228 --> 01:09:45.668 but in theory, other... I called it Mesh sidecar because in theory, 01:09:45.788 --> 01:09:47.288 other services should work just fine. 01:09:47.288 --> 01:09:49.528 Am I right? The magic is really the network namespaces. 01:09:49.628 --> 01:09:52.248 That's a lot of the whole setup and making it work and then getting the right 01:09:52.248 --> 01:09:56.208 wrapping and modifying of the systemd service to make sure that it like joins 01:09:56.208 --> 01:10:00.228 the right network namespace and the namespaces get set up and all that kind of bookkeeping stuff. 01:10:00.428 --> 01:10:03.728 And then the actual, yeah, the actual mess stuff, other people are doing much better. 01:10:03.948 --> 01:10:04.528 Nice work. 01:10:04.928 --> 01:10:09.928 So also, maybe don't use it just yet. I already want, I made the initial interface 01:10:09.928 --> 01:10:13.088 really easy. So you just give it a list of services you want to wrap, 01:10:13.288 --> 01:10:16.428 which works great as long as you're not trying to run like multiples of those 01:10:16.428 --> 01:10:17.848 where you might want to have different names. 01:10:18.028 --> 01:10:21.148 You know what I mean? Like it works great if you're just running one grafana 01:10:21.148 --> 01:10:24.708 instance across your tail net but if you start to have multiple or. 01:10:24.708 --> 01:10:25.548 Plex or jellyfin. 01:10:25.548 --> 01:10:30.908 Right um because it just right now it uses the nix os module interface name 01:10:30.908 --> 01:10:33.828 as well as the system those are all assumed to be identical so i want to add 01:10:33.828 --> 01:10:35.128 some configurability so you can 01:10:35.568 --> 01:10:39.148 change like which exact maybe the nix os and the system d name aren't exact 01:10:39.148 --> 01:10:42.508 matches or you want to have the name on your tail net be slightly different 01:10:42.508 --> 01:10:45.628 oh sure so i'm going to modify the interface a little bit so there's already 01:10:45.628 --> 01:10:46.608 going to be one breaking change. 01:10:46.608 --> 01:10:49.808 I'll tell you the immediate use case if it hasn't quite clicked yet is jellyfin 01:10:49.808 --> 01:10:52.508 you know that's one area where i think 01:10:52.508 --> 01:10:55.548 jellyfin doesn't quite stack up to plex and that is sharing 01:10:55.548 --> 01:10:59.528 you know it is so easy on plex to share with your buddies and have multiple 01:10:59.528 --> 01:11:03.008 friends and multiple servers and jellyfin doesn't necessarily have that inherently 01:11:03.008 --> 01:11:07.968 built in but you can solve that if all of your buddies are on a tail net and 01:11:07.968 --> 01:11:13.388 you could because this is application specific this one application could be like on a dedicated, 01:11:14.028 --> 01:11:15.588 shared tail net with your friends. 01:11:15.868 --> 01:11:17.428 Yeah, you shared just this node or whatever. 01:11:17.648 --> 01:11:19.148 Yeah, and you can all get to your Jellyfin servers. 01:11:19.388 --> 01:11:21.168 Yeah, it doesn't matter what else you're hosting on that same box. 01:11:21.931 --> 01:11:24.811 So that's where it gets really cool, just to kind of put it practically down. 01:11:25.251 --> 01:11:29.231 I noticed this is licensed MIT. Can you say anything about that? 01:11:29.311 --> 01:11:30.631 Why did you chose MIT specifically? 01:11:31.171 --> 01:11:36.311 It's kind of my default license, just because it's really short and sweet. 01:11:36.551 --> 01:11:41.191 And I mean, there are probably projects I do want to license with more copy left style licenses. 01:11:41.191 --> 01:11:46.931 But for a lot of stuff on the programming side, library things tend to be licensed 01:11:46.931 --> 01:11:52.071 more on the MIT or BSD or Apache or similar spectrum. 01:11:52.271 --> 01:11:57.371 So I don't mind the MIT, and I've built that into my little make-a-new-get repo script. 01:11:58.351 --> 01:12:03.191 I have a second pick here. This one is also a little niche but useful if this 01:12:03.191 --> 01:12:04.771 is something you've been looking for. 01:12:04.911 --> 01:12:08.731 It's called Element.fm, and I was just recently made familiar with it. 01:12:08.731 --> 01:12:12.111 element.fm and it is a podcasting 2.0 01:12:12.111 --> 01:12:15.071 open source hosting platform it's licensed under the 01:12:15.071 --> 01:12:18.431 gpl3 they offer unlimited episodes they 01:12:18.431 --> 01:12:22.211 have ai automated generation of certain things you might like you know show 01:12:22.211 --> 01:12:25.251 notes whatever you might want to have it generate they supposedly i haven't 01:12:25.251 --> 01:12:28.631 seen these yet have advanced analytics but the big thing here for me is the 01:12:28.631 --> 01:12:33.411 podcasting 2.0 transcriptions chapters value for value all built into the hosting 01:12:33.411 --> 01:12:36.771 platform and they're launching with an API. 01:12:37.171 --> 01:12:40.071 So they have an API that people can use, which we really love. 01:12:40.271 --> 01:12:43.911 It's also self-hostable if you want to go that route. So if you're looking to 01:12:43.911 --> 01:12:48.891 produce a modern podcast that supports things like live tags and the cloud chapters 01:12:49.291 --> 01:12:52.411 and, of course, transcriptions, which I think are super valuable to have these 01:12:52.411 --> 01:12:55.711 days and going to make it much more relevant in a world of LLMs and, 01:12:55.771 --> 01:12:56.951 of course, value for value, too. 01:12:57.980 --> 01:13:02.560 Which supports the ecosystem of the podcast app creators, the hosting platforms, 01:13:02.660 --> 01:13:03.640 and the creators directly. 01:13:03.960 --> 01:13:08.080 And it's all just built in to element.fm. So they contacted me over the week 01:13:08.080 --> 01:13:10.980 and said, how come you've never looked at us? And I took a look and I was very impressed. 01:13:11.280 --> 01:13:14.800 So if you want something out of the box, it's going to just make you very competitive 01:13:14.800 --> 01:13:16.140 in the podcast space. Check it out. 01:13:16.460 --> 01:13:18.600 I think it looks really good. And it's GPL3. 01:13:19.000 --> 01:13:22.620 So the code is open source, which I feel really nice and solid about. 01:13:22.700 --> 01:13:25.420 When you're looking for something you want to be able to rely on for years as 01:13:25.420 --> 01:13:27.680 a podcaster, that gives you kind of that insurance policy. 01:13:27.980 --> 01:13:31.020 And you can self-host it if you want to. So check it out. We will have links 01:13:31.020 --> 01:13:32.260 to all of that in the show notes. 01:13:33.020 --> 01:13:33.420 Neat. 01:13:33.700 --> 01:13:38.660 Yeah. There we go. So this was a packed episode. We talked about the news items. 01:13:38.760 --> 01:13:40.320 We talked about the Big D Witch. 01:13:40.480 --> 01:13:41.860 All of that will be linked in 01:13:41.860 --> 01:13:46.660 the show notes. You can find those over at linuxunplugged.com slash 614. 01:13:47.040 --> 01:13:49.420 Now, we're not going to be live next Sunday. 01:13:50.000 --> 01:13:54.520 We will be on a trip to Boston because we are attending Red Hat Summit. 01:13:54.960 --> 01:13:58.840 So we'll probably have a prerecorded episode. We'll have something for our members as well. 01:13:59.260 --> 01:14:01.900 We're kind of flying by the seat of our pants this week, so we'll get all of 01:14:01.900 --> 01:14:03.980 the details figured out for you really soon. 01:14:04.180 --> 01:14:07.660 I want to remind you, I'm looking for feedback on my sound. We're looking for 01:14:07.660 --> 01:14:11.300 ideas for Brent's bus name, which is technically a van. 01:14:11.440 --> 01:14:13.700 So you could also, if van makes it more litter, that's fine. 01:14:13.980 --> 01:14:18.920 And then last but not least, please do check the show notes for the TUI challenge. 01:14:19.240 --> 01:14:22.720 We'd love your feedback while we're traveling. It's a great time collectively 01:14:22.720 --> 01:14:26.040 for the community to work on that. So when we get back, we can hopefully launch 01:14:26.040 --> 01:14:27.880 the TUI challenge, at least pretty close to when we get back. 01:14:28.040 --> 01:14:31.420 We'll have all of that at linuxunplugged.com slash 614. 01:14:33.000 --> 01:14:36.360 Now, we will have more for you. We'll have one more episode before we're actually 01:14:36.360 --> 01:14:38.800 at Red Hat Summit, and then we'll have all of the details. You know, 01:14:38.880 --> 01:14:41.740 we'll take the best bits, the things that you really care about, 01:14:41.840 --> 01:14:45.060 the stuff you want to know about, all of the signal from the noise from Red 01:14:45.060 --> 01:14:47.040 Hat Summit, and we'll have it in a future episode for you. 01:14:47.300 --> 01:14:50.240 So go subscribe. Links to everything, our Mumba Room, our Matrix, 01:14:50.400 --> 01:14:52.280 our RSS feed. It's all at a website. 01:14:52.640 --> 01:14:57.160 It uses HTML. it's incredible linuxunplugged.com you don't even have to type 01:14:57.160 --> 01:15:00.920 the https anymore can you believe it they took that out you don't even brother 01:15:00.920 --> 01:15:04.940 you don't even need the www www can you believe it i love the www you don't 01:15:04.940 --> 01:15:07.940 need it i'd say put it in there why not i think we set up a redirect so do it 01:15:07.940 --> 01:15:10.840 thanks so much for joining us see you next tuesday as in sunday.
Previous episode Next episode

Related episodes

Search

Search

Listen on

Apple Podcasts Spotify RSS feed

Tags

Partner Privacy