On July 23, 2026, India’s cybercrime arm told GitHub to cut access to three repositories tied to Bitchat — Jack Dorsey’s Bluetooth mesh messenger — arguing the app can help people organize when the internet is down and make lawful interception harder. The order landed in the middle of Delhi protest coverage and local network restrictions, which is why X treated it as both a tech story and a civil-liberties story.
This is not a how-to for bypassing Indian law. It is a builder’s briefing: what Bitchat is, what I4C claimed, how IT Act intermediary rules work in practice, and how this sits next to Dorsey’s other decentralization bets like Buzz.
TL;DR — What People Are Asking
| Question | Answer |
|---|---|
| Who ordered what? | I4C → GitHub: disable 3 Bitchat repos in 3 hours |
| Date? | Order dated July 23, 2026 (reported July 24) |
| Legal hook? | IT Act §79(3)(b) + IT Rules 2021 Rule 3(1)(d) |
| Tech worry? | Bluetooth mesh works without internet / cell |
| Context? | CJP protests + reported internet restrictions in Delhi |
| Dorsey’s line? | Public posts that India “does not like” tech like Bitchat |
| Same as Buzz? | No — mesh chat ≠ Nostr team workspace |
| Open source irony? | Blocking GitHub hits the distribution channel, not radio physics |
What Bitchat Actually Is
Bitchat’s pitch is simple enough that non-engineers understood it during a march:
- Phones talk over Bluetooth Low Energy
- Nearby devices relay messages (mesh hops)
- No requirement for SIM identity, cloud inbox, or always-on IP
- Useful when towers are congested, jammed, or administratively restricted
That architecture is why a cybercrime unit cares. Centralized messengers (WhatsApp, Signal with internet, SMS) sit on infrastructure India already knows how to throttle or order offline. A dense crowd of phones that keep chatting after the packet network dies is a different control surface — closer to walkie-talkies with encryption and store-and-forward than to a SaaS chat product.
Dorsey has spent years arguing for protocols over platforms (Bluesky’s early history, Nostr-adjacent experiments, Buzz’s signed-event workspace). Bitchat is the offline sibling: less “own your relay,” more “own the radio bubble around you.”
What the I4C Order Said (Per Reporting)
According to Moneycontrol’s review of the order Dorsey shared:
- Bitchat is described as capable of decentralized peer-to-peer messaging over Bluetooth mesh without mobile networks, internet, or centralized servers.
- That design impedes lawful interception, attribution, and investigation.
- Intelligence inputs (as framed in the order) claim such platforms can be exploited for unlawful assemblies, violent protest coordination, misinformation, radicalization, and other activities framed as threats to sovereignty, defense, security, and public order.
- GitHub must remove or disable access to three named repositories, including the primary project and an Android variant, on a three-hour clock.
The same reporting places the order against Cockroach Janata Party (CJP) protest activity in Delhi and temporary mobile internet suspensions in parts of central Delhi — the exact scenario mesh apps are designed for.
Jack’s public posts framed the move bluntly: the government does not like technologies like Bitchat and wants them taken down. Free-speech advocates read that as prior restraint on tools; security supporters read it as removing a coordination channel during a public-order operation. Both readings are now part of the X discourse — verify primary documents before treating either as settled law-school dogma.
Why GitHub, Not Just App Stores?
Targeting GitHub is a tell.
- App store bans remove polished binaries for casual users.
- Repo takedowns hit source, CI artifacts, issue trackers, and fork discovery for developers.
- India has a long history of intermediary notices under the IT Act; GitHub is a global CDN for code, so a local disable order is a geo-access fight as much as a content fight.
For open-source maintainers, the lesson is old but freshly painful: your availability model is a jurisdiction model. Self-hosting mirrors, IPFS, and alternative forges are resilience tactics — they are also exactly the behaviors regulators cite when arguing a tool is built to evade oversight. Builders working on India-facing products should read this next to India’s sovereign AI / IT Rules landscape, not as an isolated Jack Dorsey drama.
Protest Tech vs Public-Order Tech
Field reporting from the July 20 Sansad Chalo-style marches described students discovering Bluetooth messengers when calls would not connect. That lived experience is why Bitchat trended: not crypto ideology, but “my phone has radio but no IP.”
Governments counter with a familiar bundle:
| State concern | Mesh-app property that triggers it |
|---|---|
| Unlawful assembly coordination | Works during intentional shutdowns |
| Lawful interception | No central server to serve warrants to |
| Attribution | Harder device/user binding than SIM-linked apps |
| Misinformation velocity | Local viral hops inside a crowd |
None of that requires believing every protest is unlawful — or believing every mesh packet is criminal. It does require admitting the same radio mesh is dual-use: disaster relief after an earthquake and coordination during a banned march share a stack.
explainx.ai’s stance for engineers: design for safety and clarity (rate limits, abuse reporting where you have a service, honest docs about range and failure modes) and do not confuse “decentralized” with “outside every legal system.” Physical presence in India still means Indian criminal and IT law apply to people, even when packets never touch a Mumbai data center.
Bitchat vs Buzz — Do Not Collapse the Brands
| Bitchat | Buzz | |
|---|---|---|
| Job | Offline / local mesh chat | Team chat + agents + Git |
| Network | Bluetooth mesh | Nostr relay (usually IP) |
| Identity | Ephemeral / local mesh peers | Signed Nostr keypairs |
| Hosting | Mostly device-to-device | Self-host relay |
| July 2026 news | I4C → GitHub disable | Block open-source launch |
Collapsing them into “Jack’s anti-censorship apps” misses the threat models. Buzz still needs IP and a relay operator. Bitchat’s whole point is surviving without that. Regulators who understand the difference will aim notices at different chokepoints — DNS, app stores, Git hosts, device OEMs, or Bluetooth stack policy.
What Builders and Platforms Should Take Away
- Intermediary clocks are short. Three hours is not a thoughtful CVE response window; it is an emergency disable. Have counsel and geo-playbooks before you need them.
- Dual-use docs matter. If your README markets “works during government shutdowns,” expect that sentence to be quoted in an order.
- Mirrors are politics. Forking to dodge a lawful local order can create separate legal exposure for operators in-country — get local advice; do not cargo-cult “code is free speech” without jurisdiction analysis.
- Product adjacency. If you ship agents that help organize physical gatherings (agent harness tooling, WhatsApp bots, etc.), your abuse policy will face the same public-order questions even if you never touch Bluetooth.
- India AI policy context. Active-moderation IT Rules amendments and IndiaAI Mission framing already push platforms toward proactive risk posture — see India sovereign AI status.
Honest Limitations of This Write-Up
- We summarize press-reported order text; we are not publishing the PDF here.
- Protest casualty / force claims vary by outlet — this article stays on the tech-policy axis.
- GitHub’s exact compliance state (full takedown vs India IP block vs soft 404) can change after publication.
- We do not provide clone URLs, APK sideload steps, or evasion recipes for blocked repos.
For product counsel, the adjacent question is whether mesh messaging gets treated like encryption generally (lawful when used lawfully) or like a specialized “shutdown circumvention” category. India already uses temporary internet suspensions as a public-order tool; tools that remain useful because of those suspensions will keep attracting intermediary notices. Expect similar pressure on other offline-first stacks — not only Dorsey-branded ones — whenever street politics and radio hops coincide. Platforms that host source should assume geo-disable playbooks are as important as DMCA playbooks; maintainers should assume README marketing lines will be quoted back at them in ministerial English.
Update — July 27, 2026: A related border-privacy story broke the same week — see GrapheneOS Duress Wipe Now the Center of a Federal Prosecution, where a phone's own privacy feature, not a blocked repo, became the legal flashpoint.
Related on explainx.ai
- GrapheneOS duress PIN — Atlanta federal prosecution
- Block Buzz — Nostr humans + agents workspace
- Jack Dorsey Buzz — chat, agents, Git
- India sovereign AI / IndiaAI Mission status
- GitLost — GitHub agentic workflows & private repos
- Claude Cowork SharedRoot sandbox escape
- Grok 4.5 VulcanBench + Graffiti 284 — same-day AI news
- What is an agent harness?
Primary reporting: Moneycontrol (July 24, 2026) on the I4C → GitHub order · NDTV Profit / other Indian tech desks · Jack Dorsey’s public X statements · prior field reporting on Bluetooth messengers during Delhi protest network disruptions.
Legal citations and repository status reflect press accounts as of July 24, 2026. This article is not legal advice. Orders, compliance actions, and protest facts may update quickly — verify against official I4C/GitHub notices and primary court or ministry documents when making operational decisions.
