 I'm your host Matt, and I'm your co-host team, and I'm Josh. I'm Tyler. All right, yeah, Tyler, his audio is a little low. I won't be able to fix that in post, but it's fine. It's all going to happen. So if you're watching this live, this is the horribleest podcast in terms of technical issues ever, but not surprising. It's literally, we've been fighting with him for an hour. But speedrun, as somebody just said, I use Fedora by the way, he said in the chat. We're going to do a speedrun. This is Linuxcast. We talk about Linuxy things. We're going to try to do this in under an hour for the first time because Tyler's literally starving to death. Steve's phone is at 39%, and that is sick of his podcast already, and we're just getting started. I'm losing my mind. It's going to be okay. It's going to be fine. It's fine. It's going to be great. I'm sure it's going to be great. Anyways, the Linuxcast, we talk about Linuxy things, and we have a topic for you. We're going to talk about Waylon later on. Steve's going to lead us through that. Before we do, we're going to do a very, very quick lightning round of what we've done this week in Open Source. So Steve, very quickly, what have you been up to this week? Updating my ISOs, KDE frameworks, updating, fixing column arrays, and enjoying my Android phone. That was the best lightning round ever, Steve. It was perfect. Golf claps. We guys needed some claps, so we had a clap. All right, Josh, Lightning Speed, what have you been up to this week? I haven't been doing anything unless this week. I've read all these books. Lane, Tyler, what have you been up to this week? I've been messing around with a new laptop I got. It's an Intel Whitebook OEM Intel laptop. You can find it on eBay. It's really cheap. It's real nice, and it's very upgradeable. All right, and me personally, I've done very little, mostly work all the week. That's usually what I've been doing. So I'm very boring. Not as boring as reading all those books. I make fun of them because I read a lot of books too, but it's just fun to make fun of Josh. Anyways, that was the least informative open source, our weekend open source ever, but we're in a rush. Anyways, so our main topic this week comes from Steve. So Steve, lead us off, friend. All right, so the topic of the week, as Matt mentioned it earlier, is going to be about boiling. I don't know why I had dildos on my brain, but it's going to be Waylon in all seriousness. It's not where they go, bro. It's not where they go. Okay, sorry. I'm getting over a end of summer cold, and I'm semi-high on high on all, not to words you're going to hear in a sentence. But Waylon is the topic of the week, and it's going to come as a surprise to everyone. When I say this, Waylon, I do not hate Waylon. I have no gripe with Waylon. I just respect the developers and what they say. They say Waylon is currently in its mid-stage, not yet in its final stages, and they don't recommend to use it on production hardware. I talked to some of the developers, two of the developers. They mentioned this to me, and they were very adamant on a sentence. Not all applications are yet ready to be adopted on Waylon. It's not them to be blamed. It's mostly applications either refusing to jump on board, causing issues, or jumping on board too early and causing more issues. But what I will say about this is we do need users to adopt Waylon, because it's the user reports, error reports, that will help Waylon grow and fix for scene. They did not expect. In all reality, Waylon is not ready for mass adoption, but it can be used, however, with a lot of limitations and caveats. I don't hate Waylon, and to prove it to everyone, the next release coming in a week or so, from XeroLinux, KDE basically, and GNOME, will be shipping with Waylon included, but not enabled, so we can finally get over this, XeroLinux hates Waylon, quote. I'm using Waylon on my newly acquired or... People are gonna say that that was a shitty deal, that is, but I don't care. I exchanged my Steam Deck for a 2017 7th Gen laptop, but this laptop will help me build Waylon, the XeroLinux Waylon support, where the Steam Deck won't. So I needed something that will help me continue working on XeroLinux, rather than something that will remain on the shelf gathering dust. So with that being said, I am going to be switching, on that laptop I'm going to be switching to a distribution, not so much a distribution than Arch installed, so basically it's the vanilla Arch ISO, with a script integrated into it, that will allow you to install NWG thing, and Josh will explain in a bit what that is, because he's encyclopedia of the team here. Yeah, we just rely on you for that kind of shit, but it's basically hyperland turned into a semi desktop environment. So Josh, explain encyclopedia style what NWG is, NGW, NWG. Okay, so in order to explain what NWG shell is, I need to explain what the graphic stack is on your Linux machine. So when we're talking in terms of Wayland, what is Wayland actually? Wayland is actually just a set of protocols that tell app, that is just think of it as like an instruction book or a set of guidelines. That's all Wayland actually is. There is some code, there is some libraries that were written for Wayland, but in the scope that's what Wayland is. When Steve was talking about this thing called hyperland, what hyperland is, is a compositor. Basically what a compositor is is much more similar to what the Xorg server is, which if you've heard people talk about Xorg, they typically talk about the Xorg server, which is the thing that actually draws the display up onto your screen. And we might talk about window managers as well, which window managers don't necessarily exist on Wayland, but they're functionally from what we're talking about, they're basically the same thing. Compositors are window managers, they're just not actually window managers, they do a lot more than just managed windows. But what NWG shell is, is NWG shell is just like a shell that sits on top of a compositor. So think of it as like your panels, your menus and stuff like that. That's all NWG shell really is. And NWG shell also includes NWG elements like the doc, written in GTK, a GUI written in GTK to create your hyperland or sway because it's got both. But it allows you to build your configuration using a graphical user tool instead of having to open a document or configuration file and start typing away. For example, in my case, I'll be like an idiotic moron staring at that freaking configuration file not making hesitate of what does what with a graphical tool that answers my questions. So I wanted a desktop environment on top of hyperland because I really love the effects on hyperland and everything and I love the rainbow animated thing that Josh introduced way back when. So to be able to do that with a graphical tool, that's all I wanted and a doc because I'm a latte doc fanatic because I have a MacBook and I love the MacBook UI. Let me ask this question. We don't need to get into the specifics of window managers and stuff right now. We don't need to get into there. What I want to know, just a quick poll, on the distro that you're running right this second, the thing that you're using to record the podcast, who's actually using Wayland? I am. I am. Not. I'm not. Okay, so it's 50-50. I'm assuming you're, Josh, you're using the KDE version of Wayland, yeah? The Wayland session for KDE? Yeah, I'm in KDE Plasma right now using Wayland. And you too? Yeah? All right. So I'm using Qtile. It's just the extro version. So, and Steve, what, or Tyler, what are you in right now? Oppo Us. I'm running on my laptop with an NVIDIA card. I'm not willing to, you know, pass around. We're Wayland on NVIDIA. So just to kind of broaden the topic instead of getting buried in the specifics of NWG, whatever the hell you're talking about, Steve, let's talk about Wayland itself. We don't need to get into the specifics, right? Okay. No, no, hold on a second. I'll take this over. First, for a second. You said something earlier that was really interesting. You said you talked to a Wayland developer, and you said that it's in the midpoint of its development and that it's not ready for primetime use. My issue with Wayland has always been not that it exists, but that it's been pushed on literally everyone as the default by all the major distributions. So Ubuntu has done it. Fedora has done it. Debian at this point has done it. So if you're using a mainstream disk show, at least most of them have turned Wayland on as default. This brings me... You just attacked the second part of the discussion, and I know this is a lightning round, so I'll attack it right on. I mentioned that to the developers. They were like, every distro is free to... They're not against distros switching to it, but it's preferable. All they said was it's preferable not to set it as default currently in its current state, but a lot of distros just want to be the first to something. So they're doing it. I agree with you, they shouldn't be doing that, especially in its current state, but what can we do to stop them? They will do whatever they will do, but zero Linux will not be one of those distros. I'm just including the Wayland packages to allow users to mess around with Wayland. I recommend to mess around with them, but I do not recommend to use it as a production as the main session that you log on to, but I'm going to say one thing that will contradict what I just said is, since I'm using Wayland right now to talk to you guys, the only difference that I noticed, major difference, and that's something that makes me want to use Wayland more. I can't because a lot of applications I use haven't jumped on board yet, but smoothness, like Luttedock, I don't know how to show this, but I don't want to mess up the stream, but when I hover the mouse over the dock, over Luttedock, it could be a Luttedock issue, I don't know, but if I do it on Xorg, it skips every other frame. It's like very jittery, and sometimes you see the label of one icon, whereas I'm on a different icon on the other end of the dock, whereas on Wayland, it keeps up, it keeps up, it keeps up. It's instant, it's smooth. There's not a single dropped frame, and the whole experience is very smooth, dragging windows, and another major thing is that I have three monitors with three different refresh rates. No problem on Wayland, big, big problem on X11. So there's a lot of good things with Wayland, but they're not enough to make it adoptable as a main production. Josh, you're the fanboy here of the four of us. Other than security benefits, which are primarily a developer-focused reason to use Wayland, what are good reasons to use Wayland? Sell me on Wayland, would you please? Okay, so Matt, have you ever had the fight screen tearing? Yeah, but I know how to fix it. Yeah, what if I told you that you'd never had to fix it if you use Wayland? Like, actually never had to fix it. I mean, it would save me two seconds. Yeah, it would save you two seconds, but let's just say that you didn't know how to fix it. Then I'd need to learn how to fix it. Josh, haven't you learned yet that you're dealing with Matt? You can't convince Matt of anything. So Wayland has a lot of nice features. For one thing, like I mentioned, it enforces perfect window drawing. So by default, VSync is enabled on Wayland. And yes, it doesn't affect video games. It's not going to be anymore. It's going to be an application bypass to run the screen tearing. But the compositor itself will still be running with vertical sync. And it does support FSR, or not FSR, but precync and gsync as well. So all the things should work. It's amazing for gaming. It's amazing for gaming. And because this is running at the display server level, that means that your input delay is not going to be nearly as bad as it would be on X11 or even on Windows. So sorry, Kudu, you're wrong in that. But it's also amazing for gaming. If you want a game, it's better to game on Wayland than it is to game on for most of the games at all. That's not really true. Yes and no. In theory, yes it should be because you're not running a dedicated actual server. That's then communicating with a client. So yeah, a Wayland environment is going to be theoretically lighter. And because Wayland is also just a newer software stack as well, it's not going to have like the past 40 years of support for X11 calls. So in general, the codebase is a lot cleaner. It's a lot more maintainable than Xorg. Which means that... When it comes to gaming, just an important point to make out is when it comes to gaming, almost every game you're going to play, especially if it's over a couple to a few years old, it's going to be running in X Wayland. Because it uses most games, make use of SDR, and FDL does not support Wayland yet. They are working on it, but... For more modern games, though, it's like... I can give an example, Doom Eternal. Doom Eternal on Wayland and especially that it's a Vulcan title. Wow. Just wow. I couldn't believe my eyes. I was getting 110 FPS on Wayland where I was getting around 80 FPS between 60 and 80 FPS on X11. If I continue on here, here's a benefit that you might notice as well, Matt, where you mentioned previously that you've had issues with monitors going to sleep. Wayland supports dynamically plugging monitors on like X11. Because the way that X11 is written, when the Xorg server starts up, it's going to index every single screen that's on the system. And every time you plug in a new screen, the entire X session technically actually restarts every time you plug it or unplug the screen. Same thing happens with DPMS. So when your screens turn off through DPMS, X11 is going to restart itself and then it's going to say, see, hey, there's another monitor. So it's going to shut that monitor off again and it's going to restart itself. It's a really hacky protocol just to get multi-monitors support working on Xorg. Especially if you're using something like a laptop or a docking station, you probably know exactly what I'm talking about. Sometimes it just doesn't work. Or say you have a multi-monitor system and you just let system screens turn off after a set amount of time of system idle time. Wayland natively supports that just out of the box. And because of the support that they built for the multi-monitor configuration, that also means that your screen refresh rate. So on my system, I have three different monitors on my system. All my monitors are capable of 60 hertz to 75 hertz. I can run 75 hertz on one screen, 60 hertz on another screen on Wayland. That does not work on Xorg because Xorg relies off of, I can't remember the library name on the top of my head right now, the library that Wayland uses to actually draw the window. It's not X-Rander. It's not that. But the way that Xorg works is that technically when you're launching a graphical session on Xorg, you're actually just spawning a big window. And that big window is what stretches across all the screens. And they are just one massive screen. So that's how you can just take a window and just drag it from one to another because technically that window is sitting within a window within a window within a window. Yeah. And on X11 it will run as, even if you have a monitor that's 144 hertz, it will run at the slowest monitors refresh rate. So that's a big problem. I have 144 hertz main display, but I cannot get it to run at 144, especially in games because I have 65 hertz, 144 hertz, 75 hertz, 60, 75, 144. And it will run at 60. Okay. The library that I was talking about is called Xenorama. That's what I'm thinking of. Okay. So somebody in the chat asked me what it would take to get media actually like and use Wayland. I talked about this in a video recently. Guys, I make videos for our YouTube channel and right now OBS doesn't support Wayland out of the box, at least on a window manager. I don't know if that's the truth on a desktop environment. I don't use desktop environments, but if you're going to use Wayland or use OBS on Wayland and a window manager of some kind, you have to have portal set up and you have to have certain environment variables set. This is exactly what I meant, what the guys over at Wayland meant. It's application dependent. And if applications don't support it, especially when it comes to media production, there's a lot of things that go behind the scenes when you're doing media production that Wayland is still, well, applications on Wayland still, and specifically talk, they mentioned something along the lines of HDCP also. Oh, look, if we're being clear, OBS on Wayland does work. You do need a portal. It does work, but it's hacking. No, it's not. Tyler, you talk, not Steve. Go ahead. It works perfectly fine. All you need is a Paul Kidd installed when you're using a window manager, because on Wayland it needs your permission to be able to access the screen. You know the one thing that doesn't work well on OpenSUSA? Paul Kidd. Well, that's a you problem then, Matt. No, that would be an OpenSUSA problem. They need to fix it. But in all seriousness, I want a burger. Why would you say that? That's great. It's just random. No, but this is another, this is part three of the discussion, and I mentioned it to Josh before the podcast three hours ago. The question I'm going to be asking chat here, and since you guys are seeing chat, you'll be reading it because my browser is currently closed. When it comes to Wayland, a lot of distributions like, let's say Fedora, as far as desktop environments are concerned, you know, everyone has their own implementation of Wayland. Shouldn't there be a standard for Wayland so everybody adopts the same implementation of Wayland so everybody knows what to expect from Wayland across the board? Why should we always have to relearn what to do on Wayland on every different desktop environment? Why the different implementation? So the reason for that is because Wayland does not have a server. What Wayland official projects that you do have are really just tools to check to see what things are doing and how they can do it. Now, I see somebody mentioning WL roots. What WL roots is, it's a library for a compositor, but generally it's the compositors that are supposed to be doing all this. Now, Nome has its own compositor because Nome had the first compositor. The first compositor was actually what is the Wayland reference compositor? Man, I'm googling stuff here. It's not WL roots. They have oh shit, I know what you're talking about. It's not mutter. It's not mutter. Weston was the first Wayland compositor and it's really just like the example. The one that came right after was Nome's mutter, which mutter is a compositor. Now, because there is no Wayland server, these compositors are lifting that load themselves and each compositor is doing its own different thing. Now, WL roots is just a library of tools that a compositor uses. Technically, Sway, Hyperland and those things are what uses WL roots. Now, that's a whole different ecosystem. AD Plasma has its own ecosystem. It has a bunch of different ecosystems. The way that the portal spec is made is purely for your applications like your OBS studio. Now, Matt said that he was having issues with setting environment variables in OBS just for OBS to run properly in a Wayland environment. That's actually not OBS's fault because if you look at all the OBS official tools their official make file that's available on GitHub they set all those environment variables as compile flags which means that if you had to declare an environment variable just to launch OBS on a Wayland session, that means that your package manager disabled Wayland so you need to be filing a bug report on the package in your distribution. What you're trying to say is that we should all be using Gen2 and compiling it from source do what you're saying. No, it doesn't even have to be. You just need to tell the package manager to fix his crap. And if you were using flatback version which is the official version that's what I use is the flatback version and it never works for me. And when I say it never works it doesn't mean that I can't get to launch I can't get to record a webcam it does all those things, it's specifically with screen recording which I do a ton of it just most of the time doesn't work. Matt, I have a solution for that. Not use Wayland. The solution. No, open flat seal and I noticed that too but it works flawless for me on KDE Wayland. I can share screens, I can do everything no problem. You have to open flat seal and play around with the Wayland and X11, X Wayland Let's see if we can troubleshoot Matt's issue right now. Matt, what Wayland sessions have you tried with OBS Studio? Hyperland, Sway, KDE. You haven't installed the XDG desktop portal packages for them? Depending on which one of those I was using, so like when I use Hyperland I use the Hyperland portal, when I use Sway I use the regular XDG portal, the WL Roots portal with KDE, the KDE has their own portal. After you installed the portals did you exit the graphical session and relaunch it at all? Yeah, rebooted. It's flat seal. That's what it did with me. If I didn't set the flat seal X11, Wayland or whatever flags, it didn't work. It didn't allow me to share screens, but as soon as I selected the right one, I was able to select whatever screen. So when I was having the problem specifically with Hyperland I joined the Hyperland Discord and I got into the thing and I was guys are going to remember this has been months and months ago so I don't remember the exact errors and stuff. But the biggest problem was that the actual option in Discord to grab a screen or to grab a window or screen didn't even exist. It wasn't even there. It wasn't an option to select in like... So that's a Discord limitation. It had nothing to do with Discord. Well Discord, you can't share a screen on Discord. I was literally trying to capture a monitor. It didn't even have Discord running. It was literally in OBS when I wanted to go and add a scene you do that you click the plus button and it comes Even the developer Hyperland had no clue what was going on. Now Garen, this was not all from Suza. This was on whatever just was probably Fedora at that point, but it just couldn't get it to work. I'll agree with Vaxry on that one. I've never heard of that because even if you can't screen share something on Discord, the button should still be there. The button shouldn't disappear. It has nothing to do with... If I said Discord, I misspoke it. I meant OBS. On OBS you press the press button and in the menu that comes up, one of the things that should be there should say something like screen capture and then in parentheses pipe wire, right? That should be there. That option didn't exist. Like it wasn't there. There was no option for screen capture whatsoever. It just didn't exist. That was with the environment variable set and a reboot afterwards to make sure that it was running and with the proper portal. Let's be clear that button missing should only happen with the actual package itself inside a flat pack. If that stuff exists there, even if you don't have pipe wire installed, it should still show up. It just obviously won't work. You don't have pipe wire installed. There probably was a dependency issue but actually flat pack won't bring in pipe wire. If he's running a Waylon session and pipe wire is not running then that would probably be why. But if he's running a Waylon session but if he's running a Waylon session pipe wire is running it was probably fedora not true actually. Because you can launch a graphical Waylon session and not have pipe wire running. I don't even know how you would achieve that. In my case it was fedora and fedora comes with pipe wire by default and has for ages. But in my case it was just a matter of flicking the correct option in flat seal. It could be a permission issue with flat pack as well. All of this stuff doesn't really matter because troubleshooting something that happened months ago is just really silly. It's for me it gets annoying having to relearn every time I switch to a desktop environment I have to relearn the Waylon implementation. It gets annoying in my opinion and that's just in my humble opinion. I remember how to do things on Waylon on one desktop environment having to relearn how to do it in the implementation on a different one. There should be some sort of a standard not an actual general standard but basic standard. The one thing that works you can say whatever negative things you want about XOR. You can say all of them. It's insecure, it's really old, it's bloated, it has 30 years of code legacy code behind it that obviously makes it really hard to maintain. All of those things are absolutely true but you know the one thing about XOR that is also absolutely true it works. If you want to record a video it works. If you want to play a video game it works. While I'm not saying that that doesn't mean that it doesn't need to be replaced it doesn't need to what I'm saying is that there are still a lot of workflows right now that if you want to do them on Waylon it either doesn't work or requires a significant investment in time and knowledge in order to actually work. Right now. Right now this is what it requires but when it really is baked and it's official and it's officially announced. One of the things that you hear when people review like a phone or something like that on YouTube like you watch MrMobile or MKBHD you buy the product for what it is right now not for what it's promised to be in the future. Exactly. Waylon has all those things that Josh says sound fantastic but those benefits while here for some people right now aren't here for everybody right now especially if you're running a video card it's still a pain in the ass. If you want to do certain workflows like I do I just somebody asked what would it take to get Waylon what I want to be able to do is open up OBS and just be able to record a video just like I do right now that's what I want to be able to do. Brody made a dedicated video Brody Robertson if you follow him I don't know but Brody Robertson made a valid point in that video it's like he went back to X11 for the exact same reasons that Matt is discussing because for video production especially video production it's not ready yet and even the OBS people the Waylon those two developers were like if you are in the media if you are a content creator please don't use it it's simply that said these words please, they didn't go into details it just said it's not ready yet especially for media production if you're a content creator you have to get through a lot of battles get there and still you're not going to be 100% there if you are a content creator don't use Waylon if you like to tinker if people use Linux for tinker, you can tinker with Waylon all you want we need you to tinker what the Waylon people said yes, we want more people to jump on board Waylon for the tinkering purposes or for the testing purposes they said testing, they didn't say tinker because professionals won't say tinker for testing purposes and they want their issue tracker to be filled with issues they don't mind 100,000 issues they're doing as their valid issue and if not many users jump on board of Waylon there will be no issue reports they need more people to adopt it maybe that's why some distros are making some of their spins use Waylon by default let's talk about distros for a minute here the distros that are enabling Waylon by default which ones are they so a lot of the distros that ship Nome has been using Waylon by default for about 6 years now so it kind of just makes sense that eventually they'll just leave it as the default now, Fedora is not for the average user it says so on their website the average desktop user probably shouldn't be using Fedora because Fedora is for developers they want to push the Linux ecosystem forward that is what Fedora has been doing for 20 plus years now and they're not going to change anytime soon so Fedora's hard switching off of X11 to Waylon makes sense because that's what Fedora has always done what about Ubuntu? explain Ubuntu to me they ship Waylon by default they ship it and they have it enabled in fact it wasn't until 2204 the LTS release where they even considered using Waylon as the default system on Ubuntu and then they quickly went back on that after release so if you boot 2204 Ubuntu will actually run a hard check to see what kind of hardware you're running and it will disable Waylon as it by default so depending on if you're using a video card or something like that but for the most part, Ubuntu is only ever enabled Waylon as the default on the non-LTS releases which if you know anything about the Ubuntu development model you know that the one release that they care about is the LTS release everything else is basically just like here's a new feature we're trying out we want to see what the community thinks and also an important thing to keep in mind is Ubuntu when they roll out Waylon they also don't have to deal with nearly as many problems coming from their general user base because they are switching over to snaps and using snaps pretty much for everything so it's much easier to pretty much guarantee that a majority of the user base isn't going to have these problems since they control the app ecosystem for them because they control every app they will logically they will include all the apps that are ready for Waylon by including Waylon by default you still have the X11 session I think they would leave the X11 session to be used by the switch to by the user that they want to but they will set it as default logging what I would like to see just for a minute it'd be so nice to be able to switch back and forth because I would like to be able to go out and test Hyperland or Sway or any of the newfangled Waylon window managers that are out there but I can't use it as a daily driver but give me a favor right now on your system just install a Waylon compositor and in that same terminal just launch the Waylon compositor so you're using OpenSusa so just zipper install Sway and then just run Sway in the terminal now you have an entire Sway session inside your X11 session does it take over all the screens no it in fact will spawn as a normal window so you can do that he's like mute I'm doing it now we're right on the podcast let's do it right now with all its problems for my use case I just browse the internet build my ISOs and watch youtube Waylon just works my use case I'm currently trying attempting to play Baldur's Gate 3 that turn based at combat mode just won't agree with me I keep dying at the beginning of the game I'm not going to say I have Sway up running on this screen right now it's freaking the fuck out but you're launching a Waylon session inside your X11 session it's the opposite of X11 but okay primary display literally opens no terminals it just did that on its own huh I closed it because it was freaking out the whole system so it's fine I don't need to do that in the middle of the podcast that isn't not really the way I'd want to I'd actually like to actually use it in an actual proper way and switch back and forth I mean you can do it you just have to install the proper port or get it all set up and then when I want to go back to X or install the other portal to go back to where I would normally use it for the basic use case not in media production or anything on the internet read some books compile a few packages and stuff like that Waylon is perfectly usable if that's all you do though Xorg does all those things too yeah of course but again for me Xorg and I think it's an NVIDIA Xorg thing there's a lot of drop frame nothing is smooth the dragging window from from one monitor to another feels janky whereas on Wayland it's smooth like butter Tyler if you honestly the only reason if you don't give a shit which most likely you shouldn't care which one you're running especially if you're doing just regular normal computer usage just browse the web when you watch some videos and do one video call here and there like every once in a while Wayland is just fine and Xorg are just fine either one use whatever's default with your system doesn't matter and then the only reason you should ever really consider trying out Wayland is if you're running a laptop just to see if it gets you extra battery life really got it I would agree on that one because I was getting extra battery life I didn't mention that but on my janky laptop that's from 2017 the battery isn't great on either or but it's better on Wayland than it is on Xorg that's another reason I'm using Wayland on that laptop but I chose the wrong desktop environment for that on that 18 laptop because GNOME loads most of its shell in the RAM and so I basically I get when I boot it up on cold boot for whatever reason on that specific laptop it's using 2.5 gigs on cold boot the reason I wanted to talk about Wayland is nobody should hate Wayland it's just don't expect the unexpected there's four of us here but let's have a vote is Wayland ready? no no damn close I'll say yes with an asterisk and the asterisk is another discussion the asterisk is literally you should at least try it the asterisk is literally like if you're reading the small print when there's an asterisk in this case the small print is no it's got a good note in that like 2 size font nope what I'm gonna end with is the following if you so much as come to any discord server and say Wayland is awesome, Wayland this should be used and Wayland works for me flawlessly it should be adopted by everyone I'll ban you myself because it's not true when you get banned you can come right on over to mine and you'll be free to speak your mind it's a matter of speech it's not something I'll actually do but you shouldn't be doing that because if it works for you that means your use case does not require any extra effort it doesn't mean all use cases are the same as yours it's not the use case that should be the I'm gonna murder Tyler in his whole face McDanks I'm gonna murder you're horrible let's get the thingies of the week done then Tyler can go dive into the ball pit of McDanks McDanks I was not gonna say it alright anyways very quickly Steve you're thinking of the week please my thinking of the week is called Vendetta no I don't have a Vendetta against anyone if I ever would have a Vendetta it's gonna be against gosh but for mentioning Gen 2 way too much because I attempted Gen 2 and the VM crashed the whole application the work manager gotta give it a lot of memory bro so basically it's called Vendetta it's better discord for android the best way I can describe it Vendetta is amazing it's awesome there's another version called Alucord but Alucord is very janky it's not a good version Vendetta is very simple you just install the Vendetta manager install it through Vendetta manager on unrooted phones you don't need it to be rooted on android to install it just install the Vendetta manager install it through that what it will do is install the official version of discord then patch apply a few patches on top and it will allow you to install custom themes and plugins just like better discord we have to do is join their discord go to the theme section if you want to install the theme click on the link of the theme it will pop up with saying install just click install it's gonna install it go to the settings there's a theme section or plugin section go to the theme section select the theme it will automatically apply and if you have an AMOLED device like I do I enabled an AMOLED theme so every application on my phone is AMOLED it allows you to install custom themes and plugins and you can even install repositories so you can have access to all the themes and plugins in one place and have fun enjoy it well Android is open like iOS Tyler you're thinking of the week my thing of the week is good though beautiful engine it's a phenomenal gaming engine probably gonna love it especially with what's happening with Unity now yeah I just real quick I've been using Unity for a long time I've been in personal projects and freelancing and doing C sharp like game scripting stuff like that gotta be honest Unity has literally burned their company to the ground the past couple of weeks I mean like there's hundreds of game studios that are leaving them and Godot has gotten a lot of money thrown their way since the whole ordeal actually very good it's very difficult to learn coming from Unity just because the way you set up and code behaviors is very different but pretty easy to learn it's actually much simpler once you do learn it I've been enjoying it, it's great and I swear to God I can feel my stomach eating itself I swear to God if the engine guy in my chat says nuggies one more time who the hell McDank and Nuggies what happened to the English language I swear to God guys, Josh, you're thinking of the week my thinking of the week is called Make MKV because you know I hate Blueberry players shut up I used to use Make MKV on every single thing and did you know that there's a hidden option if you know can Josh why you want to use it please oh well but basically what Make MKV is it's a scriptable ripping program for DVDs and BlueRays and yes I imagine that you're talking about the hidden option to automate it we're basically as soon as you plug in the disc it'll immediately rip the disc and it'll kick it back out did you know that I could do that yeah I do and the hidden option is you can just instead of ripping it to an MKV file you can rip the disc as is make a clone copy in a folder on your desktop it's just called Decryp just check that box instead of making an MKV it will rip the thing it will keep the menus it will keep the special features it will keep the commentaries everything without having to convert it because the way it's normally used it converts a BlueRay or a 4K BlueRay into an MKV file you have to rip another MKV file to replace the original audio with the commentaries you will end up with two different files so why do that just decrypt the whole folder and most players today support playing from BlueRay folder decrypted BlueRay folder alright my thing first of all all the people in the chatter band they're all every single one of them are trolling me they're saying nuggies right now it's where it's already got to hate it nuggies I would like to take a moment to talk about RoboNuggy which is an amazing YouTuber you post free VSD videos I knew I'd heard that name alright anyways my thing really quickly my thingy of the week is Vivaldi web panels they're really cool basically along the side of Vivaldi if you want to use a web page or whatever and have it docked in a panel along the side so I've been using it for Mastodon and for Todoist it's over there and you can clap some if you want them out of the way and you can bring them back they can be floating they're really awesome the reason why I got into was because Todoist stopped working for whatever reason the flat pack version so I had to use the web like a web tab and I didn't want the tab pinned all the time but I wanted it where I could get it so I was able to use the web panels Vivaldi continues to be freaking amazing just putting that out there I know proprietary software but it's good stuff but thank you Matt but regarding Vivaldi officially now it's an official announcement it's official Vivaldi now exists on IOM yeah and it's garbage by the way horrible basically it's not good and it's not Vivaldi's fault but the thing you use Vivaldi for customization and you can't customize their app at all like I want to be able to move the address bar to the bottom like literally that's all I want to do you can't do it anyways I'm assuming it's an iOS thing that's a limitation anyways that is it for this podcast guys if you watched this live God bless your soul exactly you're a champ this was a rough one we actually started this podcast over I don't think we've ever had to do that before anyways we record this live every Saturday at 3 o'clock PM Eastern time so if you want to join us live you can do so at the Linuxcast YouTube.com Linuxcast I didn't do any contact information I'll do that real quick Josh is at tenleyj.com stocker Steve is at Fawcett on the stocker contact I knew that Steve is at Fawcett on the org slash at zero Linux Tyler has a YouTube channel he doesn't remember how to get into it but he's at YouTube.com also YouTube.com slash Linuxcast for me so follow all of us there record live every Saturday at 3 o'clock PM Eastern time before I go I should take one more thing the current patrons if you want to support me patreon.com slash Linuxcast also on Ko-fi and there's a shop shop.thelinuscast.org for merchandise you can add over there to check all that stuff out thanks everybody for supporting me you guys are awesome without you the channel from anywhere near where it is right now so thank you so very much for your support and we'll see you next time we'll promise no tech go to Ko-fi next time there's still those for everyone why does he ruin everything swear to god