Jack Dorsey Is Wrong on Bitchat and India's Takedown Order

The Lift Line

A state can have a legitimate reason to act and still choose the least transparent way to do it. Both things can be true at once.

Why This Editorial Matters for Your Exam

Answers on internet governance and free expression tend to default to naming Section 69A. This editorial forces the harder distinction: the actual order here used Section 79(3)(b), a different and less procedurally safeguarded route, to achieve a public-order-based blocking outcome, and knowing which provision was actually used, and why that choice matters, is what separates a Prelims-level answer from a Mains-level one.

GS Paper 2: Indian Constitution: significant provisions and basic structure; separation of powers between various organs; issues and challenges pertaining to the federal structure; role of technology in governance.

GS Paper 3: Cyber security and challenges in security through communication networks; role of media and social networking sites in internal security challenges, cyber security basics.

Background and Context

The trigger was a directive issued by the Indian Cyber Crime Coordination Centre (I4C), under the Ministry of Home Affairs, ordering GitHub to disable public access to three code repositories hosting Bitchat, an open-source messaging application associated with Jack Dorsey, within three hours of the order.

Bitchat uses Bluetooth Low Energy mesh networking to relay encrypted messages directly between nearby devices, without requiring an internet connection, mobile network access, a phone number or a central server. This design allows communication to continue even when conventional connectivity is suspended, which is exactly the circumstance in which it saw increased use.

The order came during a sustained period of protest at Jantar Mantar, Delhi, over the 2026 NEET-UG examination paper leak, in which the National Testing Agency cancelled the examination and referred the matter to the CBI. Authorities suspended mobile internet in a 1.5 km radius of the protest site and shut 17 Delhi Metro stations; reporting documented protesters turning to Bluetooth mesh apps to stay in contact once conventional connectivity was restricted.

The order itself invoked Section 79(3)(b) of the IT Act, 2000, read with Rule 3(1)(d) of the Intermediary Guidelines and Digital Media Ethics Code Rules, 2021, a provision that conditions an intermediary’s safe-harbour protection on compliance with a lawful takedown direction, rather than Section 69A, the Act’s dedicated content-blocking provision.

The Analysis

1. The legal route chosen matters as much as the outcome. Section 69A carries a review committee process for blocking orders; Section 79(3)(b), the provision actually used here, does not carry an equivalent safeguard, even though this order pursued a public-order and security rationale similar to what 69A is designed for.

2. Bitchat’s architecture is a genuinely hard case for any state. With no central server, a conventional takedown notice has nothing to be served to; blocking has to target the code repository, app-store listing or device level, a blunter instrument that is harder to confine to only the misuse it targets.

3. The civil-unrest context is specific, not generic. This was not a blanket judgement about mesh-network technology; it followed weeks of documented protest activity in which internet suspensions were already in effect and Bitchat use rose specifically in response to those suspensions.

4. The proportionality question is unresolved by the order itself. A technology’s use by some protesters to evade monitoring does not establish that blocking the repository for all users, the great majority using it entirely lawfully, was proportionate; the order’s own text cites risk of misuse rather than documented instances of it.

5. The order’s practical effectiveness is itself in question. Reporting indicates Bitchat remained available on major app stores after the GitHub order, since open-source code is easily mirrored elsewhere, which raises a separate question about whether this specific instrument achieves what it sets out to.

6. The transparency gap is the strongest structural critique. Digital-rights groups argue that using Section 79(3)(b) for a public-order-based blocking outcome functions as a way to achieve a 69A-style result without 69A’s procedural safeguard, a pattern that, if it recurs, would matter well beyond this single case.

Data and Institutions Vault

Prelims-grade facts:

• Blocking order issued by: Indian Cyber Crime Coordination Centre (I4C), Ministry of Home Affairs
• Legal basis: Section 79(3)(b), IT Act, 2000, read with Rule 3(1)(d), Intermediary Guidelines and Digital Media Ethics Code Rules, 2021 (not Section 69A)
• Target: three GitHub repositories hosting Bitchat, ordered disabled within three hours
• Bitchat: open-source, Bluetooth Low Energy mesh-network messaging app associated with Jack Dorsey; works without internet, mobile network, phone number or central server
• Context: 2026 NEET-UG paper leak protests, Jantar Mantar, Delhi; mobile internet suspended in a 1.5 km radius; 17 metro stations shut
• Critics: Internet Freedom Foundation, Software Freedom Law Centre (SFLC.in)

Watch the trap: do not write that this order was issued under Section 69A; the actual provision was Section 79(3)(b), a narrower intermediary-liability route with weaker procedural safeguards, and that distinction is the editorial’s central legal fact.

The Debate

Argument FOR the state’s action. A democratically elected government has a legitimate duty to respond when a communication technology is credibly used to evade lawful monitoring during organised civil unrest. The order targeted a specific tool in a specific context, using an existing statutory provision, not a blanket ban on encrypted communication or an extra-legal emergency power, and mislabelling this as authoritarian collapses a meaningful distinction between targeted, lawful regulatory action and general suppression.

Argument AGAINST treating the order as unproblematic. The provision actually used, Section 79(3)(b), lacks the review committee safeguard that applies to Section 69A even though the order pursued a similar public-order rationale, and blocking an entire open-source code repository catches the overwhelming majority of lawful users along with whatever misuse motivated the order, a proportionality concern that a general capability for misuse does not resolve. The order’s apparent limited practical effect, given that the app remained available on app stores, also raises the question of what was actually achieved.

Balanced verdict. The state’s underlying interest in responding to organised evasion of lawful monitoring during a public-order crisis is legitimate and should not be dismissed as inherently authoritarian. But legitimacy of purpose does not settle the separate question of procedure: routing a public-order-based blocking decision through a provision with weaker transparency and review safeguards than the dedicated blocking provision available for exactly this purpose is a real institutional gap, independent of whether Bitchat itself deserved to be blocked.

How to Think About This

The transferable pattern: when a state has more than one legal route to the same outcome, ask which route was chosen and what procedural safeguard that choice avoided, not only whether the outcome itself was justified.

Legitimacy of purpose and adequacy of procedure are two separate questions, and a state can satisfy the first while failing the second. When a government reaches for a general-purpose provision (intermediary liability, emergency powers, a residuary clause) to achieve an outcome that a more specific, more accountable provision was designed for, the choice of route deserves as much scrutiny as the substantive decision itself, because it reveals whether the safeguards built into the specific provision were being deliberately avoided.

This same structure recurs in preventive detention law, where states sometimes invoke broader public-order provisions rather than more specific, more procedurally safeguarded ones; in financial-intermediary regulation, where a general compliance direction can achieve what a more specific, appealable order would otherwise require; and in content regulation more broadly, wherever multiple statutory routes exist to the same practical outcome with different procedural protections attached.

Diagram-in-Words

TWO ROUTES TO THE SAME OUTCOME

SECTION 69A (IT Act)                SECTION 79(3)(b) (IT Act)
dedicated blocking provision        intermediary safe harbour
grounds: sovereignty, defence,      condition: comply with
security, public order              lawful takedown direction
        |                                   |
   REVIEW COMMITTEE                   NO EQUIVALENT
   procedural safeguard               REVIEW STEP
        |                                   |
        v                                   v
   more accountable                   THIS ORDER
   blocking route                     (Bitchat, July 2026)
                                             |
                                             v
                                   GitHub directed to disable
                                   3 repositories within 3 hours
                                             |
                                    BITCHAT ARCHITECTURE
                                    no central server to notify
                                    (Bluetooth mesh network)
                                             |
                                    blocking targets repo/app-store
                                    level instead, catches lawful
                                    users along with any misuse
                                             |
                                    app remained on app stores
                                    (limited practical effect)

CRITIQUE: same public-order rationale as 69A, weaker safeguard

Takeaway Box

Lift line for an answer:

The state may have had good reason to act. It still chose the provision with the weaker safeguard to do it.

Prelims hooks: Order issuer I4C (Ministry of Home Affairs); legal basis Section 79(3)(b) + Rule 3(1)(d), NOT Section 69A; target Bitchat (Jack Dorsey, Bluetooth mesh-network app), 3 GitHub repositories, 3-hour compliance window; context 2026 NEET-UG paper leak protests, Jantar Mantar; 1.5 km internet suspension radius, 17 metro stations shut; critics Internet Freedom Foundation, SFLC.in.

Ethics and interview angle: if a technology has a large majority of lawful users and a small minority of users evading lawful monitoring, and the state cannot technically separate the two, does proportionality require accepting some risk of misuse, or does it justify blocking the tool for everyone?

PYQ linkage: UPSC has examined internet shutdowns, free expression versus state security, and IT Act blocking powers in various forms; this editorial supplies a live case distinguishing between two different statutory blocking routes with different procedural safeguards, a distinction not usually tested with this specificity.

Probable question: “A state’s authority to block a communication technology during civil unrest does not, by itself, settle whether the procedure chosen to exercise that authority was adequate.” Discuss with reference to the blocking of Bitchat in India in 2026.

Sources: Hindustan Times, PIB, Ministry of Home Affairs

Source: Jack Dorsey Is Wrong on Bitchat and India's Takedown Order — Ujiyari.com | Free UPSC & State PCS Editorial Analysis