All good! You’re still totally right; outside of the context, Linux has quite the user base with servers, embedded devices, and even phones, if we count Android. I think that’s relevant because it means we can’t rely on “security by obscurity”.
I haven’t heard of any such cases, but it is a smaller pool of users. Also, many desktop Linux users know more about using a computer than other operating system users, since it’s less common for Linux to come preinstalled. So that may affect it, too.
I imagine vulnerabilities with the Linux kernel or common utilities do apply to desktop users as well, which is a good reminder why staying up-to-date is important. But to my understanding, exploiting remotely would need a way of sending data to the target. And most desktop computers won’t have ports open to the internet for anyone like servers will.
I know that Wayland’s design does make it more difficult for a user-mode program to act maliciously, like as key-loggers or reading the clipboard.
Yeah… Apex Legends dropped Linux support a while ago and that’s one of the reasons they cited; and tbf, there were publicly available Linux cheats that ran under proton.
But there’s also loads of publicly available “external” cheats that run the way you described. Some run through a virtual machine even. It’s just not a robust solution for preventing cheating, and mostly hurts the legit Linux players.
I’m sorry to hear you’re having trouble!
Regarding the vainfo thing, at least on Arch, the Nvidia vaapi driver is a separate package. I’m not sure what the equivalent is on bazzite, but that’s likely why vainfo doesn’t show anything. And you should still be able to use nvenc anyways, which sunshine will choose before vaapi.
Is moonlight able to see the computer on your network? And in sunshine’s web interface under the “troubleshoot” tab, there’s a log. Does it say anything that might help?
I don’t think there’s a separate build with Nvidia patches now (at least on the AUR), as they’re included/fixed upstream. Still plenty of config and environment variables to set on Nvidia. And the new Nvidia beta driver, 555, should fix flickering in xwayland windows that was caused by a lack of explicit sync support. It’s been working well for me so far!
Right up front two major issues with Linux:
No standard UI - it’s different on every system
No standard tools - you can’t rely on the same tools being on every machine
These seem like pretty fundamental traits, since Linux is only the kernel. I think a better way to compare other OSs to Linux would be comparing them to specific Linux distros, since those often do have standardized installs.
But there’s not really a great answer for which distro or distros should be used to represent the whole linux ecosystem… and that fragmentation has both pros and cons.
Like, I really love my Arch desktop, but it took lots of time to learn and configure. And it often breaks with updates— it’s not something most users would want. However, I get cutting-edge updates and features, and I have specialized my entire OS to best work for my workflows.
I currently use and love bluetuith! I hope you are able to secure funding and contributors, as this sounds like it could be a great development.
Got home, it’s working really well. Like, I’m super pleased!
VRR still needs testing on my system. I know that there’s yet to be a fix for multi-monitor VRR. I still need to test with a single monitor, though.
YOOO!!
I can’t wait to get home for this! I’m going to try to use VRR again too, see how it plays with that.
Developers of Doom, Wolfenstein and Quake
Sorry for the late reply. Also @Cricket’s response is great and actually references a source!
Anecdotally though, as a user, I’ve noticed that some things require extra permissions. Usually there’s a prompt from the operating system that’ll ask for permission capture the desktop, which lets me specify which window or monitor to share. It uses the “XDG Desktop Portal”, which was already what allowed Flatpaks to securely access OS resources, and it has a whole bunch of different requests for resources and permissions. It’s similar to a web browser, where it’ll prompt you for privileges when an app wants them.
The hardest pain point for me has been that an app cannot detect keyboard input if it isn’t focused. This could prevent key loggers, but it also makes global shortcuts not work. There is a protocol that allows an app to request a key be forwarded to it, but it’s not widely implemented in apps (discord, for example) and I’ve had to rely on workarounds.