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

推荐订阅源

酷 壳 – CoolShell
酷 壳 – CoolShell
D
DataBreaches.Net
C
Check Point Blog
雷峰网
雷峰网
小众软件
小众软件
GbyAI
GbyAI
美团技术团队
P
Proofpoint News Feed
让小产品的独立变现更简单 - ezindie.com
让小产品的独立变现更简单 - ezindie.com
罗磊的独立博客
大猫的无限游戏
大猫的无限游戏
WordPress大学
WordPress大学
MyScale Blog
MyScale Blog
The Cloudflare Blog
阮一峰的网络日志
阮一峰的网络日志
Apple Machine Learning Research
Apple Machine Learning Research
Y
Y Combinator Blog
Jina AI
Jina AI
爱范儿
爱范儿
Last Week in AI
Last Week in AI
MongoDB | Blog
MongoDB | Blog
I
InfoQ
钛媒体:引领未来商业与生活新知
钛媒体:引领未来商业与生活新知
博客园 - 司徒正美

DEV Community

Authentication Security Deep Dive: From Brute Force to Salted Hashing (With Java Examples) Why AI Systems Don’t Fail — They Drift Spilling beans for how i learn for exam😁"Reinforcement Learning Cheat Sheet" I Replaced Chrome with Safari for AI Browser Automation. Here's What Broke (and What Finally Worked) How Python Borrows Other People's Work The $40 Architecture: Processing 1 Billion API Requests with 99.99% Uptime Vibe Coding: A Workflow Guide (From Zero to SaaS) Most webhook security guides protect the wrong side. The scary part is delivery. Headless CMS for TanStack Start: Build a Blog with Cosmic EU Age Verification App "Hacked in 2 Minutes" — What Actually Happened Comfy Cloud’s delete function does not actually remove files Running AI Models on GPU Cloud Servers: A Beginner Guide Event-driven media intelligence with AWS Step Functions and Bedrock I scored 500 AI prompts across 8 quality dimensions — here's what broke How to Call Google Gemini API from Next.js (Free Tier, No Backend Needed) The Portal Protocol: Reclaiming Human Connection in the Age of AI How to Fix Your Team's Scattered Knowledge Problem With a Self-Hosted Forum Intro to tc Cloud Functors: A Graph-First Mental Model for the Modern Cloud Designing Multi-Tenant Backends With Both Ownership and Team Access I Built a Neumorphic CSS Library with 77+ Components — Here's What I Learned PostgreSQL Performance Optimization: Why Connection Pooling Is Critical at Scale Cómo construí un SaaS multi-rubro para gestionar expensas en Argentina con FastAPI + Vue 3 🚀 I Built an Ethical Hacking Scanner Tool – Open Source Project I Replaced /usage and /context in Claude Code With a Single Statusline A Pythonic Way to Handle Emails (IMAP/SMTP) with Auto-Discovery and AI-Ready Design I Collected 8.9 Million Polymarket Price Points — Here's What I Found About How Markets Really Move EcoTrack AI — Carbon Footprint Tracker & Dashboard Everyone's Using AI. No One Agrees How. 5 self-hosted ebook managers worth trying in 2026 Building Your First AI Agent with LangChain: From Chatbot to Autonomous Assistant
"Sign in with Google" as the surveillance default — and t...
Solidus Network · 2026-06-22 · via DEV Community

"Sign in with Google" has become so naturalized that questioning it feels paranoid. This is itself worth questioning. When a surveillance arrangement becomes the unquestioned default, the surveillance no longer requires justification; the alternative requires justification.

The civic dimension of the default matters. A democratic society depends on the existence of un-surveilled spaces — spaces where citizens can think, discuss, organize, dissent, change their minds, without the activity being logged for later use. The architecture of identity infrastructure determines what un-surveilled spaces are operationally possible. If every authentication is logged centrally, the un-surveilled space collapses.

The historical analogue. The transition from cash payments to card payments transferred a similar amount of activity into the centrally-logged category. The card networks did not advocate for this transfer on the basis of its civic implications; they advocated for it on the basis of convenience. The convenience was real; the civic loss was diffuse and slow to be recognized. Decades later, scholars and regulators are arguing about whether the loss can be reversed.

The same pattern is repeating with identity. The federated authentication default — Sign in with Google, with Apple, with Facebook — was adopted on the basis of convenience. The civic loss is diffuse: every authentication metadata becomes part of a near-complete profile of the citizen's activity. The scale of the surveillance is invisible per-transaction and overwhelming in aggregate.

The architecture of decentralized authentication offers an alternative civics. A credential held by the user, presented selectively, verified cryptographically — no third party in the loop, no log retained by any centralized provider. The same convenience for the user (one identity, many services) but without the surveillance trade-off.

The civic case for this is not merely about privacy as a personal right. It is about preserving the structural conditions under which democratic society operates. The argument requires the same kind of intentionality the historical defenders of voting privacy, mail privacy, and association privacy applied.

Three structural conditions worth preserving.

Condition 1: Unobserved deliberation. Citizens forming political opinions, evaluating candidates, considering controversial views need spaces where the consideration is not logged. The current authentication architecture undermines this because the platforms where deliberation happens authenticate users through the surveillance default.

Condition 2: Reversible association. Citizens joining or leaving associations (political parties, religious groups, advocacy organizations, support networks) need the joining and leaving to be reversible without permanent record. The current authentication architecture creates permanent records of every association joined.

Condition 3: Cross-platform pseudonymity. Citizens engaging in some activities under one persona and other activities under another persona — a long-standing pattern of healthy democratic engagement — need the personas to be cryptographically separable. The current authentication architecture (one Google account → many services) breaks the pseudonymity by default.

Each of these is preserved by the decentralized authentication architecture and broken by the federated default. The civic stakes are real.

The transition from the federated default to the decentralized alternative is not just a technical choice. It is a civic choice. The technologists building the alternative — Solidus and peers — are doing civic work even when the immediate framing is commercial. The buyers integrating the alternative are making civic decisions even when the immediate justification is procurement.

The 100-year frame. The architectural choices made in 2026-2030 about identity infrastructure will shape the structural conditions of democratic society for generations. The convenience trade-off that produced "Sign in with Google" was not, in retrospect, a fair trade. The opportunity to undo it without giving up convenience exists in this decade.

For the citizen, this article is not asking for personal action — most readers cannot meaningfully shape the architectural choices at the platform level. The asks are different: notice the default; support technologists building the alternative; favor platforms that integrate the alternative; advocate where appropriate for regulatory frameworks that mandate it.

The civic case for decentralized authentication is the case for preserving the structural conditions of democratic society. The technology exists. The standards exist. The implementations exist. The choice to deploy them broadly is collective.

solidus.network