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.
When they were installing the alarm at my house I noticed that the main guy had nextcloud on his phone and it sparked a nice conversation about privacy. He has no technical background but managed to self-host it on his old laptop with one of those distros that have an easy UI for self-hosting (don’t remember which one exactly). He’s a pretty cool guy.
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?
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.
Fortnite OS
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.
I know, I’ve been using it since 2010, when it was still called CyanogenMod :)
Wow, I never thought I’d agree with the devs of GrapheneOS on something
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.
Ok, I had no idea they were the first to do that lootbox shite, I’m not into multiplayer games. That could be considered worse than allowing third party DRMs, since it pretty much introduced kids to gambling.
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.