I’d say I’m a “time-strapped” user since I have a full time job and I’d rather spend my free time gaming rather than fixing a broken OS, nevertheless… I have 2 PCs with Arch Linux (one for personal stuff and one for work) and a server with NixOS.

When things break on Arch (which is rare these days but it can happen, especially if you play around with things from the AUR), I just rollback with timeshift (it takes just a few seconds with btrfs) and try that update again in a few days. Minor issues I can just ignore or work around them and take care of them when I feel like it, but they usually get fixed with updates within a few days. The only time I felt that it was actively wasting my time was when Plasma 6 came out a few months ago and a lot of little things broke, especially on wayland, but they were fixed rather quickly with 6.1 so I can’t complain too much.

NixOS on the other end has been nothing but trouble and a waste of time ever since I installed it. It took me a week to configure it, some packages are kinda old, most have incomplete declarative config, I had to manually write some units myself, and when things break it drives me crazy because even basic troubleshooting of services can be a pain in the ass because I have to find out where stuff is, know which config files are going to be overwritten, launch the correct nix-shell, … it’s all so tiresome… so I just revert to an older config and hope for the best. To make things worse, major updates often require manual changes to the config or even to application files themselves (looking at you, nextcloud) and you will excuse me if I can’t be bothered to do that on a DECLARATIVE DISTRO. Even debian doesn’t need that, come on! I don’t care what people say on NixOS, this OS is not ready yet, I don’t have time for this shit when I’m working and that server will be going back to debian next summer.

I think I might be the only person who bought a 9950x on launch and was actually very happy with it. Not only it performs excellent, but unlike its predecessor, I can actually use it with air cooling, it’s a very efficient and powerful CPU.

Arch Linux. Everyone said it was hard to use, unstable, etc. but my experience with it has been the exact opposite.

Yes, the install process is needlessly complicated (although it got a lot simpler now that we have archinstall), but the OS itself is rock solid and rarely has any issues that require more than a reboot or a package reinstall to solve. The AUR is a godsend too if you don’t want or don’t know how to compile stuff from source.

I already had a script on the router that I used to notify me of network outages, IP changes, keep the DDNS updated, etc. and I thought it was easier to just add a couple lines to that

The jitsi user is a system user so it can’t login even if you set a key for it. Besides, I wouldn’t risk it anyway since that user is in the docker group, if it gets compromised somehow, the attacker would have very high privileges.

I think this one beats them all.

My home server keeps a few services up, including an instance of Jitsi Meet. The server runs nixos and the nixos package for jitsi is incomplete to say the least and doesn’t even support authentication, so I use the docker-compose version and I have a script that runs periodically to keep it updated. So far so good, right? Well, no.

Because the server is at home, I have a dynamic external IP address, so I have to use a DDNS provider, but jitsi doesn’t expect this and uses a stun server at startup to determine the public IP of the server once, so if my connection goes down or is restarted and the IP changes, jitsi needs to be restarted or it won’t work anymore.

The solution?

• My router runs OpenWrt, so I am able to run a script that checks for external IP changes. When a change is detected, it uses SSH to connect to my server to restart jitsi
• Because I don’t want the router to just be able to run any command, I created a jitsi-restart user that has no shell
• When the router tries to log in with its pubkey, sshd creates a file called restartasap in the jitsi folder and closes the connection
• On the server, there’s a systemd unit running a script as the jitsi user that periodically checks for that file, and if it exists it deletes it and restarts jitsi

I’ve been running this setup since mid 2020 and I expect this to continue until IPv6 becomes the norm.

I switched for good in 2019, when I realized that I was wasting more time getting windows into a usable state than the average arch user.

Privacy and usability were the biggest reasons for me.

Good idea, I’ll add it to the to-do list for the next major release.

Occasionally some cloud providers or ISPs chime in and offer their servers to the public. If you have an LS server, you can submit it here: https://librespeed.org/submit

I’m the author of the project. The servers are simply overloaded af unfortunately. It’s a fairly popular project and we don’t have enough servers to support this many concurrent users.

It doesn’t need javascript from “20 different domains”, only a file called empty.php is fetched from those servers to measure the ping. The javascript is hosted on librespeed.org, which is under my control.

Hi, I’m the original author of LibreSpeed. When you load the website it downloads a list of servers and tries all of them to see which one has the lowest ping, that’s what you’re seeing.

It means it’s what we in the trade call “a nothingburger”. On Windows you need to explicitly install a malicious driver (which in turn requires to you to disable signature verification), on Linux you’d have to load a malicious kernel module (which requires pasting commands as root, and it would probably be proprietary since it has malware to hide and as every nvidia user knows, proprietary kernel modules break with kernel updates)

Framework is not a FOSS project, it’s not a charity or a non-profit organization, it’s a company. Would you volunteer to work for free at your job?

Nah mate, 2022 was when it started getting really good, GPL got rid of shader compilation stuttering (as well as dxvk-async related glitches), compatibility improved massively with improvements to both dxvk and vkd3d, and ray tracing finally started working

I’ve seen this happen after switching to wayland. Changing the cursor size and then changing it back solved the issue for me.

I know, I know :)

I reported the bugs I’ve encountered but I don’t have time to install another distro right now. I’ve seen some of those bugs (scaling) on the KDE neon live iso though.

I’ve been using it since Plasma 6 came out so about 3-4 weeks.

Overall, it’s been a very negative experience for me. The main problems have been:

• Random scaling issues in apps: some apps show a slightly smaller cursor, other show a poorly upscaled one, others have random rendering issues like lines remaining on the screen after an option is no longer highlighted (gimp, libreoffice, many others), some apps have random flickering of parts of the UI, some apps no longer scale at all or are scaled twice. Plasmashell itself has blurry icons on the desktop but all other KDE apps don’t. I know fractional scaling has always been problematic, but it has gotten worse to the point of being almost unusable
• Random crashes of GTK apps when using the wayland backend. Some GTK apps don’t even start and segfault immediately with a wayland error in the terminal
• Some apps like okular and libreoffice lag like crazy or outright freeze when scrolling
• Some games not capturing the cursor properly (Proton)
• Inconsistent font rendering, some fonts look fine in some apps and atrocious in others
• Issues when resizing or moving windows, some times they “jerk” off the screen or resize to a very tiny window and I’m forced to use key combinations to resize them again
• Random issues with window decoration not appearing in some apps but randomy appearing for things like context menus

This is on a full AMD system with Arch Linux, the latest kernel and mesa-git. I hope for KDE’s sake that there’s something broken in my installation because I can’t believe the KDE team released Plasma 6 in this sorry state.

It’s just bait for investors. This is the kind of crap that gets people with money and zero understanding of computers to buy stocks.

The problem with 5Ghz is that it doesn’t go through walls very well compared to 2.4Ghz, resulting in APs having less range (or having to use several times more power)