Breyer argues the vote preserves an indiscriminate scanning regime that overwhelms police with false positives while failing to identify actual offenders. He cites Swiss federal police data showing ~80% of NCMEC-referred reports are not criminally relevant, and German BKA figures where fewer than half of tips lead to a suspect — evidence that the current voluntary regime harms rather than protects children.
By submitting Breyer's piece to HN with the framing 'Our children lose out,' rapnie amplifies the argument that mass scanning is counterproductive to child protection. The 163-point score signals strong developer-community resonance with the civil-liberties critique.
The editorial argues the extension matters less for what it does than for what it preserves: the political scaffolding for Chat Control 2.0, which would mandate on-device scanning before encryption using government hash databases and AI classifiers. For anyone shipping E2EE messaging, the signal is that the appetite for backdooring encryption at the OS or client layer has not diminished.
Whittaker, president of Signal, has repeatedly stated Signal will withdraw from any EU market that mandates client-side scanning rather than compromise its end-to-end encryption guarantees. Her stance frames the debate as existential: either encryption remains intact or major secure-messaging providers exit, leaving users worse off.
On July 8, the European Parliament greenlit an extension of the so-called 'Chat Control 1.0' regulation — the temporary derogation from the ePrivacy Directive that lets US-headquartered platforms like Meta, Google and Microsoft scan private messages, photos and (in some cases) audio for suspected child sexual abuse material. The extension runs until April 2027. It passed without the amendments civil-liberties MEPs had pushed for, most notably a mandatory judicial-review step before any account gets referred to law enforcement.
Patrick Breyer, the former Pirate Party MEP who has spent five years as the loudest voice against this file, called the vote a defeat dressed as a compromise. "Our children lose out," Breyer said, arguing that indiscriminate scanning floods police units with false positives while doing little to catch actual offenders. His office cited Swiss federal police data showing roughly 80% of NCMEC-referred reports are not criminally relevant, and German BKA figures where fewer than half of tips lead to a suspect being identified.
The vote matters less for what it does — Chat Control 1.0 has been in place since 2021 — than for what it preserves. By re-upping the voluntary regime, Parliament kept the political scaffolding intact for Chat Control 2.0, the mandatory client-side-scanning proposal that has been ping-ponging between the Council and Parliament since 2022. That file, in its current Council draft, would require messaging providers to scan content on-device before encryption, using government-supplied hash databases and, in some versions, AI classifiers for 'unknown' CSAM and grooming.
For anyone shipping encrypted messaging, the meaningful signal is not the 1.0 extension itself — it's that the political appetite for backdooring E2EE at the OS or client layer has not gone away. Signal's Meredith Whittaker has repeatedly said Signal will withdraw from any EU market that mandates client-side scanning. Threema has said the same. Matrix's Matthew Hodgson has spent two years explaining, in painful detail, why on-device scanning is functionally a backdoor: once the client is trusted to inspect plaintext against a state-supplied list, the threat model of end-to-end encryption collapses regardless of what happens in transit.
The technical community's position has been unusually unified: 500+ cryptographers and security researchers, including Ron Rivest, Bruce Schneier and Martin Hellman, signed an open letter in 2024 stating that client-side scanning cannot be made safe. The core argument is boring and correct — any perceptual-hash or ML classifier deployed at global scale generates false positives at a rate that makes universal human review impossible, and any hash list handed to a client is one policy change away from scanning for something other than CSAM. Apple learned this lesson publicly in 2021 when it shelved its own CSAM detection plan after two weeks of researcher backlash.
What's genuinely new in the current EU debate is the concept of 'upload moderation' — the fig leaf Council legal services proposed to square the circle. The idea: don't call it scanning encrypted messages, call it scanning uploaded attachments before encryption is applied. This is the same mechanism with a different label, and Breyer's office has been blunt about it: "There is no such thing as a little bit of encryption. Either the provider can read the message before it's sent, or it can't."
Meanwhile the empirical case for indiscriminate scanning keeps eroding. Ireland's own DPC has questioned whether the voluntary regime is even compatible with GDPR. The EU Commission's own impact assessment, leaked in 2023, admitted false-positive rates for known CSAM detection sit around 10% and grooming detection is worse. A Swiss study published this spring found that of ~1.3 million NCMEC reports processed by Swiss authorities, only about 8% led to any investigative action.
If you ship a messaging, collaboration or file-sharing product to EU users, the two-year runway to April 2027 is not a reprieve — it's the window to make Chat Control 2.0 politically or technically expensive to enforce.
On the architecture side: audit where your product model assumes the client is trusted with plaintext outside the user's control. If you have a desktop client with an update channel you control, a Council-mandated scanning module is technically trivial to ship. Threema's response has been to move key material out of processes the OS can inspect; Signal has invested heavily in reproducible builds and third-party audits of its client binaries. Matrix's Element X has pushed toward a model where server-side state is opaque even to Element's own infrastructure. None of these are silver bullets, but they raise the bar for a compliance-driven backdoor.
On the product side: know your DPO. The 1.0 extension keeps voluntary scanning legal, which means your competitors can — and Meta, Google and Microsoft do — scan message content for CSAM matches under an ePrivacy carve-out. If you're offering E2EE as a differentiator, that carve-out is now your marketing story for two more years. If you're not offering E2EE, understand that you are shipping the surveillance surface the Council wants to mandate.
On the compliance side: watch the Danish Council presidency, which took over July 1 and has telegraphed that it wants to move Chat Control 2.0 forward. The Belgian and Hungarian presidencies before it both failed to find a qualified majority. Germany, the Netherlands, Poland and Austria have been the blocking coalition. If that coalition holds, 2.0 stalls again. If it cracks — most likely under pressure from France, which has flipped positions three times — mandatory client-side scanning could pass in a Council vote before EU Parliament elections in 2029 re-shuffle the file.
The honest read of the July 8 vote is that Parliament chose the least politically costly option: extend the status quo, defer the fight. That's not a win for encryption, but it's not the loss Chat Control 2.0 would be. The next 18 months will be a Council-level slog, and the technical community's job — for once — is not to invent new cryptography. It's to keep explaining, to legislators who don't want to hear it, that a scanner in every EU citizen's messaging client is a backdoor no matter what the regulation calls it.
FTA:What changes with the return of Chat Control 1.0—and what stays the same:*What is coming back:* US tech companies are once again allowed to scan private messages without a warrant or prior suspicion. This affects direct messages on platforms like Instagram, Discord, Snapchat, Skype, and Xbox, as
Stupid parliamentary trick: Hold the vote on the day before the summer break - ensuring that many people have already returned to their home countries. Then use a sort of "reverse" parliamentary trick: the default is that this legislation is accepted. They needed an absolute majority - not
This is a nice piece of democracy right here:"a measure it had rejected twice in March. Although a majority of voting Members of the European Parliament (MEPs) actually opposed the regulation (314 against, 276 in favor, 17 abstentions), the motion to reject it failed to secure the required abso
Roberta Metsola's actions this week jeopardise the legitimacy of the EU project as a whole.It's clear that member countries use the EU as a blame-laundering mechanism to pass domestically unpopular laws, but the forcing of this vote under the urgency procedure that requires absolute majori
Top 10 dev stories every morning at 8am UTC. AI-curated. Retro terminal HTML email.
The EU is a farce, an undemocratic virtue signaling organization, and this is why:- The Parliament voted against the first reading of this proposal twice in 2026, the first time they only supported limited cases for it, while the second time they actually defeated it fully.- The Commission didn'