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.
It's easy to dismiss as an ad. I did, too.
Well, Vivaldi's built-in in adblock apparently agrees with this categorization. The video shows up if I disable it. Lol
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)
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
manufacturers can put it where your hand naturally rests, meaning that you can unlock the phone BEFORE you have even taken it out of your pocket.
Idk, my "unlock" finger naturally rests wherever the fingerprint scanner is on my phone. When I had a rear fingerprint scanner, I used to have my phone's bottom right corner planted into my palm near the thumb and used the index finger to support its back near the scanner, so I was always ready to unlock it.
Now that I have an under-screen scanner, I use my pinky as a "shelf" for the phone's bottom side, ring finger to hold it on the far side and index finger along the near side (which makes me suspect this grip would work for in-power-button scanners too), and that makes my thumb naturally rest exactly on the spot where the scanner is. With (one) tap to wake, I have no problem unlocking the phone while taking it out of my pocket - literally just a quick double tap. Although it's true that you can't unlock the phone directly in the pocket like this, because the proximity sensor should prevent the tap to wake from working.
I used to have a phone with a scanner in the power button too, but I can't remember how I held it - I don't think it was the same way as now, because I'm pretty sure I never used to rest my thumb on screen like this.
But it's a design for designs - it tells you how to design your own UIs, it doesn't dictate what for example a calculator app should look like. You can follow Material Design and still end up with a terrible UI design.
Surely that's enough for some distinction, right?
@Markaos
@lemmy.one