The Indian Government Just Gave GitHub a Choice: Break the Internet or Fight Back

Imagine a chat app that no one can shut down. Not a dictator. Not a government. Not even the company that made it. That’s Bitchat. And last week, the Indian government tried to kill it.

On the surface, this is just another censorship story. The government ordered GitHub to remove the repository for Bitchat, a decentralized messaging app built by Jack Dorsey’s team. The reason? People were using it to organize protests against the CJP (Cockroach Janata Party). In other words, citizens were coordinating dissent. And the government didn’t like that.

Decentralization isn’t just a feature — it’s a declaration of independence.

You’ve probably used WhatsApp or Telegram. Ever wondered what happens if the government asks them to block your group? They comply. They have to. Centralized servers mean a single point of failure. But Bitchat is different. There’s no server to seize, no company to pressure. The code lives on GitHub, and the network runs on thousands of devices. The only way to stop it is to delete the source code itself.

That’s exactly what the Indian government is demanding. And now GitHub faces a choice that will echo far beyond this one app.

Here’s the real story: most commentary focuses on censorship. But the real tension is about who controls the infrastructure of the internet. GitHub is a platform — a neutral host for code. But neutrality is a myth. Every time a government demands a takedown, GitHub has to decide: comply and risk being a tool of oppression, or refuse and risk being shut down themselves.

GitHub’s next move will set a precedent for whether code is speech or just a product.

This isn’t an abstract debate. I’ve seen this firsthand. When the Indian government blocked hundreds of apps in 2020, they went after the infrastructure. They forced ISPs to block domains. But decentralized apps don’t have domains. They have code. And code can be forked, mirrored, shared. One user already tried to mirror Bitchat on nonograph, but the links were automatically removed. The cat-and-mouse game has begun.

The stakes are enormous. If GitHub complies, they signal that any government can silence any decentralized project by targeting the code repository. If they refuse, they become a target themselves — a legal battle that could define the next decade of internet governance.

This is a modern David and Goliath story, where the slingshot is a few lines of code. The Indian government represents the old world — borders, control, sovereignty. Bitchat represents the new world — borderless, peer-to-peer, unstoppable.

The only thing more dangerous than a government that fears its citizens is a technology that makes that fear irrelevant.

So what happens next? GitHub hasn’t responded yet. But the clock is ticking. And the answer will tell us whether the internet is still a decentralized network or just a collection of services that governments can switch off at will.

Right now, the future of digital autonomy hangs on a single decision by a single platform. Choose wisely, GitHub.

FAQ

Q: Isn't this just about one obscure app? Why should I care?

A: Because it's a test case. If GitHub complies, every decentralized project becomes vulnerable to government takedown. If they refuse, it sets a precedent that code is protected speech, not just a product to be censored.

Q: What does this mean for me as a regular user?

A: It means the apps you rely on for communication may not be as secure as you think. Decentralization is the only way to ensure your group chats and organizing tools can't be shut down by a single government order. This case is a wake-up call.

Q: Maybe the government has a point — decentralized apps can be used for illegal activities.

A: That's true, but the same can be said of encrypted messaging, email, or even phones. The real issue is that the government's solution is to block the entire platform rather than target specific illegal activity. That's a dangerous precedent that undermines the principle of due process.

📎 Source: View Source