Ask HN: A Fault-Tolerant Internet (Or Untangling the Cybernetic Supply Chain)
Bootstrapping of a country's communication system sounds nightmarish enough, but it's flat out impossible if all the software and hardware has built-in assumptions about what should be able to access on the other side of the world. I reckon it's no good to spoof a remote server location without the corresponding information and credentials. What will software updated look like when security certificates are out of reach?
Even the development and deployment of such contingencies is at risk. Worldwide, software developers rely on online resources and services in their usual workflow (hosting, version control, plugins, testing, coordination efforts, documentation, good ol' copy-pasting, Stack Overflow, etc). And even taking software for granted, hardware guys would need to deploy the changes in logistical darkness if done post hoc. Implementing this could be incredibly costly and disruptive for any nation, but if it is imperative the sooner the better. IT staff would get overwhelmed one way or the other, preventing or fixing it. And all of this working against unknown deadlines, utilizing services that might go offline at any time because of obscure chains of dependencies. Y2K sounds like a walk in the park all of a sudden.
So when does push come to shove? Should any country worry about the possibility of going offline? Can anything even be done to mitigate it?