Chris: Hello, friends, and welcome back to your weekly Linux talk show. My name is Chris.
Wes: My name is Wes.
Brent: And my name is Brent.
Chris: Hello, gentlemen. Well, coming up on the show today, we have some big news stories to dig into.
Chris: Then I'm going to tell you how my hyper-tuned play toy has turned into something
Chris: that's maybe the real deal.
Chris: And then we'll round out the show with some great boosts, a whole rack of picks,
Chris: too many picks, and a lot more. So before we go any further,
Chris: let me say a time-appropriate greeting to our mumble room. Hello, VirtualLug.
Chris: Hello, Chris. How are you? And hello, Brent. Hello. Hello, Dave.
Chris: Nice to see you. Everybody camping out there in the quiet listening.
Chris: And shout out to our live matrix as we go along, too.
Chris: And, of course, Define.net slash unplugged. Go meet Managed Nebula from Define Networking.
Chris: It is a decentralized VPN built on the open-source Nebula platform that we love.
Chris: And I'll get more into that in just a moment. But Nebula is really something special.
Chris: It's super fast. It's simple. And it has industry-leading security.
Chris: Nebula's decentralized design means that your network is resilient in a way
Chris: that the other providers just cannot offer or manage.
Chris: And you can go from just a home lab all the way up to a global enterprise.
Chris: It was originally developed back in 2017 to securely connect Slack's global
Chris: infrastructure, which is all over the place.
Chris: And they've got, like, the world's trade secrets in their system.
Chris: So they had to have it secure.
Chris: Nebula was engineered to scale, perform, and be secure from day one.
Chris: And this, okay, what I love is that it's truly top to bottom an open source platform.
Chris: Right? So if you're building your whole network infrastructure on this,
Chris: you could do all of it yourself, open source.
Chris: But it also means that you can watch development and see where things are going.
Chris: And there's an issue that has been in the works since October of 2022.
Chris: And it's a nice little win for the Nebula community because they've begun testing this upstream now.
Chris: And it allows Nebula to support multiple UDP source ports, i.e. multiport support.
Chris: And this is no small feat. Like this has been challenging for WireGuard in general.
Chris: And this week the work was finished upstream. Now it's not shipping.
Chris: They're still looking at it.
Chris: But what it means is this new multiport support means that you can tunnel a
Chris: whole range of UDP source ports instead of just one.
Chris: And that spreads the traffic across multiple flows.
Chris: So if you've got like a cloud provider that's limiting you, or maybe you're
Chris: on a connection like Starlink that's throttling you, you can kind of spread that out now.
Chris: They're running through the test. It's not shipping, but oh man,
Chris: does it look good. And the payoff is better reliability on these connections too.
Chris: And in the thread of the PR, there's some massive gains noted.
Chris: They write, I suspect that Verizon was throttling individual UDP streams.
Chris: So this proved that to be true. I went from 50 megabits to one gigabit by using
Chris: a 4X multiport configuration.
Wes: Whoa.
Chris: Yeah. So it's one of those things where as somebody who's planning their infrastructure,
Chris: it's really nice to see this stuff coming.
Chris: You can watch this from 2022 all the way to today where they're working it out.
Chris: They're testing it. They're documenting the results.
Chris: They're discussing if they should ship it. It's all right there for the world to see.
Chris: And you can trust it when you build on top of that because it's open source
Chris: and that's all just out there in the open.
Chris: And they make it completely hassle-free with their managed product.
Chris: Nothing else has the resilience, speed, or scalability.
Chris: Get started with up to 100 hosts, absolutely free, no credit card required.
Chris: Go to defined.net slash unplugged.
Chris: That's defined.net slash unplugged.
Chris: Okay, so we are planning our Texas road trip. We're still looking for anybody
Chris: who would like to help us go there and do our coverage.
Chris: So reach out to me, Chris at JupyterBroadcasting.com if you'd like to work together.
Chris: And we have been considering a just after the fest meetup.
Chris: And I want to know if there's interest because it's specifically for people that are road tripping.
Chris: We haven't really figured this out, but we figure towards the end of Texas Linux
Chris: Fest or the day that we're leaving, as we're going out of town or something
Chris: like that, We set up for a breakfast and we have one last goodbye.
Chris: We usually do these things like before the events or during the event,
Chris: but I thought, wouldn't it be kind of fun?
Chris: So if you want to join us, reach out, boost in or send us an email and say you'd
Chris: be interested in doing like a after the festival meetup kind of thing.
Chris: And if we get a few bites, we'll put something together like Brent over there.
Chris: He's putting something together right now.
Brent: Sure am i've been thinking the last couple weeks that
Brent: i might consider crashing the september 20th
Brent: meetup of the jb crew in toronto but i
Brent: want to know would people show up if i end up in that neck of the woods maybe
Brent: i can convince i don't know other jb friends to show up too so uh let us know
Brent: if you'd be interested in a brent crashing september 20th in toronto and uh if so,
Brent: please go to our jb colony events website there's a little posting there of
Brent: the location and uh if if you don't mind register your attendance and let us
Brent: know if that would be interesting to you.
Wes: I guess we got to get some tickets huh chris.
Chris: Yeah we better i mean i don't think actually we were technically invited yet west so true.
Brent: Let us know if you'd like us to invite chris and maybe.
Chris: Don't uh but yeah colony events.com and we will have a link in those show notes,
Chris: All right, so let's do a news update. It's been a minute, and there is a story
Chris: that we sort of have a midway update on, and it's BcacheFS's inclusion in the Linux kernel.
Chris: And while things are still very much in development and the situation is fluid,
Chris: as things stand right now, it is possible that Linux may lose out on the next
Chris: big file system, not because of code issues, but over a clash of personalities.
Chris: And Linux 6.17 is out, but without the BcacheFS updates.
Wes: Yeah, just to be clear, it's not that 17's out totally, but we're in the RC phase now.
Wes: So that merge window has closed and no poll for BcacheFS.
Wes: And it's all kind of unfortunate timing because BcacheFS core developer Kent
Wes: Overstreet passed guest on this program.
Wes: Well, he mentioned that he'd planned for BcacheFS to actually shed that experimental
Wes: label in 6.18, the next kernel.
Wes: But, unfortunately, disagreements over his criticisms on the LKML about the
Wes: ButterFS file system, well, that ended up turning into a rather heated exchange
Wes: on the mailing list this past week.
Wes: Meta's Yosef Bacik has done a ton of great work on ButterFS,
Wes: called Kent's behavior unacceptable, and the ext4 maintainer Ted So went further,
Wes: saying, many developers see him as, quote, toxic, and want his code removed.
Wes: And Ted was clear, not for technical reasons. It seems like actually most of
Wes: the folks in this thread respect Kent's technical chops and BcacheFS,
Wes: you know, just as a code base.
Wes: But for Kent's style of communication and his conduct, and in particular here,
Wes: criticizing other file systems in the kernel.
Wes: Now, Kent has promised to stop criticizing ButterFS, but the fallout makes it
Wes: even more likely that BcacheFS won't be seeing any advances or maybe even not
Wes: continued acceptance in the kernel.
Wes: You know, it kind of seems like this dispute is highlighting a long-running
Wes: issue we've seen for years in the development of Linux, which is sometimes,
Wes: you know, it's not just about the technical decisions.
Wes: That can actually be overshadowed by personality clashes, politics,
Wes: and just people having to try to work together in the open across the world,
Wes: maybe without really even knowing each other.
Wes: And that can actually leave users in a lurch. You know, you might not get the
Wes: tool you want, not to technical reasons, but because of people.
Brent: Now, we thought Liam over at the register put it pretty well.
Brent: It looks likely that Overstreet has upset too many important,
Brent: influential people and hurt too many feelings.
Brent: And as a result, Linux is not going to get a new next-gen copy-on-write file system.
Brent: It's a significant technological loss, and it's all down to people not getting
Brent: along, rather than the shared desire to create a better OS.
Chris: I think that is well put. I'm on the record of thinking this is an extremely
Chris: important file system for Linux.
Chris: And my takeaway is, and I say this, I don't like saying this at all because
Chris: I have so much respect for the individuals involved. They're really titans.
Chris: We stand on their shoulders and, you know, they're smarter than me.
Chris: They've accomplished more than me.
Chris: They're great individuals. And yet,
Chris: as happens to anyone who is in a position of power and maybe some comfort for
Chris: a while, they lose touch with the people on the ground and they become more
Chris: and more out of touch over time.
Chris: And I think we're seeing the signs of that right here. And I get no joy in saying
Chris: this, but they don't have the hunger to make Linux competitive anymore.
Chris: And they don't understand the situation out here on the ground or facing because
Chris: they don't deal with these things anymore.
Chris: I would bet you if you polled them, most of them are probably using Extended 4.
Chris: So the people that are probably perfectly comfortable with the way things are
Chris: right now are put in a position to make a decision over personality conflict.
Chris: And it makes the operating system less competitive. There will be ways to run
Chris: BcacheFS, and no doubt we will cover those ways and we will use those ways.
Chris: But when you don't include it in the kernel, you are going to always exclude
Chris: a certain niche of users, maybe embedded systems or something like that.
Chris: And it doesn't provide the level of guarantee that a file system built into
Chris: the kernel does when you do upgrades and, you know, update your bootloaders
Chris: and your kernels and your whatnots.
Chris: So it's a downgrade in functionality for what is a very competitive and impressive file system.
Chris: And this was going to be one of the answers to not having ZFS in the kernel.
Chris: This is another issue that the kernel developers have been ignorant,
Chris: arrogant, and out of touch on.
Chris: And so Bcash FS was a solution to this that took the pressure off of the ZFS issue.
Chris: But they're too blind by their own egos to appreciate the stakes here.
Chris: We literally are making decisions based on feels now. And my last point on this.
Chris: The tone is set from the top. You set the tone from the top.
Chris: And Kent is being persecuted for things that are no worse than have been said
Chris: by Ted or Linus themselves.
Chris: Just two weeks ago Linus told an individual that their code made the world a
Chris: worse place you set the tone from the top so how do you persecute Kent who hasn't
Chris: even said anything that hostile,
Chris: when the leadership acts like that all the time and if we zoom out over the
Chris: 30 years of which Kent is familiar with,
Chris: the dialogue was even more let's say robust,
Chris: so we have 30 years of the tone being set from the top.
Chris: And then all of a sudden, we just shut the door on that. And as a result,
Chris: everyone listening to this podcast loses out.
Chris: Everyone running Linux. And there's not even a good technical reason.
Chris: This is where we're at now.
Chris: It's pretty embarrassing. That's my take, at least. Hopefully this gets worked out.
Chris: It's still, you know, it's an in-fluid situation.
Chris: It's a dynamic situation.
Wes: So there was some talk in it. I guess to hear Kent talk, it almost happened
Wes: that for 6.17, he was able to find an intermediary, you know,
Wes: to sort of be the person interacting with the mailing list that wasn't Kent.
Wes: But of course, that's a tough job between being acceptable to Kent and knowing
Wes: and being able to work well with the upstream Linux community.
Wes: So that might be something we see in a future somewhere. And I saw over on the
Wes: BcacheFS subreddit, a ZFS dev coming over and chatting with folks there and
Wes: offering a lot of really constructive,
Wes: concrete advice about, you know, if DKMS or similar is going to be the main
Wes: way to run this file system for a while. There are advantages to that.
Wes: There are some tips were shared, which is great. It's not like this is pure
Wes: antagonism between all of these file system developers. I don't want that to
Wes: be the picture people get here.
Wes: And Kent has committed, it sounds like, to being, you know, pretty aggressive.
Wes: Of so there won't be a ton of lag issues so you know 6.17.0 or whatever you
Wes: know one of the first kernels that you might actually run should have good support.
Chris: Yeah so we can now have a long distance relationship with bcachefs i will.
Wes: Say too i just want to be clear like i don't think we're trying to say kent
Wes: hasn't done you know hasn't had issues here i'm not trying to defend all of
Wes: the statements by kent or say that there couldn't be a lot of improvements on that side too.
Chris: I agree but.
Wes: The end result is is definitely disappointing.
Chris: Yeah there's some frustration too that Kent couldn't have adapted his approach
Chris: and communication style much earlier in all of this there has been several off-ramps
Chris: along the way that he could have taken here and that I think is on Kent and
Chris: that's just my opinion so it's not all the kernel developers but there is just this,
Chris: I don't I'm gonna I'll punt it to the audience to tell me if you think I'm off on this but
Chris: I just think there is this extreme irony
Chris: in individuals who have been called toxic and are
Chris: now calling someone else toxic and it's just they're doing to someone what has
Chris: been attempted to be done to them and it's i don't like it i don't know boost
Chris: in you know my thoughts on bcashfs have been clear how do you feel about this
Chris: entire situation let us know because uh it's got me fired up.
Chris: I am hopeful that there will be either some sort of, like Wes said,
Chris: intermediary or a pretty straightforward approach.
Chris: Kent is all over the kernel development cycle, so I have no doubt,
Chris: like, the day that the kernel ships stable, he'd probably have an update. It's a solution.
Chris: It's one I shouldn't have to use, but it's a solution. Let's talk about something
Chris: kind of fun. This is interesting.
Chris: Ubuntu has committed to developing a new dangerous desktop image.
Chris: Yeah, they're calling it the Dangerous Edition. It's daily builds,
Chris: and all the applications are snaps pulled from the edge channel for the snap.
Chris: So it's the absolute newest, raw, most experimental snap versions.
Chris: And the idea here is to make it easier for devs to seed snaps during what they
Chris: call their spike development, kind of like their sprints, which can last for like six weeks.
Chris: And then they can focus deeply on one thing and this could be a time to get that stuff involved
Chris: recently that was done with tpm full disk encryption work and the next spike
Chris: is the desktop prompting client i suppose i think this is really interesting
Chris: obviously it's not meant for end users to run on the daily but,
Chris: I like that they're calling it the dangerous version, the Ubuntu Dangerous Desktop.
Chris: I think that's a great name.
Chris: And it really conveys like, hey, don't run this as your daily driver.
Chris: But if you need access or if you're working on something developing, this is where to go.
Wes: I think it's neat, too, because previously, right, this was all kind of work
Wes: that I'm sure many developers, people hacking on this stuff,
Wes: were doing already in various different ways.
Wes: So the more you do it faster and make it available upstream so that you have
Wes: a common shared base to start development from that's refreshed often,
Wes: I mean, that's just less work for more people, which is great.
Wes: We did get some more details here. Canonical engineer Tim Anderson of the Ubuntu
Wes: release management team had a nice summary of these new dangerous desktop images,
Wes: saying, quote, we're currently working on building what we're calling dangerous images.
Wes: They'll be the same as daily desktop images for the Devel series,
Wes: but all of the snaps will be on their respective edge channels.
Wes: This work is ongoing, and there's going to be some more news soon.
Wes: These images are intended to help developers who work on our seeded snaps.
Wes: During the TPM full disk encryption spike earlier this year,
Wes: all the snaps for daily builds were switched to edge to help those developers.
Wes: And these dangerous images will remove the need to do this in future spikes,
Wes: one of which starts on Monday.
Wes: For those who are unaware, within Canonical, we've started doing spikes this cycle.
Wes: Spikes are segments of the whole cycle, six weeks long, where members of varying
Wes: teams join together to focus on one topic, partially or entirely,
Wes: leaving behind their regular daily duties.
Wes: There was a spike just after the Frankfurt sprint, working on TPM-based full
Wes: disk encryption, and the next spike, which starts this week,
Wes: focuses on the desktop prompting client.
Chris: You know, imagine that for a moment. You know, you're going about your daily
Chris: job and then there's this six week period where you sort of leave behind the
Chris: daily grind and just focus on one thing.
Chris: It kind of sounds incredible, actually. I think I would love that.
Wes: Yeah, you know, you get some diversity in your workload. Plus,
Wes: I mean, it seems to make a lot of sense where normally these sort of cross-cutting
Wes: concerns, you know, you have to have new emails or, you know,
Wes: DM messages or team channels to try to pull people out of their daily work.
Wes: So this is some blessed time where everyone across the stack can focus on one
Wes: thing, which I mean, that seems pretty useful. Right.
Chris: You would presume everybody's on board with the idea so you could actually pull
Chris: it off, which is, that's probably the secret trick.
Chris: But we have a little bit more Ubuntu news, Brantley.
Brent: Indeed, from Pharaonics this time, we get a few extra details.
Brent: Knuckle is sticking to the promise of always shipping the latest upstream kernel.
Brent: That means Ubuntu 25.10 will launch with Linux 6.17, even if it is still an unstable RC release.
Brent: Now, this timing is tight. Ubuntu's kernel freeze is September 25th,
Brent: while Linux 6.17's stable release is expected September 28th.
Brent: So just a few days later, the kernel team says it'll likely ship the near final RC,
Brent: which should still be, they say, very close to stable and highlights in 6.17
Brent: include Intel's XC3 graphics by default on Panther Lake and other major hardware improvements.
Brent: So once 6.17 goes stable, Ubuntu will push it out as quickly as a stable update.
Wes: And we got a bit more from Brett Grombois on behalf of the Canonical Kernel team,
Wes: saying, With the recent release of Linux 6.16, we now have a much clearer idea
Wes: of when 6.17 is likely to be released, as of this writing being tentatively September 28th, 2025.
Wes: The current 25.10 release schedule has kernel freeze set at September 25th,
Wes: which means that there is a strong possibility that linux 617 will still be
Wes: in a final rc state at the time the kernel needs to be frozen for the 2510 final release they're.
Chris: Sticking to it.
Wes: Yeah it's impressive especially because you know i i feel like five years ago
Wes: you wouldn't imagine this would really even be possible.
Brent: This does feel quite bold from Ubuntu, which I like. I like this new flavor.
Brent: I think they're pushing the envelope a little bit compared to what's been done
Brent: in the last several years. And I'm looking forward to what's coming out of this.
Wes: I also think it speaks well for the kernel development process, right?
Wes: This is canonical saying we trust the kernel team enough to ship these RCs,
Wes: knowing that we can ship a stable and there's not going to be big regressions.
Chris: Yeah, that's true. Good point. And they're also, though, committing to shipping
Chris: that stable release basically as fast as they can, which does mean you're going
Chris: to get a new system installed, and then a few days later, you'll get an update.
Chris: So you might just wait a week or two and then upgrade. But I like that they're
Chris: doing this, and it is combined with a series of data points we're seeing come
Chris: out of Canonical, where there definitely seems to be a bit more focus behind the desktop now.
Chris: And pushing, like, we see this dangerous release, and now we see them committing to, okay,
Chris: you know, we're not going to hit the stable, so we're going to ship the RC,
Chris: but that means, you know, if you're using Intel Z83 graphics or whatever on
Chris: Panther Lake, you're going to be good to go here.
Chris: And when these are midterm releases between LTSs, I think that's a really smart strategy.
Chris: So props to see them follow through with it.
Chris: You know what? Promise made, promise kept. Now, one of my favorite tools that
Chris: I've been using for almost a decade, I think, just finally hit 2.0.
Wes: And that project is SyncThing. Yes, that's right, the thing secretly running
Wes: pretty much all of Chris's infrastructure.
Wes: It's finally hit version 2.0, the first release in a new series.
Wes: And, well, like any first release in a new series, users should probably expect
Wes: a few rough edges, because there are big changes under the hood.
Wes: For one, the database backend now uses SQLite instead of LevelDB,
Wes: and that means a one-time migration at first launch of this new release and
Wes: that might take a while if you've got a big database.
Chris: Uh-oh.
Wes: Logging has also been overhauled, structured entries per package log levels,
Wes: and a new warning level between info and error.
Wes: So that's going to be nice. But if you have filters or alerts based on the existing
Wes: logging format, those are going to need to be updated.
Chris: You know, what's funny is it seems like all these tools too are,
Chris: they're reinvesting in the command line interface again just after the two-week challenge?
Wes: Yeah, what's the deal with that? The command line interface has been modernized in SyncThing 2.0.
Wes: Long options now require double dashes. Some are renamed. Others got moved to subcommands.
Wes: Here's a nice change, too. Deleted files are no longer stored forever.
Wes: By default, they're forgotten after six months, though you can change that in a setting.
Wes: There's also no more default folder on First Startup, and SyncThing now uses
Wes: three parallel connections by default between devices. I mean,
Wes: that sounds like a good thing.
Chris: That's the way to do it. That is the way to do it. I have heard some reports.
Chris: I have not verified because I don't do this, but I've heard some reports that
Chris: SyncThing 2.0 might not be compatible with SyncThing on Android right now.
Chris: So verify that before you upgrade. I've heard some people report that.
Chris: I have not verified that.
Wes: Something else that might not
Wes: be so great, some older platforms are losing official pre-built binaries.
Wes: I don't know if this is like totally dropping support, they're just no longer
Wes: going to build these, but that includes Dragonfly BSD, Illumos,
Wes: Solaris, NetBSD, OpenBSD on 32-bit in ARM and Windows on ARM.
Wes: So maybe if you're on one of those, do your homework before trying to switch to 2.0.
Wes: There's also some new features here, including ED25519 keys for secure connections,
Wes: bandwidth limits for your LAN, and quick UDP port mapping support.
Chris: That's nice.
Wes: And of course, like any release, you've got dozens of bug fixes,
Wes: you've got other performance improvements, you've got all of that database work,
Wes: improvements to file syncing, improvements to the GUI and the TUI as we talked
Wes: about so maybe don't commit your whole infra to switching to it right away but
Wes: do go start playing with it and check it out.
Chris: Yeah I think I need to look at I think I need to look at it because I do run
Chris: it on a lot of systems one of the things I've done if I have also I've deployed
Chris: it I don't sync everything to it but I've deployed one on a VPS that I kind
Chris: of use as a go-between and then do multiple connections off of that because
Chris: the VPS as a super fast connection.
Chris: I really, really appreciate the Sync Thing project, and there really isn't a
Chris: lot of opportunity to talk about it because they don't have a lot of major releases,
Chris: which is sort of what generates the news cycle.
Chris: So it's nice to take a moment here and just appreciate something that's worked for me for over a decade.
Chris: I found it in the wake of BitTorrent Sync, and it's just been fantastic ever since.
Wes: It really has. And I think as, you know, folks who listen to the member stream
Wes: can attest, the fact that we haven't really heard you complaining about it in
Wes: the past five years says a lot about the project.
Chris: That's a good point. Well, boys, my week was really made when the Open Home
Chris: Foundation and Home Assistant made some big, big news.
Chris: So a little backstory here. I love Z-Wave. It's a wireless communications protocol,
Chris: and one of the reasons I really like it is it operates at the 800 to 900 megahertz range.
Chris: Here in the U.S. and Canada, it's 908.42 megahertz specifically.
Chris: And a lot of the alternatives, which are better in some ways,
Chris: like licensing, are worse in other ways that really matter.
Chris: Like they use the 2.4 gigahertz frequency, as we all know, a very busy frequency.
Chris: Even just turning on your microwave kind of blasts it out. It also doesn't travel
Chris: through walls as well as 900 megahertz does and doesn't quite reach the same distance.
Chris: But it really hasn't gotten much attention lately. They kind of made the QT
Chris: mistake where they had sort of a aggressive license and certification process at first.
Chris: And then they've rectified that over the years. But it left a window of opportunity
Chris: for competitors like Matter and Zigbee and others to emerge.
Chris: And I thought, OK, we're not hearing about it much lately.
Chris: These other things are out. They're open source. I really should start to adopt
Chris: them. And I started getting more and more gear there on these other protocols.
Chris: Started slowly accepting that my beloved Z-Wave was fading away.
Chris: But it turns out the truth is actually quite the opposite.
Chris: There was a big old Z-Wave Alliance member meeting in Austin,
Chris: Texas. And the news out of there is good, boys.
Chris: Home Assistant has a blog that shares a lot about the event.
Chris: But I pulled some highlights that I thought were interesting.
Chris: 10% of all Home Assistant users use Z-Wave. which is more than 1.7 million active devices.
Chris: And that's just a small percentage that actually submit their stats.
Wes: Of course.
Chris: And I think the key takeaway from the Z-Wave event is it isn't going anywhere.
Chris: In fact, it's seemingly thriving.
Chris: But the Home Assistant team in Polis, they really encourage them to open up further,
Chris: just really participate more in the community and they
Chris: put their money where their mouth is and they have released an
Chris: incredible piece of hardware for z-wave users and
Chris: if you're looking at home automation tap the brakes and
Chris: look at the home assistant connect zwa2 it is
Chris: their z-wave antenna and it is brilliant
Chris: first of all it's big but they have engineered the
Chris: absolute snot out of this thing the results are
Chris: incredible so it's 69 us 59 euros
Chris: it's designed to really give you the absolute optimal range
Chris: possible they've had some incredible incredible experiments now of course there's
Chris: two to tango so your device you're communicating to us to have a decent antenna
Chris: and this also supports the z-wave long range protocol which is extremely fast
Chris: and it's built on the new Z-Wave 800 chip.
Chris: Which is, it's like a whole new SoC, essentially. It's not quite the same thing, but it's way faster.
Chris: And the nice thing is, is because it's made by Home Assistant, it's a seamless setup.
Chris: You plug it in, Home Assistant detects it, it knows your region automatically,
Chris: it guides you through a setup, it'll guide you through migrating to the new one.
Chris: It's open, it's hackable, it's absolutely all offline, privacy first.
Chris: Open firmware files, you'll get over-the-air updates to it, no cloud reliance at all.
Chris: You buy it once, and then you own it, and it looks great.
Chris: The base looks a lot like their voice preview box, and then it goes up into
Chris: this antenna where they've built this really powerful antenna inside,
Chris: and then on the top it has a little LED light that tells you the status,
Chris: which you can also turn off.
Chris: It really, I think, is going to up the reliability of a Z-Wave network,
Chris: and this is going to slow my role on all the other protocols so much.
Chris: I was starting to really start going to Zigbee and Z-Wave, and I could not make
Chris: Zigbee as reliable as Z-Wave.
Chris: It's just not the same level. And then I started putting more devices on Wi-Fi,
Chris: which isn't great either.
Chris: So to be able to rely on Z-Wave again, to see their investment in this,
Chris: to see this hardware, I pulled the trigger immediately.
Chris: It may arrive today, actually, during the show. And I was recently talking on
Chris: the podcast here about wanting to redo my Home Assistant setup.
Chris: And I was concerned about the Z-Wave migration. Well, problem solved.
Chris: I'm going to plug this into my Home Assistant.
Chris: I'm going to migrate to this thing. And then I'll unplug it and plug into the new Home Assistant.
Chris: And it's a gorgeous piece of engineering. And they have some YouTube videos,
Chris: which I'll link in the show notes. The range demonstrations are absolutely bonkers.
Chris: So if you have a large garden or even a farm, you could actually put sensors
Chris: and devices way out there and they'll still communicate with this thing,
Chris: especially in long range mode.
Chris: They were seen in testing up to 1.5 kilometers.
Chris: Really incredible. And to see the whole combination, they support the open source
Chris: community, the open development.
Chris: They're paying for one of the developers to continue to contribute to that.
Chris: And now they've released this piece of hardware that is open and hackable, all offline.
Chris: Love to see this kind of stuff. This is it.
Chris: And the Home Assistant platform is going from fantastic win to fantastic win,
Chris: both in software features and hardware devices.
Chris: They're selective about the hardware they release.
Chris: They're super laser targeted. And every time it makes a ton of sense.
Chris: And every time it's just validating to be in this ecosystem when I see this kind of stuff.
Chris: And they've gotten to the point now where it's like they release a piece of hardware.
Chris: I know it's going to be great. I know it's going to work with Home Assistant
Chris: super easy. And it's not like they're using their own private,
Chris: you know, a la AirPod style way to connect it.
Chris: Like the technology they use to make this work tremendously seamlessly with
Chris: Home Assistant is available to any vendor in any hardware device.
Chris: And it's all open standards.
Chris: I don't know if you can tell, but I'm kind of excited.
Wes: Whatever happened to Matter, can I ask? Because I thought for a minute you were
Wes: checking that out too. And I haven't heard much after kind of some initial excitement.
Chris: You know, it's still, it's, you know, it's still, you know, it's out there. It's been slow to adopt.
Chris: And most of the implementations, although not required, most implementations just use 2.4 gigahertz.
Chris: So it's kind of like just a new version of Zigbee. And it has a lot of the core
Chris: problems that 2.4 gigahertz has.
Chris: And so at the end of the day, like there's other ways to do it.
Chris: There's a thread pro. There's other ways they can implement it with Matter.
Chris: The spec allows for that. But you can even use Bluetooth.
Wes: But it's up to manufacturers to actually choose to go that route.
Wes: And with Z-Wave, you kind of get that by default. Okay.
Chris: Yeah. And, you know, this whole stack, right? It's all open source.
Chris: It's a lot of it's Python based. And then it's running on top of Linux.
Chris: And then the hardware you connect is open.
Chris: And it's backed by the Open Home Foundation, who has the super long-term view of this.
Chris: So it's the exact 180 from buying some cloud-connected smart device off of Amazon
Chris: or from Costco that lasts for three years, and then you've got to throw it away,
Chris: and you have to sign up with their app and their cloud service.
Chris: It's the 180 of all of that, and it's exactly the kind of thing you want to put in your home.
Chris: You want to put something in your home that's going to last a decade, right?
Chris: If you put that in the wall or you put that somewhere where it automates that
Chris: thing, you want it to last as long as the house lasts.
Chris: That's my goal. Everything I'm building that I put into Joops,
Chris: I don't ever want to tear out again. I want it to last forever.
Chris: So everything has over-the-air updates now.
Chris: Nothing requires a cloud account. Nothing requires an internet connection to function.
Chris: All of it works offline. All of it works without me having to open up any other
Chris: apps other than Home Assistant. No other apps on my phone.
Chris: And it's not that hard to get there anymore with these hardware devices they're
Chris: releasing. It's powerful stuff, boys. It's a good time to get into Home Assistant.
Chris: 1password.com slash unplugged that's
Chris: the number one password.com slash unplugged all
Chris: lowercase go take the first steps to better security for your team by securing
Chris: credentials and protecting every application so go learn more at 1password.com
Chris: slash unplugged if you are in security if you are in it if this is your world
Chris: then you know about the mountain of assets that you have to protect more than
Chris: ever, devices, identities,
Chris: and applications.
Chris: And the more applications, the more security risks you have.
Chris: That's where 1Password Extended Access Management comes in. This is a growing
Chris: problem. You're not the only one.
Chris: Over half of ITPro surveyed said that when they were asked what their biggest
Chris: concern was, it was SaaS sprawl.
Chris: It was securing these SaaS applications, especially the ones they don't even know about.
Chris: That quickly becomes your responsibility.
Chris: Well, Trelica by 1Password can discover and secure access to all your apps,
Chris: the managed and the unmanaged apps.
Chris: Trelica by 1Password inventories every app in use at the company.
Chris: And then it has pre-populated app profiles that it can assess the different SaaS risks.
Chris: It lets you manage access, optimize spend, and enforce security best practices
Chris: across every app your employees use.
Chris: Yes, you can manage shadow IT. When I used to show up as a contractor to these
Chris: companies and get on their network, I mean, nine out of ten times,
Chris: the IT would be completely ignorant to the fact that a new device was on their
Chris: network wrecking havoc.
Chris: I mean, of course, I was supposed to be wrecking havoc.
Chris: This is the difference, though, now. We have this whole new generation with
Chris: 1Password Extended Access Management and Trelica by 1Password.
Chris: It's a complete solution for SaaS access governance. And it's just one of the
Chris: ways that extended access management
Chris: helps teams strengthen compliance and security at the same time.
Chris: One does not have to take away from the other.
Chris: 1Password's award-winning password manager, which is trusted by millions,
Chris: over 150,000 businesses like IBM and Slack, well, now they're securing more
Chris: than just passwords with 1Password Extended Access Management and Trelica.
Chris: So go check it out. Go to 1Password.com slash unplugged.
Chris: Be the IT hero in your corporation. Take the first step to better security for
Chris: your team by securing credentials and protecting every application,
Chris: even the unmanaged shadow IT.
Chris: Go learn more. Support the show. Go to 1Password.com slash unplugged.
Chris: That's 1Password.com slash unplugged.
Brent: Now, Chris, last week you featured your brand new desktop, all riced up and looking delicious.
Brent: And I feel like you weren't quite done with that.
Brent: Based on our private chats this week, it sounds like most of your free time
Brent: went towards continuing that project.
Brent: What is going on over there?
Chris: Yeah, remember how I said I was not going to mess with it anymore and I was
Chris: done and I was just, you know, I got it out of my system and I was just going to move on.
Chris: That wasn't true. No, no, no, that was not true at all. In fact, it's getting serious.
Chris: I'm ready to take this thing home to mom and dad for dinner.
Wes: Whoa, whoa, whoa. Yeah. What is that? Okay, so when we were at Red Hat Summit,
Wes: you kind of bailed ship. You went whole hog on a U-Blue lifestyle.
Wes: What does that mean?
Chris: I think it means the grand experiment, which was a lot of fun.
Chris: The days on Bluefin are over.
Chris: I liked it but i think when you hear where i ended up everyone will understand
Chris: i kind of you know i i want to take a moment and i want to blame two people
Chris: specifically if i could for this i'm.
Brent: Not taking the blame on this one.
Chris: Because i was happy i was living in this blissful world where i didn't need
Chris: to tweak my system much i didn't need to worry about performance that much yeah.
Wes: That's because soltros os did all the work for you.
Chris: Right soltros os comes along and does the work and I'm like oh man you can move
Chris: the needle on some of this stuff you know you can make a few adjustments here
Chris: and make a noticeable improvement in like the application launch time like oh
Chris: of course that makes me start wanting to tweak it a little bit more and then
Chris: DHH comes along with his Alma Archie,
Chris: and finally shows me a Hyperland that I can appreciate,
Chris: And I just, I think I just slipped into this, I'm going to build a Hyperland
Chris: desktop that works for me.
Chris: And it also coincided with after a summer of travel, I finally set up my home
Chris: desktop PC again, which still runs an XOS because it's just been packed away.
Chris: And if you caught last week's episode, you know I ended up vibe-ricing my way
Chris: into a pretty, pretty sweet Hyperland desktop.
Chris: And since last week, I went from like a silly, couldn't I even do this MVP self-challenge
Chris: to like, now it's my dream distribution.
Chris: And I think it's actually worth wider testing and other people should try it.
Chris: I've been using it and refining it for over a week. And I actually think there's
Chris: even a market fit for a distribution like this.
Chris: And I know I'm going crazy here, but I have been seeing post after post recently
Chris: on the Mastos and the Xs about how people wish somebody would come along and
Chris: do an opinionated Oma Archie style Hyperland setup on NixOS.
Chris: And I'm seeing a couple of people take a stab at it, But I think I might have the best one.
Chris: Humbly I say, because it's not only the best-in-class open-source desktop applications
Chris: that are through just years and years of us looking at all the different apps
Chris: and using all the different things and reviewing all the different desktop environments,
Chris: all the thousands of hours that I've done all that, that have gone into just
Chris: the decisions on the apps that I'm picking with this Hypervibe,
Chris: but I have done just bonkers out-of-the-box
Chris: performance that I've been slowly building on for the
Chris: last year um like for example i'm using
Chris: the zen kernel which just as a quick aside is
Chris: a great desktop kernel that i don't understand why more
Chris: desktop distributions don't ship it's optimized with low latency patches to
Chris: reduce input output processing delays which improve the overall feel of your
Chris: desktop and gaming experience it makes it feel like your desktop more responsive
Chris: it's using the bfq the budget fair queuing scheduler which gives you smoother
Chris: multitasking in a desktop environment Also.
Chris: Disk I.O. is better optimized for a desktop environment.
Chris: And it's tweaked to have a more responsive CPU process scheduler that benefits
Chris: multitasking workloads.
Chris: It has preemption and real-time support if you need that.
Chris: And there's a lot of little kernel parameters that have been tuned in there
Chris: that just favor multimedia playback and desktop performance out of the box that
Chris: you just get by using the Zen kernel.
Chris: It also supports ZRAM, which I'll get to in a moment.
Wes: I'm so glad you're finally here because we did, I don't remember exactly when,
Wes: sometime in the last year, we did some dabbling. We were trying the licorice
Wes: kernel and a few other, you know, tweaks, especially looking at getting low
Wes: latency audio because, you know, we do a lot of audio work here.
Wes: So since then, I've been just using the Zen kernel. I've seen no reason to switch off.
Wes: And like you're talking about with the IO stuff, I mean, I've used desktop Linux
Wes: long enough to know like you're doing some big transfers or other stuff with
Wes: a lot of file operations and your desktop can get kind of laggy.
Wes: And OK, it's not a huge deal, but that is just almost totally gone with Zen.
Chris: Yeah. Yeah. And so that's just the kernel, right?
Chris: And then in there, I've also utilized BPF to do auto-tuning, which is really nice.
Chris: And then there's just some housekeeping items that automatically happen.
Chris: The Nick store auto-optimizes and garbage collects every week.
Chris: I have out of memory for certain things ready to go.
Chris: Butter FS with FS trim and auto-scrub is set up even on root.
Chris: And the governor is set to performance mode at a default, but you can change
Chris: it. It's a Wayland-based system, and it comes completely loaded with Steam.
Chris: All wired up with game scope, which if you know what that is,
Chris: you realize why that's a big deal.
Wes: What? Oh, I missed this in our notes. Oh, okay.
Chris: Oh, yeah. Yep. Oh, yeah. I got the Lutris in there.
Chris: I got all the wine stuff you need to play 64-bit and 32-bit wine games,
Chris: and it has Vulkan support for all that stuff.
Chris: Has UDEV rules for the controllers you might want to use with it.
Chris: Steam with hardware support out of the box, ready to go, all optimized.
Chris: Now, right now, the way it's built, it's,
Chris: It's tilted towards AMD, but it really wouldn't be much work to make it work with NVIDIA or Intel.
Chris: Got LibVert, Invert Manager out of the box. Docker's there with weekly auto
Chris: prune ready to go. And then it's a Hyperland desktop that I have customized the hell out of.
Chris: And so you have to build the entire thing. Everything from the toolbar to the
Chris: file manager to the launcher, everything.
Chris: So in here, Thunder's available, but I went with Dolphin.
Chris: And to make Dolphin really, truly functional, you don't need just Dolphin.
Chris: You need the KIO extras. You need the Fuse support.
Chris: You need the arc package or extractor and you need u-disc so that way you can
Chris: mount network shares all of that works so when you get dolphin it's a fully
Chris: functional dolphin clipboard support you know i had to add the right clipboard
Chris: manager right and a screenshot manager so you have all of that.
Wes: You're doing a lot of work just to get back to what plasma gets you out of the gate but.
Chris: It gives you a really.
Wes: Nice you know look at like what pieces do you want you can swap those out in
Wes: a lot easier way and you know since you got the vibe help you kind of can get
Wes: a nice set out of the gate and then tweak it from there right.
Chris: And it's a smaller subset right it's just you know a handful of the plasma packages
Chris: which is a lot smaller of a moving target this entire thing even after all this
Chris: work is so much leaner and meaner than a full genome cinnamon or plasma desktop
Chris: and so because of that there's a lot less that breaks and so,
Chris: less to break and the fact that we have rollbacks i have
Chris: gone all the way to the edge with this system it is
Chris: on nix os unstable and it is pulling straight
Chris: from hyperland's github yeah they have a flake so
Chris: they make that nice and easy and so this thing is
Chris: the absolute freshest packages and desktop
Chris: environment possible something goes wrong you roll back but so far two weeks
Chris: nothing's gone wrong and the terminal environment is an actual chef's kiss now
Chris: i know wes thinks it's a little weird but i have combined fish shell with a
Chris: tuin which i picked up from bluefin and it is.
Chris: A command line history tool that syncs across
Chris: your systems so you can have the same command history
Chris: if you want with support for multiple systems and all of that and
Chris: it displays in a really nice list anyways that is
Chris: combined with fish shell to have just a fantastic tool
Chris: set on the command line i've designed it so your secrets
Chris: like your github token they exist outside the github repo they exist outside
Chris: the config and i've put a lot of polish into waybar to put media controls in
Chris: their bluetooth integration brightness control network mount information gpu cpu load,
Chris: All that kind of stuff is laid out in there.
Chris: A playback, you can play and pause media controls and get a list of what's playing.
Chris: You get open window notifications. And there's a system tray.
Chris: I even have a system tray. So if you've got a chat app or something like that
Chris: that has a system tray icon, it actually shows up in there.
Chris: And it's so fast. It's between the optimizations I've done at the core and Hyperland,
Chris: which was built from day one to just be as smooth as possible on Wayland.
Chris: And then you combine it with a high refresh rate monitor it's and then fully
Chris: vulcan accelerated desktop i mean it's it is the nicest setup i've ever had
Chris: and it's on like a 300 b-link it's ridiculous i cannot imagine how great this
Chris: would be on a brand new high-end system.
Wes: Okay so i'm just going to ask about that you've kind of been developing this
Wes: on one system have you made any attempts or do you have any plans to use this
Wes: like you know on your office workstation or on a studio machine or,
Wes: you know, some of your other setups.
Chris: Absolutely. And I'm trying to build it to be machine agnostic.
Chris: So there is a per machine configuration support in this.
Chris: So you'd like, right, I have my machine at home. I call it RVB because it's a B-link in the RV.
Chris: And that's just dropped inside a host folder. And you can put your different
Chris: hosts in there. And then you just on that machine, your configuration gets pointed to that.
Chris: But I would love ideas because I'm seriously think other people should try this.
Chris: Because this is probably the opposite of Bluefin. It is everything turned up to 11.
Chris: It is the absolute latest packages. It's using all the latest technology to
Chris: put all this together. You've got rollbacks in here.
Chris: You've got massive performance optimations that squeeze every bit of performance
Chris: out of your system that it can possibly provide, optimized for a desktop session.
Chris: And last but not least, built on top of Hyperland and the way Waybar works,
Chris: I've been able to recreate a lot of the functionality of GNOME extensions without GNOME extensions.
Chris: They're really just like Bash or Python on the back end, and they're really
Chris: simple, and they just put out plain text that gets inserted into the Waybar,
Chris: and there's essentially a CSS-style layout that you tell where to go in the Waybar.
Chris: And why I bring that up is because it's nearly unbreakable, at least compared to GNOME extensions.
Chris: Clearly, the Waybar developers could mess it up.
Chris: But it's just so simple that it's likely to persist through upgrade after upgrade
Chris: because we're just executing bash on the back end and then just getting text output.
Wes: You might not be able to do technically as much with whatever the deep hooks
Wes: into GNOME that you could do with extensions, but for all the stuff,
Wes: you just kind of want to display stuff in a bar.
Wes: Yeah, right? You don't have to deal with all the interface changes that can
Wes: happen between GNOME releases anymore.
Chris: You know, like an example is I like having just a small little icon in my bar
Chris: that is a screen sleep inhibitor.
Chris: So I can hit that if I know my system is going to be going for a while and my
Chris: system won't go to sleep.
Chris: And then I can come back and hit it again. And now regular, you know,
Chris: screen and sleep modes are back enabled.
Chris: And to do that, you need to get an extension in Gnome.
Chris: But that's actually, it's just commands. There's just commands getting executed.
Chris: And if you could just, you can just do that with a bash script and then put
Chris: an icon in the way bar for it with an emoji.
Wes: That is a great example. Yeah. You just need a thing that you can click and
Wes: then it runs a command. I mean, exactly.
Chris: Yeah, like player CTL is another great example. Like player CTL is a command
Chris: line tool to control any of the playback on your system.
Chris: And player CTL can pull metadata from applications like Firefox and,
Chris: you know, other applications of what's now playing and whatnot.
Chris: So if you just ran player CTL, and I think it's like dash dash metadata or whatever
Chris: you can get the, you know, commands, it'll tell you what's actively playing
Chris: on your system and what it knows about it.
Chris: And you can just capture that information and display it. You know,
Chris: it doesn't have to be a big complicated JavaScript mess that's tying in with
Chris: all this different stuff.
Chris: It can just be using player CTL on the command line. And so it's just a lot
Chris: more robust in the sense that it's going to survive upgrade after upgrade after upgrade.
Chris: So it's a system that's designed to just continue to run, regardless if you
Chris: update it every day or if you update it every month.
Chris: And I really think it's at a point where I just need more people looking at
Chris: it and finding the things that make it unique to my system.
Chris: Or finding the things that make it hard to distribute because it's about probably
Chris: two hours away from making it easily to distribute, maybe three or four hours
Chris: at most, and it could be universally distributable,
Chris: ideally like with an ISO image and an installer.
Chris: But there are things like I have my username and a couple of paths,
Chris: and there's a few other things that I have in my home.
Chris: There's a couple of things in there that are specific to my system that would
Chris: need variables and replaced or whatever on individual systems.
Wes: Yeah, I think if we combine like some refactoring on your upstream stuff,
Wes: and then I started taking a little look at how the NixOS ISO stuff is put together.
Wes: And I think we could get something where you could just, you know,
Wes: have the same graphical install experience, but at the end of the day, get HyperFive.
Chris: I love it. And it has also been a process of learning to use Hyperland and leaning
Chris: into the Hyperland workflow.
Chris: And then finally using a desktop environment that feels like my computers from 2025 and not 1998.
Chris: It's so smooth. And it really, because it's, I think, like everything that you
Chris: just think should work, works. Like, say you've got a game playing full screen in one desktop session.
Chris: You know, if I swap over to the other virtual desktop, nothing gets messed up.
Chris: I don't have weird stuff getting moved around or the game doesn't weird out.
Chris: Like, the mouse doesn't get stuck. Like, everything just...
Chris: Works like it should on a computer and it totally is irrelevant that i'm using
Chris: wayland is a benefit in this case because it's so performant i really am happy
Chris: with this and there's just no way i could use anything else and i want to move
Chris: it to my other systems i do have a couple of odd bugs that i also could use
Chris: help tracking down i created really basic prs for both of them is.
Wes: There like a term because these are vibe bug like is it a bug is there.
Chris: Yeah yeah i think so
Chris: so well i've kind of gone more manually editing now too now that i'm getting
Chris: more serious about it i've been making more manual tweaks oh you're taking over
Chris: maintenance huh a little bit some of them yeah so yeah yeah more and more yeah
Chris: it's funny because if you look at my github activity you can see when i'm really
Chris: jamming there's like there's periods where i'm just like commit after commit
Chris: after commit because i'm like oh this is great this is great i'm done now one more thing.
Brent: Wes can we take a moment here and just congratulate chris on like some ups on
Brent: sophistication here like he just said he's committing all of his versions to github this is.
Chris: The first time yes.
Wes: You've done this with your.
Chris: Next os i'm.
Brent: Seeing this like it's a flake with multi-host support this is fancy it's like
Brent: this whole week you've just like skipped a ton of steps towards uh getting way
Brent: more sophisticated i applaud you.
Wes: Before you know it he'll be a nix packages committer.
Chris: Necessity is also quite frequently the
Chris: mother of invention like like well if i'm gonna make this
Chris: usable by the audience i need to make this multi-host and
Chris: if i'm gonna be making these kinds of changes and i want other people to try
Chris: it i need to do version control and i need to have this up on a spot where other
Chris: people can see it and review it and then i was like i need to have a serious
Chris: readme too so then i went and redid to put a bunch of information in the readme
Chris: put a screenshot in there so people know how freaking rad it looks and.
Brent: You even have like a table here of key bindings.
Chris: This is really sweet.
Brent: You should do most of your like testing with the audience in mind. This is really great.
Chris: But I have a couple of bugs I need help tracking down. So I'm trying to do the
Chris: Hyperland desktop in a declarative way.
Chris: So you make your changes in one spot, which is in my home directory,
Chris: and then you build it and it deploys it to the proper locations where Hyperland
Chris: config and your Waybar config is supposed to be.
Chris: And the idea is, you know, you can centrally manage that.
Chris: And then next time you build, it just gets a new version.
Chris: It doesn't work. You just roll back. However, every now and then,
Chris: especially after I do a build and then reboot,
Chris: I come in and my key bindings have reverted to like one of the very early iterations,
Chris: that's almost more Ama Archie inspired.
Chris: I haven't like extensively tested this, but then if I build again,
Chris: I don't do like an upgrade, but I just do another build and boot and reboot
Chris: again and come back in, my config is back. It's the weirdest thing.
Chris: And I tried and tried to track it down. I'm not sure where it's at.
Chris: And the other issue that I could use some help tracking down is if I leave the machine for a while.
Chris: Like say I leave it on overnight.
Chris: Screen goes to sleep. Doesn't really matter if the screen goes to sleep or not.
Chris: But say the screen goes to sleep. I come back in the morning. I wake it up.
Chris: There's like a console output on the top. You can't highlight this text.
Chris: But there's just a series of errors on the top that seemingly are very helpful.
Chris: This is config error. And it says the path to my config file on line 69.
Chris: And it says config option declarative drop shadow does not exist.
Chris: And then same on line 70. However, I go in there, I fix it, or I look at it, I don't see an error.
Chris: And I check the logs, there's no error in any of the logs.
Chris: So I'm not sure where this error is actually coming from. It's very bizarre.
Chris: So these are the two issues. Other than that, I'm using it for work during the
Chris: day, and then my son is literally gaming on it all night long.
Chris: And we are I know this is not a huge deal because it's just Geometry Dash but
Chris: he's getting 300 he's maxing the game out at 360 frames per second at a 200
Chris: hertz refresh rate on a little B-Link and we're playing,
Chris: I'm playing Star Trek Resurgence or whatever it's called,
Chris: Star Trek Online on this thing we're playing multiple games on this tiny little
Chris: thing and it is absolutely keeping up with this Thaleo right now it's wild and
Chris: it did not start that way It did not start that way.
Chris: The frame rate was low. The screen was a little jerky, even though I had the
Chris: new monitor. It was having stuttering issues.
Chris: There was all kinds of little performance, like legs, that would happen,
Chris: and then it would speed back up again. And it was frustrating, the boy.
Chris: So, you know, while he was AFK, I set off on a mission to see if I could really
Chris: optimize the hell out of this thing.
Chris: And now it's, I mean, it's flawless in the gaming performance.
Chris: You know, within reason. It's a tiny little AMD chip in there.
Chris: But it's incredible what I'm getting out of this thing.
Chris: And so he's massively pounding on it. I'm pounding on it during the day, all day long.
Chris: And these are the two things that I've come up with that are issues so far.
Chris: Plus, it needs help with portability. And ultimately, it needs an ISO image.
Chris: But that is a few hours of work. And this is something really special.
Chris: While a little wild, is a hell of a Linux experience and only something you can do on Linux.
Chris: And it's going to be my distro now for my desktops. So it's not a server distro, it's a desktop distro.
Chris: And my next move is like, I got to get it working with multi monitors.
Chris: I suspect that's going to be pretty easy in Hyperland, but I got to get that working.
Chris: And I got to figure out a way to expand it to multiple machines that works reliably.
Chris: And then eventually I want to deploy it here in the studio too.
Brent: I have a couple of questions.
Brent: First one, last week you leaned heavily on some, let's say, AI help to design
Brent: this whole thing, but you just sort of teased that you slowed down on that and
Brent: you're making some manual changes.
Brent: Do you see yourself using more vibing to modify this thing, or think you're
Brent: slowing way down just permanently and doing just manual changes from now forward?
Chris: I may be at the limits. Well, two things, you know, so I was on a free,
Chris: like, try it out. And there, you know, no API limits.
Chris: That's over now. So, yeah.
Wes: Our paper vibe is back.
Chris: Yeah. So I'm not going to do a lot of paper vibing.
Chris: But looking up little things, you know, like maybe the syntax to do a hyperlink
Chris: config file on multi-monitor, I might use an LLM for that.
Chris: But I think I'm at the point now where I need humans to look at it with multiple
Chris: different systems and sort of beyond
Chris: what the tool can do, which is fine because I got pretty far with it.
Chris: And now it's really iterative stuff. So I'm totally happy with that.
Chris: But for just probably technical lookups, you know, that kind of stuff,
Chris: I could see it. Or like if I were to try to get it working on a video system.
Wes: Are you going to do official versions with fun, you know, Linux kernel style version names?
Chris: Well the whole thing's really all rolling so that's tricky you know the whole
Chris: thing is i mean but i kind of do.
Wes: It whenever you want right you just say yeah.
Chris: Right that's true yeah and it would really be like an update to the configs
Chris: you know major new things to the configs yeah you could see it.
Wes: Yeah you change a theme out i don't know.
Chris: I've never done the release thing on github but that could be kind of fun right
Chris: like the main repo is all the current stuff and then every now and then i just
Chris: carve a release when something major has been accomplished or like i've you
Chris: know Or maybe we re-based on a new version of Hyperland or something. I don't know.
Brent: Chris is going to learn about branches, everybody.
Chris: Yeah. Woo. Here we go. It has been a lot.
Brent: Like any good distribution, you need a good name. Have you come up with a name for this thing?
Chris: I'm kind of embracing the Hypervibe.
Chris: You know, because it's Hyperland and it's a vibe. You know, I'm just going with
Chris: Hypervibe. You know, I don't know.
Brent: Are you locking it in?
Chris: I could lock it. Do you think it's okay? I mean, what do you boys think?
Brent: Well, I think it's quick and snappy and memorable.
Chris: Yeah? Wes? Could you live with Hypervibe?
Wes: Heck yeah. It's good vibes to me.
Chris: Locked in, then. Locked in. So we'll have a link to the GitHub repo,
Chris: chrislass slash Hypervibe, if you want to check it out. if you have any suggestions
Chris: on making it more portable or if you try it and run into any bugs.
Chris: Right now, I'd say it's probably for the more advanced Nix user,
Chris: but I'd like to take it to somebody that just wants to, you know,
Chris: try a nice image and run with it. I'm not sure how well it would run in a VM.
Chris: It probably comes down to how well Hyperland works in a VM, which is probably
Chris: doable, but you'd want to have some 3D acceleration.
Chris: It's been a lot of fun. I never thought I would actually really do this either.
Chris: But I'm going for it, boys.
Chris: Go Unleash your hardware and celebrate 20 years of Unraid OS. What a milestone.
Chris: What a milestone. And to really kind of mark it, now is your opportunity to
Chris: get 20% off the starter or Unleash licenses. So if you've been thinking about it, do it.
Chris: Also, if you're ready for an upgrade, you get some off that.
Chris: And if you want to grab some of the new merch to show off your HomeLab pride,
Chris: you can get 20% off that too.
Chris: Every day, they have giveaways, free licenses, merch bundles,
Chris: and they're even giving away a link station, which looks like a sweet rig.
Chris: So if you've got a great Unraid setup, submit it to them.
Chris: They have a Show Us Your System competition for a chance to win prizes.
Chris: You get bragging rights and, of course, get featured in that birthday bash stream
Chris: that I mentioned last week, which will be on August 31st.
Chris: That's the thing to do, really. Go mark your calendars for that big event.
Chris: Unraid's founder and guest will be joining to celebrate 20 years of Unraid and
Chris: to reveal the show your system winners.
Chris: So you'll want to put August 30th on your calendar.
Chris: You'll learn more by going to unraid.net slash unplugged. But giveaways,
Chris: merch, special guests, which I have a hint who a couple of them are,
Chris: and of course celebrating 20 years of Unraid, which is what I love.
Chris: I love that they have been with this for so long. and having spoken to them,
Chris: you know, I would have had the sense they're just a few years into this with the energy they have.
Chris: I mean, incredible energy and direction for Unraid as well.
Chris: So check it out. If you've got storage sitting around, maybe a machine you could
Chris: throw this on or you've been thinking about building one and you want to try
Chris: out all the applications we talk about all the time on this show,
Chris: Unraid will get you going in like a Saturday, right? That's the thing.
Chris: Like you could build all this from scratch and have like this crazy bespoke
Chris: system or you could let Unraid do the heavy lift with the Linux curation,
Chris: the VM curation, all the applications, of course, the container management,
Chris: and you supply the hardware.
Chris: And then you get up and running right away. And then they're already 20 years
Chris: in and they're still going strong.
Chris: So that's something that's going to last for a long time. Go check it out.
Chris: Find more about the celebration and support the show.
Chris: Go to unraid.net slash unplugged. That's unraid.net slash unplugged.
Brent: Well, this has been a great week for shout outs. And we want to welcome aboard
Brent: all sorts of new members.
Brent: We've got Zach, Anders, Trevor, Nicholas, Hanji, Alejandros, Adam, and Timothy.
Brent: So a huge thank you to these new members.
Chris: Woo!
Brent: And Chris, do we have any of those discount slots left?
Chris: Four left. There are four slots left for the bootleg promo code that takes 15%
Chris: off your jupiter.party membership, which is a great deal, or your core contributor membership.
Chris: Either plan gets you the bootleg or
Chris: the nice and tight version fully produced version of
Chris: the show and the party membership supports all the shows and the whole network
Chris: and the core contributor goes right here to this show and gets you all them
Chris: features thank you everybody that got on board this week hi yeah whoo whoo four
Chris: left use the promo code bootleg linuxunplugged.com membership or jupyter.party.
Brent: Now we have a little ask here from Fergus, who asks about the safety of BitChat.
Brent: He says, I heard you discussing Dorsey's new messaging app that is based on Bluetooth.
Brent: Has anyone considered the implications of creating a, quote,
Brent: secure peer-to-peer Bluetooth network in contrast with the Bluetooth surveillance
Brent: networks that are currently deployed by, say,
Brent: Apple with AirTags, Google, Tile, and the Amazon Sidewalk stuff?
Brent: I doubt that the target audience are Graphene OS users with an eSIM purchased in Monero.
Brent: My concern is that this opens another channel for tracking that would otherwise be inactive.
Brent: I would be interested in hearing your guys' thoughts.
Chris: I think the threat is not in so much the use of Bluetooth, it is in having Bluetooth enabled.
Chris: Like, if you have Bluetooth on, you're going to get tracked.
Wes: Right.
Chris: Right. So I don't think BitChat increases that risk.
Wes: Yeah, it will. It is pretty good. Like when you, I have my Bluetooth set to
Wes: just auto go off if I'm not using it.
Wes: And BitChat's good if when you open the app, it'll prompt you to turn it back on.
Wes: And it's a pretty slick, it doesn't, it's not super much of a fuss because I
Wes: was doing that at DEF CON constantly checking.
Wes: I didn't get many hits or anything, but you know, it was easy enough that it
Wes: wasn't a big pain to keep opening it,
Wes: turning it on just while I was using Bluetooth and then turn it all off.
Chris: I, just as an aside, have been getting three or four or maybe even more messages
Chris: a day on my Mesh-tastic TDEC out at the farm I'm staying at.
Wes: Oh.
Chris: The Mesh-tastic traffic is increasing. That's been pretty neat to see.
Wes: I need to get mine set up again. I'm slacking.
Chris: Yeah, I'd love to see if we could eventually connect. Quinn wrote in and shared his Nix setup with us.
Chris: He says, hey, Unplugged team, loving the new bootleg, and I just wanted to drop
Chris: my Nix OS configs. They're not finished, at least by my standards,
Chris: but right now it is multi-host and sets a host name based on a folder name.
Chris: It's split across four repos, and I love the name of these repos,
Chris: and I'll put the links in the show notes.
Chris: Repo 1, the formatter. Repo 2, the home.
Chris: Repo 3, the shared. And then the last repo, Repo 4, the host.
Chris: They're just great names.
Chris: And I'm going to have to take a look at it. I love it when people share their
Chris: configs. And maybe there's something we could steal in there for Hypervibe.
Chris: I like the idea of setting the host name based on a folder. That makes a lot
Chris: of sense. Thank you, Quinn.
Chris: That was good to see. now i want more i can look at configs like as a pastime
Chris: you know if we just had like something that just filtered them as they came
Chris: in and i just went to like some sort of offline reader and i could just read
Chris: through people's configs as like a short pastime before bed like.
Brent: The configs chronicles.
Wes: Oh yeah you spin the spin the dice and one up config pops up.
Chris: With a credit.
Wes: Oh that'd be Great.
Chris: Yeah, it is. And we got some great boosts this week.
Chris: In fact, Anonymous came in during the live show and is our baller booster with 71,000 sets.
Chris: That is great.
Chris: Coming on Podversus. Hi there, I finally caught up with the last episode today.
Chris: So I'll be hopefully live with you tonight. after hearing about
Chris: your summer bis dip what is
Chris: that what's a boost boost boost oh the boost dip yeah
Chris: we had the summer yeah the summer lull i thought i'd send some love and some
Chris: sets so chris i wanted to know about setting up hyperland on nyx why are so
Chris: many revisions why so many revisions and they all need a full rebuild how did
Chris: you get this done without spending so much time waiting for builds this is one
Chris: of the i'm glad you asked this,
Chris: This is actually one of the things that drew me away from Bluefin to Nix OS.
Chris: And it was the time for iteration. Not that it is super arduous to iterate on a uBlue base,
Chris: but it is a longer process, and the images are large, and they take a long time
Chris: to pull down, and then it actually does assemble them pretty quickly.
Chris: Whereas with Nix, I make a line config change, and I can do a rebuild,
Chris: and if you have a fast SSD and a fast CPU, and you're not changing very much,
Chris: it can take literal seconds.
Chris: And so you can build and build and build really quickly, deploy that,
Chris: and with Nix, you can also choose to switch to the system or you can choose to boot.
Chris: And so depending on the level of change, sometimes I would do a switch and sometimes I would do a boot.
Chris: And every time I would do a build, I'm also deploying a new version of my Hyperland
Chris: config, my Waybar config, and some of the ancillary tools that make all of that
Chris: work. That's all included and managed by Nix.
Wes: Right, and Nix is pretty good about, you know, You still have to do the full
Wes: evaluation step on your config every time, but after that, it's able to do a
Wes: diff to see what actually needs to get rebuilt and what actually needs to get restarted.
Wes: So if you're doing it, especially as you work kind of incrementally,
Wes: each time there's not that many components that are changing.
Chris: And I like that sanity check. For me, it's a nice thing to have in there,
Chris: to make sure everything's looking right and whatnot.
Chris: And then after I would do several and I would test them, I would then do a push to GitHub.
Chris: But usually for like one push to GitHub, there was probably five or 10 little
Chris: smaller things. And then, all right, this is enough. I'm going to push it now.
Chris: And you can kind of just see that going and going and going for a bit. Thank you, Anonymous.
Chris: Appreciate that boost. And if you want to boost in and let us know who you are,
Chris: we'd always love that too.
Wes: Adversaries 17 boosts in with 57,344 sats across three boosts.
Chris: Woo!
Wes: Haven't boosted in a while since I switched to Fountain. Unfortunately,
Wes: it doesn't look like Fountain supports boosting the member feeds.
Wes: And, uh, re your extreme makeover home assistant edition.
Wes: When are y'all coming to my place?
Brent: We would love to do that.
Chris: Keep boosting.
Wes: Okay, and then, uh, one last boost here. Responding to Chris's KYC society in the outro.
Wes: Definitely agree with you on how that's going to go down.
Wes: Unfortunately, that's how all governments eventually go. Just look at history.
Wes: People say, they won't take away my freedom.
Wes: Well, they already have. You just haven't gotten caught in the crosshairs yet.
Wes: Once you're in the crosshairs, the agenda pushers will stop at nothing to rid
Wes: you of everything you ever knew.
Chris: Woo! Adversary is keeping it real. Keeping it real.
Chris: Yeah, I'm sorry about the, uh, it's so ironic that the members can't boost and
Chris: the members want to boost. That's so amazing.
Chris: But it's probably not going to really get resolved until we can swap out memberful.
Chris: That might be what it takes. I'm not quite sure there, but well,
Chris: the real problem is that it's a private feed actually.
Chris: And a fountain looks up the value splits via the podcast index API.
Chris: And so if the podcast isn't published on the index, which it's not for a private
Chris: member feed, there is nothing to look up via the API.
Wes: It is something that really bugs us too though. So we can solve it.
Wes: But we will definitely do so.
Chris: Thank you for the boost. It's nice to hear from you. Missed you.
Brent: Well, Mick ZP came in with two boosts for a total of 40,000 sets.
Brent: Mick says, I just hate hearing that damn lowered expectation soundbite.
Chris: I'm not going to play it.
Chris: It's only when we don't meet expectations.
Brent: Well, I think we're meeting expectations a little more this week,
Brent: thanks to Mick ZP's boost.
Wes: Yeah, we need a meeting expectations boost.
Chris: Yeah, yeah. Well, that's what all the other sounds are, are meeting expectations.
Chris: Okay, we'll pick one of those.
Brent: Do you have a special meeting expectations boost there?
Chris: How's that there you go there you go oh is that it okay that's it huh thank
Chris: you it's nice to hear from you mixip and uh i love that boost hey there's hybrid
Chris: sarcasm coming in right now,
Chris: 25 000 sats i hear boosts are on sale so get them while they're hot by the way
Chris: how are the 2025 boosties looking oh i don't know if we want to talk about that right now yeah.
Wes: I'm way behind but maybe maybe sometime in the next couple of weeks i can uh
Wes: get caught up and um do a preliminary take take a look at uh that doesn't see
Wes: at least who's in the front running.
Chris: It's you know it's one of those things where i
Chris: actually think the overall total number of sats will be probably significantly
Chris: down from last year because like last year we did uh i think it was last year
Chris: we did the uh you know scale trip i think maybe i don't know but my point being
Chris: i think the total amount of sats boosted in may be down but the value may be up.
Wes: Yeah yeah true.
Chris: Not sure we'll find out thank you for checking and it's it's nice to hear from
Chris: your hybrid appreciate you retro.
Wes: Gear boosts in with 20 000 sats,
Wes: I've been playing with Libre NMS for a work project to monitor radio repeater
Wes: sites via a microwave network.
Wes: The monitoring also includes the radio repeater devices and DC power equipment.
Wes: Alert notifications are excellent with many platforms to choose from.
Wes: I wonder what your thoughts are, or have you used it? I did have a quick look
Wes: at Zabbix, but the UI seemed clunky.
Wes: Keep up the great work, team. I wouldn't be doing what I am now without LUP and self-hosted. P.S.
Wes: Don't forget about those ham radio licenses.
Chris: Good reminder.
Wes: Don't worry we haven't I was just chatting with a family member this week about
Wes: ham radio came up and I was like yeah I'm definitely gonna get it eventually
Wes: the audience wouldn't wouldn't forgive us if we didn't.
Chris: I took a quick look at Libre NMS and it looks pretty good better than I expected
Chris: I don't know what I expected but for some reason it looked better than I expected
Chris: I am down to get some decent monitoring going,
Chris: I don't think there's a lot of content in that. Other than once you have it
Chris: all set up, I guess we can have some takeaways.
Chris: But I would very much be interested to know what people are using these days.
Chris: Back in my day, Libre NMS did not exist. But I wonder if it might be based on
Chris: a project that I'm familiar with. Because it does look vaguely familiar.
Wes: Yeah, it looks like good stuff. I had the same. I didn't ever get to quite use
Wes: it. I think maybe it had just started when I last took a peek at these kinds of things.
Wes: But hey, we need more Libre options in this space. So glad to see it. I'm curious.
Chris: Thank you for the boost.
Brent: Well, Otterbrain boosted in 15,000 sets.
Brent: Sorry for the late boost. I'm listening live. Just got back from the wilderness
Brent: and gearing up for that academic year.
Chris: Hey! Thank you, Otterbrain. Nice to hear from you. Thanks for the check-in and thanks for the update.
Chris: The academic year is nigh, isn't it? That's the thing in my household, too.
Chris: Good luck. Once you get started, let us know how it's going.
Chris: Well, PJ's here with 6,666 sets.
Chris: He says, Darn near every boosted-in app and JB app pick has piqued my interest
Chris: this episode. Thanks for opening a few more permanent tabs on my phone browser.
Chris: Also, I've recently tried FFShare, and I've tried it a number of times,
Chris: and it typically makes my files even bigger.
Chris: That one time I sent a WebM was from my laptop. Oh, because we called him out.
Chris: And now he's got to defend himself on a web.
Chris: That one time I sent a WebM from my laptop. It was using a quick cut editor. You recommend it.
Brent: So it's our fault?
Chris: Telegram rented a fine on the desktop, just not on mobile. I do love a good
Chris: roast, though. Put some mac and cheese on there for me if you would, too. You got it, PJ.
Wes: Yeah, I wonder, I'll have to play more with FFShare just because I wonder if
Wes: you can change like your Q values or other things.
Wes: That's what I always do on the command line. It's just kind of turn the quality
Wes: down somewhere reasonable, at least for things you don't really,
Wes: you know, need precise quality on. I don't know what it defaults to in its settings.
Wes: But thank you for the experience report, PJ.
Chris: Yeah.
Brent: I'm thinking PJ doesn't understand what FFShare is for. It takes what you've
Brent: got and it boosts up the quality, doesn't it?
Chris: Yeah, make it, you know, make it better. And you can always add bits, you know.
Wes: They might be you hands you ai enhance boom get.
Brent: Into the modern world there pj.
Chris: It might be ai that imagines the bits that it adds but you can always add bits.
Wes: Galactic starfish boosts in with 7777 sets
Wes: i am not quite a
Wes: completionist but i'm not that far from it occasionally i take breaks from podcasts
Wes: all together but when the big when the breaks become too lengthy i compromise
Wes: and skip all but the most interesting one to five in the gap per podcast that
Wes: said i'm never late to twib hey.
Chris: There we go.
Wes: Up 616 sre rip 148 launch 29 keep up the good work and thanks for all you do.
Chris: Nice check-in oh.
Wes: You got the deets on that one.
Chris: Appreciate that thanks galactic good to hear from you.
Brent: Well tomatoes here with three boosts for a Total of 9,999 sets.
Brent: Well, I jumped ahead to listen to 626 and 627 while catching up,
Brent: throwing in some support.
Brent: I agree, we need a good modern in-kernel file system.
Brent: I'm also still frustrated at the BZF attitude of the kernel devs with regard to ZFS.
Brent: If they'd embrace it as an external project with a special status,
Brent: this, the file system story would have been so much better.
Chris: I think you and I are on the same page there, Tomato. Like,
Chris: I'm not expecting them to make allowances for something that's not licensed
Chris: properly, but also not really understanding the user's perspective and never
Chris: coming to a middle at all on it has been frustrating for those of us that want
Chris: to run these things in production.
Chris: Thank you for the boost. Nice to hear from you, Tomats.
Chris: I think this is a new one.
Chris: Doornail7887, I think, maybe new, comes in with a row of ducks.
Chris: You guys mentioned a boost barn previously. Does that exist?
Chris: Is there a place where you post the messages to?
Chris: That was a self-hosted thing because we didn't put all of the boosts above 2,000 sats on the show.
Chris: However, you have Podverse, so it's a little tricky. But if you go to,
Chris: I think you can get on the Fountain FM website, either in the Fountain app or
Chris: in the Fountain FM website. You can read all the boosts.
Chris: To Brent's help and call out in episode 627, I'm not a Knicks user,
Chris: but it got me wondering if there wasn't some sort of interesting combination of Pixie Boot and Knick.
Chris: That might make deploying these machines a lot easier to manage.
Wes: Yes.
Chris: Yeah, he said, I'm going to grow that. I'm going to add that to my growing half-baked
Chris: ideas stash. I actually think it's not half-baked at all, actually.
Brent: That's a good idea.
Wes: Pixie and Nix are a match made in Linux distro heaven.
Chris: And Pixie is so nice, and you have less things to fail in the machine.
Brent: This is also exactly the reason we ask for your ideas, is that you come up with
Brent: something that we had never even considered that's probably an even better idea. So thank you.
Chris: Yeah, that's a good one. i'd like i actually would like to do that for the machines
Chris: in the studio why you know except for the recording machine why do they need
Chris: local hard drives totally right one day one day distro.
Wes: Stew boosts in with 11 100 and 11 sets,
Wes: Yes, to Flatpak. It's not the best, but it's really getting there.
Wes: I generally try to install as much as I can through Flatpak.
Wes: Then if it doesn't work there, I fall back to the native package manager.
Wes: This really speeds up my Nix updates too.
Chris: True. That is true.
Wes: But what about terminal or server apps? Snap is the closest thing I can think
Wes: of in that direction, but I've not really dabbled what do y'all think.
Chris: I think this is the realm of containers that's why flat pack doesn't really
Chris: bother with it and while it is handy to have snap packages on server i mean
Chris: i like that i think outside of that ecosystem wouldn't you say it's people use
Chris: containers for that type of job.
Wes: Yeah probably so i mean obviously for the server side stuff containers are pretty
Wes: much king and more and more you do see i mean you know you can just run a terminal app from, you know,
Wes: a Podman run or Docker run command, or you could use something like Toolbox or Distrobox too.
Wes: So there are a lot more options there now.
Chris: Yeah, when we were doing the TUI challenge, there was a couple of times where
Chris: it's like a Podman runs essentially a one-liner, and then I've got the application up and going.
Chris: That's how I was running my web browser with the whole TUI challenge,
Chris: actually. So it worked for me that way.
Wes: And actually, you know, it's not quite contained in the same way,
Wes: but Nix can work well for TUI apps too, if you're willing to have that on your system.
Brent: Well, Marcel sends in a row of ducks. i
Brent: particularly liked this past episode i'm not
Brent: sure why it didn't get the usual support though i don't boost often because
Brent: i put my support on autopilot as you like to say with the that jupiter.party
Brent: membership but since you mentioned the low boost numbers i wanted to write in
Brent: and vote for more content like this keep up the good work.
Chris: Well thank you marcel message received i I appreciate that signal.
Chris: We can count on it right there.
Chris: Just like kangaroo paradox, who's it's been a minute. I'll be dead boys.
Chris: He's back. And he came in with 12,345 sats.
Chris: Well, I've built behind on the shows these past weeks, slowly catching up as
Chris: time rolls on, and I wanted to give a shout-out to the bootleg version of Unplugged,
Chris: where you can hear Chris, uh-oh, admitting that Vim's superiority to Nano.
Chris: It's in episode 618, The Tooey Challenge.
Chris: And Wes enjoying the situation just all too much.
Wes: Confirmed.
Chris: He says, I teased the time, but it's well worth the dime. Oh,
Chris: he says, I teased, but it's well worth the dime. Thank you.
Wes: Oh, you're so sweet.
Chris: I kind of vaguely recall that conversation.
Wes: Oh, I very much recall that conversation.
Brent: What you don't see in the audio version of the podcast is the pipe that Wes
Brent: brought to the studio that day. It seems to have worked in this case.
Chris: Oh, man. Thanks, kangaroo. You outed my secret.
Wes: Turd Ferguson boosts in with 13,000 sets.
Wes: I'm curious if Brent was going to make his own distribution,
Wes: Brunch OS, obviously, what would the focus be and what would it be based.
Brent: On oh yeah oh goodness good question
Brent: oh turd i have never
Brent: considered doing this i guess now i should start thanks so
Brent: much for that burden and i think brunch
Brent: os would clearly have some like deep privacy implications so that would be one
Brent: of its main focuses you know we would try to be bug free but that's you know
Brent: always a hard thing but it would clearly and obviously be based on Gentoo.
Chris: Oh, there you go. I would love to try that, actually. I would love to try that.
Chris: Thank you, turd. Appreciate the boost.
Brent: Leclament comes in with 15,000 sets.
Brent: My AI companion is OpenCode, which allows me to keep NeoVim as my main editor.
Brent: I migrated a significant part of my home lab from floating Docker Compose to a monorepo Nix OS.
Brent: This is a perfect setup for AI.
Wes: Cool.
Chris: How about that? So you can still use NeoVim. That's nice. That's really nice.
Wes: I love hearing about these setups.
Chris: Also, look at that, boys. They boosted from their own self-hosted AlbiHub.
Chris: Boom. Oh, how can they? Well, there, you don't get the claps then.
Wes: No, this was from Fountain, but it sounds like there's interest,
Wes: which we should applaud, I think.
Chris: Yes, that's true. Okay, all right, okay, that's fine.
Chris: Step one is go listen to This Week in Bitcoin episode 68. I have the co-founder
Chris: of Albie on there just so you get some broader context.
Chris: And then, you know, getalbie.com to get started.
Chris: I think it's even easier if you have a system that allows you to deploy,
Chris: like, application containers because it's packaged up for a lot of those,
Chris: like Start9 and Umbral and Unraid and all kinds of stuff.
Chris: So if you have a system like that already in place, it's just a one-click away
Chris: to get going. But you can also just run it as a container image too.
Chris: It's really amazing how straightforward they've made it.
Chris: And I bet if you, just going by what you've got going for your home lab,
Chris: I think you'd probably get it running pretty quickly.
Wes: And then from there you want the Albi extension, right?
Wes: And then you could use an app like Podverse that can call out to that to then talk to your node?
Chris: Or Podcast Index.
Wes: Right.
Chris: Or Cast-O-Matic if you're on iOS is really good. So there's a few options there.
Chris: You get kind of like this universal backend. Good question and good luck.
Chris: Let us know. Let us know.
Chris: Chlorophor comes in with a row of ducks.
Chris: Started AlbiHub instance 14 days ago and learned quite a lot.
Chris: I even did an open direct channel to Chris's node to decrease fees and to help us with liquidity.
Chris: More to come. But no channels for Brent or Drew.
Chris: Zero zero zero zero is not a good routable ip address for a node.
Wes: Yeah i think this is a bug in a particular version of lb it might might be fixed
Wes: now but i noticed that early on too is that the the public address they were
Wes: reporting was that but uh props that you're doing direct connects i mean that's
Wes: awesome thanks for the boost you.
Chris: Know thank you thank you for that and these really because brent and drew are
Chris: taking advantage of the subwall feature they're not their actual own node so
Chris: that's why that bug crops up nice spot good job.
Wes: The one the only the gene bean comes in with 2048 sets,
Wes: The challenge with everything being Flatpaks, though solvable,
Wes: is that things like 1Password's Firefox extension don't properly work with the
Wes: desktop app. This has been painful.
Wes: That's good to know. Right, like anytime you do containerization,
Wes: you got to get all the right holes poked through and plumbing put in,
Wes: and sometimes, you know, those aren't all ready in all the places.
Chris: We need another portal. That's what we need. Another portal.
Wes: The password portal.
Chris: Yeah, or something. The browser extension portal? I don't know.
Chris: Something. Yeah, that's painful.
Wes: And then Gene goes on replying to LUP625 regarding who could filter or test
Wes: Flatpaks, talking about like the future of Flatpaks and Fedora.
Wes: Get the package maintainers from distros to help with that, which you are saying as I type this.
Wes: I love it. This was a live boost, you know, to local to Gene being as Gene was
Wes: listening, which is rad.
Chris: Gene, that's one of the things I love about the boost is that button's right
Chris: there on the player, right? So as you're listening, you can hit the button and
Chris: send us the feedback while it's fresh in your mind. You don't lose it.
Chris: And that's exactly what Gene does. And I really appreciate that.
Chris: Thank you, everybody who boosted in. And thank you to you sat streamers who
Chris: set that sat stream while you listen.
Chris: We had 27,189 sats come in.
Chris: And that is not too bad right there. It's a decent little boost all in itself.
Chris: When you combine that with everybody who sent a message, including the folks
Chris: below the 2000sat cutoff, We stacked a grand total of 340,145 sats.
Chris: This is a value for value podcast and what that means is we put the show out
Chris: there for free and if you enjoy it you send some value back that could be your
Chris: time participating in our community could be talent maybe you'd like to help
Chris: us make some texas linux festival swag or it can be in treasure with a boost
Chris: or a membership this is an
Chris: independent podcast that is focused on making the best product for its audience.
Chris: And we always want our audience to be our number one partner,
Chris: not an advertiser, not dynamic ads, but the people consuming the content.
Chris: It's a radical idea, but I think it's the best way to have genuine good content on the internet.
Chris: There's not a lot of people doing it. And so we appreciate everybody who's helping make it possible.
Chris: You can do a boost with Fountain FM. They make it real easy or self-host with AlbiHub.
Chris: All right, we've got to let everybody know that I think we're going to be going
Chris: into a wee bit of overtime here because we got too many picks.
Chris: And this one I'm putting out there to get feedback from the audience. I'll start with this.
Chris: It's called Papera, and it's a minimal document archiving platform.
Chris: This is something I struggle with. I'm sure a lot of people do.
Chris: You want to archive your documents in a digital way that makes them easy to
Chris: tag and retrieve later on. This is a project under active development,
Chris: but the core functionality is stable and ready for use.
Chris: And it has lots of features and more coming.
Chris: It organizes your documents. You know, you can categorize family, friend, business.
Chris: You can share certain categories with colleagues. It makes it super easy to
Chris: quickly share the documents with full text search.
Chris: It has user authentication. It has a responsive design so you can use it on mobile.
Chris: Yes, it is open source. It's AGPL 3.0. You can self-host it.
Chris: You can tag your documents.
Chris: It has email integration. It has content extraction. It can automatically extract
Chris: the text from images or scan documents, making it available for search.
Wes: Ooh.
Chris: Huge.
Wes: This looks nice.
Chris: It has a command line interface, if you want. It has an API. It has webhooks.
Chris: I mean, it's got a lot of the stuff, Wes. I know there's PaperlessNG,
Chris: and there's other ones out there.
Chris: This is something I'd be very interested in adopting, and I'm really curious
Chris: if anybody has input. and paper a p-a-p-r-a which i'll have linked in the show
Chris: notes as well as the demo looks like a real contender here boys i.
Wes: Like how they call out self-hosting right like they've got a.
Chris: Yeah under.
Wes: 200 meg docker image compatible with x86 arm 64 and arm v7.
Chris: You know you should be thanking me brent you should be thanking me for this
Chris: pick i'm doing the lift here for you because you're living the hashtag van life now.
Brent: Ah and you want me to live kind of efficient and keep all those documents stored somewhere safe.
Chris: Are you gonna bring are you gonna bring all of your records all of your cat's
Chris: vet records all their stuff with you everywhere you go forever as you just collect
Chris: more and more as you become an old man and then god forbid what happens if something
Chris: happens to the rig and you lose your documents you know i.
Brent: Appreciate how you're slowly trickling in the problems to solve with this van
Brent: life uh new lifestyle that you've somehow yeah.
Wes: Where he didn't say this back in california did he.
Chris: I might have left that bit out yeah but you know through the pick segment i
Chris: can help you along you know i appreciate.
Brent: It i also think maybe if you consider uh like perhaps this project might be canadian it's paper a.
Chris: Paper a maybe paper a paper a it.
Brent: Is a gpl.
Chris: Paper a i i don't have the natural positive canadian up talk with the a yeah
Chris: i really have to work on that i'm not big on the up talk thing so that's fine.
Brent: We'll get happy.
Chris: Well, Canadians. From the category of where was this during the TUI challenge,
Chris: we have Lou, which is a terminal e-book reader with text-to-speech.
Wes: And isn't it pretty? I mean, look at that interface.
Chris: It's beautiful. I really do actually wish I knew about this sooner because I
Chris: could see even if you're just reading a manual that's in an e-book format or
Chris: something or, you know, some book related to what you're working on.
Chris: It supports EPUBs, PDF, text, docx.
Chris: Obviously, doc files, HTML, RTF, markdown.
Chris: All just automatically detected. The text-to-speech system is modular.
Chris: You don't have to have it. It can run locally if you do want it.
Chris: It saves your place. It switches between reading and speaking,
Chris: and it saves your place. It's GPL3.
Chris: It's got nice intuitive keyboard shortcuts.
Wes: Including Vim-like shortcuts, if you'd like.
Chris: Oh, good. Good. And I guess surprisingly smooth scrolling and transitions for
Chris: a terminal app, which I think is just a funny thing to actually call out.
Chris: But there it is hey that looks so good and.
Wes: Of course it uses our beloved ffmpeg.
Chris: Under the hood yeah yeah and then if you're going to try out hypervibe and you
Chris: want to take it to the absolute max i guess i do have my limits i didn't do
Chris: this out of the box i have my limits it's called wlg block wayland gameboy locker.
Wes: Yeah this project replaces the usual password screen with a gameboy emulator
Wes: running a patched pokemon game so to unlock your session you have to solve a
Wes: little challenge kind of like a mini escape room built into your os.
Chris: Yeah a pokemon puzzle kind of thing and then you unlock the screen uh you got
Chris: a lot of time on your hands if you're using this and.
Wes: You can tell um something this crazy clearly came from a nix user and yes there
Wes: is a flake in there and there's a nix os logo in the little demo video so we're
Wes: we're just that type aren't we.
Chris: My goal is to get you to try out the Hypervibe setup on your ancient laptop
Chris: and see if you notice a performance difference. And then I think you should get this going.
Wes: Oh yeah, that sounds like a good homework item from this show.
Chris: I mean, I'd love to see it. Not a temporary K exec. I'm on to you.
Chris: I'm on to you. I think you should try to convert your base to Nick system.
Wes: Full swap, okay.
Chris: Go all in. Go all in and see if you can make Hyperland work.
Chris: See if you notice the performance improvement. see if your fans run more give
Chris: me feedback on it you know in fact i extend that to everybody
Chris: go try it out and give me feedback and let me know also i
Chris: want you to boost in and tell me if you think i'm off guard on the bcash fs
Chris: situation and what your resolution could be i
Chris: mean if you had a magic wand for one day and could solve this how would you
Chris: solve it it's not necessarily an easy problem people problems well they matter
Chris: right it's right now we're in a situation where it's feels over features but
Chris: it's a project of people so boost in maybe i'm off i'd love to hear your take
Chris: on it, even if you disagree with me.
Chris: And of course, we will be live at the same time on the same bat channel next week.
Chris: It's on a Sunday, so you can make it a Tuesday on a Sunday when you come and
Chris: join us. We start at 10 a.m. Pacific, usually a little earlier than that even.
Chris: 1 p.m. Eastern, local time at jblive.tv.
Chris: Now, Wes, there's something really important we need to remind the audience
Chris: about an extra set of features they have.
Wes: It's that they can watch us live in their podcasting app, right?
Chris: That's one of them. And we got transcripts, too. We got chapters.
Wes: Yeah, we do. Cloud chapters, magic JSON, floating in the clouds, ready for you.
Chris: That's right.
Wes: For you.
Chris: Not just crammed in there, but JSON chapters. It's beautiful.
Chris: Links to what we talked about today at linuxunplugged.com slash 628.
Chris: Thanks for joining us. See you next Sunday.