someone just plain lying about what OS they're using in order to break fingerprinting.
The idea with avoiding fingerprinting is to look like whatever the biggest group of users looks like, because that's who you share the fingerprint with. If you use an uncommon value for something, you make fingerprinting easier.
That's one of the reasons why for example Vivaldi on Linux sets its user agent to match the latest version Chrome on Windows.
That really depends on the technology used. For example, all modern Ethernet standards (which includes both copper and fiber optic) are full duplex, meaning they can provide the full bandwidth in both directions at once. So a gigabit Ethernet link can do a gigabit in one direction AND a gigabit in the other direction at the same time (but not two gigabits in one direction).
In my very limited experience with my 5400rpm SMR WD disk, it's perfectly capable of writing at over 100 MB/s until its cache runs out, then it pretty much dies until it has time to properly write the data, rinse and repeat.
40 MB/s sustained is weird (but maybe it's just a different firmware? I think my disk was able to actually sustain 60 MB/s for a few hours when I limited the write speed, 40 could be a conservative setting that doesn't even slowly fill the cache)
Fair enough. I misunderstood, my bad.
Then what's the meaning of this whole part?
On non-corpo linux syslog can be disabled if you want, though I'd prefer to just symlink/mount /var/log to a memory filesystem instead.
Is it just a random tidbit that could be replaced with a blueberry muffin recipe without any change of meaning of the whole comment? Because it sure won't help OP at all with their Arch-specific question, so it's either that, or it provides contrast to the "corpo Linux", which is how I interpreted it.
And here's the remaining part of your comment I left out, just to make sure people won't lose the context between two three sentence long comments (for those without any attention span, it comes before the previous quoted part):
If you're on arch you use redhat's garbage.
On non-corpo linux syslog can be disabled
systemctl disable --now systemd-journald
I'd prefer to just symlink/mount /var/log to a memory filesystem instead
Set Storage=volatile in /etc/systemd/journald.conf
Your mileage may vary - your experience might be different for one reason or another
How is it open source?
How is it not? Open source doesn't mean you have to accept other people's code. And it is perfectly valid to only dump code for every release, even some GNU projects (like GCC) used to work that way. Hell, there's even a book about the two different approaches in open source.
So whatever benefit you were hoping to get from Nvidia's kernel modules being open source probably is not there.
It allowed the actual in-tree nouveau kernel module to take the code for interacting with the GSP firmware to allow changing GPU clock speed - in other words no more being stuck on the lowest possible frequency like with the GTX 10 series cards. Seems like a pretty decent benefit to me.
What's Steve?
~~Probably a bit of a TL:DR of the other answer, but the short answer is:~~ the execute bit has a different meaning for directories - it allows you to keep going down the filesystem tree (open a file or another directory in the directory). The read bit only allows you to see the names of the files in the directory (and maybe some other metadata), but you cannot open them without x bit.
Fun fact, it makes sense to have a directory with --x or -wx permissions - you can access the files inside if you already know their names.
Edit: not a short answer, apparently
You can now turn on the “autoscrolling” feature of the Libinput driver, which lets you scroll on any scrollable view by holding down the middle button of your mouse and moving the whole mouse
Am I crazy, or did this used to be a feature? And not just in Firefox
It's a Windows feature that never really made it to Linux. I used to miss it but honestly, middle click paste feels way more useful to me now
The comment you replied to is a direct reply to the comment you linked - I don't think it was intentional, but if it was, then I'd like to say it's not a very helpful reply as OP already read it.