jwt

I'm not angry, that's in your mind. You seem to have a habit of linking things that shouldn't be linked. Good day.

That has nothing to do with what I was answering to OP (who seems to have a difficult time translating 'operating in' to 'being reachable from'), I don't know why you are trying to debate (?) me on something else completely. Same goes for the www, I've never called it that.

(1) Agreed of course, but I don't see much of an issue there. You try to get a 100% coverage on your blockade, but 99% will move twitter to compliance too. same goes for (2). As for (3), I'm not really sure why you directed that at me.

They're not accessible anymore from a jurisdiction if said jurisdiction which rules they are violating decides to change their networking policies. And because twitter likes to be accessible, twitter decided to comply with the rules eventually. You seem intentionally obtuse btw.

operate in != run from

If you want an apt example of a company 'run from' America not allowed to 'operate in' another jurisdiction:
https://en.m.wikipedia.org/wiki/Blocking_of_Twitter_in_Brazil

TempleOS

Btw also an awesome way of telling people you're pregnant.

fyi, systemctl disable/enable has a --now flag

I heard they recently switched to pagers because cell phones where deemed to be compromised. So I think besides the direct deaths and injuries, this attack also targeted lines of communication and trust in technology as a whole (or anything supplied by your superior even).

"Absolute honesty isn't always the most diplomatic nor the safest form of communication with emotional beings".
— TARS

--force-and-I-really-mean-it-this-time

Keep in mind an unencrypted /boot partition still leaves you open to an evil maid attack. I'm not really paranoid (or interesting) enough that I feel the need to take measures to prevent those kinds of attacks, but your situation may differ.