What I find to be a rather interesting tidbit related to this is that some applications (e.g. certain garbage collectors) map multiple ranges of virtual memory that address the same physical memory.
There are ways to avoid having buses stuck in traffic. Dedicated lanes for public transport, getting more people to use public transport rather than cars, and so on. So I'd say it's more often than not a choice in planning if it's convenient compared to using cars or not.
(There's also the problem of less developed systems often being less convenient, and because of it not having the funding needed to expand due to low usage)
Especially considering that OP posted a link to uniqkey a couple months ago on HN (not necessarily wrong, but considering that downloading the "whitepaper" also asks for a bunch of PI...)
The idea is that you aren't giving away any kind of biometric data, just using your fingerprint/face-unlock/etc to "unlock" the key used for signing the request locally.
It could also be implemented in a way where it's behind a password instead of biometrics. Yubikey and the likes already use this method.
It's not what they're doing here, but you should be able to read the biometric chip using a phone and verify the data that it contains server-side (since it's signed). Not sure how easy it is to get hold of the public keys though.
Which also would be a nice feature if it could be implemented here, might be possible with WebNFC :)
But the new connector is still only rated for 600W (if used within spec), if we directly compare that to using 4 of the old connectors (rated at 150W each) we're spreading the same load over many more pins.
A 12VHPWR connector is using 12 pins for GND/12V.
An 8pin PCIe connector has 6 pins for GND/12V, with 4 connectors that's 24 pins total.
Assuming that the pins are fairly similarly specced, the old connector should be safer, especially when exceeding the rated power. Regardless of how you frame it, it seems like aesthetics got prioritized over safety.
Even easier to use the old standard instead of making a new solution to a problem that didn't exist in the first place (except for aesthetic reasons).
The old connectors were solid and had plenty of headroom if used within spec, with the new cards you'd still just need 3-4 to be well within spec - no monitoring circuitry needed.
At least Webhallen in Sweden sells them in physical stores around the country. Not sure about other places though.
Weirdly enough it's also cheaper to buy a 12m card there (500SEK instead of the usual 600SEK). Checked, and they're listed as a reseller on Mullvad's page so they must've gotten a good deal / are selling at a loss.
Terrible (for 2.4/5GHz). They seemed to have worked around there not being a lot of hobbyist receivers by buying toy submarines that use lower frequencies like 40MHz and used the boards from there, nifty but seems very limited.
You could surely still have this for non-genuine / used batteries, but here we have a genuine battery coming straight from Apple throwing that warning. Just let 3rd party repair shops buy them at a reasonable price and don't throw the warning if it's unused.
Edit: and preferably let them buy the batteries in bulk, without having to have the phone on hand which just causes unnecessary delays.
Isn't that way too extreme? Firefox and Chrome don't share a lot of similarities, except arguably both implementing manifest v3 after Google's push, but even those are fairly different.
(in reply to krehl) And in that specific case you should probably have a DPA ready. Big issue with anything Google-related (and probably CloudFlare) is that they may transfer the data outside of the EU[0].
Wouldn't a better alternative be a summary of the 300 page document? Both that and a FAQ wouldn't be the canonical sources in a legal capacity, but a summary has the benefit of deduplication and is probably nicer to read (depending on how much you want to cross-reference in the FAQ)