The day the internet dies, you won’t be streaming anything. You won’t be uploading anything. You won’t be sending that Slack message, checking that cloud backup, or pulling that critical file from a server three time zones away.
You’ll just be sitting there. With a laptop. And nothing.
It’s a scenario most of us dismiss as science fiction — until the AWS outage, the undersea cable cut, the natural disaster, or the infrastructure attack that makes it suddenly, terrifyingly real.
Now someone has built a backup plan. And it’s equal parts absurd and genius.
Two webcams. QR codes flashing on a screen. That’s it. That’s the entire infrastructure.
The throughput? About 20 KB/s. To put that in perspective, transferring a single photo from your phone would take roughly a minute. A full document might take several. A video? Forget it.
20 KB/s sounds like a joke until it’s the only speed that exists.
Here’s what makes this more than a novelty: the protocol includes a sliding-window ACK/retry scheme for reliability. It does ECDH key exchange with fingerprint verification — because when your communication channel is literally a QR code displayed on a screen, it doesn’t get more public than that. Someone built cryptographic security for a protocol that transmits data through a camera looking at a screen.
That’s not a toy. That’s first-principles engineering.
Most of us never think about how many layers of dependency sit between “I have a file” and “you have the file.” There’s the local network. The router. The ISP. The DNS system. The backbone. The server. The cloud provider. The data center. The power grid. Each one is a link in a chain, and every single one can break.
Every layer of abstraction we add is another layer that can fail. And we’ve been adding layers for decades without asking what happens when they all fail at once.
This project strips it all away. No internet. No servers. No cables. No Bluetooth. No WiFi. Just two cameras and two screens, blinking at each other like two people signaling with flashlights across a dark canyon.
The ingenuity isn’t in the speed — it’s in the reduction. What’s the absolute minimum you need to move information from one machine to another? A display that can change. A sensor that can read the change. That’s it. Everything else is convenience.
And convenience, it turns out, is the enemy of resilience.
Think about it: when was the last time you had a file transfer method that didn’t depend on at least three third-party services? When was the last time you moved data between two devices without routing it through someone’s server, someone’s cloud, someone’s network?
We’ve built a civilization that can’t function without WiFi, and we call that progress.
The developer who built this understands something that most of the tech industry has forgotten: resilience isn’t about adding more redundancy to fragile systems. It’s about building systems that work when the fragile systems disappear.
Yes, 20 KB/s is painfully slow. Yes, pointing a webcam at a screen feels ridiculous. Yes, in the normal world, this solution is nearly unusable.
But the normal world is a recent invention. And it’s more fragile than we think.
The undersea cables that carry 99% of international data are sitting on ocean floors, unguarded. The data centers that run our cloud infrastructure depend on power grids that have already shown they can fail spectacularly. The satellites are reachable. The routers are hackable. The DNS system has been taken down before.
The most fragile thing about our digital infrastructure isn’t the technology — it’s the assumption that it will always be there.
This protocol won’t replace your fiber connection. It won’t replace your cloud backup. It won’t replace anything you use on a normal Tuesday.
But on the day that nothing works — the day the cables are cut, the servers are dark, and the networks are silent — two webcams blinking QR codes at each other might be the only way to move a critical file from one machine to another.
And on that day, 20 KB/s won’t feel slow. It’ll feel like a miracle.
FAQ
Q: Isn't 20 KB/s so slow it's basically useless?
A: In the normal world, absolutely. But this protocol isn't built for the normal world. It's built for the scenario where every other option — internet, cellular, Bluetooth, even physical cables — is gone. When the alternative is zero KB/s, 20 KB/s is infinite.
Q: What's the practical takeaway for someone who isn't prepping for doomsday?
A: It forces you to audit your own dependency stack. Count how many third-party services sit between your data and the person who needs it. If that number scares you, you understand why this project matters.
Q: Is this actually serious engineering or just a clever hack?
A: The sliding-window ACK/retry scheme and ECDH key exchange with fingerprint verification tell you everything. This person didn't just make QR codes flash — they built a real network protocol with reliability and security, adapted to a visual medium. That's systems engineering, not a weekend toy.