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

推荐订阅源

Forbes - Security
Forbes - Security
A
Arctic Wolf
M
MIT News - Artificial intelligence
T
Threat Research - Cisco Blogs
T
The Exploit Database - CXSecurity.com
C
CERT Recently Published Vulnerability Notes
NISL@THU
NISL@THU
L
Lohrmann on Cybersecurity
Martin Fowler
Martin Fowler
A
About on SuperTechFans
P
Palo Alto Networks Blog
Project Zero
Project Zero
The GitHub Blog
The GitHub Blog
WordPress大学
WordPress大学
Blog — PlanetScale
Blog — PlanetScale
博客园_首页
大猫的无限游戏
大猫的无限游戏
Cisco Talos Blog
Cisco Talos Blog
P
Proofpoint News Feed
D
DataBreaches.Net
Cyberwarzone
Cyberwarzone
T
Tor Project blog
IT之家
IT之家
P
Proofpoint News Feed
Help Net Security
Help Net Security
S
Securelist
Threat Intelligence Blog | Flashpoint
Threat Intelligence Blog | Flashpoint
C
CXSECURITY Database RSS Feed - CXSecurity.com
Microsoft Azure Blog
Microsoft Azure Blog
V2EX - 技术
V2EX - 技术
K
Kaspersky official blog
Hugging Face - Blog
Hugging Face - Blog
MongoDB | Blog
MongoDB | Blog
B
Blog
N
News and Events Feed by Topic
The Cloudflare Blog
S
Schneier on Security
P
Privacy & Cybersecurity Law Blog
T
The Blog of Author Tim Ferriss
Recorded Future
Recorded Future
Last Week in AI
Last Week in AI
The Last Watchdog
The Last Watchdog
Hacker News - Newest:
Hacker News - Newest: "LLM"
L
LangChain Blog
I
InfoQ
F
Full Disclosure
The Register - Security
The Register - Security
阮一峰的网络日志
阮一峰的网络日志
H
Hacker News: Front Page
V
V2EX

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 Common SOC 2 Failures (Real World) Stop Vibe-Checking Your AI App: A Practical Guide to Evals How to Use SonarQube and SonarScanner Locally to Level Up Your Code Quality Your Next To-Do App Is Dead — I Replaced Mine with an OpenClaw AI Sign a Nostr event in 60 lines of Python using coincurve — no nostr-sdk, no nbxplorer, no rust toolchain ITGC Audit Explained Like You’re in Big 4 Patch Tuesday abril 2026: Microsoft parcha 163 vulnerabilidades y un zero-day en SharePoint Stop scraping everything: a better way to track competitor price changes Listing on MCPize + the Official MCP Registry while routing payments OUTSIDE the marketplace — how I kept 100% of my x402 revenue Building an AI-Powered Risk Intelligence System Using Serverless Architecture Why We Ripped Function Overloading Out of Our AI Toolchain Testing AI-Generated Code: How to Actually Know If It Works SaaS Churn Is Killing Your Business. Here Is What to Do About It (Without a Support Team) The Speed of AI Is No Longer Linear - And Self-Improving Models Are Why How to Implement RBAC for MCP Tools: A Practical Guide for Engineering Teams From Standard Quote to Persuasive Proposal: AI Automation for Arborists I built a CLI that scaffolds complete multi-tenant SaaS apps Axios CVE-2025–62718: The Silent SSRF Bug That Could Be Hiding in Your Node.js App Right Now The dashboard that ended our friendship Data Pipelines Explained Simply (and How to Build Them with Python) The Hidden Cost of AI Systems Nobody Talks About. undefined vs undeclared, and how typeof behaves Switching from file-based jobs to NATS/Kafka in Rust without changing code io_uring Adventures: Rust Servers That Love Syscalls Why Agentic AI is Killing the Traditional Database The POUR principles of web accessibility for developers and designers Quantum Neural Network 3D — A Deep Dive into Interactive WebGL Visualization How To Install Caveman In Codex On macOS And Windows Automation Pipeline Reliability: Why Your Workflow Breaks When Nobody Is Watching I Built an 'Open World' AI Coding Agent — It Works From ANY Folder From Freelancing to Product: A Tech Service Company's SaaS Transformation China's AI Giants: Adding Tencent Hunyuan & ByteDance Doubao to AI University (74 Providers) On the Vibe Coders and Their Lies clerk: Auto-Summarize Your Claude Code Sessions AI Weekly — 2026/04/10–04/17 | The Model Lockdown Is Here, but the Toolchain Is the Real Battleground AI 週報 — 2026/04/10–2026/04/17 模型封鎖潮來了,但工具鏈才是真戰場 Maybe this is how Open-Source apps are born... 🚀 Fine-Tune LLMs with LoRA and QLoRA: 2026 Guide tRPC v11 + Next.js App Router: End-to-End Type Safety Without the Boilerplate ShadCN UI in 2026: Why I Stopped Installing Component Libraries and Started Owning My Components SaaS Billing in React Server Components: Stripe + Supabase Without a Single `useEffect` Join our DEV Weekend Challenge — $1,000 in Prizes Across TEN winners! Submissions Due April 20 at 6:59 AM UTC. Implementing FSRS Spaced Repetition in Flutter + Supabase — Adding Memory Science to an AI Learning App "I Texted My Localhost From the Train — Claude Code Fixed the Bug Before I Got Home" I Built a Sales Prep AI and It Went Deeper Than Expected Design to Code #2: One JSON, Eleven Outputs Solving the 100M-Row Problem: A Summary Table Pattern for High-Volume Push Notification Logs Flutter Web With Wasm: What Actually Changes For Developers I Built 50 Royalty-Free Soundtracks for My Side Project in a Weekend Using AI Music Generation The Vibe Coding Security Checklist: 7 Things to Check Before You Ship Stop Letting Googlebot Guess Fix Your React App's SEO Right Desconstruindo o Streaming do LinkedIn: Como Criar um Engine de Extração de Vídeo de Alta Performance com HLS e FFmpeg (EDA Part-1) EDA (Exploratory Data Analysis) Explained With Real Life — Why Looking at Your Data Is the Most Important Step in Machine Learning Brand Relationship Management at Scale: Our 4-Touch Outreach System for 200+ Brands Why String.fromEnvironment() Might Return an Empty String in Dart JGuardrails 1.0.0 — Hardening Java LLM Apps Against Jailbreaks, Toxicity, and Prompt Injection Plan and Schedule a Full Week of Threads Content From One Claude Conversation Coding Cat Oran Ep3, Five Tables Changed Everything Updated: BFF Pattern I'm done watching freelancers get buried by 200 proposals. So I'm building the alternative. This is my first post BFS Algorithm in Java Step by Step Tutorial with Examples Tracking LLM Pricing Monthly: An Open Dataset for 22 AI Models How We Measure Content ROI on a Comparison Site: Revenue Attribution Without Perfect Data Introducing Nova AI Ops: The AI-Native Operating System for SRE Teams I built a free desktop video downloader for Windows — Grabbit How Talkie OCR Helps Vision-Impaired & Dyslexic Users Read the World Around Them VRCFaceTracking安装和iPhone面捕配置教程,有bug Even CrowdStrike Can't See Your Agents The Automation Gold Rush: What n8n Workflows and Claude Are Opening Up for Developers Right Now
The Pope and the Dynamo
David Aronchick · 2026-05-31 · via DEV Community

On Monday, Pope Leo XIV released a 42,300-word document about artificial intelligence. The English text runs ninety pages, named it Magnifica Humanitas. He picked the date of signature for May 15, the 135th anniversary of Rerum Novarum, which is the 1891 encyclical on labor, capital, and the industrial revolution.

I find it INCREDIBLY interesting that AI has now reached a point where religious figures feel the need to weigh in. The Pope is worried about AI in warfare, and he is, and the final chapter is direct enough about it that the just-war tradition gets explicitly retired. But I read the document (so you don't have to? but you should?) and that is a small fraction of what I took away.

Specifically, the 1891 problem, for lack of a better term, is back, the Catholic Church has had a hundred and thirty-five years to think about that problem, and the answer it landed on then is the same shape as the answer it would land on now.

What 1891 was actually about

Rerum Novarum was published into a world where electrical power and steam-driven manufacturing had centralized the means of production in a way that was new in human history. A worker who used to own his tools and the seasonal value of his labor was now showing up to a factory floor where someone else owned the boilers, the looms, the dynamo, and the building that contained all three. The 1891 question was not "is technology good" since the concept of technology barely existed - it was all just "stuff" that let you "work faster." The 1891 question was who gets to own the dynamo, and what the rest of society owes to the people whose labor is now mediated by an asset they will never personally afford.

Leo XIII's answer was specific and, for the time, contrarian. He defended private property against the socialists, defended workers' associations against the laissez-faire crowd, and insisted the state had a role to play that neither side wanted to admit. He also insisted that the family and the parish and the local trade group all had functions that should not be absorbed upward into the corporation or downward into the atomized individual. That tradition is called subsidiarity. The idea is that decisions get made at the smallest competent unit, and authority only moves upward when the smaller unit cannot do the job.

Not to turn everything into computer science, but subsidiarity is, accidentally, a load-balancing principle, that is core to how a working distributed system gets built. The decision should happen where the data is, where the context is, and where the people affected by the decision actually live. Authority that gets bumped up a layer when it should have stayed local tends to ossify into something nobody asked for, and once it is up there, you cannot get it back down without breaking something.

I want to be careful here, because it is easy to make a Pope into a mascot for whatever position you already held. The encyclical is not a Distributed Thoughts blog post; it is a moral and theological document with an institutional purpose, written for 1.3 billion Catholics, and the parts of it that talk about transhumanism and embryonic dignity are not the parts I am qualified to summarize.

The part I am qualified to summarize is the part that maps to the architecture conversation, and the encyclical itself invites that mapping. Pope Leo XIV does not write about "agents." He does write about subsidiarity in the algorithmic age. He does not use the words "data sovereignty." He does spend about ten thousand words arguing that the asymmetry between the people who own AI infrastructure and the people whose labor is increasingly mediated by that infrastructure produces the same structural problem Leo XIII identified in 1891. He concludes that it does, and goes on for a while about why.

Who showed up to the launch

The presentation on May 25 was attended by, among other people, Chris Olah, who runs interpretability research at Anthropic, is one of the company's co-founders, and gave remarks at the press conference. The remarks said, more or less, that the labs operate inside incentives and constraints that can conflict with doing the right thing, and that people outside those incentives need to pay close attention and be willing to be honest critics. He thanked the Pope for being one of those critics. He used the word "unsettling" about what his own team is finding inside frontier models.

Sit with that for a second. Anthropic flew its head of interpretability to Rome to stand next to the Pope and say "we need outside oversight because we cannot reliably oversee ourselves." Whatever else you think about that, it is the most theologically literate move any of the labs has made in three years. The other labs noticed. The Washington Post coverage framed Anthropic's appearance as a deliberate alignment away from the White House and toward the Vatican, which, regardless of intent, is now the cleanest description of where the moral high ground of this debate actually lives.

The 1891 prescription, in 2026

The labs are very willing to talk about safety. They are very unwilling to talk about who owns the dynamo. The Pope just wrote ninety pages saying the second question is the question, and that the first question, on its own, gets you nothing useful. You can build the safest possible model and still hand it to eleven counterparties under a Glasswing-class contract the rest of the market cannot sign, and you will not have addressed any of the questions a serious moral framework would have asked you to address. You will have addressed about half of one of them.

I do not agree with everything in Magnifica Humanitas. I do not need to. The point is that the institutional response to a wave of centralized infrastructure is forming, the framework that is going to do the most coherent intellectual work over the next decade was just published by a 70-year-old Augustinian, and the people responsible for the centralization have, with one notable exception, not read it.

They should. The diagnosis is good. The diagnosis was already good in 1891. The prescription is the same as it was then, which is that authority not held locally tends to ossify into something nobody asked for and nobody can leave. The labs have built infrastructure of exactly that shape. The grid bills are going up. The data center moratoriums are spreading. The people whose work is increasingly mediated by the model cannot vote on it, cannot leave it, and increasingly cannot afford the electricity it draws.

Push the decisions down. Push the compute down. Keep the dynamo close enough that the parish can see it.

That is what 1891 actually figured out. The Pope is the one who remembered.


Want to learn how intelligent data pipelines can reduce your AI costs? Check out Expanso. Or don't. Who am I to tell you what to do.*

NOTE: I'm currently writing a book based on what I have seen about the real-world challenges of data preparation for machine learning, focusing on operational, compliance, and cost. I'd love to hear your thoughts!


Originally published at The Pope and the Dynamo.