惯性聚合 高效追踪和阅读你感兴趣的博客、新闻、科技资讯
阅读原文 在惯性聚合中打开

推荐订阅源

钛媒体:引领未来商业与生活新知
钛媒体:引领未来商业与生活新知
云风的 BLOG
云风的 BLOG
IT之家
IT之家
C
Check Point Blog
T
The Blog of Author Tim Ferriss
S
SegmentFault 最新的问题
人人都是产品经理
人人都是产品经理
H
Hackread – Cybersecurity News, Data Breaches, AI and More
美团技术团队
M
MIT News - Artificial intelligence
Jina AI
Jina AI
Blog — PlanetScale
Blog — PlanetScale
freeCodeCamp Programming Tutorials: Python, JavaScript, Git & More
Microsoft Security Blog
Microsoft Security Blog
G
Google Developers Blog
F
Fortinet All Blogs
V
Visual Studio Blog
奇客Solidot–传递最新科技情报
奇客Solidot–传递最新科技情报
T
Tailwind CSS Blog
Hugging Face - Blog
Hugging Face - Blog
MyScale Blog
MyScale Blog
爱范儿
爱范儿
The Cloudflare Blog
博客园 - 三生石上(FineUI控件)

MEDIANAMA

India in talks with US, Anthropic for Mythos access; no Indian firms in Project Glasswing yet Eternal Q4FY26: All Users Pay Higher Platform Fee, Only Some Get Discounts Amazon, Meta to challenge PhonePe-Google Pay dominance as UPI cap delayed since 2020 Meta failed to protect the safety of under-13s: European Commission If markets and regulators are ready for network slicing, we are ready: JIO Why defining ‘news’ won’t fix the free speech problems of draft IT Rules? #NAMA Eternal Q4FY26: Goyal Dismisses AI Disruption Risk as Zomato Quietly Builds Agentic Commerce Infrastructure Karnataka files appeal challenging the bike taxi ban lift in the Supreme Court How did WhatsApp turn 17 govt. flags into 9,400 digital arrest scam bans? Google Wallet integrates Aadhaar as digital ID, expands India’s mobile identity ecosystem Kerala HC issues notice on MediaOne’s Facebook page block in India MeitY warns VPN providers against enabling access to blocked betting platforms Shreya Singhal targeted private censorship. Today’s threat is the State #NAMA Amazon scales its quick delivery service ‘Amazon Now’ in 100 cities Can MeitY issue binding rules via advisories? Experts raise alarm over draft IT Rules #NAMA How 2019 election code of ethics became India’s three-hour content takedown mandate #NAMA Australia proposes new levy on big tech to fund news, opens draft law for consultation ‘judge, jury, executioner’: experts warn of Inter-Departmental Committee (IDC) overreach under New draft IT Rules Lowdown: TRAI flags low deployment under PM-WANI in public Wi-Fi consultation paper Why the NBFC licence matters for MobiKwik China blocks Meta-Manus deal, asserts origin-country jurisdiction: what this means for India ‘No transparency’: experts warn of expanding powers to block online speech in India #NAMA X launches standalone iOS messaging app XChat with encryption in India How India’s content takedown framework was built and where It has gone wrong #NAMA Claude Mythos puts India on alert: CERT-In, telcos, banks assess unprecedented cyber risks Explained: why did the RBI cancel Paytm’s banking licence? Meta now instantly blocks content in India Govt. asks ZEE5 to halt ‘Lawrence of Punjab’ web series release Online Gaming Rules notified, to be in effect from May 1, what are the major changes? RBI mandates additional factor authentication for e-mandates
How experts are reading the Delhi HC’s Telegram ruling
Prabhanu Kumar Das · 2026-06-22 · via MEDIANAMA

The Delhi High Court on Friday dismissed Telegram’s petition challenging the Central Government’s emergency blocking order under Section 69A of the Information Technology Act, 2000, which temporarily restricted access to the platform until the immediate aftermath of the NEET-UG 2026 re-examination. 

Upholding the government’s action, Justice Tejas Karia held that the order satisfied the constitutional test of proportionality and fell within the Centre’s statutory powers under Section 69A. The Court also held that Telegram, as an application and platform, fell within the scope of the provision, observing that software-based infrastructure qualifies as a “computer resource” under the Act. 

Platform-wide blocking and free speech: The Internet Freedom Foundation (IFF), in a statement issued after the judgment questioned the court’s interpretation of Section 69A: 

  • IFF argued that Shreya Singhal v Union of India upheld Section 69A because the power was understood to be narrowly drawn and directed at specific information.
  • It warned that extending the provision to an entire intermediary treats “the speech of a whole population as a single switch to be turned off.”
  • According to IFF, the precedent carries consequences for “the open internet that extend well beyond this case.”

Nikhil Pahwa, Founder & Editor at MediaNama, argued in an X thread that the ban was disproportionate and set a troubling precedent for future platform regulation. 

  • Pahwa said the government had not proved that it had exhausted all possible avenues before resorting to a block and described pre-censorship as “an extreme step.”
  • He argued that “blocking of a platform is different from blocking of a group, is different from blocking of an account, is different from blocking of a post” because the restriction affects lawful users, businesses, and speech across the platform.
  • He warned that the ruling creates “a problematic precedence where the government of India will, on a whim, threaten to block entire platforms because they don’t accede to their extreme-censorship demands.”

Section 69A, proportionality, and less restrictive alternatives: IFF argued that the temporary nature of the restriction does not automatically make it proportionate.

  • Citing Anuradha Bhasin v Union of India, it said the State must demonstrate that no less intrusive alternative was available.
  • It warned that “a blanket block, however brief, restricts the lawful expression and the right to receive information of millions of Indians.”

SFLC.in, in an X thread following the judgment, focused on the Court’s interpretation of “information” under the IT Act: 

  • SFLC noted that the statute defines information broadly enough to include software and databases.
  • However, it described the ruling as setting “a dangerous precedent” because it accepted a platform-wide restriction affecting nearly 150 million users as proportionate.

Writing for the Bar Bulletin, advocate Arjun Harkauli argued that the ruling effectively transforms a content-blocking provision into a platform-blocking mechanism.

  • Harkauli questioned whether constitutional rights could be curtailed for millions because authorities found it difficult to target specific bad actors. He wrote, “This raises a critical question: Can constitutional rights be curtailed for millions on the basis of the inability of the State to target wrongdoers effectively?”
  • He also argued that the judgment expands executive power under Section 69A and effectively “transforms a content-blocking provision into a platform blocking mechanism.”

Writing for Constitutional Law and Philosophy, Tanmay Durani, a researcher at the Centre for Advanced Studies in Cyber Law and Artificial Intelligence, questioned whether the government had sufficiently demonstrated that narrower interventions had failed: 

  • Durani argued that the judgment showed the executive claimed to have exhausted alternatives, but did not clearly establish why those alternatives were insufficient.
  • He wrote that the Court could have required stronger evidence before accepting a complete platform block.

Platform architecture and future implications: Harkauli argued that the government relied heavily on Telegram’s channels, bots, cloud infrastructure, and message-editing features to justify the restriction: 

  • He said the judgment endorses pre-emptive intervention based on anticipated harm rather than proven future misconduct.
  • Harkauli also questioned what “principled standard” distinguishes Telegram from services such as WhatsApp or Signal.
  • He further argued, “The absence of a clear, specific criterion risks selective regulation, which is constitutionally suspect. It will keep citizens and State alike in a situation of ambivalence. The instrumentalities of the State may ban messenger channels before any prominent examination or event in anticipation of harm to public order.”

Supreme Court advocate Shaileshwar Yadav argued that the judgment shifts the focus from intermediary compliance to platform design:

  • Yadav wrote that once unlawful activity is attributed to a platform’s architecture rather than a failure to comply with legal requests, the intermediary’s obligation effectively becomes one of redesigning its services.
  • He criticised the direction requiring Telegram to disable message editing, arguing that “Section 69A authorises the blocking of information. It does not authorise the redesign of software.”
  • Yadav warned that the reasoning could justify future directions affecting encryption, anonymity, forwarding, and other platform features.

Durani similarly argued that the judgment treats a platform’s resistance to targeted intervention as justification for broader restrictions:

  • He wrote that “the less amenable a platform is to surgical intervention, the more proportionate total intervention becomes.”
  • Durani warned that the same reasoning could eventually extend beyond Telegram to encryption, anonymity tools, VPNs, and other privacy-enhancing technologies.

Due process and hearings: IFF criticised the use of the emergency procedure under Rule 9 instead of the ordinary hearing process under Rule 8:

  • It argued that hearing rights are “integral to the fairness of the blocking process.”
  • According to IFF, dispensing with those safeguards in these circumstances “calls for close scrutiny.”

SFLC highlighted a separate transparency concern:

  • It noted that Telegram was able to challenge the order because, as an intermediary, it had access to the blocking directions.
  • SFLC.in contrasted this with cases where Rule 16 confidentiality prevents ordinary users from accessing blocking orders.

Also read

Post navigation

Flipkart

The Delhi High Court has found a prima facie case of passing off after sellers allegedly exploited Flipkart’s latching on feature to market counterfeit products.