Skip to main content
LawHub
Sign In
About LawHub Advantage Exploring Law Preparing for the LSAT Applying to Law School Excel in Law School Charting Your Career Podcast - I Am The Law Law School Trends Sign In
Search

Plausibly Postulated Prophecies

Dec 28, 2025
Listen to this episode

We make our big Linux predictions for 2026, but first, we score how we did for 2025.

Sponsored By:

Support LINUX Unplugged

Links:

Transcript

WEBVTT 00:00:11.092 --> 00:00:15.972 Hello, friends, and welcome back to your weekly Linux talk show. My name is Chris. 00:00:16.112 --> 00:00:16.812 My name is Wes. 00:00:16.992 --> 00:00:17.692 And my name is Brent. 00:00:18.312 --> 00:00:24.072 Hello, gentlemen, and joining us as referee this week, it's our friendly editor, Drew. Hello, Drew. 00:00:24.372 --> 00:00:25.932 Welcome to the Thunderdome. 00:00:26.952 --> 00:00:27.712 Uh-oh. 00:00:27.972 --> 00:00:30.892 That's a little indication of how it's going to go today. Today, 00:00:30.892 --> 00:00:35.092 we are owning up to our 2025 predictions. We'll see how we did. 00:00:35.292 --> 00:00:39.032 And then we're going to make bold and powerful 2026 predictions. 00:00:39.432 --> 00:00:42.492 So don't miss that. Then we're going to round out the show with some really 00:00:42.492 --> 00:00:44.652 great booze, some pics, and a lot more. 00:00:44.872 --> 00:00:47.932 This is where I'd say hello, Mumble Room, but shout out to those of you that 00:00:47.932 --> 00:00:49.412 are up there in the quiet listening right now. 00:00:49.832 --> 00:00:51.872 Look at them. Look at them. 00:00:52.052 --> 00:00:53.572 Listening so quietly. 00:00:53.752 --> 00:00:55.932 So quietly. If only my kids could be that quiet. 00:00:55.932 --> 00:00:56.552 I don't hear them. 00:00:57.072 --> 00:00:59.972 I know. Because they're in there quiet listening. Hello to all of you that join 00:00:59.972 --> 00:01:03.972 us in that live Mumble Room. Going every single Sunday that we do this here show. 00:01:05.378 --> 00:01:08.878 And a big good morning to our friends at Defined Networking. 00:01:09.538 --> 00:01:13.998 Defined.net slash unplugged. Go check out Managed Nebula. 00:01:14.358 --> 00:01:18.498 This is what you want to build on. It's a decentralized VPN that is built on 00:01:18.498 --> 00:01:21.598 top of the open source Nebula project that we already trust and love. 00:01:21.698 --> 00:01:23.218 It's out there. It's fully open source. 00:01:23.938 --> 00:01:27.618 But here's the real difference with Nebula. There isn't a free tier that exists 00:01:27.618 --> 00:01:31.858 to funnel you into some sort of VC-funded SaaS roadmap that's being developed. 00:01:32.238 --> 00:01:35.618 Right? So when a networking tool reaches a certain venture scale, 00:01:35.738 --> 00:01:39.318 let's call it, the business eventually competes with the free product, 00:01:39.878 --> 00:01:42.858 especially if there's a free tier. We all have seen the way this goes. 00:01:43.798 --> 00:01:47.718 We've seen the way this goes. With Nebula, you own the network. 00:01:47.918 --> 00:01:52.098 You own identity, routing, and the control stays with you. 00:01:52.678 --> 00:01:57.578 Not a third-party control plane that you don't control. You control everything. 00:01:57.698 --> 00:02:01.358 And Nebula's decentralized design means that no single point of failure is going 00:02:01.358 --> 00:02:04.818 to impact you. And the optional self-hosted Lighthouse nodes means that you 00:02:04.818 --> 00:02:06.938 keep discovery in your hands. 00:02:07.558 --> 00:02:09.378 That's so sweet. It's how you 00:02:09.378 --> 00:02:12.978 want to build when you're building your home infra or your business infra. 00:02:13.518 --> 00:02:16.038 Nebula was originally built to connect Slack's global infrastructure. 00:02:16.038 --> 00:02:20.858 So it was designed from the beginning to scale and perform so it can work for 00:02:20.858 --> 00:02:23.478 your lab and it can work for your global corporation. 00:02:23.718 --> 00:02:28.578 Go get 100 hosts for free right now. Support the show. No credit card required. No lock-in. 00:02:28.798 --> 00:02:33.838 Go to defined.net slash unplugged. That's define.net slash unplugged. 00:02:34.218 --> 00:02:38.138 Go support the show and check out Managed Nebula. 00:02:38.838 --> 00:02:43.318 Now, gentlemen, we have a little bit of housekeeping to get into before we start with predictions. 00:02:45.658 --> 00:02:49.598 It's that time of year again. If you can believe it, the call for papers for 00:02:49.598 --> 00:02:53.438 LinuxFest Northwest 2026 ends in just a couple of days. 00:02:54.178 --> 00:02:55.898 December 31st, 2025. 00:02:56.838 --> 00:02:58.218 You going to get a talk in, Wes? 00:02:58.418 --> 00:03:00.398 Oh, boy. Well, I better go quick. 00:03:01.078 --> 00:03:04.978 I swear, like, years are getting shorter or something. It feels like we just did this. 00:03:05.078 --> 00:03:09.358 I know, right? I know. It's crazy. LinuxFest Northwest is back in April, 00:03:09.518 --> 00:03:14.578 the 24th to the 26th, 2026 at Bellingham Technical College. and I believe that 00:03:14.578 --> 00:03:17.018 big area is going to be back available to us again. 00:03:17.258 --> 00:03:17.778 Oh, nice. 00:03:18.618 --> 00:03:19.058 Yeah. 00:03:19.758 --> 00:03:21.198 It was a great time last year. 00:03:21.358 --> 00:03:25.398 It was nice. If you can believe it, that's only 117 days away, 00:03:25.938 --> 00:03:28.498 which means if you include holidays in this, except for U.S. 00:03:28.578 --> 00:03:32.958 federal holidays, that's 82 business days away, which makes it 16 Linux unplugs 00:03:32.958 --> 00:03:36.998 away, which means Brent needs to be on the road by episode 660. 00:03:38.338 --> 00:03:41.738 I really appreciate how you give me the heads up because I need it. 00:03:41.738 --> 00:03:45.558 Oh, boost in your bet by which episode he actually hits the road. 00:03:45.818 --> 00:03:47.138 And which route should I take? 00:03:47.458 --> 00:03:51.498 You better. Also, if you want to catch up on how the van, or a.k.a. 00:03:51.538 --> 00:03:56.698 the bang bus, is doing, Brent stopped by the launch episode 46 at weeklylaunch.rocks. 00:03:57.278 --> 00:04:03.278 Nature chose violence, and Brent tells quite the tale, which I appreciated. 00:04:03.538 --> 00:04:07.398 Also, I talk a little bit about the flooding that hit the Pacific Northwest. 00:04:08.018 --> 00:04:09.318 You've been a local weatherman. 00:04:09.598 --> 00:04:13.418 It was quite the thing, Wes. I became an island is what happened. 00:04:13.538 --> 00:04:14.718 I became an island for real. 00:04:15.598 --> 00:04:19.158 So that is weeklylaunch.rocks and episode 46 for that. 00:04:19.278 --> 00:04:25.118 And we'll have a link to the LinuxFest Northwest 2026 call for speakers if that interests you. 00:04:27.506 --> 00:04:33.446 All right, gentlemen, it is time for predictions past. Before we get into how 2026 is going to go. 00:04:33.746 --> 00:04:35.146 You're making us make good on it. 00:04:35.366 --> 00:04:37.466 We got to see how we did for 2025. 00:04:38.286 --> 00:04:41.926 Did anyone else completely forget their predictions from last year? 00:04:42.406 --> 00:04:42.886 Yes. 00:04:43.186 --> 00:04:48.206 I only remembered one of mine and the others. I feel like it wasn't even me 00:04:48.206 --> 00:04:50.706 who wrote those or committed to those. But there's evidence, right, somewhere? 00:04:50.946 --> 00:04:55.006 There is evidence. In fact, we have audio on tape. 00:04:55.186 --> 00:04:59.086 So let's start with Brent's first prediction. For 2025. 00:04:59.786 --> 00:05:05.726 I believe in 2025, we will see a commercially available machine be released 00:05:05.726 --> 00:05:09.486 using RISC-V from major vendors. 00:05:12.117 --> 00:05:17.917 That's not my best prediction sentence, got to say. Machine is not very good. 00:05:18.337 --> 00:05:19.777 Yeah, Drew, you should have caught me on that. 00:05:20.737 --> 00:05:24.597 Well, I wasn't judging last year, so that's not on me. 00:05:24.977 --> 00:05:27.977 Well, we needed you. I'm nervous about this one. 00:05:28.137 --> 00:05:32.197 For those that are new to the show, Drew is here to play referee to make sure 00:05:32.197 --> 00:05:36.517 that we have good, solid predictions that should be measurable by the next year. 00:05:36.877 --> 00:05:40.357 And so this is a tricky one, ref. I think we might have to start with right away. 00:05:41.637 --> 00:05:46.157 I think you could call this technically true in the sense that Meta, 00:05:46.317 --> 00:05:52.457 in March of 2025, started deploying their custom AI and training inference chips 00:05:52.457 --> 00:05:54.417 built around RISC-V in their data center. 00:05:54.877 --> 00:06:02.457 And in late 2025, the Coral MPU officially released the Coral MPU from Google that is RISC-V based. 00:06:02.457 --> 00:06:06.457 I guess you could kind of consider that. But there's a few other like large 00:06:06.457 --> 00:06:11.537 data center implementations of RISC-V this year that didn't exist in 2024. 00:06:12.237 --> 00:06:15.137 So I asked the AI bot, and I want to hear what you think about this, Drew. 00:06:15.137 --> 00:06:20.257 The AI bot says that the prediction correctly identified an inflection point 00:06:20.257 --> 00:06:26.017 as of late December 2025, RISC-V has reached an estimated 25% market penetration 00:06:26.017 --> 00:06:27.917 in the semiconductor industry, 00:06:28.317 --> 00:06:34.757 largely due to major vendors abandoning expensive ARM licenses in favor of custom RISC-V silicon. 00:06:35.097 --> 00:06:39.417 So when Brent said a commercially available machine using RISC-V from a major 00:06:39.417 --> 00:06:43.317 vendor will be released, what do you think, Ref? Did he get it right? 00:06:43.317 --> 00:06:46.017 So here's the tricky part, custom. 00:06:47.475 --> 00:06:52.775 All right. So these guys are making their own risk five boards. 00:06:52.955 --> 00:06:55.095 Is that correct? Or are they selling them? 00:06:55.995 --> 00:06:57.035 Mm hmm. 00:06:57.875 --> 00:07:02.415 I believe you do have them on a technicality there. I think they may be at least 00:07:02.415 --> 00:07:03.975 having them manufactured on their behalf. 00:07:04.275 --> 00:07:12.815 Yeah. So for it to be commercially available, it needs to be sold from one company to another. 00:07:13.155 --> 00:07:15.335 That can't be an in-house product. 00:07:16.015 --> 00:07:19.635 Mm hmm. I think that's fair. It's not commercially available. 00:07:19.755 --> 00:07:20.995 It's privately available. 00:07:21.215 --> 00:07:26.795 So yeah, if you can tell me a company that is commercially producing these and 00:07:26.795 --> 00:07:30.775 selling them, it's a win. If you can't, it's a loss. 00:07:31.035 --> 00:07:36.015 I think this was a failure in describing my prediction, I will say. 00:07:36.175 --> 00:07:45.235 So I remember the sort of intention for this prediction was specifically around desktop computers. 00:07:45.235 --> 00:07:50.595 So when I use the word machine in saying a commercially available machine, 00:07:50.595 --> 00:07:58.615 I should have said a commercially available like desktop or tablet or single. Exactly. 00:07:58.855 --> 00:08:02.835 So I was thinking more available for the consumer market. 00:08:03.395 --> 00:08:04.155 Okay. 00:08:04.655 --> 00:08:11.195 So if we take it from that perspective, I do recall that the framework did make 00:08:11.195 --> 00:08:13.015 available a RISC-V board. 00:08:14.258 --> 00:08:18.238 but I think I'm going to fail myself on that from a technicality unless anyone 00:08:18.238 --> 00:08:23.258 else can help me win this one because that was announced February 4th, 00:08:23.338 --> 00:08:27.338 and our episode was February 5th, so I feel like it's not fair to make a prediction 00:08:27.338 --> 00:08:28.458 that happened the day before. 00:08:30.058 --> 00:08:31.678 Oh, you didn't have to out yourself. 00:08:32.458 --> 00:08:34.018 I'm the honest one here. 00:08:35.798 --> 00:08:37.698 So it was announced. 00:08:37.778 --> 00:08:40.978 Yeah, the day before the episode. He didn't know about it, but it was technically 00:08:40.978 --> 00:08:43.538 public information the day before the episode. 00:08:46.658 --> 00:08:50.018 At least for my limited research, which is, yeah, that's not fair. 00:08:50.955 --> 00:08:53.415 You know, I'd say, are we doing half points? 00:08:54.095 --> 00:08:54.475 Wow. 00:08:54.855 --> 00:08:58.175 I could get behind half points. If Wes doesn't object, I could get behind a 00:08:58.175 --> 00:09:01.255 half point. We could do that, like a .5. 00:09:01.475 --> 00:09:04.595 Okay, yeah. All right, we'll be generous this year. It is the holidays. 00:09:04.675 --> 00:09:05.295 It is the holidays. 00:09:05.515 --> 00:09:05.815 That was unbelievable. 00:09:06.155 --> 00:09:06.935 Half a point. 00:09:07.235 --> 00:09:09.715 And there was definitely an uptick in the deployment of RISC-V. 00:09:09.895 --> 00:09:10.195 Mm-hmm. 00:09:10.995 --> 00:09:15.975 Fair. Fair. Okay. All right. Well, Brantley, you win on a technicality. Congratulations. 00:09:16.235 --> 00:09:16.915 What are we doing? 00:09:17.255 --> 00:09:17.555 Wow. 00:09:17.855 --> 00:09:21.795 All right. I'm going to keep this. I'm going to keep track here. I'll keep track. 00:09:22.535 --> 00:09:26.095 All right. So, Brentley, you had a second prediction for us. 00:09:26.475 --> 00:09:31.035 You said in 2025, this was definitely going to happen. 00:09:31.295 --> 00:09:36.575 In 2025, the Ubuntu core desktop will be found as either a download on ubuntu.com 00:09:36.575 --> 00:09:39.795 slash download or as an Ubuntu flavor. 00:09:40.275 --> 00:09:44.735 I, this was like half prediction, half hope. 00:09:45.335 --> 00:09:51.175 I was really hoping this was going to happen for Ubuntu's future generally. 00:09:51.535 --> 00:09:54.475 I don't know if our wish casting generally works or does it? 00:09:54.655 --> 00:09:55.715 It does not seem to work. 00:09:55.855 --> 00:10:00.855 I know. That's where I trip up on my predictions is I just put in my own desires 00:10:00.855 --> 00:10:03.155 in there. And sometimes they happen and most of the time they don't. 00:10:03.595 --> 00:10:08.195 Here's the deal, ref. I looked it up. No, it is not downloadable on Ubuntu.com. 00:10:08.815 --> 00:10:12.235 The traditional Ubuntu desktop release is shipped as scheduled, 00:10:12.235 --> 00:10:16.575 but the ubuntu desktop that is the ubuntu core version and immutable snap only 00:10:16.575 --> 00:10:21.135 version of the os did not graduate to a standard download option and is still 00:10:21.135 --> 00:10:28.175 very much under development so i think that one's kind of a clear yeah loser yeah sorry brently no. 00:10:28.175 --> 00:10:30.295 It's fine i also have to add that, 00:10:31.397 --> 00:10:38.097 Given zero action last year, it felt like, on this, a micro prediction is that 00:10:38.097 --> 00:10:39.977 this year doesn't feel so good for this either. 00:10:40.097 --> 00:10:40.357 Does it? 00:10:44.117 --> 00:10:49.197 Okay, so zero points for that one. But let's see what your next one was, 00:10:49.217 --> 00:10:53.657 because maybe you had a vision for this next one. I was very impressed. 00:10:53.657 --> 00:11:02.337 In 2025, we will see a tech YouTuber of over a million subscribers do a iSwitched-style 00:11:02.337 --> 00:11:07.417 video for Linux, using it as their main desktop OS for a period of time. 00:11:08.137 --> 00:11:11.897 Wow, did you nail that one. So, yeah. 00:11:12.097 --> 00:11:16.737 On April 26, 2025, PewDiePie, I installed Linux, and so should you. 00:11:17.257 --> 00:11:23.677 PewDiePie has 110 million subscribers, and as of this AM, the video has seen 00:11:23.677 --> 00:11:30.337 7.3 million views, and it's the third most popular Linux video on YouTube. 00:11:31.397 --> 00:11:35.837 Yeah. It took a couple months, but that was an early win. 00:11:36.217 --> 00:11:37.077 Very clear win. 00:11:37.717 --> 00:11:38.517 Wow, Brent. 00:11:38.517 --> 00:11:41.737 I mean, do we know that Brent and PewDiePie aren't friends, or there's some 00:11:41.737 --> 00:11:42.617 sort of back-channeling? 00:11:42.977 --> 00:11:48.797 Not only was there that, But then there was a kind of a secondary effect of 00:11:48.797 --> 00:11:51.437 many other YouTubers making Linux content as well. 00:11:52.437 --> 00:11:57.277 Lots of reaction videos based on it, right? It was a whole hoopla there for a couple of weeks. 00:11:57.297 --> 00:11:58.077 In a way, you were not bullish enough. 00:12:00.137 --> 00:12:01.897 Okay. Congratulations, sir. 00:12:04.748 --> 00:12:11.528 So that's 1.5 points for Mr. Brentley, I believe. So not bad, Brent, not bad. 00:12:11.788 --> 00:12:14.528 Of a possible three points, is that it? So 50%. 00:12:14.528 --> 00:12:14.668 Yep. 00:12:15.068 --> 00:12:15.308 Yeah. 00:12:15.768 --> 00:12:16.248 I'll take it. 00:12:16.468 --> 00:12:20.148 Yeah, I mean, better than zero, as has been some of my years in the past. 00:12:20.948 --> 00:12:25.468 And that YouTuber one was great. All right, gentlemen, so it's my time to see how I did. 00:12:25.548 --> 00:12:25.948 You're up here. 00:12:26.308 --> 00:12:32.868 Mm-hmm, mm-hmm, mm-hmm. All right, so I said in 2025, this was my first prediction. 00:12:32.868 --> 00:12:34.208 And this was definitely going to happen. 00:12:34.208 --> 00:12:41.628 In 2025, inspired by NixOS, but not based on NixOS, a major distribution-based 00:12:41.628 --> 00:12:48.568 flavor, spin, or remix will ship a declarative configuration system for a reproducible system state. 00:12:48.768 --> 00:12:52.828 Now, there have been forks of NixOS, but I don't think that was my intention here. 00:12:53.908 --> 00:12:58.248 BlendOS is a thing, but I don't think that's probably a mainstream major distro. 00:12:58.768 --> 00:13:04.128 But I'm wondering what you guys think about OpenSUSE, because you have OpenSUSE, Aeon, and Kalpa. 00:13:05.493 --> 00:13:09.813 In 2025, they announced these two different variants, and they have doubled 00:13:09.813 --> 00:13:12.353 down on the zero-config declarative philosophy, they say. 00:13:12.773 --> 00:13:16.913 It's based on micro OS. It uses two specific tools to have declarative setups. 00:13:17.213 --> 00:13:20.593 You typically place these configuration files on a USB drive labeled ignition 00:13:20.593 --> 00:13:24.753 or combustion, and it does disk partitioning, rate arrays, creating users, 00:13:24.893 --> 00:13:26.973 writing files, system units, and software install. 00:13:27.253 --> 00:13:33.013 You do it with a human-readable butane YAML file, which is then compiled into 00:13:33.013 --> 00:13:35.033 a machine-readable ignition JSON file. 00:13:35.733 --> 00:13:39.973 And it can run any bash command, install any RPM package via whatever, 00:13:40.253 --> 00:13:42.913 transactional update, set up your networking, et cetera. 00:13:43.233 --> 00:13:47.393 So I think maybe you could argue that OpenSUSE is dabbling with this declarative setup. 00:13:47.573 --> 00:13:48.973 I have three questions. 00:13:49.133 --> 00:13:49.273 Okay. 00:13:49.293 --> 00:13:49.593 Three things. 00:13:49.833 --> 00:13:49.913 Fair. 00:13:50.233 --> 00:13:53.253 Well, I guess one of them is combined. So you made some notes here. 00:13:53.393 --> 00:13:59.293 The length of the notes combined with the fact that it's you talking about OpenSUSE 00:13:59.293 --> 00:14:02.073 makes it seem like a stretch automatically. 00:14:05.173 --> 00:14:08.873 my other question is like i don't think the ignition stuff is new i don't know 00:14:08.873 --> 00:14:13.253 about the butane so how much of this is a thing that was net new to 2025. 00:14:13.253 --> 00:14:18.233 Well the announcement of aeon and calpa was 2025. 00:14:18.233 --> 00:14:23.773 But was is the declarative or tech they're using well. 00:14:23.773 --> 00:14:28.753 No i don't think so But the distribution that uses the. 00:14:28.753 --> 00:14:29.573 Declarative tech was. 00:14:29.853 --> 00:14:35.733 Yeah. The wording is a major distribution-based flavor or spin or remix will 00:14:35.733 --> 00:14:38.053 ship a declarative configuration system. 00:14:38.253 --> 00:14:40.293 So it only had to ship in this year. 00:14:40.713 --> 00:14:42.173 Okay. Questions. 00:14:42.953 --> 00:14:43.773 All right. What do you think, though? 00:14:44.273 --> 00:14:45.833 Can I download this today? 00:14:46.493 --> 00:14:47.593 Yes, you can. 00:14:47.773 --> 00:14:52.633 Okay. Yeah. So ignition files are not a new thing at all. 00:14:53.213 --> 00:14:54.073 No. No. 00:14:54.073 --> 00:14:58.513 I mean, Cloud in it and the like are... 00:14:59.600 --> 00:15:04.420 Very old but this is this also gives you desktop zero config declarative desktop 00:15:04.420 --> 00:15:09.380 open source setup yeah it's like they're silver blue you could maybe kind of well. 00:15:09.380 --> 00:15:11.860 That's okay see that seems yeah 00:15:11.860 --> 00:15:14.520 i do think maybe you might have to install this on airmaster if you get. 00:15:14.520 --> 00:15:14.880 The point. 00:15:18.860 --> 00:15:26.680 All right so calpa and aon are brand new for 2025 using these ignition setups. 00:15:26.680 --> 00:15:30.540 And butane yeah yeah butane and ignition yeah sure. 00:15:30.540 --> 00:15:32.720 Well you can't have ignition without the fuel source. 00:15:32.720 --> 00:15:35.500 Right see you get it yeah see they're good at naming. 00:15:36.778 --> 00:15:37.638 I'm fine with it. 00:15:38.558 --> 00:15:40.338 Oh! Yes! 00:15:40.738 --> 00:15:40.918 Yeah. 00:15:41.138 --> 00:15:43.978 One point. All right, one point for me. That was a hard point I had to earn, 00:15:44.058 --> 00:15:46.398 but I'm going to take it. I had to work for that one. Yeah. 00:15:46.538 --> 00:15:47.838 Do you feel good about what you've done? 00:15:48.038 --> 00:15:52.158 I mean, I was hoping to see more. I really was. I was hoping to see more. 00:15:52.258 --> 00:15:55.398 And when CacheOS Server Edition came out, I was hoping that would be something like that. 00:15:55.398 --> 00:16:01.218 And this one was a hard one for me to say yes to, because an admission file 00:16:01.218 --> 00:16:03.738 is not really the same thing as a Nix config. 00:16:04.138 --> 00:16:06.158 It's just not. But... 00:16:06.158 --> 00:16:06.418 No. 00:16:06.418 --> 00:16:08.998 But it's arguably declarative, right? 00:16:09.498 --> 00:16:11.178 Technically, it is a declarative config. 00:16:11.538 --> 00:16:12.278 It is, right? 00:16:12.538 --> 00:16:12.778 Yeah. 00:16:13.838 --> 00:16:16.238 You can install your software, your networking, get it all set up. 00:16:17.718 --> 00:16:18.918 Begrudgingly, you get the point. 00:16:19.198 --> 00:16:24.338 I think this next one's not going to be super easy either. Here is my second prediction for 2025. 00:16:25.078 --> 00:16:32.058 In 2025, Debian 13 Trixie will ship, and every desktop that is capable of supporting 00:16:32.058 --> 00:16:36.058 Wayland will have Wayland support turned on by default. 00:16:36.418 --> 00:16:41.658 See, this is going to be a nuanced thing because there are desktops that are technically... 00:16:41.658 --> 00:16:43.718 How many desktops does Devin even ship? 00:16:43.938 --> 00:16:44.998 Well, I pulled the top four. 00:16:45.098 --> 00:16:45.358 Okay. 00:16:45.918 --> 00:16:48.958 I pulled the top four, and once you know it, it's right down the middle. 00:16:49.298 --> 00:16:52.558 So, GNOME 48 is shipping with Waylon by default in Trixie. 00:16:52.678 --> 00:16:56.358 So is Plasma 6.3. Those are both shipping with Waylon by default. 00:16:56.358 --> 00:17:05.338 However, LXQ 2.1 is using X11 by default and does technically support Wayland 00:17:05.338 --> 00:17:11.298 via LabW or LibAWBWC something, but is experimental. 00:17:11.758 --> 00:17:19.038 And XFCE 4.20 also ships with X11 by default, but the team considers it experimental 00:17:19.038 --> 00:17:23.438 and should not be used for regular users and should only be used for testing only. 00:17:23.438 --> 00:17:29.018 so it's literally split down the middle where the two that are on X11 could 00:17:29.018 --> 00:17:33.938 technically support it but are not yet recommended by the projects to run it. 00:17:33.938 --> 00:17:35.138 What does capable mean. 00:17:37.253 --> 00:17:37.853 Hard fail. 00:17:38.273 --> 00:17:44.633 I really, if I just would have left, I could have just kept it a little more vague, you know? 00:17:44.733 --> 00:17:45.653 There is an art to that. 00:17:46.033 --> 00:17:46.233 Yeah. 00:17:46.333 --> 00:17:46.473 Yeah. 00:17:46.693 --> 00:17:48.933 No, that's a hard fail. Sorry. 00:17:49.093 --> 00:17:49.873 All right. Okay. 00:17:50.533 --> 00:17:51.393 I was hoping. 00:17:52.833 --> 00:17:56.573 I blame XFCE and LXQT. 00:17:57.113 --> 00:17:58.893 Experimental means technically capable. 00:17:59.353 --> 00:17:59.753 Okay. 00:18:00.153 --> 00:18:02.753 Turned off by default means you fail. 00:18:03.693 --> 00:18:07.073 It is technically, if I hadn't said technically, I think that would have been a winner. 00:18:08.302 --> 00:18:12.582 Okay, well, I feel a little better about this next one, although at the time 00:18:12.582 --> 00:18:15.342 I was like, hmm, this is going to be a winner, a slam dunk. 00:18:15.442 --> 00:18:19.222 It actually was a nail-biter almost up until the end. 00:18:19.522 --> 00:18:23.802 In 2025, Valve will release Proton 10.0. 00:18:23.942 --> 00:18:27.582 They will tout brand new types of compatibility with Windows games, 00:18:27.602 --> 00:18:31.062 and it will be released before the end of 2025. 00:18:31.062 --> 00:18:34.682 I expected it to actually become much earlier in the year, 00:18:35.042 --> 00:18:42.162 but Proton 10.0 beta was released in April, but Stable did not actually ship 00:18:42.162 --> 00:18:48.042 until November 13th of 2025, and a major update just went out to 10.0, 00:18:48.162 --> 00:18:50.762 version 10.0-4 in late December. 00:18:50.762 --> 00:18:55.062 So this one, I actually just got in under the line when I thought I was getting a slam dunk. 00:18:55.242 --> 00:18:58.442 But, I mean, that one's cut and dry, easily measurable. 00:18:58.922 --> 00:19:02.822 The stable version of Proton 10 shipped on November 13th. What do you think, 00:19:02.882 --> 00:19:03.642 Ref? It's a winner, right? 00:19:04.642 --> 00:19:07.002 What types of new compatibility are there? 00:19:07.702 --> 00:19:12.922 Ah, so many games that previously required Proton Experimental were now moved to the stable branch, 00:19:13.062 --> 00:19:16.442 and they addressed issues with certain games, like Assassin's Creed Shadows, 00:19:16.442 --> 00:19:21.722 that had video playback issues, And another game that had issues that didn't 00:19:21.722 --> 00:19:25.102 work before was Resident Evil Village, which began working with Proton 10. 00:19:25.182 --> 00:19:27.942 There's other games, obviously, but those are the ones that stuck out. 00:19:28.662 --> 00:19:29.682 Okay. Yeah. 00:19:29.822 --> 00:19:30.722 Good. Good to go. 00:19:31.022 --> 00:19:32.962 Yeah. You've taken the lead. 00:19:33.402 --> 00:19:33.642 Dang. 00:19:33.642 --> 00:19:35.022 That brings you up to a two. 00:19:35.582 --> 00:19:39.502 I have two points, Wes Payne. Let's see if you can beat a 2.0. 00:19:40.202 --> 00:19:41.522 I certainly can't. 00:19:41.662 --> 00:19:46.422 I love, well, what I love about you, Wes's predictions, he often shoots for 00:19:46.422 --> 00:19:47.642 the stars and makes it fun. 00:19:48.202 --> 00:19:52.282 So let's see what Wes said would happen in 2025, his first prediction. 00:19:52.562 --> 00:19:59.622 I predict that in 2025, Chris Fisher purchases a RISC-V device that is a RISC-V 00:19:59.622 --> 00:20:02.702 device that has a RISC-V processor as its primary CBU. 00:20:03.490 --> 00:20:04.090 Uh-oh. 00:20:04.270 --> 00:20:05.530 Yeah, you really failed me on this one. 00:20:05.710 --> 00:20:07.850 There's still time. There's still time. 00:20:08.130 --> 00:20:11.330 That is true, but nothing's in my shopping cart, Wes. 00:20:11.950 --> 00:20:13.630 Well, why not? What are you waiting for? 00:20:14.210 --> 00:20:16.270 What do you think, Rev? I think that's a fail right there. 00:20:16.270 --> 00:20:19.790 I'd like to ask here, what was your motivation, Wes? What was your thinking on this one? 00:20:20.110 --> 00:20:24.110 He buys a lot of gadgets for himself, and there's just been a lot of chat about RISC-V. 00:20:24.370 --> 00:20:26.550 Ah, you see, I didn't buy many gadgets this year. 00:20:26.650 --> 00:20:28.750 Yeah. I blame inflation. 00:20:28.970 --> 00:20:29.190 Yeah. 00:20:30.390 --> 00:20:34.130 I was hoping you were right. I think we were feeling like it was going to be 00:20:34.130 --> 00:20:36.990 a big year and it was but just not in a way that impacted and like. 00:20:36.990 --> 00:20:40.930 I could have seen like you know was there like some kind of little tiny like 00:20:40.930 --> 00:20:44.030 old school phony size gadget or terminal or. 00:20:44.030 --> 00:20:44.690 Little development. 00:20:44.690 --> 00:20:45.970 Board that could I don't know. 00:20:45.970 --> 00:20:50.590 Or like a little laptop thingy sort of thing but I think that's a fail ref that. 00:20:50.590 --> 00:20:56.510 Little emulation thing that you bought from like Alibaba or whatever that that doesn't run risk 5. 00:20:56.510 --> 00:20:59.850 It does not then nope sorry, 00:21:02.121 --> 00:21:03.181 All right, zero points. 00:21:03.401 --> 00:21:04.181 Risky prediction. 00:21:04.381 --> 00:21:06.781 Fun prediction. That's one I wish would have happened. 00:21:06.961 --> 00:21:08.261 Maybe you'll get it in this year. 00:21:08.441 --> 00:21:11.201 You never know. Could be the year of RISC-V. You never know. 00:21:11.661 --> 00:21:15.041 All right, Wes's next prediction for 2025. 00:21:15.641 --> 00:21:21.361 I predict that in 2025, a distribution or spin or addition will feature BcacheFS 00:21:21.361 --> 00:21:26.301 as default file system, by which I mean you can go to the website, download an ISO, 00:21:27.181 --> 00:21:29.901 click through the defaults of the installer without having to change anything, 00:21:29.901 --> 00:21:33.001 and you will get BcacheFS as your main file system. 00:21:33.481 --> 00:21:34.141 What do you think. 00:21:34.301 --> 00:21:37.841 Wes? You know. Sadly, this is one I was hoping for, too. 00:21:38.101 --> 00:21:43.821 Yeah. In a way, I think that's gone the opposite direction. I think it's a good setup for 2026. 00:21:44.821 --> 00:21:47.961 True, yeah. We're getting to a point of, I mean, the experimental label might 00:21:47.961 --> 00:21:51.721 actually be off here real soon, too, so that's probably a reasonable precursor 00:21:51.721 --> 00:21:55.241 before it's likely, at least. But I was being hopeful. 00:21:55.721 --> 00:21:59.381 What do you think, Rav? It was hopeful, but seemingly misses the mark? 00:21:59.381 --> 00:22:02.901 It missed the mark. Yeah. Sorry. That's a no go. 00:22:05.336 --> 00:22:11.396 All right. Well, let's see. He may have made up for it with his last prediction for 2025. 00:22:12.376 --> 00:22:16.156 Wes Payne said this was absolutely going to happen in 2025. 00:22:16.576 --> 00:22:21.556 I predict that at the end of 2025, all three of us, Chris, Wes, 00:22:21.736 --> 00:22:27.616 and Brent, are using NixOS stock, you know, regular NixOS, not a derivative, 00:22:27.916 --> 00:22:30.796 as our primary workstation desktop operating system. 00:22:30.796 --> 00:22:35.196 All right, we got a little nuance here. Because this is technically true, 00:22:35.196 --> 00:22:38.076 but technically not, because I'm running Hypervibe on my systems. 00:22:38.236 --> 00:22:39.536 I think Hypervibe counts. 00:22:39.616 --> 00:22:39.936 I think so. 00:22:39.996 --> 00:22:41.656 Because you're just using Nix packages. 00:22:41.876 --> 00:22:42.696 Right, right. 00:22:42.836 --> 00:22:49.076 When you install Hypervibe, do you install Nix and then switch it into Hypervibe? 00:22:49.396 --> 00:22:54.936 Yes, technically I do right now. So is that the moment it switches? I like this line. 00:22:55.276 --> 00:23:00.376 So yes, I am installing mainline Nix, and then I destroy it. 00:23:00.796 --> 00:23:04.956 And there's nothing that you couldn't get with what you have from just a Nix 00:23:04.956 --> 00:23:08.396 file. As long as you could just do that and get what you have. 00:23:08.496 --> 00:23:12.516 Yep. What about you, Brantley? NixOS is your main daily driver? 00:23:13.076 --> 00:23:19.056 Well, I kind of feel like it was my daily driver before the predictions episode from last year. 00:23:19.236 --> 00:23:21.836 So I haven't changed it, I don't think, at all this year. 00:23:22.136 --> 00:23:24.196 So I'm NixOS all the way. 00:23:24.396 --> 00:23:27.056 It is a possibility. It could happen. 00:23:27.736 --> 00:23:30.336 Yeah, we try a lot of distros over the years, so you never know. 00:23:30.336 --> 00:23:32.936 So there's a lot of trying, but I always seem to come back. 00:23:33.356 --> 00:23:36.716 Okay, so what do you think, ref? Can we excuse the hyper-vibe technicality and 00:23:36.716 --> 00:23:37.856 consider this one a winner? 00:23:37.976 --> 00:23:40.176 It's not even a technicality. He just gets it. 00:23:40.636 --> 00:23:41.696 Hey! All right. 00:23:41.836 --> 00:23:42.456 No shout-out. 00:23:43.716 --> 00:23:46.116 That does put him in last place, but I mean. 00:23:46.256 --> 00:23:49.196 That does. One point for Wes Payne. All right. 00:23:49.316 --> 00:23:54.036 So as far as last year's predictions go, Brantley comes in at a 1.5. 00:23:54.196 --> 00:23:55.396 Well done, Brantley. Very nice. 00:23:55.396 --> 00:23:56.276 That half point. 00:23:57.756 --> 00:23:59.476 I didn't even fight for it. 00:24:00.396 --> 00:24:03.736 I come in at a victorious two points. 00:24:03.996 --> 00:24:04.556 Ha ha ha. 00:24:06.245 --> 00:24:11.665 And Wes Payne ranked in at one solid point, which honestly. 00:24:11.885 --> 00:24:13.225 Big beefy point. That's what I say. 00:24:13.405 --> 00:24:16.545 Hey, that one point's doing a heavy lift. That means none of us got a zero. 00:24:17.085 --> 00:24:20.285 That's not too bad for forecasting the future. Really, if you think about it, 00:24:20.565 --> 00:24:21.545 those are pretty good odds. 00:24:21.845 --> 00:24:25.565 I bet you most weathermen aren't that accurate. So we have that going for us. 00:24:29.925 --> 00:24:33.565 Onepassword.com slash unplug. That's the number one and then password. 00:24:33.745 --> 00:24:38.525 And it's unplugged, all lowercase. If your employees bypass security to use 00:24:38.525 --> 00:24:42.285 unapproved apps that they feel they need to do their job, you're not alone. 00:24:42.765 --> 00:24:44.625 Fortunately, with 1Password Extended 00:24:44.625 --> 00:24:48.545 Access Management, security and productivity do not have to be at odds. 00:24:48.725 --> 00:24:52.105 IT and the staff do not have to be at odds. 00:24:52.345 --> 00:24:55.765 And I know that you care about security. And how much do you want to bet that 00:24:55.765 --> 00:24:58.145 everyone in your company cares as much as you? 00:24:58.465 --> 00:25:00.905 I think you probably know the answer to that, unfortunately, 00:25:01.205 --> 00:25:05.145 especially with the growth of SaaS apps. There's just so many different services 00:25:05.145 --> 00:25:06.725 where they can simply sign in and start. 00:25:07.784 --> 00:25:11.824 Helpfully sharing their data. Trelica by 1Password makes security simple for 00:25:11.824 --> 00:25:13.584 every employee on every application. 00:25:14.064 --> 00:25:17.544 Now, what if I told you that one tool could secure hundreds of applications? 00:25:17.784 --> 00:25:24.024 Trelica by 1Password gives IT and security complete oversight of what is really 00:25:24.024 --> 00:25:26.684 a sprawling landscape of SaaS applications. 00:25:26.964 --> 00:25:31.464 And it's company-managed or unmanaged, the shadow type IT. 00:25:31.884 --> 00:25:34.884 Find out how many SaaS applications are being used at your company. 00:25:35.004 --> 00:25:38.504 Know right now. And if you can't keep count, You're not alone. Don't worry. 00:25:39.024 --> 00:25:41.544 That's where Trellica by 1Password will help you discover and secure those. 00:25:41.744 --> 00:25:43.804 Even the ones you don't know about will go out, discover it, 00:25:43.864 --> 00:25:46.864 has profiles so it knows about them. You can find the redundant spends. 00:25:47.864 --> 00:25:52.004 And it gives you processes for onboarding and offboarding staff. 00:25:52.764 --> 00:25:57.444 Not always an easy process, so it's nice to have something that helps you manage the spend and that. 00:25:57.684 --> 00:26:01.444 Trellica by 1Password will help you take control of your SaaS environment and 00:26:01.444 --> 00:26:04.584 give you visibility, automated workflows, and cost optimization. 00:26:05.484 --> 00:26:10.244 That's really powerful. You should go check it out. Go to 1Password.com slash unplugged. 00:26:10.284 --> 00:26:13.264 You can take the first step to better security for your team by securing credentials 00:26:13.264 --> 00:26:17.504 and protecting every application, even the unmanaged shadow IT. 00:26:18.004 --> 00:26:23.584 Learn more at 1Password.com slash unplugged. Remember, you can reduce unnecessary 00:26:23.584 --> 00:26:28.284 costs by analyzing your app usage to identify and eliminate those unneeded and 00:26:28.284 --> 00:26:30.444 unused licenses and redundant apps. 00:26:30.624 --> 00:26:32.624 That's just the tip of the iceberg. 00:26:32.904 --> 00:26:37.484 There's so much more. Go learn at 1password.com slash unplugged. 00:26:37.564 --> 00:26:41.124 That's 1password.com slash unplugged, all lowercase. 00:26:44.542 --> 00:26:50.522 All right gentlemen it is the time that we've all been waiting for it's our 2026 predictions, 00:26:52.142 --> 00:26:57.522 now you guys are really going to have to impress me on this i am not going to 00:26:57.522 --> 00:27:04.922 take any slack on this your predictions need to be concise they need to be accurate 00:27:04.922 --> 00:27:08.962 and what you say and how you say it matters. 00:27:09.982 --> 00:27:15.342 So let's go. Brent, you're up first. What is your first prediction? 00:27:16.122 --> 00:27:19.822 Well, after that, I'm feeling pretty nervous because I didn't workshop any of my predictions. 00:27:20.362 --> 00:27:23.822 So I might need a little help. So I'll give you the premise here. 00:27:23.942 --> 00:27:32.722 So this is my first shot at it. I believe in 2026, we will see local AI assistants 00:27:32.722 --> 00:27:38.462 like Lightspeed, be available in two other major distros. 00:27:38.822 --> 00:27:42.062 So two other major distros will ship something akin to Lightspeed. 00:27:43.719 --> 00:27:46.159 Okay, so not Lightspeed specifically, but something akin to it. 00:27:46.339 --> 00:27:49.579 Yeah, something like their own version of it or their own flavor or their own 00:27:49.579 --> 00:27:50.799 take on it, something like that. 00:27:50.979 --> 00:27:55.379 I'm not saying exactly how it'll be architected, just that someone will implement 00:27:55.379 --> 00:27:57.419 this sort of AI in your pocket. 00:27:57.419 --> 00:27:58.979 What do we mean by Lightspeed? 00:27:58.979 --> 00:28:10.759 Yeah, what I mean is like having an AI companion be available in the distro, 00:28:11.059 --> 00:28:15.259 like a distro native available feature. 00:28:15.399 --> 00:28:16.979 The word you're looking for is agentic. 00:28:18.079 --> 00:28:18.799 Gross. 00:28:19.819 --> 00:28:21.319 Can we get that as a... 00:28:26.739 --> 00:28:29.739 Yeah so maybe i need a little help wording all that because there's a lot of 00:28:29.739 --> 00:28:36.599 buzzwords and stuff but really it's just like uh in 2026 two other major distributions 00:28:36.599 --> 00:28:41.399 will make available a native agentic ai i. 00:28:41.399 --> 00:28:42.519 Would go with in-house. 00:28:42.519 --> 00:28:45.039 Okay all right i. 00:28:45.039 --> 00:28:48.019 Think that's getting at what you're what you're trying to describe here. 00:28:48.019 --> 00:28:53.219 So when we say in-house does that mean say it has to be like a canonical developed LLM. 00:28:53.919 --> 00:28:54.319 Hmm. 00:28:54.739 --> 00:28:56.059 Is that what, when we say in house means. 00:28:56.319 --> 00:28:59.799 I don't think so because that's a much bigger lift than just, 00:29:00.815 --> 00:29:03.975 having some blessed interface is. 00:29:03.975 --> 00:29:07.795 The definition then that it's a local thing it's not running on a cloud provider 00:29:07.795 --> 00:29:10.055 like open ai or something like that but it's something that. 00:29:10.055 --> 00:29:13.075 Runs on premise that's also 00:29:13.075 --> 00:29:17.355 quite restrictive i don't know if i want to commit to that okay okay i but i 00:29:17.355 --> 00:29:25.875 do think the interface itself has to be created by the distro so oh this is 00:29:25.875 --> 00:29:30.795 something like the distro So it's part of their like path, 00:29:31.055 --> 00:29:35.455 their feature set to offer this as a, as a, I don't know, service. 00:29:36.035 --> 00:29:39.735 So a minor technicality here, but that's not quite what. 00:29:39.735 --> 00:29:40.435 Those are a lot of them. 00:29:40.755 --> 00:29:44.675 That's okay. Yeah. That's not quite what Lightspeed is. Lightspeed is like a 00:29:44.675 --> 00:29:47.655 helper for specifically Ansible, right? 00:29:48.015 --> 00:29:52.515 Oh yeah. But that's kind of the ish I'm aiming at. 00:29:52.515 --> 00:29:59.335 Uh red hat does have its own in-house agentic ai for rel red hat enterprise 00:29:59.335 --> 00:30:02.015 linux and i think that's really more what you're getting at. 00:30:02.015 --> 00:30:04.395 Okay sure i i couldn't remember what it was called. 00:30:04.395 --> 00:30:09.415 Well and it's that's fine and it's worth pointing out that that particular agent 00:30:09.415 --> 00:30:14.535 can be configured to talk to multiple different llms yeah. 00:30:14.535 --> 00:30:20.995 So my my real aim here is that it will be specifically aimed at helping you 00:30:20.995 --> 00:30:22.675 manage the distribution. 00:30:22.675 --> 00:30:32.335 Okay so i think what you're looking for is an in-house interface to talk with 00:30:32.335 --> 00:30:38.615 llms to answer questions about your operating system is that. 00:30:38.615 --> 00:30:40.755 Uh yeah i guess. 00:30:40.755 --> 00:30:42.395 That's what we're looking for yeah. 00:30:42.395 --> 00:30:45.815 Like uh like in-house By in-house, we mean distro-developed, right? 00:30:46.055 --> 00:30:50.595 So a distro-developed interface to communicate with an LLM to help manage your system. 00:30:51.055 --> 00:30:51.875 I like it. 00:30:52.475 --> 00:30:53.195 How's that, Brent? 00:30:53.975 --> 00:30:57.215 I'm noting it down because to communicate, I went, yeah, yeah. 00:30:57.835 --> 00:31:02.695 A distro-developed interface to communicate with an LLM to help manage your system. 00:31:03.809 --> 00:31:07.349 And that doesn't necessarily specify local, right? It could be, you know. 00:31:07.549 --> 00:31:10.509 I mean, local would be nice, but I'm not going to restrict myself to that. 00:31:10.689 --> 00:31:13.609 I mean, if I'm Shuttleworth and I'm looking for some AI money, 00:31:13.769 --> 00:31:18.329 I'm probably thinking, how do I add a little AI magic to the canonical cloud 00:31:18.329 --> 00:31:19.449 and really get everybody worked up? 00:31:19.569 --> 00:31:24.449 That's where I'm going. All right. I think I can try a first go at a lock here. You ready? 00:31:25.029 --> 00:31:26.029 Yeah. Give us a first pass. 00:31:26.029 --> 00:31:34.049 In 2026 i believe two other major distributions will make available an in-house 00:31:34.049 --> 00:31:41.069 distro developed interface to communicate with an llm to help manage your system what. 00:31:41.069 --> 00:31:45.449 If you just changed other to non-redhat i don't know because you're not other 00:31:45.449 --> 00:31:46.149 we might not know who you're. 00:31:46.149 --> 00:31:48.209 Talking yeah yeah yeah yeah yeah yeah fair other. 00:31:48.209 --> 00:31:49.869 Than that what do you think i think it's pretty good that seems. 00:31:49.869 --> 00:31:51.129 Workable yeah real close. 00:31:51.129 --> 00:31:52.189 Okay brantley. 00:31:52.189 --> 00:31:57.469 Lock her third time's jam I believe in 2026, 00:31:57.789 --> 00:32:05.269 we will see two major non-Red Hat distributions make available an in-house distro-developed 00:32:05.269 --> 00:32:09.209 interface to communicate with LLMs to help manage your system. 00:32:11.009 --> 00:32:16.409 All right, it's officially locked. Number one is down, Brent. 00:32:16.709 --> 00:32:18.269 It's anxiety-inducing. 00:32:18.529 --> 00:32:19.449 It is, isn't it? 00:32:19.569 --> 00:32:22.109 What did I just commit to? what. 00:32:22.109 --> 00:32:26.109 Is uh your second prediction for 2026. 00:32:26.109 --> 00:32:29.669 Uh this is going to ride a little on the success of my 00:32:29.669 --> 00:32:34.609 youtube prediction from last year uh so my prediction will be that a youtube 00:32:34.609 --> 00:32:40.889 personality will start an opinionated distribution a la omacube or omarchie 00:32:40.889 --> 00:32:47.089 and it will be reported by its foss and the news stack to make it measurable. 00:32:48.006 --> 00:32:50.846 Why are you specifying particular news outlets, though? 00:32:50.986 --> 00:32:53.986 Because they're like any old YouTuber. And I didn't want to say, 00:32:53.986 --> 00:32:57.586 like, someone over a million subscribers or something, but I'm open to, 00:32:57.586 --> 00:33:00.106 like, suggestions for better measurability. 00:33:00.586 --> 00:33:02.046 I don't think I would limit it to any. 00:33:02.586 --> 00:33:04.066 How do you make it measurable, then? 00:33:04.906 --> 00:33:08.646 Well, just any of the Linux news outlets that we follow, I think. 00:33:08.846 --> 00:33:08.966 Yeah. 00:33:09.266 --> 00:33:10.966 What if Pharonix wrote about it? And then you didn't. 00:33:11.306 --> 00:33:15.426 That was my exact first thought, but Pharonix did not write about Omar G or 00:33:15.426 --> 00:33:16.586 Omocube. So I was like, oh. 00:33:16.586 --> 00:33:18.726 That's true. Yeah, they probably wouldn't. You're probably right. 00:33:19.026 --> 00:33:22.586 But so you're saying essentially the core of what you're saying is that we're 00:33:22.586 --> 00:33:23.826 going to see a YouTuber distro. 00:33:23.946 --> 00:33:26.406 Yes. Yes. That's really the core of it. 00:33:26.846 --> 00:33:27.046 Interesting. 00:33:27.306 --> 00:33:27.606 And so. 00:33:27.746 --> 00:33:28.386 What do you think of that? 00:33:29.006 --> 00:33:30.166 Like a Prime OS? 00:33:30.966 --> 00:33:35.786 Oh, yeah. For Primogen, I can see a Prime OS. Or you can see a PewDiePie distro. 00:33:36.806 --> 00:33:37.146 Mm-hmm. 00:33:37.746 --> 00:33:38.346 Mm-hmm. 00:33:38.466 --> 00:33:43.126 So it just needs to make that prediction measurable because I think it's gold. 00:33:43.606 --> 00:33:45.106 Well, I think we'd find out about it. 00:33:45.106 --> 00:33:50.706 I mean so we could see linus linux too right yeah sure right. 00:33:50.706 --> 00:33:55.466 Well ref what what is a good measure for you at the end of the year. 00:33:55.466 --> 00:34:05.406 Major youtuber with x number of followers minimum creates a youtube or it creates 00:34:05.406 --> 00:34:09.686 a linux distribution would be the way i would do it and not mention where it's. 00:34:09.686 --> 00:34:14.006 Reported at all all right all right okay yeah i don't know if i want to say 00:34:14.006 --> 00:34:18.526 a million that's a lot yeah i'll say 500k okay. 00:34:18.526 --> 00:34:19.326 That seems fair yeah. 00:34:19.326 --> 00:34:20.146 Yeah all right i. 00:34:20.146 --> 00:34:26.006 Mean you know 100k is like the base of like you've kind of made it right so 500k is yeah you're. 00:34:26.006 --> 00:34:28.906 It's like someone with some recognition you're not 00:34:28.906 --> 00:34:35.946 like the biggest of big yeah all right yeah i believe in 2026 we will see released 00:34:35.946 --> 00:34:42.246 a youtube personality that starts an opinionated distribution similar to Omacube 00:34:42.246 --> 00:34:47.526 and this YouTuber will have more than 500,000 followers. 00:34:49.780 --> 00:34:52.240 Okay. A YouTuber distro. 00:34:52.620 --> 00:34:55.300 I can only imagine how great that's going to be. 00:34:55.300 --> 00:34:56.400 Can you imagine reviewing that? 00:34:56.900 --> 00:34:57.940 Well, Brent's going to have it. 00:34:57.960 --> 00:35:00.140 Oh, God. It better be called Influencer OS. 00:35:03.660 --> 00:35:06.460 Oh, man. That would be good. That would be good. 00:35:07.140 --> 00:35:11.880 Okay, Brent. Why don't you dazzle us with your third prediction for 2026? 00:35:12.780 --> 00:35:17.280 Okay. This one was hard, but you'll help me. 00:35:18.220 --> 00:35:24.140 In 2026, I believe the Linux Foundation will start a new foundation. 00:35:25.600 --> 00:35:28.580 Are you serious? Are you serious? 00:35:29.360 --> 00:35:36.180 No, I'm not serious. The question is, how many tens of foundations will they start? 00:35:36.280 --> 00:35:41.200 That would be a fun one to guess. Or could you do a range like more than three? 00:35:41.200 --> 00:35:41.720 Yeah, over, under. 00:35:41.780 --> 00:35:42.560 Within abundance. 00:35:43.340 --> 00:35:46.180 10 to 13? Or is it more like 13 to 15? 00:35:49.400 --> 00:35:51.360 All right. I have a real one if you need one. 00:35:51.880 --> 00:35:52.380 Yeah, yeah, yeah. 00:35:52.580 --> 00:35:59.520 All right. In 2026, I believe there would be an XZ style breach in another widely 00:35:59.520 --> 00:36:04.680 used open source project, specifically an inside man style compromise. 00:36:05.440 --> 00:36:06.000 Ooh. 00:36:08.727 --> 00:36:13.967 An X, Z style breach. And then you say specifically an inside man. 00:36:14.107 --> 00:36:16.887 So somebody that already has like commit access to the project is kind of what you're saying. 00:36:16.887 --> 00:36:20.747 Someone who's infiltrated a project and gained some trust. And then, 00:36:20.747 --> 00:36:25.927 you know, we discover that, oh, wait, they're not the person we thought they were. 00:36:26.047 --> 00:36:28.287 And they're trying to do some maliciousness. 00:36:28.567 --> 00:36:32.847 So you could say something like a vulnerability via trusted commit access. 00:36:33.787 --> 00:36:34.267 Yeah. 00:36:34.347 --> 00:36:39.007 Or something, right? Is that seeming? and I'm you know it would depend on that 00:36:39.007 --> 00:36:43.307 actually getting coverage but for us to find it probably but assuming it's even 00:36:43.307 --> 00:36:45.327 if it's close to xz style yeah. 00:36:45.327 --> 00:36:48.807 Right if it's if it has an impact then there'll be some kind of security coverage you'd think. 00:36:48.807 --> 00:36:53.547 Yeah it seems reasonable what do you think refs yeah yeah. 00:36:53.547 --> 00:36:59.367 No notes I missed the verbiage you used there you said vulnerability via trust. 00:36:59.367 --> 00:37:04.667 Base I think it was something like a um a vulnerability will be discovered in 00:37:04.667 --> 00:37:08.627 an open source project that what did i say after that yeah. 00:37:08.627 --> 00:37:11.807 Right because it's not that it's not just that there's a vulnerability in the code it's. 00:37:11.807 --> 00:37:12.247 That this was. 00:37:12.247 --> 00:37:13.027 Put there by. 00:37:13.027 --> 00:37:16.187 A trusted somebody has access yeah yeah 00:37:16.187 --> 00:37:19.227 because that 00:37:19.227 --> 00:37:22.127 is a stinker that is a real stinker and you know it seems 00:37:22.127 --> 00:37:25.287 plausible because a revenue source really could become this 00:37:25.287 --> 00:37:28.407 is horrible to say and awful when you consider open source projects need more 00:37:28.407 --> 00:37:32.247 funding but a twisted development of this could be a revenue source is becoming 00:37:32.247 --> 00:37:37.307 this already where you sell a well-respected well-established trusted account 00:37:37.307 --> 00:37:40.587 and you can make more money than the free software project makes in an entire 00:37:40.587 --> 00:37:43.867 year just to sell that account to get you know it's just awful. 00:37:43.867 --> 00:37:45.907 It's not i feel really bummed about my prediction. 00:37:45.907 --> 00:37:47.787 Yeah don't put those ideas in. 00:37:47.787 --> 00:37:50.807 There nobody listens to this show though right. 00:37:52.067 --> 00:37:56.427 All right i think you got something all right all right i. 00:37:56.427 --> 00:38:01.787 Believe in 2026 we will see a vulnerability in an open source project via trust 00:38:01.787 --> 00:38:05.447 commit access, similar to the XZ style breach. 00:38:07.995 --> 00:38:13.055 Okay, that's three pretty solid predictions there. What do you think? 00:38:13.295 --> 00:38:16.835 Raph, this is your chance to get a few in. Enjoying the fun. 00:38:17.155 --> 00:38:18.155 Stretch your wings. 00:38:18.315 --> 00:38:21.315 Yeah. You got a prediction for 2026? 00:38:21.655 --> 00:38:26.555 I do. I've got a few. So first one is maybe the spiciest. 00:38:27.255 --> 00:38:31.815 I think that NVIDIA is going to potentially exit the consumer sector. 00:38:32.375 --> 00:38:33.295 I like that. 00:38:33.295 --> 00:38:40.155 The way that I would state this is that NVIDIA releases no consumer hardware cards in 2026. 00:38:40.475 --> 00:38:41.095 Oh, man. 00:38:41.795 --> 00:38:46.635 So, like, similar to what Micron has done, they just kind of pivoted to non-consumer. Wow. 00:38:47.275 --> 00:38:49.975 That would really hurt. But again, like, I guess it wouldn't really impact me 00:38:49.975 --> 00:38:52.035 because I haven't been able to buy NVIDIA cards for about six years. 00:38:52.215 --> 00:38:52.455 Yeah, yeah. 00:38:53.055 --> 00:38:54.935 I keep waiting for the prices to come down. 00:38:55.555 --> 00:38:56.715 They just keep going up. 00:38:57.175 --> 00:38:57.675 Uh-huh. 00:38:57.795 --> 00:38:58.195 Yeah, yeah. 00:38:59.055 --> 00:38:59.415 Yeah. 00:38:59.535 --> 00:39:00.375 This is dark. 00:39:00.375 --> 00:39:05.015 Boy, this would really be a sideways tilt to the PC manufacturing business. 00:39:06.155 --> 00:39:09.735 So that's pretty solid. I mean, NVIDIA exits the consumer business is a pretty 00:39:09.735 --> 00:39:11.575 solid, succinct prediction. 00:39:11.835 --> 00:39:14.855 I don't really have any notes there. Yeah, I think you can lock that in. 00:39:15.255 --> 00:39:15.835 All right. 00:39:18.217 --> 00:39:23.817 In 2026, NVIDIA will release zero consumer graphics cards. 00:39:28.177 --> 00:39:29.917 I hope you're wrong. I hope you're wrong. 00:39:29.997 --> 00:39:31.837 Me too. But, you know, I mean. 00:39:32.857 --> 00:39:36.257 Because, like, where else am I going to get a used card in five or six years? 00:39:36.637 --> 00:39:37.757 Right? That's what I'm looking for. 00:39:38.197 --> 00:39:42.917 AMD and NVIDIA, or no, AMD and Intel are both working it. 00:39:43.417 --> 00:39:47.857 And there's that Chinese company that's trying to start making cards. 00:39:47.857 --> 00:39:51.477 I don't remember their name, but, you know, maybe it gives some breathing room 00:39:51.477 --> 00:39:52.997 to the market. We'll see. 00:39:53.117 --> 00:39:58.177 Come on, Ark. Come on, Ark. This is your moment. Okay. Mr. Drew, 00:39:58.357 --> 00:39:59.557 do you have a second prediction? 00:39:59.737 --> 00:39:59.897 Sure. 00:40:00.037 --> 00:40:00.477 For 2026. 00:40:00.777 --> 00:40:05.817 So my second prediction is security-based. I believe that a major vulnerability 00:40:05.817 --> 00:40:13.297 of CVSS 9.0 or greater will be found somewhere in the base Kubernetes components. 00:40:13.957 --> 00:40:16.637 Ooh. 9.0 is putting a real number on it. 00:40:16.757 --> 00:40:17.097 Mm-hmm. 00:40:18.017 --> 00:40:20.197 Not an eight. You're going for a nine. 00:40:20.697 --> 00:40:21.137 Major. 00:40:22.097 --> 00:40:24.837 Wait, is this like inside baseball? You got some kind of... 00:40:25.765 --> 00:40:29.685 It's just a very complicated stack. There's a lot that can. Yeah. 00:40:29.985 --> 00:40:33.285 Have we seen any of these previously? Like, is this a trend? 00:40:33.545 --> 00:40:36.225 I mean, I almost feel like it averages out to one a year, but I'm not sure. 00:40:37.225 --> 00:40:42.365 The only possible issue I can see is in the base Kubernetes component. 00:40:42.585 --> 00:40:43.285 What is that? 00:40:43.545 --> 00:40:48.405 Yeah. Could you argue for some optional networking component that you were labeling as base? 00:40:48.405 --> 00:40:53.245 No, no. I'm not talking like no CSI drivers that are outside of base Kubernetes, 00:40:53.245 --> 00:41:02.125 that sort of thing. uh we're talking like in kubernetes uh not add-ons right okay. 00:41:02.125 --> 00:41:05.825 So base as in like but how do you define what you would define is what you would 00:41:05.825 --> 00:41:08.565 define as like the base thing to just have kubernetes operational. 00:41:08.565 --> 00:41:15.665 Yeah um that is a good question of how to how to state that effectively well 00:41:15.665 --> 00:41:21.085 and it it is also worth stating that some csi drivers are in base kubernetes right, 00:41:22.365 --> 00:41:23.665 All right. All right. 00:41:23.925 --> 00:41:25.145 There's nuance here. 00:41:25.705 --> 00:41:26.705 And a lot of yellow. 00:41:27.425 --> 00:41:31.125 What about something like, what about like using sort of cheat language in a 00:41:31.125 --> 00:41:36.085 way like a vendor shipped version of Kubernetes? 00:41:36.185 --> 00:41:41.245 I'm thinking more that it's a component that exists within the Kubernetes GitHub. 00:41:42.865 --> 00:41:45.025 Okay. That's okay. That's concrete. 00:41:45.385 --> 00:41:49.325 Yeah. GitHub. Okay. Yeah. That could be lockable right there, I think then. 00:41:49.565 --> 00:41:53.685 All right. So let's go with, in 2026, 00:41:54.005 --> 00:42:01.625 a major vulnerability of CVSS 9.0 or greater will be found in a component of 00:42:01.625 --> 00:42:06.465 Kubernetes that exists in the Kubernetes official GitHub. 00:42:09.019 --> 00:42:12.999 True, bringing the spice. Damn, sizzle to those. 00:42:13.119 --> 00:42:13.259 Yeah. 00:42:13.819 --> 00:42:17.219 Okay, all right. So do you have a third prediction for 2026? 00:42:17.559 --> 00:42:24.259 Yeah, yeah, this last one's cheap. I think global use of Linux will breach 10% 00:42:24.259 --> 00:42:25.619 in the Steam hardware survey. 00:42:25.739 --> 00:42:27.159 Let's hope so. 00:42:27.479 --> 00:42:31.539 So you think it's going to, I mean, that would technically be a double. That would be a double. 00:42:31.679 --> 00:42:32.579 It's trending up, yeah. 00:42:33.259 --> 00:42:33.659 Yeah. 00:42:33.919 --> 00:42:39.679 And a Windows 11 has been really biffing it. So, I don't know, 00:42:39.939 --> 00:42:43.879 maybe, and Steam machines are coming back. 00:42:44.619 --> 00:42:50.119 You know, I heard somebody say this weekend that's been using Linux for a few 00:42:50.119 --> 00:42:52.599 months, and they said, you know, 00:42:52.659 --> 00:42:56.419 I feel really great because I'm early to Linux. And I thought, you know. 00:42:56.559 --> 00:43:00.339 Wow. Well, it depends who you're comparing yourself to, I guess. 00:43:00.739 --> 00:43:03.199 And which adoption wave you're thinking of, right? 00:43:03.339 --> 00:43:04.059 Yeah, yeah, yeah. 00:43:04.059 --> 00:43:07.119 Yeah, so you may be right. There may be a whole wave coming, 00:43:07.419 --> 00:43:10.479 and 10% may be. I think it's the PewDiePie effect. 00:43:10.899 --> 00:43:11.219 Yeah. 00:43:11.339 --> 00:43:14.459 I would love to see it. I would love to see it. All right, well, let's log it in. 00:43:14.559 --> 00:43:14.959 All right. 00:43:17.066 --> 00:43:24.866 In 2026, global use of Linux will crest over 10% in the Steam Hardware Survey. 00:43:26.506 --> 00:43:27.846 Woo-hoo-hoo-hoo! 00:43:28.146 --> 00:43:28.406 Wow. 00:43:28.586 --> 00:43:29.626 Let's go Linux! 00:43:29.666 --> 00:43:32.706 I like it. It's a couple of hard hitters and a really positive one there, 00:43:32.766 --> 00:43:34.046 like a moonshot. That's great. 00:43:34.466 --> 00:43:38.826 That's a nice mix. That's a nice mix. All right, Wes Payne, are you going for 00:43:38.826 --> 00:43:42.786 a W this year? What do you think? How are your 2026 predictions looking? 00:43:42.946 --> 00:43:44.006 We're about to find out. 00:43:44.206 --> 00:43:49.486 I wonder if Wes's theme will be the dark one. this year or just the very like 00:43:49.486 --> 00:43:52.786 kind of spot on well calculated one you always flip. 00:43:52.786 --> 00:43:58.986 Well i'm going with hopeful for my first one okay a consumer oriented nas is 00:43:58.986 --> 00:44:02.926 announced that uses bcash fs under the hood oh. 00:44:02.926 --> 00:44:07.586 And now could that be an existing vendor that just updates their os. 00:44:07.586 --> 00:44:11.406 That would be my intention whether or not i've conveyed that or not we should decide. 00:44:11.406 --> 00:44:15.206 And it doesn't necessarily mean that when you install it it uses bcash by default 00:44:15.206 --> 00:44:16.526 but it just has support for Bcash? 00:44:17.406 --> 00:44:19.546 I think that means it's using it. 00:44:19.826 --> 00:44:20.966 Okay. Okay. 00:44:21.106 --> 00:44:27.746 I have a question. Is this, when you say consumer-oriented NAS, 00:44:27.866 --> 00:44:30.046 do you mean hardware or do you mean software? 00:44:32.586 --> 00:44:33.026 Either. 00:44:33.746 --> 00:44:35.906 So it could be an ISO, it could be a product pre-built. 00:44:36.086 --> 00:44:36.186 Yeah. 00:44:36.306 --> 00:44:36.486 Okay. 00:44:37.566 --> 00:44:40.506 I'd love to see it. It does feel a little long-shotty. 00:44:40.686 --> 00:44:42.046 It does feel a little long-shotty. 00:44:42.966 --> 00:44:48.386 So you're basically, You would lock in a vendor, a NAS vendor will announce, 00:44:48.546 --> 00:44:49.446 doesn't mean they shipped it. 00:44:50.777 --> 00:44:51.397 Just announce. 00:44:51.937 --> 00:44:52.337 Announce. 00:44:53.337 --> 00:44:54.957 Bcash FS being used under the hood. 00:44:54.957 --> 00:44:57.757 Oh, that's a good trick. They don't have to actually make anything. 00:44:58.317 --> 00:45:01.757 That is. It might not ship until 2027, but it's announced in 2027. 00:45:03.477 --> 00:45:03.877 Cheater. 00:45:04.097 --> 00:45:07.197 What do you think, ref? I think that's actually, I think that's, I don't know. 00:45:07.897 --> 00:45:09.417 I think we're close. It's a little weaselly. 00:45:09.517 --> 00:45:10.017 But it's clever. 00:45:10.177 --> 00:45:10.977 It's reasonable. 00:45:12.357 --> 00:45:18.077 Maybe offers Bcash FS as a default option Because a lot of these NAS vendors, 00:45:18.077 --> 00:45:26.357 you will have an option of what underlying file system to use, right? 00:45:26.997 --> 00:45:31.817 Yeah. Okay. Sure. Okay. So what do we think here? What was the phrasing you liked for the NAS? 00:45:33.137 --> 00:45:36.157 Like it's in the dropdown? I don't know. I don't know exactly how to describe it. 00:45:36.157 --> 00:45:39.477 So not necessarily the default, but an available file system feature. 00:45:39.477 --> 00:45:43.137 But it is available by default during installation. 00:45:44.317 --> 00:45:46.557 Oh, during installation. Okay. 00:45:46.597 --> 00:45:47.337 What do you say to that. 00:45:47.357 --> 00:45:47.637 I guess? 00:45:48.297 --> 00:45:50.517 Well, because here's what it is. This is going to be, so say Unraid, 00:45:50.637 --> 00:45:55.597 for example, they support NTFS and Extended 2, but during installation, 00:45:55.597 --> 00:46:00.297 it's not going to deploy those on the disk, but if you put a disk in with NTFS, 00:46:00.397 --> 00:46:02.137 it would support it, and you could use it. 00:46:02.257 --> 00:46:04.457 So maybe not during installation, but during setup. 00:46:05.677 --> 00:46:07.817 So then for this to, right, because then by that definition, 00:46:07.957 --> 00:46:11.837 for this to win, Unraid would just need to ship an update that includes BcacheFS support. 00:46:11.917 --> 00:46:12.337 Yes, true. 00:46:12.817 --> 00:46:14.977 A NAS vendor announces BcacheFS support? 00:46:15.977 --> 00:46:18.317 I think that would be the way I'd go because it's still kind of a long shot. 00:46:20.497 --> 00:46:21.057 I'm down. 00:46:22.197 --> 00:46:25.317 Next week, Wes gets hired by a NASDA company. 00:46:25.737 --> 00:46:26.357 I hope you're right. 00:46:27.277 --> 00:46:28.677 Supported Bcash FS support? 00:46:29.077 --> 00:46:29.437 Okay. 00:46:29.817 --> 00:46:33.657 Does that make sense? Like, it's an official part of it. It's not like an extension. 00:46:33.657 --> 00:46:34.537 Yeah, it's not a janky. 00:46:35.357 --> 00:46:38.797 It's an officially supported Bcash FS option. 00:46:39.017 --> 00:46:42.137 Right. It's not like some vendor, or it's not like some community mod or something. 00:46:42.417 --> 00:46:42.737 Yeah, yeah, yeah. 00:46:42.817 --> 00:46:45.097 Okay. All right, Wes Payne, lock it in. 00:46:45.097 --> 00:46:53.997 I predict that in 2026, a NAS vendor announces official eCacheFS support. 00:46:55.904 --> 00:46:57.524 I hope you are right about that one. 00:46:57.524 --> 00:46:57.784 Wow. 00:46:57.784 --> 00:47:02.884 I really do. I really do. I like that a lot, Wes. That's a good, solid first one. 00:47:03.084 --> 00:47:06.564 It's a risky one, and if it wins, it's going to be such a payoff. 00:47:07.224 --> 00:47:08.624 All right. Do you have a second prediction? 00:47:08.744 --> 00:47:13.024 Yeah, all right. Here's a safe option. I predict that in... Sorry. 00:47:15.024 --> 00:47:20.384 I predict that in 2026, we will see Linux kernel version 7. 00:47:21.164 --> 00:47:24.684 Whoa! I didn't even think of that. I like that a lot. 00:47:24.684 --> 00:47:27.104 Wow, that's so nice and simple. 00:47:27.624 --> 00:47:28.704 Very easy to measure. 00:47:28.924 --> 00:47:29.064 Yeah. 00:47:29.564 --> 00:47:31.424 Can I ask you a couple of qualifying questions? 00:47:31.624 --> 00:47:31.964 Of course. 00:47:33.104 --> 00:47:34.784 Does a RC count? 00:47:34.944 --> 00:47:35.724 That was my question too. 00:47:35.724 --> 00:47:41.724 Does a beta count? Yeah. Okay, what do you think? So, because how are you defining 7.0 release? 00:47:41.864 --> 00:47:45.544 Is it stable or is the code out there and we could run it? Like where's the line? 00:47:45.544 --> 00:47:48.744 Is this like announced versus shipped? Is it you did pull in one of those again? 00:47:48.904 --> 00:47:55.704 We will see that the next version will be 7. so we'll have an announcement that 7 is the next. 00:47:56.464 --> 00:47:57.724 Okay that's. 00:47:57.724 --> 00:47:58.584 Sneaky that buys you. 00:47:58.584 --> 00:48:01.544 Like a couple weeks that seems probable actually that actually seems probable, 00:48:02.424 --> 00:48:06.844 I can't believe I didn't think of that damn it I wish I would have thought of 00:48:06.844 --> 00:48:11.764 that one alright Linux 7 announced is essentially what you're saying well. 00:48:11.764 --> 00:48:14.064 You said next version so it needs to be like. 00:48:15.064 --> 00:48:16.484 Well a version we will see. 00:48:16.484 --> 00:48:21.044 Right because 8 is going to be the actual next stable version right and seven 00:48:21.044 --> 00:48:22.824 would be a development series? Is that how they still do it? 00:48:22.884 --> 00:48:24.844 Well, because we're at six, 19. 00:48:24.944 --> 00:48:25.544 19, yeah. 00:48:25.804 --> 00:48:30.364 So I'm saying that in 2026, we will go into the seven series. 00:48:30.624 --> 00:48:33.044 We'll get out of the six series into the seven series. However, 00:48:33.104 --> 00:48:34.564 we will think that's best said. 00:48:34.904 --> 00:48:36.664 How about, what about something like, what do you think of this, 00:48:36.764 --> 00:48:41.384 Ref? Is something like in 2026, the next series of the kernel, 00:48:41.484 --> 00:48:44.244 the next major series of the kernel will be announced? Something like that? 00:48:44.544 --> 00:48:49.704 Well, no, it's got to include the seven. That's a pretty crucial part of it. 00:48:49.704 --> 00:48:53.864 And do they start on that development branch? 00:48:55.929 --> 00:48:56.849 Is that one way to measure it? 00:48:57.409 --> 00:48:58.409 Just announced. I think announced. 00:48:58.649 --> 00:48:58.669 Yeah. 00:48:59.489 --> 00:49:00.309 I think announced is... 00:49:00.309 --> 00:49:03.469 They announced they're bumping the major kernel version to 7. 00:49:04.489 --> 00:49:04.849 Okay. 00:49:05.029 --> 00:49:05.609 At that point in the future. 00:49:05.749 --> 00:49:08.749 Either that or they're taking this thing to like 30-something. You know, I don't know. 00:49:11.589 --> 00:49:15.629 Okay, how about... I predict that in 2026, the Linux kernel community will announce 00:49:15.629 --> 00:49:17.509 they are bumping the major version to 7. 00:49:17.929 --> 00:49:18.769 I think that works. 00:49:18.829 --> 00:49:19.489 Yeah, I'm cool with it. 00:49:20.109 --> 00:49:22.629 All right, Wes Payne. Lock it in. 00:49:23.929 --> 00:49:29.049 I predict that in 2026 the linux kernel community will announce they are bumping 00:49:29.049 --> 00:49:31.269 the major version to seven. 00:49:31.269 --> 00:49:36.469 All right there it is i like that. 00:49:36.469 --> 00:49:37.469 All right i wish. 00:49:37.469 --> 00:49:40.989 I would have stolen that one i wish i would have thought of that one you got a third one. 00:49:40.989 --> 00:49:45.569 For us some backups in the doc if you want to steal any of those thank you i 00:49:45.569 --> 00:49:51.869 do have a third one here um by the end of 2026 when we review predictions next year. 00:49:52.229 --> 00:49:57.289 It will have been at least a month since you, Christopher, hand edited, 00:49:57.629 --> 00:50:01.089 without LLM assistance, your main NixOS config. 00:50:01.529 --> 00:50:02.049 Whoa. 00:50:02.549 --> 00:50:05.269 I mean, that might be true for this year's predictions. 00:50:05.269 --> 00:50:06.029 How do we define main? 00:50:06.209 --> 00:50:07.749 Yeah, we could... 00:50:07.749 --> 00:50:10.509 Because I have, you know, my server config that I use. 00:50:10.629 --> 00:50:13.009 Yeah, we could probably switch that out. 00:50:13.289 --> 00:50:17.829 But the nut of what you're trying to get at here is that I'll have gone a month 00:50:17.829 --> 00:50:20.849 without having to have touched a config file because I'm telling the machine. 00:50:20.849 --> 00:50:22.329 Yeah, there we go. Maybe that's it. Okay, yeah. 00:50:24.202 --> 00:50:26.902 That's that's probable how. 00:50:26.902 --> 00:50:28.802 Much are you paying him for this one. 00:50:28.802 --> 00:50:32.902 I mean it's possible it is surprisingly possible actually because i've been 00:50:32.902 --> 00:50:35.982 i've been trying to push it as far as i can okay. 00:50:35.982 --> 00:50:40.802 I have a question like yeah go this assumes he's still using nixos at that point 00:50:40.802 --> 00:50:46.582 right yeah he's not using nixos then obviously he wouldn't have edited it right. 00:50:46.582 --> 00:50:52.362 I would say yeah i have used uh i have used it to um edit an ubuntu config file 00:50:52.362 --> 00:50:53.742 so if you just made a config file. 00:50:53.922 --> 00:50:58.222 Yeah, it'll have been at least a month since you've hand-edited without LLM 00:50:58.222 --> 00:51:01.122 assistance a Linux config file. 00:51:01.262 --> 00:51:02.382 That seems pretty good, ref, right? 00:51:02.622 --> 00:51:04.722 Yeah, so anything in .config. 00:51:06.302 --> 00:51:06.822 Etsy, 00:51:09.182 --> 00:51:15.222 Dockerfiles, Yeah, Dockerfiles, NixConfig, a lot of things, Wes, 00:51:15.422 --> 00:51:17.502 that just need a quick edit. That is spicy. 00:51:17.782 --> 00:51:21.342 Alright, lock it in. I'll be honest. 00:51:22.342 --> 00:51:26.942 I predicted that by the end of 2026 when we're reviewing these very predictions 00:51:26.942 --> 00:51:32.342 it will have been at least a month since chris hand edited by which i mean without 00:51:32.342 --> 00:51:38.582 llm assistance a configuration file like a linux config a docker config an open source app config. 00:51:40.752 --> 00:51:45.052 We shall see. All right, so I have too many predictions. 00:51:45.532 --> 00:51:52.092 I have to whittle this down a little bit, and I have to go with my winners and losers here. 00:51:52.732 --> 00:51:59.612 And I'm going to start with kind of, I think, maybe an aspirational prediction. 00:52:00.432 --> 00:52:07.532 And I think that in 2026, Fedora Atomic replaces Workstation as the recommended 00:52:07.532 --> 00:52:10.312 download when you go to the Fedora's download page. 00:52:10.992 --> 00:52:11.472 Wow. 00:52:12.212 --> 00:52:12.612 Yeah. 00:52:12.932 --> 00:52:15.152 What's this based on? What's the hunch here? 00:52:15.512 --> 00:52:21.992 Well, over 2025, the Fedora Engineering Steering Committee has been kind of 00:52:21.992 --> 00:52:27.532 moving towards making the image-based system the main stable Fedora. 00:52:27.732 --> 00:52:30.412 So it's not based on the Aurora install you're talking about wiping? 00:52:30.652 --> 00:52:33.692 Nope, nope, nope, nope. It's based on the three years of the steering committee 00:52:33.692 --> 00:52:35.392 slowly working towards this. 00:52:35.452 --> 00:52:39.812 And I have to imagine this could be the year we actually see their efforts come to fruition. 00:52:40.752 --> 00:52:44.972 So I think the way to verify this would be you'd see changes at GetFedora.org 00:52:44.972 --> 00:52:49.792 where essentially a Silverblue-based download would be the default. 00:52:49.972 --> 00:52:51.092 Silverblue Workstation, perhaps. 00:52:51.512 --> 00:52:54.212 So year of the Fedora Atomic Desktop is what you're saying. 00:52:54.212 --> 00:52:59.392 Okay, so when I go there now, I get Fedora Workstation, Fedora KDE Plasma Desktop, and Fedora Server. 00:52:59.632 --> 00:52:59.772 Yeah. 00:53:00.312 --> 00:53:03.112 Well, then there's also three more under that. So there's like a row of... 00:53:03.112 --> 00:53:04.252 Is it just offered there? 00:53:04.372 --> 00:53:09.692 The top ones. The premiered featured workstation gets replaced with the Silverblue Workstation. 00:53:10.752 --> 00:53:19.072 Okay. Yeah. Another, so there's also fedorproject.org slash spins is currently all standard spins. 00:53:19.392 --> 00:53:24.252 And then atomic dash desktops is a list of all their atomic stuff. 00:53:24.252 --> 00:53:29.592 So you could also say that those would swap where atomic desktops become spins 00:53:29.592 --> 00:53:35.092 and spins becomes legacy or something along those lines. 00:53:35.092 --> 00:53:40.192 The shorthand I was thinking of using for that is just, it becomes the recommended download. 00:53:40.272 --> 00:53:40.812 Yeah, yeah. 00:53:43.181 --> 00:53:47.821 Okay, so my lock-in would be Fedora Atomic replaces Workstation as the recommended 00:53:47.821 --> 00:53:50.701 download. Just sort of, you think that works? Does that work? 00:53:50.981 --> 00:53:54.721 As long as it's measurable, right? As long as we feel like there's a way that 00:53:54.721 --> 00:53:56.661 we can see that a switch has happened? 00:53:57.401 --> 00:53:59.801 Well, if they did make that switch, it would be huge news. 00:53:59.961 --> 00:54:00.361 It would. 00:54:00.661 --> 00:54:01.661 Okay, all right. 00:54:01.881 --> 00:54:02.921 It's kind of a long show. 00:54:02.941 --> 00:54:07.361 I think we do need to be a little bit more specific about what recommended means. 00:54:07.741 --> 00:54:10.541 Recommended as the default download of the ISO. 00:54:10.541 --> 00:54:11.941 On the primary download page. 00:54:11.941 --> 00:54:14.581 Yeah, something along those lines would make me happy. 00:54:15.281 --> 00:54:18.001 So Fedora Atomic replaces Workstation 00:54:18.001 --> 00:54:22.521 as the recommended download on the primary project download page. 00:54:22.661 --> 00:54:23.081 Works for me. 00:54:23.361 --> 00:54:25.821 And if it doesn't change there, then the prediction... Yeah. 00:54:26.001 --> 00:54:27.481 Okay. All right, I'll give that a shot. 00:54:27.881 --> 00:54:33.181 In 2026, Fedora Atomic will replace Workstation as the recommended download 00:54:33.181 --> 00:54:35.961 on the project's primary download page. 00:54:37.601 --> 00:54:45.861 We shall see. So that's one. Now, I got to pick one that I think is a real curveball here. 00:54:46.261 --> 00:54:48.941 And I don't think this one's going to be a winner. But if it is, 00:54:49.061 --> 00:54:52.041 I'm going to feel like Nostradamus over here. 00:54:52.221 --> 00:54:53.101 Not Nosferati. 00:54:54.261 --> 00:55:01.261 Here's what I'm thinking about going with. I think Framework might launch their own distro in 2026. 00:55:01.761 --> 00:55:06.021 Framework computers. I want to know more about what you think it'll look like. 00:55:06.021 --> 00:55:10.941 So I think in part, we have seen them finance multiple projects this year, 00:55:10.981 --> 00:55:17.921 and that could be a great way to lay a bit of goodwill before you announce your own thing. 00:55:18.641 --> 00:55:24.181 And what made me think about this is they kind of need a framework edition OS 00:55:24.181 --> 00:55:29.741 just so that way when they do new edge products like their Snapdragon X Elite 00:55:29.741 --> 00:55:31.961 laptop that we talked about in LEP 641, 00:55:32.912 --> 00:55:37.572 In LUP641, we talked about how the generic kernels weren't enough for this new 00:55:37.572 --> 00:55:40.312 hardware, and that's been a pain point for Framework. 00:55:40.472 --> 00:55:44.712 If they have, like, a Framework Lite edition ISO, it might not be, 00:55:44.832 --> 00:55:47.472 like, a full-blown distro, but it's, like, a slightly, you know, 00:55:47.492 --> 00:55:51.252 amended distro that you could just download from them, and you could, 00:55:51.492 --> 00:55:55.112 say, install on a RISC-V development system or on an ARM. 00:55:55.112 --> 00:55:59.012 Not saying for points or anything, but just I'm curious. Do you have any ideas 00:55:59.012 --> 00:56:03.012 what they, in this hypothetical world of yours, how are they building this district? 00:56:03.752 --> 00:56:05.792 Well, they would make it arch-based like everybody else is doing. 00:56:05.792 --> 00:56:10.932 I think so. Yeah. I mean, if I were, I'm not going to put this in the prediction, 00:56:11.072 --> 00:56:14.912 but I would think maybe they do a little contract with DHH's company. 00:56:15.472 --> 00:56:15.872 Wow. 00:56:15.872 --> 00:56:16.892 Do a little business contract. 00:56:17.132 --> 00:56:17.252 Wow. 00:56:17.252 --> 00:56:18.092 Something that has some terms. 00:56:18.552 --> 00:56:19.752 Now that's a prediction. 00:56:19.952 --> 00:56:20.212 Yeah. 00:56:20.212 --> 00:56:23.232 I know. That is a prediction. I don't want to be that. 00:56:23.732 --> 00:56:24.692 No. Yeah. 00:56:26.092 --> 00:56:29.412 Interesting it could just be a fedora spin at the end of the day and that would still count. 00:56:29.412 --> 00:56:30.872 Sure i mean. 00:56:30.872 --> 00:56:31.332 This is kind. 00:56:31.332 --> 00:56:35.812 Of what we saw so 776 do right is they saw that having an officially supported 00:56:35.812 --> 00:56:40.372 os was easier for their hardware support and all that stuff fascinating so. 00:56:40.372 --> 00:56:41.852 You're thinking like an omaframey. 00:56:41.852 --> 00:56:47.572 Yeah basically a framework distro light. 00:56:47.572 --> 00:56:49.812 Why light sorry why are you. 00:56:49.812 --> 00:56:53.272 Well because i don't i don't think it's going to be a massive departure right 00:56:53.272 --> 00:56:56.832 i don't think they're going to have a customly in-house built desktop environment. 00:56:57.752 --> 00:57:01.152 I wouldn't expect it to be, I mean, it could be, but I wouldn't necessarily 00:57:01.152 --> 00:57:06.192 expect it to be, say, like SteamOS where it's image-based and things like that. I'm picturing... 00:57:06.192 --> 00:57:08.732 But it's more than them installing Ubuntu and putting a wallpaper on it. 00:57:09.629 --> 00:57:12.329 It could be as little as that, or it could be more than that. 00:57:13.109 --> 00:57:17.129 Basically, the key is it enables their hardware to run out of the box. 00:57:17.129 --> 00:57:20.329 So you ship with a kernel that has the right drivers that are signed and so 00:57:20.329 --> 00:57:23.729 forth for that particular hardware. That's the nut of what they're trying to accomplish. 00:57:23.929 --> 00:57:27.109 You can put any distro you want on there that's supported if it has the upstream 00:57:27.109 --> 00:57:30.609 drivers. But the idea is you can buy it with something that works out of the 00:57:30.609 --> 00:57:31.609 box. It doesn't run Windows. 00:57:32.309 --> 00:57:34.249 Framework branded distribution. 00:57:34.649 --> 00:57:34.949 Yeah. 00:57:35.089 --> 00:57:36.549 Yeah, framework branded distribution. 00:57:36.769 --> 00:57:36.949 Okay. 00:57:37.069 --> 00:57:43.029 Yeah. Okay, so how about in 2026, Framework will announce a Framework-branded distribution. 00:57:43.569 --> 00:57:44.189 Yeah. 00:57:44.329 --> 00:57:44.669 Does that work? 00:57:44.829 --> 00:57:45.689 Works pretty good to me. 00:57:46.109 --> 00:57:53.629 Here I go, gentlemen. In 2026, Framework will announce a Framework-branded Linux distribution. 00:57:55.814 --> 00:57:57.034 Watch him do it with FreeBSD. 00:57:57.254 --> 00:58:00.214 I noticed you said announce there, not ship. Interesting. Yeah, 00:58:00.274 --> 00:58:01.774 well, things are hard. I'm seeing a trend here. 00:58:02.434 --> 00:58:05.894 Things are hard. This is where, okay, I could use your guys' input. 00:58:06.814 --> 00:58:08.994 I have a couple of extras to go with. Yeah, let's see what you got. 00:58:08.994 --> 00:58:10.134 I don't know which direction to go with. 00:58:10.494 --> 00:58:15.614 One prediction is that a distribution, a rolling distribution, 00:58:16.254 --> 00:58:20.414 will replace sudo with run zero from systemd. 00:58:21.054 --> 00:58:21.494 Okay. 00:58:21.974 --> 00:58:26.774 And then my other prediction, and this is a little spicy, kdelinux 00:58:26.774 --> 00:58:32.494 misses a 1.0 in 2026 and maintains in the you know beta and rc state building 00:58:32.494 --> 00:58:38.514 a distro is hard and the last 10 15 is the hardest and then and this is the 00:58:38.514 --> 00:58:42.054 one i think is my weakest prediction but i feel the most conviction about so 00:58:42.054 --> 00:58:44.514 i don't know how to square and. 00:58:44.514 --> 00:58:47.074 You should go with that one clearly yeah. 00:58:47.074 --> 00:58:47.934 I said second brent. 00:58:47.934 --> 00:58:54.774 Okay here's the prediction in 2026 refurb used and upgrade not replace becomes 00:58:54.774 --> 00:58:59.974 the top Homelab narrative showing up as a dominant theme across Linux and Homelab 00:58:59.974 --> 00:59:01.974 channels on Reddit and other communities. 00:59:02.154 --> 00:59:03.294 Oh yeah, I think that's a good one. 00:59:03.454 --> 00:59:05.914 That's a good one, but that's real hard to prove. 00:59:05.934 --> 00:59:07.454 That's going to be true, but impossible to measure. 00:59:07.594 --> 00:59:12.834 Yeah, I know. Well, so I figured the way you'd measure it is there'd be a couple 00:59:12.834 --> 00:59:14.314 of scoreable success criteria. 00:59:14.514 --> 00:59:18.294 You'd have to look at our Homelab and our self-hosted and our Linux and see 00:59:18.294 --> 00:59:21.694 how often keywords like refurb, used, e-waste, old hardware, 00:59:21.874 --> 00:59:26.194 upgrade, DDR4, DDR5, SAS, enterprise surplus were used. 00:59:26.754 --> 00:59:32.614 Maybe two major outlets like Serve the Home, Level 1 Techs, Pharonix, the LWN. 00:59:32.854 --> 00:59:38.394 They have articles or videos explaining, you know, centered around surplus, refurb hardware. 00:59:39.114 --> 00:59:42.134 And this probably doesn't count, but I would also imagine it becomes a topic 00:59:42.134 --> 00:59:44.574 on this show too. It'll become a topic throughout the show. 00:59:44.834 --> 00:59:45.634 Isn't it already? 00:59:45.734 --> 00:59:51.034 Because, well, I mean, it's already so bad. And with the RAM and... 00:59:51.759 --> 00:59:56.999 and the disk prices and GPU prices already crazy, I really think it's going 00:59:56.999 --> 01:00:00.979 to be a year about getting every inch out of the hardware you already have. 01:00:01.239 --> 01:00:07.419 And honestly, there is room. Stock distributions have room for improvements. We've played with this. 01:00:07.539 --> 01:00:11.359 And you can get better performance if you are willing to dig into it. 01:00:11.479 --> 01:00:17.119 So I think that type of system optimization and reusing hardware is going to 01:00:17.119 --> 01:00:18.819 be a major trend for 2026. 01:00:19.119 --> 01:00:21.499 Okay. So here's the way I see it. 01:00:21.499 --> 01:00:23.279 Do you like that one more than the KDE Linux one? 01:00:24.379 --> 01:00:27.139 I do. I think it's a more interesting prediction. 01:00:27.459 --> 01:00:27.779 Okay. 01:00:27.959 --> 01:00:31.619 I also think it's the one that's going to piss you off the most when you actually 01:00:31.619 --> 01:00:33.519 have to go and collect the statistics. 01:00:34.619 --> 01:00:34.939 100%. 01:00:35.799 --> 01:00:37.139 Yeah, yeah, yeah, yeah. 01:00:37.199 --> 01:00:38.119 It's your funeral. 01:00:39.879 --> 01:00:42.679 Yeah, if I could think of a really good way to measure it, I would feel better about it. 01:00:43.079 --> 01:00:44.999 But also, who's going to verify your measurements? 01:00:46.119 --> 01:00:46.439 Yeah. 01:00:46.679 --> 01:00:49.499 Well, no, I think, no, it would have to be like, it would have to be. 01:00:49.999 --> 01:00:51.279 Submit the code for review. 01:00:51.499 --> 01:00:51.759 Yeah. 01:00:52.899 --> 01:00:56.819 Ideally, should we build stats, start building stats now to see what the baseline is? 01:00:56.819 --> 01:00:56.899 Right. 01:00:57.679 --> 01:01:00.859 Yeah, you'd have to be based on, like, coverage, community discussions. 01:01:01.339 --> 01:01:02.919 You got to bring your homework. Podcasts and YouTube videos. 01:01:03.079 --> 01:01:06.059 Is the thing. When you go to prove this out. 01:01:06.999 --> 01:01:10.199 You could do it another way. You could say, like... 01:01:10.935 --> 01:01:16.395 the trend becomes so powerful that like there's a new pod, three new podcasts 01:01:16.395 --> 01:01:21.795 that start specifically angling that or like an, you know, 10 new YouTube channels 01:01:21.795 --> 01:01:24.215 are specifically about refurbing or something like that. 01:01:24.475 --> 01:01:25.615 My old home lab. 01:01:25.875 --> 01:01:30.975 This old home lab. That's less. You should have sent that URL. That's good. 01:01:32.335 --> 01:01:35.835 Micro center has a, a used home lab. 01:01:36.575 --> 01:01:38.155 There you go. There you go. 01:01:38.955 --> 01:01:41.735 Honestly i want to do a this old home lab segment where we go 01:01:41.735 --> 01:01:44.815 out and we refurb on listeners home labs so i 01:01:44.815 --> 01:01:47.995 want to do that i mean this is to me seems 01:01:47.995 --> 01:01:52.095 like it's at least going to be a strong narrative for most of the year if it 01:01:52.095 --> 01:01:56.495 dominates 2026 is yet to be seen but like drew if your prediction plays out 01:01:56.495 --> 01:02:02.395 where nvidia pulls out of the consumer market and if the uh who was it also 01:02:02.395 --> 01:02:05.275 was just announced that they might be leaving the consumer market just just 01:02:05.275 --> 01:02:06.935 yesterday or the day before on Friday. 01:02:07.815 --> 01:02:10.395 Another company announced that they're probably pulling out of the consumer 01:02:10.395 --> 01:02:12.695 market. It's getting rough out there. 01:02:13.555 --> 01:02:17.995 So, yeah, the measuring it, the proof is going to be to measuring it at the time. 01:02:19.195 --> 01:02:24.755 And I guess if we said two major outlets, so if I said something like two major 01:02:24.755 --> 01:02:33.595 outlets on YouTube and in writing and dominant themes on our home lab self-hosted in our Linux. 01:02:33.595 --> 01:02:38.695 Is that the dominant themes is hard to measure right yeah. 01:02:38.695 --> 01:02:39.595 It is mm-hmm, 01:02:41.365 --> 01:02:42.565 But probably achievable. 01:02:43.365 --> 01:02:47.505 Well, you could sort the posts for the year, and if the top five, 01:02:48.245 --> 01:02:52.185 I don't know, 50% of the top 10 posts are about it. 01:02:52.185 --> 01:02:54.765 I don't know if it'll materialize like that or if it would just be a lot of chatter. 01:02:55.205 --> 01:02:57.885 Well, you got to measure this thing. 01:02:58.045 --> 01:02:58.245 Yeah. 01:02:58.825 --> 01:03:02.745 It's a good prediction, but it's nebulous. 01:03:03.545 --> 01:03:10.165 Primary verification signal to me seems like news coverage and just frequency 01:03:10.165 --> 01:03:14.245 of YouTube videos, subreddit posts podcasts like if like if you know at the 01:03:14.245 --> 01:03:16.765 end of the year if we can measure that somehow all. 01:03:16.765 --> 01:03:22.945 Right look if i'm judging again when you go to prove this out there had better 01:03:22.945 --> 01:03:26.965 be a pepe sylvia style board behind. 01:03:26.965 --> 01:03:28.425 You yeah. 01:03:28.425 --> 01:03:31.905 There we go build the board prove it out yeah and i. 01:03:31.905 --> 01:03:33.285 Recommend working. 01:03:33.285 --> 01:03:34.505 On this thing through the year. 01:03:34.505 --> 01:03:37.965 I mean maybe i shouldn't go with this one because like the KDE Linux doesn't 01:03:37.965 --> 01:03:41.925 hit 1.0 would be easy to measure, or say Tumbleweeder Arch switching to run zero. 01:03:41.925 --> 01:03:43.545 But it's quite plain as a prediction. 01:03:43.785 --> 01:03:47.285 I'll give it a go, and if I can't argue my case, I'll have to take the L next 01:03:47.285 --> 01:03:50.165 year. Probably going to hate that I did this, but I could do it. 01:03:50.225 --> 01:03:56.105 What about like a well-established podcast takes it up as a topic that they 01:03:56.105 --> 01:03:59.045 would have never done in the past? Because it's like... 01:03:59.425 --> 01:04:01.125 I just don't know if I'd notice that. 01:04:01.625 --> 01:04:02.885 Well, that's up to you, man. 01:04:04.325 --> 01:04:06.825 Can you imagine me spending my entire year You're scouring the web. 01:04:07.525 --> 01:04:08.645 Isn't that what you do anyway? 01:04:09.665 --> 01:04:10.745 I must be right. 01:04:12.926 --> 01:04:14.506 If you can measure it, I think it's a good one. 01:04:14.586 --> 01:04:19.386 Yeah, it's a really good one. I like it. But, yeah, you've got to put in the legwork. 01:04:19.486 --> 01:04:24.826 Okay, how about reused, refurb, upgrade, not replace, becomes a top homelab 01:04:24.826 --> 01:04:32.066 narrative showing up as a dominant theme across YouTube, Reddit, and news outlets. 01:04:33.166 --> 01:04:37.046 Not a dominant theme across news outlets, but showing how about as a reoccurring theme. 01:04:37.766 --> 01:04:41.526 I don't know if that's also very – See, this sucks, you guys. This one sucks. 01:04:41.866 --> 01:04:42.086 It's tricky. 01:04:43.066 --> 01:04:44.326 How bad do you want it? 01:04:44.366 --> 01:04:48.326 Recurring theme isn't terrible. It could probably be improved. 01:04:48.566 --> 01:04:49.346 Come on, chat room. 01:04:49.966 --> 01:04:52.786 How do you yes or no the prediction? That's the real question. 01:04:52.906 --> 01:04:54.646 What's the tip over point? 01:04:55.126 --> 01:04:57.026 What about Google Trend words? 01:04:57.666 --> 01:04:58.006 Oh. 01:04:58.346 --> 01:04:59.166 Ah, yeah, okay. 01:04:59.966 --> 01:05:01.486 So as measured by Google Trends? 01:05:02.675 --> 01:05:04.555 Yeah, but would you define a set of... 01:05:04.555 --> 01:05:05.575 You have to take a base for it. 01:05:05.575 --> 01:05:05.675 Yeah. 01:05:05.775 --> 01:05:06.315 ...thing you plug in. 01:05:06.495 --> 01:05:11.095 Yeah. I have them here in the doc. Refurb, used, e-waste, old hardware, 01:05:11.255 --> 01:05:16.815 upgrade, DDR4, DDR5, SAS, enterprise surplus, those types of things. 01:05:17.555 --> 01:05:19.475 If they trend strongly upwards. 01:05:20.135 --> 01:05:27.555 Yeah, okay. In 2026, refurb, used, upgrade, not replace, terms that get the 01:05:27.555 --> 01:05:32.415 most out of old hardware will see an uptick on Google Trends. That's pretty... 01:05:33.995 --> 01:05:37.755 we gotta move on so I'm gonna lock it in even though it's crap no I think that's 01:05:37.755 --> 01:05:40.935 okay it is okay we'll argue it next. 01:05:40.935 --> 01:05:43.975 Year it's fine see the terms say see the terms in the doc yeah. 01:05:43.975 --> 01:05:52.335 Yeah terms of fable in show doc there you go I love that alright okay okay I'm gonna try this, 01:05:53.315 --> 01:06:00.335 in 2026 refurb used upgrade not replace these types of topics become a top narrative 01:06:00.335 --> 01:06:06.295 on Homelab subreddits YouTube and news outlets and I will have terms in the 01:06:06.295 --> 01:06:10.835 doc that can be used for Google trend searches and others good enough, 01:06:11.955 --> 01:06:16.015 not great but I like the sentiment because it just feels like and I think it's 01:06:16.015 --> 01:06:21.115 an area where Linux is kind of super positioned to do really well it's a sucky 01:06:21.115 --> 01:06:25.235 position for us all to be in but this is like our moment to shine too so the 01:06:25.235 --> 01:06:26.915 Linux wave continues that's strange our. 01:06:26.915 --> 01:06:29.455 Show doc just changed with new tags in it. 01:06:30.255 --> 01:06:30.955 Yeah it seems. 01:06:30.955 --> 01:06:32.575 To be dynamically updating throughout the year. 01:06:38.507 --> 01:06:42.247 Join crowd health dot com and use the promo code unplugged. 01:06:42.327 --> 01:06:47.607 The clock is ticking and these are hard decisions that need to be made. It's enrollment time. 01:06:47.827 --> 01:06:51.307 The season where the health insurance companies hope you're just going to sign up and pay for more. 01:06:51.507 --> 01:06:54.547 It's expensive every single year. And then when you really need it, 01:06:54.647 --> 01:06:58.307 it's awful. And if you're a small business owner, well, the story is just a 01:06:58.307 --> 01:06:59.387 nightmare here in the States. 01:06:59.567 --> 01:07:03.367 You should really go check out crowd health. Join crowd health dot com and use 01:07:03.367 --> 01:07:07.427 the promo code unplugged. CrowdHealth is a community of people that fund each 01:07:07.427 --> 01:07:08.567 other's medical bills directly. 01:07:08.787 --> 01:07:12.307 No middleman, no networks, no nonsense. 01:07:12.507 --> 01:07:17.627 It's stress-free. I've been a member for over three years, and I've saved thousands 01:07:17.627 --> 01:07:19.367 of dollars. My wife's a member, too. 01:07:19.967 --> 01:07:23.927 You can get health care for under $100. You get access to a team of health bill 01:07:23.927 --> 01:07:27.847 negotiators, access to low-cost prescriptions, lab testing tools. 01:07:27.987 --> 01:07:28.787 Man, has that been handy. 01:07:29.107 --> 01:07:32.927 As well as a database of low-cost, high-quality doctors that have been vetted 01:07:32.927 --> 01:07:35.287 by CrowdHealth. And they've been around for a minute now. 01:07:35.487 --> 01:07:38.447 I mean, I've been a member for over three years, and they were around before I started. 01:07:38.667 --> 01:07:42.747 But they've been really refining that app, giving you access to all of this in just seconds. 01:07:42.947 --> 01:07:46.027 It really is a nice way to go. And when something major happens, 01:07:46.207 --> 01:07:50.347 you pay the first $500, and then the crowd steps in and helps you fund the rest. 01:07:50.907 --> 01:07:55.087 It's really the way things should be working, and it's a great option for a 01:07:55.087 --> 01:07:58.427 lot of us. But I think, don't take my word for it, you should go check it out yourself. 01:07:58.607 --> 01:08:02.947 Go to joincrowdhealth.com, and if you sign up, use the promo code UNPLUGGED. 01:08:02.947 --> 01:08:07.987 You become part of the crowd who want to help pay for each other's bills and 01:08:07.987 --> 01:08:09.167 save money on insurance. 01:08:09.407 --> 01:08:12.787 I mean, it's it really doesn't need to be so expensive. And the system, 01:08:12.927 --> 01:08:15.907 the system is so broken. They're just they're betting your stay in it. 01:08:16.307 --> 01:08:18.627 And I opted out several years ago. 01:08:19.544 --> 01:08:23.784 You can too. So go check it out. CrowdHealth members have saved over $40 million 01:08:23.784 --> 01:08:26.784 in health expenses because they refuse to overpay for health care. 01:08:26.944 --> 01:08:30.764 It is open enrollment season, so go take your power back. So go join CrowdHealth 01:08:30.764 --> 01:08:34.564 at joincrowdhealth.com, and you'll get started when you use our promo code UNPLUGGED, 01:08:34.584 --> 01:08:38.824 $99 for your first three months. It really is awesome. 01:08:39.964 --> 01:08:44.164 Joincrowdhealth.com, and that's promo code UNPLUGGED. CrowdHealth isn't insurance. 01:08:44.164 --> 01:08:46.244 You can opt out. You can take your power back. 01:08:46.444 --> 01:08:52.224 This is how we make a difference. Join crowdhealth.com, promo code unplugged. Join me in the crowd. 01:08:52.784 --> 01:08:55.504 Join crowdhealth.com, promo code unplugged. 01:08:57.876 --> 01:09:04.296 Unraid.net slash unplugged. Unleash your hardware and start 2026 off right by 01:09:04.296 --> 01:09:06.376 reducing your dependency on the cloud. 01:09:06.556 --> 01:09:09.836 Go build the system you have right now or your dream server. 01:09:10.016 --> 01:09:11.136 Unraid will grow with you. 01:09:11.536 --> 01:09:14.676 Unraid.net slash unplugged to get you started. 30-day free trial. 01:09:14.876 --> 01:09:18.136 It's really something. And recently 7.2 came out. 01:09:18.256 --> 01:09:21.356 There has been some incredible improvements in there, really nice improvements 01:09:21.356 --> 01:09:24.216 to the web UI to make it responsive so you can work on your couch, 01:09:24.216 --> 01:09:27.896 on your mobile device, which, come on, that's actually really great. 01:09:27.996 --> 01:09:29.496 You're sitting there watching kind of a low-key show. 01:09:29.636 --> 01:09:33.036 You can sit there and poke on your home NAS, right, install a new application. 01:09:33.556 --> 01:09:37.276 And with the Unraid API available now, there's some really cool, 01:09:37.436 --> 01:09:41.696 powerful applications and dashboards being built, and they've expanded their ZFS support. 01:09:41.836 --> 01:09:46.036 They have NTFS support now for Grampus Photos, and the really great thing is 01:09:46.036 --> 01:09:48.016 the growing community app repository. 01:09:48.416 --> 01:09:51.196 I don't think there's been an application we've talked about on the show yet 01:09:51.196 --> 01:09:54.116 that isn't just essentially a click away on an 01:09:54.116 --> 01:09:56.816 unraid system and they have different versions depending on your 01:09:56.816 --> 01:09:59.956 hardware so if you have an all intel system well they'll 01:09:59.956 --> 01:10:02.816 have builds optimized for that or if you have an nvidia or 01:10:02.816 --> 01:10:06.136 amd etc etc you'll find community versions of some of these apps where it really 01:10:06.136 --> 01:10:09.796 matters they'll they'll special optimize them for your different gpus meaning 01:10:09.796 --> 01:10:13.716 it's a one click install to get something that's optimized for your particular 01:10:13.716 --> 01:10:18.736 hardware be it with gpu or without and that's just kind of a taste it's really 01:10:18.736 --> 01:10:22.136 it's such a powerful aspect to unraid is those community applications. 01:10:22.456 --> 01:10:27.896 And now, really, that new responsive web and that API. You bring it all together. 01:10:28.296 --> 01:10:31.236 Unraid's built on top of a modern Linux system that they've been maintaining 01:10:31.236 --> 01:10:34.716 now for over 20 years, and they're going strong from strength to strength. 01:10:34.936 --> 01:10:39.636 It's so great, and I think you're going to love it, especially for those of you that have a weekend. 01:10:39.976 --> 01:10:43.416 You've got some hardware in your closet right now. You want to try a project. 01:10:44.416 --> 01:10:47.776 Unraid.net slash unplugged. You get started right away and you get going. 01:10:47.956 --> 01:10:51.656 Check it out. Support the show. Unraid.net slash unplugged. 01:10:54.908 --> 01:10:57.848 Well, happy holidays, everybody. As we're nearing the end of the year, 01:10:58.028 --> 01:11:01.068 we have some baller boosters this week. 01:11:01.808 --> 01:11:05.628 A baller booster of baller boosters. Chris, you want to take this one? 01:11:05.708 --> 01:11:09.128 You saw it come in and you kind of like lost your cool. 01:11:09.828 --> 01:11:12.708 Well, Optic Gray is our baller booster. 01:11:16.308 --> 01:11:23.288 And get ready for this, gentlemen. Brace yourselves. 1.5 million Satoshis. 01:11:23.948 --> 01:11:25.108 Oh, wow. 01:11:29.008 --> 01:11:29.028 I... 01:11:40.024 --> 01:11:41.344 It's absolutely amazing. 01:11:41.524 --> 01:11:43.184 I don't think baller is the right word anymore. 01:11:43.404 --> 01:11:46.344 No, no. Hello, Chris, Brenton, and Wes. 01:11:46.524 --> 01:11:49.644 Happy holidays. I don't know if you remember, but I wanted to reminisce about 01:11:49.644 --> 01:11:53.064 a trip I made back in 2019 to the Texas cyberside. 01:11:53.304 --> 01:11:53.324 Oh. 01:11:55.164 --> 01:11:59.044 The conference itself was meh. Yep. 01:11:59.604 --> 01:12:03.124 But it was completely overshadowed by the evening I got to spend with you two. 01:12:03.364 --> 01:12:06.684 Carl, special thanks for paying chauffeur and cheese and a bunch of other JB 01:12:06.684 --> 01:12:09.224 fans while gallivanting around San Antonio. 01:12:09.864 --> 01:12:13.004 The night remains one of my most cherished memories, and I'm still incredibly 01:12:13.004 --> 01:12:15.384 thankful to all of you for being so gracious. 01:12:16.024 --> 01:12:19.284 Wow. Well, thank you, Optic. That's amazing. 01:12:19.664 --> 01:12:21.624 And he said that in where he had some trouble with Fountain, 01:12:21.644 --> 01:12:24.904 he was persistent and kept going anyways. We really appreciate that. 01:12:25.804 --> 01:12:30.484 And I would say it was that evening that was the singular highlight of our trip. 01:12:30.704 --> 01:12:31.584 Yes, definitely. 01:12:31.944 --> 01:12:32.184 Yeah. 01:12:32.384 --> 01:12:36.484 We'll have to run into another, some kind of event, hopefully a better event, but some kind of event. 01:12:36.644 --> 01:12:42.344 Yeah. Hopefully we'll be down in Texas next year. That's my prediction. We go to Texas in 2026. 01:12:42.964 --> 01:12:43.964 It's a good one. 01:12:44.124 --> 01:12:45.804 Hopefully we'll see you there. Thank you for that baller boost. 01:12:45.964 --> 01:12:50.824 We tremendously appreciate it. Fantastic way to wrap up the year and kick off the new year. 01:12:52.604 --> 01:12:56.844 The Dude Abides comes in with 247,000 Satoshis. 01:12:57.744 --> 01:12:58.184 Wow. 01:13:05.234 --> 01:13:08.514 247. Sounds great number. The dude abides writes, hey, alas, 01:13:08.634 --> 01:13:10.134 boost of the year. I finally caught up. 01:13:10.274 --> 01:13:13.874 I always like to listen to the full members episode, so it takes some time. 01:13:14.094 --> 01:13:16.394 I enjoyed the last episode with Kent and Carl. 01:13:16.754 --> 01:13:19.194 Keep them coming. Also, thanks for the IPTV suggestions. 01:13:19.714 --> 01:13:23.394 I almost had no idea this existed. I managed to submit my home lab in time, 01:13:23.494 --> 01:13:26.354 so I'm excited to listen to this episode, although not sure if I'll catch it live. 01:13:26.994 --> 01:13:29.494 But it would be fun to have Alex on the show to roast our setups. 01:13:29.634 --> 01:13:31.594 Oh, that would be a great addition. 01:13:31.914 --> 01:13:32.274 That would be good. 01:13:32.434 --> 01:13:35.714 That would be a great addition to next year, wouldn't it? We should consider that. 01:13:36.834 --> 01:13:40.734 Thanks for the holidays, gents, and the company. Well, thank you, the dude abides. 01:13:41.214 --> 01:13:41.694 Keep abiding. 01:13:42.074 --> 01:13:43.014 We really appreciate that. 01:13:43.254 --> 01:13:45.894 Do we have to redo the boosties because of these two boosts? 01:13:46.094 --> 01:13:52.474 I know, right? Also, we should mention, these are not even all of the boosts 01:13:52.474 --> 01:13:54.314 because we're a little out of time. 01:13:54.514 --> 01:13:57.914 We're going to do another batch in the next episode. So if you do not hear your 01:13:57.914 --> 01:14:02.354 boost read this episode, we have it banked and it'll be in next episode. 01:14:02.354 --> 01:14:03.934 So thank you very, very much for sending it in. 01:14:04.214 --> 01:14:07.534 Just for time, we're doubling them up and also because of the recording schedule. 01:14:09.134 --> 01:14:13.514 Nostromo boosts in with 37,879 sats. 01:14:13.754 --> 01:14:14.154 I like that. 01:14:17.281 --> 01:14:22.201 Thank you for another year of great entertainment, and happy new year to all of you. 01:14:22.361 --> 01:14:26.661 Happy new year to you. Thank you very much, Nostro. Appreciate that. 01:14:26.881 --> 01:14:28.521 Appreciate that value, too. It's good to hear from you. 01:14:28.641 --> 01:14:33.801 I'll take Amunday here, too. Amunday Boosin with 24,444 sats. 01:14:34.761 --> 01:14:35.661 Not too bad. 01:14:36.121 --> 01:14:41.621 Ah, and answering a question. Yes, Signal is still absolutely the best secure messenger. 01:14:41.781 --> 01:14:45.361 Or maybe MOLLE, which is just an alternate but compatible version of the Signal 01:14:45.361 --> 01:14:50.161 client with a handful of security improvements and optional settings made mandatory. 01:14:50.621 --> 01:14:54.001 There's periodically FUD varying ridiculousness around Signal, 01:14:54.081 --> 01:14:55.281 but it carries on through the noise. 01:14:55.701 --> 01:14:58.901 I'm continually impressed by how everything Signal does is from an explicitly 01:14:58.901 --> 01:15:00.061 security-first position. 01:15:00.281 --> 01:15:06.121 The one maybe legitimate criticism of it was that it used to require a... Oh, that got cut off. 01:15:06.441 --> 01:15:06.881 Oh! 01:15:07.701 --> 01:15:08.901 I believe it's... 01:15:08.901 --> 01:15:09.321 Phone number. 01:15:09.721 --> 01:15:10.021 Yeah, exactly. 01:15:10.381 --> 01:15:12.181 But that was recently addressed. 01:15:12.761 --> 01:15:13.281 Yeah, yeah. 01:15:13.281 --> 01:15:19.101 Also, Amadei here wanted to say that they really enjoyed the conversation with Kent. 01:15:20.261 --> 01:15:22.441 So we've seen more continued support there. 01:15:22.601 --> 01:15:25.461 We really do appreciate that signal. You don't have to send us a huge boost, 01:15:25.561 --> 01:15:30.861 but that is a big signal for us to continue that kind of stuff. That's a great boost. 01:15:31.461 --> 01:15:33.381 Really nice. Thank you, Amadei. Appreciate that. 01:15:34.241 --> 01:15:39.421 Well, Johnny Castaway sends in 19,045 sats under two boosts. 01:15:39.541 --> 01:15:44.121 boosts and one of those boosts is a one two three four five satoshi boost oh. 01:15:44.121 --> 01:15:47.001 Sneaking in there well let's give them a little let's give them some fruit loops 01:15:47.001 --> 01:15:58.861 which everybody loves thank you very much and of course a little space balls nicely done. 01:15:58.861 --> 01:16:03.381 The johnny here is a long time listener and jupiter signal member just saying 01:16:03.381 --> 01:16:08.801 hello from the south coast of england that's in devon uk oh hello Oh. 01:16:10.319 --> 01:16:11.799 Thanks for sending the letter all this way. 01:16:12.259 --> 01:16:17.039 I've just upped my Knicks game and now running Knicks Flakes with BcashFS, 01:16:17.399 --> 01:16:22.239 ZSwap, FBE, Plymouth, Gnome, and Neary desktops. 01:16:22.979 --> 01:16:27.799 Oh, by the way, some little tail scale with a work in progress to give Nebula a try. 01:16:28.419 --> 01:16:33.199 I'm off to Fosdom early next year, my first Linux expo, and very excited. 01:16:33.659 --> 01:16:37.499 And have some mince pies on me with some Santa sets. 01:16:38.139 --> 01:16:40.679 Thank you very much. You ever had mince pie with? 01:16:40.979 --> 01:16:42.559 No, but I think we got to go get some. 01:16:42.719 --> 01:16:47.519 I think so. Also, if you are interested, and this goes out to everyone too, 01:16:47.739 --> 01:16:51.919 but especially to you, Johnny, if you would like to send us a Fosdom report, 01:16:52.159 --> 01:16:56.179 especially from a perspective of a new person, we would very much love to read those on the show. 01:16:56.999 --> 01:16:59.559 That would be a good signal. If you're interested. 01:16:59.779 --> 01:17:00.239 Good idea. 01:17:01.099 --> 01:17:04.039 Johnny continues here with the second boost. Just wanted to say I enjoyed the 01:17:04.039 --> 01:17:08.979 show on Bcash FS. amazing work by Kent and the JB crew for the great content. 01:17:09.179 --> 01:17:12.919 As always, this gave me the extra motivation I needed to switch up my daily 01:17:12.919 --> 01:17:20.079 driver, a Nix OS T460P ThinkPad with Bcache FS, Cache OS kernel using my favorite 01:17:20.079 --> 01:17:23.679 terminal emulator, Ghost TTY and Neary desktop. 01:17:24.379 --> 01:17:28.339 It's been rock solid. And by the way, the boost amount is cryptic, 01:17:28.519 --> 01:17:30.019 but related to Bcache FS. 01:17:30.879 --> 01:17:36.919 Oh, interesting. 6, 7, 7, 100. Oh, Maybe a commit number? 01:17:38.219 --> 01:17:42.279 I think my prediction should have been something about how much of the audience is running Bcache. 01:17:42.399 --> 01:17:42.699 Really? 01:17:43.019 --> 01:17:43.079 Yeah. 01:17:44.239 --> 01:17:48.419 I love to hear how it goes. Keep us posted on that, too. And CacheOS Kernel, 01:17:48.459 --> 01:17:50.999 I agree, is pretty great, even on NixOS. 01:17:51.299 --> 01:17:53.859 So good to hear. Thank you for that. 01:17:54.479 --> 01:17:58.119 Thor's coming in with a row of ducks. That's 2,222 sats. 01:17:59.449 --> 01:18:03.029 And he says he loved the People's File System episode. Now I really need to 01:18:03.029 --> 01:18:07.349 try out Bcache FS. I have an upcoming reinstall for sure. 01:18:08.249 --> 01:18:11.929 Yeah. I do that thing, too. Like, I'm thinking about my next install, 01:18:11.969 --> 01:18:14.709 and I'm like, okay, this time around, I'm going to do Bcache FS. 01:18:14.729 --> 01:18:16.589 I'm going to do a two-gigabyte boot. 01:18:16.849 --> 01:18:17.829 New install dreams. 01:18:18.009 --> 01:18:18.349 Yes. 01:18:18.589 --> 01:18:18.689 Yes. 01:18:19.469 --> 01:18:22.249 Even when the system's totally fine, I already start planning the next system. 01:18:22.349 --> 01:18:23.749 You got to think about something while you're falling asleep. 01:18:23.929 --> 01:18:26.529 That's true. Thank you, Thor. Appreciate that. Boost. 01:18:27.929 --> 01:18:31.649 Adagia boosts in with 6,969 sets. 01:18:32.089 --> 01:18:32.569 Cryptic. 01:18:35.089 --> 01:18:41.089 Love the chat with Kent as well as the one with Carl today. Our pal Carl from System76 of course. 01:18:41.269 --> 01:18:42.249 Yeah, and the new Cosmic release. 01:18:42.569 --> 01:18:46.509 The technical episodes are some of my favorite, but then I often find myself 01:18:46.509 --> 01:18:49.689 not knowing what to say, kind of addressing boosting or not. 01:18:49.869 --> 01:18:53.069 I also need to remind myself that when small boosts still give you signal even 01:18:53.069 --> 01:18:56.289 though I can't afford much beyond the party membership, and we really appreciate 01:18:56.289 --> 01:18:59.829 the boost amount I mean a huge amount of the value is just the message. 01:19:00.349 --> 01:19:01.869 Yeah and thank you for being a party member. 01:19:03.089 --> 01:19:08.429 Also Brent's comment reminded me have you guys read ADHD is awesome would 110% 01:19:08.429 --> 01:19:12.869 recommend wow got it on yeah and then there's some links and we can find some 01:19:12.869 --> 01:19:16.789 links maybe to it to add to the show notes thank you for the recommendation. 01:19:18.129 --> 01:19:20.049 ADHD I think the answer is no. 01:19:20.049 --> 01:19:20.909 This is a great. 01:19:20.909 --> 01:19:23.769 Recommendation I have not heard of that thank you yes I will look into that. 01:19:23.769 --> 01:19:26.629 Sounds like there should be an audio book available as well Oh. 01:19:26.689 --> 01:19:28.869 That's probably the route I'm going to go, you know, with ADD and all. 01:19:31.729 --> 01:19:32.969 I'll put a link to that in the show notes. 01:19:33.569 --> 01:19:34.309 Thank you, Daja. 01:19:34.689 --> 01:19:35.569 Thank you very much. 01:19:36.349 --> 01:19:41.849 Well, the Sithy Penguin boosted in. This is two boosts with rows of ducks. 01:19:45.443 --> 01:19:51.203 Hello there, JB Crew. I'm a medium-term listener question. What is the minimum 01:19:51.203 --> 01:19:53.083 time required for a long-time listener anyway? 01:19:53.963 --> 01:19:57.803 Either way, I've been listening for a few years now, and it's my first boost 01:19:57.803 --> 01:20:01.883 to any of the shows, but I did leave a voicemail on launch earlier this year. 01:20:02.683 --> 01:20:03.103 Nice. 01:20:03.423 --> 01:20:04.503 Well done. Thank you. 01:20:05.263 --> 01:20:06.323 A vocal boost. 01:20:06.323 --> 01:20:12.983 I am dropping my nix config for the next config confessions it's about 95 percent 01:20:12.983 --> 01:20:17.483 vibe coded with flakes and hyperland which i have yet to fully grasp but the 01:20:17.483 --> 01:20:19.143 next nerds room has been great. 01:20:19.143 --> 01:20:22.723 Oh good i'm glad to hear that it is a very helpful room. 01:20:22.723 --> 01:20:28.283 We didn't even open the next config confessions and we're already getting submissions this is great, 01:20:30.115 --> 01:20:34.195 Second Boost here says, hey, question for the crew. Do you ever collaborate 01:20:34.195 --> 01:20:37.675 with any of the other podcasters out there? 01:20:37.935 --> 01:20:40.895 Aside from all the stuff you guys have done since I tuned in, 01:20:41.535 --> 01:20:44.515 we'd love to see more collaborations with other Linux podcasts. 01:20:45.055 --> 01:20:48.815 That's a great – in fact, I meant to mention at the top of the show, 01:20:49.095 --> 01:20:53.355 Michael Tunnell from Tux Digital and Destination Linux was going to join us 01:20:53.355 --> 01:20:57.395 today for this episode but ended up with a sore throat and was traveling, 01:20:57.395 --> 01:20:59.175 so the two combined just couldn't make it work. 01:20:59.695 --> 01:21:05.075 because we do want to do more of that, but the reality is all of us are super 01:21:05.075 --> 01:21:06.615 busy making the shows that we make. 01:21:06.915 --> 01:21:09.775 Yeah, the double calendar system. 01:21:09.935 --> 01:21:15.415 I mean, just trying to schedule this week's episode was a little tricky, 01:21:15.515 --> 01:21:17.975 right? And then also additionally, there's time zones. 01:21:18.095 --> 01:21:21.495 So some people are on opposite times and stuff like that. 01:21:21.775 --> 01:21:25.035 So that is a compounding issue. So you'll often find a lot of us are just very 01:21:25.035 --> 01:21:28.555 heads down. But around the holidays, we try to reach out a little bit. 01:21:29.275 --> 01:21:31.395 Hopefully we can do some more collabs in 2026. 01:21:31.535 --> 01:21:35.795 Yeah, absolutely. And as far as what makes a medium-term listener? 01:21:37.835 --> 01:21:42.395 Well, so it's tough to say because the show's been going for a while. So maybe a year? 01:21:43.735 --> 01:21:48.695 Or maybe we need like, you know, like there's sort of like geologic eras. 01:21:48.835 --> 01:21:49.875 Maybe we need that for the show. 01:21:50.135 --> 01:21:50.575 Like E-Pons. 01:21:50.575 --> 01:21:51.075 Different eras. 01:21:51.695 --> 01:21:54.475 That is often a thing, right? That is often the way people... 01:21:54.475 --> 01:21:56.495 As a reference point. I kind of joined in this, yeah. 01:21:56.495 --> 01:22:01.335 Were you here for LUP 600 or not, you know, the pre-600 or post-600? 01:22:01.775 --> 01:22:05.175 If you're here before 600, you're probably no longer medium term. 01:22:05.255 --> 01:22:09.795 And if you're here before 300, you're probably a long time. I don't know. You could cut that out. 01:22:09.795 --> 01:22:11.515 Going forward, pre-van and post-van. 01:22:11.735 --> 01:22:15.195 Yeah, yeah. The van era. Sure, sure, sure, sure. 01:22:15.715 --> 01:22:19.835 That's great. All right. Thank you very much. Thank you for setting up the booze 01:22:19.835 --> 01:22:20.815 stuff, too, and setting that in. 01:22:20.915 --> 01:22:23.595 Really appreciate it. I know that takes a bit of work. And the beginning of 01:22:23.595 --> 01:22:25.035 the journey is the hardest guy. 01:22:25.655 --> 01:22:29.035 Thank you, Penguin Guy. Appreciate you. Hybrid sarcasm. There he is. 01:22:29.115 --> 01:22:30.695 Comes in with 10,000 sats. 01:22:33.252 --> 01:22:34.792 And he just says, Merry Christmas, boys. 01:22:35.452 --> 01:22:37.132 Oh, Merry Christmas to you too, Hybrid. 01:22:37.412 --> 01:22:38.792 Thank you, Hybrid. Merry Christmas. 01:22:39.432 --> 01:22:44.012 Pot Bun comes in with a row of ducks. It'd be interesting if we could somehow 01:22:44.012 --> 01:22:48.292 get a count of how many times you guys have said Graphene OS or Rust. 01:22:48.452 --> 01:22:48.672 Oh. 01:22:48.792 --> 01:22:50.332 I'm sure people would have other ideas. 01:22:51.432 --> 01:22:51.732 Yeah. 01:22:52.472 --> 01:22:53.912 I mean, we have transcripts now. 01:22:54.072 --> 01:22:57.432 That could be something that's done. And I would love if anybody ever wanted 01:22:57.432 --> 01:23:03.332 to cut together like a cut of our Rust coverage or our Graphene OS coverage. 01:23:03.332 --> 01:23:06.032 And we could do a highlight thing. And then one day we just, here you go. 01:23:06.192 --> 01:23:08.352 We're off for this week, Drew. Here's somebody made this for us. 01:23:08.592 --> 01:23:08.812 A supercut. 01:23:09.172 --> 01:23:11.032 Theme supercuts. I like that. 01:23:11.492 --> 01:23:15.512 Yeah, I thought you could write a Python script pretty easily that would go 01:23:15.512 --> 01:23:19.892 and search all the transcripts that we have available and give you a count. 01:23:20.712 --> 01:23:24.492 Drew, I'm going to say every time pod bun boosts in, I think ear buns. 01:23:24.492 --> 01:23:26.912 Not your buns, but your bunnies. 01:23:32.492 --> 01:23:38.832 Well, Odyssey Westra boosted in here at 20,000. Oh, sorry, 2,052 Satoshis. 01:23:40.212 --> 01:23:45.152 Sigh. It's just wet, cold, and windy on the east side of the state. 01:23:45.412 --> 01:23:46.552 That's Washington State. 01:23:47.192 --> 01:23:50.672 Winds didn't cause too much damage, though, on this side. Definitely not what 01:23:50.672 --> 01:23:54.652 you are all experiencing over there on the other side. That stays safe. 01:23:54.832 --> 01:23:59.232 Also, a little birthday boost since you released the episode on that same day. 01:23:59.752 --> 01:24:03.992 Oh. Happy birthday. Happy birthday. Yeah, the studio with the winds lost power 01:24:03.992 --> 01:24:09.292 twice, which really stinks because the UPS is last 15, 20 minutes, 01:24:09.452 --> 01:24:13.332 and the power was out for two hours one time, and then it was out for quite a while the second time. 01:24:14.052 --> 01:24:17.592 And it was one of those things where both times I wasn't here, so I showed up. 01:24:17.892 --> 01:24:21.512 And you start putting it together like, uh-oh, that's not right. 01:24:21.592 --> 01:24:23.372 That's not right. Oh, no. 01:24:23.992 --> 01:24:27.152 So there's always a bit of a job there. I'm glad you're okay over there, Odyssey. 01:24:28.092 --> 01:24:32.692 Mr. Mayhem's here with 2,323 sats. 01:24:34.503 --> 01:24:38.043 A new challenge suggestion. Oh, good. I was hoping we'd get one of these. 01:24:38.623 --> 01:24:43.303 He says, I just found out that damn small Linux has started showing signs of 01:24:43.303 --> 01:24:46.063 little life after 15 years of a hiatus. 01:24:46.443 --> 01:24:50.123 At least they were in 2024. A new challenge that I'd like to see is to find 01:24:50.123 --> 01:24:53.763 out how long the crew could last on damn small Linux while running the kind 01:24:53.763 --> 01:24:55.343 of hardware that DSL is made for. 01:24:55.703 --> 01:24:59.523 Is it the same as 30-bit challenge? Kind of. But it goes farther and embraces 01:24:59.523 --> 01:25:03.723 the ability to use modern software so long as it's small. 01:25:05.563 --> 01:25:09.303 This to me sounds like a vote for like co-host suffering. 01:25:10.003 --> 01:25:15.383 Yeah. I, I do think 2026 is prime for a new challenge. I, that's one of the 01:25:15.383 --> 01:25:16.583 things I enjoyed over 2025. 01:25:17.243 --> 01:25:21.263 I liked the home labs too. That was a lot of fun. We had some great challenges 01:25:21.263 --> 01:25:24.523 that really did push us. So like, how do you do more than that? 01:25:25.123 --> 01:25:28.503 I keep thinking, I just don't know how it comes down. I keep thinking we need 01:25:28.503 --> 01:25:32.183 to go out into the real world and get ourselves into a real situation with real 01:25:32.183 --> 01:25:34.483 time constraints and fix and solve something. 01:25:35.448 --> 01:25:37.148 And I think that would be a great challenge. 01:25:37.348 --> 01:25:38.068 I like this idea. 01:25:38.248 --> 01:25:41.608 Three days to like refurb somebody's home lab or three days to get a business 01:25:41.608 --> 01:25:44.568 network operational and, you know, that kind of thing. 01:25:44.788 --> 01:25:45.848 Can we bring epoxy? 01:25:46.688 --> 01:25:48.608 Yeah. We're going to need a lot of epoxy. 01:25:48.788 --> 01:25:48.908 Buddy. 01:25:49.348 --> 01:25:52.148 We're going to need a lot of epoxy. All right. 01:25:52.288 --> 01:25:55.328 So, like I said, if you did not hear your boost read, don't worry. 01:25:55.328 --> 01:25:58.628 We have it. We're saving it for next week's episode just with the recording schedule. 01:25:58.908 --> 01:26:02.968 We do appreciate you sending that in and we will read them next week. 01:26:02.968 --> 01:26:05.468 So here's what we have for this episode so far. 01:26:05.668 --> 01:26:08.648 And first I want to start by thanking those of you who stream SATs. 01:26:08.908 --> 01:26:14.688 As you listened, we had a really, well, that's pretty good. 27 is pretty good 01:26:14.688 --> 01:26:16.248 for total streamers because I was looking at the total streams. 01:26:16.408 --> 01:26:21.388 It was 2,183 total streams. And the SAT stackers streaming it right in here. 01:26:21.508 --> 01:26:26.868 92,359 stacked by you streamers. Thank you very much. That's a very nice, healthy number. 01:26:27.148 --> 01:26:30.208 But get ready for this. When you combine it with our boosters this week, 01:26:30.268 --> 01:26:32.848 we are rounding 2025 out really strong. 01:26:32.968 --> 01:26:44.028 This episode got tremendous support with a total stats of 1,952,729 Satoshis. 01:26:44.168 --> 01:26:44.508 Whoa. 01:26:45.368 --> 01:26:45.728 Unbelievable. 01:26:46.188 --> 01:26:46.388 Woo. 01:27:04.820 --> 01:27:08.180 Thank you, everyone who supports the show with a membership or with a boost. 01:27:08.280 --> 01:27:11.640 Fountain FM is making that easier and easier, but there's an entire self-hosted 01:27:11.640 --> 01:27:14.180 infrastructure with Albie and lots of great apps. 01:27:14.320 --> 01:27:18.000 You get not just boosts, but new features, transcripts, pod chapters, 01:27:18.220 --> 01:27:21.340 all kinds of stuff like new release announcements, all that right there in the 01:27:21.340 --> 01:27:24.540 app, including live streams. Thank you, everybody who supports the show. 01:27:24.900 --> 01:27:29.320 It really means a lot to us. you know, I, at times, right, as a small business 01:27:29.320 --> 01:27:32.640 owner, the thing that really stresses me out, if you'll allow the cliche, 01:27:32.780 --> 01:27:36.160 the thing that keeps me up at night is often how am I going to fund the next quarter? 01:27:36.900 --> 01:27:40.640 At the end of the year with the holidays, all of it so much is up in the air, 01:27:41.400 --> 01:27:44.780 that if I was prone to, you know, ulcers, I'd probably have a real, 01:27:44.780 --> 01:27:46.740 a real zinger right now. Thankfully I am not. 01:27:47.100 --> 01:27:52.700 But when we get support like that, you know, I know this sounds trite and cliche, but it is true. 01:27:52.780 --> 01:27:56.080 I am going to sleep better at night knowing that we have that now in the bank. 01:27:56.360 --> 01:28:00.180 And even if I don't get contracts signed, you know, we're going to survive for 01:28:00.180 --> 01:28:02.400 a little bit longer with the members and with the boost. 01:28:02.440 --> 01:28:05.000 It truly makes a bigger difference than you can appreciate. 01:28:05.240 --> 01:28:08.320 Thank you everyone for supporting the show. It means a lot. 01:28:09.857 --> 01:28:15.337 And with that, it's time for a few banger picks. We couldn't help ourselves once again. 01:28:15.857 --> 01:28:19.717 And the first one is for those of you that are still living the TUI lifestyle 01:28:19.717 --> 01:28:20.817 after our TUI challenge. 01:28:20.917 --> 01:28:21.617 Which I hope is everyone. 01:28:22.257 --> 01:28:26.977 And it's, I don't know, how would you say this one, Wes? Emildung? 01:28:28.257 --> 01:28:31.557 Actually, that was better than I thought you were going to do. Yeah, I think ship it. 01:28:32.557 --> 01:28:33.877 Emildung is a... 01:28:34.677 --> 01:28:35.537 Elmildung? I don't know. 01:28:35.617 --> 01:28:39.777 Yeah, I'm sure I'm getting that wrong. It's a TUI RSS reader based on the Awesome 01:28:39.777 --> 01:28:42.557 News Flash library, mostly written in Rust. 01:28:43.997 --> 01:28:46.437 And with a flaked Nix in its repo. 01:28:46.637 --> 01:28:52.337 It does indeed. It's also beautiful. It's strange to say about a TUI, 01:28:52.437 --> 01:28:57.477 again, terminal user interface RSS reader, but it is actually very beautiful. 01:28:57.677 --> 01:29:03.617 And I think nicer design than just about every GUI RSS reader app I've ever used. 01:29:04.117 --> 01:29:07.257 And it could be just a really great way to bust through some RSS. 01:29:07.557 --> 01:29:11.557 And also, I'd love to know if there's interest. I have recently set up my own 01:29:11.557 --> 01:29:16.177 fresh RSS instance with a few integrations, summary tools, and different plugins. 01:29:16.397 --> 01:29:20.857 If you're out there and would like me to do a segment on fresh RSS, let me know. 01:29:21.277 --> 01:29:25.557 Send us an email at linuxunplugged.com slash contact, or even better, send us a boost. 01:29:26.357 --> 01:29:31.617 Because I have, I think, been very surprised with my time with fresh RSS. 01:29:31.857 --> 01:29:31.977 Ooh. 01:29:32.777 --> 01:29:37.177 Now, this next pick I put in here because I really wanted to get your take. 01:29:37.457 --> 01:29:40.117 You could educate me on this because there's a few things I don't know about. 01:29:40.417 --> 01:29:43.437 And the pick is, it's an app. It's called ZeeBridge. 01:29:43.937 --> 01:29:48.757 And it's a contract bridge game, which I guess is a... 01:29:50.400 --> 01:29:53.880 taking card game for four players i don't really understand but it's the. 01:29:53.880 --> 01:29:54.740 Game of bridge. 01:29:54.740 --> 01:29:57.860 Contract bridge yeah based okay based on bridge and z 01:29:57.860 --> 01:30:00.600 bridge is an online bridge club where you 01:30:00.600 --> 01:30:03.320 can play in learning mode you can play with other 01:30:03.320 --> 01:30:06.300 people in multiplayer you can play against a quote-unquote game 01:30:06.300 --> 01:30:12.100 ai you're jethro is that what it's called play with jethro that's a competitive 01:30:12.100 --> 01:30:19.460 bridge bot so jethro is available but uh i know nothing about bridge and uh 01:30:19.460 --> 01:30:22.800 you on the other hand know quite a bit about bridge so i'm wondering if this 01:30:22.800 --> 01:30:25.420 passes the westpain sniff test the z bridge app. 01:30:25.420 --> 01:30:31.300 Yeah it does look like it is a flat pack of an electron packaging for the service. 01:30:31.300 --> 01:30:33.960 Yes it's it is there's they have a website but that makes. 01:30:33.960 --> 01:30:35.080 It pretty easy to get going. 01:30:35.080 --> 01:30:35.820 Yeah and. 01:30:35.820 --> 01:30:41.380 Uh i like the idea that you are learning bridge so i'm gonna say a thumbs up. 01:30:41.380 --> 01:30:44.300 All right i got the thumbs up all right i like that. 01:30:44.300 --> 01:30:49.380 When i read the title z bridge i thought it was like a zigbee bridge for home 01:30:49.380 --> 01:30:54.260 assistant or something and then the description much better threw me right off did not expect that. 01:30:54.260 --> 01:30:57.560 Also no license was found for that one. 01:30:58.639 --> 01:31:01.939 I've got a quick pick for you guys if you want a third one. 01:31:02.399 --> 01:31:03.359 Yes, we do. 01:31:03.699 --> 01:31:07.419 All right. Yeah, I always like bringing you guys some audio visualization fun. 01:31:07.999 --> 01:31:08.479 Yes. 01:31:08.639 --> 01:31:14.119 This one's called Cavalier. It is based on the Cava graphics engine. 01:31:14.279 --> 01:31:14.499 Sure. 01:31:14.759 --> 01:31:17.499 And it's also written in .NET 8. 01:31:17.719 --> 01:31:18.939 Oh, this looks really nice. 01:31:19.019 --> 01:31:23.919 And it's MIT licensed. But, yeah, it's just a little visualizer. 01:31:24.139 --> 01:31:27.819 You just connect it and Pipewire does the rest. 01:31:27.819 --> 01:31:34.799 It will automatically connect to your main out monitors, or you can manually 01:31:34.799 --> 01:31:41.159 connect it to something else through Helvum or QPW Graph, whatever your choice is. 01:31:41.299 --> 01:31:44.999 And it has a lot of little options that you can make it your own. 01:31:45.099 --> 01:31:48.659 It's really cool, small, fancy, and fun. 01:31:48.939 --> 01:31:53.319 Take the best part of Winamp and make it into this app is what they've done. 01:31:53.319 --> 01:31:56.939 The visualizer with customization options where you can have in a window. 01:31:57.579 --> 01:32:01.739 It's really cool looking, too. It's a nice, modern Linux desktop app. 01:32:02.219 --> 01:32:02.439 Rad. 01:32:02.999 --> 01:32:07.859 Yeah. All right. That's a good pick. And so it's Cavalier, and we'll put a link to that. 01:32:08.059 --> 01:32:08.779 MIT license? 01:32:08.879 --> 01:32:14.079 Yep. Available as a Flatpak or Snap. Looks like they have it in Arch as well. 01:32:14.859 --> 01:32:18.119 Very nice. Drew, thank you for joining us and playing referee. 01:32:18.119 --> 01:32:20.159 It's always good to see you and catch up. 01:32:20.419 --> 01:32:22.919 You're very welcome. It was my pleasure and my honor. 01:32:24.019 --> 01:32:27.659 And I think we got some good results. I think you got good results out of us. 01:32:27.759 --> 01:32:28.919 So that's always appreciated. 01:32:29.179 --> 01:32:30.699 So we have someone to blame for next year. 01:32:30.999 --> 01:32:35.839 Yeah, right? Yeah. Even when Drew is not here, of course, the friendly hand 01:32:35.839 --> 01:32:37.499 of editor Drew touches every episode. 01:32:37.799 --> 01:32:40.559 So thank you, Drew. Round of applause for all your hard work there. 01:32:40.899 --> 01:32:41.599 Thank you. Thank you. 01:32:42.939 --> 01:32:49.699 Now, we encourage you to make it a Tuesday on a Sunday and join us live Sunday, 10 a.m. Pacific, 1 p.m. 01:32:49.979 --> 01:32:52.559 Eastern over at jblive.tv. 01:32:56.069 --> 01:32:59.689 And if they're getting us on the download, depending on their podcast client, 01:32:59.909 --> 01:33:02.749 Wes, there's some fancy features they can take advantage of. 01:33:02.869 --> 01:33:06.869 Yeah, how do you feel about a magical cloud-based JSON that comes right to you 01:33:06.869 --> 01:33:09.309 and tells you where we talk about what? 01:33:09.449 --> 01:33:12.809 And you know what I like about that? We can update it dynamically when we make a mistake. 01:33:12.949 --> 01:33:15.909 Yeah, it's got like you can put in images and all kinds of fancy features, 01:33:16.009 --> 01:33:18.369 which we don't even fully take advantage of yet, but we will. 01:33:18.529 --> 01:33:19.969 One day, the more people use it. 01:33:20.389 --> 01:33:24.469 And you can also just get a whole transcript. Maybe you want to count words 01:33:24.469 --> 01:33:25.709 that we say way too often? 01:33:25.709 --> 01:33:26.309 Maybe you do. 01:33:26.569 --> 01:33:29.469 Yeah. Well, that could be one way to look at it. Or if you just want to be able 01:33:29.469 --> 01:33:32.769 to follow along or double check something we said, or I mean, 01:33:32.829 --> 01:33:33.569 it's just nice to be able to read. 01:33:33.709 --> 01:33:35.589 It's all right there if you just need to double check something or whatever 01:33:35.589 --> 01:33:39.489 it is. And also makes it more accessible as well, which is a big thing. 01:33:39.889 --> 01:33:43.369 And links to what we talked about today. Those, my friends, are linked over 01:33:43.369 --> 01:33:46.909 at linuxunplugged.com slash 647. 01:33:47.949 --> 01:33:49.949 Sometimes these holiday episodes a little lighter on the links, 01:33:50.029 --> 01:33:51.749 but we tend to have pretty copious show notes. 01:33:51.889 --> 01:33:54.949 So it's always worth checking out. There's usually more in there. but links 01:33:54.949 --> 01:33:58.249 to like the apps we talked about and whatnot some of the news that i'll 01:33:58.249 --> 01:34:01.369 be in the show notes at linuxunplugged.com slash 647 01:34:01.369 --> 01:34:04.129 you'll also find our rss feed our mumble room info 01:34:04.129 --> 01:34:09.049 our matrix info membership info boost info all of it it's a website with links 01:34:09.049 --> 01:34:13.029 at linuxunplugged.com and then you can go check out the launch recent episode 01:34:13.029 --> 01:34:17.769 had brent in it or this week in bitcoin all of that and more over at jupiterbroadcasting.com 01:34:17.769 --> 01:34:21.629 thanks so much for joining us on this week's episode of Your Unplugged Program, 01:34:21.749 --> 01:34:26.269 and we'll see you right back here next Tuesday, as in Sunday!
Previous episode Next episode

Search

Search

Listen on

Apple Podcasts Spotify RSS feed