Increasing State of Surveillance From All Sides Around the World - News and Media - Qbix Community

Increasing State of Surveillance From All Sides Around the World

News and Media

Greg

May 8, 2026, 5:36pm

#1

858×600 47.5 KB

Surveillance around the world is increasing. Since the last decade, it has been growing in more and more countries . The noose is being tightened gradually, then all at once – if things continue at this pace, in a few years, it should already be beyond what most people consider bearable today.

No single actor is building “the surveillance stack.” There is no central planning office, no master document, no coordinated rollout. What there are, instead, is dozens of separate proposals, each justified on its own narrow terms, each pushed by different actors with different motivations. They look unrelated until you sketch them on the same page. Then the architecture becomes uncomfortably clear: the pieces being built independently fit together with the precision of a designed system, because the underlying problem each is “solving” is the same problem. Ordinary people have private spaces of action governments and corporations can’t easily monitor, and the people building the pieces don’t want that to remain true.

What follows is my attempt to organize the threats by source, distinguish what’s already deployed from what’s merely proposed, and resist the temptation to either catastrophize or dismiss. Each item is something operating today, currently in legislative motion, or seriously proposed as of mid-2026.

Governments — the identity layer

The identity layer establishes who you are at every level of the stack: which SIM card, which app store account, which OS, which developer published the apps you run. None of these alone is total surveillance. Together, they make every device an identifiable extension of a real human, available to be cross-referenced.

SIM card KYC is required in over 150 countries already. The United States is now considering an FCC proposal from April 2026 that would extend identity verification to phone number issuance — bringing the U.S. in line with most of the rest of the world rather than ahead of it. Final rule earliest 2027, with litigation likely.

App store age verification is rolling out across U.S. states with staggered deadlines. Texas SB2420 took effect January 2026 but is currently enjoined by a federal court on First Amendment grounds. Utah’s compliance deadline is May 2026 with enforcement starting December 2026. Louisiana follows in July 2026. California’s AB 1043 starts January 2027. The mechanism is uniform: upload a government ID to Apple or Google, possibly with a biometric selfie, before creating or modifying accounts.

OS-level age attestation is the next layer up. California AB 1043 requires operating systems themselves to verify and expose user ages to apps. The federal Parents Decide Act would mandate verified rather than self-attested age. Brazil has already passed similar legislation. The architecture shifts the trust anchor from “user chooses what to share” to “OS chooses for the user, and the manufacturer holds the keys.”

Developer KYC is the part that closes the F-Droid-style distribution loophole. Google Android requires developer identity verification starting September 2026 in Brazil, Indonesia, Singapore, and Thailand, going global through 2027. Apps from unverified developers cannot be installed on certified Android devices via normal channels. ADB sideloading and an “advanced flow” remain as escape hatches for technical users; the median user loses sideloading entirely.

Foreign service KYC completes the picture. The UK Online Safety Act requires age verification for adult sites; Reddit, X, Grindr, Tinder, and Discord all now require ID for UK users. The EU’s age verification “mini wallet” became feature-ready April 2026. Australia bans under-16s from Facebook, Instagram, TikTok, X, YouTube, Snapchat, Reddit, Threads, Twitch, and Kick as of December 2025.

Governments — the communications layer

This is the most-defended layer, and the one where resistance has the best track record. The proposals keep coming back; they keep being beaten back; they keep returning in slightly modified forms.

Mandatory client-side scanning of encrypted messages is the EU’s signature push. Chat Control 1.0 was rejected by the European Parliament by a single vote in March 2026. Chat Control 2.0 is in trilogue throughout 2026, and the framing has shifted from “mandatory scanning” to “risk mitigation measures” — which pressures platforms to scan voluntarily without explicit mandate. Same destination, softer mechanism.

CA mandates and TLS interception have been attempted multiple times. Kazakhstan tried in 2015, 2019, and 2020; each attempt was defeated by Mozilla and Google blocking the cert. The EU’s eIDAS Article 45 was partially defeated in 2024, with the legal text now explicitly preserving browser independence — but the implementing acts...