This is Iran's third total internet shutdown, but the methodology has evolved into something far more surgical. They didn't just block IP addresses; they severed BGP routes, killed mobile data, and effectively jammed Starlink signals into a dead zone thanks to Russian imports. When the signal itself is murdered, your Tor bridges and VPNs become expensive paperweights.
As builders, we are being out-engineered. We have grown complacent, assuming the "always-on" cloud is a fundamental constant of the universe. But if your software requires a remote handshake to function, it is a liability, not a tool, in a crisis zone. Every application built with heavy reliance on centralized APIs vaporizes the moment the backbone is cut.
We must stop designing for the "connected" illusion and start building for the darkness.
This is my plea to the HN community: stop treating "offline-first" as a niche feature and start treating it as a human right. We need robust, decentralized mesh networks that bypass state-controlled gateways entirely. We need isolated documentation tools and local-first databases that can sync via Bluetooth or physical handoffs.
Build for the 212 regions that went dark last year so that the next time a state pulls the plug, the people aren't left helpless.
a throwaway account for obvious reasons (they have also Chinese tech to track); make your code work when the world goes quiet.