There's a fascinating YouTube series called "The Most Complex International Borders in the World" about enclaves and exclaves. [1] There are even some "counter-enclaves", e.g. a part of the Netherlands inside Belgium inside the Netherlands. [2]
syncthing-lite [1] is already supposed to do what you want for your second point. But it's not really there yet. I haven't managed to get it to work reliably (unlike the original app, which is great).
On Android I've found that the volume that the phone thinks the AirPods are at can get out of sync with reality, the result being that Android's idea of full volume is actually very quiet. (Perhaps I tried to change the volume before they were fully connected?)
Re-pairing them from scratch fixed this. Might be worth a try.
My example was to give quantitative evidence for the speed of contactless transactions.
It is true that there is no barrier in Berlin, but you still need to buy a ticket. For casual users such as myself, who don't have a season ticket, this takes significantly longer than 480ms: find ticket machine, queue, navigate menu, insert cash, wait for change and ticket to be printed, find ticket validation machine.
It is quite possible to miss the train here by having to queue to buy a ticket, particularly in busy places like the airport. This could be avoided if the tourists were able to use their existing cards/phones to tap in.
Plus, I get an instant notification on my phone whenever my card is used. And if I see anything suspicious, I can freeze the card via the app (declining all further payments).
I am visiting Berlin at the moment, and I miss the convenience and speed of being able to pay with contactless, by card or phone.
Regarding the speed of transactions: cash might be faster than signature or even Chip+PIN, but is surely not faster than contactless.
For example, anyone with a contactless Visa/Mastercard or phone can enter the London Underground by simply tapping at the barrier. They do not need to have a pre-existing relationship with Transport for London, to buy a ticket in advance, or to preload a stored-value card (as you generally must do in other city transport networks). And the ticket barriers open on average in 480ms. [1] That's pretty fast. You can't even pay by cash on a bus in London any more.
TCP and UDP are "IP protocols" in that their packets are nested directly inside an IP packet and they have associated protocol numbers [1] to distinguish them from other things that might be inside an IP packet. QUIC theoretically deserves to be one of these too but for pragmatic reasons it has to be nested inside UDP. GP is asserting that `-p quic` will not be implemented, because it would be a layering violation.
`terraform state mv` is indeed the trick. It took me a while to understand it, but this blog post helped. [1] It leads you through refactoring some resources into a module.
The key takeaway for me was "we really only need to consider the nodes that map to the physical resources of our infrastructure when we are planning our state surgery. This means we can ignore all of the nodes that correspond to data sources, variables, and providers."
So after a refactor, this is what I do now: (1) run plan to get the names of everything terraform wants to delete and recreate; (2) pair all the resource nodes manually and translate them to state mv commands; (3) re-run plan and verify that terraform is now convinced there is nothing to do.
It would be nice if terraform could do this for me, of course, but I find that it is generally possible to avoid delete and recreate if all I've done is a refactoring.