Chris: Hello, friends, and welcome back to your weekly Linux talk show. My name is Chris.
Wes: My name is Wes.
Brent: And my name is Brent.
Chris: Hello, gentlemen. Well, coming up on the show today, we'll show you and tell
Chris: you and test a self-hosted alternative to Google Maps location tracking.
Chris: It's a hotspot of where you've been and everywhere you go, and the three of
Chris: us have been trying it out.
Chris: Plus, we'll catch up on some news that we've missed while we're on the road,
Chris: and we'll share the details on an upcoming TUI challenge. And then we'll round
Chris: it all out with some great booths, some picks, and a lot more.
Chris: So before we go any further, let's say time-appropriate greetings to our virtual
Chris: lug. Hello, Mumble Room.
Mumble: Hello. Hey, Chris. Hello, Bunt.
Chris: Hello, everybody.
Wes: We got him excited today in there.
Chris: Nice to have you. If you want details, jupiterbroadcasting.com slash mumble.
Chris: You get to hang out and get the whole stream. Or, of course,
Chris: you can become a member. And you get the bootleg.
Chris: And a big good morning to our friends at Tailscale. tailscale.com slash
Chris: unplugged go there to get tailscale for free up to 100
Chris: devices and three users because that's the easiest way
Chris: to connect devices directly to each other applications services servers
Chris: your desktop a vm whatever it might be maybe it is just an application you're
Chris: running on your system and you want to put that directly on your tail net it's
Chris: modern networking that builds out a flat mesh network protected by a world that's
Chris: right so you get secure remote access to your systems that is really fast, intuitive,
Chris: programmable, and also easy to integrate with your company's ACLs and authentication infrastructure.
Chris: It's easy to deploy. It's easy to configure. It really is no fuss.
Chris: If you've got five machines, you can probably get it running in three minutes on all of them.
Chris: And the personal plan will always be free. So you can try it out,
Chris: get it on 100 devices, build out your home lab, and it's so great.
Chris: None of my personal data for my phone, my thinking anything goes
Chris: over the internet i have no inbound ports anymore and i
Chris: love it so much that not only am i a personal user but now jb uses it and it's
Chris: integral to our back-end infrastructure and thousands of other companies use
Chris: tailscale as well for individuals or businesses you get started and support
Chris: the show by going to tailscale.com slash unplugged that's tailscale.com slash
Chris: unplugged get it for free on 100 devices support the show.
Chris: Well, we've got to start by saying Happy Mother's Day to the moms out there.
Wes: Indeed, Happy Mother's Day.
Chris: Appreciate all of you and a special appreciation to all the ones in our lives.
Chris: It's nice that they let us sneak off on this important day and do a podcast.
Chris: So we appreciate that too.
Chris: Also, we have some details about our upcoming Terminal User Interface Challenge.
Wes: You've been hard at work over there.
Chris: Yeah, and I have a first public draft. And what we're going to do is get this
Chris: posted up on the Jupyter Broadcasting GitHub so you can take a look at it.
Chris: It is, on the high level, going to be a seven-day challenge with different points
Chris: awarded for what you get completed. There is a bonus round if you want to skip
Chris: one of the seven-day challenges and go past one of them. There's also some bonus points for creativity.
Chris: There's details on how you submit your information to the show to let us know how you did.
Chris: And the idea is we're trying to come up with a way at the end where you can
Chris: sort of tally up a total score.
Chris: So you can say, guys, I got an 85, or I got a 62, or I got a 100.
Wes: Something to compare.
Chris: Something we can compare at the end. And so all of that is sort of outlined
Chris: in what I've put together, but I think it could use a little finessing.
Chris: So we're all off to Red Hat Summit next week.
Chris: So we figured we'd put this out there, let people look at it for a couple of
Chris: weeks, make some suggestions on our GitHub, and then we'll put it together and
Chris: we'll actually launch the challenge officially after we've gotten some community
Chris: input to really kind of make this thing nice.
Wes: Now I'm feeling nervous because I think Brent's going to smoke us somehow and
Wes: there's going to be numbers to prove it.
Brent: I actually feel far more nervous than I think you feel, so we'll see how it goes.
Chris: See, I'm feeling pretty good because A.
Wes: You've been doing research.
Chris: I've been stacking 2E apps.
Brent: You've been pre-gaming.
Chris: I've been stacking 2E apps. B, I got that Knicks book from Olympia Mike,
Chris: and I think I'm going to make that a dedicated 2E machine.
Chris: Going all in. So the only thing that loads is the terminal.
Chris: 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.
Chris: So we'll have the link, hopefully in the show notes, when this episode publishes
Chris: at linuxunplugged.com slash 614.
Chris: We'd like you to take a look at the challenge rules in the outline and make
Chris: any suggestions for improvements, additions, removals, anything like that,
Chris: because it really is just a draft one.
Chris: And I think it's a good chance for everybody to have some input on there.
Chris: And while we're in the housekeeping section, I want to follow up on a topic from last week.
Chris: We're officially back from the van rescue trip.
Brent: We made it.
Chris: We made it. We're here. We're alive.
Wes: Welcome back, boys.
Chris: There was definitely some adventures, a couple of detours we didn't expect,
Chris: but to celebrate the fact that we actually made it, the van survived and we
Chris: survived, we're cracking open some ciders.
Chris: Yes. Cheers, gentlemen.
Brent: Cheers, gents.
Wes: To the bus.
Chris: To the bus.
Wes: And all those who help her along her way.
Chris: Which is, the engines run like a champ, but we continue to be working out systems.
Chris: Electrical is one of the major systems right now. Generator is another major system.
Brent: The frustrating thing is the systems I thought were cool. Somehow,
Brent: now that we're in Washington, are very not cool.
Chris: And the systems we thought might be a problem.
Brent: Yeah, totally fine.
Chris: Probably going to be fine.
Wes: Do you think if you were to drive back to California, you'd swap back?
Brent: Oh, I don't know if I want to drive back to California. Sorry, Jeff.
Chris: But it's good to be back. It was really a hell of an adventure.
Chris: You know, roughly, you said 1,500 miles, but I thought it was roughly 1,800 miles.
Brent: You know um the maps tend to always want to take the i5 and we tend to not ever want to take the.
Chris: I5 we took very much the long route i.
Brent: Think my estimates were quite off.
Chris: I think it was 1800 miles based on the app i used to track us yeah.
Brent: I i reset the odometer but i don't know it didn't give us the right reading.
Chris: Uh yeah the odometer didn't seem to be reading it was on zero right yeah um
Chris: we did have one cop out of 18 pull us over we'll have this story about that um,
Chris: and more details in the launch we covered we talked about some of this last
Chris: week and then And of course, we had to make the drive since we were in episode 613.
Chris: That's when we actually had to make the drive all the way back to Washington
Chris: here to the studio. So we're going to cover all the details in the launch 21,
Chris: which will be out on May 14th, weeklylaunch.rocks.
Chris: And yeah, there's a lot. There's a lot more projects to continue to.
Chris: We may have fried the home assistant machine already.
Brent: It's not good. It's not good.
Chris: We don't know for sure. We got to do further testing. Like everything,
Chris: you got to test a few times.
Brent: I think Jeff has a spare one under his bed.
Chris: Yeah, PJ, we might need that spare.
Brent: Thanks.
Chris: I don't know if he does have it. Yeah, we were testing the electrical system.
Wes: Although I think, wasn't PJ saying maybe a Knicks book would be a good fit?
Brent: We got options.
Chris: We got, yeah. We have disagreements.
Wes: I see.
Chris: I'm not a big fan of the home assistant.
Wes: I'm poking my head somewhere here.
Chris: I'm not a fan of home assistant's laptop. I get the built-in battery and all
Chris: of that, but yeah. All right, but anyways.
Chris: Yeah, so we may have fried the machine. We'll see how. We'll see how that goes.
Brent: He claims they're bulletproof, but I don't know. Leave it to me.
Chris: Yeah, give Brent a week.
Brent: Actually, it was only a couple days.
Chris: This is literally an industrial piece of equipment that's meant to be embedded
Chris: in a very rough terrain, hard, core, hot.
Wes: Here's what happens. You see the superstructure of the van. It concentrates the bug field.
Chris: Yeah, the metal walls.
Wes: Yeah, exactly.
Brent: Oh, it sure feels that way.
Chris: So it's like a Brent-a-day cage is what you're saying.
Wes: That's absolutely right.
Chris: Oh, God. I hadn't thought about that.
Wes: Yeah, don't put your sensitive production systems anywhere near there.
Chris: Like, what happens to me? Is there, like, a cross-contamination? Do I get affected?
Wes: Yeah, we should probably hang out for a bit. I'll try to decontaminate it.
Chris: Counterbalance, thank you, Wes. Yeah. Yeah, you better watch out,
Chris: too. Yeah, you better watch out.
Chris: But we made it. We're back. Projects will continue. We may have fried the Home Assistant box.
Chris: We'll have details once we get that tested. And, of course, check out the Launch
Chris: 21 when it comes out on May 14th. Weekly launch.rocks.
Chris: We'll have all of that, hopefully, figured out. I don't know.
Chris: But it's been so much fun.
Chris: That's the key takeaway. We really enjoyed it. I wish I could do that once a
Chris: quarter. You know, go rescue something like that.
Brent: We could find a way. You know, we can crowdsource a bunch of crazy projects
Brent: for us to go find somewhere in the continent. Even off continent.
Chris: Anybody else have a semi-functional van need rescued?
Brent: Chris has been looking along the way.
Wes: What's your rate?
Chris: I have never loved another man's vehicle as much as I love this van.
Chris: Like, you know, my blood, sweat, and tears have gone into this too.
Chris: And then, you know, you do that driving along the coast.
Wes: Are you the, is there like a godfather sort of concept?
Chris: I'll take that.
Wes: Yeah, I'll take that. I'm not, I can't give that away. That's his to distribute.
Chris: I mean, I would take it. I would be honest. You asked me a question.
Chris: What was it? Do you remember? No? Okay. I don't remember either,
Chris: but I'm sure it was really important.
Chris: I have a question. One last thing before we get out of housekeeping.
Chris: How do I sound today? So I'm using the headset in studio just to get more practice with it.
Chris: I want to know, do you think this could be a forever mic? Does it sound okay
Chris: compared to the boys? Boost him, let me know how you think it sounds. Be honest.
Chris: Give me the harsh feedback or give me the good feedback. Just trying to,
Chris: you know, learn how to use these fancy new headsets that y'all helped us get,
Chris: which we appreciate very much.
Chris: So the Gnome Foundation, or I guess Gnome.
Brent: Gnome for some.
Chris: Has a new executive director. Steven Diobald, I believe is maybe not how you
Chris: say it, but he's been appointed as a new executive director of the Gnome Foundation.
Chris: There was an intern director who sat in for Holly Millen, who stepped down last year.
Chris: Now, here's what stood out to me, Brent. I thought you'd like this,
Chris: is he's a Canadian free software advocate.
Brent: Oh.
Chris: Yeah, he's Canadian. He's been a Gnome user since 2002.
Chris: and he does have some experience in the IT industry and also in the fundraising part of the industry.
Brent: It's actually quite a nice mix, I would imagine.
Chris: It seems like it very well could be.
Wes: You know, here's some cred from the intro bio over on blogs.gnome.org.
Wes: I built a graphical mud before the term MMORPG was coined. So, yeah, right? Hey.
Wes: That's probably a good sign in terms of general nerdery.
Chris: I want to play the Star Trek mud. I've seen it. I think I've never played it, though.
Chris: Yeah, so there's a welcome post that we will link in the show notes.
Chris: And what stood out to me is this is somebody who's taking the reins of GNOME
Chris: at GNOME, GNOME, at a time where they're having some financial troubles. And...
Chris: It feels like it's really a shame that probably the most widely deployed free
Chris: software desktop, even our most successful free software desktop project,
Chris: is having troubles raising funds.
Chris: And I wish maybe there's a way to leverage that position. And maybe this new
Chris: director has an opportunity to improve that situation.
Chris: Because there's a lot of big corporations that are getting a lot of benefit from the GNOME desktop.
Chris: And I know they contribute developer time. And I know there's ways that they
Chris: contribute now. But it's just such a shame that such a user-forward desktop
Chris: for Linux is struggling.
Chris: And I hope that Steven has an opportunity to improve that situation. Not an easy job.
Chris: I don't know who would want that position.
Wes: I'm hopeful. I mean, it does seem like, you know, he's got a long history with
Wes: open source and the tools and communities around it.
Wes: So if anyone can, this seems like a good candidate. So here's hoping for the best.
Chris: NixOS now has a dedicated hardware team. The steering committee is launching
Chris: a new hardware team to own the NixOS hardware repo, drive hardware enablement,
Chris: and expand partnerships.
Brent: Ooh.
Chris: Oh, I would totally be interested in the Nix First laptop.
Brent: That's fascinating.
Chris: So they want to streamline device enablement. So it makes it easier to,
Chris: I guess, say this works with NixOS.
Wes: I think that's a great idea. And I mean, it is one of the easiest first ways
Wes: you can demonstrate that like, hey,
Wes: the community already figured this out and documented it as code and you just
Wes: need to add two lines somewhere and now you have the approved way to make sure
Wes: your hardware is optimized.
Chris: We've seen some self-organizing around that, but part of this is to clarify
Chris: ownership and also to sort of ensure that those things are done consistently
Chris: and not as ad hoc, which I'm not slamming.
Chris: I'm very grateful for, but, you know, that's part of what they want to do is
Chris: make that kind of a consistent experience too.
Wes: Right. And that's exactly the kind of next stage of formalities,
Wes: maybe not the right word, process, structure, just organization in terms of
Wes: having a foundation and a sort of longer term outlook on supporting the project
Wes: for real world use cases. And that's nice.
Brent: If it does go to the next stage, I think, but I'm not sure. I'm curious to hear what you boys think.
Brent: I think I would like to see the NixOS hardware project still be used as the
Brent: central sort of hardware management.
Brent: So if we see a bunch of bigger companies committing to that repo,
Brent: that'd be really nice to see. But I don't know if you think that's best practice.
Chris: Hmm i was picturing i was picturing uh sort of like a maintainer role where
Chris: you'd still have community contributing their fixes their patches their configs
Chris: but then you would have sort of,
Chris: maintainers that are taking that in and making sure that it is a certain standard
Chris: format and things like that but you know if i was just also thinking if i could
Chris: be in charge of hardware for you know, a year at NixOS,
Chris: quote unquote, at the NixOS Corporation, deploying the NixOS software.
Chris: So this is getting pretty out there.
Brent: Um...
Chris: But I do wonder, would it be a big impact to say, work with a ThinkPad or a
Chris: System76 and try to focus on the DevOps engineer software developer market that
Chris: is particularly trying to deploy software?
Chris: I'd focus in on a couple of scenarios that I felt like I could really solve.
Chris: Or maybe, you know, is there room for a company that does this,
Chris: and they work with a company like Phlox to produce an out-of-the-box,
Chris: really friendly developer experience based on Phlox's technology and NixOS to manage the OS.
Wes: Ooh, here's your, like, super streamlined, boots-to-Phlox, ready-to-go dev setup.
Chris: Yeah.
Wes: Something like that. Hmm.
Chris: Chromebook, but more powerful, not as restricted.
Wes: Meant for the super user, or at least the professional user.
Chris: Good hardware, good battery life, decent build-out, reliability, good keyboard.
Chris: I mean, I know this is, but there's a market for this. You know,
Chris: this is what the Sputnik thing was all about.
Chris: And I don't know if they've drifted from that as much or not.
Chris: I think, you know, they're just kind of constrained to what the designs are.
Chris: And there's so much potential here. And right now, my options are,
Chris: if I buy a laptop with Fedora or Pop!
Chris: OS, I know I've got a good chance that's going to run Nix OS just fine.
Chris: But I would totally be more inclined to just buy something with NixOS preloaded
Chris: just because I would assume even when I reload Nix myself, it's going to work great.
Wes: Yeah, you know the hardware stuff's just going to detect or you can import it
Wes: and it'll have your model ready to go.
Wes: While we're on the subject, just a very quick micro selfish shout out.
Wes: I did see some folks attempting to organize or seek interest for a Seattle NixOS
Wes: users meetup group over on the Discord. course so if you happen to be in that
Wes: area and are interested maybe go chime in.
Chris: Oh something like that got rolling i think we'd pop i think we would exactly
Chris: yeah that'd be pretty great,
Chris: well it looks like sudo rs is in 2510 it's going to be default ubuntu will adopt
Chris: sudo rs a rust-based memory safe re-implementation of the traditional sudo application This,
Chris: you know, I'm surprised to see pushback.
Chris: I mean, good code is good code, right? And these tools are tools.
Chris: And if the functionality is good and it does what they need and they think it's
Chris: going to make it easier for them to maintain LTSs and whatnot,
Chris: I have a hard time finding the bad in this.
Chris: But it has definitely seen some pushback, more than I expected,
Chris: especially after we had our chat.
Brent: Can you give a sense of what the pushback is? Just like people who are traditionalists?
Chris: Yeah, it's sort of the two-track. You get a lot. It already works.
Chris: compatibility with older systems, you get that argument. And then you also get
Chris: the sort of like, well, it's Rust, and so there's a pushback because people
Chris: don't want to just arbitrarily replace everything with Rust just because it's Rust.
Chris: There's also a whole social aspect to Rust that people want to push back on
Chris: and say, well, you could use something like Go instead.
Chris: So there's just these different, there's three or four different camps that
Chris: kind of come together to push back on an announcement like this.
Chris: But I have to side with Canonical on this one.
Chris: And I think some of these things do need to be pushed forward.
Chris: And when we're talking about maintaining these, what are essentially forks of
Chris: Linux for a decade plus, which is honestly, in my personal opinion, irresponsible.
Chris: And these companies should not be doing this and they should be forcing their
Chris: customers to upgrade, which would enforce the vendors to upgrade.
Chris: But since they won't, instead, they'll just take a check and they'll pay developers
Chris: to toil away for a decade to port old patches and fixes to these ancient releases
Chris: of Linux and anything you can do to make that easier to support,
Chris: to make that more maintainable and to make that safer and secure,
Chris: not today, but 10 years from now, seems like a pretty good action to take.
Chris: And when you consider how long...
Chris: Some of these customers will take before they even get this stuff in the next LTS.
Chris: We're going to still see another five to ten years before most of the companies
Chris: that are running these things on these long-term systems even adopt this stuff.
Wes: There's also an aspect I think that's easy to not necessarily appreciate,
Wes: which I did not until we talked with John Seeger, VP Engineering for Ubuntu,
Wes: who's had some great blog posts on this effort and was on episode 607,
Wes: if you want more of the deeper rationale.
Wes: now um but you know they know here in
Wes: this discourse post that the pseudo rs team
Wes: is collaborating with todd miller the maintainer of
Wes: the original pseudo for over 30 years yeah so it's not
Wes: i guess in some considerations really a fork in
Wes: the road i mean it is a different project but you know
Wes: it it's attempting to keep in line be
Wes: pretty much a drop in replacement they've also contributed changes
Wes: and enhancements to pseudo right so like they're both still healthy
Wes: and going onwards for the most part
Wes: if you're just doing you know the basic stuff that we
Wes: all do or regular bog standard
Wes: um pseudo configuration it should be a drop replacement
Wes: but it is probably worth noting that it's
Wes: not a quote-unquote blind re-implementation the
Wes: developers are taking a less is more approach meaning some of the features that
Wes: if they are only serve quite niche audiences or maybe are just like things you
Wes: wouldn't do today from a security perspective if you were going to develop the
Wes: software now some of those features are gone so.
Wes: If the thing you relied on for your workflow is gone that's reasonable to be
Wes: concerned but you know if you can drop it in and you don't notice win.
Chris: So, BcacheFS has had some new patches introduced aimed at significantly improving
Chris: snapshot deletion performance.
Chris: These enhancements are part of an ongoing effort to refine the file system's
Chris: capabilities, but there is an actual but with this particular patch.
Chris: The implementation necessitates an update to the incompatible on-disk format,
Chris: and then must be explicitly enabled by users to make that happen.
Chris: Obviously, for safety reasons, I don't want to surprise you.
Chris: And the new ONDIS format is not backwards compatible, meaning once you enable
Chris: it, you're not going to be able to revert.
Chris: Now, of course, BcacheFS is like ultimate beta, should not be using it.
Chris: It's not even released as stable in the kernel.
Chris: We're not actually suggesting you should have it in production or on your system.
Chris: So, of course, Wes is using it.
Wes: That's right, on several of my systems, actually.
Chris: So does this impact you at all?
Wes: No i mean i'm don't have a crazy ton of snapshots to delete so i don't have
Wes: any pressure to opt in necessarily for the in the first place um what.
Chris: As a user of bcfs what um is the impact to you when there's an on disk format change.
Wes: Uh well so there are some that are
Wes: like you know the bigger ones uh that are
Wes: slowing down and maybe stable um are ones
Wes: that is sort of like you know pretty much everyone's doing so like you upgrade
Wes: to the new kernel and it's like or you do some new operation and it needs to
Wes: upgrade the file system then there are incompatible features right so there's
Wes: like the actual on just format that new kernel puts up and like you have to
Wes: make some change to all of the data structures and.
Chris: So does it just run through a process at the next boot is it just something
Chris: that's sort of like on the screen for a few minutes while your system boots for the first time.
Wes: Yeah or i mean there's probably various ways to do you can probably trigger
Wes: it from like a user space tool as well i don't know all the details but that
Wes: has happened right where You've had to do these upgrades.
Wes: This is not that, right? This is not just like automatically happen.
Wes: This is not necessary to continue using the file system on a new version,
Wes: except if you opt in and then you can't go backwards.
Wes: So this is an incompatible features.
Wes: So if you do opt in, it does change the disk format, but it's not like a feature
Wes: that is expected of all BcacheFS file systems.
Wes: As Kent was trying to clarify in some of the Pharonix comments,
Wes: this is pretty common that file systems do in terms of like,
Wes: oh, if you want to opt into this optimization, we need to make a change to the
Wes: structure of your disk and maybe that'll be something that will be default in future file systems,
Wes: that get created or maybe sometimes they remain as sort of niche versions that
Wes: doesn't make sense for everyone to enable but does depending on your workload.
Chris: You always know I love ButterFS. So this is said with no judgment I mean I got ButterFS everywhere,
Chris: But it feels like BcacheFS is working this stuff out in this alpha-beta stage
Chris: before it's stable in the kernel, before it's been unleashed to users.
Chris: The ButterFS kind of was working out in the public once we already had ButterFS
Chris: on our file systems. And we'd already formatted our disk, right?
Chris: It felt like ButterFS was making these iterations years into already being out in production.
Chris: Again, no shame to that game. I love ButterFS. It's in a great place right now.
Chris: but this particular type of stuff this big stuff if this is the time to do it
Chris: is before we all have it really seriously deployed in production unlike wes well.
Brent: And as we know with butterfs like some people got burnt in the early days and
Brent: it's really hard to come back to a file system once you've been burnt that hard.
Chris: Yeah i think ken's aware of that too based on our chat with him i got the sense
Chris: he is very much aware of trying to avoid that.
Wes: Yeah definitely and as you say right i mean it's useful between being able to
Wes: learn from the development of butterfs and zfs and other modern file systems.
Wes: And, right, there are some users out there with petabyte file systems and who
Wes: are making a bunch of snapshots. So, hopefully, and this is a good reason to
Wes: run it on systems where you can.
Wes: You know, Kent's pretty active. There's ways to communicate and share bug reports or test new features.
Wes: And if we work them out now, hopefully it'll be a reliable file system for decades to come.
Chris: Onepassword.com slash unplugged. That's the number one password,
Chris: unplugged, all lowercase.
Chris: Imagine your company's securities like the quad of a college campus.
Chris: You have your nice brick pass between the buildings. Those are the company-owned
Chris: devices you could sort of think of as the stuff IT is approved of,
Chris: the employee identities that have been managed, the things and accounts you know about.
Chris: And then you have those pass that people actually use.
Chris: The shortcuts that get worn through the grass, that's the actual straightest
Chris: line from point A to point B.
Chris: Those are the unmanaged devices, shadow IT apps, and non-employee identities like contractors.
Chris: Most security tools, they only work on the happy brick pass.
Chris: But, and I know you know this, a lot of security problems take place on those shortcuts.
Chris: That's where extended access management comes in from 1Password.
Chris: It's the first security solution that brings all these unmanaged devices,
Chris: apps, and identities under your control.
Chris: So you ensure that every user is strong, every credential is protected,
Chris: every device is known and healthy, and every app is visible.
Chris: That's what 1Password Extended Access Management solves. It's problems that
Chris: traditional IAMs and MDMs just don't touch.
Chris: It's security for the way we actually work today, and it's generally available
Chris: for companies with Okta or Microsoft Entra, and it's in beta for Google Workspace
Chris: customers to go check it out.
Chris: You know 1Password changed the game when it came to password hygiene.
Chris: Now imagine taking your game all the way to the next level. Every identity,
Chris: every app, every device.
Chris: That's what 1Password does, and they back it up with great supports and regular
Chris: third-party audits as well.
Chris: Go secure every app, every device, and every identity, even the unmanaged ones.
Chris: Go to 1Password.com slash unplugged. That's all lowercase.
Chris: It's 1Password.com slash unplugged.
Brent: Well, Chris, you threw over the fence for us this mapping application,
Brent: and I have not used too many map tracking applications.
Brent: This is one of them that got our attention.
Brent: The name is a little, I'll give it a swing. Here we go. I think it's Dwarwich.
Chris: Yeah, I'm going to go with something like Dwarwich or something like that,
Chris: or maybe we'll just call it the witch. I'm not sure.
Chris: This is such a neat idea. And Google offers a similar location history service
Chris: where you can pull up your location history and it'll overlay it on Google Maps with some hotspots.
Chris: But of course, You're constantly sending all of your location information to Google.
Chris: Years ago, I had a similar thing that was tracking everything I did.
Chris: It was connected to the ODB2 port of my car, and it was called the automatic.
Wes: Oh, right.
Brent: Why the ODB2? That's crazy.
Chris: Well, the idea was it had a little cellular chip in it. And so as soon as your
Chris: car started, it would start tracking your travel.
Chris: And what you would get is a map with, and I use this thing for multiple years,
Chris: like my trip to New York for the Ubuntu Dev Summit and all over.
Chris: So I just had this massive map
Chris: of everywhere we had gone. So I got one for the RV. I got one for my car.
Chris: And then, of course, they went out of business because they couldn't make money
Chris: just selling my data, I guess.
Chris: But the functionality turned out to be really useful because you could go back
Chris: in time and be like, oh, yeah, this was the spot we really loved.
Chris: Or look how much time we spent here. And it wasn't something I initially found
Chris: valuable, but like two years later, I found extremely valuable.
Chris: And I've always wanted something like this. And we've experimented with live
Chris: trackers for our Linode on the Road Denver trip.
Wes: Oh, yeah.
Chris: And there's a lot of ways you can solve this. But this is a newer project that
Chris: is actively maintained that lets you visualize your location history,
Chris: track your movements, and analyze your travel patterns. and it gives you total
Chris: privacy and control and it can be completely self-hosted.
Chris: It is also GPL3.
Chris: And the idea is you get an interactive map with timelines and travel statistics
Chris: about everywhere you've been,
Chris: everything you've done, the speeds and timelines and stuff like that.
Chris: And it works by using multiple different apps or clients that are available for your mobile device.
Chris: And once your mobile device detects that you're really moving,
Chris: it's using the background location services. once the background location services
Chris: realize you're moving, it can start tracking and reporting to your own server
Chris: and giving you all of this data.
Chris: And so if you go on like a family road trip or you go on a work trip or you
Chris: want to go for a nice long drive and you want to come back and have a map of
Chris: the route you took and everywhere you stopped, this is perfect for that.
Chris: And of course, we've been on a lot of trips recently, so this has been on the front of our mind.
Chris: And Brent, you probably got the most time with this because you got it set up first.
Chris: And we went on a nice little scenic route with it.
Chris: And, um, I'm just, I don't know. I'm wondering if you're seeing the value in
Chris: something like this and what your thoughts were using it.
Brent: Well, like I mentioned, I haven't really explored this space for myself just
Brent: primarily because I didn't really have a use or maybe I just didn't have people
Brent: who cared where I went, but I actually have gotten really fascinated by the
Brent: whole, cause this does like heat maps as well of where you spend the most time.
Brent: And as we'll see later, it can also bring in other data from other sources,
Brent: which is really interesting.
Brent: I am surprised I got it working first, just, you know, noting that for you guys.
Wes: And you did, you've not, have you used the Google version or any of the other sort of proprietary?
Brent: No, I've been pretty, I have some allergies I'd like to mention.
Brent: And one of them is tracking by these large corporations.
Chris: Yeah.
Wes: I did for years. I think I've turned it off now.
Chris: Same. I did for years.
Wes: But I have turned it off. I mean, I did not like the tracking aspect and I don't
Wes: especially need anyone knowing all of that.
Wes: I mean, as a sort of virtual journal wannabe, it's pretty great for,
Wes: you know, remembering past trips, seeing where you were.
Chris: Well, I was thinking for Brent. He's technically on a trip right now.
Chris: And a year or two from now, you can look back at this and be like,
Chris: what did I do when I was in Washington? Where have I not been?
Brent: Oh, I like your thinking.
Chris: What route have I not taken yet?
Brent: Okay.
Chris: That kind of stuff. I think you would find that particularly interesting as
Chris: somebody who likes to explore and take new routes. you could actually have a
Chris: map, almost like a video game, of everywhere your character has been on the
Chris: map, and you can pick new quests now.
Chris: I mean, just that kind of stuff. Do you think this is something you would keep using?
Brent: I really think it is. And I didn't think that going into this.
Brent: So it's changed my perspective of, we unfold maps on the show here from time
Brent: to time, but it's changed, I don't know, my relationship to wanting to track
Brent: the history, especially using open formats that you can import and export elsewhere.
Brent: So this might be here to stay for me because I've done, I don't know,
Brent: how many trips in the last 10 years?
Brent: Like ridiculous all over the continent, Europe as well.
Brent: And yeah, actually, I would have liked to know where I've been.
Chris: Everywhere you've been, even the small places.
Brent: Yeah.
Wes: Okay. So you got it running first. So maybe you can tell us how you set it up.
Chris: Wes. Well, we asked Wes very nicely to take a look at this while we were working on the van.
Wes: I meant the client.
Brent: It's a quick message to Wes and poof, magic.
Wes: I'm not that self-serving.
Chris: That was amazing, though. If that was your angle, that was so good.
Chris: I was like, nicely done, sir. Savage moment.
Chris: Yeah, so actually, that is a good question, though. You and I have it running
Chris: very differently on our client devices.
Brent: We do. I decided to try to stay as open as possible using clients that are well-loved by the community.
Brent: So I decided to use OwnTracks, which has been around for a long time.
Brent: Now, Chris, you mentioned you were using it in the past for a bunch of tracking.
Brent: So I knew it had a good history.
Chris: We liked it, right? That's what we use for Linode on the road tracking. Indeed, yeah.
Brent: And OwnTracks, I think, is really flexible in that it can support a bunch of backends.
Brent: And this support is built right into Vavarach.
Brent: And so I thought I'm going to go this route, see how that works.
Chris: It's also, if you're somebody who likes log output, or you want to be able to
Chris: export your config and import it to another device, and you want to get the
Chris: debug details, OwnTrax is the client that will actually expose all of that to you.
Brent: Yeah, I will say it did feel a little heavy on the tech user when I was first
Brent: setting it up. That's fine for us.
Chris: Yeah. I mean, it starts, it assumes you're going to use MQTT.
Chris: You've got to put it into HTTP mode.
Chris: Did you have to import an SSL cert or were you just, are you just raw dog plain
Chris: text sending your location information?
Brent: Probably the second one.
Chris: Okay, good. Are you plain texting? You're using own tracks?
Wes: No, to our little self-hosted instance?
Chris: Yeah, our private self-hosted instance.
Wes: I did set up Let's Encrypt.
Chris: You did, but you're not using that on the client, are you?
Wes: I think I am.
Chris: Are you? Because it seems like it just defaults to HTTP.
Wes: Well, good question, actually, then. That would be a major issue.
Brent: Wes and I are currently frantically...
Chris: I mean, if we put this on our own private lands, we would be doing this over tail scale anyways.
Wes: It's true, yeah. Okay, the mode is called HTTP.
Chris: Okay, yeah.
Wes: But the URL I'm using, it has a cute little S.
Chris: It does have the S in it.
Wes: It can also do MDT, which is interesting.
Chris: Yeah, yeah, yeah, yeah. Yeah, that would probably be a yes. So you got the S too?
Brent: I got it.
Chris: All right, good. I was just curious because I did look at that.
Chris: That's not the way I set it up. Yeah, so I...
Wes: I did leave the other server we're running, which we'll get into the integration.
Wes: That one's totally unprotected though.
Chris: I will say, I think own tracks, if you're willing to go through the configuration
Chris: is the more pro route to go with this because you do get the config export.
Chris: You might get a little more granularity, but if you're on iOS or you want to
Chris: dedicate an iOS device for this, they, they actually make a dedicated app that is very simple.
Chris: You give it the URL of your server and your API key and that's it. And it just goes.
Chris: is really nice. It's really simple to set up and,
Chris: as accurate as iOS location can be.
Chris: So I did two setups. I tested two different setups. One of the first routes
Chris: I took is you can actually install a Home Assistant integration and then you
Chris: can use Home Assistant to get the location from any of the devices that you
Chris: track in Home Assistant.
Chris: So I selected a device, fed that into home assistant then home assistant gives
Chris: that to the big d witch to track my location and i don't have to cool yeah i
Chris: don't run anything else on my phone except for the home assistant app,
Chris: so you can reduce battery usage this way however it it's going to be as accurate
Chris: as your location updates are to home assistant and i found when i was driving
Chris: using ios there were sometimes five minute gaps and you would just get like
Chris: these sharp and if you guys zoom in on your maps actually you might see this too.
Chris: I don't know, but I will have these moments where it's like,
Chris: I drove through a house on the map.
Brent: That's impressive. Yeah.
Chris: I get them less with the dedicated app. I still get them. So it really comes
Chris: down to how you fine-tune, how often it updates, how often it uploads,
Chris: and you can tweak all of those settings.
Chris: But if you're looking for just something that's kind of basic and you want to
Chris: minimize battery usage and you already have Home Assistant, that integration
Chris: will work, and it was pretty accurate.
Chris: If you want something better, I think OwnTracks or their dedicated app on iOS is the way to go.
Wes: I do like that OwnTracks lets you toggle your, you know, how much battery do
Wes: you want versus accuracy. Because, yeah, I noticed the same.
Wes: It would miss some sections of my trip if it wasn't moving enough.
Brent: What I extra liked, I'm not sure if you caught this, Wes, is that in the actual
Brent: notification for OwnTracks, which is like a persistent notification.
Chris: You can pause.
Brent: You can pause, but you can also quickly change the style of reporting.
Brent: You just tap the button and it allows you to cycle through how aggressive the reporting is.
Chris: I thought you were going to say you can pause because one of the nice things
Chris: with OwnTracks is it makes it a little bit easier to say, stop tracking.
Chris: I'm going to the adult shop. Stop, whatever you do. I don't know what you guys do.
Chris: Pause. And then it's just right there to resume. That's really nice too,
Chris: because you can just tap it and then get in the app.
Chris: Their app makes that possible as well, but there's not like that Android persistent
Chris: notification aspect that gets you there quicker.
Chris: You could run this. I think the ultimate setup would be for people that are
Chris: trying to track a road trip would be maybe it's a container on an existing machine
Chris: or a little Raspberry Pi that you power up when you're on the road.
Chris: And it just powers up and it starts tracking and reporting immediately.
Chris: And when you turn the engine off, the Raspberry Pi turns off and it stops tracking.
Chris: And you could build your own self-hosted, totally private tracker to track everywhere
Chris: you drive your vehicle to capture all of the cool spots.
Chris: And then when you go back into the application, and this is still...
Chris: This is still very much under work, and it needs a lot more work.
Chris: But when you go back to the application, if you have, and Brent,
Chris: you probably have the best, you can go to MyData and Visits and Places,
Chris: and it will have a list of what it thinks are significant places that you visited.
Chris: And then you can add a note and save them and mark them.
Chris: So you could go back in a day and review and save some of the significant places you stayed at.
Chris: Now, you have to collect them for a bit to get there. But that's also really
Chris: nice for somebody who found a great campground or for somebody who found a great
Chris: restaurant or for somebody who found a new route.
Chris: And it's just really nice because you can mark it and save that for later.
Chris: And they have a UI where they have some suggested places that you could look at.
Chris: They have the ones you've confirmed or ones you want to save or ones you can decline.
Chris: Now, it's a little hard to go through right now because it's just kind of a
Chris: raw list. But I think as they work on that UI, it's going to get a lot better.
Wes: It does have a button now, at least. So it'll pull it up on the map.
Chris: Oh, yeah. Nice. Okay, good.
Wes: It is kind of a zoomed-in map, so you probably have to have some idea of where
Wes: it's showing you, but there's zoom control.
Brent: In OwnTracks, they have something similar called waypoints, and I've been marking
Brent: a few waypoints as we've gone through this experiment.
Brent: But I definitely expected them to show up in the big D-Witch,
Brent: and no go. Not yet, anyway.
Chris: Yeah, I don't think those make it up. Yeah, that's the thing.
Chris: You've got to mark them in the D-Witch if you want to save them.
Chris: It'd be great to have, if they ever make a data app for Android and on the iOS
Chris: one, it would be great to say, oh, save this.
Chris: So you boys got to play with something that I didn't mess around with,
Chris: even though I'm a big fan of Image, the self-hosted Google Photos alternative.
Chris: You, Wes, and Brent played around a little bit with Image integration with the Big D Witch.
Wes: Yeah, I believe it supports both Image and Photo Prism, if you're a Photo Prism user.
Wes: And you go into your user settings, and you just give it the URL string that
Wes: you need, as well as the API key, and then it can start pulling in,
Wes: I think it just sucks through all the various photos in your image and looks
Wes: for GPS data and then converts that to point information and feeds that into
Wes: the trip stuff you were talking about, etc.
Chris: Yeah, in fact, image stores in the database location information separately,
Chris: so it can probably just pull that right from the database.
Chris: So what did you see after this process was done?
Brent: Well, it does process a little bit, so it's not instant. I mean,
Brent: Wes and I were a little... We were going to dinner when we were doing this.
Chris: And we were a little impatient. You got a big database, Wes?
Wes: You know it.
Chris: A lot of dog photos in there.
Brent: But the nice thing is that then in Devarich on the map.
Chris: I'm sorry, what?
Brent: DeWitch, I think we're calling it.
Brent: You end up with these little photo circles, little sort of.
Chris: Overlaid on the map.
Brent: But also the photo preview itself overlaid on the map, which is a nice touch.
Brent: And you can hover over them and get like the photo itself and a bunch of metadata, which was nice.
Brent: And it also, Chris, allows you to click and see everything else on that date.
Brent: Or that location, sorry.
Chris: Oh, really?
Brent: In that location, yeah.
Chris: That was a functionality we
Chris: were particularly hoping to get out of Google Photos, which it does not.
Wes: It's not necessarily, I think, super optimized. A lot of this is pretty new in beta.
Wes: So, like, we were noticing, as we were bootstrapping the image,
Wes: I just started syncing all of the photos to my phone. But so I decided that
Wes: was probably not a tenable idea.
Chris: Yeah, yeah, yeah.
Wes: So, you can see it sort of, you know, I'd just taken a trip to visit my folks.
Wes: Or we were doing it at LinuxFest Northwest, and some of those got there.
Wes: So you can see like the various regions populating.
Wes: So you have a ton of photos right now. It seems to like load them,
Wes: not necessarily in like one optimized batch, but it was actually quite useful to see.
Wes: And I think maybe it would be less useful in the neighborhood you're in all
Wes: the time, but especially for going on trips and just seeing little reminders of like, oh, right.
Wes: There was that waterfall from that hike that we did over in these mountains or that seems great.
Chris: Yeah, I agree. So can you tell us a little bit about how you did set it up?
Chris: I know they have a Docker Compose.
Chris: It looks like it's pretty straightforward, although it's kind of a kitchen sink
Chris: application. I say that with love, but it's a big Docker Compose.
Wes: Yeah, it's a Ruby app. We haven't had one of those for a minute.
Wes: It's also powered by Postgres and PostGIS for that GPS processing geospatial
Wes: data handling, which is great.
Wes: There's a Redis container in there too, app container.
Wes: It is quite built out. They've set up a lot of nice things. I will say right
Wes: there's health checks for a lot of these guys and it's kind of pre-figured out
Wes: a fair amount of spots you can put in like oh here's how you know you want to make sure that you're,
Wes: Maybe you wanted to respond on localhost, but you also wanted to know that it
Wes: is proxy behind this domain name that you're serving it from.
Wes: So there's already some, like, nvars set up for that.
Chris: Which worked for us because you had Nginx in front of this as a reverse proxy, which was fantastic.
Wes: NixOS, indeed. Yeah, so it was really easy.
Wes: So NixOS just built up some Nginx to quickly play Let's Encrypt Proxy.
Wes: And then this thing was just powered by Podman.
Wes: So it works just fine with Podman, Podman Compose, if you want to use their
Wes: standard Docker Compose thing. or Docker, obviously.
Chris: I just love it because it's like, yeah, there's a Docker Compose available,
Chris: Wes. And Wes is like, great. Yeah, I'll take a look at this.
Chris: Okay, I got it running in Podman. Like, okay, let's go.
Brent: Chris, you did notice that someone's working on a NixOS module for this.
Chris: Yes, although it's been a month, but there does seem to be a module in the works,
Chris: which would be really, really great because this is definitely something I'm keeping after the show.
Chris: I'm going to keep this running. I'm going to put it on my rig directly and I'm
Chris: going to track every road trip I take with this thing.
Chris: I love it. And they do also offer a hosted version, which is €5 a month,
Chris: which works out to be about €60 a year, which is an early access discount.
Chris: But, you know, you can run on anything. Like I said, it's a Docker container.
Chris: You can put it on a Raspberry Pi. You can put it on a VPS.
Chris: You can fire it up when you need it and export the data when you don't because
Chris: it does have import and export options there.
Chris: Right now, was it a little tricky to get multi-user working?
Chris: I had a sense you had to do some finagling.
Wes: Oh, yes. a good point there. It didn't, it came with the default user, like a demo user.
Wes: It was not necessarily clear how to make more.
Wes: Admittedly, I did not read all of the documentation, surely.
Wes: But what I ended up doing was just manually inserting some more rows into the
Wes: user table, which did mean for a little bit I did not manage to give us each
Wes: unique API keys, which caused some confusion.
Chris: You know, if you go into the settings, there's an add user button.
Wes: Is that right?
Chris: Yeah, yeah. Jesus, Wes. Oh, my God.
Chris: Anyways, yeah, so be aware. Depending on how you create the user account,
Chris: you need to generate new API keys.
Wes: Oh, I see. Yeah, you're right.
Wes: Well, then don't do like I do.
Chris: It worked, though. Yeah, so we actually have...
Wes: I should have made you the administrator.
Chris: We have four users on this system. Wes, you have 1,017 points of locations tracked.
Chris: I have 2,535 and Brent, you have 1,376.
Chris: I'm surprised I beat you actually.
Brent: I wonder why that is because I moved around a lot more than you did.
Chris: And we're tracking sooner.
Brent: And I was trying to have it report quite aggressively because I figured.
Chris: Well, so do I. I maxed it. I wonder why. Maybe it's because for a little bit
Chris: I fed home assistant in. I don't know.
Chris: But I'll take that as a win. That means I'm the winner of the points of tracking.
Brent: Is that how we're measuring this?
Chris: Yay!
Chris: There's not many podcasts out there that are trying to go at it full-time making
Chris: a great Linux podcast, and we take it very seriously, but we need your support.
Chris: Now you can become a sponsor.
Chris: If you think you want to reach the greatest Linux audience in history,
Chris: email me, chris at jupiterbroadcasting.com.
Chris: I'll make a great deal for somebody that listens to this show,
Chris: but of course you can be a sponsor if you're a listener by boosting us using
Chris: Fountain FM or something like that, or by becoming a member at linuxunplugged.com slash membership.
Chris: That's a pretty sweet deal because you get the bootleg version which
Chris: right now is clocking in at a healthy one hour and 16
Chris: minutes and it's not just random chit chat we get extra
Chris: content just for our members you also get a shorter version if that's your speed
Chris: with no ads and all of the production quality of our editor drew so you have
Chris: options as a member or you can support each production with a boost and send
Chris: a message or reach the greatest audience in linux history email me chris at
Chris: jupiterbroadcasting.com.
Brent: Well we have some feedback this week Wes you went to a little meetup.
Wes: Yes so Tailscale hosted
Wes: a Seattle meetup I guess the first sort of community meetup they've done but
Wes: it sounds like they're hoping to do more big shout out to the team Natasha and
Wes: the rest of the Tailscale folks for putting it on great meetup I thought well
Wes: attended well run there was snacks drinks,
Wes: and folks giving little talks, including myself.
Wes: And it reminded me a lot of a JB meetup in the sense that there was just a diverse
Wes: array of folks from folks who were, you know, doing some serious tail scale
Wes: at work with like massive network traffic to folks doing neat stuff with IPv6 in their home web.
Chris: Oh, really?
Wes: Oh, yeah.
Chris: That's fun. Did you run into any listeners?
Wes: Yes, definitely some listeners. And then some folks who maybe,
Wes: hopefully, are listening now or thought Maybe they might check it out.
Chris: Well, hello to them. Thanks for listening.
Wes: And Tailscale's own Brad Fitzpatrick gave a sort of gripe fest of things they
Wes: wanted to fix. They know our issues in Tailscale. So that was fascinating.
Chris: Oh, that's great. Brad was there. That's great.
Wes: And then folks were able to sort of, you know, quiz him on, are you considering this feature?
Wes: How about that? Could it ever work? So you got a little Tailscale nerdery.
Wes: A lot of folks sharing stories.
Wes: Some folks from Cumulo told a story of how Tailscale saved them during like
Wes: a big outage they were having. and their tailscale backdoor was the only way
Wes: they had access to that remote data center.
Wes: So a lot of great nerding out about fun networking and home lab and all kinds
Wes: of crazy stuff you can do with tailscale. Here's how you know.
Wes: I talked with another presenter there and we were just sharing tailscale stories.
Wes: And I was like, yeah, you know, it really, it's surprising how well it runs in an initramfs.
Wes: Not surprised at all. Dude was like, yeah, yeah, it really does. It's great.
Chris: That's what I love about JB meetups and these type of meetups,
Chris: is you can say something like that.
Chris: And it doesn't go right over somebody's head. They know exactly what you're talking about.
Brent: And also, it's nice to know people are doing crazier things than we are.
Chris: Yeah, we're not the only ones doing wild stuff. Well, that's neat.
Chris: We were on the road. I'm glad you could make it.
Wes: So, yeah, I don't have any insider details or anything, but do keep an eye out
Wes: if you're a Tailscale fan. And maybe they'll do a meetup in an area near you sometime.
Chris: I really would love to do more meetups in general. So we should keep an eye
Chris: out for other meetups. We should do more of our local meetups.
Chris: You know, maybe somebody out there wants to be part of the crew one day,
Chris: and the meetups seem to be a great way to discover new people as well.
Brent: Isn't that how Wes showed up?
Chris: That is. And you kind of did too. I mean, LinuxFest essentially was a meetup.
Brent: Right?
Chris: That's true.
Brent: Good point.
Wes: Oh, I definitely met a few folks who had just gone to LinuxFest Northwest there too.
Chris: No kidding?
Wes: Absolutely.
Chris: That's great. Yeah. Boy, LinuxFest. It feels like it was just yesterday.
Chris: And I already miss it too. It was a good one.
Brent: To me, it feels like it was a month ago.
Chris: Really? It feels like we just went to Linux Fest and then we were on our trip.
Brent: Well, that is true.
Chris: Yeah, that is true. That is how it kind of went, isn't it?
Brent: Well, we got a baller booster here, our dear PJ.
Brent: Jeff, you sent in 68,382 sets.
Brent: Here's your little message. I've used both a laptop and that small PC for home
Brent: assistant. The power use is about the same, but the laptop is significantly
Brent: faster, has way more RAM, and can be used for more than just Home Assistant.
Brent: With the laptop, I was able to actually use the voice stuff and ESB Home builds in less than a minute.
Chris: I like that you call it a little message. Did you catch that?
Chris: It's a little message. It's our baller boost, buddy.
Wes: I also like that he's addressing it to Jeff. As if we read all of the boosts to Jeff.
Brent: I've spent so much time with Jeff. I mean, we've been under vehicles together in the last couple days.
Brent: I feel like we've moved to a new level in our friendships.
Chris: Yeah, he farted in front of us. So there's that.
Brent: Like I said, new friendship.
Chris: Now, this is where PJ and I have a disagreement.
Chris: Technically, he is right. It is a better machine, it is faster,
Chris: it can do more things, and it has a built-in battery screen and keyboard.
Chris: So it's basically everything you'd want, right?
Wes: And when Brent is unwilling to reboot his framework, it could be a backup show machine.
Chris: Oh, that's true too. However, as somebody who has lived for 10 years in a tiny
Chris: rig, I can tell you there are certain things that are absolutely just invaluable.
Chris: And one of them is as small as possible.
Chris: No monitor, no keyboard, nothing. A laptop, if you can believe it, is too big.
Chris: It is too big. I know. And so what you do is you, and also I'm a big believer
Chris: in integrating home assistant into everything.
Chris: So your water pump, your water heater, everything you do in your RV,
Chris: your lights is going to be run by home assistant.
Chris: Maybe even the ignition one day, the generator star is going to be home assistant.
Chris: It's going to be home assistant for everything. It's going to be crazy,
Chris: Brent. And you're going to use it for just absolutely everything we can possibly think of.
Chris: And so we want this to be its own dedicated machine.
Brent: Do I start my engine through Home Assistant?
Chris: I actually would be totally down for figuring that out. If you think about it,
Chris: it could be really genius.
Wes: I mean, it probably pre-warms the shower for you.
Chris: Well, like a lot of losers, when they get remote start, they have like some
Chris: sort of remote system. You know, what is that?
Brent: Proprietary for sure.
Chris: You could remote start from anywhere. And there's actually valuable.
Chris: There's actually value in that because maybe your batteries are getting low.
Chris: You want a little bit of alternator charge.
Chris: You know what? You bring up the old Home Assistant app, you hit the button,
Chris: and ESP connects a relay. Boom, your engine started.
Wes: It's a pretty short list of folks that have remote started over WireGuard.
Wes: So you could be on that list.
Chris: I think we could do it. And I'm saying, when I say everything,
Chris: I mean, you really need to think about it because it changes your life.
Chris: And so you want this to be its own dedicated appliance.
Chris: Hard, solid, only does one thing, and that's automate your life.
Chris: So you're not going to run Graphana on this thing. You're not going to run VS Code.
Chris: Well, maybe you'll run VS Code, but you're not going to even do voice stuff
Chris: on this thing. You're only going to run your automations and your home assistant
Chris: and your controls and your dashboard, and that's it.
Wes: Is there an argument for, you know, Olympia Mike who just keeps supplying them
Wes: with backup Xbox for decades?
Chris: So I'm just actually, you know, I'm having some fun. But my point is really,
Chris: I find it super valuable to have a dedicated machine.
Chris: And I've gotten by on a Raspberry CM4 with two gigs of RAM for two, three years now.
Brent: Weren't you just saying this morning you really want to upgrade?
Chris: I do. I think it needs more memory.
Brent: Oh, okay.
Chris: But you have eight gigs.
Brent: Oh, that's true.
Chris: Yeah. So, you know, yes. and then i think the way
Chris: you do the other stuff like uh voice analysis locally
Chris: um you know whatever services like
Chris: jellyfin you might want to run whatever else that's an odroid that's something
Chris: else that's also very small or it's a raspberry pi whatever it is but it's very
Chris: small it's dedicated to just a few things also dc power um that's at least my
Chris: 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.
Wes: You do have to consider if you want the support contract from Chris Lasko.
Chris: Industries. Yeah, right.
Wes: You probably do have to go with his recommendations for the document you signed.
Chris: Yeah, let's we'll review the contract.
Wes: Turd Ferguson boots in with 27,333 sats.
Wes: Starting off here too, Boos, sending sats and good vibes for the van rescue.
Chris: Mmm, I think those vibes helped.
Brent: Thank you, Turd. It did, certainly.
Chris: I think we could have used those
Chris: vibes a little sooner, but once we got to Oregon things turned around.
Brent: Could he use those vibes for like restaurant choosing?
Chris: Yeah, and some of the gas tank work, and some of the electrical,
Chris: and that exhaust leak that we fixed and then unfixed.
Brent: I don't remember that one.
Chris: We'll get into that. We'll get into that later.
Wes: Yeah, that's because of the exhaust. It does stuff to the old memory.
Chris: It does make you very sleepy. But that's for the launch. Thank you, Turd.
Wes: Okay, and then second boost here. Did you know, in May of 92,
Wes: SLS not Slackware was the first Linux distro, making installs way easier and
Wes: sparking the distro boom.
Chris: SLS in 1992, not Slackware. Do you remember what SLS stands for? I think.
Brent: Linux trivia.
Chris: I think it's soft landing Linux. The idea was making it easy to get started with Linux, if I recall.
Brent: Way back in 92.
Chris: Yeah, isn't that something?
Wes: I think we can still install it today.
Chris: I do not. have you tried maybe in camu maybe we could do it in camu thank you
Chris: turd appreciate the boost.
Brent: Well fabian sent in 10 000 sats oh i think it's fabine,
Brent: Trying to prep for the TUI challenge, I've been trying to find a good way to watch YouTube.
Brent: All those YouTube TUIs seem to be based on NVIDIAs, which gets blocked all the time.
Brent: So I created my own based on the YouTube API, and we'll just show you a list
Brent: of videos by your subscriptions in the TUI.
Brent: It's not real YouTube subs, but then it opens an MPV.
Brent: This saves so many gigs of RAM.
Chris: You know, I would rather just have a UI that shows me my subscriptions anyways.
Chris: but raises I think one of our first gray areas that we need the listeners to
Chris: help us clarify does launching MPV from the terminal count since that is technically
Chris: a graphical application right.
Wes: I think one can make the argument that if you're controlling it from the terminal
Wes: and it's something that the terminal can't reasonably provide in a realistic
Wes: sense maybe but you gotta.
Chris: Boost in to tell us or contribute Yeah, because I feel like maybe that's the
Chris: line. If the terminal can't do it, you can't do it.
Brent: There must be a terminal out there that does it, right?
Wes: Well, there's LibCaca. That's the bargain basement version.
Chris: I'm sorry?
Wes: Are you okay? Yeah, I mean, look it up.
Chris: Do you need to lay down? Are you all right?
Wes: Well, that's a separate matter.
Chris: Okay. It can't be done. I mean, maybe, because couldn't I just launch Chrome
Chris: from my terminal if this is okay?
Brent: Oh, yeah, I don't think that would be okay.
Chris: Right, so where do we draw the line here? well.
Wes: You know Chrome's a full featured thing this is literally.
Chris: Just launching not a full featured thing compared.
Wes: To a web browser.
Chris: Well okay I'll give you that web browser's practically an operating system.
Wes: Just needs a good text.
Chris: Out of it okay well why couldn't I launch you know Zed or VS Code or Gedit.
Wes: Yeah, I mean, there's a slippery slope to be pointed out here.
Chris: I feel like it's too slippery. You see what I'm saying?
Brent: So we need...
Chris: We need the listeners to either boost in or participate in the GitHub and clarify
Chris: this particular gray area.
Chris: Because I don't know how to... Because I want to watch videos. So I want this.
Chris: But I recognize it opens up the door to cheating. It really does, boys.
Wes: Do we have like a pre-approved shortlist or something?
Chris: Hmm. Hmm. An approved list. Like MPV and VLC, maybe?
Wes: Or like for specific carve-outs, right? You can't do a browser, but you can.
Wes: If you're just playing videos, that's fine as long as you launch it from the
Wes: terminal. But I don't know.
Chris: I don't have the answers here. I don't know. I don't know. Because you can't
Chris: watch videos in a terminal.
Chris: Unless, like Minimek tells us, you use Enlightenment. Then you could.
Chris: Maybe I'll just use Enlightenment. I don't know.
Mumble: No, no. It's a standalone. It's a standalone application. You need the AFL libraries.
Mumble: You just install terminology, and then you're in. It's part of every distribution.
Chris: Well, look at that. A little Enlightenment technology saving the day.
Chris: So I feel like if the terminal is natively capable of doing the task.
Wes: Then you should do it there. Yeah, agreed.
Chris: Yeah, then that's okay. Ooh, maybe that's the line. We got to figure this out.
Brent: I have a prediction. Okay. I think we're going to find several other gray spots
Brent: that we're going to have to figure out.
Chris: Oh, great. Thanks, Brent.
Brent: Oh, you're welcome.
Chris: Oh, my God. Oppie 1984 comes in with 4,000 sats.
Chris: Brett, if you plan on doing any traveling with the van and why have a van if
Chris: you're not going to travel, then I suggest a GMRS radio.
Chris: Most truckers have switched from the old CB to GMRS, and while you need a license
Chris: to transmit, you can listen without a license, and I know you like to listen.
Chris: Also, you have to build a meshtastic node because, well, reasons, Brent. I mean, Brett.
Brent: Well, I will say I did bring my meshtastic node on this trip.
Chris: Uh-huh.
Brent: I mostly forgot to check it, and also I don't think it picked up very much,
Brent: or I'm using it wrong, or Jeff saved me.
Brent: But I do think it's a great idea to put some radios in there.
Brent: I'd be curious to hear why the truckers have moved from CB to this new GMRS.
Chris: Yeah, I would actually like to know that too. Because the CB is such a classic thing. It is.
Chris: 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.
Chris: But I think what you'd want is kind of like a dedicated MeshTastic node built in.
Chris: Maybe even something that has its own power source. Put a little solar panel
Chris: for it. I don't know. I'm just saying.
Wes: You know, if you just stick to CB, you could be CB Brent and,
Wes: you know, sort of big fish, small pond, right?
Wes: You're the guy on the CB all the time. So anyone who's listening, they're getting you.
Chris: He's already buying tapes. Right. You went to the thrift store and bought a bunch of tapes.
Brent: I did.
Chris: So he's kind of got a retro vibe going.
Brent: Diana Ross. Pretty good.
Chris: Yeah. Yeah.
Brent: I think maybe coming near you, CB Radio will feature Linux Unplugged maybe next week.
Wes: The one, the only, the genius bean himself, Gene Bean, comes in with a row of ducks.
Wes: Just wanted to say that I'm amazed at how nice the headsets you used at LinuxFest sound.
Chris: Oh, good.
Wes: On another note, I love hearing what y'all are doing with Home Assistant.
Wes: I am way, way, way down that rabbit hole and would be happy to help if you want.
Chris: Oh, that's great. Gene is a great resource. I'm pretty far down that hole myself.
Chris: I wonder, Gene, like, where are you and I at? Because I'm sure you followed
Chris: my journey on Self-Hosted.
Chris: I loved giving folks a tour of Lady Joops' Home Assistant system at LinuxFest.
Chris: There was like three or four different distinct batches of people I brought
Chris: through the RV to show them how things worked.
Chris: And it controls everything. Thank you, Gene Bean. It's good to hear from you.
Brent: Well, son of BoomBus comes in.
Brent: 4,444 sats across two booths. I think that's a bunch of ducks.
Brent: What's the least useful Home Assistant integration you have but refuse to delete?
Chris: This does become a problem.
Wes: There's a lot of integrations. I'm seeing as I get more integration set up.
Wes: I don't have any that fit yet, I don't think, because I'm still just still getting
Wes: them configured to my next config, but.
Chris: There's a lot of community repos too, so you can add even more than the built-in
Chris: ones. So you can really go crazy.
Chris: Mine, I think, might be a surprise. I think it's the Jellyfin integration.
Chris: And when I had Plex, because I thought I'd really use that and I'd maybe build
Chris: automations, like we're going to watch a movie and we'll have the lights turn off,
Chris: or I'll have a card that shows what's currently being played and I can hit pause,
Chris: Or I can track how much we watch the TV with the statistics and Home Assistant. Look at me, everybody.
Chris: But the reality is never use it. Never use it for Plex.
Chris: Never use it for Jellyfin. What I found much more useful is a remote control
Chris: and just be able to use the functions of the television via Home Assistant and
Chris: launch any application.
Brent: Now that you've expressed this to yourself, will you delete it?
Chris: No, I think I'll keep it. Great. I mean, it works.
Chris: There you go. Thank you, son of a boom bus. Boom bus isn't a bad name.
Chris: We need people to boost in names for the van.
Chris: Van or bus. Because bang bus isn't sitting well with people.
Chris: Bang bus is not sitting well. They took it in the wrong direction.
Wes: Plus, this way we can make a series of bang bus swag. That'll be the legacy
Wes: swag, limited production run.
Chris: Okay.
Wes: And then we'll have the new swag for the new name.
Chris: Because we're still on top of our swag game. But we need new names. It could be a van.
Chris: It doesn't have to be a bus. It's technically a van. It's a beautiful,
Chris: big, juicy van, really, is what it is. And so just keep that in mind.
Chris: Yes, we call it the bang bus. but it's really,
Chris: a big juicy van.
Brent: Well, Tomato sent in 5,000 SATs. Hearing about the state of the engine ceiling
Brent: in that van, here's some SATs from MQ7 so Brent can get carbon monoxide monitoring going.
Chris: Ooh, now, PJ, you're up to date on the MQ7.
Chris: You've been having some long-term project plans around building an MQ7 sensor,
Chris: right? For carbon monoxide?
Mumble: I got a couple of them sensors already. You just need to get some MOSFETs to
Mumble: create tiny little heaters on them, and then we can use them with ESP devices.
Brent: Wait, did you say a heater?
Mumble: Yep.
Brent: Oh, I feel like I'm going to get in a territory I'm not ready for.
Chris: Yeah, buddy. Yeah, buddy. All right. Thank you, Tomato. It's nice to hear from
Chris: you. Otter Brain came in with a row of ducks.
Chris: He says, thank you, guys. Thanks to you guys, I got three Raspberry Pis going.
Chris: One for Home Assistant, one for NextCloud, and one, of course, for PiHole.
Chris: it's been so much fun learning how to set these up but here's my question any
Chris: suggestions on keeping your headless pies tidy do you have a way of tucking them away,
Chris: here's what I've done I have since destroyed this but what I originally did
Chris: and I really I loved it so much I took pictures you know and I like favorite,
Chris: but I bought a bunch of little sticky pads off of Amazon that have routing for
Chris: wires in them and you can snap wires into them and they have a little 3M backing.
Chris: And I just routed the wires along a wall and just kind of embraced the wires
Chris: but did them nice and tidy.
Chris: And so like the remote disks and like the, I have my Z-Wave and Zigbee sticks
Chris: there off on their own little USB extension cords and those were tidy and put
Chris: there. And I thought that made it look really nice.
Chris: And then for some of my systems, I also threw a Pi KVM on there.
Chris: So I kind of did the same thing for that and just kind of embraced it.
Chris: And I got that also the double-sided 3M Velcro off of the Jungle Store.
Chris: And I just put that on the devices and I stick that to the wall, too.
Chris: And then it makes it really easy to pop them off and change something and pop
Chris: it back on. And you just embrace the wires, but you make them look good.
Chris: And then it looks engineered and not messy.
Brent: It would be sweet if there was, like, a Raspberry Pi backplane you could just
Brent: kind of plug them into. Wouldn't that be sweet?
Wes: I mean, folks have that.
Chris: Do they?
Wes: Well, versions of it. There's, you know, various enclosures,
Wes: especially for mounting, like, a bunch with built-in switches and then.
Chris: Yeah, I like that. I love that. I should build something like that and just
Chris: you know, you would, oh man wouldn't it be great if the CM4 platform had gone
Chris: that way with carrier boards?
Chris: Oh, that'd be a way. That would be a way.
Wes: The dude abides us 15,000 cents.
Wes: I'm always reminded to boost live on Sundays when that Matrix notification pops up.
Chris: Aw, thank you, dude.
Brent: Yeah.
Wes: Nice Home Assistant interview, too. More of those, please.
Chris: I really like Polis. I think Polis is good people. And I really respect the
Chris: trajectory they've taken, because I've been following them for a little bit over five years now,
Chris: and they've just been taking the right step after the right step to make sure
Chris: that if you deploy something using Home Assistant,
Chris: it's not going to get clouded up, it's not going to get identified,
Chris: it's going to be supported.
Chris: And I really appreciate the direction they've taken things. Thank you.
Chris: We also are very sensitive to not overdoing the interviews.
Chris: We know not every guest is dynamic and interesting, but we think Paulus is one
Chris: of those. So we do monitor the feedback on the interviews. Those types of things
Chris: are always signals that we're looking for from you guys.
Wes: We want to make the show you want to listen to.
Brent: Well, Odyssey Westra sent in a live boost. That's actually a live road ducks.
Brent: Live tracking for me is super important for my job. I use it to keep track of
Brent: when and where I've been and track my miles for my job. Oh, that's actually brilliant.
Brent: Plus, it helps with billing for multi-day projects. So self-hosting this,
Brent: he means Devarich, will be an important step in de-googling myself.
Brent: Love y'all and live meep.
Chris: Yes. Nice. Honestly, that's so cool to hear. I hadn't even thought about it for tax accounting.
Brent: That's brilliant.
Chris: That is so brilliant. and you know it does have the ability to go in there and
Chris: mark trips and so you could go in and say this was a work trip you.
Wes: Might want the high fidelity mode for that part.
Chris: Oh Wes I always have the high fidelity mode on I always do I'm.
Brent: Gonna add a feature request for fuel station integration.
Chris: Oh that would be amazing how would you do that I guess you could look up fuel
Chris: stations yeah some way somebody could somebody could figure that out right there's.
Brent: A whole ecosystem here I think.
Chris: All right. Well, GC boosted him with 7,777 sats.
Chris: He's coming in with a Grafonicon 2025 report.
Chris: Oh, my God. Reading my mind. Some value for value right here.
Chris: I received the Golden Grot Award for Best Professional Dashboard and presented
Chris: my use case on an industrial system monitoring of a wastewater treatment facility.
Chris: I would like to see this.
Brent: That's amazing.
Chris: Is there a video of this? Approximately 2,000 metrics at one second resolution.
Wes: Yeah, definitely want to see this.
Chris: Definitely want to see this. Great networking opportunity for data nerds.
Chris: I also plugged the show a ton.
Wes: Oh, you.
Chris: Oh, wow.
Chris: A NixOS sticker on my laptop brought out the NixOS lovers as well.
Chris: I met someone who uses Proxmox with a NixOS LXC containers on board.
Chris: Talescale was a sponsor. Unfortunately, I had to leave before Talescale community
Chris: events started where they had some local celebrity named Wes.
Wes: Oh, sorry not to have you there. But GC, thanks for the report.
Wes: And are you local? Were you just here for the conference?
Chris: Yeah.
Wes: There's several things we should follow up on.
Chris: And this is something I extremely appreciate. If you attend a tech event,
Chris: an industry event, especially if it's adjacent to the show, please do send these reports in.
Chris: It's so great just to keep in these, not only for our radar,
Chris: so we kind of know what these events are going on, but so the other folks listening
Chris: get an idea of what's going on out there too and what's actually worth attending.
Chris: Man, thank you, everybody.
Brent: I do have a final question here for GC. You mentioned 2,000 metrics, one second resolution.
Brent: Are you running this off a little laptop in a bus? Is that what you're using
Brent: or some kind of industrial PC?
Chris: All right, thank you everybody who supported the show, either our members or
Chris: by supporting each individual production.
Chris: Those of you who stream sats, we had 28 of you, and we stacked 40,555 sats. Not too bad.
Chris: Thank you everybody who stream sats as you listen. We see you, and we appreciate you.
Chris: When you combine that with those of you who boosted, we had a very humble but
Chris: yet very appreciated 189,657 sats. It's not our biggest episode ever.
Chris: Maybe people don't like Home Assistant.
Chris: I don't know what's going on there. Or maybe people are having problems boosting.
Wes: Now you're just trolling.
Chris: Maybe. But we do appreciate everyone who supports each production,
Chris: either through the free Value to Value
Chris: Network or through a membership at linuxunplugged.com slash membership.
Chris: You're the greatest, and we appreciate you.
Chris: All right, we have two picks this week, and one of them was cooked up by our very own Wes Payne.
Wes: Yeah, it's sneaky. You know, you're kind of one of the users I have in mind
Wes: for this, actually. So it's a little gift to you, maybe.
Chris: All right.
Wes: Well, we all know how great the Docker tail scale sidecar pattern is,
Wes: right? So you're running something in Docker.
Wes: You want it to be exposed to your whole gosh darn tail net.
Wes: So you do the sidecar. So in the same network namespace, you've got your application
Wes: running. maybe it's Dwarich, maybe it's something else.
Wes: And then a tail scale runs there too. And so to that app, it gets access to
Wes: the tail net with its very own tail net name.
Chris: And IP.
Wes: And IP.
Chris: Which is really handy for applications like VS Code. So if I just go to code.whatevermydomain.com
Chris: is, I'm actually just accessing a Docker container that is just right there
Chris: on that IP with that just served up directly from the Docker container.
Chris: I'm not going through Nginx. I'm not going through reverse proxy at all.
Wes: And it's nice in the sense that okay maybe you still want tail scale on your
Wes: host for the host to access and other things but it decouples those so even
Wes: if you decide later to move,
Wes: that application stack to a different host nothing else on your tail that has
Wes: to care because they never knew where it was in the first place.
Chris: And when the application starts up it's the same IP the same name all that stuff.
Wes: Even on.
Chris: A different host.
Wes: Yep so that's great but as you probably know from listening to the show we're
Wes: all running a bunch of stuff with Nix OS now,
Wes: and there is no built in automatic sort of
Wes: do the same easy sidecar system because one of the advantages
Wes: of NixOS depending on what you're doing is you don't
Wes: have to isolate everything to run all
Wes: these things at the same time so by default they're not totally off in their
Wes: own world like you get by default with Docker so I am working on a NixOS module
Wes: to just wrap systemd services and NixOS services basically so that they run
Wes: in their own network namespace with their own tail scale just like happens with Docker.
Chris: So without a container but you're still taking advantage of network namespaces.
Wes: It's basically me sort of uh re-implementing a
Wes: bunch of the stuff that docker compose does with networking so there's a bridge
Wes: on the host and then we use virtual ethernet pairs into namespaces per service
Wes: and a tiny little dhcp server if i'm honest to tie it all together and then
Wes: yeah so then they're able to get a natted firewalled outbound connection and then tailscale that.
Chris: Is really slick and to be totally 100 transparent,
Chris: We don't get paid for any of this. In fact, we're giving the milk away for free
Chris: right now. The only thing Tailscale pays for is the spot at the top. We just really use it.
Chris: And this makes it possible to essentially have every application you want to
Chris: run via Nix get its own Tailnet IP and name and all of that.
Wes: And there's initial support for doing Netbird as well.
Wes: In theory, you should be able to do this stuff. I haven't tried Nebula or anything,
Wes: but in theory, other... I called it Mesh sidecar because in theory,
Wes: other services should work just fine.
Chris: Am I right? The magic is really the network namespaces.
Wes: That's a lot of the whole setup and making it work and then getting the right
Wes: wrapping and modifying of the systemd service to make sure that it like joins
Wes: the right network namespace and the namespaces get set up and all that kind of bookkeeping stuff.
Wes: And then the actual, yeah, the actual mess stuff, other people are doing much better.
Chris: Nice work.
Wes: So also, maybe don't use it just yet. I already want, I made the initial interface
Wes: really easy. So you just give it a list of services you want to wrap,
Wes: which works great as long as you're not trying to run like multiples of those
Wes: where you might want to have different names.
Wes: You know what I mean? Like it works great if you're just running one grafana
Wes: instance across your tail net but if you start to have multiple or.
Chris: Plex or jellyfin.
Wes: Right um because it just right now it uses the nix os module interface name
Wes: as well as the system those are all assumed to be identical so i want to add
Wes: some configurability so you can
Wes: change like which exact maybe the nix os and the system d name aren't exact
Wes: matches or you want to have the name on your tail net be slightly different
Wes: oh sure so i'm going to modify the interface a little bit so there's already
Wes: going to be one breaking change.
Chris: I'll tell you the immediate use case if it hasn't quite clicked yet is jellyfin
Chris: you know that's one area where i think
Chris: jellyfin doesn't quite stack up to plex and that is sharing
Chris: you know it is so easy on plex to share with your buddies and have multiple
Chris: friends and multiple servers and jellyfin doesn't necessarily have that inherently
Chris: built in but you can solve that if all of your buddies are on a tail net and
Chris: you could because this is application specific this one application could be like on a dedicated,
Chris: shared tail net with your friends.
Wes: Yeah, you shared just this node or whatever.
Chris: Yeah, and you can all get to your Jellyfin servers.
Wes: Yeah, it doesn't matter what else you're hosting on that same box.
Chris: So that's where it gets really cool, just to kind of put it practically down.
Brent: I noticed this is licensed MIT. Can you say anything about that?
Brent: Why did you chose MIT specifically?
Wes: It's kind of my default license, just because it's really short and sweet.
Wes: And I mean, there are probably projects I do want to license with more copy left style licenses.
Wes: But for a lot of stuff on the programming side, library things tend to be licensed
Wes: more on the MIT or BSD or Apache or similar spectrum.
Wes: So I don't mind the MIT, and I've built that into my little make-a-new-get repo script.
Chris: I have a second pick here. This one is also a little niche but useful if this
Chris: is something you've been looking for.
Chris: It's called Element.fm, and I was just recently made familiar with it.
Chris: element.fm and it is a podcasting 2.0
Chris: open source hosting platform it's licensed under the
Chris: gpl3 they offer unlimited episodes they
Chris: have ai automated generation of certain things you might like you know show
Chris: notes whatever you might want to have it generate they supposedly i haven't
Chris: seen these yet have advanced analytics but the big thing here for me is the
Chris: podcasting 2.0 transcriptions chapters value for value all built into the hosting
Chris: platform and they're launching with an API.
Chris: So they have an API that people can use, which we really love.
Chris: It's also self-hostable if you want to go that route. So if you're looking to
Chris: produce a modern podcast that supports things like live tags and the cloud chapters
Chris: and, of course, transcriptions, which I think are super valuable to have these
Chris: days and going to make it much more relevant in a world of LLMs and,
Chris: of course, value for value, too.
Chris: Which supports the ecosystem of the podcast app creators, the hosting platforms,
Chris: and the creators directly.
Chris: And it's all just built in to element.fm. So they contacted me over the week
Chris: and said, how come you've never looked at us? And I took a look and I was very impressed.
Chris: So if you want something out of the box, it's going to just make you very competitive
Chris: in the podcast space. Check it out.
Chris: I think it looks really good. And it's GPL3.
Chris: So the code is open source, which I feel really nice and solid about.
Chris: When you're looking for something you want to be able to rely on for years as
Chris: a podcaster, that gives you kind of that insurance policy.
Chris: And you can self-host it if you want to. So check it out. We will have links
Chris: to all of that in the show notes.
Wes: Neat.
Chris: Yeah. There we go. So this was a packed episode. We talked about the news items.
Chris: We talked about the Big D Witch.
Chris: All of that will be linked in
Chris: the show notes. You can find those over at linuxunplugged.com slash 614.
Chris: Now, we're not going to be live next Sunday.
Chris: We will be on a trip to Boston because we are attending Red Hat Summit.
Chris: So we'll probably have a prerecorded episode. We'll have something for our members as well.
Chris: We're kind of flying by the seat of our pants this week, so we'll get all of
Chris: the details figured out for you really soon.
Chris: I want to remind you, I'm looking for feedback on my sound. We're looking for
Chris: ideas for Brent's bus name, which is technically a van.
Chris: So you could also, if van makes it more litter, that's fine.
Chris: And then last but not least, please do check the show notes for the TUI challenge.
Chris: We'd love your feedback while we're traveling. It's a great time collectively
Chris: for the community to work on that. So when we get back, we can hopefully launch
Chris: the TUI challenge, at least pretty close to when we get back.
Chris: We'll have all of that at linuxunplugged.com slash 614.
Chris: Now, we will have more for you. We'll have one more episode before we're actually
Chris: at Red Hat Summit, and then we'll have all of the details. You know,
Chris: we'll take the best bits, the things that you really care about,
Chris: the stuff you want to know about, all of the signal from the noise from Red
Chris: Hat Summit, and we'll have it in a future episode for you.
Chris: So go subscribe. Links to everything, our Mumba Room, our Matrix,
Chris: our RSS feed. It's all at a website.
Chris: It uses HTML. it's incredible linuxunplugged.com you don't even have to type
Chris: the https anymore can you believe it they took that out you don't even brother
Chris: you don't even need the www www can you believe it i love the www you don't
Chris: need it i'd say put it in there why not i think we set up a redirect so do it
Chris: thanks so much for joining us see you next tuesday as in sunday.