Anarchism

Your warning will not arrive in time, for enough comrades to act upon efficiently.

A "smoke out" has two mechanisms; denial of an area, and the flushing of the game towards pre-planned lanes.

With the tangle between the agreements of the 5 eyes, there are already various levels of oversight (from little rooms at AT&T, to black boxes on the intercontinental cables themselves) at the T1 level to leverage pressure even if not outright control.

With money and heavy handed laws, the T2s and T3s can and have been coerced and curtailed.

That's just data integrity at the backbone level, before you decide if Hetzner or OVHcloud can be trusted at the moment to move the e-zines to.

Far too many comrades still transmit topics of importance over the Internet at all, and not all with the appropriate rigor, let alone selecting friendly infrastructure they can network through to without hitting the open Internet until and how they're ready.

And what's friendly today to host at today, will change tomorrow, and also likely swap back to being safe on Sunday, before Monday rolls around...

Resilient systems must rely on adaptive networking with these and other concerns in mind, and they must be able to react faster than the SysAdmin can sprint out of bed.

Your instance knows what it's about and how to handle some (or most, or all, we don't go into that here) of that, but most others don't, by design.

Positions of responsibility are best discussed and settled at the canteen, but they also often must be undertaken by those who can recognize the need, and with explanations and a willingness to accept the reckoning for them afterwards.

That's what separates the values of those who might nod along at your instances' "about" information, and those who are by nature predisposed to forever crave the comforting embrace of hierarchy under a different name.

Be ready.