Tech Over Tea - Most Linux Distros Are Just Config Scripts | Dark Xero

Episode Date: April 26, 2024

The last time he was on Dark Xero was still developing his distro Xero Linux but since then he decided to drop it and instead shift over to being a post install config script for Arch which is probably much healthier for the project. ==========Support The Channel========== ► Patreon: https://www.patreon.com/brodierobertson ► Paypal: https://www.paypal.me/BrodieRobertsonVideo ► Amazon USA: https://amzn.to/3d5gykF ► Other Methods: https://cointr.ee/brodierobertson ==========Guest Links========== Website: https://xerolinux.xyz/ Github: https://github.com/XeroLinux YouTube: https://www.youtube.com/@XeroLinux ==========Support The Show========== ► Patreon: https://www.patreon.com/brodierobertson ► Paypal: https://www.paypal.me/BrodieRobertsonVideo ► Amazon USA: https://amzn.to/3d5gykF ► Other Methods: https://cointr.ee/brodierobertson =========Video Platforms========== 🎥 YouTube: https://www.youtube.com/channel/UCBq5p-xOla8xhnrbhu8AIAg =========Audio Release========= 🎵 RSS: https://anchor.fm/s/149fd51c/podcast/rss 🎵 Apple Podcast:https://podcasts.apple.com/us/podcast/tech-over-tea/id1501727953 🎵 Spotify: https://open.spotify.com/show/3IfFpfzlLo7OPsEnl4gbdM 🎵 Google Podcast: https://www.google.com/podcasts?feed=aHR0cHM6Ly9hbmNob3IuZm0vcy8xNDlmZDUxYy9wb2RjYXN0L3Jzcw== 🎵 Anchor: https://anchor.fm/tech-over-tea ==========Social Media========== 🎤 Discord:https://discord.gg/PkMRVn9 🐦 Twitter: https://twitter.com/TechOverTeaShow 📷 Instagram: https://www.instagram.com/techovertea/ 🌐 Mastodon:https://mastodon.social/web/accounts/1093345 ==========Credits========== 🎨 Channel Art: All my art has was created by Supercozman https://twitter.com/Supercozman https://www.instagram.com/supercozman_draws/ DISCLOSURE: Wherever possible I use referral links, which means if you click one of the links in this video or description and make a purchase we may receive a small commission or other compensation.

Good morning, good day, and good evening. I'm, as always, your host, Brodie Robertson. And today, we have a returning guest who now no longer has a distro. Um, you're doing an install script instead. Uh, welcome back to the show. Introduce yourself for anyone who doesn't know you. Well, I am known by many names, the man with many names. Uh, Tech Zero, Dark Zero, Steve, for the simple people. I'd rather go by Steve because the others are just fluff. And yes, as you mentioned,

the distro is gone. Everything has a shelf life, basically. And my distro had a three-year run with two years just for me, so five years total. It was a good run, but it was time to put it on the shelf and put my expertise where it counts, where it matters by contributing upstream to Arch whenever I can. So now I am in contact with higher ups at Arch from time to time, and I help maintain packages, and I do my script in my spare time. I put all the knowledge I gathered while maintaining zero Linux into a small little toolkit that people can run post install, which helps them get up and running real quick because most people want to be productive quickly. They don't want to waste time setting up their system. So I thought, okay, I had this GUI welcome tool in zero Linux. Why not get something more transparent, more akin to the way Arch likes to do things via the terminal,

because Arch is mostly terminal centric. So I was like, Yeah, okay. Oh, let me see what I can do. So I ported most of the my welcome tool into a CLI toolkit with the help of a person called Oglo. The front, he just helped me do the main menu in the front. It's written in Rust, because why not? But the rest of it is just Bash script that I gathered. And as I was working on it, the past two, three days, I created something a little bit special.

You know how you can use Arch install to install Arch now? Well, the developers now allow you to skip the profile section. You can skip it and just, it will default to the minimal profile, basically, if you skip it. So what my script does, I'm working on it still. Basically, you skip the profile and the additional packages sections. You wait for it to install the basic packages. Then when it asks you to cheroot, you say yes, and then you paste the curl command. And we're going to talk about the curl command because i know how you don't like people copying and pasting curl commands in terminal but before we get there they just paste the curl command i created it runs it executes a script which will install

kde plasma nvidia drivers enable the modules enable sddm enable all install and enable all necessary Bluetooth, cups, and all the necessary stuff. And then once it's done, you just reboot and you have a functional system. All you have to do is use my toolkit to install any extra, either from the AUR or Arch repositories or Flathub, wherever. And with this script, I fixed a lot of things that were wrong with Arch install. Because the thing that got me into creating my script was the fact that the way Arch install does profiles is kind of incomplete. I'm not going to blame them or say they're doing it wrong they're

not they're doing it the way they see fit each person does things the way they like but it didn't fit into my uh into my vision so i was like they're not installing the complete plasma they're missing spectacle they're missing dolphin add-ons they're missing. They're missing Spectacle, they're missing Dolphin add-ons, they're missing this, they're missing that. And I don't like installing meta packages, basically. So I created that KDE profile, my own custom KDE profile, that installed a more complete Plasma package. And yeah, it went from there. So I was thinking to myself, why not create multiple profiles? One for XFCE, one for Hyperland, one for whatever. So yeah, I'm working on that in my past time.

So I'm trying to talk to trucks from Arch Install. They are adamant to stick to the way they do things that's why we developers contribute upstream, we contribute we put scripts out there for people to use

I have a question for you why okay you do say it the correct way but sometimes it comes off Why? Okay, you do say it the correct way, but Sometimes it comes off as a little bit scary. Why not run curl commands? In terminal. Okay, so the problem isn't running curl commands in the terminal. The problem... Okay, so it boils down to one simple issue.

Obviously there is a separate thing where if someone is trying to do something malicious, obviously, you know, it's a problem. But let's assume that the script is running, like, it's a well-made script that is trying to do something good. The issue that can happen is if a download breaks in the middle of downloading that script,

you can be put in a position where you are executing a half-downloaded script. If that happens and you might have like, let's say you have a malformed RM command, for example, and it ends up deleting something that shouldn't be deleted, that is the main issue. The likelihood of this happening is fairly low. You would need to stop at a very, very specific point. But... It's one of those additional risks that i just don't think is i don't really think makes any sense to do when it could just be broken down

into separate commands and then that risk completely eliminated that is very true but scripts are so small these days it's impossible for them to break mid download unless somebody wrote a script that is a few hundred megabytes then i do agree with difficult but it's it again it's one of the things where it's it's very unlikely that it would happen but on the off chance that maybe i don't know there's some like the server itself has a slow connection or if the server's being hit really hard and downloads are much slower than they should be or your connection is having issues or any other number of things that can cause the download to slow down and then potentially break at a dangerous point that's the main reason that like i don't think it should be done there's the

whole separate thing again if the developer thing again, if the developer is malicious, but if the developer is malicious, you lost already trying to download the script. That's a whole separate thing. Yeah. And because of your countless times mentioning that, uh, that issue, I added a link to my website. It's called Inspect Code. It's just a little thing up top of the website on zerolinux.xyz. It says Inspect Code. They click that link, and it will take them straight to the script, and they can read the script and study it,

see what it does. And I added a nice little quote that I sent you as a DM that ChatGPT generated. Oh, that one, yeah, yeah. Why did the Arch Linux user adopt KDE Plasma? Because they wanted their desktop environment

to crash in style. Well, I'm having a look at the script now, and there's nothing here that could be dangerous, really. There's things where it's slightly inconvenient, like maybe you'll end up... The worst that could happen here is you run the script, and the script breaks halfway through it.

That seems to be the worst thing that could happen. Yeah, it will just not either add the repository, and you end up with the toolkit not being installed and stuff like that, but nothing too malicious. Actually, I guess you could possibly... Maybe the sed command could break and cause something bad to happen. That's probably the worst thing.

It edits the pacman.conf. Yeah, that's the worst thing. It edits the pacman.conf. Yeah, that's the worst thing I'm seeing, but even then I... Yeah, actually, I'm struggling to think of a way that a set command could break that would cause damage, because it would just error out. Nothing would cause damage. That's why, when I created the

script, I had your voice in my head saying, don't run curl commands if I break. Your voice is very powerful, my friend. I don't think so. at my break your voice is very powerful my friend I don't think so I just sit in my room some of the things you say do stick in my head because

your videos are super informational and they don't beat around the bush they're straight to the subject and they do help all the information you mention in your videos They don't beat around the bush. They're straight to the subject. And they do help. All the information you mentioned in your videos stays with me. Because me as an up-and-coming developer, because we all started small. And by small, I started with Bash.

And I'm sticking to Bash until I learn other things. I'm moving to Python because Arch install is in Python. So I need to learn that. But all the information you put in your videos, it stays with me. It helps me while I'm working. And I do go back to some of your videos, especially the one you did with David Edmondson videos, especially the one you did with David Edmondson about KDE, because, hey, I am one of the, if not the biggest KDE shill around. And I do talk to Nico. I do talk to some people up at KDE. I do report upstream.

Sometimes I don't get a response. I'm patient. I don't get a response. I'm patient. I learned patience while using Linux. I learned something I never thought I would ever learn. Patience. Because I do understand they got millions of other bug reports to go through. Right, right.

Mine is not the most important one, especially that it's related to network manager. But other than that, I do contribute upstream. I talk to people on GitHub. I'm using the time I gained by no longer maintaining a distro to report bugs upstream. I no longer use AUR to report bugs. upstream. I no longer use AUR to report bugs. I just go straight to source. My rice, for example, the infamous zero Linux rice is still there. It's part of my toolkit, but instead of installing the themes from the AUR, which shouldn't be done ever, and regarding the issue that that person had with a theme that deleted their home directory, I don't go to pling. I don't go to store.kde.org. I just grab everything from source, even the widgets. So that was something that I would add to your video.

So if you want to get widgets, Plasma widgets, if you want to get Plasma themes, global themes, whatever, be safe, grab them from source. And make sure you're grabbing the right version for the version of the desktop environment you're using. Because I had a person report issues. He had a lot of Qt 5 apps on their Plasma 6 system. They installed the theme from store.kde.org, but it was a Plasma 6 theme. So

Qt 5 applications were not being themed. So be careful don't just make sure you you are using the right versions of every application and the themes before you apply right anything from kde plasma store because plasma store is a wild wild west kind of like the aur yeah yeah i think the difference with the two of them though is people are under the assumption that things on the AUR could be a problem where they weren't under that assumption with the KDE store and especially with global themes. Like there are a lot of people in my comment section who are like, it's a theme, how does it have code running?

It's a theme, code running, that seems like a bug. Where internally, like that's the way it was designed to work. And it's always been known to work like that if you're a developer on the project. But they just, they never communicated that properly. And users were under this complete false assumption of what a global theme was actually capable of. And the way that global themes actually worked. Yeah, and there's the fact that, I don't know if David Edmondson mentioned it,

I watched it a week ago, but the fact that they moved away from themes having a metadata.desktop to metadata.json. I don't think he mentioned that, no now they use JSON files instead of desktop files, that's why global themes have to

update their code and the Plasma developers did push out a guide on how to port their Plasma 5 code to Plasma 6 months and months before I guess nobody got the memo very few people got the memo

so for example the lay-in theme that the Zero Linux Rice uses there's someone on GitHub who mentioned another theme developer basically on GitHub who mentioned how to... Another theme developer basically just included a guide on how to convert the.desktop to.json. So I had to do it myself, fork the theme,

do the necessary to convert the desktop to JSON, and then grab from there. So yeah, a lot of themes need to update. Plasmoids use a lot of JavaScript and JSON and stuff like that. So to add to what you said, plasmoids and global themes have code. Mm-hmm. Plasmoids especially. They're not just... Plasmoids.

Like, anyone who thought that plasmoid didn't, yeah, that like... Yeah. But obviously global themes, because global themes, they're not just Plasmoids. Anyone who thought that Plasmoid didn't... Yeah, like... Yeah. But obviously Global Themes, because Global Themes, they're not... Well, Global Themes are more like a meta package. That's what they really are. Because they include KDE theme, Plasma themes,

they include Icon themes, they also include, like, SDDM themes, which are... That's a whole other problem. They also include some Plasmoids, depending on the theme itself, and maybe KWIN scripts, depending on the theme itself, and maybe K-Win scripts, depending on the theme itself.

And it's very much not a theme. It is a meta... Maybe that's a better name. It's a meta package, basically. Yeah, Plasma Meta something or other. Maybe that works. I don't know. Speaking of SDDM,

you brought a very sensitive subject regarding sddm because since i have a testing vm i test everything in a vm before i apply to my main system but there were a few sddm themes that caused chaos. Not because they were incompatible with Plasma 6, because I made sure I was installing Plasma 6 versions. But what that broke was... You know how you have the quiet flag you set in Grub so you don't get the verbose code every time you reboot? Yeah.

Well, one of the SDDM themes was not respecting that quiet flag. I was getting a lot of verbose output every time I rebooted, shut down, or whatever, and it would hang. It would hang on SDDM something and I was able to access the root partition without root. Okay.

I mean, yeah, it was like, it would show, it would crash at the end and it would log you in as root for whatever reason maybe to troubleshoot maybe to whatever maybe that was a malicious code that i caught i don't know it just boom it landed me in in root and i could delete my root files and whatever. And I realized that this

included Plasma 5 code that wasn't properly ported to Plasma 6. So it would crash, and the only fallback for it was, for whatever reason, root. So I quickly deleted that theme. And

the guy has removed it from the KDE store since. But what the hell? STDM lands you in root and in a TTY. Not on the desktop, just in TTY root. If it did that, I can see if it did that and somebody didn't know what they were doing they would delete their route without even knowing so stdm is kind of dangerous because it's an elevated kind of element so well yeah be careful be careful on on, STDM runs as the STDM user. It doesn't always run as the STDM user.

There are other distros where it will just run as root, and then that's where you get the problems. I guess I was on Arch, so Arch behaves a little bit wonky. Arch probably just runs it as root. I'm not certain. I have STDM installed. I don't like login screens. I just boot up from the TTY,

so we've always done it. Well, yeah. So this is just me saying that you are absolutely correct. People need to be careful what they're installing. And I do agree to the point where you said

during your discussion with david that they need to move uh the store away from their kde domain yeah yeah i don't know where it would be i don't know where it should go i think like i think kde look would be fine if they put on something like that or if if they do keep it on the domain do what the aur does where there's a big disclaimer like in bold text it's the first thing you see this is unofficial like use with caution or whatever it says yeah use at your own risk just keep it and and i do also agree with the the thing you said, where it shouldn't be too wordy. Because not a lot of people like to read.

From my personal experience, even two sentences that I put on the website, still people don't read them. And they say, hey, I'm having issues running your script. I'm like, did you read? Why did you run the curl command seven times? Now you have seven instances of my repository. It just tells you in two sentences, run it from the app menu.

What's not to understand? Oh, we missed that. Oh, you don't like to read. I get it. That's why I made the video. Right. Well, how many people have you had asking you about like where zero Linux has gone? And like, how do I download zero linux where can i get

it after everything everything's all changed i still get those questions to this day i tried to download zero linux but i can't find it i'm like it's gone it's it's a script now come on people didn't you get the memo no they were like were like, oh, we must have missed it. But I did mention it multiple times on Mastodon. I mentioned it. I made a video about it. I made sure everybody was informed. But apparently, yeah, people miss a lot of things. So I'm used to it.

If they ask me the question, here's a link to the video, that'll explain everything. That's the reason I made the video. But yeah, moving towards better things is a good thing. But I'm really happy now since I am the KDE person because more and more distros are adopting KDE as their main thing, just like Fedora is planning to do. Well, it's being discussed.

It's not planning right now. I was talking to Josh before. They're having some meetings about it. They're going to bring it to the working group. It's not being blocked. That's the important thing. It's not being blocked, and's the important thing. It's not being blocked and they haven't recalled the change proposal, so

They're still very much in the discussion phase and things might happen. I wouldn't hold my breath, but If anything does happen, it'll probably end up being promoted like as a as like a dual What do you call like a dual flagship? We have the option of either GNOME or KDE. Well, I agree with the idea of dual because GNOME being, as I told you earlier, GNOME being downgraded to a spin is not a good idea. Yeah. It would be wrong

because GNOME, the way they do things is they target professional professionals first and gamers and casual users second not so where whereas kde it's the opposite it's tinkerers geeks customizers first and then professional, it kind of blends in, but not really. So if they want to adopt KDE Plasma, it would be great. It'll make me happy.

Maybe I'd switch to Fedora. But the KDE spin of Fedora needs to get more attention, and in order for it to get that, it needs to be promoted kind of to kind of a flagship. So if it's next to GNOME so users can choose which workstation they want, it's a better idea. I'm 100% on board if they put it alongside gnome so users or maybe in the installer like somebody like you while you were scrolling uh and on your video there was a guy who was uh who mentioned we could have in the last

comment i think uh that was on the thread the guy was saying what if anaconda had two options either ade or gnome whatever the user selects will they will end up with there is some work getting that done um because like fedora kde isn't just fedora with kde there are some different things they do alongside that change so it's not just a matter of changing out that package but there is work in progress to get that done and there are other distros like um open susa that do make it that easy where in the installer it's just like you want to use kde you want to use gnome i think they might offer like xsc and a couple others and you just click the one you want and then it just installs it for you that probably is the that

probably is the best way to do it but also well i think if they're not going to do that just have both options there on the home page that like that's the quickest thing to do that's the quickest thing to do and if they want to if they decide to go on the iso rod the fedora server allows you to do that if you download the fedora server iso it's i think five gigabytes or something it's it includes multiple desktop environments if you wish to install but i think it installs them it calls them uh from online it doesn't include all the packages on the iso yeah yeah or otherwise the same thing with the um the fedora meteorite as well. Yeah. So whichever route they choose to take, as long as they keep GNOME and KDE side by side,

I'm 100% with that. But definitely it would make me happy because I don't think I'm going to switch desktop environments because since I have nothing to do, I've been testing various desktop environments on my laptop and various distros. I tried

Linux Mint Debian Edition. That was boring because it's stable. And for a geek like me who likes to tinker, stable is not the right way to go but i do recommend it for new users definitely because it's so solid i the only way to break it

because there's always a way to break the unbreakable as i will mention in a bit but the only way to break it is by messing with kernels. Sure, yeah. If you install a Bleeding Edge kernel, then definitely you're going to break it. Right, right, right. But I played with Linux Mint Debian Edition. I played with Rawhide. I stayed on Fedora Rawhide for a month. What can I say about Rawhide?

It's more Bleeding Edge than Arch will ever be because that's for developers yeah yeah art i like people saying arch is like a bleeding edge distro no no it barely is cutting edge half the time i don't know if you um yep i i every so often talk to vaxxery about hyperland and prior to the current version, I think I think we were waiting about two months to get the package. There were like two big versions in between before Hyperland got made.

Which brings me to a good transition. Hyperland. Yes. Okay, since you talk to Vaxxery a lot, what does he think about

ArchInstall's Hyperland profile? I've not asked him about it, actually. Because when I checked the Hyperland profile on ArchInstall, it barely installs anything to get you up and running. It doesn't do, even if you select,

and here's my nitpick with Arch install. For us NVIDIA users. Before you go into that, for anyone who doesn't know what Arch install, just give a brief explanation of that. Okay, Arch install is a script that makes it easy to install Arch. It's written in Python. It makes it easy to install Arch. It's written in Python.

It makes it easy to select which drive you want to install Arch on. It allows you to select packages, any additional packages you want. And they have profiles, desktop profiles, window manager profiles, which they need to separate. Because when you select desktop, you've got desktop and window managers. They need to separate the two. because when you select desktop, you've got desktop and window managers. They need to separate the two. But you just select the desktop environment or window manager you want to install,

and it will take care of the rest, basically. It does everything that you don't want to bother with, like the Arch install guide on the wiki. Yeah, basically just automates the Arch install guide, effectively. Yeah, it automates the Arch install guide, effectively. Yeah, it automates the Arch install guide. That's why it's called Arch install. And it's very minimal. It's just a Python script. Very minimal.

Yeah, it occupies barely a few megabytes on the ISO. Well, also minimal in just what it does. Like, that's the other... That sort of goes into the profile thing. I went through it last night because I did into the profile thing i went through it last night because i did a fresh install i went through it last night in 30 seconds yeah yeah it gets you basically everything in the install guide that's it's not going to do anything more than that

actually well the advanced mode does have a couple other things like you can enable um oh can't you enable like multi-level something in the Advanced mode? There's a couple of extra things No, advanced Advanced mode adds two things Okay One of them being Very good, parallel downloads I don't know why that's not just the default way Pac-Man works

That, I don't understand Yeah The other one, it's going to make you laugh so hard you're going to cough up a kidney. Mm-hmm. They allow you to select NTFS for the root partition. Let that sink in a little bit. Let that sink in.

For the root partition. Not the boot partition, the root partition. The root partition. NTFS. That doesn't work with Linux. Well, no, you can do it. How are they included in that? You can do it.

It doesn't have the correct permissions. It doesn't use permission system. I tried it. It fails. You end up in the TTY. The system will not boot. Well, no, you can do it it it might just be set up completely wrong you shouldn't do it i don't know how if you if you if you add the dash dash advance and you go

to the drive selection and when when it asks you what format that you want your file system in the last choice is ntfs so maybe they don't even do they install the ntfs driver because that also could be the problem i don't know i didn't check that deep because i thought that option was a little bit hilarious and we tried it we tried it in a vm. We selected NTFS. We went through the install. The install goes fine-ish. It complains about the permissions because everything is, when you select NTFS, everything is set to 777 permission. The way NTFS does. Anyway, yeah, it's got some weird quirks.

Arch install is not perfect, but this is my nitpick with Arch install when it comes to Hyperland and the NVIDIA drivers. For us mere little mortals who prefer NVIDIA for the NVENC encoder, they don't do the necessary for HyperLan to work correctly. Because for HyperLan to work correctly, since it runs on Wayland, you need the NVIDIA modules and MKInitCPIO and the mod probe and so on and so forth.

This is a little bit technical, but those are basically the required things for NVIDIA to run on Wayland. They don't do that. They don't install the 32-bit libraries. They don't install the full package stack for the driver. They just install three packages, NVIDIA-DKMS. At least they got that one right. And they install NVIDIA utils and NVIDIA settings. and they install NVIDIA utils and NVIDIA settings. That's it.

And even if you enable the multilib repository, it's not going to grab any of the 32-bit libraries. So basically, when you select Hyperland, you will end up on a login loop if you have an NVIDIA card, a login loop

because the Wayland stuff is not being applied. Right. So, I'm like, and the Hyperland profile only includes seven packages. Yeah, for anyone just listening, it's Hyperland Dunst, Kitty, Dolphin, Woffy,

uh, the Hyperland Portal, which is nice they include, QT5 Waylandland and Qt... Why do you include those? If you're going to include nothing, why do you include those? Qt5 Weyland and Qt6 Weyland. You need Qt6. You no longer need Qt5.

My point is, considering how few packages are installed here, why even bother to install those? Like, nothing you even still needs them yeah exactly and i i am i understand that hyperland is a meta package because meta packages are necessary for correct install but still it doesn't install everything that is required so basically when you select a package wait What do you mean Hyperland's a meta package? Not a meta package, sorry. It's got dependencies. It brings with it the correct dependencies.

Sure, sure, sure. Yeah. But it's not... So basically, what you end up with when you select the Hyperland profile is... Well, if it logs in

using Mesa, because M mesa does support wayland but just basic support you will end up on the desktop with the anime image the what the usual default wallpaper with the yellow bar on top telling you okay it's time to get to work you lazy app so basically they don't do anything yeah the uh i was looking at the sway config the sway config i think is like i don't know what they're doing with these profiles i feel like the profiles are kind of kind of pointless like i'm looking at the sway config the sway one has sway sway b, which is how you set the background. SwayLock, which is a lock screen.

SwayIdle, WayBar, Dmenu, not Woffy like the other one. I don't know why it uses Dmenu on Weyland anyway. BrightnessCTL, Grim, Slurp, PavuControl, which is a pulse audio thing. Foot, Xorg Weyland. control which is a pulse audio oh yeah foot x or Wayland wait the high plan what doesn't is still X X well it isn't so X Wayland what wait no no no I'm so good why does this package I'd okay for anyone any arch devs you might be listening can someone explain to me why these profiles exist like I think it's a good idea but why do they exist? Because in their current state,

they don't make any sense. There you go. Finally, you get to what my major nitpick is with profiles. That's why I created my own KDE one. Well, they've got a nice framework here for making. I saw, like, they've got, like, a Python API for making custom profiles, and I think for that it's great,

but, like, the default ones here are completely pointless. I saw they've got a Python API for making custom profiles, and I think for that it's great. But the default ones here are completely pointless. Completely. And here's the thing. For me, to be productive, for example, I need Dolphin plugins or Dolphin add-ons, whatever the package is called, because I maintain repositories.

And you know, when you're maintaining repositories, you need to know which files have changed that you need to push and which files haven't been touched. When you install the Dolphin add-ons, there's a green check mark for unmodified files and the orange exclamation mark for files that have been modified that need to be pushed upstream. Sure. That's a visual confirmation what you need to do. And that adds to my workflow, makes me work

much faster. Without those, I cannot function. That's the thing that got me ticked off. I was like, okay, you installed Dolphin, but where's the add-on? I need to install it myself. Regular users won't know about that. I put myself in the shoes of a regular user coming to KDE. If they select the profile in Arch install, you're going to get an incomplete experience. A totally incomplete experience. And watching your

KDE install video made me laugh so hard, I just wanted to jump off the balcony. But I knew who you were, and I knew you would figure things out eventually, but this is what regular users will do. But I knew who you were, and I knew you would figure things out eventually. But this is what regular users will do.

Regular users will just select the profile in Arch install, say, hey, those are developers. They know better, so we're going to trust them, and we're going to install KDE that way. And they're going to judge KDE by the profile that Arch install provided. So if KDE gets a little bit of flack, sometimes, not always,

it might stem from the fact that they installed it via the Arch install script, which is incomplete. Yep, yep, yep. I'm like... Here's my thought on Arch install right i think arch install they are it's weird right because it it's trying to make the arch installation process easier and i think that's good but i don't think they're going far enough for it to make sense i don't

think they need to have like a custom Hyperland config. I think doing that is way out of scope of what Arch Linux is. But I do think if you're going to be having a profile for like Plasma or a profile for Hyperland or... Actually, a good example is the Sway and the Hyperland profiles. Why is the Hyperland profile far less functional than the sway profile there is zero reason to ever install a whaling compositor and not install x whaling like that doesn't make any sense to me so they have these profiles here as a way to make it seem like there's an easy way to

install a desktop but then don't fully complete the profiles. So it just doesn't make sense to me what they're doing. Again, I said... They're targeting new users, because new users are not gonna... We just... We understood this. Everybody understood the fact that people will mostly refuse

to go through the archway of doing things, because it's too manual. Well, that's why things like Endeavor exist. Exactly. Or Arco, why things like Endeavor exist. Exactly. Or Arco, if you like Arco. And that's why Zero Linux existed. Because a lot of people didn't want to go through this convoluted way of reading the wiki,

copy-pasting commands left and right, having to SSH to be able to do it more freely by copy-pasting commands instead of having to type them all in. But that's a way of targeting new users. But then those new users are going to judge whatever they install by the way Arch installed that thing. So it's not fair to...

What I'm saying is it's not fair to judge anything if you installed it via Arch install. You need to get your hands dirty and do it yourself and build, because that, I am now, ever since I stopped maintaining zero Linux, I have become a real ambassador of Arch. Like if you want to build your system and know everything about your system from ground zero all the way to the way you want it, use Arch or use the likes of Gentoo or anything that

asks you to dig your hands into the system. That's why I love it. I love building Arch brick by brick because at least then, if I suffer any issues, I know where the issue comes from, because I installed that package. Therefore, I caused my system to break, not Arch. Sometimes, yeah, issues slip through the cracks,

through the Arch cracks. We've seen that with Grub cracks we've seen that with grub we've seen that with many things absolutely recent change to yeah yeah glipsy yeah yeah glipsy was the one of the biggest issues we've ever seen but they did redeem

themselves when the XZ issue showed up yeah that was really surprising. They weren't even affected. And they're like, here, problem. Okay. Is someone else writing this blog post? Like, what's going on here? Arch never says anything in a reasonable amount of time.

Especially when it's not... Like, if it doesn't affect their core installation, Arch never says anything. Like, it needs to be part of like a base for it to be something they want to talk about half the time. Yep. Actually I think in this case I think XZ might be in base but it just doesn't affect the um uh the install we have on Arch. They updated the ISO uh they released one on the 29th of March to include

the fix. And then they released one on the 1st of April. So, basically, they were on top of things. They were doing their job correctly. And I was really happy and surprised. And they updated the package.

Is it based? Yeah, it is. And now they released another update to unlink it from SSHD. So anyway, Arch was not linking it to libZMA, whatever it's called. Yeah, yeah. So so i'm like arch safe that's a surprise but yeah but yeah issues slipped through the cracks from time to time on arch and it's the nature of every single distro like issues slip through the cracks from time to time on Arch. And it's the nature of every single distro. Like, issues slip through the cracks with Fedora. Issues slip through the cracks in Manjaro. Yesterday, I was watching my good friend Air Max.

Kudos, Air Max. You're doing a great job. He encountered an issue where installing OBS from their repositories, because, oh, who knew? Montaro have OBS on the repositories. I didn't know that. But if you install OBS from their repositories, they include a driver, VDAPU, lib32-vdapu driver. If you install that, OBS will not launch. He caught it on stream. I reported it

directly upstream to Art, to Manjaro. They're going to fix it with the eventual release of Manjaro with Plasma 6, because they're still on Plasma 5. And guess what? Manjaro, for being rolling, they're still on the 6.6 LTS kernel.

What? I guess that's... If it's an LTS kernel, I guess that's fine. But their ISO is from December. Did everyone just take a break for the past five months? Yeah, it's a long break, but... Sure. And once you update the system

after installation, you will get a 2.5 gigabyte update. You're still on Plasma 6 and you're still on... At Plasma 5. ...Curl 6.7. Do you mean Plasma 5? Yeah, Plasma 5.

And... They are still on Plasma 5. They don't upgrade to Plasma 6 since they maintain their own packages. And the maximum kernel you're going to get that you'll have to manually upgrade to using their Manjaro settings is 6.7.

In their repositories, they still have 6.8 RC6. Look, I guess it's fine. Manjaro's doing the Manjaro thing, I guess. Yeah, but come on. And they have rolling on their website. They're just rolling

very slowly. Excuse me, but that's... They're rolling very slowly. They're dragging a truck behind them. They're going so slow. Manjaro's always been like that though, like, it's nothing new. But if it's stable, why complain? It just works. Minus OBS, forget about OBS, they're gonna ship a working version at some point. Look, maybe it's broken so they forced you to go run the flatpack

because then you can actually have a working version of the application. You shouldn't be running the native package anyway. Speaking of, since I'm suffering the NVENC issue on my OBS, having to go software, but

I had a discussion with the developers over at OBS Central on Discord. I had to ask the question because I wanted to have a clear answer to give to users once they asked me. I was like, which package format is the official package format for OBS? Flatpak. Come on, developers. Yes. Flatpak. Come on, developers. Yes. Another one.

Ubuntu's package. Ubuntu from the PPAs. Yes. I think that's all. I don't know. Those two packages. Yeah, that's all. Only those two packages are considered official by the OBS team.

Only those two packages are considered official by the OBS team. But they no longer have a GitHub repository for the Flatpak package. Now you go directly to their GitHub project. To the OBS project. So any issues you report there, they don't go through FlatHub. So in case you suffer any issues, you have to report over there. But I quickly learned that talking, reporting issues there,

you might get less than nice replies. Right. One of the developers replied to me, hey, if you don't know how to use linux why are you reporting issues like what what because he asked me something i never basically what happened was he asked me to do things that i never done before because it was never required sure Sure. Like, set the FB buffer to zero, set the psychedelic, post-psychedelic processing to disabled and do this and do that. I was like, yeah, if you point me where to change them,

I will, and I will post the correct log. I was like, okay, you don't know how to use Linux. Let someone else report it, basically. I'm like, what? Okay, sure. Thanks for that. But I'm still in discussion with Titan652. Everybody knows this person.

In case you don't, he maintains his own version of OBS package on the AUR, and it's a very complete package, but please don't try compiling that unless you want to go through the countless minutes, if not hours, depending on your system specs, compiling the Chromium software. The CES stuff is probably the worst part yeah it takes me on my 3600x

32 gigs of RAM it takes me two hours and a half wait what yeah uh I've got a similar system that takes me like 10 minutes 10 minutes 10 minutes?

maybe they fixed the package maybe there was something wrong with the package because back in the day when I used to compile it used to take 2 hours and a half and I was like what? maybe because it's my connection having to download large sums of libraries or whatever

I don't know but it used to take me two hours. Your compiling definitely shouldn't take that long. But downloading the source code could be an issue. Yeah, especially when they asked me to compile the flatback where it needed to pull in the entire FFmpeg source. Speaking of things that might take a bit to compile. Yeah, the entirety of of the thing the repository is around 700 megabytes give or take and then it has to compile all that and pull it i was like yeah it failed mid mid cloning the repository because my connection is only eight megabits down. Yeah. So, yeah, I was like, yeah, you guys need to figure something out.

But anyway, just a message I want to pass along to everyone watching this or listening to this. If you have an NVIDIA card and you want to use the flatback version of OBS and the NVENC encoder, it it's currently broken they don't know where the issue is coming from but so far they have narrowed it down to and you're using plasma maybe it's it works on other desktop environments i don't know i don't use anything else but It might be because of the KDE SDK 6.6. Right. So they narrowed it down to that,

but they're doing a lot of internal testing to figure things out. For now, it's broken. If you're a content creator and you rely on NVENC, use software rendering until the issue is taken care of. I'm an AMDd user so lucky you but yeah this is it's been plaguing me because when you use the cpu there will be a lot of audio hitches like small ones they're barely perceivable i get get them as well, but they're less... I noticed in the last few...

Yeah, in the latest few videos. Yeah, I don't... Like, I've had that for a while. I tend to cut them and re-record. That's just a flat... It's just like a flat issue with capturing with Pipewire. Like, there's no way to get around that. I've had a bunch of people tell me about that problem.

Yeah, I think it's Pipewire because recently they have released a lot of updates. They've been pushing update after update after update because there are some users complaining about a certain buzz in their audio that I'm having that issue right now. Recently, yeah um my speakers if i just don't have a uh if i don't have a audio track playing if it's just um silent they'll just start buzzing so that's fine yeah i i have that issue in the in the store downstairs um but

yeah pipewire has but they're working on it because if they weren't, they wouldn't have had so many updates. Here's my thought, right? The Pipewire developers remembered that software is supposed to be buggy, so they decided to inject some bugs because it's been great for like three years now. No problems at all, but they're like, Hey guys, there actually are problems here. Let's actually just... Let's pay attention to that. Like the one I was talking about earlier. The one I posted about over on Mastodon. I've not made the issue yet. But I've had this issue while streaming.

And I've replicated it when I'm not streaming as well. So it seems to just be flat out an issue. So I capture my console gameplay with capture card and then I use the pass-through to show that on my screen and also show in OBS because I don't like playing off of the OBS preview. So I have to swap the output on my main display over from like my desktop over to the gameplay capture. Over to like HDMI. So in OBS, I'm still capturing the desktop.

But I'm also capturing the video output from the capture card. So I've still got like a portal running there that's capturing the desktop. the video output from the capture card. So I've still got like a portal running there that's capturing the desktop. And if I change my volume level, all of my pipe wire outputs vanish. Pipe wire seg faults, and then it recovers.

And every time I change my volume level, it seg faults and then recovers. And it usually disconnects my microphone as well. So I need to re-add my microphone back into obs and yeah it's just a mess right now wait wait wait you're having the same issue as me uh like now obs doesn't even uh knows that my microphone is there because okay in case people don't know i'm from lebanon okay that's across the, way thousands and thousands of miles away from Brody here. But we have power outages constantly.

It's like part of life because it's been happening since the 80s. Since I'm an 80s kid, I got used to it. But every time the power goes and the generator kicks in, a microphone just disappears. Because it's a USB microphone, and the power and the UPSs that I'm using,

they're very cheapo-cheapo UPSs that are just a small box with batteries. I'm not using online UPSs, which people should use with auto-voltage regulation. Without that, you're going to suffer the issue I'm not using online UPSs, which people should use with auto voltage regulation. Without that, you're going to suffer the issue I'm suffering. The thing that happens is the power goes down, and when it comes back, it doesn't come back fully. Because we use 220 volts over here.

So it comes at 130 volts, and then it slowly goes back to normalize it. Right. But when it comes back so low, the UPS is not providing enough because it doesn't have any auto voltage regulation thing. It doesn't come back powerful enough to feed all the USB ports in the computer. So the 5 volts, because USB ports use 5 volts. So they're not getting the 5 volts because USB ports use 5 volts so they're not getting the 5 volts

they're getting maybe 2 2.5, 2.20 2.20 you don't want to send 2.20 to USB so basically the microphone doesn't have enough power to get recognized by the system.

So I have to unplug it, wait for the power to normalize, plug it back in. Every single time. Imagine that during recording of a video. You're talking to the camera, you're moving your hands, and suddenly you look at OBS and the audio is gone. Yeah. Okay. Well, my issue is not related to power outages, but yeah, it's very much a

similar style of issue uh luckily i can just change the output in obs i don't need to unplug anything um so i just swap from like my camera to my oh my my mic to my camera and then swap back and then it just recovers um that happens that happens to me also. The microphone does not go, but OBS, I have to go to audio settings, select default, and then hit OK. Then reopen settings, select the mic, hit OK, then it will see it again. Yeah. That happens too, but I have even more issues, especially when I'm connecting. What I'm using right now is my cell phone, my iPhone. So sometimes the Wi-Fi flickers a little bit, so I lose connection with a virtual camera.

A lot of issues, a lot of issues, but mostly when it comes to P pipe wire, it's buzzing noises. It's like when I'm watching a YouTube video and the volume changes on the microphone of the person talking. It does. And then it continues with the thing. So I'm like, OK, how am going to do the content creation with all these issues because i'm relying on content creation now to to make a living trying to at least by being consistent every friday every monday and friday there's a there's a video and at the end of the month there will be a live like tomorrow the it was supposed to be at the end of the month, it will be a live, like, tomorrow. It was supposed to be at the end of March, but since it was Easter, I had to postpone it.

Right. So, this Friday, tomorrow, I'll be going live and hoping for the best, crossing my fingers, where Pipefire will not give me shit and the power will not go. But it's always fun to see the lights go off for two minutes and then come back on during a live stream. But I deal with things as they come. That's what being a Linux contributor taught me or Linux user taught me. Patience. Because with Linux, you have to be patient, especially when you're using rolling distros like Arch, Gentoo, and so forth. You learn a lot of patience.

You learn to read. You learn to grasp a lot of information. And that's not a hit on custom-based distros. They do their thing their way. They have their own plans basically but for me as a ultimate Linux geek if I don't do things manually

myself I might as well go back to Windows sure, that's understandable I run Ash myself as well so like you know yeah and as Brody saw earlier before we started recording, I don't use any Windows. I use Windows 2000.

Well, there's a reason for that. It's in a VM, number one. Number two, there's a reason. It's because I'm an avid classic games collector. Right. And in order to play classic games, especially ones that run in DOS, you need an old version of Windows. And the best old version of Windows is Windows 2000. For me, at least.

It's very stable. And I recently got into the Star Wars and Star Trek classics, like Klingon Academy and stuff like that. So, yeah, I need a classic Windows to be able to run those. So might as well run Windows 2000. But I haven't used Windows in the past four years. I haven't even had the thought of going back to Windows because I've seen the nightmare

that Windows has become. But, in its own defense, they're doing WSL correctly. Yeah, I think WSL is really cool, yeah. You can now run Linux GUI apps on WSL. Yeah, they run through Wayland.

They run through Wayland, and they now include systemd. Okay, that's really cool. Yeah, so I'm like, well, at least Windows is giving Linux a shot more than we thought they would. least Windows is giving Linux a shot more than we thought they would. If you're on Windows and you want to try Linux out just to get your hands wet, you can with WSL.

Now it's a good excuse. We can use that. Yeah, but I wanted to just talk a little bit about the XZ thing that just happened. Yeah. We touched on it earlier a bit,

but it didn't affect a lot of people because most people use LTS releases. Yeah. For anyone who doesn't know, the XZ issue was, it had been in the package for about two months, issue was it had been in the package for about two months, but

none of those packages were shipping on stable releases. So, um, it was very, very close to shipping on Fedora 40. If it had lasted a couple more weeks, it would have been on Fedora 40. Um, and it could have been on

Ubuntu 24.04 as well if it lasted a bit longer. But, yeah, it got caught. So it was only on your rolling releases like Arch, Gen 2, Void had it. And on your unstable developer releases like Rawhide, Sid, things like that. I just watched a video last night that put me to sleep. It was a very, very in-depth video where they went through the infograph

you showed in yours. And they talked about... And the guy replicated the issue in a VM. He showed us the script running, backdoor running in a VM. The sandbox environment. It was really interesting. It takes his key and injects it on top of yours and makes it look like a valid key for

the developer to gain access to your system. And that's, and we need to put an asterisk here. It affected distributions that linked SSHD to lib, lib LZMA. We, yeah, because of a,

because of a custom patch made in OpenSSH. Yeah. That was the issue. It was specifically a custom patch, which I believe I know Debian Yeah, Debian

ships it, Red Hat ships it. I think Sousa also ships it. It was a fairly common patch, but Arch doesn't ship it because for the most part, Arch there's some cases where it's not like this, but for the most part, Arch ships whatever upstream gives. So in this case

they don't do it, so not a problem. And that affected distros that built via the tarball, not Source? Directly from Source? Yeah, well I still And that affected distros that built via the tarball, not Source. Directly from Source. Yeah, well, I still... I wouldn't recommend running the Source. I don't particularly like the approach that Arch has taken for dealing with the issue.

Because most other distros, like Debian, like Gentoo, they rolled back to an old version. Whereas Arch decided to build off of the Source, but stayed within the zone of issues. It's just Source doesn't have the activation command. So it's probably fine, but I don't think it's the best approach. I think what the other distros did was better.

The issue with Arch going back is if they did that, and Gentoo has this issue right now, where Gentoo rolled back even further. So Gentoo users now have to basically rebuild the entire system, and the Arch packages probably didn't want to rebuild every single package that was affected. Yeah, exactly. And the way Ubuntu did it, and they named their package because... probably didn't want to rebuild every single package that was affected yeah exactly and the way ubuntu did it and they named their package because the way their repository works their

update system works you have to increment the version by a higher version if you downgrade it it will not downgrade right yeah the fake downgrade they did yeah yeah the fake downgrade so they called it five six one but really uh plus really five four five so that way that's how they cheated the system basically their upgrade system by adding plus really five four five that was funny that was really funny when i saw that i was like oh okay well that's but it doesn't really matter what it's called, right? As long as they are getting away from the affected version. If they're going to do a downgrade, if they're going to do a fake downgrade

where the system gets tricked into thinking it's a downgrade, or if you're going to do what Arch did and just go to the source, something had to be done. You couldn't keep that on people's systems, that's for sure. Exactly. And Gentoo went back as far as 5.4.3. something had to be done. You couldn't keep that on people's systems, that's for sure. Exactly, and Gentoo went back as far as 5.4.3. Yeah, that's why there's some

world issues. Yeah, so each distro does things their own way, weird as they might be, but as long as the issue is no longer there, we're safe. But we're aware of it and we don't really know. We're still digging into it.

Yeah, we know that the SSH issue has been dealt with. We don't know the full extent of what the target was and the full extent of what the backdoor was running. We know it was messing with SSH keys, but it's still being examined. I think so far that's the only issue that has been found. Not only that, but Firmware Updater

by Gnome was updated to use ZSTD instead of XZ. So a lot of packages are now moving away from XZ. Yeah, when I did my video on the situation, I had the number 151 dependencies on Arch. By the time I did my video, it was 145.

Yeah, they're slowly moving away, and since Arch uses ZSTD by default, they need to switch everything to... But that brings me to the subject of the poor main developer just lost his project. Not the co-maintainer. The co-maintainer is the person who injected the code. We're not going to go into judging here. But the fact that the main developer who is still recovering from burnout just had this thrusted on his shoulders. Now he doesn't know what to do, and he's slowly losing ground because more and more packages are shifting

to a different dependency. So I feel for the guy. I feel for the guy. I'm like, he has been relying on this person to help him maintain the package all this time, only for to get stabbed in the back. So,

things happen. Things happen. Like, many weirder things have happened, like in the Ferdy days. Thanks to your video. Man, Ferdy was such a ridiculous situation that debt for anyone I don't even know the full

details anymore it was so dumb because they like went on some psycho rant as well and like they were just randomly spending money on things like I got a donation from them at some point it was like a hundred dollar donation from like what are you doing with this money yeah but in the end it

it ended on on a darker note where he committed suicide i didn't hear that oh yeah so he took a dark turn quickly. But yeah, like I said, stranger things have happened. So don't be surprised. And I want to tackle a subject now with you that is very near and dear to my heart. And it should be to you too. Stemming from the XZ situation the

fact that people think that automatically by using Linux they're immune to such things this is the wrong thing to think. Like, macOS is not immune. Windows definitely is not immune.

Nor is Linux. Linux as an operating system is secure. Linux as an operating system is secure. But it is only as secure as the things you put on it. Right. So do not think that you are safe from viruses. When they tell you, oh, Linux is safe from viruses. No, that ain't true.

Just as we just saw with XZ. If you're targeted, you're targeted. No matter what operating system you're running. It ain't true. Just as we just saw with XZ. If you're targeted, you're targeted, no matter what operating system you're running. It doesn't matter. If the malicious actor wants to do malicious things to your system, they will. They will find vulnerabilities here and there. And specifically in Linux, it's going to be easier

because of the open source nature of it. Because they have access to the entire code. They know what to target, where to target, and when to target. So yeah, this Linux is more secure, yes, as an operating system it is. It's, as I said, as secure as the things you put on it. If you don't read the PKG builds of AUR packages and you just willy-nilly install them just like that

because you want the package and suffer problems, well, there's only one person to blame, not the developer, because that was their intent from the beginning. It's you who didn't read the package build. You didn't take the time to scan the code. That's why on my website, I included a button that will allow you

to inspect my script before you run it to have a peace of mind. That's why the PKG builds exist. I think a lot of people just don't want to take responsibility for anything they do. There's this idea like, oh, well, I didn't know, I, like, it's the developer's fault for doing it.

And yeah, like, if a developer ships something that is malicious, absolutely the developer is wrong for doing that. But at the end of the day, you are the only person out there that is going to be able to keep your system safe. Like, there are people out there who are going to do something malicious.

And that's bad and those people should be dealt with but before they get dealt with it's your job to make sure you don't deal with them exactly exactly so if you don't want to deal with such things look at what happened with ubuntu for example and Snap and all these malicious crypto mining. Look at that. Ubuntu, the distro that's most commonly used by Linux beginners, and they use crypto wallets and what have you. That's click okay so it's ubuntu it's it's got a certain amount of backing from microsoft it's it's this big thing they're not gonna ship me malicious code so i'm gonna blindly trust everything they ship in their in their snap store guess what

as as recent times have proved that yeah even even they aren't safe well the the snap case was just insane the fact that they were running an app store with zero human verification like that is wild how they got away with doing that for so long and it's not they got away with doing that for so long. And it's not that they got away with doing it. They got called out for doing it back in October last year and then just kept doing it. Like they had the exact same situation happen last year.

And I do agree when you said that the KDE response was better than Plasma's response when it came to such issues where they took it upon themselves. There's response when it came to such issues where they took it upon themselves to do something about it. Canonical has taken some responsibility for it. Very minor.

But they didn't do so until they got called out for it and it took them like a week to do anything. Whereas the Plasma devs, the day the global theme thing happened, there was a post out. Like, David Edmondson was talking about it, other KDE developers were like, yeah, okay, this is a problem,

and they were working on it straight away, like, very clearly working on it. Maybe Canonical was doing things internally that we didn't know about, but nothing was being said, and it took a really long time to get any sort of response about it. The issue with that is, since Ubuntu, or Canonical's Ubuntu, is such a major distro, they needed to be more vocal about it.

All they said is like one, it wasn't even official, they had an official announcement eventually, but initially it was like a comment on another thread. And it was just a post on the forum. Like it's not a big news announcement or anything. It was a very, very minor thing. Yeah. So I was like, if it happened to Ubuntu, then definitely it's going to happen to rolling releases and stuff like arch and gen 2 i was like and then we saw the thing happen with kde plasma i was like there we go since and that's what scares me the higher the adoption is for linux the more targeted it gets by malicious actors. Yes.

That's why when people start saying, this year is the year of the Linux, I'm like, you know what's gonna come when it becomes the year of the Linux? You're gonna get attacked, targeted, more and more. I think before anything gets too big,

we need to have people putting systems in place to deal with problems. Like Flathub, for example. Flathub does human verification. They do human verification for both uploading a package and also getting a package verified. So you can't do...

Like with the verification system, basically it's either putting a token onto your website or linking the source repo. Someone checks that. So you can't just go and upload a flat pack and then claim that you're the like developer of upstream they will check what you're trying to connect to and say okay well is this actually the correct thing yes get verified no piss off big example of that steam and the whole situation with the steam flatback where the valve developers are like don't install the flatback please i won't know the flatpack is

the least problematic it's the snap that's a lot worse the snap is a lot worse i'm not saying it's the worst but the situation with steam on flat hub needs to be dealt with. They need to remove the verified badge from it. Is it verified on Flathub? It is verified. No, it's verified on Snap. It's verified on Flathub as well. But

they don't write Valve next to the checkmark. They check verified by Flathub. No, it's marked as unverified right now. Oh, they updated it. Okay, so they fixed the issue. They must have updated the issue

when they started putting the unverified. Maybe. But before then, because I in my toolkit there's an option called game launchers, where users an option called Game Launchers where users can select whatever game launchers they want to install.

I didn't opt for the flatback version of Steam because it had the faulty checkmark next to it. So I think because of your video and other people's videos, they saw the issue and they rectified it.

They had the checkmark and people were complainingified it they had the checkmark and people were complaining why did it have the checkmark when it's not by Valve I don't even remember talking about that maybe it wasn't you maybe it was someone else but a lot of people complained about hey it's a false positive

we cannot trust this thing and that but now that they put the unverified It's much more clearer because even valve complained about it. I were like No, this is not the way if Steve was meant to be shipped not the only official package for steam Surprisingly enough is the dead package. Yeah. Well well yeah because that's the only official one well they started shipping uh linux for steam not that long before the original steam machines and the original steam machines were debian based yeah and also obviously ubuntu is debian based as well yeah so naturally it's a depth package

they do mention in their article on on valve's website they do mention if you want to download steam figure out a way to either install it from source or install the depth package those are the only two ways to install considering that considering that the steam deck is arch based i really wish they just either got the flat pack dealt with or released an official arch package i think that would be the first big project that had an official arch package that's another cab thing i don't understand on on arch you have two packages. You got Steam and Steam Native Runtime. So which one is to be trusted more than which? Well, the Runtime is the Runtime, not the actual client.

When you install the Native-Runtime, it installs the native client. And it installs the native client, and it installs the runtime library. Steam is optional as a dependency by the looks of it. On Arch, they make it a dependency. Yeah, it's marked as... Oh, sorry, no, I'm reading it wrong. I know I'm stupid. No, okay. Steam is required by the runtime.

Yeah, okay, no, you are right. I'm reading that completely wrong. Yeah. So which one do you install? So basically in my toolkit, I wasn't sure, so I just made my toolkit install Steam, and it works. I have Steam. I've never installed it. I just install Steam.

Yeah. It doesn't ask you what runtime do you want, what this, what that. It just installs the client, and you're up and running, and you don't need to deal with all that shenanigans. Why does the other one exist? So which one will the user trust more? It's weird. It's a weird situation that I don't understand.

Well, the native runtime is installing the Steam libraries. Yeah, and it asks you which ones you want for NVIDIA, AMD, Intel, etc, etc, etc. I did. It's been so long since I've installed Steam. I installed it like three years ago, and I've never uninstalled it, so.

Well, here's the situation. When you install just a regular Steam package It will install You launch it, it works Sure When you install the native-runtime It will ask you which runtimes do you want

If you have an Intel card You select the Intel one If you have the AMD card You select the VAMD, whatever If you have NVIDIA, the NVIDIA libraries, and so on and so forth. What's the difference?

If I install the regular one, it just works. And if I install the native runtime, it's going to ask me all these questions for a new user. They're not going to know what to answer. I think most people probably just install Steam and not even think about it. Yeah, that's what I opted for in my toolkit. Yeah, I didn't even know there was that distinction.

Because I've only ever installed the Steam package itself. Yeah, maybe that's why Valve is like, use the dev or source, fuck everything up. Basically. Well, in the case of Steam, there isn't source. There is no source package for it. Well, that's the idea. I'm just saying that's it yeah so like okay it's like the situation with uh obs either install the flatback or install the dev file don't install anything uh don't install anything else same thing with bottles ship uh ship the flap flatback package don't install anything else. Same thing with bottles.

Ship the Flatpak package, don't trust anything else. I know there was a discussion of maybe doing an app image at some point, but yeah, right now, just Flatpak. But you notice that this kind of thing is happening over and over and over and over again. Yeah, it's getting a lot more common, yeah.

It's becoming a lot more common, so, but yet more confusing for the end user. Sure. Extension. Because they now don't know which package to trust. Some people say trust this, other people say trust that. Everybody wants to protect their own package manager, basically. I think we need to stop that.

And people keep yelling at me, why are you using Flatpaks? Why are you using Snaps? Why are you using this? Why are you using that? I trust what the main developers say. They created the package. They know what they are shipping.

So if they tell you not to use a certain package manager's version, don't use it. Because there's a lot of streamers, content creators out there that just install OBS from, for example, from the Arch repositories. And they complain,

oh, I don't have that plugin. I have to manually install this and I have to manually... Did you know that if you install OBS from Flathub, there's only, I think, Mint who does that, but everybody else, they're not doing it. They're not putting the plugins,

the OBS plugins on Flathub on their GUI stores. If you go on the GNOME software center, you look up OBS plugins, you're not going to see any you go to pamac manjaro you search up obs plugin you're not going to see any unless they package it from the aur for the native package that's a different story i'm talking about the flat plugins they don't show you anything. Only Mint in their store will they show you.

I do everything from the CLI anyway, so I've never even noticed that. That's weird. Not everyone is comfortable with the CLI. That's another problem. When I'm looking for a plugin, usually what I do is I go to the plugin's repo, and the repo will usually tell me how to install it.

They need to put forth the links to the GitHub. To be fair, I don't think I have any plugins installed right now. I'm not a big OBS plugin guy. Well, the way I did it in my toolkit is I created a meta package, sort of a meta package, but basically it's install this, this, this, this, this, this, this, this, this, this, this, basically all of them. So I added OBS and all the plugins that exist on Flathub. And then users are free to uninstall the ones they don't want to. Right, right, right. But yeah, there's at least 36 plugins currently on flat hub so when they install obs using my

toolkit they're gonna get get a complete vs experience they're gonna have the game capture with the obs vlk capture they're gonna get all the background removal plugins, the pipe wire plugins. And finally, and this is good news to a lot of content creators out there, now you can capture per application audio. It included that plugin for OBS. It's part of OBS. There are ways you could already do it, but you need to make it jack lines and stuff. But now it's as simple as just adding it's right there application audio capture pipe wire

okay it's right there that's good it's been it's been in the works for the past four years so finally we can now capture per application audio. And I do that for tomorrow. I will be doing that for tomorrow's live or I'll be capturing, I don't know if it's copyright infringement, but Spotify's audio. Because I'm using Heller. Heller's audio, he creates DMCA-free music.

So I wouldn't be wrong. And I don't have ads because I have a premium account. So I'll be capturing Spotify. I just don't want to bother adding each audio track separately. I just run, capture Spotify's audio. You wouldn't be the only person who streams like that. Like massive streamers do the same thing yeah so at least we can now do that thanks to a plugin thanks to uh obs developers

finally embedding it in obs after four years of people complaining that the plugin no longer has a binary i just looked at my OBS version. It looks like I haven't updated my flat pack in a while. I am a whole major version behind. You're on 30.0? Yeah. Oh, shit.

I should update, yeah. I'll do that afterwards. You are on AMD. You shouldn't suffer a lot of issues. Oh, no, it's fine, yeah. But for us NVIDIA users, we need, because you know how NVIDIA drivers are flatback drivers. I'm not talking about the system drivers, the binaries.

I'm talking about the flatback drivers. They get updated, but if VS is not updated along with them, it will cease to launch. That actually can happen with the AMD drivers. The range seems to be a lot bigger but I have had issues where it just forgets my AMD drivers exist. I can launch it but when I start to record it's like missing encoder or something like that. Yeah So we content creators rely on flatbacks, on OBS so much. A minor hiccup, well, at least it sends me into a young boy's tantrum.

I throw a fit and I'm like, oh shit, OBS is not working. There goes my day. There goes, I. There goes... I'm not making thousands of dollars on YouTube, so I shouldn't care that much. I barely make seven bucks. So I'm like,

yeah, you shouldn't throw a tantrum. But it gets that way sometimes with OBS because we rely on it so much. Yeah. Well, I was in the middle of... When I found the issue I was talking about earlier, I just Well, I was in the middle of... But anyway... When I found the issue I was talking about earlier, I just basically stopped my stream

in the middle of it and I started just bringing up the systemd logs for Pipewire. Like, you know what? We're going to debug this right now on stream. I'm going to work it out and we'll report it afterwards.

Yeah, which brings me to a question. When are we going to see you do all the mistakes on stream what do you mean you you you you posted about it on mastodon we're like should i record all my errors and all my mistakes and leave them up oh yeah record a um record a video and just don't edit anything i know i'll i might upload that for like next, record a video and just don't edit anything. I don't know, I might upload that for, like, next April Fool's or something, I don't know.

I'll do it at some point, it'll have to be, like, a one-off thing. Because when I record a video, it takes me about an hour. I am really bad at speaking. Takes you only an hour? I've, look, I've spent three years doing this, so I've got some ability to talk a little bit, but... It takes me... I also note things out beforehand, so I have an idea of what I'm going to say.

It's just I am terrible at reading things when I'm talking. You're not the only one. People did recommend me to do highlights and to know what i'm talking what i need yeah i wouldn't say go full script but just like have a general no no just highlights yeah just highlights just bullet yeah i did that i said more ahs and ums than i ever did right right it's something you got to get used to yeah i i can never i could never read a bullet point and then turn back to the camera and talk i'm like okay i need to talk about that i start talking about it and then i lose my trail of thought immediately because in my head i need to get to the next bullet point and the next one and the next one and the next one

right again this is give up all that this is something i've spent multiple years getting better at when i first started doing it it was a mess i was very much the same way but now that i've done that for don't ask me how many videos it's something i'm a lot more used to doing now and i still you can still like tell when I'm looking at one or the other, but my flow is a lot less jumpy. It's a lot better because it keeps me hooked from beginning to end. I never skip through your video. I never skip through your videos. So my videos have gotten more scripted as I've gotten further, but a lot of the things you hear are very much off the cuff.

I will see what's written there. So I usually do all of the planning one day and then do the recording another day. So I will read what I've got written there, and I think, I don't know what the hell you are talking about. Why did you write that? And then I just basically update it as I go. Yeah.

So, and for me, I can't do that. I just go off the cuff and I forget, like, do you think that the tendency of putting a saying that click, like the video subscribe, if you're not subscribed,

do we need to say that? Just show it on screen. And yeah, I do an overlay that shows it um i don't i don't know i don't know like the youtube meta is always a weird thing people it was like when i when i first started doing videos everybody was saying that at the time so i need to stop saying that because as soon as i say it i lose my trail of thought and I have a lot of, but now I got better at it. I just, instead of saying ahs and ahms, I just put silence. And I, it's like a, it's like a cue for me to cut. Right.

Remove that part and say the thing. And I do mention at the end that because I need support, financial support, I tell the people if you want to join or you can support me on. Like you do say at the end, if you want to join those beautiful people. Yeah, it's kind of like that. But as content creators, we need to keep people up to date that we do this for free. But it doesn't mean that we can date that we do this for free but it doesn't mean that we can continue if it's always for free

so yeah content creation is fun it can be cumbersome at times because you need to know what to say when to say I'll eventually get the rhythm back because I haven't been doing youtube

for a whole year tomorrow i'm gonna do this live thing it's going to be the only live i'm going to do alone because talking to the camera and answering chat is kind of weird to me i like to have another person to bounce ideas off of yeah fair yeah fair. So we'll see where that goes with time. But it's a single live every month, so it's not a lot. But yeah, but there's one thing I want to say is Linux is a lifesaver. Because for people like me who have not a lot to do if they work short jobs, like they have maybe six hours a week or whatever, Linux will keep you occupied. Windows, not so much. Mac OS, even less.

So if you want to occupy and learn in the process, Linux is the way to go. It's not because it's safer, because as we saw recently, it's not. It's just because it keeps you learning on your toes, and who knows? Maybe you can create a career out of it.

Because there is a career in Linux, contrary to what people think. People think because it's free and open source that there's no way to make money out of it. No, there is. You can create a script, put your project behind the correct license, make money out of it.

It doesn't mean that you cannot make money. Look at, what's it called, Ubuntu. Windows. Oh, that one. Yeah, yeah, yeah. Okay, yeah. I was thinking of another one. Yeah, okay.

It's charging $40. Please don't actually buy it because it's a rebrand of another scam distro. Lindos, was it yeah yeah then that was called linspire and then yeah and basically evolved they claim things that are just not possible like they have much better wine support than other distros and they've never indicated they've shipped any sort of additional patches and just the things that their distro claims is basically nonsense as a way

to get people to I guess support them? I'm not really sure. Yeah, but look at, and they've sold so many copies. We don't know the real number because they have this static number 10,000 sold, whatever.

Yeah, right. It's stuck at 10,000, been stuck at 10,000 for the past two years. So, but look at them. They're making money out of a scam, Distro. You can't make money out of anything on them. Just do the right thing. Yeah, you could make fake crypto apps and put them on the Zapp store and steal people's

Bitcoin. You can even do that, but please don't. Please don't do that. I'm not recommending you go to prison. They will find you. And the other day, because we have a podcast unrelated to zero linux it's called nta

no tux allowed it's not no linux allowed it's a misnomer i came up with the name i was like we need to be weird this is josh big pod and i uh three weirdos making a podcast. So we need to make it equally as weird. So I came up with the NTA, no talks allowed name. But we were talking about this subject. We were like, you think on Linux, there's no such thing as piracy? There is.

Okay. I'll give you a major example. Sure. IntelliJ. IntelliJ. what like there is okay i'll give you a major example sure tell it j tell it j because they have services behind paywalls sure circumvented circumvented with with patch binaries same thing goes for something much smaller it's called sublime text and sublime merge i guess because people got annoyed with the with the pop-up that continuously shows up whenever It's called Sublime Text and Sublime Merch. I guess- Because people got annoyed with the- with the pop-up that continuously shows up whenever they save a lot. Yeah, I guess there's also people that-

Remember, this project is free and open source, pay us! There's people that also have like custom Spotify clients that, like, skip the ads. Oh. Are you listening? Oh Used to That's what got me into paying a premium subscription because when you when you block the ads Get your account banned. Yeah, they don't like that. Very easily. Very easily.

So don't use patch binaries because that's opening the door for malicious code on your system. Imagine that. Exactly. So the same thing that exists on Windows exists on Linux I guess you didn't know that did you well obviously there's also a lot of game piracy and stuff especially now that Proton's gotten

as good as it has been bottles trust me bottles I caught someone I don't pirate games anymore I just get thank the lord for GOG because the way they

remove all manners of DRMs from games and they sell you the game outright you own the installer you don't need to rely on them to reinstall the game you don't have to re-download the game specifically a game that's 140 gigs on an 8 megabit connection. Yeah, that'd take a bit.

So, yeah. But with Bottles, if you have a pirated game, you can just install it and run it. Bottles doesn't care. You're giving it an executable to run through Wine. It doesn't care what the executable is But What saves Bottles from anything

Is that it's sandboxed If you get the flatback The official flatback If you get the unofficial AUR package Then guess what You just killed the thing that Bottles was created for Sandboxing But Yeah So killed the thing that Bottles was created for, sandboxing.

But yeah, so please. The whole summary of the episode today, the whole reason I wanted to come on this episode was I need to make Linux users aware of the fact that you are the one who ultimately decides how stable and how immune your system is. You cannot blame the developers.

You cannot blame anyone. You can only blame yourself for not reading. If you don't want to read, yes, sometimes distros like where they push you not to read, not to do research like you want to read yes sometimes distros like where they push you not to read not to do research like you want to and still get such things thrusted upon you those are issue small issues that sip through the crap slip through the cracks but they're not very often if you're using a rolling distro like arch and stuff and you want to go

bleeding edge and you still refuse to read and do your diligent research, please don't get surprised if your system crashes and dies. Because you, like yesterday, someone installed a dependency that they shouldn't have, they kept on checking, checking, checking everything that PAMAX suggested. And their system was crashing. So I'm like, yes. Those were suggestions. You shouldn't have selected everything.

So it's still user error. It's not developer error. It's user error. Most issues on distros, on Linux, basically, are commonly user errors that users refuse to take responsibility for and throw the blame on the developer. It's so easy to throw blame around. You shouldn't do that. I used to throw blame around. I learned from my own experience. shouldn't do that. I used to throw blame around. I learned from my own experience. Because at the end of the day, after doing minimum amount of research, like reading the PKG build,

like reading the output internal, because guess what? If you want to get to the bottom of a crash, for example, like, don't get me started on Kdenlive, but you run it from terminal, you will get the exact problem that you can go, and that's related to another one of your very interesting videos that I highly recommend people to watch, is report upstream, not downstream. Don't report the issue to AUR. Report it directly upstream to the project's GitHub. If you report it to AUR, guess what? The maintainer on AUR is not the same as the creator upstream. I like what that video is.

I think it depends very much on the context of how the application is being used. I think with the AUR, yeah, it's probably fine to go upstream. If you're on something a bit older, then it depends on the project and what they're interested in supporting. Yeah. But most commonly you have to go, especially with Arch,

just go to the AUR. On the AUR 99% of the time they have a link to upstream, to the project upstream. Some packages don't for whatever reason, because they're completely custom and they're unrelated. But you click on that link, you go to GitHub, you create an account, you report the issue. The developer will, like repo CTL. I don't know if you ever heard of that package. Repo CTL, it's on the AUR. Repctl for is for repo maintainers like myself it allows you to

push back download the pkg build with a terminal command that i alias downloads the updated pkg build builds the package and pushes it to the repo it It's for repo maintainers. When Pac-Man got updated to 6.1, apps stopped working because the new Pac-Man 6.1 introduced debug, introduced new ways to sign the packages and so on and so forth.

I reported the issue upstream to the developer himself who hasn't pushed an update in four years because it was feature complete. It was working. As soon as I reported the issue, not 45 minutes later, there was an update. If you do your job correctly, issues will be fixed, will be dealt with. So do that. If you're on bleeding edge distros or rolling distros and stuff like that and you like that kind of stuff read that's the minimum you need to do read and report issues the right

way don't just say ah that maintainer is bullshit and we we don't we don't need to trust them. Very commonly I see it on social media. They go complain about it on social media where they could have spent that valuable time reporting the issue upstream and it wouldn't have been fixed by the time they started complaining. That's what I do.

I do a bit of both and then I'll make a video on it. You'll make a video and I think it's because of your videos that the KDE developers were more aware of the gravity of the theory. The reason why I make a video on it is because I want people to be aware of the problem, right? Like... Awareness. You're spreading awareness.

Yeah. I think people are weird. They were like, oh, well, why don't you just go and write code for it? Why don't you go and report issue? Again, a lot of times I do report issues. Sometimes I don't get reported because I forget to report it. But that's a whole other issue.

That's an issue I need to fix myself. But I make the video oftentimes because there are issues out there that don't get the attention they deserve. Because most people just are not aware of the problem and By making a video like that it it brings a lot of light to it It gets people discussing the problem oftentimes like the issue isn't something that's actually serious anyway And just gets dealt with at some point in the future other times It actually is a serious issue and by bringing light to it, a lot of developers don't like this.

I've said it before, if you make a lot of noise about something, oftentimes that will get it looked at a little quicker. That doesn't mean go and harass developers, but if you get a lot of people talking about a problem it often gets fixed a lot quicker especially when more people start to realize that it's a problem that affects them as well it's your way of reporting issues upstream your video is again i do report the issues upstream as well um but i know that developers from these projects watch the videos. So... Yeah, and especially Vox3. Vox3 is

as weird as he can be. He is one developer that if I were to use Hyperland, which I will never use, I'm not a window manager person. I don't like key bindings. I don't like config files. I just like to drag and drop

stuff, like on KDE Plasma, just drag and drop do your thing but I'm a visual person basically but with Vox3 he does things very correctly he sees your videos you report the issue upstream

and you report issues to Hyperland more than you report to any other package because you're a Hyperland shill as you called yourself it's easy to report issues to Hyperland more than you report to any other package because you're a Hyperland shill. Well, the thing with Hyperland is it's easy to report issues. As someone new to Plasma, I've said it before, but I'll say it as many times as I need to. The Bugzilla sucks. It is so hard to report issues for Plasma.

Yeah. Get it from a guy who has have been has been using plasma for five years um i don't report bugs because every time i do on their bug tracker more often than not it gets stale and then automatically gets closed so So I'm like, okay, I'll report issues to Nico directly. So the advantage us geeks have towards regular compared to regular users is we are in direct contact with some developers. You are in direct contact with Vox on Discord. I am in direct contact with Nico on Telegram. So and I'm in direct contact with one of Telegram. And I'm in direct contact with one of the Manjaro maintainers.

So in case of people mentioning an issue with Manjaro, it doesn't affect me since I don't use Manjaro. Well, I do on my HTPC and it just celebrated its 1,600th day. Because I only run Plex on it. That's the only app I have

but I do report issues directly to the developers themselves bypassing the whole bug tracker thing when you do that things get solved pretty quickly like yesterday I mentioned the issue with OBS to Philip

I was like yeah we're on top of it so yeah but this is a luxury we have that regular users don't OBS to Philip. It's like, yeah, we're on top of it. So, yeah. But this is a luxury we have that regular users don't. Right, right. We shouldn't even mention it. This is just, you gain that by being on social media,

by being a distro maintainer, by being a developer, and so on and so forth. All right. The right way to report issues is to go upstream, click issues, new issue, report your plan. It can be very dumb. Unless it's Plasma, in which case you go new issue, you go find the section with your application.

Then you find in the section, then you find the application. Then you set the rating and then you find the tool in the you set the rating, and then you find the tool in the subsection of the subsection of the subsection, and then you fill it out. But yes, that's yes, you click new issue. I think they have a GitLab instance now? Um, they do, uh, like, but they're, a lot of their tools are on GitLab, but they're like really spread out and they need to fix that yeah they need to fix nico has been mentioning that they're working on on the issue but so far we haven't seen any any fruit to that labor but it's a tough problem that's the issue there's a lot of things in plasma that's the issue that's another issue yeah but, you just, if it's not Plasma,

you just report issues upstream and you're good, especially when it comes to packages like on the AUR. Just click the GitHub link. And there's one thing I don't like on the Arch repositories is they don't directly link you to the source and the PKG build. They don't have a link to the PKG build like they do on the arch repositories is they don't directly link you to the source and the pkg build they don't have a link to the pkg build like they do on the aur you start you have to hunt for it right yeah you gotta go to the source of the package and then you can find the pkg build in there yeah and sometimes the pkg build is is buried inside a folder with it which is inside

another folder which is inside another folder you have to dig around for it with xz it's there on the first layer but yeah i know what you're talking about some of them are a bit of a mess yeah so uh and there's no commenting system on the arch repositories because it's not meant for that if you want to report an issue that's why they have the unstable you can join and here's another thing I want to mention about Arch. Since a lot of people keep saying this, it's not true. It's all

a contribution-based distro where people can contribute code, packages. It's a collaborative effort. You can join it yourself. If you're a developer, you can just request it from Antiz or whatever he's known as on Arch. AUR is known by Antiz.

I don't know if it's the same on Arch, but you can contact him. You can show him what you can do, and you can become part of the Arch community. And you can push packages there. They give you access to the unstable repositories and so on and so forth. You can push your package. They tested, multiple people tested, and if it's okay, it gets pushed to extras. So help Arch be bigger. Help it get rid of all this fluff and cruft that is called, we have to rely on the AUR.

There's a lot of packages that shouldn't be on the AUR, like downgrade. I don't know why it's still on the AUR. It should be part of the core repository. It's on the AUR. It has been on the AUR since day one. I don't know why they haven't moved it. Basecats are downloading one or more packages

to a version or cache. I did not know that was in the AUR. Huh. Yeah, sudo dot when they tell you because here's the thing. Arch tell you if you're having an issue with a certain version of a package, downgrade it. How am I going to downgrade it if I don't install downgrade from the AUR and yet you tell me not to trust the AUR? Well, the manual downgrade method, that's how. What? You can manually downgrade it. Use the Pac-Man command and pull it from your package cache.

Well, yeah, if you have it in the cache, because a lot of people clean their cache. Yeah, yeah. If you don't have it in the cache, there's no way to grab it from online unless you have the downgrade package. So put it on the extra repositories. It's a working package and it's stable and it's feature complete.

What else do you want? That's what I mean by help Arch get rid of all these problems. Tribute to Arch. That's what I'm doing. I'm not a developer. I barely know how to write bash scripting. What is bash scripting? It's a culmination of commands that you collect with time. Instead of running each command separately, you can put them all in a single script. An echo line that says what it's doing, describes what it's doing, and that's it.

Save it, and that's a script for you. Of course, you can make it more advanced, like using Wiptail for endcurses and stuff, but it comes with time. That's what I learned recently, that there's such a thing called Wiptail. I can create endcurses where people can select a single package or multiple packages to install instead of having to install one package, wait for it to be installed, then select another one, wait for it to be installed, and so on.

You get the hang of it with time, but I'm a bash scripting beginner still. I don't know how to use advanced commands, but I'm getting there slowly. So why not contribute all you learn upstream to Arch or to Gentoo or to Ubuntu, whatever? This is how Linux grows, by contributing what we have. And if you want to ask for financial support, we can ask, but don't thrust it in users' faces. This is how you lose them. You can donate. It's not necessary.

Blah, blah, blah. That's it. That's the message I wanted to get across using this episode. We've been on for two hours, but this is the message. Linux is just like any other operating system. the message. Linux is just like any other operating system. Its advantage is that it's open source. And with its open source nature, it brings with it certain responsibilities from you, the user, to know what you're installing, study things, and take responsibility for user errors. Because most of the errors stem from the fact that you didn't read the instructions correctly.

Or you installed it with a conflicting dependency. And so on and so forth. Love Linux. Be careful what you're doing on it. And be happy. Be happy. That's yeah that's the the the thing and don't go on social media spreading hate about something because i see a lot of that a lot of religious hate i call religious hate is like i use hyperland it's the best window manager

in town you shouldn't be using anything else If you use anything else, you're a pleb You're an idiot, you're a whatever That kind of thing And it's being spread more and more on social media They treat what they're using As the end-all be-all thing Nobody has the same use case as you

That's why we're different That's why we're different. That's why we're human. This is part of humanity. If we're all the same, it would be a dull life. If you were a KDE user 24-7, and so was everyone else who was using Linux, then why do other desktop environments and Windows addresses need to exist? So stop doing that. Stop doing that.

There's a lot of things wrong with Linux. Same with Windows. Same with macOS. They all have their issues. But since we are talking Linux here, we need to talk about the thing we're using. And in this thing we're using, we need to stop that. Oh, you need to use this because this is the best. NixOS is the best because it's a

whatever distro. Stop that. I'm like, that's one of the reasons I stopped Zero Linux. It was because, why don't you do this? Because this is the best. You're an idiot for not including Hyperland. You're ignoring, you're artificially

limiting your distro by not shipping Hyperland, by not including Wayland, and by not including Hyperland. You're ignoring, you're artificially limiting your distro by not shipping Hyperland, by not including Wayland, and by not including... Okay, I'm done with this. Let's create. I need to offer users more freedom. They can install whatever desktop environment, whatever window manager they should, they like.

Then use my toolkit to get the necessary thing out of the way. That's it so it pisses me off when i see people doing all this spewing all this hate and condescending comments and words because they think what they are using is it makes them reach the god tier when they say that anyway it was a great discussion

I had fun it felt good getting this off my shoulders because I've been keeping it in for so long I need to make a video on my own channel about this but I'm too scared

I was like might as well spew it out on Tech Over Tea well it's just yeah I guess that's as good a note to end it on as any yeah love Linux don't hate it and

keep an open mind yep well um let people know where they can find you and find your stuff uh you can find my toolkit on the website and i need to mention one thing about the website it's that current the current design is temporary i'm messing around with html but i'm working with someone on React, on a React version. It's coming, slowly. But you can find anything about my toolkit on zerolinux.xyz.

If you want to talk to me about anything Linux, it's mastodon, fastodon, basically, zerolinux. And if you want to talk to me about life and anything else It's mastodon.social Forward slash at tech zero

Easy And on my YouTube channel You can watch my videos I put out two videos a week Monday and Friday So yeah that's where they can find me Awesome Nothing else you want to mention?

Just one thing. Contributing to Linux doesn't mean contributing code. You don't have to be a developer. You can just be an issue reporter. You can just test if a package works. That's it. That's all Linux requires from us users.

Developers is a different story but you the regular users just hit if you encounter an issue hit report issue if you found a malicious code somewhere in the package report it upstream click of a button yeah it's so easy as clicking a button. Yeah. Yeah, that's fair. As for me, my main channel is Brody Robertson. I do Linux videos there six-ish days a week. I don't know what will be out when this comes out because, as always, I have a backlog of podcasts recorded. So this will be out sometime.

Sometime. Sometime in the future. The gaming channel that is BrodyOnGames, I am probably still playing, actually probably done with God of War 3, and I'll probably be done with The World Ends With You. So, I don't know. I don't want to promise what I'll be playing.

I'm thinking of doing like Sekiro or something like that. So, pop around and see what's there. And this channel, if you're listening to the audio version you can find the video version on youtube at tech over t if you're watching the video you can find the audio on any podcast platform there is an rss feed put it in your favorite app and you'll be good to go give it the final word what do you want to say repeat the same thing love linux linux is a beautiful toy to play with have fun not a few bad words it's fair see you guys later