Think about it.
They've been streaming the entire time since they launched. The timing tied right in with the Tulsa conference. The timing ties right in with the Chauvin trial. The timing ties right in with the audit of the ballots in Arizona They are performing load testing.
If they can keep this system up, they can communicate with ALL of us. We can then relay this information to our friend, neighbors and communities.
They can't shut the entire Internet down. Frank is the Hub, we are the Spokes.
We are the DIGITAL ARMY.
Shutting down the entire internet is actually very simple. There are about 10-15 machines that could do the job, but it would probably take at least 3, maybe more (half?) of them agreeing to shutdown for full shutdown to happen.
That is on the "civilian" side. I don't happen to know how many "military" machines are in a similar authoritative position, but I'm presuming way more than a dozen. Military shutdown could also (presumably) impact infrastructure outside of the network context, to achieve a more "hard" and/or more secure shutdown.
Depending on how and why a shutdown were to occur, it is likely that large swaths of the network would continue to operate, just isolated. Without backbone-level support, and under even a small fraction of normal loads, even that would be at dial-up-like speeds if you're lucky.
Bullshit. Shutting down a network specifically designed to survive a nuclear war "is actually very simple" - my ass. Total bullshit.
Don't listen to ass-hats like this idiot. The Internet is very resilient, by design. I'm not saying there couldn't be some problems, but they would be regional at worst... and only temporary.
Yes, don't listen to me. Just try throttling your speed to 15-30kbps, blocking DNS, and revoking all security certificates. That's just the superficial layer.
Maybe you understand network administration, and you can get around the superficial stuff. Now imagine that your ISP is where the throttle is, all of their security certificates are revoked, and their DNS and routing tables are corrupted. Good luck getting a route. Once you get a route, good luck getting a browser to consume the encrypted content you painstakingly tried to download.
Oh, yeah, this is all temporary, right. How many hours? Days? Why did it happen in the first place? How? Was it an instantaneous event, or an ongoing event? What else could go down, besides superficial protocols, in such an event?
Don't listen to ass-hats like this idiot.