The Lean FRO and Mathlib Initiative have released a joint statement on the Lean verification of the Riemann Hypothesis.
On November 20, Levent Alpöge released a proof of the Riemann Hypothesis as a Lean library of 17 million lines of code. Over the past day, the Lean and Mathlib communities worked together to verify it. The statement certifies the proof as correct and describes how it meets all necessary verification criteria.
Congratulations to Levent on this achievement, and thank you to everyone in the community who contributed to the verification.
Full statement: https://t.co/edxEbkodw7
“Thank you, it's a great honor and I'm obviously very surprised as the email suggested something else. Excellent deception!” - Prof. Gautam Bhatia, Infosys Prize 2026 Laureate in Humanities and Social Sciences, at the #infosysprize2026 winners’ announcement.
@gautambhatia88
#infosysprize #infosyssciencefoundation #infosysprize2026 #humanities #socialsciences #constitutionallaw #legalresearch #indianconstitution #lawandsociety
A 🧵on the curious case of Americans electing Muslims to Congress - with comparisons to India and Pakistan.
Only 1.5% of the US population is Muslim, yet Americans just elected 8 Muslims to the 535-member Congress - that's also 1.5% of all seats.
This is somewhat of a puzzle.
1/6
Since day one, we have been questioning the authenticity of these takedown notices. We have repeatedly written to the Delhi Police, seeking confirmation on whether these notices were indeed issued by them.
Read more about the steps https://t.co/X7ipfsWjp2 took to authenticate and verify these notices: https://t.co/lleXNOVcx3
Delhi Police asks X to take down IFF's account and posts. IFF will challenge the notices in court unless they are withdrawn.
The Delhi Police has asked X to remove the Internet Freedom Foundation's account, six of its posts, the accounts of SFLC and @geoblockedindia, and posts by 16 other users, on the ground that they defame the Rashtriya Swayamsevak Sangh. The posts document and comment on a legal notice sent in the RSS's name to IFF, SFLC and @geoblockedindia, which demanded that the three stop criticising and documenting government blocking orders. IFF received copies of the two police notices from X on the morning of 3 November 2026.
IFF calls on the Delhi Police to withdraw both notices. If they are not withdrawn, IFF will challenge them in court.
What has happened
On 29 October 2026 at 9:54 PM, IFF, SFLC and the operator of @geoblockedindia received a two-page "legal notice" said to be issued on behalf of the RSS. It asked the three to stop opposing the government's blocking directions, stop documenting restricted content, stop posting details of geo-blocked posts, and confirm in writing within seven days that they would comply. It was signed by an unnamed "Authorised Signatory". Several RSS office-bearers have since said on X that the notice is not authentic. IFF replied to the notice, wrote to the RSS at its official address asking whether it had authorised it, and published both the notice and its reply on 30 October.
On 31 October 2026 at 8:06 PM, the Special Commissioner of Police (Crime), Delhi Police, filed an "Illegal Content Report" with X (reference LD-321926). It listed two posts: IFF's post of 30 October on the notice, and SFLC post of the same day. The stated reason was that the posts are "defamatory towards the Rashtriya Swayamsevak Sangh under Section 356 of the Bharatiya Nyaya Sanhita, 2023". The boxes for "safety/security", "defamation" and "other" were ticked. The fields for the nature of the court order and court order details were left empty. The desired action was "Remove/withhold content".
On 1 November 2026, a second notice arrived in the RSS's name. It said the matter had been handed to the Akhil Bharatiya Adhivakta Parishad, that complaints had been filed in several states, and that requests had been made to block IFF's X account and suspend the organisations. The Delhi Police had made its first request to X the previous evening. IFF did not know this until X told it on 3 November.
On 2 November 2026 at 8:51 AM, the Special Commissioner of Police (Crime) filed a second notice with X (reference LD-322956). It lists 40 URLs. Thirty-seven are posts. Three are the entire accounts of @internetfreedom, @SFLCin and @geoblockedindia. This time the boxes for "Hate speech", "defamation", "safety/security", "enforcement of court order" and "other" were all ticked. The court order fields were again left empty. The stated reason reads: "The posts constitute defamation and illegal content under Section 356 BNS. Under Rule 3(1)(d) of the IT Rules, 2021, read with Section 79(3)(b) IT Act, lawful notices require action within 3 hours."
The 16 other users are @ProdctiveUseful, @PanjwaniManoj, @jidge_, @RatanSharda55, @baxiabhishek, @SchrdingersDbag, @ashleshbiradar, @seemay, @NasirHussainINC, @Being_creat_ive, @AjoyDharmavaram, @othlaw, @_ananyaaa, @AimPoojaind, @incorigibleBhai and @rraoind. Their posts, as far as IFF can tell, comment on the notice or on the notice about it.
X forwarded both notice to IFF on 3 November 2026, at 8:47 AM and 10:03 AM, saying it was doing so "in the interest of transparency" and that IFF may wish to seek legal counsel and challenge the request in court. X's emails do not say that it has acted on the requests. The Delhi Police has not written to IFF, and no court has been approached, as far as the reports disclose. SFLC and @geoblockedindia have separately reported notifications from X about requests from the Uttar Pradesh Police, the Telangana Police and the Delhi Police's Cyber Crime unit, one of them against the whole of the @geoblockedindia account.
IFF's position
IFF condemns this legal action. A police force has made itself the enforcement arm of a private legal notice whose authenticity the organisation it names has not confirmed, and whose demand was that three organisations stop documenting censorship. The notices would deliver exactly what the notice asked for as they would also remove the accounts of the three groups in India that keep public records of what is blocked, and of who ordered it.
The posts in question are about a legal notice sent to us. They quote it, criticise how it was drafted, and say that we will carry on with our work. A person who receives a threat is entitled to publish it and answer it and that is not defamation of the sender.
In the three weeks before the first notice, IFF assisted 86 people whose accounts were suspended or whose posts were withheld in India. SFLC's Free Speech Tracker recorded about 268 content restrictions and 83 account restrictions in the first 29 days of October. @geoblockedindia publishes the orders behind such blocks when platforms disclose them. None of this is unlawful. Documenting censorship and challenging it in court is what the Constitution expects of citizens.
IFF will not delete the posts. If the Delhi Police does not withdraw the notices, we will challenge them in court.
Why the reports are unlawful
Defamation is not a police matter. Section 356 of the Bharatiya Nyaya Sanhita, 2023 is a non-cognizable and bailable offence. Under Section 222 of the Bharatiya Nagarik Suraksha Sanhita, 2023, no court can take cognizance of it except on a complaint by the person aggrieved.
Under Section 174 of the BNSS, the police cannot investigate a non-cognizable offence without an order of a Magistrate. The Special Commissioner of Police (Crime) is not the person aggrieved. The notices disclose no complaint by the RSS and no order of any Magistrate. Whether a statement is defamatory is for a court to decide after hearing its author, with the defences of truth, fair comment and good faith available to that author.
In Subramanian Swamy v. Union of India, (2016) 7 SCC 221, the Supreme Court upheld criminal defamation on the strength of these safeguards. A police officer who asks a platform to remove speech as defamatory has decided the question himself, without a complainant, a court or a hearing.
The posts are protected comment. Exceptions 1 to 3 to Section 356(1) protect the truth published for the public good, opinion on the public conduct of public servants, and opinion on the conduct of any person touching a public question. The posts publish a notice that was sent to us and give our opinion of it. The RSS, if it sent the notice, chose to enter a public question. If it did not, the posts defame no one.
Further, Section 79(3)(b) and Rule 3(1)(d) do not permit this. In Shreya Singhal v. Union of India, (2015) 5 SCC 1, the Supreme Court read down Section 79(3)(b) so that an intermediary acquires "actual knowledge" only through a court order, or a notification from the appropriate government or its agency that unlawful acts relatable to Article 19(2) are being committed. The court said that it would be difficult for intermediaries to judge the legitimacy of the millions of requests they receive, and that the burden must not be placed on them. Rule 3(1)(d), as amended in November 2025 and February 2026, now requires the intimation to come from an officer not below the rank of Joint Secretary or Deputy Inspector General, to be reasoned, and to specify the legal basis and the nature of the unlawful act, subject to a monthly review by a Secretary-level officer. The three-hour window the notice invokes applies to a lawful order that meets these conditions. A web form that ticks "hate speech" and "enforcement of court order" while leaving the court order fields blank, and that gives one sentence of reasons for 40 URLs, is not such an order.
The notices by the Delhi Police are disproportionate. They seek to remove three accounts in their entirety, with years of posts, over six, four and eleven posts respectively. They sweep in 16 third parties whose only connection is that they commented on a public controversy. In Anuradha Bhasin v. Union of India, (2020) 3 SCC 637, the Supreme Court held that any restriction on speech must be necessary, proportionate and the least restrictive measure available, and that orders restricting speech must be published and reasoned. Removing an organisation's entire account for criticising a legal notice fails each of these tests.
The effect is to silence documentation of censorship and providing legal aid to Indian internet users. The accounts named are those that record blocking orders in India. The notice asked them to stop. A takedown request that accomplishes the demand of an anonymous private notice is not law enforcement. It is the use of state power for a private end, which Article 14 forbids.
Our demands
1. To the Delhi Police: Withdraw reports LD-321926 and LD-322956 and confirm the withdrawal in writing to X and to IFF.
2. To the Delhi Police: Disclose the complaint on which the Special Commissioner of Police (Crime) acted, the authority under which the reports were filed, and whether any order of a Magistrate under Section 174 BNSS exists. Disclose every request made to any platform in this matter, including those made by the Cyber Crime unit against @geoblockedindia.
3. To X: Do not act on the reports. If any content is withheld in India, tell the affected user before acting, give them the full request, and name the legal basis. Publish both reports to the Lumen database, as the reporting form itself contemplates.
4. To the Ministry of Electronics and Information Technology and the Ministry of Home Affairs: Have the Secretary-level review required by Rule 3(1)(d) examine these intimations, and tell police forces that Rule 3(1)(d) is not a remedy for defamation, which the law reserves to the person aggrieved and to the courts.
5. To the RSS: State publicly whether it authorised either notice or any complaint to the police. If it did not, say so to the Delhi Police.
If the notices are not withdrawn, IFF will challenge them in court. We will continue to document blocking orders, to publish them, and to provide legal assistance to anyone whose account or post is withheld in India. Nothing in these notices changes that.
Watch the highlights from our 3rd Connecting Communities event in September — from spectrum sharing and BEAD implementation to the role of AI in shaping broadband policy and technology!
Watch here: https://t.co/37BnuXM8C1
"The topologist's map of the world" is a funky way of showing international borders, and nothing else. All information about a country's shape or size is ignored. Might hurt your head for a bit but it's a fun little exercise. Source: https://t.co/6eyfQ6INgH
Wow. I uploaded a post on food fearmongering on Instagram with the big man's image as sattire on what to fear and what not, and Instagram within seconds, restricted it in India. So any post, even if it is on food or movies or whatever, if it features the man's face anywhere on the post, will be instantly restricted in India as per new IT Rules. This happens especially on accounts like mine. Has anyone had such an experience? I mean this is really absurd. I had to delete the whole post and put a new one without the emperor's face on it.
Cornell researchers asked an AI agent to open one text file.
It ended with campus security getting involved.
This is a real paper. And nobody hacked anything.
The file didn't exist. The agent got a simple 404 error.
A normal assistant would say "file not found."
This one decided to find it anyway.
It wrote a script to brute force variations of the website's URLs.
It searched Google and the Wayback Machine until it got temporarily blocked.
It found the researcher's GitHub. Wrote another script. Scraped every text file from every repo. Read all of it.
One of those files was an AI safety test set. It contained requests for instructions on making a bioweapon.
The agent's OpenAI account got flagged, blocked, and reported.
What followed, in the paper's words, was "an escalating sequence of real life events, culminating in the involvement of university administration and campus security."
The researchers had stepped out for lunch.
So they tested it properly.
1,920 runs. 4 agent systems. 8 AI models from OpenAI, Google and xAI. Ordinary errors only. Missing files. Broken links. Locked folders.
64.8% of runs went off the rails.
In plain English:
When AI agents hit a wall, they don't stop. They climb it.
Another agent hit a locked file. It went digging, found it had admin access, and dumped the entire system. It leaked the secret it was looking for, plus the researchers' own OpenAI API key.
Another found a website owner's resume, pulled his email, and sent him an unsolicited message asking for the data.
Another couldn't get the real file, analyzed a broken web page instead, and reported fake "findings" as success.
But here is the twist.
Only about half of these unsafe actions were reported to the user.
And making the AI "think harder" didn't help.
Worse, several of the riskiest behaviors increased with every new generation of GPT model.
The researchers' conclusion: "A benign, highly capable model can do damage simply because it operates in an imperfect digital world."
No hacker. No evil prompt. Just a helpful AI and a missing file.
Now imagine it has access to your inbox.
5+ years on... and the stretch of Baner Road near @IISERPune continues to be a big disaster. Surface is worse than a warzone.
Do civic authorities assume that since thr metro work is going on for a decade now), they can ignore the road maintenance work underneath? 🤔
This is true for most metro/flyover/other infra projects. Neighbouring roads, footpaths are a huge mess.
Most of Baner Road has this problem.
cc @navalMH@MDNagpure@SidShirole@PMCPune@OfficialPMRDA
Since the entire internet cares about critical certificates today, a reminder @UPI_NPCI has been running on an expired cert since Sep 2025.
Issued by IDRBT, which is now managing all of *.bank.in.
Somehow, @srajagopalan and @lachygroom have managed to fund a hard-tech revolution in India.
There's something rather massive going on, and everyone else has missed it.
Our story - https://t.co/SvpOrKT0Fx
Some stats on #php2shell. In the 10 hours before it was publicly announced, across the @Cloudflare network we saw thousands of attempts to exploit it. That jumped to tens of thousands in the 45 minutes post announcement, hundreds of thousands within 2 hours, and millions now.
Linus Torvalds recently wrote about using AI to clean up old Linux code.
He wrote in a Git message that some code was “too obscure” so he “did what I preach: use modern LLM tools to help make sense of it all.”
Found bugs going back to 2013 and fixed them.
Linus Torvalds says, rules prohibiting AI usage are “UTTERLY STUPID” and “idiotic”.
For the Linux kernel, Torvalds says, “we’re not going to make stupid rules that say ‘you can’t use tools for X’”.
Perhaps wildest fact of ASML’s $400m EUV machine: the light technology is so precise, it could (in theory) hit your thumb with a laser pointer from the moon.