﻿<?xml version="1.0" encoding="utf-8"?>
<!--<!DOCTYPE nitf SYSTEM "nitf-3-4.dtd">-->
<nitf>
  <head>
    <title id="Title">#Title</title>
    <docdata management-doc-idref="">
      <date.issue id="CreationDate" norm="" />
      <du-key id="rev-ver" generation="1" version="Default" />
      <du-key id="Parent-Version" version="" />
      <identified-content>
        <classifier id="newspro-nitf" value="r2" />
        <classifier id="Newspro-App" value="Epaper" />
        <classifier id="Content-Type" value="Story" />
        <classifier id="storyID" value="" />
        <classifier id="CmsConID" value="" />
        <classifier id="Desk" value="" />
        <classifier id="Source" value="" />
        <classifier id="Edition" value="" />
        <classifier id="Category" value="-1" />
        <classifier id="UserName" value="" />
        <classifier id="PublicationDate" value="18/06/2026" />
        <classifier id="PublicationName" value="HI" />
        <classifier id="IsPublished" value="Y" />
        <classifier id="IsPlaced" value="Y" />
        <classifier id="IsCompleated" value="N" />
        <classifier id="IsProofed" value="N" />
        <classifier id="User" value="" />
        <classifier id="Headline-Count" value="" />
        <classifier id="Slug-Count" value="0" />
        <classifier id="Photo-Count" value="0" />
        <classifier id="Caption-Count" value="0" />
        <classifier id="Word-Count" value="0" />
        <classifier id="Character-Count" value="0" />
        <classifier id="Location" value="" />
        <classifier id="TemplateType" value="1" />
        <classifier id="StoryType" value="Story" />
        <classifier id="Author" value="" />
        <classifier id="UOM" value="mm" />
        <classifier id="NumCol" value="0" />
        <classifier id="kicker" value="" />
        <classifier id="ByLine" value="" />
        <classifier id="DateLine" value="" />
        <classifier id="box-geometry" value="503,601,722,961" />
        <classifier id="Layer" value="Default" />
        <classifier id="numcol" value="2" />
        <classifier id="ArticleStyle" value="" />
        <classifier id="Epaper-Build" value="7.96.0.0" />
        <classifier id="ProcessingDateTime" value="Wed Jun 17 2026 23:59:26 GMT+0530" />
      </identified-content>
      <urgency id="home-page" ed-urg="0" />
      <urgency id="priority" ed-urg="0" />
      <doc-scope id="scope" value="0" />
    </docdata>
    <pubdata type="print" name="HI" date.publication="20260618T000000+5.30" edition.name="VJA" edition.area="VJA" position.section="18MAIN07FFVJA" position.sequence="7" ex-ref="18MAIN07FFVJA.indd" />
  </head>
  <body boxBorderWeightColor="" boxBorderWeight="">
    <body.head>
      <hedline>
        <hl1 id="Headline1" class="1" style="Headline1">
          <lang class="3" style="Headline1" font="Franklin Gothic Demi Cond" fontStyle="Regular" size="28">Telegram moves Delhi HC against govt curbs</lang>
        </hl1>
      </hedline>
    </body.head>
    <body.content id="Bodytext" CaptionAsBody="0">
      <p style=".Bodylaser">
        <lang class="3" style=".Bodylaser" font="Minion Pro" fontStyle="Italic" size="9">Continued from page 1</lang>
        <lang class="3" style=".Bodylaser" font="Minion Pro" fontStyle="Regular" size="9"></lang>
      </p>
      <p style=".Bodylaser">
        <lang class="3" style=".Bodylaser" font="Minion Pro" fontStyle="Regular" size="9">He said that over 150 million users had been affected by the Centre's action on Tuesday. SG Mehta sought an adjournment, saying that he had not put several things on record. "If the court posts the matter for Thursday, then there is something shocking I can show. One channel starts, it is prohibited, and then another is started. And with a QR code, you can make a payment. This is continuous," he said. "This has not happened overnight. We have been dealing with complaints since May. I don't wish to go beyond this. This platform is being misused, and imagine the situation which may arise," Mehta added. The Ministry of Electronics and Information Technology (MeitY), acting on recommendations of the National Testing Agency (NTA), issued a direction under Section 69A of the Information Technology Act, 2000, restricting access to the Telegram platform in India till June 22, covering the day of the NEET (UG) 2026 re-examination and its immediate aftermath. A separate direction requires Telegram to disable in India the message-editing feature for already-posted messages till June 30, 2026, addressing the specific structural feature through which the platform has been used to fabricate after-the-event "paper leak" evidence in respect of national examinations, according to an NTA statement. "Both measures have been taken in the interest of public order, in response to the organised use of the platform by cheating rackets to defraud candidates appearing for the NEET (UG) 2026 re-examination scheduled on 21 June 2026," the NTA said on Tuesday.</lang>
      </p>
    </body.content>
  </body>
</nitf>