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, you know, after all the AI hype
Chris: is finally over, I think there will be one real game changer that stands and
Chris: sticks around, and it impacts Linux.
Chris: We're going to tell you what it is, and we're actually going to test it out
Chris: and see where it's at today.
Chris: And then we'll round it out with some great picks, some boosts,
Chris: some shoutouts, and a lot more. So before we get to all of that,
Chris: we've got to do the right thing and say time-appropriate greetings to our virtual
Chris: lug. Hello, Mumble Room.
Mumble: Hello. Hey, Chris. Hello, Brent.
Chris: Hello. Thank you for being in there. We'd love to have you join us.
Chris: You can join us on a Sunday morning or whatever it is in your time.
Chris: JupyterBroadcasting.com slash mumble for that. And then, of course,
Chris: jblive.fm for the stream. It's a vibe. That's what I always say.
Chris: You don't think so?
Wes: No, I do think so. I'm here for the vibe.
Chris: You know so.
Wes: Well, I've, you know, it's got a different feel. You never know what we're going
Wes: to say, and we don't either.
Chris: You never know what Neil's going to say, you know?
Mumble: Hi!
Chris: Also, good morning to our friends at defined.net slash unplugged.
Chris: Go meet Manage Nebula from Defined Networking.
Chris: It's a decentralized VPN that's built on a true open source platform that you
Chris: completely self-host and own yourself, or you can lean into their managed system,
Chris: which makes it really easy.
Chris: You go to define.net slash unplugged. You can try it on 100 devices for free.
Chris: So unlike traditional VPNs, Nebula is decentralized.
Chris: And that means there's a certain resiliency you can choose to build into this.
Chris: And there's also a community of resources to help you make it more resilient.
Chris: So this is great for a home lab, of course.
Chris: This is also fantastic for a global enterprise. Best in class encryption.
Chris: Fantastic community. and battle-tested.
Chris: You know, in history of being my teacher and all, when it comes to something
Chris: as foundational as how I network everything, I want to own that stack,
Chris: and I want to own that stack end-to-end because when I'm building something
Chris: for myself and my wife and my kids to use...
Chris: I'm trying to take like five-year views, 10-year views if I can.
Chris: And I'm not digging on anybody. It's just a fact. When you tap venture capital
Chris: over and over again, it gets mixed into the tools that you rely on.
Chris: And sometimes your core infrastructure tools go different directions over time
Chris: because the priorities start to shift as they tap more and more VC money.
Chris: And when I thought about it long term when I think about what I want to be running
Chris: what I want to build on years from now for both JB and my personal infrastructure,
Chris: I want a project that's truly built around the value of ownership it's a big
Chris: deal when you think about it long term and there are a lot of options out there,
Chris: and some of them have like self hosting options kind of begrudgingly like you
Chris: know there's like different variations of it,
Chris: nobody does it like Nebula and so you know You can make the mistake of like I did.
Chris: I made a rookie mistake of linking a big tech login to my VPN provider.
Chris: And I don't like that at all. And now in retrospect, years later,
Chris: I wish I hadn't done that. That type of stuff is what I'm talking about.
Chris: Nothing does it like Nebula. And nothing has Nebula's level of resilience,
Chris: speed, and scalability.
Chris: Go get started with 100 hosts. Absolutely free. No credit card required.
Chris: Go to defined.net slash unplugged.
Chris: Well we got a wee bit of housekeeping this week because some events are coming
Chris: up that we'd like you to know about it's the 13th edition of Seagull,
Chris: And that's happening next week at 8 a.m. to 6 p.m.
Chris: Friday and Saturday, November 7th and 8th at the University of Washington.
Chris: What do you know about it, Wes?
Wes: Well, it's our local Seattle Linux Fest, you know?
Chris: Yeah, downtown.
Wes: Well, it has been kind of downtown or Capitol Hill area, but now it's over at
Wes: the University of Washington, which is kind of its own little corner.
Chris: Okay, that could be nice.
Wes: Yeah. So there should be lots of stuff nearby. I think they've got some meetups
Wes: and stuff going on after the fest. There's like a tea swap thing.
Wes: If you want to get some interesting teas, that sounds like it's a pretty good time.
Chris: Is that like gossip or is that the kind you drink?
Wes: Like I think the kind you drink.
Chris: Oh, okay.
Wes: Yeah, it's called Teagle. That's like a little subcom.
Chris: That's so Seattle. That's great. All right. Okay, that's good to know.
Chris: So seagull.org slash schedule. We'll have a link in the show notes.
Chris: Over 50 sessions or something around 50 sessions is going to be there.
Wes: Yeah, it looks like some good stuff. Dev stuff, DevOps stuff,
Wes: of course, Linux stuff, and then just general community and open culture.
Chris: And then probably should be on people's radar, LinuxFest Northwest,
Chris: Scale, PlanetNix26, all putting out their call for papers.
Wes: Yeah, and they all close sooner than you'd think. So if you're interested in
Wes: contributing, talking, speaking at any of those kind of events or volunteering
Wes: maybe too, but you might consider taking a peek.
Chris: Yeah, we want to let you know now because what's going to happen to you is the
Chris: holidays are going to hit you.
Wes: Yes.
Chris: Right in the face and you're not going to think about the call for papers and
Chris: then the events coming around. And, you know, if you can get a talk accepted,
Chris: a lot of employers will pay for that to get you there to, you know,
Chris: do your talk and maybe promote the thing a little bit that you do.
Chris: It's totally worth it. So, Scale, Planet Nix 26, and Linux Fest Northwest all
Chris: call for papers. And Siegel is next weekend.
Wes: And we hope to see you there.
Chris: I have a couple of other things to get to before we start the show.
Chris: We have decided we are going to do another config confessions.
Chris: So please send your configs in either boost with a link or go to our contact page and add a link,
Chris: And we'll start collecting those. We already have some in the bag.
Chris: If you already sent them in, we still have those. Most of those,
Chris: at least. Depends if Brent lost them.
Chris: And we'll get to config confessions very soon. So send those in.
Chris: And a great way to support the show would be send us a link with a boost and,
Chris: you know, two birds and all that.
Chris: Also, while you got that boost button hot, I got something I have to just level set with you guys.
Chris: I'm having a hard time understanding something. And I really want to take the
Chris: temperature here. When we first started talking about what everybody now calls
Chris: AI on Linux Unplugged, it was years ago.
Chris: And we really referred to it at the time as machine learning because the tools
Chris: that we were really looking at were machine learning tools.
Chris: And in the context of Linux, it really wasn't a huge topic, seemingly didn't
Chris: deserve its own episode.
Chris: And then three years ago, October of 2022, we finally did a dedicated episode on the topic.
Chris: And it was all about AI generation. Episode 481, the internet is going crazy
Chris: with AI-generated media.
Chris: What's the open source story and is Linux being left out?
Chris: And that's when we dedicated an episode to this thing called stable diffusion,
Chris: where people could generate images.
Chris: And we talked about the morality of it. Three years ago, we talked about the
Chris: power use issues in that episode. And of course, we talked about the Linux story around these tools.
Chris: And we even stood up a live instance of a web version of Stable Diffusion and
Chris: unleashed it on the live stream and let them crank out issues or images on our
Chris: VPS. Do you remember that?
Wes: Yeah, that was a lot of fun.
Chris: It was three years ago. So back then, it just didn't have the hype around the topic.
Chris: And it wasn't as charged as it is now.
Chris: And you didn't see the counter reaction to the hype that you see now.
Chris: And I cannot really, to be honest with everyone, wrap my noodle around how controversial
Chris: every little new technology is these days.
Chris: From programming languages to technology platforms to AI, it's just, it's remarkable.
Chris: And I'll explain my position on AI next week if people are interested,
Chris: but I wanted to take the colony's temperature on where you are at with AI. Do you hate it?
Chris: Explain yourself. Are you ambivalent? Explain yourself. Are you excited?
Chris: I want to know why. So help me, help us wrap our noodle around this because
Chris: as people that have been talking about this since like 2021-ish,
Chris: these were just tools and then all of a sudden they got really heated.
Chris: And I'd like to know where you're at on this stuff.
Chris: Because the premise of this episode this week is despite how much you hate it,
Chris: there's at the end of this, what we might call an AI bubble or AI hype session,
Chris: there's no doubt going to be a few tools that remain standing.
Chris: That's where we're going to find what worked and didn't work,
Chris: what was hype, what was silly, what LLMs were horrible at, and what LLMs were great at.
Chris: And that might be a little while from now.
Chris: But the people that hate this stuff have got to realize it's not going away.
Chris: Some of this stuff's going to stick around.
Chris: And what I've realized recently, and I'll get to why soon, is that Linux in
Chris: particular is going to be one of the most affected areas.
Chris: And you start to see hints of it this week when both Red Hat and SUSE made announcements
Chris: around their enterprise-grade distros.
Chris: So Red Hat has announced an AI assistant designed for application and migration
Chris: and modernization tools on the RHEL platform.
Chris: They said the launch of the Red Hat developer Lightspeed platform,
Chris: a portfolio of AI solutions, will equip developer teams with,
Chris: quote, intelligent context-aware assistance through virtual assistance.
Chris: The company said this will help speed up non-coding-related tasks,
Chris: including development of test plans, troubleshooting applications,
Chris: and creating documentation.
Chris: And then even more recently, Sousa says, with the release of Enterprise 6,
Chris: it is the Enterprise Linux that, quote, integrates agentic AI.
Wes: Sorry, I can't help not laugh a little.
Chris: I know. I know. I agree. Go ahead, Brent.
Brent: A release of Enterprise 16. You mentioned Enterprise 6, but I think we're moving
Brent: a little further. 16. You did.
Chris: You did.
Brent: See, 6 AI can solve that for you, Chris.
Chris: Well, I'm reading with the LLMs. No, I'm kidding. um i
Chris: i want yeah i agree with wes and probably a lot of you listening like
Chris: this stuff that integrates agentic ai it's it's
Chris: okay anyways they say quote this is the industry's first enterprise linux that
Chris: integrates agentic ai and reduces operational costs and complexity through ai
Chris: readiness so this is the phase we're in jargon heavy hype heavy gotta gotta
Chris: slap ai on your product in order to sell it do you think it's a coincidence
Chris: that these two announcements were made so close to each other?
Chris: No, that's no coincidence at all. That was very intentional.
Chris: It is very much each position trying to jockey or each company trying to jockey
Chris: their position in the AI race.
Chris: And all of that is exhausting. And all of that is tiring. And all of it seems
Chris: unsustainable. And that's all true.
Chris: That is all true. But what we want to talk about today, I think,
Chris: is the stuff that will remain after all of this passes.
Chris: So as those of you who've been listening to the show for a while,
Chris: you know that I have been rolling my own distro that I call Hypervibe for a while.
Chris: I'm just at like the three-month mark now, if you can believe it.
Chris: On average, I've made two or three notable changes per week as I've used it.
Chris: Some weeks more, some weeks less, kind of averages out.
Chris: And all of this has been done as an experiment using an LLM.
Chris: Every little tiny change.
Chris: And I started as a joke because I thought it was going to be a total disaster.
Chris: And I somehow walked away with a working system.
Chris: And then having refined this more as I actually start to use it on my day-to-day
Chris: to get job work done and start taking it seriously and less as a joke.
Wes: Actually depending on it to be your desktop.
Chris: I've realized that LLMs are good at text.
Chris: And everything I'm doing is a configuration file. And between the ability for
Chris: the LLM to do web searches and
Chris: to write configuration files and understand simple YAML or config files.
Chris: This is an area it's actually particularly strong at.
Chris: And I think we will see...
Chris: A future where if you don't take advantage of these tools, you're not going
Chris: to have your job replaced by AI, but you will have your job replaced by people
Chris: that are taking advantage of these tools.
Chris: Last week, I was having an issue with my network card dropping off the network.
Chris: And especially bad in the morning for some reason. I don't know what that's
Chris: about. I'd come in in the morning and I'd just have issues for a couple of hours every few minutes.
Chris: Looks like my nick would just drop off the network. And one of the ways I'd
Chris: have to fix it is unplug and plug it back in.
Chris: And then it would come back to life and it would start working again.
Chris: And I was a, it was a morning before the launch. I was rushed to get to the
Chris: show live because we do it.
Chris: We do a little bit earlier or no, we do a little bit later, but it's just a
Chris: more complete, complicated show. So it feels like it comes earlier.
Chris: And, um, I needed to fix this issue because I had to get my job done.
Chris: And so while I was going about prepping the show, getting voicemails,
Chris: doing all that stuff, I opened up another application and in the, and I just had a prompt.
Chris: I said, I want you to review my logs, look at my network driver and the recent
Chris: Linux kernel releases and figure out why my network card is dropping.
Chris: And then I completely forgot about it. And when I came back,
Chris: it had figured out what it was. There was a change in the upstream in the Linux kernel.
Chris: And now I need to make an adjustments to my power settings for my particular Intel NIC.
Chris: And it did all of that and figured all of that out while I was going about my
Chris: other work. And I came back and it's like, OK, when you reboot,
Chris: the fix is in and you're good to go.
Wes: Has it been?
Wes: That's great.
Chris: And it went through, it read the log files, it read the kernel change log,
Chris: it did all of that work, and then it made that change to my system.
Chris: And because it's just changing the output in my Nix config, and it's apparently
Chris: very adept at Nix, it handles it just fine.
Chris: And you could extrapolate that out to a network engineer who needs to make a
Chris: modification so every machine uses a new IP for something, right?
Wes: Yeah, I mean, if you try to read through some of the buzzwords in the ASUS stuff, right?
Wes: They're making an MCP server, which is basically a JSON API to interface with
Wes: pieces of the OS, including, I guess, some more stuff on top of Cockpit to help
Wes: you do, you know, LLM-enabled changes and updates or check in on what your system's doing.
Chris: And just as an aside, doing all of this, it's given me an appreciation for how
Chris: much edge case solving distro builders have to deal with and maintainers.
Chris: Like, it's constantly, like, things change upstream.
Chris: Sometimes it's just the name of a package, but you have to go through and constantly
Chris: make those little tiny changes.
Wes: Yeah, the integration is real work, right?
Chris: Not for me. I just have the LLM do it. I do. I just have it check it,
Chris: and then it goes through, oh, yeah, these things have changed upstream.
Chris: Okay, I'll go through. I'll make sure I change these for you,
Chris: and then it's ready to go for the next build.
Chris: It makes maintaining my own distribution possible.
Chris: And I thought, okay, let's put this to the test. And so that was one of the
Chris: things we wanted to do this week is we wanted to put it to the test and see
Chris: how far we could push this and kind of figure out where it breaks and really
Chris: how realistic is this now.
Chris: But I think this isn't going to work for every Linux. This isn't going to work
Chris: for every problem. It's going to work specifically well for Ansible,
Chris: for NICs, those types of things, declarative systems, it already is here. It's here.
Wes: Yeah, especially where it's like a lot of the same common repeated patterns
Wes: that maybe just need to be squeezed into particular context.
Chris: It is fair to say that, you know, we're at a stage where it doesn't always produce
Chris: the cleanest system, you know?
Wes: Yeah, that is for sure.
Chris: There's sometimes things are a little hacky and a mess. I mean,
Chris: it works, but it might not be how you would do it.
Wes: And it often works kind of the best for things like that, where you care more
Wes: about in our testing sort of from a black box perspective where you're just
Wes: like, okay, I can verify the things that I need do work.
Wes: I don't care that much about exactly how it's doing it or exactly how,
Wes: if it did it the way I would do it.
Chris: And I think the other thing to acknowledge at this point is it can be very expensive,
Chris: if you're doing a lot of this, depending on how you pay for it.
Chris: After we spent hours, we spent all day on a call yesterday working this out,
Chris: which we're about to get into.
Chris: And after we got off the call, I wanted to see how feasible it would be to just do it with a local LM.
Chris: And there's a lot of ways to crack that nut. But to really make it simple that
Chris: anybody could do is I went and I downloaded the app image of LM Studio.
Wes: Oh, nice, yeah.
Chris: Classic, right? Which has Hugging Face integrated. And it supports downloading
Chris: a, well, a bunch of different models, obviously. But one of them it supports
Chris: downloading is DeepSeq.
Chris: And also like the Quinn ones, which are like 8 billion parameters. you
Chris: need a lot of parameters and you can just download them and
Chris: then in the system tray icon you can just enable the server
Chris: and then you go over to something like zed zed editor
Chris: which is great and one of the options is just
Chris: a local connection to lm studio zed just automatically connects to lm studio
Chris: and all of the prompting is done locally with whatever model you've loaded in
Chris: lm studio be it deep seek or quen or whatever it is and it's slow on my system
Chris: of course but But it's actually using the AMD Vulcan acceleration.
Chris: So if you're not in a rush, it's usable. So after we got off the call,
Chris: I had a couple of things to fix, which I'll talk about more,
Chris: Went and had dinner while it was doing stuff and came back and checked on it
Chris: like a half hour later and it was done.
Chris: So you can absolutely do this depending on the system with local tools.
Chris: But there is still a quality gap. Like the big stuff, the big models hosted
Chris: by your chat chippities or your clods are still superior.
Chris: They're still faster and they're very expensive.
Chris: So these are real limitations. As right now it works, but it'll build a system
Chris: maybe the way you wouldn't if you're not really on top of it.
Chris: And if you don't know to catch something there was something you brought up
Chris: yesterday west it was like oh i'm really glad you said that because i wouldn't
Chris: have caught it and the ai wouldn't have caught uh.
Wes: Maybe it was the the bit about like all the extra work it was doing with uh a rofie setup.
Chris: Yeah something it was something like it.
Wes: Introduced like basically an abstraction to deal with having to use multiple
Wes: multiple rofie packages that just no longer was needed.
Chris: Whatsoever yeah it was a solution to a problem that no longer existed and it
Chris: hadn't caught that that's a great example and And so there's still that level of human engagement.
Chris: But we learned some lessons with this. And it is, in my mind,
Chris: sticking around. And I don't know what this is going to be called.
Chris: This is one of these things I always take a lot of crap for.
Chris: It's not obvious to everyone two to three years out. But as we get two or three
Chris: years down this road, it's going to be so obvious.
Chris: And it's going to be called something like prompt ops or DevOps prompts or Linux by prompt.
Chris: Really? Like, you know, like you're going to have a Linux machine as a system
Chris: administrator and you're just
Chris: you're going to have something on the command line that you work with.
Chris: If you go over to GitHub.com and you look at the CLI tag and you look at the
Chris: most popular projects in the CLI category, every other project practically is
Chris: some sort of LLM tool on the command line.
Wes: I mean, even back at Summit, Red Hat came out with Lightspeed and their little
Wes: C tool for the command line.
Chris: Yeah.
Chris: That kind of stuff is going to be the norm. It's just going to be one of the
Chris: tools on your, you know, like you have some stuff that can suggest commands.
Chris: There's going to be LM tools that do that.
Chris: And there's just going to be a name for it. Like DevOps became a thing.
Wes: I mean, that's already one of the uses, just especially that like throwaway
Wes: scripts, quick little things to clean up files or like do a particular manipulation
Wes: that it's maybe not worth me scripting, but like a script would be better than
Wes: me doing it manually. I love that.
Chris: And I actually think there is a future where small local micro LLMs or whatever
Chris: you want to call them are actually going to be better at this particular stuff
Chris: that we're about to talk about than the chat GPTs or the clods.
Chris: There will be in the future models that you can run in your text editor that
Chris: will be possible on a desktop machine that is just super focused on config files
Chris: or PHP or whatever it is that you do. That's its whole world.
Wes: That's kind of some of what Red Hat is offering with some of this new development.
Wes: Like they have stuff targeted at enterprise migrations of legacy software or
Wes: migrate into containers and stuff like that.
Wes: But it's, you know, you have models you can self host that they've figured out,
Wes: optimized for these particular types of problems.
Chris: And right now, man, if you get LM Studio and you load DeepSeq or whatever the
Chris: hell you want and you open up Zed, it's all happening locally on your machine.
Chris: It's all completely self hosted with just two desktop applications.
Chris: You didn't have to start a single container or anything.
Chris: And it's got a nice GUI to help you find the new models. You don't even have
Chris: to know what the hell you're doing.
Chris: And it's approachable right the F now.
Chris: And so this is only going to accelerate. You're seeing Red Hat and SUSE lean into it.
Chris: It is going to be so obnoxious for a while. And I really sympathize for those
Chris: of you that are so sick and tired of this stuff.
Chris: But I'm trying to give you your medicine with a little bit of sugar this episode
Chris: because what we're about to talk about ain't ever going away.
Chris: Onepassword.com slash unplugged. That's the number one password.com and then lowercase unplugged.
Chris: Take the first steps to better security for your team by securing credentials
Chris: and protecting every application, even the unmanaged ones you didn't know about.
Chris: There's more to secure than just passwords.
Chris: Managed and unmanaged SaaS applications, for instance, are a huge issue these days.
Chris: That's where Trellica by one password secures your apps without leaving your
Chris: employees behind, without creating that odd and difficult tension between IT and your end users.
Chris: And if you are an IT professional or if you're in IT security,
Chris: you know about the mountain of assets that's growing all the time and the sprawling
Chris: applications that are out there as a service that users are signing up for all the time.
Chris: It's a big problem. That's where Trellica will help you to discover and secure these applications.
Chris: It'll find out where you have redundancies, where maybe you could cut back on spend.
Chris: And Trellica by 1Password has pre-populated app profiles that'll assess the
Chris: SaaS risks, let you have a better understanding of really what you're dealing with.
Chris: And like I say, optimize that spend while you're enforcing best practices across every app.
Chris: It really is truly the missing piece, something that I have struggled with when
Chris: I was in IT because there wasn't anything like this on the radar.
Chris: When 1Password came along, getting better password hygiene seemed like a huge leap forward.
Chris: And of course, you know about their award-winning password manager,
Chris: but they're securing a lot more than just passwords now.
Chris: So check out 1Password Extended Access Management.
Chris: You get started by going to 1Password.com slash unplugged. That's where you'll find out more.
Chris: You'll learn if your employees are bypassing your best practices to use unapproved
Chris: apps, how you can get your hands around that, and how you can get one dashboard to manage it all.
Chris: So take a look at 1password.com slash unplugged. Take the first steps to better
Chris: security for your team by securing credentials and protecting every application,
Chris: even the unmanaged shadow IT.
Chris: Go right now, 1password.com slash unplugged. Support the show and learn more.
Chris: That's 1password.com slash unplugged, all lowercase.
Chris: 1password.com slash unplugged.
Brent: Well, your three hosts yesterday got on a call because, well,
Brent: I had an inclination at least that Chris's dear Hypervibe needed some love on the back end.
Brent: We had a couple of listeners say, I think things could be better.
Brent: And we had some PRs come in and we figured we should have a look at this.
Brent: And Wes, what did we find?
Wes: Well, first off, as usual with our community, we found like just incredible
Wes: pull requests and issues and just a lot of wonderful engagement,
Wes: including someone had like sopsified it with
Wes: sopsnix and written just an incredible readme about
Wes: how to use it and work with it so we'll have to look more in that for
Wes: sure but you know hypervibe has has done
Wes: well it's obviously been working well from from chris's experience reports
Wes: here but it's really kind of it started as a
Wes: one system thing that got extended to a two system thing right
Wes: rvb and next station is are the names here yep and
Wes: then at one point earlier we did try kind of a first round of
Wes: this where we were like well you have a lot of shared functionality between these
Wes: two configs that you probably don't including a whole bunch
Wes: of janky activation script stuff that is sort
Wes: of a bunch of crappy bash yes i'll own that yeah i guess you vibed into existence
Wes: to not use home i did not want to use home manager i will own that yeah and
Wes: so that each one had their own version of that was but it was pretty much identical
Wes: right so it's like took an early stab at trying to refactor some of that into
Wes: actual modules that you could then i was use in your host config like.
Chris: I was doing a backwards approach of taking two linux boxes that We're totally
Chris: separate systems set up years apart from each other.
Chris: With very different, you know, display setups. And I wanted to unify them into one experience.
Chris: You know, try to create one ultimate Linux desktop for myself that I use across all my machines.
Chris: So I essentially tried to backwards integrate them. And I got to a working point
Chris: for like those two systems.
Wes: But it was not in a very good state if you wanted to onboard a new system.
Chris: Yeah. Which eventually I do. And I wanted you to try it too. Right.
Wes: It also meant like if anyone else wanted to use it, right? There was a lot of
Wes: work you had to figure out and like copy your structure.
Wes: Not really do it the nix native way at all and or i mean not the like easiest
Wes: way anyway and to boot right we talked about the problems of the stuff that
Wes: you know we wanted to refactor but there's also stuff we needed to make more
Wes: variable just in that like you had hard coded in a few things including your
Wes: username you know the wonderful chris f yeah.
Chris: I mean i thought everybody would just run as chris f but turned out they didn't want to do that.
Wes: Yeah so we needed to expose stuff there and there were a couple pull requests
Wes: already to do that so people had taken a few stabs at basically using the module
Wes: system and exposing those as configuration options for a Hypervibe module that
Wes: would say, like, what user are you using?
Wes: Because we need to, like, put that in some of the scripts and plan for that.
Chris: Yeah, so it's something you could add to an existing system.
Chris: It'd be a Hypervibe module that you could add to a Nix box that already exists,
Chris: and then you could define run as this user. Run as Wes instead of Chris F.
Wes: The goal was like you could import this module from Chris and then enable it
Wes: and set whatever required options like what your local username you're going
Wes: to use it with is and just have it work.
Wes: But to get there, we had the problem that in our first attempt,
Wes: well, one, we didn't have the optionality on username at all. That was hard coded.
Wes: But then in our attempt to simplify things before, it kind of pulled some stuff
Wes: out into shared modules, but it put it under a shared namespace instead of hyper
Wes: vibe namespace. So we're going to have to replumb.
Chris: Yeah.
Wes: That's more of like a find and replace almost, so stuff that it should be pretty decent at.
Chris: It's not, at first it wasn't obvious to me what should be machine-specific configurations
Chris: and what do I want on all my systems.
Wes: Right, and that's where either you have to put your judgment or rely on it's...
Wes: Quote unquote judgment.
Chris: And it's something I hadn't thought a lot about. So it is an example of if you
Chris: don't think of it, it won't necessarily.
Chris: It doesn't mean you can't go back and refactor, which is what we decided to
Chris: do is essentially re-architect the way this thing is completely done.
Chris: In order to make it possible for, say, somebody like Wes to run it on their system,
Chris: we had to extract out machine-specific stuff and try to put the overall Hypervibe
Chris: experience of Hyperland, the chosen application, the theming, the Waybar,
Chris: the performance optimizations, the Zen kernel.
Chris: We wanted all of that to be something that would be a shared thing across all systems.
Wes: Yeah, and that's where it's you as the crafter here who's trying to figure out
Wes: enough of what your vision is if you're going to have it be able to be executed by something else.
Wes: Part of the problem, too, was the first attempt had pulled some stuff out,
Wes: not the way we wanted, but it hadn't necessarily always deduped that, right?
Wes: It didn't always update all the configs to use that new functionality.
Wes: So then there was now, instead of deduping, it just duped again.
Wes: So we had even more cleanup to start with, really.
Chris: Yeah, that is true.
Wes: And that's just kind of stuff you got to, you know, watch for if you're going
Wes: to be using some of these tools sometimes.
Chris: The goal that we wanted to pull off was to task the machine to re-implement
Chris: this into a way that could be shared and not break the existing system while doing so.
Wes: Because we were basically switching. You were redefining and picking an interface
Wes: that would be Hypervibe and you needed your two existing machines to still use
Wes: that and not use their old hard-coded previous version.
Wes: That's kind of a tall ask. I mean, that is not managing a simple Nix OS config
Wes: for one workstation. That is a little more abstract.
Chris: And you're really trying to
Chris: change the plumbing of how this entire thing is built while it's in use.
Chris: And the more you realize, oh, I have to solve for this edge case.
Chris: Oh, I have to solve for this edge case because these machines have this resolution
Chris: and these machines have this resolution.
Chris: It just keeps increasing the scope. And as we were doing it,
Chris: I know, Brent, you were like, I don't think this is going to work.
Chris: This is, we're getting too far out there.
Brent: Oh, I was skeptical. I mean, just the expressions that you had watching some
Brent: of its progress go by and you're the quote unquote expert at this particular,
Brent: uh, let's call it an operating system.
Brent: Right. And you're like, well, I don't know if we should be doing that, but I'll say, okay.
Wes: And you were freaking like the higher, the number of files touched count.
Wes: You're like, well, why is it touching that? Why that one?
Brent: And all level headed West was like, no, no, it's okay. It'll be okay. We'll just fix it later.
Chris: I was getting more, because it was getting more and more complicated.
Chris: And I thought the more complicated this gets, it feels like the more little
Chris: side edge pieces it won't think of.
Brent: Can you talk a little bit about the setup that we had to make all of this work?
Brent: What did you use to actually like make these modifications?
Brent: I know it seemed like a pretty cool setup from what I was looking at,
Brent: but give us the nitty gritty.
Chris: You know, there is a thousand ways to do this. So don't take this as the blessed
Chris: path, but this is what's worked for me, is I got the Cursor application and I connected it to GPT-5.
Chris: And then later I connected it to a local LM after we got off the call.
Chris: But that's a whole other process and it was really a pain in the ass.
Chris: And I wouldn't recommend it with Cursor.
Chris: But back to my point, I wanted something that would work quickly for us while we were on the call.
Chris: And so what's great about Cursor is it's essentially a re-skinned, modified VS Code.
Chris: So if you have used VS Code before, you'll be at home in Cursor,
Chris: and you know how it can open up entire directories.
Chris: Well, that entire directory becomes the context for Cursor and the LLM.
Chris: And so it becomes, and that would be all my config files, and they're all in
Chris: a different hierarchy in one directory, and it knows all of them.
Chris: And it can read across all of them.
Chris: And when you ask it a question, it considers the entire scope.
Chris: And so one of the ways I've made this work is I've put all of this for all of
Chris: my hosts in a build directory in my home folder.
Chris: And so everything I'm doing is in that build folder. That's what gets checked in and out of GitHub.
Chris: And so it has the context of all of the machines because it's looking at that one directory.
Chris: And then you can just open up a chat session and say, tell me about this.
Chris: Or it can be something as simple as What key bind am I using for XYZ to,
Chris: all right, let's refactor this thing,
Chris: which we, I would say it took longer in the sense that I thought we'd be done in a couple of hours.
Chris: I thought we'd be done at noon and I think we wrapped up around 530.
Wes: Yeah. Maybe 430.
Chris: Okay. However, I think if we had done that manually, I think it would have taken us three days.
Chris: You know possibly what do you think.
Wes: I think i think we're taking me three days maybe
Wes: you one day yeah there we go i think that's about right yeah yeah i think
Wes: it probably would have taken about a day maybe regardless just because there
Wes: was a certain amount of like i had to catch up on what had all because i took
Wes: a snapshot look at it a couple months ago but you've continued
Wes: vibing right along so like enough stuff had changed i need
Wes: to get enough exploratory work to like wrap my head around what was happening and
Wes: then just like some of the stuff are just kind of mechanical changes that you
Wes: got to do that are actually kind of perfect work for the element because it
Wes: is kind of thoughtless really um and then some of it that maybe would have gone
Wes: faster is if we had used more human abstract reasoning for some of the like
Wes: more stuff to be obvious to us that it was struggling with.
Brent: What really struck me chris throughout was would you even attempt something
Brent: like this without this tool because now that you're in it you're like okay well
Brent: I could probably have figured it out,
Brent: but I'm not so convinced you would have started the project in the first place.
Chris: I would have started over from scratch. I would have started over and just sort
Chris: of rebuilt the whole thing with this new model in mind.
Chris: And I don't think I would have ever had the time for that, so I don't think
Chris: that's actually what would have happened.
Chris: But if I were to take this on without a tool like this, that's how I would have had to go about it.
Chris: So beforehand, we kind of had like this scattered configuration,
Chris: activation scripts that were defined in different machines and sort of a lot
Chris: of duplicate efforts, duplicate paths for stuff. We had my username hard coded.
Chris: We made it really hard for somebody
Chris: to come along and just add it to their machine and just define a user.
Chris: And what we got to at the end of our call was a single declarative source of
Chris: truth for Hyperland, Waybar, Shells, all the system fine tuning,
Chris: and then per host overrides for certain config options,
Chris: users, maybe resolution monitor, 3D, you know, driver stuff.
Wes: And there's definitely a lot of work that could still be done,
Wes: you know, like one, I think just in general would be good to kind of just audit
Wes: the whole thing and delete as much as you can without breaking it just as a, you know, cleanup item.
Wes: But then mostly, yeah, I think there's some improvements to be made on the interface
Wes: of like what stuff that we have as fallbacks and isn't required,
Wes: but it's more just like a good default because I had to override or comment
Wes: out some stuff in my code to make that work super easily, as easily as we'd like.
Wes: So we got really close to the interface we want, but it's not quite there.
Chris: But that said, you know, after 250 lines moved from per host stuff to a single
Chris: module or a couple of modules, we got a new namespace for Hypervibe.
Chris: Like, we got it pretty far. So the real test was, after we got it working in
Chris: a VM, could you get it working on physical hardware?
Chris: And I'm happy to report, Wes Payne, ladies and gentlemen, running it right now
Chris: on the laptop, switched during the pre-show.
Chris: How's it going so far? What do you think?
Wes: Yeah, it's been fast.
Chris: Does it feel faster?
Wes: You know, I got to do more tests.
Chris: It feels faster to me. That's all I know.
Wes: It was easy, though. Like, I did have to, like, there's some stuff you have
Wes: for, like, the garbage collection for the Nix Demon that I had slightly different settings.
Wes: So, like, that's a conflict, right? So, some things like that is what I mean.
Chris: Oh, yeah, yeah. I suppose because you weren't starting from, like, a fresh.
Wes: No, I had to put it on. It's just my existing NixOS configuration.
Chris: Right.
Wes: But even then, right, it's mostly, there's a couple of changes.
Wes: I don't know, under five things I had to come in on my config or adapt or override.
Wes: You could do a make force kind of thing, too. and then in the flake you just
Wes: kind of you know i had to add your hypervibe as an input i had that uh hypervibe
Wes: module and then i set enable equals true user equals west.
Chris: So it's four or five lines you added to your nix configure or your flake and
Chris: now you have a hypervibe system that's pretty great right i mean you took it
Chris: you it was a plasma system for years you added three or four lines to your flake
Chris: oh yeah i did also commented out some stuff i did also.
Wes: Comment out the plasma stuff.
Chris: Yeah but if you were on a fresh box i mean you wouldn't even have to do that yeah.
Wes: For our first test we just got a vm going from like a default uh no graphical
Wes: environment nix os install from the installer so.
Chris: Yeah and.
Wes: That worked pretty well too.
Chris: The machine had produced us a success a successful reproducible version of hypervibe
Chris: which we had not gotten to before so that was very impressive that it actually
Chris: did manage to properly refactor it into shared modules into you know host overrides
Chris: and then deliver us something that we could actually get to.
Wes: A working state yeah.
Chris: That and it's that's on your system right now that's incredible,
Chris: To do that, we had to completely rip apart my home system, the system that was
Chris: working, sort of the original box.
Wes: Oh, did you want that to keep working?
Chris: And because we were on a call through that system, I couldn't build and reboot and see if it worked.
Wes: We could build it. We just couldn't boot.
Chris: I couldn't reboot because I would drop off the call. And so I had to wait till
Chris: we were all done and so find out if I had a working box or not.
Chris: And I don't know how to properly convey the amount of rearranging of the guts
Chris: of this system that we did.
Chris: I don't know if I – it's like an entirely new distribution.
Wes: Oh, yeah, we should definitely – I don't think we updated the readme at all, so that's – Oh.
Chris: I know.
Wes: Add that to the to-do list.
Chris: Yeah, I realized that as I was looking at it this morning. I had no idea if
Chris: anything was going to work anymore.
Chris: I didn't even expect it to boot. So I got off the call, went ahead,
Chris: did one last rebuild boot, hit the old reboot button.
Chris: And it came up. I think I have one error message during the activation phase.
Chris: But GDM launched, and it came up, and I thought, oh, my God,
Chris: I can't even believe I got this far.
Wes: Okay, that's positive.
Chris: I got GDM, and it booted.
Chris: And everything works fine except for one thing, and it's so funny.
Chris: GDM launches, and instead of saying my name, it now says Hypervibe.
Chris: It's still Chris F for the user.
Wes: Yeah, okay, that's another thing we need to set.
Chris: We're.
Wes: Setting that user description and to make it work i think we had it probably
Wes: uncommented just like i did.
Chris: But you don't get.
Wes: Your username you get a generic hypervibe user.
Chris: Because all my dot files were the same and all the software was the same but
Chris: the system was completely reconfigured that was the only thing that was wrong
Chris: is that my full name for my username was hypervibe,
Chris: and i was sitting there going wow i cannot i cannot believe we just vibed our
Chris: way to a completely re-architected system, and that's the only problem I have?
Chris: That's the only problem I have? You've got to be kidding me.
Chris: And I sat there just like my jaw.
Chris: We ripped this thing apart and just walked away. I just couldn't believe it.
Chris: And so it's working just fine. It's working absolutely. I later on used DeepSeek to fix the username.
Chris: But we should fix it in a way where it's set for everybody. That would be the better way to go.
Wes: Oh, yeah, did you just override it locally?
Chris: Yeah, and I just, you can change the display name.
Chris: But what do you think, Wes? What do you think about sticking with it for a little
Chris: bit? See what you think trying out the Hypervibe lifestyle for a few days.
Wes: Okay.
Chris: Yeah? Are you going to do it?
Wes: Yeah, I'll do it.
Chris: I think if you and I try it out.
Wes: I might have to ask you some questions, though, that you can vibe for me.
Chris: What do we need? Yeah, I need to update the readme, put a cheat sheet on there
Chris: of all the key binds, because there's a lot of key binds to know about.
Chris: You and I battle test it for a little bit. Then, you know, the next stage,
Chris: Brent, we've got to get you to do a bug test on it. We've got to get you to
Chris: run it for a little while.
Brent: Well, that's really up to you when you want to pull me in if you're ready for it or not.
Chris: Right? Or are you ready for it?
Brent: Oh, I'm ready. Are you ready?
Chris: I don't know, actually. I don't know. I haven't been so good with keeping up
Chris: with the issues and PRs, but I do appreciate people that sent them in.
Chris: One of the things we were able to do is Cursor can also, you can add links to GitHub as context.
Chris: So where we actually started is we pulled in a few of the pull requests and
Chris: a couple of the issues and had it analyze those and compare it to the existing
Chris: system because there was a pretty big change since those issues were submitted.
Chris: Three months ago almost and we had it look at the differences
Chris: and see what would be practically possible to apply and how we might
Chris: apply it to the existing configuration and so we started with an analysis of
Chris: those poll requests and issues that people submitted and were able to kind of
Chris: iterate from there that's really how we even started down this direction and
Chris: we just had to give us an overview what they said what would what we would need
Chris: to change and that was kind of our launching off point which is pretty powerful just that right there.
Wes: Yeah thanks to the community really.
Chris: Yeah, it was longer than I wanted, but we ended up with something that is much
Chris: more shareable, much more reproducible for me on a new system.
Chris: So if I one day finally do get a new laptop, this is now completely deployable for me.
Wes: In particular here, props to
Wes: FBit818, SAMH, and Shift because they've all made excellent looking PRs.
Chris: Yes. Thank you, everybody. Go check it out. If you want to see it,
Chris: it's at github.com slash chrislasset. We'll put a link in the show notes and
Chris: try to get the read me updated pretty soon to explain how to get it working.
Chris: It's been a lot of fun and I've learned a whole new appreciation for the people
Chris: out there that are maintaining distributions for us and how much of it is just
Chris: little chicken ass that they have to deal with on a week to week basis that
Chris: keeps them busy along with all the other stuff you have to think about with
Chris: the architecture level.
Chris: It's been a great experiment to kind of not put myself anywhere near their shoes,
Chris: but I'm in the same room as their shoes and I can smell them.
Chris: You know, and I've gotten I've got a much better appreciation for the smell of their shoes now.
Chris: Join crowdhealth.com promo code unplugged.
Chris: The open enrollment is now so take your power back and join crowd health to
Chris: get started for just $99 for your first three months.
Chris: I struggled to solve healthcare as a small business owner with just a really
Chris: small team. There wasn't a great option for me. And I looked for years.
Chris: I tried everything but the cost just kept getting absolutely bonkers.
Chris: And I needed to make an informed decision.
Chris: And so I did a deep dive into crowd health. I have been a CrowdHealth member
Chris: for over three years, and it has been a peace of mind for myself and for my wife.
Chris: And we've participated in the Crowd helping others with their health needs, too.
Chris: Don't take my word for it. Trust yourself. Go take control of your future with
Chris: CrowdHealth. It is a health care alternative for people who want to make their own decisions.
Chris: So you don't have to play the insurance game. You join CrowdHealth,
Chris: which is a community of people like myself, funding each other's medical bills
Chris: directly. No middleman, no networks, no nonsense.
Chris: And I can tell you, it works better than I initially expected.
Chris: I was just hoping for anything that would be functional.
Chris: And I would say it's far beyond my expectations.
Chris: There's a great app to let you manage all of this, including looking at your
Chris: status in the community, seeing what the requests that come in,
Chris: where things are at, and also getting information.
Chris: Including, like, you know, taking care of things when they come up,
Chris: unfortunately, and all that kind of stuff.
Chris: It has dramatically saved my family so much money. This is CrowdHealth.
Chris: It's a health insurance alternative.
Chris: It's health care for under $100.
Chris: You get access to a team of health bill negotiators, low-cost prescriptions,
Chris: and lab testing tools, as well as a database of low-cost, high-quality doctors
Chris: that have been vetted by CrowdHealth.
Chris: And it works. And if something major happens, you pay the first $500 and the
Chris: crowd steps in and helps fund the rest.
Chris: It feels like everything has been messed up for the few years.
Chris: And with health care, it's just getting so much worse this year in particular.
Chris: So if you join the crowd, you take care of each other. You get outside that system.
Chris: That system is going to be overpriced. It's not really taking care of your health.
Chris: It doesn't incentivize you to take care of your health.
Chris: And it's so, so complicated now with all the subsidies and the things that are expiring.
Chris: It just is not something I even want to have to participate in anymore.
Chris: CrowdHealth has saved members over $40 million in healthcare expenses because
Chris: they just refused to overpay for healthcare.
Chris: They do it right, they figured it out, and it's working for me.
Chris: The open enrollment is now, so take your power back. Go join CrowdHealth.
Chris: Get started for just $99 for your first three months.
Chris: Use the promo code UNPLUGGED at joincrowdhealth.com. That's joincrowdhealth.com,
Chris: and then our promo code is UNPLUGGED.
Chris: CrowdHealth is not insurance. opt out, take your power back.
Chris: This is how we win. Join crowdhealth.com promo code unplugged.
Chris: Unraid.net slash unplugged. Unleash your hardware.
Chris: Go check out Unraid, the powerful, easy-to-use NAS operating system for those
Chris: of you that want control, flexibility, efficiency, and you just want to play
Chris: around real quick with the stuff we're talking about. Unraid is your gateway to that.
Chris: And Unraid 7.2.0 just landed. Yes, the new stable release of Unraid is here. New, fresh features.
Chris: First and foremost, the web GUI is now responsive. So it's going to look great on a lot of devices.
Chris: And then you ZFS users, you're going to love the fact that you can expand a RAID Zed pool one by one.
Chris: Whatever that means, I know you're going to love it. And it's here.
Chris: That's right. You now have solid NTFS support. If you have a bunch of disks,
Chris: like I have a couple of old Windows disks that I want to use,
Chris: but I want to copy the data off, boom!
Chris: NTFS support's in there. You would be blown away.
Chris: You would be blown away. Can I just mention how blown away you would be if you
Chris: knew about the just excellent file system support in Unraid?
Chris: I mean, we talk a lot about the awesome virtualization support for passing through
Chris: hardware and doing VMs and containers next to each other.
Chris: We talk about the luxurious community application catalog and the fact that
Chris: they're always maintaining this thing and putting out new versions and making
Chris: it super easy to upgrade and safe. Your data is always safe.
Chris: Like that's stuff I talk about.
Chris: But what I don't really mention enough is like, it's got you covered on file systems.
Chris: And one of the things that a lot of people who script are going to be happy
Chris: to see, they now have a built-in open source API.
Chris: And I've already seen the community working on some apps around this. It's chef's kiss.
Chris: And I don't know, I guess the community is at a point with maturity where these
Chris: applications are just bangers. It's just really impressive.
Chris: So the new Unraid's great. And if you haven't checked out Unraid yet,
Chris: we've got a deal for you Because not only can you support the show by going
Chris: to unraid.net slash unplugged, but you can check it out 30 days for free,
Chris: no credit card required, unraid.net slash unplugged.
Chris: And if you decide to pull the trigger, they got a lot of nice price options
Chris: at different points you're going to like.
Chris: And that's just kind of locking in the guaranteed maintenance,
Chris: the continued improvement.
Chris: I mean, they just hit 20 years and they're still going strong.
Chris: So this has got a long runway and it's something you can run for a very long
Chris: time with the hardware you have today. It's that great.
Chris: Unraid.net slash unplugged.
Brent: We have a little piece of mail here from our dear olympia mike hey mike it's been a while,
Brent: mike writes hey guys um i'd love to get
Brent: in on that roast my nix config action this
Brent: isn't my personal config of course but it's the main
Brent: nix module for the nix book project that i've been working
Brent: on for nearly a year the nix book install script
Brent: basically just adds this base.nix as an
Brent: import and before you jump all over this
Brent: no the project doesn't use flakes yet mainly
Brent: because one technically flakes are still experimental
Brent: and i'm trying to be conservative here it's
Brent: also just complicates the installer and number two flakes
Brent: seem to also be very host specific but
Brent: i won't know what host name a user of nixbook wants
Brent: either way this has been running well for the most
Brent: part notable parts of this config is the
Brent: nixbook config updating itself sending notifications
Brent: to users when you don't know the usernames of the
Brent: users on the system and the automatic way to switch channels when i bump the
Brent: channel version biggest issue nixbook users are having currently is printing
Brent: oh yeah yeah i have a vahi uh enabled and it finds the printers but for some reason,
Brent: the user still needs to go into CUPS, modify the printer, select the driver,
Brent: and then enter their password.
Brent: Curious how this can be more automatic, like the way Linux Mint or other distros do it.
Chris: That could be something anybody out there knows. Let us know,
Chris: because I don't think I have an answer for that one.
Brent: Please roast away, boys. Call me out on my jank and make the Nixbook project even better.
Chris: Well, I think this email seals the deal, gentlemen. Yeah.
Chris: Yeah, I think we're going to do another episode of Config Confessions.
Chris: It doesn't have to be a NixConfig.
Chris: It could be whatever you are working on, including a Docker Compose file,
Chris: maybe an Ansible. I'd love to see a few Docker Composes.
Chris: And, of course, your NixConfig. Send them in either via a Boost link or at the contact page.
Chris: There'll be a Mike's in there. We've got a few others in there we'll be talking
Chris: about. And, you know, of course, I think you better prepare yourself because
Chris: a lot of the answers is flake it up, Mike.
Chris: Like, number one, the number one problem you listed you wouldn't even be having.
Chris: And number two, you need to knock that experimental stuff off.
Chris: But we'll get to that we'll get to that he does I'm just telling it like it is that is that is you.
Wes: Gotta listen to the episode.
Chris: That's big channel propaganda is what it is it's big channel propaganda and
Chris: I'm not standing for it on this show I just feel I just feel strongly about
Chris: that alright but thank you and prepare prepare yourself,
Chris: we got some boosts into the show this week as well KS Koba comes in as our baller
Chris: booster with 88,887 that's.
Chris: I like it. I like it a lot. Thank you very much.
Chris: And I feel like that number means something, but what it really is is a bunch of ducks.
Chris: He says, I watched a great interview with DHH and Primogen about the perfect
Chris: storm of Windows 11 dropping the ball,
Chris: macOS getting stale, and Linux getting good, or at least good enough to finally
Chris: make the 2025-2026 the year of the Linux desktop, desktop, desktop.
Chris: Kind of echoes what Chris was saying recently about a new demographic of users.
Chris: I've been able to shift fully in my life now to Oma Archie on all of my laptops and desktops.
Chris: Still some learning to do, like how do I install from a tarball?
Chris: But overall, it feels so fresh and I'd say unobtrusive. And OS just gets out of the way.
Chris: That's great to hear. And thank you for the boost.
Chris: I really appreciate that. But I love knowing that it's working for more and more people out there.
Chris: I do think there has been a particular audience that Oma Archie has locked in on.
Chris: And I think that's fantastic. As far as running from a tarball,
Chris: well, that's a little complicated.
Chris: It depends on what you downloaded. You might need to extract it and mark it
Chris: executable and then run it.
Chris: But generally, you want to try to install something from your package manager
Chris: if you can and not from a tarball.
Chris: Because you're not really installing it. You're just running it.
Chris: So there's that little hot tip for you but thank you Kay, appreciate that baller
Chris: boost you're the best around.
Wes: Well turd Ferguson boosts in with 22,200 and 22 sets,
Wes: I already thought we were called the Jupiter Colony we have colonyevents.com
Wes: how quickly we forget ouch that's.
Chris: A good point that's true and the matrix server is the Jupiter Colony Yeah,
Chris: I'm going with it. I'm leaning in.
Chris: I'm leaning in. We're calling the audience a colony, and I am fine with that.
Wes: Colonized.
Chris: Yeah, I agree.
Brent: Well, Oppie 1984 boosted in 4,000 sets.
Brent: Here's a quote lifted from last episode's boost. A quote, I'm assuming home
Brent: assistant here. And Chris, that was your response to some feedback.
Brent: Well, Oppie says, insert Picard face bomb here.
Brent: I only happen to leave out the most important details in my feedback.
Brent: Yep, I'm switching a home assistant.
Brent: Little update on my mom using Mint, though. She's trying a live USB,
Brent: and so far it's positive about it.
Chris: That's an interesting way to
Chris: slip it in for old mom there, is give her a USB live stick. I like that.
Brent: She does, of course, like that it looks and feels just like Windows 7.
Brent: She's still not ready to take that plunge, though, but I'm on the lookout for
Brent: one of those Windows 10 laptops people are getting rid of when moving to Windows
Brent: 11, and then I'll just do a full install so she can try the full experience
Brent: before making the switch.
Brent: She needs a new laptop anyways, so two netbirds with one gemstone.
Chris: Ah, that's big kidneys right there. I like that. Good thinking.
Chris: That's a perfect little snipe. You know, those laptops are still going to be plenty good.
Chris: Nice thinking. Thank you for the update, Oppie. It's good to hear from you.
Chris: Not the one comes in with 2,000 sats.
Chris: Should be lup rats instead of lab rats. Oh, and plus one for another config
Chris: confession. I love the deep dives.
Chris: Even if it's a topic I don't have a use for. Now that is the perfect listener.
Chris: Thank you. We really appreciate that.
Wes: Hybrid sarcasm boots in with 10,000 sats.
Chris: Are you serious? Thank you, hybrid.
Wes: Love the recent baller boost. And just a reminder that a free Jupiter Party
Wes: membership goes to the listener that boosts the most total sets in 2025.
Chris: Right.
Wes: There's still time to get those boosts in.
Chris: Yeah. We're going to have to put something together for the end of the year
Chris: because we're not, well, we haven't, we technically ended the tuxies last year.
Chris: That doesn't mean we'd have to do something, but we should, you know,
Chris: get together, have a beer, and discuss what we're going to do.
Chris: And maybe eat some food too. You know what I mean? We should probably eat some food too.
Brent: I mean, do listeners have ideas of what we should do? I'd be open to that.
Brent: I mean, we could party, we could road trip, we can go to space, whatever you want.
Chris: What? Okay. All right. Okay.
Wes: The suggestions have to come with funding proposals.
Brent: Well, Moon and I boosted in 5,135 sats.
Brent: Now, this is a live boost from a train running under the San Francisco Bay,
Brent: 135 feet below sea level. Is that a new record?
Brent: I wonder what the record is for lowest and highest elevation. Live boost, anyone?
Chris: That's got to be it. At least below sea level, 135 feet below sea level live during the show.
Wes: Impressive.
Chris: I bet you somebody could beat them on altitude for sure.
Wes: And, you know, we welcome all elevation boosts.
Chris: This is a great idea. If anybody is above 1,000 feet, we're at sea level right
Chris: now. So if you're above us, boost in and let us know your elevation.
Chris: I wonder if anybody's on a mountain out there. And can I come live with you?
Chris: Thank you, everybody who boosts. We have the 2000sat cutoff just for on-the-air
Chris: timing and all of that, but we save all of them in our show notes and we read them.
Chris: We also had a nice batch of you stream. 24 of you just streamed those sats as you listened.
Chris: You collectively stacked a nice humble 21,058 sats for the show.
Chris: It's not a strong week for us, but, you know, it's a showing up,
Chris: and it's still appreciated.
Chris: The episode, which gets split between myself, Wes, Brent,
Chris: Editor Drew, the podcast index, and the creator of the app, we all
Chris: collectively stacked 153,802 sats
Chris: thanks to you that's like an investment in the future of the show and we really
Chris: appreciate that and of course it's also a signal if you like that episode gives
Chris: us an idea of what content really works for you there's no better vote than
Chris: a boost and you can use fountain fm to do that or albi hub there's lots of options there.
Chris: And thank you to our members, our core contributors, and the Jupyter.party.
Chris: You put that support on Autopilot, and it's our foundation. We appreciate you
Chris: very much. Thank you, everyone.
Chris: And we do have some picks before we get out of here. And we've mentioned this on air once before.
Chris: It was a sly mention, but it's never made it into the pick category.
Chris: And I need to elevate it up because the team's done great work.
Chris: It's a very useful application, and it's got a great name.
Chris: They had a release on September 8th. It's called Duff, D-U-F,
Chris: and it is a free disk usage utility that is, I think, the best visualization,
Chris: especially if you've got some media shares or photo shares.
Chris: If you have a NAS and you need to kind of get your head around what on your
Chris: NAS is eating up a bunch of space, Duff is the way to go.
Chris: It's MIT licensed, and they've just been doing great stuff.
Wes: And so think less DU, more DF in terms of where its role is.
Wes: Because you get just a really nice breakdown of what file systems you have mounted,
Wes: including like it'll call out special devices, like places like slash dev and
Wes: slash run and slash sys differently.
Wes: So then you kind of get to see like your actual more physical real disks all in one place.
Wes: Handy rendering in the terminal, including like little progress style bars to
Wes: indicate how full your disk is, color coded. It's just really easy to read.
Chris: And a nice breakdown. Also, like the type of the file system is so handy to
Chris: have just right there. I just love that.
Chris: And you'll love this Wes, outputs to JSON, packaged for just about all the distros
Chris: you might possibly want, including Arch and Nix, Fedora and Ubuntu and others.
Chris: So Duff, D-U-F, that's the first pick.
Chris: But we've kind of fallen into this habit of having more than one pick because
Chris: there's so much good stuff these days.
Wes: A cup runneth over.
Chris: It does. And this one's a little bit different. It's called cheat.sh,
Chris: and it bills itself as the only cheat sheet you will ever need.
Chris: And the idea is you install this on your machine, and you forget a command,
Chris: and you use cheat sheet to pull it up.
Chris: And one of the things that the project talks about here is they focus on crazy great performance.
Chris: Like they want it to be back with an answer in like you know two milliseconds
Chris: or something like that and it covers 56 different programming languages a thousand
Chris: of the most important Unix and Linux commands a bunch of other stuff is in there,
Chris: and it's called cheat.sh it's pretty nice and I think it's probably one of the
Chris: handiest tools I've seen in a while it's mostly written in Python,
Chris: and did I mention it's MIT licensed I'm not sure if I did or not No.
Wes: You got the last one, though.
Chris: Yeah.
Brent: Now, Wes, on our call yesterday, I specifically remember you disabling,
Brent: was it man pages on the Hypervibe?
Brent: I was wondering, would you install this instead?
Wes: You know, I haven't. That's a good question. As long as you have a system that's
Wes: constantly connected, yeah, it might work pretty decently.
Chris: Yeah, you want to be able to look up. It's very fast, but it does require internet
Chris: connection, so there's that.
Chris: It can be used on the command line for command completion. It could be used inside code editors.
Chris: They aim for sub 100 millisecond response times, so you don't have to sit there and wait for it.
Chris: I think there might be a way to do it. Yeah, there is a way to do it offline
Chris: as well. You can store it for offline.
Wes: Oh, that's nice.
Chris: I thought so. Yeah, it's pretty great. So it's called cheat.sh.
Chris: So two great apps we'll have linked in the show notes, D-U-F, Duff, and cheat.sh.
Chris: Yeah, I'll be honest. I've been leaning into these types of things recently
Chris: just because like fish showed me the way.
Chris: And if I can get another fish-like experience that makes it just,
Chris: oh, yeah, that command I do every six months.
Chris: That kind of stuff love that love things that make that simpler i don't remember
Chris: all that stuff like i used to
Chris: i want to print out a cheat sheet actually and put it to my monitor just.
Wes: Like all that for learning neovim.
Chris: Well done sir well done maybe one day wes you never know could always be a challenge well.
Wes: Maybe with the lm helping you it'll go a little.
Chris: Easy nice nice i think that's a burn i think that was a sick burn actually call.
Brent: It a burn.
Chris: Yeah but topic relevant oh Well, let's see. What should we tell people about?
Chris: Should we tell them about our fancy features that we have?
Wes: Yeah, absolutely. Not only do we have chapter markers, you can go right to the
Wes: stuff that you like or don't like or skip around or listen in reverse order. I don't know.
Wes: We also have transcripts of the whole thing with who said what dumb stuff.
Chris: Yeah, and a lot of that stuff is compatible with the OG podcast apps,
Chris: the 1.0 apps. We'll bake it into the MP3.
Chris: And if they support the standard for the...
Wes: And TenantPod does a great job with the transcripts.
Chris: Yeah, TenantPod's great for the transcripts. If they support the transcript
Chris: standard, like Apple, actually, Apple Podcasts does of all. They support the transcript standard.
Chris: So it just kind of depends on the player. And then if you have a nicer 2.0 player,
Chris: you get even more features.
Chris: You get better chapters. You get perhaps more features with the transcript depending on the client.
Chris: And then additionally, you get the lit support and potentially the boost support too.
Chris: So check us out. Yes, we are live. We do a Sunday, Tuesday show.
Chris: Sundays, 10 a.m. Pacific, 1 p.m. Eastern over at jblive.tv.
Chris: We have that mumble room, too. You can join us. There's always more in that
Chris: mumble room. And if you're a member, be sure to get the bootleg version.
Chris: It's clocking in at over an hour and 42 minutes right now of content just for our members.
Chris: Now, links to everything we
Chris: talked about today, those are over at linuxunplugged.com slash 639. Woo!
Chris: Woo! Almost to 640. How about that? Also, our RSS feed, our contact form, all that good stuff.
Chris: Matrix room, all linked over there. You can find it. It's a website.
Chris: It's got links. You're going to love it. Thank you so much for joining us on
Chris: this week's episode of Your Unplugged Program.
Chris: And we're going to see you right back here next Tuesday, as in Sunday.