If there's no ForceCommand (I think that's what it was called?) in sshd.conf and no command=x in .authorized_keys (if any), you can probably use mosh. It spins up SSH to authenticate and then immediately start a UDP based connection afterwards. Instead of logging out every 15 minutes, you will get a "Last contacted X seconds ago" overlayed every minute, that's sure an improvement. Do note, however, that it keeps your shell running with no way to reattach to it if your machine turns off.
Idk, XDG is weird."Music", "Documents", "Downloads", "Public" and "Templates" are in Ukrainian;"Public" and "Downloads" are duplicated in English; "Desktop" is just English;"Images" is in Russian for me for some reason.
No Projects despite me updating recently, I guess it just gave up.
Most compromised routers scrape the hostname (both regular and mDNS) and MAC address. What you do is disable mDNS related daemons like kdeconnect and avahi (until you want them) and put this in /etc/NetworkManager/NetworkManager.conf:
(yes, the mdns bit above is a bit redundant, but systemd has something related that might read it and better be safe than sorry)
This won't protect you if the router is a bit smarter and can see your NTP server (usually like "x.archlinux.pool.ntp.org" instead of just "x.pool.ntp.org"), your connectivity check (same as NTP) and other servers your machine connects to (like Tor nodes if you have the daemon running and oftc.net if you have an IRC client). The good news is that none are known to check that (at least to me).
Well, that's quite ironic, because their fiscal sponsor and biggest donor (in both directions) is "Hack Club", which insists you use GitHub and Figma everywhere and lies to you about deleting your data (source: me, you will have to take my word for it).
So performance? Idk, I zone out or go get a glass of water whenever something's compiling or some bloatware is trying to launch. Probably like 0.x second improvements (in addition to the random "faster paths" the maintainers add from time to time regardless).
drivers, mesa/vulkan
I have an AMD APU, kind of sharing a lot of code with the Deck hardware. GPU suspend was broken twice (when the machine was new + 2 weeks ago). Oh, and whenever my uptime exceeds like 10 days or so, it sometimes decides to wake up to a black screen with my cursor (and the entire plymouth shutdown screen) being colored stripes. Now, the popularity of the Steam Deck made navigating issue trackers near impossible. Constant dump of random bullshit daily. Lots of shit is being closed as duplicate of other bugs which are slightly different but "close enough".
gamescope
If we are talking about impact, may as well mention that they could have forked cage or something for the compositor.
proton
Cool. The ReactOS/Wine people do most of the work on matters other than obscure graphics and application specific quirks though. One must really hate themselves to understand Win32 internals in the first place, so you have to give them credit. Also, Valve's fork is often pretty outdated to upstream which is why lots of people are using the third party fork of the fork that rebases with the original (Proton GE).
Ngl, I was a user the whole time, before and after, and can't tell a difference. Except maybe slightly better HDR support? They mostly donated to KDE tho (!= the kernel).
With the wording of "without restriction", the GPL could be arguably "too restrictive". Well, probably for a court to decide. I guess 9front is safe regardless...
If there's no
ForceCommand(I think that's what it was called?) in sshd.conf and nocommand=xin.authorized_keys(if any), you can probably usemosh. It spins up SSH to authenticate and then immediately start a UDP based connection afterwards. Instead of logging out every 15 minutes, you will get a "Last contacted X seconds ago" overlayed every minute, that's sure an improvement. Do note, however, that it keeps your shell running with no way to reattach to it if your machine turns off.