Internet Freedom Foundation calls India’s BitChat GitHub takedown order ‘unconstitutional’

The Fight for the Code

India’s heavy-handed move to scrub a decentralized messaging project from GitHub is the latest proof that the battle for the future of the internet isn't being fought in boardrooms, but in the repositories where builders store their work. The project in question is BitChat, a peer-to-peer messaging application backed by Jack Dorsey’s TBD. The Indian government issued a takedown order, and now, the Internet Freedom Foundation is calling foul, labeling the move as unconstitutional and a direct assault on the right to build.

As a founder, I look at this and see a clear pattern. When a government can't intercept your messages, their first instinct isn't to ask for a key; it's to break the factory that makes the locks. This isn't just about one app. It is about whether the code we write is protected speech or if it’s merely a utility that the state can switch off on a whim.

The Breakdown of the Order

The details are messy. The Indian government utilized its emergency powers to demand GitHub remove the BitChat repositories. This wasn't a standard copyright claim or a request based on a specific crime. It was a broad stroke aimed at ensuring decentralized, encrypted communication tools don't reach the hands of the public. The Internet Freedom Foundation (IFF) has stepped in to argue that this exceeds the legal authority of the state. They aren't just defending a piece of software; they are defending the principle that software development is a form of expression.

For those of us in the crypto and AI space, this should sound alarmingly familiar. We are moving toward a world where the infrastructure of communication is no longer centralized in a single data center. Tools like BitChat leverage peer-to-peer protocols to bypass the middleman. If you are a builder in this space, you need to understand that your code is a political statement, whether you intended it to be or not. If it works too well at providing privacy, it will be targeted.

Why Target GitHub?

GitHub is the town square for developers. By forcing a takedown there, the government isn't just stopping people from downloading the final product; they are disrupting the collaborative process. They are making it harder for contributors to see the source, audit it, and improve upon it. It is a chilling effect designed to make developers think twice before contributing to privacy-centric projects.

The irony is that decentralized software is, by its very nature, difficult to kill. Taking it down from a centralized harbor like GitHub is a speed bump, not a brick wall. However, the legal precedent being set is dangerous. If the Indian government succeeds in classifying peer-to-peer code as a threat to national security without specific evidence of wrongdoing, it sets a template for other nations to do the same.

What This Means for Builders

If you are building in the decentralized web (Web3) or working on open-source AI models that aren't behind a corporate API, you are in the crosshairs. You have to start thinking about censorship resistance not as a feature, but as a core requirement of your development lifecycle. This means considering where your code lives and how easily it can be wiped by a single legal notice to a centralized entity.

• Redundancy is king: Relying on a single platform like GitHub for your source of truth is a vulnerability. Builders need to look at decentralized alternatives or self-hosted mirrors.
• Legal awareness: You can't just be a coder anymore. You need to understand the regulatory landscape of the regions you inhabit. The IFF is doing the heavy lifting in India, but these battles are happening globally.
• The Privacy Premium: Tools that offer true privacy are going to face the most friction. If your project is succeeding, expect pushback.

The IFF’s argument is straightforward: Section 69A of India’s IT Act, which is often used for these takedowns, does not give the government the power to preemptively ban tools just because they provide anonymity or encryption. This is a foundational legal fight. If code is speech, then banning the code is a violation of fundamental human rights.

The Jack Dorsey Factor

It is worth noting that BitChat is part of the ecosystem Jack Dorsey is trying to build. He has been vocal about moving away from the centralized social media models he helped create. His involvement adds a layer of visibility to this case, but the hardware and software don't care about a billionaire's endorsement. The tech either works or it doesn't. The fact that the Indian government is targeting this specific project suggests they are worried about the scalability of peer-to-peer protocols.

We are seeing a divergence in the tech world. On one side, you have the managed, sanitized, and easily surveilled internet of the tech giants. On the other, you have the chaotic, sovereign, and private internet being built by people who value freedom over convenience. The Indian government has clearly picked a side.

The Long Game

This isn't going to be resolved overnight. The IFF is pushing for transparency and for the government to justify why this specific repo was a threat. Most of the time, these orders are shrouded in secrecy, making it impossible for the public to know why their access is being restricted. By shining a light on this, the IFF is forcing a conversation that most governments would rather avoid.

As builders, we should be skeptical of any government that claims it needs to ban a tool for the public's own good. History shows that those tools are usually the only ones that actually protect the public's interests. We need to stay focused on the work, but keep one eye on the courtroom.

The moment we accept that code can be banned based on potential use rather than actual harm, we have lost the battle for the open internet.

The takeaway here is simple: The legal walls are closing in on centralized coding platforms. If you want your project to survive, you need to build it like it’s already been banned. Use the tools that are currently available, but prepare for the day they aren't. The IFF is fighting the good fight in the courts, but the real victory will be won by developers who make their software impossible to delete.

Read the original at Cointelegraph →