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. Coming up on the show today, we'll tell you about a homemade
Chris: tool that we just built that I think you're going to like.
Chris: And then it's time for config confessions.
Chris: From finely tuned setups to total config carnage, we're going to review some listener home labs.
Chris: Then we'll round it out with some great shout outs, some picks,
Chris: and more. So before we get into all of that, we have to say time-appropriate
Chris: greetings to a packed mumble room. Hello, virtual lot.
Mumble: Hello. Hello. Hello. Hello, everybody.
Chris: Goodness. We got a big one today. Hello. This is our last episode in the studio
Chris: before we hit the road for Texas Linux Fest.
Chris: So I want to say a good morning to our friends over at Defined Networking.
Chris: Go to Defined.net slash unplugged Nebula. It's a decentralized VPN built on the Nebula platform.
Chris: I don't know, Wes, maybe you were hip to this first between the two of us.
Chris: You were on this like a bonnet when Nebula shipped. It's really something special.
Chris: It's optimized for speed. And what that means is, like on your mobile device, less battery usage.
Chris: On your servers, on your laptops, on your desktops, less traffic.
Chris: It also means there's a simplicity to it.
Chris: And they're using industry-leading security that you can trust.
Chris: And unlike traditional VPNs, Nebula has a decentralized design,
Chris: so your network stays resilient if you're using their managed system or you're
Chris: building yourself for your home lab or a global enterprise.
Chris: I mean, we're talking massive, massive corporations and organizations already use Nebula.
Chris: It was developed in 2017 to get Slack connected across their various data centers around the world.
Chris: So it was engineered for scale and performance from day one.
Chris: Nothing else is like Nebula. And when we get back from Texas Linux Fest,
Chris: I am looking forward to a fabulous network makeover.
Chris: It might just be Wes and I, but we're going to do it.
Chris: Brent has another tale to tell us. But we're going to redo a network from a
Chris: design that's about five years old and modernize it with new DNS and a Nebula mesh network.
Chris: And you can take advantage of Nebula if you want to build it in your home lab
Chris: or get started with 100 hosts absolutely free, no credit card required on Managed Nebula.
Chris: Go to define.net slash unplugged.
Chris: Redefine your VPN experience today. Support the show and try it out.
Chris: It's define.net slash unplugged.
Chris: Yes, Texas Linux Fest, October 3rd through the 4th at the Commons Conference
Chris: Center, is just about five days away.
Chris: And our buddy Carl George joins us to celebrate. Hey, Carl!
Mumble: Howdy, y'all.
Chris: Hey!
Wes: Hey, hey!
Chris: How you feeling? Things are getting pretty close? You got like that pre-fest
Chris: jitter anxious stuff, or are you feeling confident?
Mumble: Absolutely.
Chris: You do? You're supposed to be like, no, it's all handled, man. It's great.
Mumble: Yes, yes, everything's lining up perfectly.
Wes: No problems at all.
Chris: I mean, it's a community-run event, right? It's not like there's a big corporation
Chris: that has a team of people that run these things every year and they just come
Chris: in and execute on some plan they already have.
Mumble: Correct. It's all volunteer run, so a lot of times, you know,
Mumble: stuff needs to happen and it's like, okay, well, I'll get to that this weekend
Mumble: when I'm not doing my day job and things like that.
Chris: And it's at a new location. I imagine that's a pretty new, big variable.
Mumble: Yeah, being a new location, I was worried about, but thankfully this venue has
Mumble: been really nice to work with. So a little bit lower stress there.
Mumble: That's working out well.
Chris: So I think one of the things we haven't been very clear about is people do need
Chris: to register. There's a process there, right?
Mumble: Yes, sir. You can just go to the website, 2025.texaslinuxfest.org.
Mumble: There's a little link there to buy a ticket.
Mumble: Right now, the ticket prices are $75 for the main ticket.
Mumble: And there's a $100 ticket that will get you the swag pack.
Chris: Ooh, swag pack. And we have a promo code JB15 will get you 15% off the ticket price, too.
Chris: So that ain't too bad. Save a little money there.
Chris: Carl, one of the things I'm concerned about is that you won't have time to take
Chris: us to a new barbecue location.
Chris: I mean, I still wouldn't mind going to Terry Black's, but I'm concerned you're
Chris: going to be too busy to sneak out for a good barbecue.
Mumble: That is a concern of mine as well. Definitely not Terry Black's.
Mumble: That's going to be way too far from where the venue is. It's a little bit different
Mumble: part of town than last year. Yeah.
Mumble: There's a few other barbecue spots in the area. I'm going to try to go find some good barbecue.
Mumble: There's one that's really highly ranked called Interstellar Barbecue that's
Mumble: about 10 minutes away from the conference center.
Mumble: I'm going to try and go out there on Thursday and try my luck there and wait in line.
Chris: Now, I don't know. Maybe we could talk to somebody at the fest and say,
Chris: look, it's really important that Carl takes this time because it's fest outreach
Chris: and its relations with the media.
Chris: And so he's got to take them out and show them a good time.
Chris: So that way they talk really well about the fest. I mean, you know,
Chris: we can reach out and, you know, suggest that to somebody if it carves a little time.
Mumble: But I support this idea.
Chris: We have lunch planned. I don't know if you can make it on Saturday.
Chris: We have our birthday lunch during the Saturday lunch break.
Chris: So if you're around, you're totally welcome to join us for that, too.
Mumble: Of course. I'm going to try to make it.
Chris: Well, I'm excited, Carl. Can't wait to see you in just a few days.
Chris: You may end up having lunch with Brent. He's making good progress.
Mumble: So hope a whole bunch of the community can come out there to the event.
Mumble: There's the Texas Linux Festival matrix room on the JB server that a few people
Mumble: are chatting about, you know, either going to a conference for the first time
Mumble: or they're conference regulars, but they haven't been to Texas Linux Fest before.
Mumble: So hoping to see a lot of the JB folks out there.
Chris: Yep, that Texas Linux Fest chat is a good one. If you want details about our
Chris: lunch event, we'll have links to that in the show notes. Of course,
Chris: links to Texas Linux Fest, too.
Wes: I'm getting excited.
Chris: Yeah. I'm hoping you'll have some pocket meat, too. That's right.
Chris: Don't you think, Brent? That's important.
Brent: I mean he always gets me when i go anywhere he's just like hey hey hey vegan
Brent: hey i know you only like eat meat a couple times a year and like do you want
Brent: some out of my pocket it's nice and warm and.
Chris: Brent always says yes,
Chris: The warmth helps, you know, makes it a little softer.
Brent: We did want to try another little piece of software you've been excited about,
Brent: Chris, at the meetup, but also at the conference.
Brent: You wanted to get people to try BitChat.
Chris: Yeah, I think especially once we're either in route or on the ground,
Chris: because it doesn't require a server.
Chris: It doesn't really require creating an account. It's all location based.
Chris: And when you're at the venue, it'll all be Bluetooth based. So it should also
Chris: survive like Wi-Fi issues or if you don't have cellular data.
Chris: and we're going to talk more about bit chat but i do think it's worth mentioning here
Chris: that we are planning to use it to sort of coordinate with folks on the
Chris: ground for like the lunch day or people have
Chris: questions things like that we're going to be popping into bit chat bit chat
Chris: which we'll have links to that in the show notes too but let's get into it let's
Chris: get into the show gentlemen we are like i said just five days away from texas
Chris: linux fest and brent is already on the road i,
Chris: I suggested that by this point I would be able to guess if he has a chance of beating Wes and I,
Chris: and I'm feeling a little nervous, and I know so far it's been pretty adventurous,
Chris: so now I'm gambling on some more adventure, I think, in order to beat you. How's it going?
Chris: Where are you right now, Brent? What's going on? You're already well into the trip.
Brent: I use the tauntings that you've been doing for the last week of saying that
Brent: i would arrive last to get a head start yesterday somehow i managed to drive,
Brent: 700 miles or something like that.
Wes: How did that happen don't hurt yourself how are you even here today.
Brent: I wanted to give myself a really really really good head start you wanted to.
Chris: Put the fear of god in us and you did.
Brent: Yeah how's it going over there guys i'm i hear you're not leaving till monday so.
Chris: Uh as of right now brent is um about 800 miles for uh no 945 miles from austin
Chris: as the crow flies and as the crow flies and west under a.
Wes: Thousand that that's what i felt like that was my marker it's like okay if he crosses that.
Chris: Already you and i are about 2300 miles as as it goes uh so.
Brent: I'm basically
Brent: to you know if you want to situate yourself i'm just a little bit
Brent: south of chicago currently okay and i'm
Brent: i think in a really special place uh it just so happened i got invited by one
Brent: of our absolute baller boosters to hang out at his place for the show so um
Brent: i'm sitting here beside adversary 17 can you believe it.
Wes: Hello adversaries thank you for helping our boy Brent.
Chris: Yes. Wow. How cool is that? That, you know, a little shout out there.
Chris: That's pretty cool because, you know, I felt like Brent was visiting a celebrity. He was stopping by.
Chris: We're jealous. You're at Adversary's house right now?
Brent: No way.
Chris: That's pretty great. And then he's hooking you up, you know,
Chris: he got you on the internet, he got you a little spot to record.
Wes: You refused his glorious ethernet.
Brent: You have no idea, Chris. I got here and there was a little bit,
Brent: you know, I'm driving a 30-year-old van,
Brent: so, and me being me, as you guys know, like,
Brent: maybe I'm a little behind the schedule that I was hoping for so i got
Brent: in this morning just in time and and
Brent: basically 10 minutes before they had to leave they had a thing
Brent: this morning and uh there's like these
Brent: beautiful little like handwritten notes all over the kitchen just like hey brent
Brent: we set up a custom wi-fi network for you the name is you know linux unplugged
Brent: with the episode number and you just connect to that if you need to there's
Brent: coffee over there and everything you need there's ethernet on the desk here if you wait wait can we.
Chris: Can we take a moment and appreciate that he stood up, a standalone AP titled
Chris: after the episode just for this? Love that.
Brent: Yeah, so if anyone in the area needs Wi-Fi, it's unplugged, 634,
Brent: and Brent leaves a password.
Chris: Yeah, act now before he tears it down.
Wes: Limited time only.
Brent: So I got to say, A, thank you for having me and reaching out and suggesting it.
Brent: And because of the reach, um, you reach out like perfectly in time when I was
Brent: sat down, you know, those last moments when you sit down and you're like,
Brent: okay, I need to leave like in a couple hours, but there's still a couple of
Brent: like final details I got to sort out.
Brent: And then I got a message from you just saying, Hey, you want to like stay at
Brent: my place maybe for Linux unplugged while you're here.
Brent: And it was just such perfect timing. And now that we're here,
Brent: it's working out beautifully. So thank you for having me in your home.
Mumble: It's a pleasure.
Chris: And I think you needed that, Brent, because it was a bit rocky,
Chris: right? It wasn't a super smooth start to the trip.
Brent: Well, I'm learning, Chris, that if you have a van like this,
Brent: which is, you know, adventures built in,
Brent: the first day or so of a trip is really just ironing out all the uncertainties
Brent: and the things you didn't plan for and the things that, you know,
Brent: are going to happen to you whether you want them to or not.
Brent: So I was something like three and a half hours into the trip and I stopped at
Brent: Canadian Tire, as you do, you know, just before you cross the U.S.
Brent: border and just to get a few little last-minute solar supplies.
Brent: And then I realized I ran into an issue.
Chris: Not a great start. Not a great start. And I love if you have headphones on,
Chris: you'll hear Cosmo in the background yelling at him like, what are you doing, idiot? Get in the car.
Brent: I have a photo basically of the moment when my mood changed drastically when
Brent: I realized I had locked both my sets of keys in the van.
Chris: With the two cats.
Brent: Oh, yeah. I'm outside looking into the window and the cats are like,
Brent: hey, how's it going? I haven't seen you in like 20 minutes.
Brent: And I'm like, guys, can you get the door for me?
Brent: just like paw at the door would you uh luckily
Brent: you know there are about five pretty easy ways to break into the van one of
Brent: them i taped up because that one seemed too easy but uh so i was able to get
Brent: in in like two minutes so a modern vehicle would have been like that would have
Brent: been the end of the day yeah but i gotta tell you an old van it's got quirks and perks easy.
Chris: Access wow so so then then i suppose it's just get down some distance right
Chris: get across the border which by the way, kind of a stressful thing to happen
Chris: right before you cross the U.S. border.
Brent: Tell me about it. Hey, you were worried about crossing the border because basically
Brent: like, this vehicle is registered in your name and I'm driving it across the
Brent: border on the complete other side of the continent.
Brent: How did you think it was going to go?
Chris: I wasn't sure. I figured because you got in it was probably going to be okay
Chris: getting back in since it's registered to a U.S.
Chris: citizen, but what I'm So I'm a little, it's like a little, they kind of have
Chris: to wonder a little bit, like the
Chris: names don't match, the residency doesn't match. So was it okay? Did it go?
Brent: Well, I wasn't too sure which question they would ask about the van,
Brent: because like the, you know, the van, it's.
Wes: There's a lot of questions you could ask.
Chris: Is that a meth lab?
Wes: How many cats you got in there?
Brent: Hey, meth lab. It's like one step up from a meth lab.
Chris: I'm kidding. I'm kidding.
Brent: Give me something. But it has an apocalyptic look to it, right?
Brent: and uh the fact that i pull up in this thing and also
Brent: i am canadian but i'm driving a vehicle register in the u.s is kind of so i
Brent: wondered what they were going to ask and basically asked me one question it
Brent: felt like a trivia question he said what is the state plate on this vehicle
Brent: like which state is it registered to,
Brent: That is not the question I expected. Of course, I knew the answer,
Brent: which means I probably didn't steal it.
Brent: But that was the only question he asked about the van. I was like,
Brent: oh, wow. A, I didn't expect that. B, that was really easy.
Chris: Well, there you go. Hot tip it, everybody. If you ever steal a vehicle,
Chris: memorize where the plates are.
Brent: Yeah, yeah, yeah, exactly. Both plates.
Chris: I mean, I'm damn impressed. You put down some serious miles.
Chris: So you must have slept once you got just inside the States?
Brent: Well, that would have been the reasonable thing to do. I decided since it was
Brent: A, beautiful out, and B, there was seemingly no traffic at all,
Brent: I thought this is my opportunity.
Brent: So I put down miles until I couldn't stay awake anymore, basically.
Chris: I know of nothing that motivates you more than proving Wes and I wrong. Yeah? Seriously.
Wes: He's going to be in Austin on Wednesday.
Chris: I know!
Brent: Like that was driving
Brent: day one of the trip and i'd say okay i locked myself out
Brent: of the van uh which isn't so good but
Brent: i made some distance so yeah success but
Brent: there are still like three to four
Brent: days left of this so anything can go wrong and well we'll see but uh man i gotta.
Brent: Tell you after sleeping for three hours in the middle of nowhere and then pulling
Brent: up to just a wonderful listener's place. It was just such a warm welcome.
Chris: Some real value. I mean, you know, think about, too, from a logistics standpoint,
Chris: Brett needs to be somewhere with reliable internet, reliable power.
Chris: You can't even get that from most Airbnbs and hotels these days.
Brent: That's so true.
Chris: Yeah. Best audience ever.
Brent: Yeah. With that said, I had a typical colonel also reach out and say,
Brent: Hey, I heard you bought a solar panel.
Brent: Like, if you're cruising by, I can help you install it or fix it or whatever.
Brent: So it didn't quite work out for timing yesterday to see each other.
Brent: But on the way back, I might stop in and don't tell Jeff, but I might get a
Brent: solar upgrade or like, you know, get some proper less jank, let's say. So we'll see.
Chris: That's exciting. Yeah. All right. Well, Wes and I, we hit the road tomorrow
Chris: morning and we have a little bit of distance to catch up, but we are in a lean
Chris: and mean and nimble vehicle.
Chris: And I'm familiar with the route. So I'm fairly, well, I'm not confident at all
Chris: that we'll catch up. But I think we'll make good time.
Wes: That is, you know, victory is a secondary target.
Chris: Right, right. I mean, maybe.
Wes: Linux, you know, Texas Linux.
Brent: You know, my weakness is, though, meeting up with listeners.
Brent: So I think if you convince enough listeners to be on my path,
Brent: you can really slow me down here. So that's maybe the angle you could take.
Chris: This is the way to go. That could happen to us as well. So we decided to build a tool.
Chris: And this is pretty great. It's built on top of something we've covered on the
Chris: show before, and we hope you'll take advantage of it over the next couple of weeks.
Chris: And we have an official Texas tracker. Two teams, Team Bigfoot. That's Wes and I.
Wes: That's right. Civic Northwest represent.
Chris: Here we go. And then, of course, you've got Team Moose.
Chris: That's Brent and the Cats. Brent's coming down the East Coast.
Chris: We're coming down the West Coast, both headed for Austin. And we wanted a way
Chris: where you could watch our progress, see our distance between each other and our distance to Austin.
Chris: And there's lots of ways to build this, but we wanted something that would work great for the show.
Chris: And so we needed a back end thing to kind of keep track of all of the logistics
Chris: and the travel data and something we could report to.
Chris: So we pulled out our old friend, the big D witch, Dara witch,
Chris: which you might recall automatically can track your daily life.
Chris: so that way you can go back in time and see everywhere you went and mark locations. It's pretty neat.
Chris: It's kind of like the Google Timeline feature.
Chris: Totally under your control and self-hosted.
Wes: Yeah, well, we've started first playing with this sometime around our trip to
Wes: Boston for Red Hat something.
Chris: That's right. Episode 614, Self-Hosted Location Tracking.
Chris: You can check that out, and we kind of go into more details about the project.
Chris: But it's something that we've kind of become familiar with.
Chris: I'm still using it every single day for my setup. I actually have it integrated with Home Assistant.
Chris: And so I'm just reporting my location to Home Assistant. and then Home Assistant
Chris: is relaying that to Darwich, which is really nice because it's just sort of one app on my phone.
Chris: And then you get location and maps with lines of where you've been and hotspots.
Chris: But maybe the most important part for our project, you get an API.
Chris: And once we realized there was an API that we could poke at,
Chris: well, I think Wes had a dream.
Chris: He had a dream and he built us a front end to sit on top of that API.
Wes: Yeah, well, maybe more like Vibe built.
Chris: Yeah. I mean, give yourself some credit. Like you got to have an understanding
Chris: of how to properly design these things.
Chris: Right. Like if I had vibed this, it would have been a total piece of crap. So let's, you know.
Wes: We'll get it. That's for later in the episode. yeah.
Chris: It is yeah it is.
Wes: But yeah but we have just like it's like a single page uh
Wes: html just has like plain um embedded css
Wes: and javascript uses leaflet js
Wes: to do map rendering and then
Wes: kind of just the main thing is that it's able to pull on the back end we have
Wes: a little tiny container that just runs and sinks down a set of points from the
Wes: big d which api and then we aggregate those and upload that to an S3 bucket and then...
Wes: The JavaScript and the web page
Wes: can just pull down the data from that and then just render on the map.
Chris: And the end result is you get a real-time location, roughly,
Chris: of where we are at, and you can see the path we have traveled.
Chris: So you know if we're in your neck of the woods. And then the thing that Wes
Chris: did that's a real kind of nice chef's kiss touch is he's automatically computed
Chris: the BitChat geohash for our current location.
Chris: And one of the things we're going to try to do is have BitChat running as we go down the road.
Chris: In theory, although I don't know if it works 100%, but in theory,
Chris: it will auto-switch locations as we go down the road.
Chris: And so if we're in your location, we'll be in your local chat room.
Chris: And you'll see the geohash of where we're at at the time listed on this tracker.
Chris: And it's nice. It's clean. It also has a time range filter. You can replay some data.
Chris: There's a couple of different view options in here.
Chris: I'd really like it if you checked it out and followed along as we make our way
Chris: down to Texas Linux Fest.
Chris: It's texastracker.jupiterbroadcasting.com.
Chris: texastracker.jupiterbroadcasting.com. It's pretty cool, Wes!
Wes: And if you'd like, it is open source over on our GitHub, jupiterbroadcasting.com
Wes: slash texastracker there.
Wes: And, you know, if you want to make it better, it was vibe-coded,
Wes: so surely there's lots that could be fixed.
Chris: We would love that because our stinking plan is we could kind of stand this up for every big trip.
Chris: You know, you relabel it the scale tracker or whatever it might be.
Chris: And we could use it from time to time and other people could use it for their
Chris: trips because what we're using to actually make it all work,
Chris: and we'll put a link to this in the show notes for you, is we're just running a client on our phone.
Chris: And there's a couple of options. Dara, which makes a client for iOS,
Chris: but you just need something that can report to the big D.
Chris: And so, Brent and the, well, anybody using an Android, I think should check
Chris: out GPS Logger, which is a really lightweight GPS logging application we've
Chris: actually talked about before.
Chris: And it can just log your travel location to a, you know, a GPX file on your local device.
Chris: Or it can report to an HTTP endpoint.
Wes: Yeah, there's a little custom configuration you have to do. but the plus side
Wes: of that is you can make it work with basically anything that can accept an HTTP
Wes: request of some kind or another.
Chris: So you can make it work with Darawich, which is what we're doing.
Chris: And so that's communicating to Darawich and the API we're using to build the website.
Chris: Anybody could do this. We're just doing a Docker Compose container for Darawich,
Chris: and then Wes's project is posted on GitHub. It's pretty small on the dependency side.
Chris: You need a way to store the file and all that kind of stuff.
Chris: you could label it your own thing and have at it or send us some,
Chris: you know, some fixes. This thing's pretty cool. And it's already using a bunch of great technology.
Chris: And the way we can do it is we can turn our tracker on and off if we need to.
Chris: So, you know, I'm going to start our tracker officially Monday after Wes and I are on the road.
Chris: So if you check this as you're listening and our location isn't on the map yet,
Chris: you only see Brent's location, then you're probably catching us just before we've hit the road.
Chris: But if you check later in the day, Monday, you'll see where we're at.
Chris: and you can follow along. You can see our geohash location so you can say hi
Chris: and pop in. And the whole stack is really great.
Chris: It's just such a cool set of technology from Darowich to the little thing you
Chris: vibe coded to the BitChats stack.
Wes: It's a lot of good little tools. I think that's what made it.
Chris: Yes.
Wes: Like, you know, we didn't have all week or anything to work on this.
Wes: We basically just threw it together after the show last week.
Chris: Yeah, in an evening.
Wes: And so there's a lot of good stuff, I think as primitives, otherwise we would not have been able to.
Chris: Yeah, and we've been playing it with the week and kind of testing on it. It's been great.
Chris: Also, if you're interested in BitChat, don't sleep on it. We covered this weeks
Chris: ago, and it's exploded since we've talked about it.
Chris: It's had some major rewrites, and there's a lot of now really nice tools built around it.
Chris: I'm going to link in the show notes to a guide, and I would really recommend
Chris: you give it a peruse, look at some of the tools they link to,
Chris: and try out BitChat. It's awesome, and in an emergency, it could be a life-saving tool.
Chris: But it's also perfect for events where everybody's kind of at a location.
Chris: And I'll just remind you, one of the neat things about BitChat,
Chris: no login required, and it can switch between relay over IP or over Bluetooth mesh.
Chris: So if you're at an event, everything can be just taken right there device to
Chris: device. It's really great for that kind of stuff.
Chris: So do go look at BitChat. you can find it at bitchat.free and I'll have a guide
Chris: to bitchat in the show notes as well as a couple other links in there once we
Chris: get to Austin we should be at geohash 9v6sb,
Chris: I don't know if we can put that in the show notes or not but 9v6sb I believe
Chris: is where we will be you pop in there and you chat with us it's going to be great,
Chris: so the next time you hear our voices we'll be in Austin, Texas from the next episode for 635,
Chris: better bring the gear.
Chris: 1Password.com slash unplugged. That's the number one password.com and it's unplugged
Chris: in the classic lowercase style.
Chris: Go take the first step to better security for your team by securing credentials
Chris: and protecting every application, even unmanaged shadow IT.
Chris: You want to go to 1Password.com slash unplugged to learn more.
Chris: So this is the thing that I think is a clear and present reality.
Chris: If you're in security or you're in IT, you already have a mountain of assets to begin with.
Chris: You've different devices, different identities for the staff,
Chris: all the different applications required to run the business. It's a lot.
Chris: And there's a lot of security risks just there. But now there's also all of
Chris: these additional different SaaS applications and different services that your
Chris: end users want to do their job better.
Chris: Well, you can conquer this mountain of security risks with 1Password Extended Access Management.
Chris: It's a real problem. Over half of IT pros that were surveyed say this is one
Chris: of their biggest challenges.
Chris: And that's where Trellica by 1Password can help you discover and understand
Chris: and learn about all of the apps your users are using, managed or not. Yeah, that's powerful.
Chris: That's Trelica by 1Password. It inventories everything at your company.
Chris: It has pre-populated app profiles, so you can kind of assess the risk right
Chris: there in a dashboard with a report.
Chris: It lets you manage and access who has what logins and also how you off-board
Chris: people when that time comes. And then ultimately, if you need,
Chris: it helps you optimize your spend.
Chris: So you can eliminate redundancies, make sure you're not spending for multiple
Chris: services for the same thing, for the same people, and ensure that your best
Chris: practices are being followed across every app your employees use.
Chris: Even shadow IT, which I used to be when I was a contractor, I'd plug in.
Chris: I'd get on the network. And the other thing I always saw companies struggle
Chris: with is a secure, standardized process and procedure to onboard or off-board employees.
Chris: You want to make sure you're also meeting compliance goals. That's where Trellica
Chris: by 1Password provides a complete solution for SaaS access governance.
Chris: And it's just one of the ways extended access management helps teams strengthen
Chris: compliance and security.
Chris: You know 1Password and their award-winning password manager and how important
Chris: good password hygiene is and how they've helped millions of users and hundreds
Chris: of thousands of businesses.
Chris: 1Password Extended Access Management builds on all of that and so much more.
Chris: They get regular third-party audits, they have the industry's largest bug bounty,
Chris: and they exceed the standards set by various authorities.
Chris: 1Password is always taking it up a notch. So take the first step to better security
Chris: for your team by securing credentials and protecting every application,
Chris: even the unmanaged shadow IT.
Chris: You need to go learn more at 1Password.com slash unplugged.
Chris: That is the number 1Password.com slash unplugged, all lowercase.
Chris: More information, and it's a great way to support the show.
Chris: 1password.com slash unplugged.
Brent: Well, come on in, my friends. We asked you to send us your config sins for the
Brent: last couple weeks, and you have. Thank you.
Brent: We have a massive batch of Homelab configs that we need to go through.
Brent: but where do we start?
Chris: Where do we start indeed? Yes. Well, I think we have, we've gone through some
Chris: of these and now we have more that have come in but we'll see if y'all like
Chris: this segment, let us know and we'll do another batch. But why don't we start with Zach?
Chris: He says, I've been listening for a few years now and I've learned a lot by listening to the show.
Chris: I heard you were looking for some NixOS configs to look over so I started using
Chris: Nix after listening to one of your podcasts and I've been slowly converting
Chris: all my servers to it this year.
Chris: I still have a few more servers or services to go, then I'll work on converting my laptop over to Nix.
Chris: The configs are pretty rough as I'm still trying to figure it all out.
Chris: So, Brentley, if you pull up his GitHub there and peruse through that, see what interests you.
Chris: Wes and I took a little look in there, and I'm curious to see what jumps out
Chris: at you just from an overall structure standpoint or interesting packages.
Chris: Wes, when we started this process, you're like, I want to see if anybody does
Chris: X. Do you remember what that was?
Wes: We had a few things we kind of discussed you know I'm always curious about like
Wes: how much do people define their own sets of tooling are they kind of using a
Wes: template or going their own way do they use special args or not the.
Chris: One that stuck out to me is like I wonder if anybody's doing any custom modules.
Wes: Stuff and.
Chris: Then we pulled up Zach's and it was right there.
Wes: Yeah right at the top.
Chris: So can you explain what a custom module is.
Wes: Well so you know how there's NixOS modules right so like you say services.vscode.enable.true
Wes: So if you'd like the VS Code service running in the background,
Wes: the web version, or whatever service that NixOS supports,
Wes: well, you can do that yourself, right?
Wes: So you can add so that the system now accepts new parameters that you can input and define.
Wes: And that's a way to, I mean, not only like enable or disable functionality,
Wes: but also pass things through your system and through your configuration.
Chris: And he has, like, so in here he has vscodeserver.nix. And so he's got a .nix
Chris: just for running vscode.
Chris: And he's defining, like, of course, enable the options module,
Chris: optional vscodeserver enabled, so that turns it on right there.
Wes: Yeah, so in this case, right, so in the normal setup, you just do,
Wes: like, hey, tell me I want to run the vscodeserver.
Wes: And then here you've got, like, extra wrapper stuff you can do around to apply,
Wes: like, oh, here's a workaround for something that I need to work around.
Wes: I know I want these initials like enabling Nix LD here to make it so that like
Wes: random extensions that have their own binaries might have a better chance of working.
Chris: So that's, that's a nice little thing because sometimes those are edge cases
Chris: with some of these apps on Nix you do need to solve.
Chris: And so he solved it once, he put it in its own file, and then any system he
Chris: wants to use that on, he's got that, that LD library problem solved now.
Wes: And this is where it's kind of interesting because like Nix provides a lot of
Wes: ways to structure things.
Wes: And so one method we'll see, I think later on is you can kind of just have like,
Wes: you can include modules or not just by whether you include the file or not,
Wes: or you can go this route where you sort of define it and you gate it behind
Wes: like actual first class config options.
Wes: So I don't know if I would call that rough shape.
Chris: Also kind of a common approach we saw, but managing secrets,
Chris: he's got that taken care of here.
Wes: Yeah. Using age nix. I think we see both swaps and age nix happening here.
Wes: It's kind of fun to see how people do handle secrets or if they just,
Wes: you know, some aren't addressed in the repo at all.
Chris: We do have a couple of small nitpicks if we were going to dig in there.
Chris: We did a little review, and one of the things that stood out was you could review
Chris: your domains, your ports, your GitLab image tags, and your registry wiring.
Chris: They all are repeated across multiple modules, so you could maybe centralize
Chris: that in one common NICS file so you're not having to change those names everywhere
Chris: in all those different files.
Chris: It might make it easier for future upgrades, less typos. It's probably something
Chris: I would screw up if I had to change something across six or so files.
Chris: did we have any other nitpicks with uh.
Wes: No, I don't think so. I mean, it seems like a lean, mean config to me.
Chris: One thing the LLM called out is that maybe he could look at changing permissions
Chris: for some of the files he does do with secret management, but we didn't really think it was a big deal.
Chris: And it also dinged him, again, on Nix,
Chris: not a big deal, but maybe on other distributions this would make sense.
Chris: The LLM dinged him for using a mix of Docker and Podman.
Chris: We don't think that's a real problem, but it thought it was weird.
Wes: I think it was interesting just to note that, one, you can do that,
Wes: and two, it makes me wonder, what's the reasoning behind that?
Wes: Not that it's not legitimate, but just what drove that choice.
Chris: Right. You can see the care and the love. So he has this hosted on GitLab,
Chris: and you see on the readme, he has essentially instructions for himself if he
Chris: ever needs to get this up and running again. I love that.
Brent: I mean, obviously a good choice, and the readme was updated,
Brent: what, 21 hours ago? so either that's for our benefit or for their benefit but
Brent: everyone's benefiting that's for sure.
Wes: Also I think some others will use this too but using NVF which I hadn't seen
Wes: before is a modular extensible distro agnostic NeoVim configuration framework for Nix and NixOS.
Chris: Yeah that could be a good little pick we'll have a link to that in the show
Chris: notes if you want to check that out.
Wes: Also using Home Manager and Disco very nice.
Chris: Yeah to get everything laid out on the disk And a lot of home manager use In
Chris: the audience A lot of home manager Overall though pretty good config,
Chris: Thank you, Zach. Thank you, Zach. Sutterman boosted in his config with 5,555 sats.
Chris: I've never boosted before, but you asked for a Nix config, so I had to share mine.
Chris: It's an impermanent setup for all my machines, complete with Home Manager,
Chris: Disco, and Hyperland. Secrets are encrypted via...
Wes: AgentX.
Chris: AgentX. I always want to say age and X, using a key derived from my cold wallet's seed words and BIP85.
Chris: Okay, that's cool. My SSH keys and age identities are deterministically delivered
Chris: from this key, meaning I can bootstrap a host scanning a QR code on my cold card Q.
Chris: And if the key gets compromised, I can rekey everything by picking a different
Chris: derivation index number.
Brent: Wow.
Wes: Fancy. that's so nerdy and great that.
Chris: Is that really is also so open this one up Brent I mean it's a beaut,
Chris: some of these really give me like the most FOMO ever like I just I could do
Chris: so much better on my readme this is another really nice readme he's taking advantage of blueprint here.
Wes: Yeah that's a project from numtide a standard folder structure for Nix projects
Wes: yeah so it's like an opinionated library and map standard folder structure to
Wes: flake output so like it kind of handles automatically you just put files in
Wes: folders and then it'll make sure those get exported out of the flake automatically.
Chris: Sutterman's also accomplished something that I'm still struggling to fully pull
Chris: off and that is a custom ISO for the setup a custom ISO to get the setup going from scratch,
Chris: mine is still kind of get a base system going and then build my setup on top
Chris: of that he's also using impermanence what does he what do you mean impermanence yeah.
Wes: So impermanent is impermanence is that setup that basically there's a very you
Wes: can use like temp fs you can use rollbacks on something like butter fs there's
Wes: various mechanisms but essentially it's where you wipe your uh file system every reboot you like.
Chris: Don't leave stuff hanging.
Wes: Around that isn't controlled somehow by nix.
Chris: Right boy it's there's a lot of these terms i also was really impressed with
Chris: a very slick server setup he has where he's configured automatic backups and
Chris: he's mounting Backblaze into a common spot and then backing systems up to it,
Chris: Really slick. Really well done. I think anybody that's curious about a setup
Chris: like that should check out Sutterman's link in the show notes for that.
Chris: Just going through there and perusing that section.
Chris: It's really nice. I was really impressed by that. I know I'm supposed to be
Chris: criticizing, but it, this is one of the cleanest configs that was sent into
Chris: the show in terms of readability.
Wes: I mean, just very well structured, very clearly thoughtfully put together.
Chris: Yeah yeah i want it i wanted to be really critical
Chris: but it's kind of beautiful it's
Chris: kind of like when it's readable it's so it's so intelligently structured it's
Chris: clean the way the backups work like for example uh he's got like some stuff
Chris: in here for tail scale to make sure some unused routes are cleaned up after
Chris: the backups like he's just really got it dialed in boys also.
Wes: Some custom nix like library code of helper functions and other stuff in here
Wes: like some custom um gen adders to first convert provided paths or attributes
Wes: to a list that seems nice or even like a nix module here that has um attribute
Wes: set describing my domains and ip addresses.
Chris: Neat good idea a lot of these setups are multi-machine
Chris: a lot of these setups are multi-machine they got home lab
Chris: servers they've got desktops and laptops some people
Chris: even have surface books uh but before we before
Chris: we get off of setterman's pretty impressive setup i noticed a tool he was using
Chris: in here that i think i need to take advantage of he has um nick's flat pack
Chris: and it's declaratively installing flat packs this as i become a larger and larger
Chris: user of flat packs this is really something how.
Wes: Many flat packs again.
Chris: Yes you know this embarrasses you're making me say it in the show it's.
Brent: Like as many as i have tabs open.
Chris: It's 59 ish i think 59 flat packs
Chris: it takes a long time to update all those over starlink i'll
Chris: just say that but you know i try stuff out for the show and i
Chris: also i kind of i kind of go with a base minimal well that's
Chris: not true either anymore but i have too many flat packs
Chris: uh and so one of the issues is i've kind of come
Chris: to depend like telegram is a flat pack i think i'm
Chris: using steam as a flat pack now maybe not so i
Chris: need something and this declared a flat pack manager essentially is just you
Chris: define everything you want installed and you can do versions and all that and
Chris: then when you stand up a system you just get those flat packs from flat hub
Chris: installed really nice and one of the things i when i went through i was like
Chris: oh i gotta do that some custom stuff in here too,
Chris: also a nice slick implementation of the r stack if you know what i mean for
Chris: backing up your media nice little nix based implementation of the r stack there
Chris: not the full full stack but the solid A.
Wes: Lot of good components.
Chris: Yeah. So I really had no complaints.
Chris: The LLM dinged him on a mix of SOPs and...
Wes: Aged nicks.
Chris: But again, I don't know if we really would ding him on that.
Chris: It does ding him on a mix of a secret manager.
Wes: I think that it just says it's a testament to how good it is.
Wes: Sophia thinks to Chris says.
Chris: Yeah, I really wanted something. Brent, do you have anything?
Chris: It's beautiful, right? It's got a nice readme. It's structured.
Chris: Even the config files themselves are clean.
Brent: I know. I feel like even I could learn something from this. There's a little
Brent: note at the bottom of the readme here that I think might explain why.
Brent: It says, when trying to figure out how to do something, examples are almost always best in NixOS.
Brent: Make use of GitHub's search with the code language filter to find examples from
Brent: other Nix users' personal configurations.
Brent: And it gives a nice little handy link for, like, you know, an NGINX example.
Wes: This is like a step up. Not only do you get a great example of an actual working
Wes: config, you get tips for how to find more.
Chris: Other examples, yeah. I've heard that is a great way to do it,
Chris: too. I do it every now and then, but I forget.
Wes: Okay, so next up, huh? We got Adam.
Chris: Yeah, yeah, tell me about Adam.
Wes: I reverse-engineered the past
Wes: hostname into Flake as parameter setup from Wimpy's Nix configs. Nice.
Chris: All right.
Wes: I'm particularly proud of my install instructions in the readme.
Wes: Just boot into the Nix installer, open terminal, and copy and paste just two
Wes: commands to get the disks partitioned with Disco and get the latest configurations installed.
Wes: I even have an alternate install path for VMs that have less than 5 gigs of RAM.
Wes: I'm a puppet refugee that just couldn't stand not having strong declarative
Wes: configurations for my systems.
Wes: NixOS fit the bill for me, and I haven't looked back.
Chris: Again, a very well-structured readme. It starts with, this is my Flake-enabled
Chris: NixOS configuration repository. It uses Home Manager, but not extensively.
Chris: I've only implemented just enough from tutorials to get it to work.
Chris: And then he's got a broken down by section, including how to get it working on a new host.
Chris: Here's the URLs you need to pull down. Here's the commands to get it installed.
Chris: Here's how to do system secrets.
Chris: The kind of stuff that when you only do something once or twice a year,
Chris: or maybe once a year or every couple of years, really nice to have it written down.
Chris: So he gets immediately good marks right there just for a fantastic readme.
Wes: And a nice-looking flaked.nix as he was talking about here.
Wes: There's some helpers, like this make system function that has a hostname parameter
Wes: to make it easy to build systems and pass the hostname in and make it nice and
Wes: clean, as well as a bundle of all your inputs.
Wes: So if you are doing the special arg stuff, you can pass that through in a clean way.
Chris: There's also another one of these, I got to do it this way now.
Chris: Now that I've seen this working functionally, I can't go back.
Chris: And I'm going further down the Git rabbit hole. So he is using branches as he builds out new configs.
Chris: And as we were reviewing his config, Adam's config, we saw him very recently
Chris: committing things to a new branch.
Chris: I think he was building out something for Jellyfin trying to get no, it was ersatz.
Wes: It was ersatz.
Chris: He was trying to get ersatz to have hardware acceleration which I lit up when I saw that.
Chris: I was so excited to see him deploy an ersatz. I'm very, very,
Chris: very excited because it's such a great app. And so...
Chris: Basically, can you convince me why I should be building out my future configs
Chris: this way, especially on my home server?
Chris: Because this really does seem
Chris: like a superior way to test something out without breaking production.
Wes: Well, it's using the power to Git now that we've got you using Git. Yeah.
Wes: You know, when Git came around, unlike some of the past systems,
Wes: it made working with and using branches cheap and easy to do.
Wes: And so it lets you have a separate place where you can freely make changes,
Wes: vibe to your heart's content.
Wes: And then at the end of the day, you can pick and choose which things you want
Wes: to actually keep and get a really clean diff view of what's changed between
Wes: you and your base system.
Wes: And if you want to work on multiple things at the same time, you can do that too.
Chris: When you say it makes it cheap and easy to do branches, what do you mean?
Wes: Like you just don't have to worry about it. Make as many branches as you want.
Chris: Oh, because it's just managing it all for you. You don't have to do the math. Yep. Okay.
Wes: And it's not an expensive process for the way Git works internally.
Chris: So that was really cool. It was neat to see him testing that out as a way to
Chris: build out his new config. And then I imagine he just merges it when it's time to roll.
Wes: Yeah, exactly. Plus, it then opens you up to all of the especially modern Forge
Wes: workflows, right, where you can have PRs or MRs and do review and take a look
Wes: at things or trigger CI tests if you want to run tests or...
Chris: This would be a great way to manage Home Assistant.
Chris: yeah i know that smile what i didn't do anything smiles i'm gonna get him to
Chris: drop dockers what that smile was that's what that smile was well we'll see you
Chris: do a lot you know see the flatback count um i.
Wes: Was gonna what was i gonna say i don't know.
Chris: Special he's got some special args in here did we mention that did we want to
Chris: go over that we talked about the oh also the r suite in here yeah.
Wes: I was gonna say there's just the structure's really nice in that there's a ton
Wes: of just explicit modules that are all set aside so this is i think where we
Wes: want to take your config which we'll touch on later.
Chris: Okay right.
Wes: It's like pretty much all the functionality rather than being in like directly
Wes: in the host config it's all implemented in different modules.
Chris: Yeah that is great and.
Wes: Then the various hosts can just import those modules.
Chris: I i had a bit of feedback we don't need to spend a lot of time
Chris: on this but i noticed uh those of you that do have
Chris: the r suite nobody has their own local indexer nzb
Chris: hydra or prowler something like that might be worth considering um
Chris: nobody had that in their stack oh also i i
Chris: thought this was hilarious adam has a bonker
Chris: setup oh brand i don't know if you can find this if you
Chris: look in his uh repository he has a bonker setup
Chris: to get world of warcraft working no and just looking
Chris: through it i'm kind of picturing what he does and i'm
Chris: thinking he's got he's got like a a disc
Chris: somewhere or a partition somewhere with a massive world
Chris: of warcraft installation that's been patched and all of
Chris: that and then he kind of like mounts it in and
Chris: then launches world of warcraft which probably points at
Chris: that that path and then he plays the game i don't.
Chris: Know if he uses it to cross machines because back in my day when wow was brand
Chris: new i did that i had i had a central storage location and then i would mount
Chris: it on various places so that way i wouldn't have to patch and all of that stuff
Chris: every single time i don't know if that still works or not but it was pretty
Chris: funny to see a world of warcraft module in its configuration,
Chris: and then to see such a technical approach to setting up World of Warcraft.
Brent: I also find it interesting how the World of Warcraft module has options ZFS
Brent: util in there because you do need that for your gaming, right?
Chris: Yeah, well, I mean, you got to have your World of Warcraft data on ZFS. You don't want BitRot.
Wes: Adam, you should write back to us or something sometime. I'd be curious.
Wes: I'll have to follow up in one way or another because if you get the acceleration
Wes: stuff working with our sets, I would definitely want to pull that upstream too.
Chris: Yeah, for sure.
Brent: I did notice two interesting things that stood out for me, at least,
Brent: from what I can tell from state version here.
Brent: I've been using this at least since 2023, so that's a good long while.
Chris: Yeah.
Brent: But the other thing is, in the list of hosts, I noticed one here called Boomer Nix OS.
Brent: I'm just curious, is that like your family deployments?
Brent: You know, you do it for your parents, and that's the one you put on their machines?
Brent: Because I know my parents can use Nix OS.
Chris: I said the same exact thing when I saw the boomer OS or the boomer config I
Chris: thought oh this is like this is like a family but now I think one of his machines
Chris: is named boomer oh sure he's got it yeah,
Chris: But I had the same thought, like, oh, a special config of Nix for my boomer
Chris: folks, that's actually a great idea.
Chris: I mean, I do it for my kids. Why not do it for my folks?
Brent: The boomer does play World of Warcraft, just saying.
Chris: That was another really good one that put me to shame, Adam.
Chris: Thank you for sending that in.
Chris: I think it's Kieran, I think maybe, or Kyron came in.
Chris: He says, I have a Nix, or they have a Nix configuration that hopefully you can
Chris: rip apart. It does need some improvement.
Chris: I made my dots about a year ago and have been running them up until about a
Chris: month ago on Hyperland with my framework 13.
Chris: Although it randomly died the other day, I needed one for school.
Chris: So now I'm begrudgingly on Darwin, in other words, macOS.
Chris: And I do manage as many servers as I can and as well as my MacBook with it.
Chris: So far, it's been rock solid for me. And I love learning how Nix works.
Chris: So we took a look at this. We hated it.
Chris: I'm just teasing. We didn't hate it.
Wes: It's a beautiful setup. I love the screenshot.
Chris: Yeah.
Wes: You've been eyeing a lot of this screenshot for a while.
Chris: I like that Waybar. That's a good Waybar setup.
Chris: I think it's a little bit more elegant than mine. And I also appreciate a nice layout snapshot.
Chris: I've attempted to do something similar just right there.
Chris: And then, as I've noted with some of these other ones, some one-liners so you
Chris: can just get this thing going and get it set up so you can get right back to your config.
Wes: I appreciate the exposition. and there's a big caution bar at the top that says
Wes: these dots are highly prone to change or breakage.
Wes: And then there's a crossed out thing that says like, I'm not an expert.
Wes: I'm just kind of figuring this out.
Chris: That's crossed out now.
Wes: And it says after 284 successful days of these dots being in constant operation,
Wes: many, many rebuilds and 364 commits, these dots have been rock solid and I have no complaints.
Chris: I think that's great.
Brent: Very nice.
Chris: Yeah. There was, everybody organizes these differently.
Chris: And so that's always interesting because it's kind of like you can get a little
Chris: bit of personality traits when you look at these.
Chris: And one that stood out to me is Kieran has a aesthetics module where they configure their aesthetics.
Wes: It's a nice way to break it out.
Chris: I love the Hyperland module. I'm going to steal some ideas from that.
Chris: And then I don't know why this is funny to me but a dedicated wallpaper Wallpapers.nicks,
Chris: which just has like a bunch of great wallpapers to find in it.
Chris: That to me, I don't know why.
Wes: Why are we doing that?
Chris: Yeah. First, I was like, that's so silly. You're overthinking it.
Chris: And then I thought, actually-
Chris: You know, there's probably about 10, 15 wallpapers I really like that I have. Why not?
Wes: And what, you don't do declarative wallpapers, Chris? Jeez, man.
Brent: Go with the times.
Wes: I got real interested because I've been using that Crush tool,
Wes: the like vibe coding little 2E thing more just because it's really convenient.
Wes: I don't, you need it a ton, but you know, when I want it, it's handy,
Wes: especially because it works with Open Router.
Wes: But like kind of like reconfiguring it sometimes can be a bit of a pain.
Wes: And it turns out there's, in these dots, we've got a HomeManager config for Crush.
Chris: Yeah.
Wes: And that seems like something I might want to copy.
Chris: Do you think that might pull you into HomeManager?
Wes: Well, it might. We'll see. That's tempting.
Chris: Yeah. There's so much HomeManager use here. It's a little rough.
Chris: It's making me feel like I'm missing out. But I'm also curious if I could do
Chris: without it. The Crush config is pretty tempting, though.
Chris: All right. So let's talk about just a couple more here.
Chris: 40Deuce came in. He sent in a boost with 42,000 sats, and we captured this last
Chris: week, but I think it maybe came in after the show?
Wes: No, it's in the boosts.
Chris: Oh, it came in this week?
Wes: No, it was in last week's boosts.
Chris: I can't keep it straight. I'm sorry. But anyways, so he came in with 42,000
Chris: sats and said, you asked for it, you got it, my Nix config. I've shared this
Chris: before, but it's come a long way.
Chris: This is my Nix OS and Home Manager flake that manages multiple hosts with many
Chris: shared modules and a few host-specific modules.
Chris: It has a pretty nice usable configs for Hyperland, Neary, Sway,
Chris: River, and Wayfire compositors, as well as enabling Plasma and the Cosmic desktop.
Chris: One recent change you might appreciate, I abstracted out all the usernames to
Chris: a let statement in myflake.nix to make it easy for another user trying myflake
Chris: to quickly change the username in just one place.
Wes: That way you might have a chance to try it, so you can slam Chris F in there.
Chris: I mean, yeah, I guess I would just put Chris F. in there if I were you,
Chris: 40 Deuce, but I guess that's fine.
Brent: Everyone is Chris F.
Chris: Um, what I thought was hilarious about this config is 40deuce has obviously
Chris: spent some time getting FireWire devices working and FireWire audio devices.
Chris: And he has an audio prod dot nix.
Wes: Yeah, there's a lot of good audio config in here. I like that.
Chris: Real-time. Real-time's in here. And some kernel parameters to make FireWire
Chris: behave appropriately, as well as some rules to make it work with the audio subsystem and with UDev.
Chris: And then disabling some conflicting subsystems, enabling the appropriate pipewire
Chris: subsystems and the appropriate pipewire latency settings as well for really quick real-time audio.
Chris: Enabling Wireplumber and hooking it up with FireWire support.
Chris: I mean, everything. It took so much work. And then again, 40Deuce has a beautiful
Chris: syntax structure to the point where I thought this almost looks machine generated.
Chris: It's so clean. It's so consistent.
Chris: But then when you read the comments, they're clearly written by a human.
Wes: Although, much like you were learning about, you know, development stuff from
Wes: the branches and another one, this one you noticed that there was an agent.md.
Chris: Yes. So there may be some LLM going on here.
Wes: Either way, the end result is lovely.
Chris: It is very clean, very readable. So if that was an LLM, I should use that one.
Wes: Yeah, I think, right? We should offer like a bounty. Do you want to clean up Chris's config?
Chris: We'll shoot you some sats. Go look at my Hypervibe config and I'll shoot you
Chris: some sats if you want to clean it up because I would love it to be as clean as yours.
Chris: So the AgentsMD is interesting. Pretty simple layout, right?
Chris: Not too confusing. Not overdone. Sometimes people get a little too complicated.
Wes: Yeah, true.
Chris: Uh, individual hosts only is nice.
Chris: I like the way bar again here. This is another really nice way bar config.
Chris: Um, too much home manager, maybe one of the cleanest configs overall sent in. I don't know.
Wes: I like the thoughtful read me in terms of like folks actually trying it,
Wes: you know, that wasn't, I mean, many of them didn't have that,
Wes: but there's especially taken to another degree with this one.
Chris: A lot of hyperland. I mean, hyper, he's got a lot. He's got cosmic. He's got plasma.
Wes: Neary.
Chris: Yeah, you can switch between them depending on which one you want to enable, which is neat.
Chris: But all the screenshots were Hyperland. A lot of the default configs are Hyperland.
Chris: I guess I'm late. I'm late. Yeah.
Chris: It's like, welcome, welcome. Been here for a minute. It's funny. A lot of setup.
Chris: Really nice. A lot of intention has gone into these. People have really built something pretty cool.
Chris: Do we have any criticism for Deuce here? Do we have anything we want to lob?
Chris: Brent, you got any criticism? We got to come up with something.
Chris: We're being way too nice here.
Brent: I got a softball if you need one.
Chris: Yeah, give me something.
Brent: In the screenshot, is that pipes in the background? I think it might be pipes
Brent: or snakes or something. What's going on there?
Chris: Come on. Yeah, and you know what? Not a single Fast Fetch.
Chris: And is it really a Hyperland desktop screenshot without a Fast Fetch?
Chris: So dinging them for no Fast Fetch.
Brent: The Fast Fetch is in the Matrix code there. I think you're missing that.
Chris: Oh, okay. I love I do kind of like the pipes though so I like the pipes I think
Chris: I'll give them credit for that I'm going to ding them,
Chris: oh god i gotta have something here there's got to be something i can think the readme is too long.
Brent: You know what i did notice in the readme that i'm seeing as a bit of a theme
Brent: here uh there's one line that says uh i'm still very much learning next along
Brent: with many other things so please leave feedback on any bugs best practices corrections
Brent: or appreciation as indicated a lot of people saying like hey i'm just learning
Brent: so here you go and have fun she's.
Chris: I'm going to need to know what 40 Deuce is doing with Firewire.
Chris: I got to know what's going on. Why are you using so much Firewire audio?
Chris: What are you doing? It's 2025. What's your plan for the future?
Wes: Can you get us some Firewire?
Chris: Yeah, I'm also kind of envious.
Chris: Let us know, okay? Okay, you ready for the last couple here, boys?
Wes: Yeah.
Chris: All right, we're rounding it out now. Team Toronto, a.k.a. Brad,
Chris: came in with 20,000 sats, and he says, In the past 12 months,
Chris: I've gone from Windows to Mint to Ubuntu, now to Nix OS.
Chris: Linux Unplugged has been the best and the worst influence.
Brent: It is for us, too.
Chris: So he's coming in hot here, boys. He's got a couple of interesting things,
Chris: Wes. I noticed you noted maybe a custom library here.
Wes: Yeah, that always stands out. You know, if you're writing a bunch of Nix code
Wes: that you're using, reusing throughout, there's some fancy stuff.
Wes: It's list importable subders, make system, list Nix files. I like it.
Chris: Okay, so he's got modules. So his modules are broken out into hardware,
Chris: programs, and services. Let's go look at services here.
Chris: Oh, yeah, Restic, rsync.
Wes: Secrets with SOPs.
Chris: Nice. Scrutiny collector.nix? What is this? Restic backup. Oh,
Chris: something for Restic. I see.
Wes: We were also noticing various Samba mounts going on.
Chris: Yep.
Wes: In a nice way, I think, that you liked.
Chris: Yep, yep. I'm always a fan of doing Samba nice and clean and just having a Samba config there.
Chris: Also, I think this is smart. More people should consider a separate printer
Chris: config. We didn't see that a lot. But do all your systems really need to print?
Chris: Why not just have that as an optional feature on the systems that need it?
Chris: Some of you could just pull in.
Chris: Seeing, you know, that kind of stuff also to me is just kind of thinking ahead,
Chris: like, oh, for a linear system, I don't need it. I don't need it.
Chris: Nice, simple, straightforward config, Brad. I think it could use a little more
Chris: love in the readme department, and explain what's going on and maybe give yourself
Chris: some tips for future you to get going.
Chris: I do like to see some secret management. Got to give them credit there.
Wes: Absolutely.
Chris: And we do like to see you getting fancy with the Samba mounts.
Chris: All right, before we tear mine apart, the last one of the batch for this round is Monty.
Chris: He came in with 6,666 sats, which a row of ducks for each one of the repos, he says, I'm sharing.
Chris: First is my HomeLab Ansible config, which was the only Ansible submission,
Chris: which is totally fine, of the show. Next is my Nix config, which is a multi-host
Chris: for a few parts of the home lab and growing, as well as the family PCs here.
Chris: And finally, a relatively new project that spins up a Nix LXC container on my Proxmox node.
Chris: Might seem like an odd combination, but I actually dig the declarative config
Chris: and easy update of Nix and the portability and isolation of LXC.
Chris: I'm no expert, so be gentle with me.
Chris: Yeah, yeah. All right. Okay. Okay, so we liked a lot what we saw here.
Chris: Lots of commits, clearly well used, lots of functionality.
Chris: It is a little bit all over the place. Did you have any notes on the ANSW? Oh, God, yeah, we did.
Wes: No, it was mostly that it was just, you know, it was a lot of YAML for us.
Chris: It's a lot of YAML that references YAML that references YAML that then just
Chris: executes a command. And I'm not exaggerating.
Chris: And it's just what it is. And when you go through, dear listener,
Chris: take the exercise yourself.
Chris: go to the show notes, peruse through everybody's Nix configs,
Chris: and then go check out the Ansible config.
Chris: And tell me if it isn't three or four layers of turtles before you actually get to what you want.
Chris: It's just a totally different level of abstraction.
Chris: You know, Monty is transitioning, so I'm not going to ding him too much.
Wes: Nice docs, definitely. Also a nice JustFile setup.
Chris: What's going on there with the JustFile? Not everybody has a JustFile.
Chris: A couple of people did. Why is he using a JustFile?
Wes: I mean, that just kind of vibe, right? Maybe it was a good way to provide easy
Wes: access to run various commands.
Chris: Yeah, because he's got a bunch of stuff in there. Like, he's got Nick's flake check mapped to NFC.
Chris: He's got a bunch of, like, longer commands that also have host variables in
Chris: them, mapped to like three-letter words.
Wes: Yeah, and like, you know, here's your Ansible playbook, bootstrap,
Wes: just as AP bootstrap. That's nice, right?
Chris: Yeah, and it automatically, dynamically, it figures out the host name and all
Chris: that kind of stuff. So it's pretty sweet.
Chris: I mean, Monty's doing some clever stuff there that I didn't really see anybody else doing.
Chris: So some of the other folks that send in your configs, you might want to go check
Chris: out. Again, we see secrets management with SOPs again this time.
Wes: Mm-hmm. In Monty's next config, some nice auto-upgrading going on. I like that.
Chris: I, again, love the naming. One of his host configs is Omnitools.
Chris: Omnitools. I don't know what he's doing over in Omnitools, but I like it.
Chris: It's a pretty simple config over there, but the naming of these things are always funny.
Wes: And then this NXC scripts, like this Proxmox plus Nix thing, I like it.
Wes: It combines the declarative configuration power of NixOS with the portability
Wes: and isolation benefits of Linux containers, LXC.
Wes: You can clone this repository and use the included examples or point the scripts
Wes: to your own Nix configuration repository to deploy and update your custom NXCs.
Wes: It's nice.
Chris: I was also impressed with the fancy backup setup, the auto-upgrade setup,
Chris: and the dope tailscale setup, which is one of the cooler ones we'd seen.
Chris: There's a lot going on in there.
Wes: I'm impressed that there's all, you know, all like the expansive,
Wes: well-used Ansible configuration plus now nix configs as well and you're doing this lxc stuff.
Chris: Yeah we need a good criticism though and that might be you need to get all under
Chris: one house or something you know pick a horse i don't know can you think of a criticism yeah.
Wes: All right we can go with that.
Chris: Pick a horse yeah that's it there you go we got tough there for a second but
Chris: maybe we could be easy on this next one maybe we could go gentle here for a minute why.
Brent: Is that why would we change our tune chris.
Chris: Uh So I thought I would submit my config for review, and as you know,
Chris: this is called Hypervibe because it's a riced-up Hyperland desktop built on
Chris: top of NixOS that I vibed together. And, well...
Chris: It's not like go-to-town ready. I'll just say that. It's not something you want
Chris: to go to town in, but it's close.
Brent: Wes, you had a go at this recently, trying to install it live on the show. How was that?
Wes: It did not end well, if I recall. I try not. I sort of blanked that out for some reason.
Chris: I see my screenshot isn't loading anymore in my readme, so I'm going to ding me for that.
Wes: Yeah, bad readme.
Chris: I do have a screenshot, but I just think maybe it got taken out.
Chris: I mean, I do really enjoy the desktop.
Wes: Uncontrolled vibe usage so.
Chris: Lay it on wes what's the worst give me like the you know.
Wes: I don't know the bad the good the ugly kind of there's a lot of scripts folders
Wes: you just there's a lot of scripts folders sort of just strewn about for some reason yeah.
Chris: A lot of activation scripts.
Wes: Yeah there's also a lot of duplication like uh there's just between them like
Wes: you have a lot of copied packages and which is can be totally fine like there's what.
Chris: Do you mean what do you mean like i've got the same package listed twice or something.
Wes: Well that yeah that's been somewhat cleaned up i think there's probably
Wes: still a couple of those but then just between like you
Wes: have sort of um you've started using some shared modules like we saw nice implementations
Wes: today yeah yeah but it's sort of like halfway done so you have like a packages
Wes: like an area where in theory you'd have packages but there's not that many packages
Wes: there but then in each of your hosts they have a whole bunch of packages in there and.
Chris: A lot of the same.
Wes: Yeah across the two that's very true,
Wes: And then, so it's kind of unclear how far that's been adopted in terms of modularity.
Chris: That wouldn't be too bad to clean up.
Wes: And then in what you did do, you put it under kind of a weird,
Wes: actually someone opened an issue about this.
Chris: Oh, really?
Wes: Yeah.
Chris: Okay.
Wes: Do you have 10 issues already?
Chris: Oh my God.
Wes: I don't know if you've been attending.
Chris: Oh, T-Cario.
Wes: Okay, great.
Chris: I haven't been looking. I really should get back to it. I'm sure I'll get right on that.
Wes: T-Cario was so polite too. You have Nix OS modules that can be reused in other
Wes: people's system configs. This is awesome.
Wes: But then continues to go on to point out some of the problems.
Wes: The current namespace name of shared may not be highly likely to conflict,
Wes: but it's also not specific to this project.
Wes: I think it would make more sense to name these under Hypervibe,
Wes: so just kind of changing the namespacing being used for the modules, which is a great idea.
Chris: Sam H. contributed a pull request of how I could add options for different users.
Wes: Hey, there we go. you.
Chris: And i should go through this and merge some of these west because some of this
Chris: is probably with a few tweaks actually pretty usable.
Wes: And then there's like the searching and replacing and copying and like basically
Wes: the giant activation script that yeah sort of is brutal yeah and in place of
Wes: maybe something like home manager yeah.
Chris: It is my it is my hack around home manager i will admit i'm leaning heavily
Chris: on a few scripts to do that.
Wes: So it's not yet and you kind of touched on that with the users it's not yet
Wes: like portable right it's still kind of like really specific to your config it's
Wes: getting there and we're gonna get it there but and then um yeah what else well
Wes: you you got sudo set up without a password you don't have a firewall hell yeah
Wes: buddy you're living pretty dangerously i.
Chris: Love it i don't i don't need i don't need no stinking password to use sudo.
Wes: And then i think this one came from the uh lm noting just that you know your
Wes: gpu temp setup it depends on amd yeah.
Chris: Yeah yeah i need a way to abstract out the gpu temperature stuff.
Wes: So maybe we can you know list that up like brittle weight bar setup yeah.
Chris: Brittle weight bar set up,
Chris: So it's a mess, too many scripts, duplication, need to modularize the user stuff,
Chris: reduce dupe apps across machine configs and put them in a shared config.
Wes: We'll just start fresh.
Chris: Yeah, and then I've got nine poll requests. Nine poll requests,
Chris: all of which actually seem like a pretty good idea.
Chris: Who knew the distro would be so much work?
Brent: Adversaries here has a criticism you'd like to share.
Wes: Oh, good.
Chris: I got one too.
Brent: Actually.
Chris: Okay excellent.
Mumble: You know what you really need chris is a ci config that way every time you commit
Mumble: and push it just resets all your hosts to whatever broken config you have.
Chris: I do i do you're right i do because like i do something on one machine oh yeah
Chris: i gotta go update over here now you're right i should just push it all out and
Chris: break all of them at once that's a good that's a great tip what's yours brent.
Brent: Well i'm just gonna lean in with wes on one of his criticisms and say like,
Brent: you know, there's 63.7% Nix in here, but 30.4% shell scripts?
Brent: You said you were leaning on shell scripts, but like, that's a lot, dude.
Chris: 2.6% is Python.
Wes: Maybe we should see if we can vibe convert it to Rust.
Wes: Vibe convert, sorry.
Chris: And then I can say it's a hyper-vibed, hyper-land-based, Wayland-first NixOS
Chris: desktop using Rust configuration management.
Wes: Nix OS native.
Chris: Yeah, right.
Brent: Nailed it.
Chris: I mean, it's funny, like, as busted as it is, it has been working very solidly for me.
Wes: The other critique is it hasn't yet been totally adapted for Brent and I, right?
Chris: Oh, yeah, well, that's true.
Wes: You know, this is your production, and we're kind of, like, helping you with
Wes: it, and so it's customary that you
Wes: provide us and sort of a flake for our computer configs with our users.
Chris: I do ultimately want to get it running on the studio computers.
Chris: I know it's crazy.
Wes: Let's do it.
Chris: I do ultimately want to get it running on there because we can't keep running these OSs forever.
Brent: I can hear Wes's tone. He says yes, but he means no.
Wes: No, I'm in.
Chris: The fear in his face also suggested no. He's like, oh my God,
Chris: we have so much work to do.
Chris: So mine's clearly in the worst state of the group.
Brent: I mean, cancel the Texas trip. You guys should just spend a week over there.
Chris: I think what I'm learning, too, is watching Wes vibe code a live tracking website
Chris: front end and then watching our listeners vibe code some of these configs.
Chris: It's not the LLM. So you thought my excuse for being a mess was that I used an LLM.
Chris: But these other people are using
Chris: LLMs. And it's much cleaner and much tighter. So it's me. It's all me.
Chris: And I do appreciate anybody that has any suggestions, pull requests or issues
Chris: they want to pull against mine.
Chris: Because I do intend to come back around to it eventually. and incorporate some of that stuff.
Chris: If you enjoyed this too, send us a booster and email and let us know because
Chris: we do have another batch of configs and we could use a few more.
Chris: We could definitely do round two.
Chris: And I hope maybe in round two we'd get some real, real awful ones because I'm ready to be a stinker.
Chris: Unraid.net slash unplugged. Go unleash your hardware.
Chris: Unraid is a powerful, easy to use NAS operating system for those of you that
Chris: want control, flexibility, and efficiency in managing your own data.
Chris: What you got in the closet is going to work with Unraid. It allows you to mix
Chris: and match drives of any size.
Chris: You can build what you want with no restrictions. There's also built-in support
Chris: for things like tail scale and one-click remote access and easy hardware acceleration
Chris: and a ginormous community app store that has everything in there from AlbiHub
Chris: to the latest RAR series of things.
Chris: And if you know what I mean, you know what I mean. Now, I got a note from Alan
Chris: in Texas. He says, in your latest read, you mentioned you wanted to hear people
Chris: with their Unraid setups.
Chris: Well, I am running Unraid on a Dell PowerEdge R730XD as my home server.
Chris: It's running a couple of VMs for Home Assistant, PFSense, and a Minecraft server
Chris: on Ubuntu, and a couple of Linux distros to play around with.
Chris: There are also several containers for Image, Jellyfin, Nextcloud,
Chris: Pinchflat, Matrix, Minifold, Vault Warden, and more.
Chris: I've been busy with work, so it needs some love. I'm not really sure if that's
Chris: worth sharing, but if you guys want to pull the trigger on Linux Unplugged Home
Chris: Lab Extreme Makeover Podcast, I could be a prime candidate. I would love to do that, Alan.
Chris: Thank you for sending that note in about your Unraid setup. I love hearing what people use it for.
Chris: I'm going to check out Minifold. I know everything on that list.
Chris: I'm not sure if I'm familiar with Minifold.
Chris: I might check that out after this show. So go get set up with Unraid and then
Chris: write in and tell me what you've built, what you're running.
Chris: Could be huge, could be small.
Chris: What really matters is that it makes a difference for you. Get started.
Chris: Support the show. Try it for 30 days for free. Unraid's fantastic.
Chris: Built on modern Linux. You're going to love it.
Chris: Unraid.net slash unplugged. That's unraid.net slash unplugged.
Brent: Well, we would like to do one big, huge shout-out to Chris B.,
Brent: a new core contributor this week.
Brent: That's not Chris Brentley, is it?
Wes: Welcome, Chris Brentley.
Chris: You are one new member this week, and we appreciate you very, very much. Thank you.
Chris: Now, we have been raising funds to get to Texas Linux Fest, and we have the
Chris: fake booths, which are set in Just in Love, because you can send an amount,
Chris: it's to a particular thing, and you can attach a message.
Chris: and park a launch came in with 25 us
Chris: dollars eagerly awaiting this coverage sending
Chris: some value back to you all that you can send to me you got it buddy pack a lunch
Chris: pack a lunch we should pack a lunch wes should we pack some food for monday
Chris: we probably should pack some snacks oh yeah we should get in the snack headspace
Chris: thank you pack a lunch i appreciate that very much brooke.
Wes: H fake boosen with 50 usd thanks for the great content been listening since linux action show.
Chris: Oh and.
Wes: A member oh wonderful.
Chris: Thank you thank you your.
Wes: Boost financial transparency is awesome would you consider including your number
Wes: of paid members when you report boosts or amount of membership income.
Chris: I don't even know if i have that number handy that's a good question there's
Chris: something i can look into there the system is sort of a black box to a degree
Chris: because we don't host that aspect of it.
Chris: And one of the things that's really great about the node setup is that we can
Chris: pull that information and store it in a database constantly.
Chris: But yeah, thank you, Brooke. Appreciate the value and we'll look into that. It's a good question.
Brent: Well, we have Brad who boosted, oh no, not a boost, a fake boost of 50 US dollars.
Brent: Now Brad says, team Toronto, and they recently in Toronto had a meetup.
Brent: I think was that last week and a bunch of people showed up some people took
Brent: the train to go in I unfortunately missed it I'm so sorry try to be there next time go.
Chris: Figure it's that's the timing of things I suppose but that's great I'm glad
Chris: they had a good meetup go team Toronto Brian came in with 15 U.S.
Chris: greenbacks thank you Brian,
Chris: Here's a little something for the trip. If you guys happen to be passing through
Chris: Boise on your journey, I'm happy to meet up and top off your supply of snacks.
Wes: Oh, that's so sweet.
Chris: That is actually the point where we'd be out of snacks.
Brent: Maybe I'll take a detour.
Chris: So we probably will go through Boise. Keep an eye on texastracker.jupiterbroadcasting.com.
Chris: We may, or near it, we may be glancing through it.
Chris: If we make really good time, I think we'll make it there. Thank you, Brian.
Chris: Appreciate that offer. and maybe get BitChat so you can hit us up.
Chris: Also, I'll be trying to keep an eye when we stop on things like Matrix and maybe email.
Chris: But while we're on the go, it's probably going to be BitChat.
Wes: Alex Gates comes in with 50 USD. Lit streams on standalone apps is especially
Wes: difficult without any backend infrastructure to watch for podpings.
Wes: I've been working on a solution for this, a service to allow apps to register
Wes: for podping notifications via either Unified Push or Web Push.
Wes: It will be self-hostable, but I also want to offer a managed service.
Wes: The problem is free services are not sustainable.
Wes: Question for the crew and the audience. What would you pay for such a service
Wes: for use in applications such as AntennaPod? Interesting.
Chris: That is an interesting idea. As a podcaster that wanted to get my live stream
Chris: into AntennaPod, I'd probably be willing to pay like 10 bucks a month to notify AntennaPod users.
Chris: Assuming that was a way they could hook up to it and not have to implement PodPing on the back end.
Chris: I love the goal, Alex, of trying to make it so that way podcast apps don't need
Chris: back end infrastructure.
Wes: Totally.
Chris: Yeah, and just because it's in the RSS feed, I mean, the only other option would
Chris: be that the client is refreshing manually and reparsing the XML all the time, right?
Wes: As some of them do now.
Chris: Yeah, yeah. Let us know, Alex. Keep us posted on that.
Brent: Well, Dave M. sent in 60 US dollars. No message, just a whole lot of value.
Chris: Thank you, Dave. Appreciate that. Eric T. came in with 25 U.S. greenbacks.
Chris: Sold some old junk from the garage and got paid for it for your Venmo.
Chris: So I'm passing the found money along to you. Have a great trip, guys.
Chris: Well done, Eric. Thank you. I need to do that. I need to do a garage purge very
Chris: badly. I am buried in stuff.
Wes: You're going to reduce the laptop stack?
Chris: Yeah, I'll even give a discount. Tell you what, buy a bundle.
Wes: Erixi octane comes in with 123 dollars.
Chris: And 45 cents that might be a one two three four five boost,
Chris: Heck yes.
Wes: Some filthy fiat for the cause. See y'all in Texas. I'll see you there.
Wes: Thank you for the support.
Chris: I hope so. Yeah, be sure you say hi. Come to the lunch.
Brent: Did you say lunch? Jens didn't boost in 10 US dollars.
Brent: Posting from the past. Hope it's soon enough for the Texas Linux Fest. Have fun, boys.
Chris: Oh, thank you. It is just in time for the Texas Linux Fest.
Chris: We are hitting the road. we had nine
Chris: fake boosts everybody who fake boosted in thank you very much
Chris: and you stacked $408.45 yes we'll
Chris: have the link in the show notes we are making the trip down and back still appreciate
Chris: the support it's been tremendous we're hitting the road thank you everybody
Chris: who supported the show with a fake boost and with that we also have a batch
Chris: of regular boosts came in and is Brad our baller this week,
Chris: Brad coming in at 20,000 sets.
Chris: Brad, who also sent us a fake booth? Is this the same Brad? Or was Brad that sent us?
Brent: Yeah, Brad's all over.
Wes: And this is what we used for the Knicks.
Chris: Brad sent us a Knicks. Brad, way to go, man. Dude, being engaged.
Chris: Thank you, sir. Appreciate that.
Brent: I think Brad should, you know, get a brunch. Brunch with Brad. We'll make that happen.
Chris: There we go. I'll take the next one, too.
Chris: Batvin came in with 2,000 sets oh no did i miss the live stream nope well you
Chris: missed last week's but you made it just yeah that was on the 21st but you're
Chris: early for this week so it just depends on your perspective we.
Wes: Hope you're out there user 304 comes in with 18 000 sets,
Wes: Okay, for the Texas trip. Oh, and this must be, oh yeah, this is stuff earned
Wes: on Fountain. I see I have earned more, so boosting again.
Wes: Well, thank you, user304. We appreciate it.
Chris: Yeah, seriously.
Brent: Well, we got a boost here, a row of ducks from the Golden Dragon.
Chris: Hey-oh!
Brent: Great episode, gents. I hope to get to bigger boosting soon.
Brent: Say, I know you guys set up fake boost for Texas Linux Fest,
Brent: but what are the chances it sticks around long-term?
Brent: It seems that it was pretty popular for some of those non-Bitcoin folks.
Chris: It has some technical limitations in that it doesn't do splits.
Chris: So it makes sense when we're allocating all the funds anyways to one particular cause.
Chris: That works perfect for that. But on a day-to-day way of supporting the production,
Chris: one of the brilliant things about the boosts is they baked in the split system.
Chris: So we all get a cut. Editor Drew gets a cut. The podcast app developer gets
Chris: a cut. the podcast index gets a little split.
Chris: We're all happy to participate. And it happens automatically at the protocol
Chris: level, if you will, or at the application level. And so the contract is in the code.
Chris: It's in the RSS feed for you to be able to just review it yourself.
Chris: You can look at our XML file and you can see what the splits are.
Chris: That's a level of transparency I really like. And the fiat systems don't yet offer that.
Chris: However, there may be something in the future we could rig up,
Chris: but we would try to make it an even better experience and make it something
Chris: that people could actively participate and enjoy.
Chris: But it has worked tremendous for this, so it's on the back of our minds, Dragon.
Wes: You know, if it sticks around, we're going to have to start calling it fake
Wes: real boosts, or real fake boosts.
Chris: You're right, you're right, you're right. Ed comes in with one,
Chris: two, three, four, five sets.
Chris: All right, I'm giving Fountain another try after the 1.3 release,
Chris: hoping to replace Intenapod as my go-to podcasting app.
Chris: The Nostra integration and value-for-value features aren't making
Chris: it into antenna pod soon enough i listened
Chris: to the episode on the next unplugged today while offline and watch the sat
Chris: streaming while i listen it's very nice i have to do some
Chris: tuning on the best amount to stream to my to meet my budget but fountain makes
Chris: that pretty easy to do the good news is is that the show will now be received
Chris: more consistent support from me will be receiving consistent support from me
Chris: thanks for the show and all the hard work that goes into it ed thank you for
Chris: putting the time effort and often honestly the thoughtfulness into that really appreciate that.
Wes: I've always liked that aspect of the streaming side. It's just sort of like,
Wes: yeah, you know, you kind of set a budget you're comfortable with,
Wes: and then you're just automatically supporting it as you're using it.
Chris: Yep, that is great. Thank you.
Wes: GeekDude comes in with 13,260 sats.
Wes: Boost for Linux Fest.
Chris: Heck yeah, we're getting there. One bit at a time.
Chris: Monty's here with his boost for his config with 6,666 sats.
Chris: Okay, we'll go with that. And we went over Monty's config. Thank you,
Chris: Monty, for sending in a boost with that.
Wes: Yeah, that's value, double the value over there.
Chris: Oh, and look who it is, Wes.
Wes: Oh, we got Adversary 17 coming in with 4,096 ads.
Chris: I believe it's adversaries.
Wes: You're right, you're right.
Brent: Would you like them to read their own boost? That seems like a reasonable thing to do.
Chris: Is that nice? That's pretty, that's mean. That's on the spot, Brent. Come on.
Brent: Oh, there it is. Adversary, if you want to read your own boost.
Chris: Here we go. your own voice regarding.
Mumble: Multi kernels maybe you have a specifically optimized
Mumble: for gaming kernel run on a few cores so that
Mumble: all the gaming tasks have better performance wait if there's a different kernel
Mumble: running on each core does that mean that things like kernel anti-cheat won't
Mumble: be able to see other tasks running elsewhere so do you negate the privacy implications
Mumble: of kernel level anti-cheats that way hmm.
Chris: That is a great question yeah.
Wes: I like where your head's at.
Chris: Yeah so you could have one kernel that's all like compromised up with
Chris: drm and crap like that so you could play your stupid windows game and
Chris: then all your other kernels live in free and that has it's none the wiser or
Chris: something like that but your other idea of like you can have a gaming optimized
Chris: kernel a video production optimized it's an interesting idea and you could see
Chris: how you could sell that as a service like it's a box it does hardware accelerated
Chris: this and it does this and that and it's like multi-kernel setup to actually accomplish it.
Chris: I don't know, guys. We haven't heard much more, but it may be the future just one day.
Chris: Sutterman's here with 11,110 sets.
Chris: And we loved your config. Thank
Chris: you very much. And also, thank you for setting up the tooling to boost.
Wes: Yeah, I've never boosted before, but you asked for NixConfig, so I had to share mine.
Chris: Do really appreciate that.
Wes: I like this bit. P.S., I blame you for my NixOS Hyperland and Bitcoin journey. Thank you so much.
Wes: This is another thing, and this happens all the time and I love it,
Wes: is I still feel like such a Nix noob, especially looking at the configs that
Wes: we have been, right? There's so much to learn.
Wes: and uh so that even if we've helped in that journey you're also there's so much
Wes: you teach us back which is amazing.
Chris: Yeah this is this is one this one is i'm stealing that
Chris: i'm stealing that this has been a good one for that thank you everybody who
Chris: sent a fake boost or a real boost as we call them uh we do appreciate it you
Chris: sat streamers uh stepped up too we stacked 40 54 671 sats just by all the out
Chris: there streaming it as you listen to us and we always appreciate that And then
Chris: when you combine that with our boosters,
Chris: we stacked a grand total of 144,620 sats this week.
Chris: You've heard the way to do it. Fountain.fm makes it real easy.
Chris: AlbiHub is something you can
Chris: also get into if you want to get real nerdy and do all the self-hosted.
Chris: And then there's lots of apps you can pick from, including just boosting from
Chris: the podcast index website, actually. You don't even need an app for that.
Chris: And it's a fun experiment, and you'll learn a lot about the technology and the process.
Chris: Or Fountain.fm if you just want somebody to manage it all for you.
Chris: And thank you, everybody who supports the show with a boost or a membership.
Chris: You actually found the pick this week. I don't know if you knew I was going to make it a pick.
Wes: I did not.
Chris: But it's so cool, and it helped with our little project that we worked on this
Chris: week, so it seemed only appropriate to include vTunnel.
Chris: It's a tool that proxies IP traffic between a guest and a host network by using the VSOC protocol.
Chris: So this could be a way to make inter-container communication,
Chris: perhaps, really simple.
Wes: You don't even need it really with containers, but with anything when you're
Wes: doing with a hypervisor in a virtual machine.
Chris: Okay, so a VM, and so two different VMs that need to talk to each other?
Wes: You can use it for that, but primarily communication from the host context into
Wes: the virtual machine and back.
Chris: Oh, just to basically build a network between the host and the VMs.
Wes: Yeah, but instead of having to necessarily. So VSOC in general is essentially,
Wes: it's a type of socket. So it's kind of like a Unix socket, but it's used specifically for this.
Wes: And the idea is you can have a connection over this socket between the virtual
Wes: machine and the host, and you don't have to deal with a whole bunch of like the entire IP stack.
Wes: If you don't want to necessarily, you can have this kind of faster,
Wes: higher throughput connection.
Chris: A little private networking that's actually a little bit simpler in its stack.
Wes: You know, maybe you have something, some server or some process running stuff.
Wes: You kind of just want to feed in data, calculate stuff and spit stuff back out.
Wes: you can have that all connected up without having to have all of the like you
Wes: know the switch the virtual switch on the host and having all the plumbing and
Wes: running DHCP and having DNS set up for it and all the right forwarding and firewalling,
Wes: vTunnel comes in if say maybe you do still need some
Wes: you know maybe this little server process does need to like
Wes: make a couple of outbound calls to grab some data occasionally for its cache
Wes: or something so this can enable proxying without still having to go set up all
Wes: of that traditional infrastructure you can use that vsoc and then have a ip
Wes: stack on top just a proxy to like carry those connections out to the internet
Wes: and get your reply back that's.
Chris: Really handy it's really useful in little ways.
Wes: Yeah there's a few tools like this and this is one that seems like it actually
Wes: works with um a lot of different setups so.
Chris: That's v tunnel and it is bsd licensed um and then this one probably not blowing
Chris: away anybody with this particular pick but wes finally convinced me.
Wes: Oh did i you.
Chris: Did Tab Session Manager, a tool to save and restore the state of browser windows and tabs.
Chris: And we like this one just because it is...
Chris: Open source. It's MPL2 licensed and really easy to get in Chrome or Firefox
Chris: or in Chrome-based browser.
Chris: And I started, what really got me is, you know, I have multiple Firefox windows
Chris: open, and sometimes the wrong one is the last one to close, and then I lose
Chris: all of my tabs and my restore isn't working properly.
Chris: While Firefox is generally pretty good at restoring your previous session,
Chris: it just wasn't quite doing it.
Wes: Yeah, you were hitting an edge case.
Chris: But you also, one of the things you like about this, right, is you can,
Chris: like, save the tabs. You can export the tabs. You can make a list of the tabs.
Wes: Yeah, and there's a lot of ways to do all this stuff, right?
Wes: There's tab groups now, and you can have all kinds of it.
Wes: But especially for the show, because often I want to reload all the stuff that
Wes: we have in the doc for the links we're talking about today.
Wes: But I had state I was working on yesterday, right? And I can kind of just store
Wes: that, work on the stuff for today, and then restore that after the fact.
Chris: Yeah, I'm not blowing anyone away, but this is a solid one. And it's open source,
Chris: cross-browser, so that's nice too.
Chris: And that's tab session manager. will have a link to that in the show notes.
Chris: Links to all this stuff that we talked about today, that's at linuxunplugged.com slash 634.
Chris: Okay, there we go.
Wes: Yeah, that's what my tab session is named.
Chris: I'm just, this is it. This is it. It's going to be you and me in a tiny car
Chris: for about three days after this.
Wes: That's right, 635 from Texas.
Brent: Makes the van feel so spacious.
Chris: Yeah. So follow us on texastracker.jupiterbroadcasting.com. We'll be hitting
Chris: the road Monday morning.
Chris: Wes and I, Brent's already on the road, and we'll have BitChat going if you
Chris: want to chat with us along the way. And, of course, we're looking forward to getting down to Austin.
Chris: And then we'll be on the route back to where we're going to be taking a slightly
Chris: different return trip as well.
Wes: You know, we didn't factor something in. What? We don't have,
Wes: like, a virtual walkie system with Brent.
Chris: Yeah, that would be cool. We should have thought of something.
Brent: You can vibe something up, right?
Chris: I should try to remember to pack some walkie-talkies, though,
Chris: So when we're caravanning on the return trip.
Wes: Oh, yeah.
Brent: You know, Chris, the last time we were together, it turns out you left a walkie
Brent: in my glove box. So I have one ready to go.
Chris: All right. We'll make sure it's charged up and I'll bring another one.
Brent: Okay. I'll need a bigger antenna, though, I don't think.
Chris: And you can be there in spirit at Texas Linux Fest with a boost.
Chris: If you want to send us a boost to support the trip and the show,
Chris: we always really do appreciate that.
Chris: And a big shout out to all our members who make the show possible.
Chris: And everybody who participated in the fake boost, too. The link's still going.
Chris: We really do appreciate that as we stack that up and actually begin to have
Chris: to absorb some of these costs.
Chris: So it's all it's all happening and it's because of our community and we greatly appreciate it.
Chris: We will try to be live from Austin, Texas next Sunday.
Chris: We'll see how that goes. So I'm going to bring all the right gear. It survives the trip.
Chris: And the internet connection works in the Airbnb. We will be live from Austin,
Chris: and we'd love to have you join us over at jblive.tv. Times.
Wes: Yeah, it's 10 a.m. Pacific.
Chris: Yeah.
Wes: But that means it's noon central.
Chris: Yeah. JupyterBroadcasting.com slash calendar for that. Hey, pro tip for them, right, Wes?
Wes: Oh, yeah.
Chris: The doggo's got the pro tip. that bark right there that's your key to go get
Chris: chapters go get transcripts with the podcasting 2.0.
Wes: App it's a fully loaded podcasting 2.0 feed you gotta check.
Chris: It out let us know if the bark shows up in the transcript and we'll see you
Chris: right back here next week.