They probably couldn't get google drive to work without 3rd party cookies.

Meanwhile over in Europe - went to the doctor in spring as a cough didn't go away for ages. As suspected nothing he could do much - irritated throat, and just at the time when cold season was giving way for allergy season. So he prescribed some nose spray - and asked if he should also add some antihistamine to the prescription to save me a few eur (didn't check, but it probably is single digits. That stuff is cheap)

Nowadays it matters if you use a compression algorithm that can utilize multiple cores for packing/unpacking larger data. For a multiple GB archive that can be the difference between "I'll grab a coffee until this is ready" or "I'll go for lunch and hope it is done when I come back"

Is it a ‘death by quantity’ thing?

Pretty much that - those companies rely on open projects to sort it for them, so they're pretty much scraping open databases, and selling good data they pull from there. That's why they were complaining about the kernel stuff - the info required was there already, just you needed to put effort in, so they were asking for CVEs. Now they got their CVEs - but to profit from it they'd still need to put the same effort in as they'd had to without CVEs in place.

Make sure you use a long extension cord to a fuse without RCD for the hair dryer, though - otherwise the constant resetting of the breaker will eat up all your time savings.

A major difference is how they interact with feedback - the main reason I never did my own mastodon instance is the developers attitude. "We're not interested in helping you because you didn't set it up exactly as in the guide" was (and maybe still is) all over the mastodon bug tracker.

That was the first thing I looked for when lemmy became popular - and found they were taking deployment issues to even the most absurd system seriously.

Additionally they treat suggestions seriously - even if they personally think it is stupid - and even implement some of that. Pretty much no chance of anything of that happening with mastodon.

I don't think infotainment systems need a concept of copy/paste but having to write:

Having lived through the whole "phones don't need copy and paste debate", which fortunately got solved by now having it everywhere I'm in the camp "just stick that everywhere, just in case somebody might use it one day"

That attack is via bluetooth, not NFC. And the article states exactly that (just checked).

Pretty much everybody pushing fingerprints as a sensible thing for accessing a device is fucking up. It is way too easy to obtain a persons fingerprints suitable for device unlocking without them knowing - and that's ignoring that using fingerprints enables device unlocking with a persons finger against their will.

It wasn't really a replacement - Ethernet was never tied to specific media, and various cabling standards coexisted for a long time. For about a decade you had 10baseT, 10base2, 10base5 and 10baseF deployments in parallel.

I guess when you mention coax you're thinking about 10base2 - the thin black cables with T-pieces end terminator plugs common in home setups - which only arrived shortly before 10baseT. The first commercially available cabling was 10base5 - those thick yellow cables you'd attach a system to with AUI transceivers. Which still were around as backbone cables in some places until the early 00s.

The really big change in network infrastructure was the introduction of switches instead of hubs - before that you had a collision domain spanning the complete network, now the collision domain was reduced to two devices. Which improved responsiveness of loaded networks to the point where many started switching over from token ring - which in later years also commonly was run over twisted pair, so in many cases switching was possible without touching the cables.

You did receive credit. A good bug report allows reproducing and ideally fixing the issue - which can involve considerable effort. This is the difference between your report, and the one you linked from 6 years ago.

Like I said, I'd probably have added an additional thanks for that in my commit message - but I'm unfamiliar with the kind of reports this particular subsystem typically receives, so it is quite possible your report is just something average coming in there.

I personally prefer to include code suggesting a fix in my bug reports - but I usually don't expect it to be just merged as I'm not familiar with surrounding code. I also don't expect that to receive an additional mention - it's just part of the report, and is often cleaner in demonstrating the issue than a problem description.

"Salaried worker" over here means just that you're being paid for fixed, regular working hours - typically something like 37.5 or 40 hours per week. Anything on top of that is overtime, which needs to be compensated either in time off, or paid out.

On call rules also vary a lot by country, but typical it's something like being paid 20-25% of your regular hourly wage while on call, with overtime pay when you're taking a call.