What does it do on new hardware? Not a lot of people are running normal desktop Linux on phones / tablets, are they? Which, totally cool if it works better on those things… but I guess I’m just surprised by how much hype there is for Wayland when X just works for me and would presumably just work for most people’s use cases. Like… who are all of these people that are emotionally invested in display servers, and what am I missing?
I mean, 20 years ago or whatever there was always the pain of black screens and X configs… but it just kind of works now in my experience?
What’s so much better about Wayland than X? I mean, I’m not really a fan of X and the security nightmare that it is, but as a user it’s all pretty plug and play these days. What does a normal user get out of Wayland? Would they even know they’re using it?
I’d love to try it, but it currently won’t work with some software I use, so I haven’t bothered… And honestly I’m kind of confused about how everybody is talking about how amazing Wayland is (and how it seems to suddenly be the one true path for a bunch of distros) when my only experience with Wayland is people talking about how great it is and then not being able to screenshare or whatever… Which doesn’t make it seem great from the outside? That maybe sounds a bit flippant, but I genuinely don’t understand why “normal” people are so excited? I mean, I can see people caring about features like HDR and maybe that’s easier to build into Wayland than ancient X11, but I’d be more excited about the specific feature than Wayland itself which may make implementing these things easier?
I saw a warning once a while ago on Firefox… and completely forgot this was a thing until I saw this post right now. I’ve had absolutely no issues. I guess I’m lucky…?
My understanding (which may be false) is that this can come about from competing design considerations and regulations. Like… It’s ideal to be able to push the door open from the inside of the bathroom so you don’t have to touch a nasty doorhandle, but you also don’t want somebody to be able to put something in front of the door, potentially trapping you in the bathroom (particularly in the event of a fire… Dying in a fire is probably worse than touching a nasty doorhandle), and you also don’t want doors to unexpectedly swing open into busy hallways. This drives me nuts too, though.
Huh. I’ve used chirp under Linux before and I just installed it with my package manager. Maybe it wasn’t available on your distro? Then it can get a lot more tricky. The other problem with these things can be permissions… once you have chirp installed maybe you need to add your user to the dial out group in order to be able to use the serial port to flash the radios.
The exam is relatively easy, and you can find lots of resources for practice exams and stuff. At first you’ll have a hard time with some specific questions, but you’ll get the hang of it. If you want they usually let you write the general and the extra exams after the technician for no extra fee (they’re harder but give you a better license with more permissions. Technician gives you a lot, though)
If you’re at all interested you should do it! Getting licensed doesn’t take much time, even if it seems a little daunting at first. Then you’re ready to go when you get the itch!
Running Jellyfin off of a VPS provider seems needlessly expensive. I guess server hardware has an upfront cost, but having real hardware to host it on at home will be far more cost effective long term, especially for storage.
Mine always have the ReplyTo field set to the email of the senior security analyst, so I always say hi and tell them that maybe the higher ups need some training on how to not send sketchy as fuck emails that train people to click on phishing links.