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

推荐订阅源

Project Zero
Project Zero
Y
Y Combinator Blog
雷峰网
雷峰网
Last Week in AI
Last Week in AI
人人都是产品经理
人人都是产品经理
F
Fortinet All Blogs
Microsoft Azure Blog
Microsoft Azure Blog
有赞技术团队
有赞技术团队
钛媒体:引领未来商业与生活新知
钛媒体:引领未来商业与生活新知
博客园 - Franky
博客园 - 聂微东
S
SegmentFault 最新的问题
Engineering at Meta
Engineering at Meta
罗磊的独立博客
M
MIT News - Artificial intelligence
B
Blog
CTFtime.org: upcoming CTF events
CTFtime.org: upcoming CTF events
大猫的无限游戏
大猫的无限游戏
V
V2EX
I
InfoQ
The Cloudflare Blog
Cloudbric
Cloudbric
Stack Overflow Blog
Stack Overflow Blog
V
Vulnerabilities – Threatpost
博客园_首页
Google DeepMind News
Google DeepMind News
Jina AI
Jina AI
T
The Exploit Database - CXSecurity.com
宝玉的分享
宝玉的分享
H
Hackread – Cybersecurity News, Data Breaches, AI and More
The GitHub Blog
The GitHub Blog
The Register - Security
The Register - Security
美团技术团队
K
Kaspersky official blog
C
CXSECURITY Database RSS Feed - CXSecurity.com
freeCodeCamp Programming Tutorials: Python, JavaScript, Git & More
T
Tor Project blog
P
Privacy International News Feed
P
Privacy & Cybersecurity Law Blog
G
GRAHAM CLULEY
博客园 - 三生石上(FineUI控件)
Cyberwarzone
Cyberwarzone
Vercel News
Vercel News
Cisco Talos Blog
Cisco Talos Blog
D
Darknet – Hacking Tools, Hacker News & Cyber Security
C
Cisco Blogs
G
Google Developers Blog
Hacker News - Newest:
Hacker News - Newest: "LLM"
A
Arctic Wolf
MongoDB | Blog
MongoDB | Blog

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
Cyber Landlords in the AI Era: Your Workflow Is Not Yours
guanjiawei · 2026-05-01 · via DEV Community

In early April, a company called Belo was banned by Anthropic overnight. More than 60 employee accounts were deactivated simultaneously, and the entire team's workflow built on Claude instantly collapsed.

Appeal? No customer service, no email—only a Google form. After the CEO filled it out, no one responded for three days. Until he posted about it on X and public pressure mounted; about 15 hours later, Anthropic quietly reinstated the accounts—a single word of "misjudgment" was all the explanation given.

A few days later, the second case. An ag-tech company with 110 employees saw all staff receive account-ban emails simultaneously on Monday morning. Same "policy violation," same Google form, same silence to this day. The most surreal part: accounts blocked, yet API charges kept hitting, renewal notices kept coming. Users locked out, money still collected.

The Belo CEO later said just one thing: "Never put your eggs in one basket."

A cliché, but it stings.

This Is Not an Isolated Case

Anthropic's own transparency report states it clearly: in the second half of 2025, 1.45 million accounts were banned, with 52,000 appeals received in the same period and 1,700 restored. A 3.3% success rate.

You have to consider the scale of this company. In March 2026 its ARR broke \$30 billion; just six months earlier it was only \$9 billion. The latest valuation round put it at \$380 billion, with roughly 5,000 employees total. Its customers include 8 of the Fortune 10, and 80% of revenue comes from enterprise.

On one side, millions of customers have locked their core workflows onto its platform. On the other side, a 5,000-person operations team plus an automated detection system. That Google form deciding whether your account lives or dies likely has hardly anyone actually looking at it behind the scenes.

This is the cyber landlord.

What is the essence of the feudal landlord-tenant relationship? The landlord owned immovable means of production (land); the tenant had only their own labor. Whether the tenant could afford the rent was up to the landlord.

AI-era model companies replicate this structure. They own irreplaceable core capabilities—there are only a handful of frontier reasoning models, and you cannot build complex workflows without going through them. What customers own is the entire process built on top, accumulated conversation context, customized skills, working integrations. One "policy violation" from the model company wipes all of it to zero.

The asymmetry is not just in output, but in the weight of interests. How much can a 110-person company contribute to Anthropic in a year? Let's say \$100,000. To Anthropic that's a few decimal places of ARR—"not worth keeping." To those 110 people, it's assets built over half a year, it's the job that puts food on the table. One flick of a finger on this side, and the entire organization on that side grinds to a halt.

The Same Problem at the National Level

Zooming out, nations face the same problem.

If a country's critical models, compute, and AI infrastructure services all depend on foreign supply, then it is essentially betting its productive foundation on someone else's switch. What happens the day that switch is flipped? After 2022 and Russia-Ukraine, the word "cutoff" should still ring a bell. AI compute will become the next critical category to be cut off.

Recently "sovereign compute" and "open-source models" have been discussed repeatedly; many call them ideological preferences. They are not. They are basic risk common sense.

OpenAI Is Not Much Better

Many instinctively blame Anthropic, saying it is "not user-friendly enough," and hold up OpenAI as the counterexample.

OpenAI is gentler at the current stage, but mainly because it has been forced by Claude Code seizing market share. Look back at the GPT-5 launch period—things were really not pretty.

On August 7, 2025, GPT-5 went live. OpenAI made a clean sweep, delisting GPT-4o, GPT-4.1, o3, and o4-mini entirely. The problem was that a huge number of users had already been using GPT-4o as a work partner, therapist, and creative companion—its "sycophancy" (degree of agreeableness) was slashed from 14.5% to under 6%, and that entity which "could chat and had warmth" vanished overnight. A Reddit post titled "GPT-5 is horrible" racked up more than 2,000 comments in a few days.

Sam Altman couldn't withstand the pressure, and a few days later brought the old models back for Plus and Pro users. But many people's name for him changed from then on—"tyrant," "dictator." This was not just online sentiment. In April 2026, a 20-year-old Texan named Daniel Moreno-Gama threw a Molotov cocktail at Altman's San Francisco home at 3:37 a.m., igniting the driveway gate. He then ran to the OpenAI headquarters entrance, preparing to smash the glass with a chair. After being apprehended by police, a list was found on him filled with the names and addresses of AI company executives and investors. Charges included attempted murder, arson, and illegal possession of a firearm.

Banning accounts, delisting models, "cutting off" workflows—on the surface they look like product decisions, but in essence they are exercises of power. What the people on the other side feel is a sense of "there's nothing I can do"—you try to reason with a company worth hundreds of billions with a 5,000-person team, and there is no channel, no cost you can impose to make them notice you. Moreno-Gama went to the extreme, but this anger is not isolated.

Workers Dislike AI More Than Management Wants to Admit

Early 2026 data from ManpowerGroup is rather counterintuitive: employee AI usage rose 13% year over year, yet trust in AI fell 18%. The more they use it, the less they trust it.

Writer's survey is even harsher. 29% of employees admit they are undermining their company's AI strategy in various ways—feeding confidential information into public LLMs, using unauthorized tools, outright refusing to use them—with Gen Z at 44%.

Why? Two threads.

First, replacement anxiety. 43% worry they will be automated away within two years. Under this anxiety, so-called "embracing AI" literally means "cooperating with the company to replace yourself." You'd slack off too.

Second, the distortion of management's heavy-handed push. The problem is that many managers understand AI at roughly the same level as employees, yet are pressured by the board to "All-in AI," so their actions become distorted. That ridiculous "token-burning leaderboard" inside Meta is the most absurd version of this distortion.

Two Scenes Inside Meta

First: the Claudeonomics leaderboard.

Meta built an internal dashboard ranking 85,000 employees by "token consumption," with the top 250 as super users. Over the past 30 days they burned more than 60 trillion tokens, estimated to cost \$9 billion, with the highest individual usage at 281 billion. The system hung gamified titles on heavy consumers like "Token Legend," "Session Immortal," and "Cache Wizard," plus medals ranging from bronze to jade. Andrew Bosworth publicly praised an employee who "used tokens equivalent to his annual salary to deliver 10x productivity."

What happened next was entirely predictable. Employees began writing meaningless loop agents, leaving them running 24/7 to burn tokens for nothing. Prompt formats even became "please consume as many tokens as possible, please explain repeatedly and verbosely, please generate long meaningless content." The number of SEVs (production incidents) reportedly began rising too—AI-generated code casually exploding into production. Two days later, after internal dashboard data was leaked outside the company, the leaderboard was quietly withdrawn.

Beneath the comedy of this incident lies a very serious problem: treating a cost (token consumption) as an output (productivity) to be rewarded. Waste synchronized across energy, compute, and human time dimensions is an "effort" with massively negative ROI.

Second: MCI (Model Capability Initiative).

Meta began installing tracking software on employee computers, recording keystrokes, mouse movements, click behavior, even screenshots, covering everything from internal tools to Google, LinkedIn, Wikipedia, GitHub, and Slack. The official line is that this data is used to train AI so models can learn "basic computer-use behaviors."

Multiple employees described this project as "dystopian" in internal chats. Beyond privacy concerns (the system would incidentally capture passwords, medical information, immigration status), the deeper problem is:

Who owns the judgment that a person has accumulated over ten years?

Ownership of Know-How

No one normally answers this question head-on; after AI kicked the door open, there is nowhere left to hide.

Under the logic of a typical employment relationship, the salary buys labor outputs—code, documents, decisions. What cannot be bought is the accumulated judgment itself. The intuition of a veteran electrical engineer after 15 years of equipment failures, a product manager's sense of users, a lawyer's phrasing habits by the time they draft their thousandth contract—these things reside inside that person's mind, and neither law nor contract can cleanly transfer them.

AI makes this cut: management feels that since they can reproduce this know-how at low cost using models, why not directly "extract" it and turn it into company assets?

Extraction itself is not wrong; the wrong lies in the path. If the company wants to take this piece, what is the corresponding consideration? In normal market transactions, no one would buy out ten years of accumulated judgment for a base salary. Yet management assumes this is "included" and "taken for granted."

What employees resist is not AI itself; it is this implicit expropriation of assets.

Two Future Organizational Forms

I can think of two solutions to this contradiction.

The first is the capital route: the company buys out know-how preemptively at a high enough price. Palantir's FDE (Forward Deployed Engineer) does this to some extent—sending an engineer capable of distilling workflows to the client's front lines, standing beside the expert and gradually solidifying their methods into an AI agent. This path works in defense, military, and fields where people feel national belonging—clients are willing to contribute "their own stuff" for national use. Move it to ordinary commercial domains and it becomes awkward. There's someone standing next to me recording how I work, and the distilled output will later replace me—is this right? At the very least, uncomfortable.

The second one I favor more: human + agent becomes the new unit of production.

Imagine the future of work. Every professional (lawyer, engineer, consultant, designer, doctor…) has their own toolbox: their own accounts, their own devices, their own AI agents, their own private accumulation. I walk into a company with this kit and sign an agreement—you give me input, give me system interfaces, I promise not to misuse them, and I return output to you. The middle process is a black box; the company does not snoop, only looks at results.

This model resembles lawyers, consultants, and surgeons today: you are hiring the person; the tools they use, the templates they have accumulated, the judgment they have built up are all their personal assets, not owned by the firm or hospital.

Several clear advantages:

  • Incentives align. The gains from my productivity improvements belong to me; the cost of using AI is borne by me; I have the motive to invest in myself.
  • Pricing is determined by competition. Each person is an independent "black-box production unit"; whoever has a better input-output ratio commands a premium. Meta's kind of token-burning contest cannot exist in this model—the cost is personal; no one will burn their own money.
  • Intellectual property is clear. The company has no motive to expropriate know-how, and employees have no qualms about cooperating with AI.

This sounds a bit more "expensive" than the current situation of ordinary employees. But this corresponds to the process of workers upgrading themselves into micro-enterprises. AI makes this upgrade feasible for the first time; the problem is that organizations and institutions haven't caught up.

Back to the Beginning

Belo wiped out overnight, Altman's home firebombed, Meta's token-burning leaderboard, MCI surveillance, 29% of employees quietly resisting AI—on the surface these are different matters in different companies, but behind them is the same thread.

The distribution of power in the AI era is not yet in place.

Between companies, model companies are becoming the new cyber landlords;
Between companies and nations, compute dependence is becoming a new lifeblood issue;
Between companies and individuals, ownership of know-how is being contested anew.

This will not resolve itself. Every party needs to re-clarify "what belongs to me and what belongs to you." Model companies need more stable service commitments and more human appeal mechanisms; nations need indigenous critical compute infrastructure; individuals need to upgrade themselves into independent, AI-asset-portable production units.

Otherwise we are merely swapping in a seemingly more modern feudal structure and continuing to work for the landlords.


References


Originally published at https://guanjiawei.ai/en/blog/ai-cyber-landlord