What happened
On July 1, 2023, Elon Musk announced 'temporary' limits on how many tweets users could read per day — 'to address extreme levels of data scraping [and] system manipulation', with AI companies the likely target. Verified, Twitter Blue-subscribed accounts got 6,000 posts a day; everyone else got 600 or 300 depending on account age. The caps came a day after Twitter started blocking unregistered users from reading tweets at all. Musk later raised them to 10,000 for verified subscribers and 1,000–500 for others.
The first casualty was TweetDeck, the dashboard Twitter's professional and power users live in. Users — including at least one paying Twitter Blue subscriber, spotted by TechCrunch — reported empty interfaces where tweet columns should be, with notifications, mentions, likes and lists failing to load; The Verge's own accounts were hit. For newsrooms using TweetDeck as a reporting tool and creators running their brands through it, the platform's most valuable users had gone dark.
Two Twitter employees said the limits weren't the cause: the old TweetDeck's legacy APIs were being removed, forcing users onto a new version that had been sitting 'in preview' — where the rate limits do apply.
The breakage fit a pattern. In March 2023 a sole engineer's 'bad configuration change' broke the Twitter API; Musk had laid off over 6,000 of roughly 8,000 employees, leaving 'skeletal' teams on critical infrastructure, and reportedly stopped paying Google Cloud until new CEO Linda Yaccarino mended the relationship. When The Verge asked for comment, Twitter's press line answered with an automated poop emoji — the standard response since the communications department was gutted.
What it cost
TweetDeck's notifications, mentions, likes and lists failed for paying and free users alike; newsrooms lost a core reporting tool mid-breakdown.
Why it happened
The legacy APIs were switched off before the replacement had left preview, so a forced migration and an outage arrived at once.
The users hit first were the most dependent: journalists, community managers and creators for whom TweetDeck was the product.
Even paying Blue subscribers saw the same broken dashboards, undercutting the subscription pitch at the exact moment limits made it matter.
The limits were aimed at AI scrapers, but the visible damage landed on real, loyal users — the cost of the policy was paid by the wrong audience.
The lesson
Killing the old plumbing while the replacement is still 'in preview' pushes your most dependent users off the cliff first — migrate to the new thing before you switch off the old.
Aftermath
Twitter said it would move users to the new TweetDeck, where the reading limits applied, and Musk raised the caps within days. The main site and apps stayed functional — the damage was concentrated on the platform's power tools during the breakdown.
FOLLOW THE EVIDENCE