Untitled Linux Show 191 Transcript
Please be advised this transcript is AI-generated and may not be word for word. Time codes refer to the approximate times in the ad-supported version of the show.
00:00 - Jonathan Bennett (Host)
Hey folks, this week we're talking again about Rust in the kernel, but this time Linus has put his foot down. Then we've got news about Asahi, news about one of those other OS manufacturers wrestling with an encryption law, gen 2 meta, taken to court for torrenting All kinds of crazy stuff. You don't want to miss it, so stay tuned.
00:21 - Leo Laporte (Announcement)
Podcasts you love From people you trust. This is Twit.
00:30 - Jonathan Bennett (Host)
This is the Untitled Linux Show, episode 191, recorded Saturday, february the 22nd. Linux like sausage. Hey folks, it is Saturday and you know what that means. It's time for Linux Geeking out about open source, free software, linux, desktop, some other things. We're going to talk about some of those other OSs today and some other things going on sort of around the world. We're going to branch out just a little bit beyond Linux, but some important stuff and some fascinating stuff. It is not just me, of course. We've got Mr Rob Campbell and Mr Jeff Massey. Welcome to both of you, yo yo, and we're going to let Rob go first. He's got a story about something we've been talking about for a long time. There's more drama. What's the latest on the kernel trying to get rusty.
01:18 - Rob Campbell (Co-host)
So the saga continues with more news about Rust in the Linux kernel and I think this is going to be the last week I do it, unless there's something just huge. I'm getting tired of it. But, as I said last week, I would feel better about Rust in Linux policy that we discussed if it came from the top. You know from the Linux guys themselves and you know they must be listening. Maybe they're listeners of the show hey Linus and Greg, but you know from the Linux guys themselves and you know they must be listening. Maybe they're listeners of the show hey Linus and Greg um, but you know they must be listening because this week it comes from the top, as both Linus Torvald and Greg Cage uh, greg Cora Hartman both had things to say.
01:59
So I'm going to start back it up with a little bit with, uh, christopher Hellway. So he's he was, he's a kernel maintainer involved with the DMA layer in the kernel and he's been one of the people who's been critical of Rust in the Linux kernel. You know he's worried about the kernel becoming unmaintainable due to Rust bindings just creeping up all over the place and then having to be continually updating to keep up with this rust change and that to be changed and just endless keeping up with us. So that's as is concerned, and you know we've we've discussed our thoughts on the validity of that. But regardless of his objections, hellwig says that Linus told him privately that he would override maintainers' vetoes on rust code within the kernel. So a couple days later Linus made his views public, hands-off approach where it's more complementary to their code. But kernel maintainers can't object to new Rust code. As you know. Effectively, as a user of their C code you know meaning. If it's not something they're actually maintaining and involved in, they can't object to Rust code going into some other part of the kernel. So before this point Linus was quiet on the matter, hoping to see, you know, hoping he'd see something constructive come out of the discussions that were going on. But he got involved. When he says, things appeared to be moving backwards. So Linus's main objection to a recent veto Helwig attempted was the fact that the pull request that Helwig objected to did not touch any part of his DMA code. So in effect, here Hellwig was merely objecting as a user of that code rather than a maintainer of the that actual part of the code, and that's that seems to be what he really had a problem with. You know you got nothing to do with it, just keep out. Essentially, so let it, you know, and that's that's what I'm going to say about that piece of it.
04:29
But uh, linus's number two in charge, greg cage, also had something to say about the whole rust in the kernel debate. So in general, greg shares his reasoning. Uh, he believes gradually moving to the linux kernel, to Rust is a good thing. Greg says quote the majority of bugs quantity, not quality or severity we have are due to the stupid little corner cases in C that are totally gone in Rust. Things like simple overwrites of memory not that Rust can catch all of these by far error paths, cleanups, forgetting to check error values and use after free mistakes. End of quote. But he points out that there are more than 30 million lines of C code in the Linux kernel that aren't going anywhere any year soon. But that isn't a reason to stop new code and new drivers from being written in Rust. He talks about other benefits, you know, to the API that'll improve that and providing more time to work on real bugs while you're not trying to find and fix these edge cases, these little C bugs. But he also admits Rust isn't a silver bullet to solve all of their problems. But, to be clear, greg isn't a Rust developer and he had this to say about that Quote yes, the Rust bindings look like magic to me in places Someone with very little Rust experience and he has very little Rust experience. But I'm willing to learn and work with the developers who have stepped up to help out here, to not want to learn and change based on new evidence parentheses see my point about reading kernel bugs. We have so into that quote there, you know. So, with this new update here, you know the leaders on Linux kernel have spoken and they're in favor of Rust, and you know I really only had time to touch on the key highlights of what these two wrote this week, but if you check out the show notes, you can find links to these, which you'll find links to the full Linux kernel mailing list Letters, emails.
06:59
I guess that they wrote, or how we phrase that, what they wrote on it, how we phrase that, what they wrote on it, it's a good, it's. It's a good page or so letter. That you know. I don't have time to break down every detail. I got the highlights for you, um, but they're. They're interesting letters to read and to hear what their their take is on it, and it's good to see that, um, they have a view on it. You, you know personally. I guess I was almost kind of leaning to. Yeah, it seems like a pain to maintain and I'm maybe concerned that it will cause problems in the future. But then again, I'm not a Rust developer. I barely know much C. I've done some C, so maybe I'm not the one to ask, ask. I don't know what it really takes to put those two together like this. But uh, the, the, the linux gods have spoken yes, yes, they have.
07:59 - Jonathan Bennett (Host)
um, and honestly, I understand right why maintainers are so concerned about Rust in the kernel, particularly when they don't speak Rust and when there's sometimes a pain. But I think Torvalds has hit the nail on the head here. This is sort of a bigger open source and free software argument to make that you don't get to control what people do with your code and the people that don't like Rust don't get to keep users of their APIs out of other directories in the kernel, and that just seems pretty straightforward. So I'm not sure why we needed Torvalds to come in and say this. But well, no, I know. But, like, from a certain point of view, we should not have needed him to come in and make this statement. It should have been self-evident.
08:47 - Jeff Massie (Co-host)
The big thing for me was that I didn't realize that it didn't touch any of the C code. I thought that it was kind of intermingled a lot more and that they would have to maintain it. You know there was a lot more intermixing versus okay, I have this section of code I don't want. I'm complaining about your pull, but it doesn't affect me, I'm not, you know.
09:09 - Rob Campbell (Co-host)
So you're thinking like a single file of C programming, with some C here and some Rust here and some C here again.
09:17 - Jeff Massie (Co-host)
Well, or maybe you know different object files and it would have to get knitted together, or you know the maintainer was going to have to know Rust to be able to do it and it's like no, here's the section I maintain.
09:29 - Jonathan Bennett (Host)
So here's part of it. Here's part of what's going on. The kernel has internal APIs, and so those are the way that the different parts of the kernel talk to each other and with someone that is in charge of one of those APIs, they work together. They will make a change to it, and so let's just say that they make a change to the DMA side of it. Um, that will break other code, and so the way the kernel has historically worked is, when you send one of these patches in that's going to change API, you also include in there the fixes to all of the places that that use that API, or you at least work with the people that do it. And so one of the things that really was bothering these maintainers, particularly in the internal kernel APIs, is, if the Rust code is going to use their API, what do they do when they need to make a change to the API? What do they do when they need to change the way something works in the kernel and they've got this code that's written in Rust that depends upon their stuff?
10:32
How do these C developers that are the maintainers then go out and fix this when they don't know Rust, when Rust is not their preferred language. It's not the language they speak at all. Perhaps preferred language it's not the language they speak at all. Perhaps, um, and so they're like, there's this legitimate question of in having rust bindings for my code. Is that going to tie my hands to not be able to make changes, and like that's a pretty legitimate concern to have.
10:58
Um, that has been answered and the answer is no, that will not tie your hands. It's going to be on. The burden is going to be on whoever is maintaining the rust binding. And hope, you know that's like hopefully that's you that's helping with that, but even if it's not, that's okay, and so that's sort of the the answer that they've come to. Um, yeah, it's, it's. We're kind of watching the sausage get made. It's not surprising that there is disagreement and contention in exactly how all of this is going to get worked out. Hopefully we don't have anybody else throwing their hands up and leaving the kernel in disgust. That would be ideal, but you know, it might happen.
11:36 - Jeff Massie (Co-host)
Well, I mean, like you said, we're seeing how the sausage is made. It's a little messy, but Linux-like sausage is pretty darn good, yes.
11:44 - Jonathan Bennett (Host)
Yes, and it's always been messy inside the Linux kernel mailing list. Let's be real, let's be honest. It's a lot calmer than it used to be. Yes, I would say that every large software project mailing list is going to have moments of messy sausage making. We'll say this is pretty typical. When you have a big decision to make, you're trying to change something. This is pretty typical.
12:14 - Jeff Massie (Co-host)
Well, and when you're dealing with people putting a lot of code into the kernel, you're dealing with a pretty high level programmer. So I mean, this is not just a script kitty or something. You're and you're going to have egos. You're going to have people that are maybe not as socially adept as others. You know it sometimes comes with the territory and you know there's there's a little grinding of gear sometimes.
12:41 - Jonathan Bennett (Host)
Yep, and it's like any other communication over text is hard right, so like email, email just has sort of this built into it. Problem you don't get, you don't have face-to-face conversation with email. You don't get um the body cues, you don't get even the tone of the way someone is saying something.
13:01
So like emojis, emojis are important in some cases they literally can be yes, and and I don't think they use much emoji in the linux kernel mailing list. Um, maybe maybe that's what they need to do, maybe that's the solution to all of this problem. So you use more emojis, um, but anyway. So I'm just saying like, and these guys know that, like all the people that work in the linux kernel, they realize that, and so they. It's kind of like they've adapted to the point to where, yeah, they may get fired up over something, but generally, if they're going to last in the kernel for very long, they'll calm down and they'll can explain themselves over text and they'll figure out a way to move forwards. Right, like it again.
13:37
It's as normal, all right yes, no, I was just saying definitely, I was just agreeing with you okay so let's move on to something else that's actually rather related and that is asahi, which is one of these rust projects that has been trying to push code up into the rust kernel, and we talked last week about um, uh, about the week, about the leader. I always think of Martin as his name. I always think of Markan because that's like his screen name, it's his handle. But Martin is moving on. He's left both the Linux kernel and the Asahi project and there is a new blog post from Asahi that is laying forward what they are going to do next and it sort of involves a change in governance in a way. So Asahi previously had a single sort of benevolent dictator, we could say, and they are moving it to more of a panel of experts, kind of a model Ben Grunow and Sven Peter, which you've got three kernel devs, a graphics dev, two Fedora devs and an audio dev in that list, and you may think that's weird to see Fedora devs, but remember that Asahi is now based on Fedora. Fedora is their sort of flagship, so it's not all that unexpected to see it get a little bit closer to Fedora with this. But anyway, I just I found it very interesting to see that they are.
15:31
The people that are still in the project want to continue on. They're pushing forwards. Even in this blog post they've got a list of things that they're still working on and should have working in the in the next release. In the next release, the DisplayPort Alt modes that you can run a monitor just over USB-C. They are working on the internal microphone support and some other things like that. Working on the Vulkan driver still. So you know some good things from Asahi. They're having to obviously make modifications to the way the project works, but it appears as though there are enough people still involved in it that still care about it that it's going to continue on, and so those of you out there with Mac machines based on the M processor take heart. Things will continue to happen, and it looks like code will continue to go upstream into the kernel as well. So that is that Neither of you guys have Mac machines, so you don't care.
16:33 - Jeff Massie (Co-host)
No experience.
16:36 - Jonathan Bennett (Host)
I really wish that there were a way, and obviously there's not, because the iPad and the iPhone are so locked down with their bootloader. I would love to be able to run a sahi on something like an iPad, because their new iPads are based on the M processors. But I've asked a couple of actually I've asked a couple of people involved in the Asahi project about that, and they've each told me that the bootloaders are locked down. It's just not possible.
16:59 - Rob Campbell (Co-host)
Yeah, you know, I didn't realize that the Asahi was now based on Fedora. I thought they still had their arch, and then the Fedora. There was now a Fedora spin.
17:11 - Jonathan Bennett (Host)
I think I'm pretty sure Fedora is the flagship now.
17:14 - Rob Campbell (Co-host)
Yeah, I'm trying to find that and that's what I believe I am seeing on their bonus page in the faq section. So, uh, I learned that new today. That is something new I learned about uh, you relearned it.
17:31 - Jonathan Bennett (Host)
I know we covered it back in the day.
17:33 - Rob Campbell (Co-host)
No, no, I we covered we covered that fedora asahi was going to be a flagship. Um, I just didn't know it was going to replace. I don't think we ever clearly said that it was actually replacing theirs.
17:48 - Jonathan Bennett (Host)
Yeah, yeah. And I mean, let's be honest, the door is a better choice than arch. For for people coming from the Mac OS side particularly, the door is a better choice than arch.
17:58 - Rob Campbell (Co-host)
You know, void Linux also has an Asahi mix, or whatever they call theirs, whatever they call theirs.
18:04 - Jonathan Bennett (Host)
Yes, I guess, if you really want to go, use void and, and so that's the other thing. Right, like there's nothing stopping, uh, ubuntu and um, you know, leap and tumbleweed and all these guys from having an asahi spin right, especially now that things are landing upstream in the kernel. In some cases it's just going to work and it's going to be pretty easy to get it going, and some of those have images and there are ways to get it running. We're just talking about the sort of flagship, the preferred Asahi experience, and that happens to be on Fedora right now. It may change to something else in the future, who knows? All right, jeff. What's up with KDE?
18:49 - Jeff Massie (Co-host)
Well, nate Graham and his weekly blog provides numerous updates on what's happening with the Plasma desktop and we know that version 6.3 is out and, depending on your distribution, version 6.3.1 is also available. Both versions are receiving a lot of attention and fixes and the team is currently working on version 6.3.2, and fixes are already underway regarding what will be included in Plasma 6.4. That was resolved. Involved KWIN built with LTO on GCC 15, which could result in a black screen on login when using an ICC profile. The code was restructured to avoid this issue. Now I should say ICC stands for International Color Consortium, which is a profile that allows users to define their colors, adjusting them if necessary for their display device, thus enabling color accuracy tuning.
19:52
Another fix addressed is a plasma crash that occurred when attempting to access the properties dialog for a file in the recently or frequently used file list in the kickoff application launcher. Additionally, a regression that caused the volume change on screen display to fail when adjusting the volume with the integrated volume buttons of a Bluetooth headset was resolved. There's other fixes as well, but in the interest of time let's move to version 6.3.2. So in version 6.3.2, a regression that caused desktop icons to become inappropriately deselected if you dragged a selection box around several icons and released the mouse button over one of them was then fixed In a two-for-one fix. They addressed a bug where the desktop and panels would go missing when applying new global theme and using the option to replace the existing layout. This also fixed an issue that caused deleted widgets to not be removed from the desktop-applet-sourceconfig file. So always love those two-for-one fixes. Moving on to Plasma 6.4.0, an issue was fixed when switching users using KRunner would cause the desktop to start working erratically and eventually crash. Additionally, there was a change to KWin's render loop initialization code, which now uses a more precise timer to reduce frame drops.
21:18
Now, overall, when reviewing the list of bugs, there's one very high priority plasma bug that remains the same as last week, and it is worth noting that this is actually an X11 bug, not a Wayland bug. There are currently 30 15-minute plasma bugs, up from 27 last week, but overall 129 bugs were fixed over the last week, over the last week. So overall, although the overall bug tracker might not show significant change, nearly 130 bugs being fixed demonstrates the substantial work being done to fine-tune the plasma code. For full details and a comprehensive list of all the bugs that were fixed. Please refer to the link in the show notes. And there was a lot I skipped over. I kind of just picked some, cherry-picked some highlights. You know I must say I'm genuinely excited for the future of kde and you know, even bigger with the cosmic desktop. You know, on the horizon, you know, stable release. I mean, I know there's some alphas out but you know it's coming on. I believe the interface for lin. Linux is set up to be a fantastic future, you know happy times ahead We've had.
22:28 - Jonathan Bennett (Host)
We've had some neat stuff honestly on the Linux desktop for a long time now with the, with the advances in eye candy and and it's just some things that you've been able to do on Linux for forever with like multiple workspaces, the. There have been things. There have been neat things that have landed on linux that have not come to other desktops, either have not at all come to other desktops or very slowly. You know the, the other big two have kind of stolen our ideas and rolled them out yeah, a lot of the big things come to the other desktops one way or another.
23:02 - Rob Campbell (Co-host)
either they opt them 10 years later or some third party makes something that kind of replicates it, Because analytics comes up with a lot of great things on the well in general.
23:17 - Jonathan Bennett (Host)
Well, I mean, it's because the code's open source, right, it's so easy. Or if somebody can just go, hey, wouldn't it be cool. And the next thing you know they're hands deep into the code working on it. Make it work, make it happen, hey, it was cool, send a patch in and then everybody can enjoy it. I mean, you have an idea, you know, you have your Windows machine. You go, hey, wouldn't it be cool if it did this? How are you going to make it do that? I don't know, I can't get to the source to do anything with it.
23:43 - Jeff Massie (Co-host)
Well, if you're one of those people go ahead, and even if you're a developer for, say, windows I think this would be cool to do you now have 20 levels of management to put it through and project design reviews and then probably case studies, and how is this going to affect everything? It's a glacial movement because you know this might break something too, and yep yeah, so linux is more experimental linux desktop.
24:13 - Jonathan Bennett (Host)
But some desktops in particular are more experimental.
24:16 - Rob Campbell (Co-host)
They're more open to experimentation and so they get to move faster and do cool things if you are one of those people who likes to dig into the code, as jonathan said it, um, there is a company we're going to talk about soon that may have a job for you why don't you go ahead?
24:31 - Jonathan Bennett (Host)
why don't you take it and tell us about it?
24:34 - Rob Campbell (Co-host)
I will. I just did the uh. Since ken's not here, I had to do the segue for him. So gaming on linux has gotten quite good in the past few years. This week I've even seen a few posts. They were on reddit, people talking about how the infamous youtuber pewdiepie is now using linux and and apparently he's rather impressed with its gaming capabilities.
25:01
So are you one of those developers who likes to dig into the code? Are you looking to make gaming on linux even better for pewdiepie and the rest of it? Well, code weavers is looking to hire multiple wine developers, uh, as well as their crossover products. Uh, being val's proton downstream for for steam play and related wine-based tech. And oh yeah, someone who really needs to be better is Linus from Linus Tech Tips, because we saw that one in the past. But anyway, back to the story. So who is CodeWeavers? We've mentioned them, but I'm sure a lot of people forget who they are, or maybe just saying the name brought it up.
25:50
But for users of the Valve Steam Deck or desktop Steam gaming on Linux, you're likely familiar with their work, as they are contracted by Valve for helping with Proton to power Steam Play for running Windows games on Linux, and that's a huge part of what's made gaming so accessible on Linux these days, and then along with other commercial agreements that they have with organizations for running Windows, software analytics and Mac OS too I guess who cares? So if you're experienced with working on open source projects and plus you have a strong C language skill, maybe you're one of those kernel developers who doesn't want Rust. But you're a C developer, you can come over here. Excellent debugging abilities and a desire and desired Windows. Well, they desire Windows 32 programming experience. So I guess a little bit of Windows is going to help you there too for Linux. But this might be a job for you. The job posting is up on their site Go apply.
27:11
But for the rest of us not looking for a job or we're not C developers, this is still good news, especially for gamers. This is a sign that CodeWeavers and probably Valve, they probably have some role in this. Maybe they're contracting more, maybe they're asking for more, but either way they are. Code weavers specifically at least, is investing and putting more into this, even more work into their code, and we're likely to see the results in the future with games, way more games working other applications. One complaint I hear is Office doesn't work on Windows or Adobe, who knows? I'm just throwing things out there. Maybe they'll get those things working in the future. I don't know, maybe everything will work in the future with with your help there you go.
28:09 - Jeff Massie (Co-host)
I should say code weavers is one of the companies I actually spend money with and because it's basically supporting wine development, which supports proton and all that, I don't really have a huge use for it, but I'm just kind of supporting them through having a license and they do package things so they have automatic installers and whatnot. So if you say I want to run this specific program, a lot of times they will have kind of predefined scripts that will kind of automatically load things and set up some of the wine tricks that you need and things like that to make it easier to to run some of that software yeah, they have the crossover uh version of wine, right, yeah, yeah, so when?
28:56 - Rob Campbell (Co-host)
and crossover is basically it's a paid version of wine and my I haven't used it in years. I maybe I should, maybe maybe not, but, um, my understanding is it it will. You know, like regular wine, you can maybe run some really old versions of office.
29:14 - Jonathan Bennett (Host)
From what I've read, you can run some pretty new versions of office with the the crossover plugin and I think you know part of the part of the package there is being able to have somebody to call to get support right. That's, that's going to be part of what they offer and so for somebody like a business, that probably makes a whole lot of sense. For individual tinkerers like us maybe less so.
29:35 - Rob Campbell (Co-host)
We're sort of allergic to calling for help, uh, but you know, last I looked that crossover uh plugin wasn't too expensive but honestly it it's been a while.
29:44 - Jeff Massie (Co-host)
Yeah, yeah it was. I want to say it was like 30 something, 35 a year or something like that, because it was it was a little more. But then if you keep renewing then it's it's cheaper. And I just had the lowest level of license and then I just thought, well, I'm just support a company that's supporting Linux. Yeah.
30:04 - Jonathan Bennett (Host)
Yeah, and Valve now is supporting them, and so you know you can. You can support crossover by, I'm sure, buying games for valve and playing them on linux, right?
30:13 - Rob Campbell (Co-host)
so if you want to work for a company that's supported by valve and jeff crossover indeed.
30:21 - Jonathan Bennett (Host)
Oh, that'd be fun. It would be fun if one of our listeners got, got in there and was able to tell us about it. You get a job there, let us know, let us know. Even even if it's privately, we would like to hear about it. Uh, all right, let's see up next. Oh yeah, that other os. I warned everybody we were going to talk about this, the other os, so I got it. I got a couple of interesting, fun stories that we're going to talk about, and when I say I mean that sarcastically in this case.
30:47
So the United Kingdom, uk, has passed a law In fact it was an order, not a law telling Apple that the UK government wanted access to the end-to-end encrypted iCloud backups. So we talk about getting access to a device your cell phone. Most cell phones these days are quite well encrypted and the various manufacturers have been very resistant to putting any backdoors in that encryption for obvious reasons. Right, as soon as you try to put a backdoor in encryption, well it will be abused either by governments or by criminals who figure out a way to abuse it Like there is no way to actually do backdoor encryption without completely breaking the encryption. That's just the reality of the situation. That's like the reality of the math, it's kind of like physics. There's no arguing with it. So the UK has come out privately about a month ago and said we want to be able to get into iPhones. Well, you can't get into iPhones directly. There's this kind of workaround, this sort of loophole that's been around for a long time. That is, you can't get into the iPhone itself, but the iPhone will automatically back up all of its data to iCloud, and historically that has not been end-to-end encrypted inside of iCloud. It's been encrypted, but Apple has the encryption key.
32:15
And so there was always sort of this backdoor where they could say we can't get access to this person's telephone, but we want access to this person's iCloud backup. And it was because Apple had the ability to do that. They were required by law to do so. So Apple rolled out a solution for that and they called it the Advanced Data Protection ADP, and that is end-to-end encryption for iCloud backups. It uses the same password that your phone uses and then when it uploads it, it encrypts it with that first. And so then when a government would come to Apple and say, hey, give us this person's iCloud backup, they could either say you know, either say we don't have it at all or fine, here are the encrypted bits. This is probably what actually happens. Here are the encrypted bits and everything we know about it. Good luck figuring out their password right. That's likely what actually happens.
33:16
The UK has passed this order that says that is no longer acceptable. Apple, you are now required to put a backdoor of some sort into ADP, the Advanced Data Protection feature of iCloud, and this has been sort of in the news. If you pay attention to the privacy security. It's been in the news for about a week now and various people had various ideas about what should happen. Some said that Apple will just do what they're told to do.
33:50
Um, apple has actually been reasonably good at trying to protect protect their, their, their consumers privacy. Like there are things that I do not like about Apple, but they've actually been really good about this. Uh, they, they have consistently refused to put any back doors in doors in their products and they let people know about the things that happen, and so they were kind of at an impasse here, and at least one cryptographer that I've read I forget his name now he suggested that what really should happen is the United States should pass a law and says basically pass a law that says it is illegal for US companies to add encryption backdoors, or at least add encryption backdoors at the behest of foreign companies. I don't think that's an interesting idea. I don't know that it exactly gets them out of the jam, but it does give them some backstopping to refuse to do it, regardless that law has not happened. Them some backstopping to refuse to do it, regardless that law has not happened. And so Apple has made the choice to just not provide ADP, this advanced privacy end-to-end encryption, in the UK, and so, rather than add a backdoor in a way that could expose everyone, they've just made the decision that, okay, fine, we're not going to do the end-to-end encryption, we're not going to offer that to our customers in the UK, which is really unfortunate that they can't do that.
35:18
I like encryption. I think it is a thing that we should all be doing if we can, for various reasons. But being put between a rock and a hard place here, I think apple probably did the right thing about. The only other option that they would have had would be to pull out of the uk entirely, which would then have essentially the same effect. Um, so it's. It's a difficult. It's a difficult topic for them. It's a difficult topic to try to figure out exactly what the right answer is politically and across the world. But I wanted to let everybody know that this is what's going on. I'm going to link off to the Ars Technica article, which is pretty good. I will try to find a link to the other coverage that I came across and read as well. That I came across and read as well. But yeah, if you're in the UK and you have an Apple phone, you just lost the ability to have end-to-end encrypted iCloud backups, and for that I'm sorry. It wasn't our fault this time.
36:19 - Rob Campbell (Co-host)
Yeah, you know, Write your Marlin people.
36:23 - Jonathan Bennett (Host)
I guess, does that even work in the uk? We usually we usually don't stick our noses into other countries politics, but does that even work here unless? You have enough money anyway. Apparently, if enough people do it all at the same time, you can get your congress critters. But having lots of money seems to help Anyway.
36:50 - Rob Campbell (Co-host)
Sorry, Congress listeners.
36:53 - Jeff Massie (Co-host)
I think a lot of bad things happen under the premise of good intentions.
36:59 - Rob Campbell (Co-host)
Yep, yep, oh, and Kira says that it was an order based on a law that was passed a few years ago. There you go.
37:07 - Jonathan Bennett (Host)
Yeah, I knew there was a law in there, but it wasn't a new law that was passed, and I think it was a secret order for the first month or two. And then somebody's like we've got to let the world know about this. Then it got confirmed.
37:20 - Rob Campbell (Co-host)
Yeah, yeah, I don't know. I think they probably did about the best thing I could think of other than just pulling out altogether. I mean, that might be a wake-up call too.
37:33 - Jonathan Bennett (Host)
But that wouldn't help consumers anymore. You still wouldn't have access to it, right?
37:39 - Rob Campbell (Co-host)
Right, but I mean, maybe they'd back down, maybe they wouldn't, I don't know.
37:44 - Jonathan Bennett (Host)
Yeah, we'll see.
37:47 - Rob Campbell (Co-host)
You know if all they could get is, you know, cheap little knockoffs. You know if Google and Apple both said, okay, we'll back out, all you get is well, I'm not going to name any names, because I'm talking about cheap knockoffs. We don't know their names.
38:03 - Jonathan Bennett (Host)
Apple phones. Apple phones, yeah, yeah, that's the sort of thing you get. Uh, it's unfortunate. Um, yeah, I don't want to get any more into the politics. Um, I would. I would like to see, I would like to see the United States look at this and see about trying to make it harder for other countries. Right, so, like, this is the sort of thing that everybody should be able to look at and agree on. We do not want other countries to dictate to US companies that they are required to backdoor the encryption of US-made products, required to backdoor the encryption of us-made products. Like. You know how.
38:48
How is it that not everyone that that looks at this immediately comes to that conclusion? I don't understand. Like left, right, this is. This seems to be an issue that, if you understand what's going on, regardless of which side of the aisle you're on I, I, it's. It really seems to me that there should be a big crossover between. The left side is very much privacy and independence for individuals you have your data privacy online and the right has kind of this US nationalism and let's protect our companies in the United States. This seems like it's a win for both of those mindsets.
39:25 - Rob Campbell (Co-host)
And I agree. But also, even if the US made a law, I don't think Apple doing business in the UK, I don't think it would Only thing it would do. I think is would mean that Apple can't open the back door, which would mean that they either have to pull out they have to do what they did already or the UK has to back down.
39:53 - Jonathan Bennett (Host)
And those are pretty much kind of the three options anyway. Can you just imagine, though, tariffs, tariffs for everything from the UK?
39:59 - Rob Campbell (Co-host)
Okay there's that.
40:01 - Jeff Massie (Co-host)
I think you said. The first thing, though, is if they understood. The problem is so many people doing this kind of stuff. They have no clue how this even works and have no idea of what the unintended consequences are going to be.
40:14 - Jonathan Bennett (Host)
That's absolutely the thing. You have people that are writing these laws and in a lot of cases, they honestly just want to be able to catch criminals. I fully believe that there is some good intentions behind stuff like this, but you just don't understand that this is not like a safe. You can't just say that you have to make two keyholes in the safe. Like encryption doesn't really work that way.
40:40 - Rob Campbell (Co-host)
I got a few knockoff phones for you the EYE phone, the Samsung or the new Kia.
40:49 - Jonathan Bennett (Host)
The new Kia. That sounds like something you'd find in Fallout.
40:56 - Jeff Massie (Co-host)
Thanks, Harold Nice, those are good. It comes on your wrist and it's kind of got that amber color to it with the black background. You know, hip boy.
41:08 - Jonathan Bennett (Host)
All right, let's move on and not get ourselves into any more political deep waters. And let's talk about hung GPUs. Jeff, I saw this, I didn't dive deep into it. What's the deal with the hung GPUs?
41:21 - Jeff Massie (Co-host)
Well, we're still pretty early in the 6.14 kernel release and, as the time of this recording, we're only on release candidate number three. But if we look ahead to the 6.15 kernel, something very helpful, I believe anyway, is coming our way. The feature I'm talking about is a standardized way of informing user space of a hung GPU you know, stuck, glitching, whatever. So if anybody's not sure what a hung GPU is, it's a malfunctioning GPU. I should preface this early on. This is initially set up for AMD and Intel GPUs only, so NVIDIA is not supported at this time. But this is a standardized interface. So the article does comment that other non-Intel AMD Linux GPU drivers and non-Intel drivers basically they're saying Team Green will likely adopt this event interface in the future as well, because it's open and sounds like it's not going to be hard to implement.
42:32
It started with Intel graphics driver engineers for their XE and their i-915 direct rendering manager and they added a new event to the kernel. Now this event reports onresponsive hardware to user space. Now the AMD GPU drivers are also able to make use of this device event. When the hardware becomes unstable or hung you know malfunctioning it then notifies user space. Okay, now what? Well, this would allow for a user then to intervene and take actions to possibly be able to recover from this bad hardware state. It could even trigger recovery scripts to automate recovery of the problem hardware.
43:17
Now several things can be done to get the hardware working again, such as unbinding and rebinding the kernel driver. Unbinding and rebinding the actual hardware driver. You know it's talking to the hardware. Unbind that. And there's things like resetting the bus device after the driver unbind. Now they also leave room for other actions that aren't defined at this time. But if you take a look at the link in the show notes there's an example of a recovery script given for a rebind. So it's a way to flag and then you can try to kind of re-kick your hardware to get things going.
44:02
Now in the article in the show notes there's a link to the actual mailing list patch and it has been submitted to the DRM NextQ. So this means that when the 6.15 merge window opens, probably around the end of March, give or take how many release candidates there are in 6.14. It will then be pulled into 6.15 at that time. That is assuming there's no major roadblocks or issues with the patch. Linus doesn't take a look at it and go. What are you doing? Barring any of that? It should make it in Now. These are Intel developers, so they're old hat at this. It's most likely going to make it in now. These are intel developers, so I mean, they're old hat at this, so it it.
44:40
It's most likely going to make it in yeah but take a look at the link in the show notes in the article for all the details on this. But I think for gamers and people like myself who may run beta or even pre-beta software, you know, so you can play games, this might come in handy once in a while.
44:56 - Jonathan Bennett (Host)
Yeah you also find. You also find stuff like I was, I was, I've, I've been in this situation before, right, like I've hung my gpu multiple times and I am used to finding in my error log something like error radion fence weight timed out, and that's just one of the messages that the kernel will throw when the GPU has hung in some way. You run into this like playing a new video game in Wine for the first time when nobody has looked at it yet, and because it's new, it does something unexpected. It triggers some bug in video card firmware or the driver, and any one of these bugs can then cause so what we're essentially talking about is the firmware on your video card crashes right, just like your.
45:42
Your os and your computer can hit a bug and crash. A program can crash. Your kernel can crash. There's code running inside your gpu. That code can crash as well, and sometimes that code crashes because it's just buggy. Sometimes it crashes because your driver is telling it to do something that just doesn't make any sense, all kinds of reasons.
46:01
And yeah, this is the thing and you have in the past you had like I know this is something that they tried to handle in AMD land If your video card crashes right now. If you have an AMD, your machine will attempt to restart it and get it running again. Now, sometimes that works and sometimes that doesn't. But if you're in the middle of playing a game and everything goes dark and then it comes back up again, and maybe even you get a few more frames out of it and then it goes dark again and then it comes back up again, that's your video card trying to reset because it's crashed, and so this sort of thing has been around. What's really neat about this is that they're going to try to make this one um, this one protocol, this one api across all of them. I don't think that would be that would. It's going to make the desktop designers like the kde guys and all that.
46:52 - Jeff Massie (Co-host)
It's going to make their job much easier, going to make them much happier oh yeah, because right now, just so everybody knows, there's no way for the kernel to tell user land and user land is what you and I interact with that something's gone wrong with the GPU currently in the current kernels and this will allow the user land to kind of take a little bit of control on. Hey, maybe here's some things we can do to try to to reset that. And and you also will run into this you know we've got the 5,000 series out from NVIDIA. You know pretty new driver there. We're going to have the 9,000 series out from AMD here in a couple weeks. They're probably going to have some driver issues in there too, because it's all brand new hardware and you're you're going to run into things that you don't normally see, just because they can test a lot of things, but they're not going to run it through the gambit like 20 000 people are yep yep, we links.
47:56 - Jonathan Bennett (Host)
Users do some crazy off the wall things with our hardware.
47:58 - Rob Campbell (Co-host)
Sometimes it's true if I, you know, caught your story correctly and it wasn't, you know, just over my head, like all your other hardware stories. Um, the one key thing I caught here that I think you said in a roundabout way, is that on linux, uh, nvidia has fallen behind again. I think you said right, they don't have this cool new feature.
48:22 - Jeff Massie (Co-host)
That is true.
48:23 - Rob Campbell (Co-host)
I wanted to make sure I heard that right.
48:26 - Jonathan Bennett (Host)
Yeah, this is cool, though you could see doing things like detect what is actually using the GPU and automatically killing that process and then trying a GPU reset If it's a particular game. Rather than crashing your entire system, you can just kill the game. Don't crash my game. I mean, if the whole system crashes, your game is also going to crash.
48:49 - Rob Campbell (Co-host)
Try something else first, sure. We'll try something else first I might be in the middle of something and an animal will kill me.
49:00 - Jeff Massie (Co-host)
You're not that good of a player. Anyway, rob, it'll be okay.
49:06 - Jonathan Bennett (Host)
All right, so it's back up to Rob, and he's going to talk about Gen 2. Have you run Gen 2? Have you daily driven Gen 2 yet, rob? No, well, you need to add it to your list then.
49:19 - Rob Campbell (Co-host)
Well you know, for followers of the show who pay attention and remember these things. Um, if you listen, you would know that I have tried to set up gen 2 in the past and I got to the compile point and well, I wouldn't say I gave up, but I just decided I didn't want to go through it at that time.
49:43 - Jonathan Bennett (Host)
You, just need a faster computer.
49:44 - Rob Campbell (Co-host)
Well, you know, I didn't even start, I didn't even hit the command to start it. I got there and I don't know. So I still had the virtual machine waiting for me to come back and finish, waiting for me to come back and finish. Well, it looks like if I want to daily drive it, there may be another way. You know, gen 2 may have released a much easier way. I mean, I guess they have released a much easier way for people like me to try out Gen 2 in a virtual machine. And what they have released is a pre-made QCOW2 disk image designed to be easily deployed to a VM or a cloud environment. Right now images are offered for the x86-64 and the AR64 platforms and this allows you to quickly, quickly boot into gen 2 with a qemu native qcow2 format. So it it's already basically installed for you on a nice little file, the hard drive or it's storage, whatever uh and it, and they say it's going to be updated on a weekly basis. So you know you're going to get updates faster than your Uba 2 with a fully functional Gen 2 installation. And while they also have future plans to support the EFI-based RISC-5 64-bit and LongArt 64-bit bootable images're, they're not there yet they're, they're expected to come, and you know sure this, you know this kind of defeats much of the purpose of running jet 2.
51:30
You know, kind of building it up from scratch and compiling it, which you know I wouldn't know about because I didn't get that far, I mean I didn't do that yet. But compiling it, which I wouldn't know about because I didn't get that far, I mean I didn't do that yet. But compiling your own system, building it up, making it yours from scratch, how you want it. But it may be a great way for people like me to test it out before going all in. I could put that on a VM and give it a good test run and and find out if I really want to spend the next hours, day, whatever, um, building it up myself. And you know their hope is to become more crowd cloud, more cloud friendly and increase their presence, uh, you know, in data centers and cloud and you know anybody using a VM.
52:20
So, because you don't really hear about gen two in in these circumstances, months, it's it's more the person, people running on their desktops and and, uh, the hobbyist kind of, because it takes some work. It's it's like cross between arch and, uh, lennox from scratch, I mean it's. It's a little easier than Lennox from scratch, except for Lennox from scratch has great directions, though You're really kind of doing all the same thing, except once you have an installed, they do have a pack and package manager. That's my understanding. I've never ran it, but in a way it's also like Arch. You build it up like Arch, but then, instead of installing everything with the package manager, you compile it all. So my understanding. Hopefully I didn't say that wrong because, like I said, I haven't ran it. But I have an easy way to do it soon and I look forward to trying out the q cal 2 image from gen 2.
53:22 - Jonathan Bennett (Host)
Yeah, yeah, that'll be, that'll be fun, it's. It is a valid observation that gen 2 is very difficult to use for real deployments if you have to compile everything from scratch. It's just makes it makes it kind of a no-go so I might.
53:38 - Jeff Massie (Co-host)
I might have to try it because, uh, my pre-alpha 25.04, uh, kubuntu nightly build yeah, it dorked itself along the way, so I have to, uh, and again, nightly build pre-alpha.
53:58 - Jonathan Bennett (Host)
It's not unexpected, right? It's not that much of a surprise.
54:01 - Jeff Massie (Co-host)
So I need to reload to get in a usable state and it's like, oh, maybe.
54:04 - Leo Laporte (Announcement)
I'll try.
54:04 - Jeff Massie (Co-host)
Gen 2. Are you talking bare metal here?
54:08 - Jonathan Bennett (Host)
Yeah, yeah. So this is a QCAL image, so it's specifically for virtualization. I don't know what it would take to try to boot a QCAL on bare metal. I'm sure there's a way to do it.
54:20 - Jeff Massie (Co-host)
No, I'm talking just running regular Gen 2 and just try it You're going to go through it all.
54:24 - Rob Campbell (Co-host)
All right, it's a race.
54:25 - Jeff Massie (Co-host)
Let us know.
54:26 - Rob Campbell (Co-host)
No. I'm not racing, I mean come on, it's taken me like six months already.
54:34 - Jeff Massie (Co-host)
But you've done Arch, right, rob?
54:36 - Rob Campbell (Co-host)
Yeah, yeah, yeah see, then I can just go.
54:43 - Jeff Massie (Co-host)
Oh, you didn't compile your OS, then Zoom is a step above. Yeah, so then?
54:50 - Rob Campbell (Co-host)
you got those bragging rights on the Arch guys. I've done Linux from scratch too, but honestly, linux from scratch has excellent directions. It really does Step by step, and that was one thing that made me stop with Gen 2. Is they're good? I think. Not as good, I don't think. And I got to a point I'm like I kind of wasn't quite sure exactly what I was supposed to do.
55:17 - Jeff Massie (Co-host)
I kind of wasn't quite sure exactly what I was supposed to do and you know, maybe I can try out just okay. What is the basic user experience, starting from just bare metal, empty, drive and go. Okay, what do I do? Because realistically we know, compiling, optimize and all that, it doesn't gain that much For most things. Yeah, it really doesn't yeah unless you're really running a database or something where it's compiling, doing heavy crunching, where every second matters, you'll never notice anything, but I can check it off the list.
55:52 - Rob Campbell (Co-host)
There's a question Does Linux from scratch have Mesa 25.00? And the thing is linux from scratch, you're compiling it, so you get anything you want. You download it from them, from from from wherever the projects are at.
56:11
Yeah, yeah, generally you download the mesa source or any other source. As long as you can get the source code, you compile it, and if you can do that, you got it there. There's no package or repo to no package manager or repo to install things. So but you know, I think, I think, maybe I'll, I'll do the, I'll take the QCow2 image and maybe I'll do like a DD over to a drive and that might work.
56:43 - Jonathan Bennett (Host)
The latest beyond Linux from scratch, seems to be Mesa 24.3.4. So I don't know what it would take to try to do 25 instead. Things like Mesa tend to be a little more difficult to just jump ahead inversions. Um, it might work, it might not.
57:06 - Jeff Massie (Co-host)
You just have to see there's a lot of dependencies that come along with. You say, okay, I want 20 mesa, 25.0.0, oh, but then here's 16 other things that have to be upgraded and aligned that's essentially the whole point of b of linux from scratch was that there was always these sort of interleaved dependencies.
57:28 - Jonathan Bennett (Host)
Like you have to have to have the kernel, you know xyz, you've got to have one of these three gcc compilers and you have to have one of these three libc versions, and trying to figure out which ones of those went together was, I think, for the longest time and probably still to some extent a huge pain to try to figure out. And so that's that's what Linux from scratch was. It was a manual, for here are known compatible versions of everything, and then also here, you know, it comes with instructions to actually bootstrap into an environment to be able to build the kernel and enough things to get a running system.
58:07 - Rob Campbell (Co-host)
Yeah, so the directions are not for 25.0 yet. Not yet. If you're adventurous and you want to do it on your own. It's probably well, it's got to be possible. Obviously Somebody built it. Yeah, it's possible. Yeah, it's probably well, it's got to be possible. Obviously somebody built it.
58:18 - Jeff Massie (Co-host)
Yeah, it's possible yeah, it's just you're going to have to research those dependencies on.
58:23 - Rob Campbell (Co-host)
You're just gonna go to hate your life for the next week or month, or well, but this is this is actually.
58:30 - Jeff Massie (Co-host)
You know, okay, rob wants to make his coffee linux, you know, and he's. He'll tell you where to send the coffee at the end of the show. But anyway, he wants to make his distribution Linux from scratch is how you do it. This is where you say, oh, I want to have this kind of kernel in this version of Mesa and I'm going to make it. Whatever. This is what somebody who builds their own Linux distribution basically goes through. This is what somebody who builds their own Linux distribution basically goes through. Well, do they? I don't think so.
58:59 - Rob Campbell (Co-host)
Well, if you're truly from scratch, not a derivative, I'm basing it off of something else, but a few.
59:10 - Jeff Massie (Co-host)
But if you want it unique, there you go.
59:14 - Jonathan Bennett (Host)
Yep, yep, I would recommend a build system and a package manager to go with it, not just lfs, but you do, you, rob coffee, linux can be whatever you want it to be, all right. Uh, we've got one. Oh, this one, yes, we've got one more story from me. And then we've got one more story from jeff. Uh, oh, this one is fun, this one is so much fun. So Meta, the company previously known as Facebook, is sort of in legal trouble because it torrented a whole bunch of books. That is fun, this is so much fun. This whole story is so much fun. This whole story is so much fun.
01:00:06
Meta torrented a huge data set of pirated books for AI training and they got caught, and a group of authors are taking them to court, and there are multiple claims that are happening in this court case, and there are a couple of them that are very, very, very interesting. All right, so one of the first claims is that these authors are claiming that it is unlawful for Meta Facebook to copy and distribute these written works via AI outputs, and so this is getting into a question that I find very, very interesting Is training an AI on copyrighted works enough of a transformative work that it breaks the chain of copyright from the original works. It's a huge legal question that we all have in our current AI world, and this is one of the court cases that is going to decide it. We've got a group of authors on one side and we've got Facebook meta on the other, so that in and of itself is super interesting because we need case law on this. We need the world to sort of come to conclusion of how much training or at what point is training in AI the same thing as stealing written works, and it's not going to be a black and white answer. There's going to be some point where, if you can get the AI to spit back out the word for word original works, then, yes, you have broken copyright law, but if you can't do that, then it's more of an open question, right, and I've seen some people say well, trying to block an AI from doing it essentially makes it illegal to read a book, because arguably there's not a whole lot of difference between what an AI does when it reads a work and sort of makes that work part of itself, and what we humans do when we read a book and we sort of make that book a part of our own psyche. So that's an interesting thought experiment as well.
01:02:09
What makes this one particularly fascinating to us as Linux users is that Meta torrented these pirated books and so these book authors and publishers are also going after them for the unlawful distribution of copyrighted works through illegal torrenting, which has long been considered established case law. I'm reading from the Ars Enica article long been considered established case law. I'm reading from the Ars Enica article. And Meta's response to this their legal defense is yes, we torrented those things, but we didn't seed the torrents, so it's not actually illegal, which is hilarious to me. So, yes, we downloaded it, but we didn't re-upload it, so we didn't actually break copyright. It was whoever packaged up that torrent and uploaded to us. That's who wrote copyright, and boy, that's actually really fascinating. Legally, if that were to become case law, that would change the way piracy cases were handled. For it to become suddenly not illegal to download something via torrent, only illegal to seed it to re-upload. Boy, that's fascinating. Um, yeah, very, very, very interesting case going on here. That I will be.
01:03:29 - Rob Campbell (Co-host)
I will be following it's usually been the seeds that, uh, or the actual uploading of it that's gotten people in trouble. But, as I was thinking about it, not always true. I had somebody I knew one way or another gave their computer to a relative. I think they had some disabilities or something to the relative and maybe it got caught. Maybe they actually tormented him, seated him back up, I don't know, but I know that somehow they found him on the computer and then it got back to them and it cost them like $2,000. This was like 15 years ago too, but I guess it could have been. Actually, I bet it was also uploading in that case too. So it's usually the upload and they get you in trouble. Yes, yes.
01:04:29 - Jonathan Bennett (Host)
Well, because if you're uploading, then you are participating in actively distributing. They're not stolen, right, it's not technically theft, but you're you're actively participating in um, in breaking that copyright. Um, yeah, it's a, it's a. It's a. It's an interesting case. It's, it's weird, um, and there are some weird questions around the idea of torrenting and pirating and all of that as well. Most of those have been kind of settled over the years, but this one is pretty interesting. It's interesting if only because it's such a big company with lots of legal team.
01:05:07
That's making the argument and, unfortunately, that makes a huge difference. Right, it's one of the downsides of the US, not just the US legal system, the legal system around the world. Right, and that's one of the. It's one of the downsides of the us, not just the us legal system, legal system around the world. Right, it's just one of the one of the problems. I'm not sure there's any solution to it, but to be able to make a novel claim like this and argue it in court, you've got to have the money to be able to pay court fees and lawyer fees, and so you've got to be fairly big to be able to make a claim like this and test it in court.
01:05:33
If, if, if I torrented something and they came after me, it may be true that, hey, I didn't seed it, but I would have no way of fighting that.
01:05:42 - Rob Campbell (Co-host)
Five, ten years from now, we'll give you all an update on this.
01:05:47 - Jonathan Bennett (Host)
Yeah, let's see the downside. Things move extremely slowly. But yeah, it's just so fascinating to me and, like I said, not directly Linux related, although this could have repercussions for torrenting, even torrenting Linux ISOs.
01:06:02 - Rob Campbell (Co-host)
Facebook runs on Linux.
01:06:03 - Jonathan Bennett (Host)
It's all Linux.
01:06:05 - Rob Campbell (Co-host)
They're contributors to Linux. They're big on the. Are they big on the ButterFS, I think, file system? I?
01:06:12 - Jonathan Bennett (Host)
think Possibly. I know they do a lot for PHP as well, I know they do a lot for PHP as well.
01:06:17 - Jeff Massie (Co-host)
ButterFS, and they're big on the IO ring design. That makes sense.
01:06:25 - Rob Campbell (Co-host)
Yep, yeah, they were big on ButterFS, I think, before anybody was really barely using it, if I remember right.
01:06:32 - Jonathan Bennett (Host)
Yep, all right, so let's hit our last story, actually, and that is Jeff, and he has the story about changes at Mozilla.
01:06:44 - Jeff Massie (Co-host)
Oh boy, yeah. Mozilla Corporation's president, mark Sermon, announced plans today to well not today, I guess, wednesday but to tackle what are major headwinds facing the company's ability to grow, make money and remain relevant. To quote Mark, he said Mozilla's impact and survival depends on us simultaneously strengthening Firefox, finding new sources of revenue and manifesting our mission in fresh ways. So how are they going to do this? Well, they have a new council composed of executives from each of the different Mozilla organizations. So they have Mozilla Corporation you know someone from Mozilla Corporation Mozilla AI, the not-for-profit Mozilla Foundation, and MZLA Technologies, slash Thunderbird and Mozilla Ventures, which it's Mozilla Vent ventures, which is its capital venture arm.
01:07:41
Now, a major note is the absence of michelle baker, co-founder of firefox. She is no longer a chair or member of either the mozilla foundation or the mozilla corporation boards. Now she's been a polarizing figure in the past due to mozilla having layoffs while she was receiving multimillion-dollar salary payments. We've covered in previous shows how the drama and contention surrounding her paycheck and direction for the company have really there was a lot of people that disagreed with her direction and the amount of her paycheck, based on the size of the company, and so I'll leave it at that, but she is now completely out of Mozilla privacy-respecting advertising fund. Develop and push open source AI features to remain product relevant and pursue novel new fundraising initiatives. Now, they didn't go into what that is. That's just the direction they're heading. The article does mention that, while Firefox is named a few times, it's not the central focus, even though it brings in the most revenue because of the deal with Google. For those who don't know, google pays Mozilla a lot of money to have Google as the default search engine on Firefox.
01:09:06 - Jonathan Bennett (Host)
And you can distill that statement even more and say that Google pays Mozilla for Chromium to not be the only browser in existence.
01:09:13 - Jeff Massie (Co-host)
I was just going to say that.
01:09:14
Yes, I was going to read between the lines and say we don't want to be stuck with a monopoly, so we're paying Firefox to be around. Yes, yes. The article continues with some editorial comments from the author. Now, this is just from the author and just summarize him. He understands that Mozilla is in a difficult position because, you know, based on legal cases, the funding Mozilla gets from Google could be in jeopardy. He goes on to say finding an equitable, sustainable future to maintain its flagship browser and advocate for an open web. It needs to be Mozilla's priority. You know there has to be an alternative out there. Take a look at the article in the show notes, which also has links to LWN's comment section. In addition to where this article is from, the link in the show notes is OMG, Ubuntu, UK, and they have their comment section in there too, where, you know, there's a lot of people with input and I'm sure my co-hosts have some opinions on this and I would love to hear them. I do?
01:10:33 - Jonathan Bennett (Host)
Um, I'm going to let Rob go first. I want to look something up, so go go Rob, Um I?
01:10:40 - Rob Campbell (Co-host)
don't know, I just I don't know, I just I don't know, I'm speechless.
01:10:57 - Jeff Massie (Co-host)
Well, a lot of the comments in both comment sections basically came down to stop focusing on things besides Mozilla. Stop making goofy little side projects that nobody wants, nobody cares about, you know. Really focus on making the browser really, really good.
01:11:09 - Rob Campbell (Co-host)
I mean, I feel like we have said it all before and I guess I don't know if I want to be too redundant with it, but yeah, obviously she was getting paid too much. They get a lot of money from Google, blah, blah, blah. And yeah, obviously Firefox browser is their thing. That's what they should focus, focus on. And obviously Firefox browser is their thing, that's what they should focus on. And I think they should spin out their email client.
01:11:40 - Jonathan Bennett (Host)
So, okay, the email client is already spun out. Oh yes, you, rob, and everybody else listening, need to go listen to Floss Weekly episode 820. Oh, firebird is under the Mozilla organization, the open source, the nonprofit. It is not a part of the Mozilla corporation, which is an interesting note to make. I was looking to try to figure out this press release that they put out. What does it represent? Is it the corporation or is it the organization? Because those are two different things. I am going to say that I think diversifying is the exact opposite of what they need to do.
01:12:39
Mozilla has two core competencies. So, if we're talking about the Mozilla open source like nonprofit organization, right, there are two things that they do that people care about, with a possible third. I'm going to list a third that I think people should care about, but there are two that people really care about, and that is Thunderbird and Firefox. Those are the two things that are on Mozilla that anybody cares about. Those are the only things. Those are the only things that Mozilla does that people care about, none of the rest of it. Those are the only things that Mozilla does that people care about, none of the rest of it. There is a third thing that Mozilla does that people should care about, and that is trying to engage with politicians and teach them about how technology actually works. Right. This is a thing that Mozilla actually does, and so I get to talk to some of these people. Simon Phipps is also in the same space, for example. So when you have something like the UK trying to say, well, we need encryption backdoors, one of the things that the Mozilla organization does is they try to come along and say let us tell you why this is a really bad idea. And so Mozilla does this sort of.
01:13:42
In the realm of web technologies, you and in this realm, one of the things that you get, you get fun things like standards being adopted that everybody is required to support, that have patents tied up in them, and so then you this is this is one of the ways that big companies that own patents make money, by the way. So let's say a video codec. Well, let's make this video codec standard for the web. Let's get politicians to encode this video to specify that this video codec is a standard for the web. And oh, by the way, mpeg LA owns 72 patents on this, and everybody that runs this video codec has to give us a $1,000 license. Lots of money gets made this way, and so one of the things Mozilla does is they come along and they will say this is a really bad idea. Let's not use patent and cover technologies inside of these standards.
01:14:43
That's the third thing that Mozilla does that is worthwhile. That is the third thing that Mozilla does that is worthwhile. Not as many people know about it, but it is something that they do. No-transcript. Stop doing things that people roll their eyes at. Stop putting out observations like that. We've got to diversify.
01:15:18
There are three things that I want Mozilla to do. I want you to make Thunderbird great, I want you to make Firefox great and I want you to keep some common sense. Try to teach politicians common sense about the way that open source and the web works. Those are the three things. Anything not related to those needs to go, and if they were to do that, I think they could probably turn profit and then take inspiration from what Thunderbird has done, and Thunderbird, in turn, took inspiration from what KDE did, and that is, every six months, pop up a little notice that says we pretty much exist because people give us money. If you enjoy what we're doing, please give us a little bit of money. Do it in Firefox exactly what they've done in Thunderbird. Thunderbird and KDE have had huge success with this. Do it in Firefox.
01:16:08
Do not do ads. I can tell you nothing will tell. Nothing will get people to uninstall Firefox quicker and having ads built into it, because the people that get totally irritated like that are the people that are running Firefox. Um, it is a, it is a. It is a betrayal of the existing user base to do something like ads in the product. So don't do that. Don't do any of that dumb stuff. Just let people know this is the amount of money we need. If you can't support us, then we're eventually going to go away. People will come out of the woodworks to support you, but stop doing all the dumb extra stuff.
01:16:40 - Rob Campbell (Co-host)
Okay, I'm going to give a slightly different take. Feel free, so focus on Firefox. That's. Feel free, so focus on firefox. That's, that's your baby. All the things you said great about firefox. Good, uh, thunderbird, spin that off, go, go, give that to libre office or something.
01:16:57 - Jonathan Bennett (Host)
I know thunderbird. Thunderbird is already its own company. It is not part of the corporate structure of mozilla. It only exists underneath the non it is in that nonprofit umbrella.
01:17:09 - Rob Campbell (Co-host)
Yeah, go give that to LibreOffice. They can donate to them, but I think that should be bundled in with LibreOffice or something. And then, for the other, the educational or lobbyist branch or whatever you want to call it spin that off too. I mean, it should exist. Fire mozilla can donate to it and support it, but let it be its own thing. Don't let it drag other things down on their main focus yeah, yeah, that's fair.
01:17:42 - Jonathan Bennett (Host)
I think we could probably go one step forward and say that all of this needs to be very clearly delineated, right? So have the Mozilla overarching nonprofit that helps manage all these things, and then split it up into these three different groups.
01:17:56 - Rob Campbell (Co-host)
Yeah, that works too. You know, whatever it is, you know, don't let the other two detract from Firefox. And you know, if people care more about the educational piece than they care about Firefox, well then that's where their donations and support will go and Firefox will go away, and not that I foresee that happening. But you know, let's let the support speak for itself. You support this, let it go to that. You support this, let it go to that. That's fair. And I suppose you, you know the foundation, can be the one who can support a manager, just like the linux foundation I guess you know does are in the, in the. Well, all the foundations they have, like all kind, they're an umbrella over top of so many things. And maybe there's just some confusion, the fact that it's the mozilla foundation and mozilla firefox and mozilla thunderbird, I don't know, maybe that grays it for a lot of us. So we don't really realize that there's maybe more, a little more separation than we think but yeah, there's several sub corporations under there.
01:19:03 - Jeff Massie (Co-host)
But I mean I can totally see, you know really what needs to happen. I mean I know it's different, but you know, Thunderbird, they need to make it, uh, probably a little more corporate friendly. You know, really may just juice it up and they're working on it.
01:19:19 - Jonathan Bennett (Host)
I will. I will also say they are working on that that is one of the that is one of the goals that they that we talked about on the show is being able to do, like Office 365 integration inside of Thunderbird, and that is coming In fact, it's partially working and they are putting the finishing touches on that.
01:19:36 - Jeff Massie (Co-host)
Nice and as far as like AI only where it helps browsing, be better, work on AI and not as like I'm going to make a virtual assistant, I'm going to help it maybe hit multiple search engines, something like that or whatever. And it does surprise me because when you read the comments, it's overwhelmingly of make Firefox better, make it the top browser. Focus on that. I mean it's like 95% of the comments say that. And there's a lot of comments saying you know, focus on that. I mean it's like 95 percent of the comments say that. And there's a lot of comments saying you know what I would donate to it. They said I would. You know. A lot of people said you know, kind of the wikipedia style of hey, you know, if you just give us a couple bucks, you know it'd really help.
01:20:21
Yeah, and people donate and even if they're worried about Google saying because the court case is saying, oh, we cannot force, you know, you cause, basically it comes, it's coming from kind of an antitrust spin of saying, okay, Google can't pay everybody to make Google the default search engine, because that's like antitrust or whatever. Well, you know what? Google's still going to hit that donate button and go well, here's a few hundred million just to stick around. You know, because it's not illegal to have a monopoly. It is not illegal. But when you are classified as a monopoly, you have an extra large set of rules you then have to play under. I mean, it brings a lot of overhead and they just as soon say we don't want that. Hey, firefox, keep going. And as long as they can keep it a viable alternative, they go we're not a Monopoly. Okay, we have 99 of the market, but we're not a Monopoly. Yeah, there's, here's an option you can go to.
01:21:24 - Rob Campbell (Co-host)
Right here, that's viable yeah, so I I haven't given thunderbird an honest chance in a long time. I'm looking at now it actually looks a lot better than it used to, than it used to be. I mean I'm it is maybe very petty, but what just drove me nuts is just kind of the look and feel of it. It just always looks so antiquated like, just like something made in the early 2000s and looking at it looks pretty good, but I can't remember. Now is there theming, because I still don't like the icons in it I think there is some.
01:22:00 - Jonathan Bennett (Host)
I think they're working on more trying to remember it's been. It's been a little bit so I had that conversation.
01:22:07 - Jeff Massie (Co-host)
They went through a big revision here about six months ago. They really advanced the code quite a bit, yeah, because it stagnated for quite a while, and then they had a big release and now they're back into it.
01:22:22 - Jonathan Bennett (Host)
Well, they came to the point where there was only budget for a very small handful of engineers to work on it. And they came to this point where it's like, well, what do we do? Do we spin out and go into the library office? Do we do something else? And they came to the conclusion they said we're going to ask people if they want Thunderbird to stick around. And people overwhelmingly said yes, there's a large group of people that love Thunderbird and want it to continue. It's okay, we're going to ask them. Every six months, we're going to do a pop-up and ask people to give. And they've been able to hire multiple full-time engineers off of that. They've done exceptionally well with it.
01:23:01 - Jeff Massie (Co-host)
Well, and I'm glad to hear there's a corporate take on it too, because this is a problem that they're aware of. Yes, I have to use outlook at work. It's, it's all windows based, and outlook, the new outlook. I have tried it. It is like fisher price outlook for you know. Oh, it's great for somebody that I know which.
01:23:24 - Jonathan Bennett (Host)
I know what you're talking about.
01:23:25 - Jeff Massie (Co-host)
Yes, it is yeah, and I forced it back to classic and I'm still on classic and I'm going to, I'm going to die on that, but it's you know, for anything that's serious email. The new version is horrible. It is not. You know when you're getting. You know 800 to a thousand emails a week and you've got to go through them and you know really power through stuff. That new one is just it's made for grandma sending an email.
01:23:58 - Jonathan Bennett (Host)
I was, I was with a customer.
01:24:00
Yeah, I was with a customer it's been a couple of months ago, um and he got updated to the new outlook and there was something that we needed to do. We needed to do something with one of his actual Outlook files, like split, I think. We needed to create a new offline Outlook file and download email into that so that when his email account went away, he wouldn't lose it all. And you couldn't do it. You could not do it in the new Outlook. You could not make a separate file. That's what it was.
01:24:27 - Rob Campbell (Co-host)
which new outlook is? That is that the paid one or the one that's built into windows 10, because they have everything's called outlook now that's part of.
01:24:34 - Jonathan Bennett (Host)
That's part of the problem. I'm not sure which it was, but I went searching on the internet it's like how do you do this in new outlook and found several threads you just can't. It's not, it's not supported not at all, I think.
01:24:45 - Rob Campbell (Co-host)
I think the one that's comes built in with windows 10 has the bigger issue where jeff is talking about the paid one, where they just, yeah, made it a colorful.
01:24:58 - Jonathan Bennett (Host)
Uh yeah, so one one more thing that I will really quickly touch on um people are. A couple people in the chat mentioned well, webmail is so good. Now Gmail's webmail is so good. Why would you want Thunderbird? And I would tell you, one of the reasons that you actually want Thunderbird is to have an offline, local copy of your emails. I don't like.
01:25:19 - Rob Campbell (Co-host)
Gmail, webmail either.
01:25:20 - Jonathan Bennett (Host)
I mean, I don't care if you like Gmail, I like Gmail webmail, I use it a lot.
01:25:23 - Rob Campbell (Co-host)
I don't like the interface. I don't like the interface.
01:25:26 - Jonathan Bennett (Host)
I don't like their interface either, and that's totally fine. But, like every once in a while, you will lose connection to the Internet. I know it's hard to believe, but it does happen.
01:25:35 - Rob Campbell (Co-host)
I like Thunderbird's interface better than Gmail webmail.
01:25:40 - Jonathan Bennett (Host)
Yeah, I probably do a little bit too.
01:25:43 - Jeff Massie (Co-host)
The online versions too. I see there's like Curious's Outlook 365 online got much better a while back. It's still terrible. It does not. When you're doing now I'm talking serious emailing here, I'm talking, you know, huge number attachments, you're forward to get through it. You know you can't. You can't sit around and kind of oh, let me sounds like you need a secretary or some ai no, I fly as well, and I'll tell you what administrative assistant sorry but I, I, you know, I know we're getting off a little off the rails, but online office like excel and word, it's missing too much functionality.
01:26:29
It's yeah, it's again.
01:26:31 - Rob Campbell (Co-host)
It's built for grandma sending something once in a while when your online outlook is okay, but excel's losing, missing a lot of functionality.
01:26:40 - Jonathan Bennett (Host)
Yeah, word isn't if I, if I wanted that, I would just go use Google Docs, right yeah.
01:26:48 - Jeff Massie (Co-host)
But again at work. Yeah, I'm a power user.
01:26:55 - Rob Campbell (Co-host)
I'm probably using a lot of functions that most people aren't. Windows power user here.
01:26:57 - Jeff Massie (Co-host)
Yeah, as somebody said in the comments, roger H, jeff is an email, one percenter you know, get my patch, but for home it would be okay. You know I'm not doing anything but at work.
01:27:12 - Rob Campbell (Co-host)
No, it does not hold a candle to the applications so to bring this back to linux, one thing I'm I'm looking at thunderbird here, and they seem to be following the new outlook design with that tab on the side that I kind of dislike. I really hated when my outlook at work would put that tab running down the left side, and that's what thunderbird did too.
01:27:34 - Jeff Massie (Co-host)
I'm sure you can change it yeah, well, yeah, I went through and because even when they changed the wanted outlook, I went through. And I want compact mode. I want to get rid of the big fluffy headers with the pictures.
01:27:45 - Rob Campbell (Co-host)
I would, because I got to get more information on that screen and I need to read 20 emails at a time you'd be surprised at what you I mean the you need to find that delete button a little quicker shit oh, I, oh, I do.
01:28:03 - Jeff Massie (Co-host)
I use the yeah, I, I do, because I literally say a thousand emails a week. You have to be able to sort through them and there's ways you do it to just speed through it.
01:28:18 - Rob Campbell (Co-host)
You just select, select, delete. Hope there's nothing in there important. If there was, they'll email again I'm going to give Thunderbird a shot. It does look a lot better. I really want to change those icons because they look colorful, kind of like something I would have thrown on a website about 15 years ago. But if I could fix that, I think I'm okay with it.
01:28:41 - Jonathan Bennett (Host)
I think it has some theming, so give it a test run. Let us know what you think.
01:28:45 - Jeff Massie (Co-host)
I've been using Gmail for a while and I still like I'm kind of lukewarm on it. But you know now's a good time. I maybe as well. I will try thunderbird and, uh, give it a shot again, because I used to use it all the time. Quite a while ago.
01:29:00 - Jonathan Bennett (Host)
Yeah, it's. It is once again getting getting to be better and much more usable. All right, let's get this. Command line tips we've talked to. We've pontificated enough about the news. We've told the mozilla folks what they need to do. Let's tell the users what they need to do rob. What is q?
01:29:18 - Rob Campbell (Co-host)
I got something really cool for you guys spelled K E, w, it's a, it's a terminal, uh, audio player. So basically it's, it's it's when amp for your terminal. So if back in the day I would have loved this, you know, 25 years ago, I'd set up a computer and the thing would be hooked up to an amp and just some speakers, basically basically dj for friends and and I just have a playlist going and I'd have to use this graphical user interface when it's just not necessary because q will do that for you. All, right, for those watching. I'm going to give you a little snippet of q and this is in, like all you know app to install K-E-W.
01:30:11
There are a couple of things to set up. You have to point it to the directory where your music is, which isn't hard. If you run Q, it says can't find directory. Run this to point to your music directory, not hard directory, uh, not not hard, um, and yeah. So if you're on q, I put a few, I grabbed a few uh mp3s, slapped them in a folder here, uh, to demonstrate. I said I want you to see all my inappropriate music. So I mean I guess I just grabbed whatever. So if I so, here, uh, for those watching, um, if you can see that, yeah, you guys can see that. Uh, you can see the songs in the directory.
01:30:59
There's, uh, some f keys. F2 will show the playlist, uh, which I have nothing yet. F3 is going to show the library, which goes on. F4 is going to show the tracks, so goes on. F4 is going to show the tracks, which is nothing there yet. F5 will show all the keys. It gives you all the shortcut keys plus, minus for volume, arrow keys for tracks, scrolling through the playlist, up and down arrow keys. I'd toggle color, delivered from album or from profile. I'm not going to go through all these, but there's a bunch of keys that you can use to navigate through fast forward, backwards and then. So, if I go to the f3, to the library, I'm gonna click on a couple of these two area. Click on a couple these dad to the playlist here. So I'm going to stars by them now. I'm going to stars by them Now. I'm going to go. Well, I'll show you the playlist there. Shows it right there.
01:32:10 - Jonathan Bennett (Host)
If I hit F4, I don't have the audio piping in, but I thought you said you weren't going to show any of the inappropriate ones.
01:32:26 - Rob Campbell (Co-host)
Yeah, I guess it does. It has the explicit, explicit lyrics, doesn't it? But you can't hear it because I do not have the audio piped over. But you get a nice little, um, well, a nice. You get a text-based album cover, which I assume that's what the album looks like. I don't know.
01:32:47 - Jeff Massie (Co-host)
It looks like an. It looks like an adult game from like 1985.
01:32:51 - Jonathan Bennett (Host)
Yeah, exactly.
01:32:55 - Rob Campbell (Co-host)
It's just a bunch of colors, and then you have the what is that called? The sound at the bottom there there's a name for that with all the bars going Equalizer, equalizer.
01:33:12 - Jonathan Bennett (Host)
There we go.
01:33:13 - Rob Campbell (Co-host)
It's more like a visualizer honestly, yeah, because I can't adjust it or anything, but anyway you can be listening and you can just have a simple little audio player and you know whateverj for your friends or or go professional, whatever you might want something fancier than this, but a nice q little music player yeah, your spectrum analyzer in the bottom yeah, there you go, there you go.
01:33:42 - Jonathan Bennett (Host)
That's neat. Now the unfortunate thing is on my systems it's not available to install via the package manager. I don't know why pop os does not have it but it does not. It's not available to install via the package manager. I don't know why Pop OS does not have it but it does not. And it's not packaged. On Fedora, they had a DNF in there. They have a DNF to get all of the things that you need to be able to build it. Ah well, it's fine, I know how to compile software.
01:34:05 - Rob Campbell (Co-host)
On Ubuntu. It installed it all, Yep so.
01:34:08 - Jonathan Bennett (Host)
Yeah, yeah. So a win for Ubuntu, I guess. No, that's actually pretty neat. I have wanted something like that a few times in the past, so we'll definitely add that to my little toolbox of tools.
01:34:21 - Rob Campbell (Co-host)
Yeah, I've found times when I wish I had that and I had to go with other workarounds.
01:34:31 - Jonathan Bennett (Host)
Yep, yep. So, jeff, I found a command line tip and I got really excited about it because it was really cool and I had never seen anything that quite did this before. And I found it and I went to paste it into the command line tips and I discovered that you found the same command line tip and you beat me to it. We're gonna let jeff talk about kill ports and then I will talk about something else.
01:34:51 - Jeff Massie (Co-host)
Okay, for my command line tip. I have two links in the show notes. The first one is to the Linux TLDR website that goes over the command line tip, which is kill port, k, I, l, l, p or P O R T. The second link is to the GitHub page for kill port. Now, kill port is basically like how it sounds.
01:35:12
It's a command line tool that lets a person kill a process based on the port it's using. So just, I know there's a lot of people you know Ken's probably listening going I can do that, I don't need, I don't need a program. But you know, manually doing it is a little more cumbersome. You know you'd have to find your open port, look for the responsible process behind the port, find the process PID and then stop that process. This tool just simplifies things. The article in the show notes goes on. It talks about how to install it, which is available. It's available for Linux, windows and Mac OS Goes over the installation methods for Linux and then it goes into the usage of Killport and it's pretty easy.
01:35:56
I mean, the easiest way to use it is simply sudo killport 80, which would kill whatever process you have on port 80. Now you can do more than one you can. In the example they have, they set up something so it's listing on port 80 and 88. Well, if you want to kill both of them, you do pseudo space kill, port space 80, space 88. So you can just list the ports you want to kill. Now there is a V flag that you can use which will allow you to see the verbose mode. So it gives you a lot more information that it's just showing that, yep, it definitely killed what you said you wanted to kill. And there's also a dash S flag If you want to kill the process using the SIGUP, sigkill or SIGTERM signal. So if you want to use those, you can. The command is really pretty basic and you can take a look at the article linked in the show notes for more information, but that's pretty much everything. So it just simplifies something that you manually could do.
01:37:01 - Jonathan Bennett (Host)
Yeah, that is neat and it's a Rust program, so it looks like generally you'll install it with Brew or, excuse me, you can install it with Brew. That is one of the options, but Cargo is what I was trying to spit out there.
01:37:14 - Rob Campbell (Co-host)
Yeah, I guess we got a Mac user here.
01:37:17 - Jonathan Bennett (Host)
You can run it on Linux. There's also on Linux.
01:37:21 - Rob Campbell (Co-host)
You can, but most people running Brew are probably on Mac.
01:37:27 - Jonathan Bennett (Host)
Maybe, what was that.
01:37:31 - Jeff Massie (Co-host)
Jeff, oh, and there's also a script method. So if you don't have Homebrew or Cargo, they do have a script you can get with Curl.
01:37:42 - Jonathan Bennett (Host)
Okay, cool, All right, I'm going to plug. Actually it's not exactly a terminal. I mean, you run it from the terminal, but then you use your web browser to interact with it. It is Stable Diffusion Web UI and this is actually a Python program. But the thing that's interesting about it to me, this uses Stable Diffusion to do AI generation of images, and it works on AMD cards with PyTorch and the RockM backend, and what's really interesting to me is it's a pretty good test. It actually works with the Fedora RockM packaged packages Packaged packages, sure.
01:38:26
So I've got a link off to the actual GitHub page and then also to a YouTube video that I found extremely helpful, talking about how to actually get this thing installed on a Fedora machine.
01:38:38
Um, and so you know there all of the all of the normal um AI image generation things apply here. So you know you can go get your models of a hugging face and all of that. But also don't be dumb with AI, especially because when you're running these locally, they don't have all of the safety things built into them that they will running them off of website, and so don't be dumb with the things that you make your AI generate for you and that you then send to people Just don't be dumb the things that you make your AI generate for you and that you then send to people. Just don't be dumb. Don't break any laws, Don't be dumb. I do not claim any responsibility for people doing dumb things with this, but it is cool that it works and that it can work on local machines and that it can work with AMD video cards. The world is not all CUDA anymore, and that is the main thing I find neat about this.
01:39:28 - Rob Campbell (Co-host)
Yeah, don't be dumb and download torrent books and train it with your AI.
01:39:34 - Jonathan Bennett (Host)
Don't train your AI on torrented books. Yes, that is the lesson that Facebook engineers learned, or maybe didn't learn. I don't know Just the cost of doing business, right? Okay, well, I think we've gotten through everything. I will let each of the guys. I don't know Just the cost of doing business, right? Okay, well, I think we've gotten through everything. I will let each of the guys plug whatever they want to plug. We'll let Rob start. I have a feeling that he's going to try to plug Coffee Linux.
01:39:58 - Rob Campbell (Co-host)
Yeah, I've just got the same old plug that I do every time because I'm boring. I'm not as fun as Jeff with the cool poems. Here's my poem. No, never mind, I can't think of anything. Come and connect with me online. If you go to robertp campbellcom you'll find my webpage, all kinds of cool things about me. Well, maybe not that much. There's some things there, but the key thing I'm trying to point out here is near the top, in the gray little box, you'll find little button links to my LinkedIn, my Twitter, my Blue Sky, which I am trying to be more active, or I am maybe the most active here these days. Active here these days mastodon, which I'm second active, I think, and coffee linux. No, this is, uh, where you can donate coffees to little old me and let me know that I'm still appreciated.
01:41:04 - Jonathan Bennett (Host)
Or yesterday was my birthday, so if you want to send me a birthday coffee, get some of that too how many coffees do we have to buy you to get you to roll your own linux, to make coffee linux a reality?
01:41:21 - Jeff Massie (Co-host)
uh 20 000 um all I know. All I know is one of those coffees was earmarked for me, so rob owes me uh I'm headed out your way in the summer, so oh, nice, nice, I'm gonna, I'm gonna convert it to beer, though, or coffee beer.
01:41:41 - Jonathan Bennett (Host)
There you go all right, uh, jeff anything you want to plug.
01:41:47 - Jeff Massie (Co-host)
Not really. I'm not very active on social media, but I do have Poetry Corner. This one's for you. Rob Hickory, dickory dock, Don't watch Netflix on the clock we can see what you're doing. Bandwidth you're ruining and soon that website will block have a great week everybody.
01:42:12 - Jonathan Bennett (Host)
Yep, fun, fun, fun, all righty.
01:42:14
Thank you guys for being here. I sure appreciate it. You can find my stuff on most of it on Hackaday these days, including Floss Weekly. You can find the Untitled Linux Show here at Twit. You can find Floss Weekly over at Hackaday.
01:42:28
And we have had a string of really cool interviews. Unfortunately I've been doing them by myself because my guys have just not been responding. I've got Rob lined up to come for next week, so we're making progress there. But we've had a couple of really interesting ones. This past week we interviewed Gregory Kurtzer and one of the community managers at Rocky Linux to kind of be the bookend to our Alma Linux episode from several months back. And then we did also the week before that, talk to Ryan Sipes from Thunderbird and that was a really cool conversation and we did indeed tell him please don't add AI Clippy to Thunderbird, and he was in agreement with that. So I think we're safe there. But that is a lot of fun.
01:43:11
You can also find my security column goes live there every Friday morning at Hackaday. We have a lot of fun doing that too. And then of course, here at Twit with the Untitled Linux Show. We appreciate those watching, those who got us live and on the download. Don't forget to check out Club Twit if you haven't yet. It's about the price of a cup of coffee per month and you can support the network that you know and love. Keep us on the air. We sure appreciate it. And, yeah, thanks for watching. We'll see you next week
