saool

Anecdotally...

Having spent time driving in both Europe and Southern California, I'd say that European drivers are more attentive to their driving and way less likely to be looking at their phone while driving, since it's policed. You can often see drivers in SoCal holding their phone for a video call.

The Skagen Hybrids (cell battery powered for 4+ months) are the best I've found for this low-tech approach, much more so than any Garmin.

Sorry, I should've specified that it's impossible as the standard is written, not necessarily cryptographically impossible.

A scheme could definitely be devised to add authenticator "stubs", but I don't think it's possible right now.

Unless you're saying the above is already available in the spec.

1, 2, and 4) Yes, that's already possible. Look into Solo Keys for open source hardware and firmware. The standard allows for key manufacturer attestation but seems like the way it is going (especially with the proliferation of software authenticators) it likely won't be relevant in practice. You can also enroll many authenticators to the same account (provided the service allows it, which most do).

3) This is pretty hard/impossible, I think. The authenticators don't use the same key-pair for all websites (a la SSH through Yubikey), but rather create a per-service, per-credential key-pair, and encrypt it with the main key-pair. The encrypted credential key-pair is then handed off to the server for storage, and the service sends it back for the authenticator to decrypt and use during a challenge. Clever trick to not depend on local hardware memory and be able to have unlimited per-credential key-pairs, but afaik prevents you from just "adding lists of public keys".

I'm also not mentioning the resident keys aspect of the standard but that won't fix it as they're still service and credential based.

In the typical case and handwaving a bit:

On registration, the server is handed a site/user-specific key pair _encrypted_ with the master key of the authenticator device (your usb key or your phone, etc), together with the plain-text site/user-specific public key.

On authentication, the server sends down that encrypted blurb, which is temporarily decrypted and then used to sign a challenge the server sent.

So basically the server is used as storage. There are exceptions to this (e.g. resident/discoverable credentials on hardware keys)

For an industry so enamored with scale and network effects, we sometimes fail to recognize how these work against us organizationally. Or maybe we don't, and the boards/execs just prefer a more controllable organization even at the expense of rigidness and efficiency?

wireguard (or tailscale) + sshd + VNC (macOS screen sharing) server bound only to the virtual interface or firewalled.

As long as we are talking (de)colonization, the distinction makes all the difference.

The difference in the treatment of a land and its people as equals to the rest of the country's citizens and states is what makes Hawaiians regular Americans and Ceuties regular Spaniards, and what keeps Llanitos from being British _citizens_.

To answer your question: yeah, if Gibraltar was a self-sufficient state within the UK (instead of an -arguably- geo-strategic colony that is a tax haven according to the OECD) you likely wouldn't hear as many complaints about it.

Take for example the cession of Sardinia in the very same Treaty of Utrecht. You ever hear complaints about its sovereignty?

Not only is that a tu quoque fallacy but it also fails to take into account that both Ceuta and Melilla are integral parts of Spain and have been since the 16th century, centuries prior to Morocco's independence from France in 1956, whereas Gibraltar, being a British Overseas Territory, is not and never has been part of the United Kingdom.

I wouldn't extrapolate.

Most places in Spain have and need heating, apart from a few coastal enclaves in the south. Spain is the 5th largest user of energy for residential heating in the EU, behind Germany, France, Italy, and Poland.