You’ve probably noticed the tech world’s favorite fantasy: the idea that if you build a decentralized app, it becomes immune to government censorship. We tell ourselves that peer-to-peer architecture and blockchain magic make software untouchable. But right now, in India, reality is hitting the crypto-utopian dream like a sledgehammer.
The Indian government just ordered GitHub to take down the source code for Jack Dorsey’s decentralized messaging app, Bitchat, amid widespread farmer protests. They didn’t try to block every single node. They didn’t chase down individual users. They just sent a legal notice to the centralized repository where the code lives.
If your ‘uncensorable’ app lives on a server owned by Microsoft, it’s not uncensorable. It’s just temporarily embarrassed.
This isn’t just a story about India or Jack Dorsey. It’s a masterclass in how state power adapts to modern technology. Most observers are obsessing over the app itself, missing the actual strategic strike. The government isn’t just blocking access; they are executing ‘source code censorship.’
When you take down a GitHub repository, you don’t just stop people from downloading the app today. You cripple the ability of developers to fork, improve, audit, and redistribute the software tomorrow. You kill the ecosystem before it can mutate and survive.
You can’t fork a future when the government has already deleted your past.
We have built a massive, multi-billion dollar industry on the promise of decentralization, yet we rely on the most centralized infrastructure imaginable to build, host, and distribute it. We use GitHub for our code, AWS for our nodes, and Cloudflare for our routing. We are building palaces on rented land, acting shocked when the landlord evicts us at the request of the local sheriff.
India’s use of intermediary liability laws exposes a critical blind spot for anyone building or relying on decentralized tech. State sovereignty hasn’t been defeated by cryptography; it has simply shifted its aim. Why fight an unwinnable war against a distributed network when you can just pressure the centralized gatekeepers who hand out the keys?
This move is a blueprint. It’s a subtle, powerful form of control that bypasses the technical robustness of an app and attacks its political and legal vulnerabilities. If your distribution mechanism can be severed by a single takedown notice, your architecture is fundamentally broken.
Decentralization isn’t a shield; it’s just a slightly longer hallway for the state to walk down before it kicks down your door.
If we actually care about digital sovereignty and free speech, we have to stop pretending that a clever protocol can save us from political reality. Without truly distributed hosting and development, our tools remain just as vulnerable as the early internet forums we thought we had outgrown. The state has found the kill switch. It’s time we stop building systems that have one.
FAQ
Q: Can't developers just host the code elsewhere?
A: Yes, but the friction of moving and re-establishing trust kills momentum. The state doesn't need a perfect, permanent block; they just need a chilling effect that disrupts the community and stalls development long enough to win the immediate political battle.
Q: What does this mean for Web3 builders?
A: Your code repository is a massive single point of failure. If you aren't using decentralized hosting for your source code and developer coordination, you are building on quicksand and leaving yourself open to the exact legal pressures you claim to be immune to.
Q: Is Jack Dorsey's Bitchat actually decentralized?
A: Barely. If a government takedown notice to a single centralized platform like GitHub can effectively hobble your distribution and development, your architecture is fundamentally centralized at the points that actually matter.