Is there?

Bold of them to reinvent something that hadn't been invented yet.

While that’s true, it’s also still not monochromatic in the electromagnetic sense.

But it's really simple:

- The "let's leave the EU" side won in the UK, no question - The UK entered a period where it struggled to figure out what "Get Brexit done" meant - Eventually they figured that out, it was pretty much the shape that was expected, and did it.

What you have described as "threats" are clearly examples of what you would expect the impact of leaving an integrated union would be. That includes negotiating the terms of the departure, and the EU was obviously in the interests of the EU.

I'm honestly just baffled that you think otherwise. The UK chose to leave the EU – fine. The EU acted to protect its interests in that exit – also fine. Weird to get so threatened by things that turned out to be obviously true.

I think you're just projecting, to be honest. The "leave the EU" side won; unexpectedly, with no clear vision of what that involved. And then the UK's internal inability to agree resulted in a tumultuous period of internal politics, the result of which is pretty much the outcome we'd've all expected.

Time to get over it, I think.

It being “fought” or countries being “penalised” is a matter of opinion but not one I share.

I'm actually quite surprised by the number of people who have fallen for this. There aren't even any concrete claims here – just the vague assertion that some things are "impossible".

I mean come on – the point literally could not be more clearly expressed.

The "London has fallen" trope that has been prevalent on social media recently stank of some kind of deliberate manipulation. But increasingly—in part due to stories like this—I wonder if it is actually just all "for the views".

This can all be automated using e.g. the Terraform Tailscale provider, which takes the OAuth id/secret and can then issue keys as needed for the infrastructure you are deploying.

We use this for debugging access to CI builds, among other things – when a particular build parameter is set, then the CI build will use an OAuth key to request an ephemeral, single-use access key from the Tailscale API, then use that to create a node that engineers can SSH into.

Access keys ideally should be short-lived and single-use where possible. https://tailscale.com/kb/1215/oauth-clients#generating-long-... has details on this flow.

Edit: in fact from your original post it sounds like you’re trying to avoid re-issuing auth keys to embedded devices. You don’t need to do this; auth keys should ideally be single-use and are only required to add the node to the network. Once the device is registered, it does not need them any more - there is a per-device key. You can then choose to disable key expiration for that device.

Some people are happy to release code openly and have it used for anything, commercial or otherwise. Totally understandable and a valid choice to make.

Other people are happy to release code openly so long as people who incorporate it into their projects also release it in the same way. Again, totally understandable and valid.

None of this is hard to understand or confusing or even slightly weird.