TweetDeck users report major problems, including notifications and entire columns failing to load, after Elon Musk's new read-limits; home timelines still load
Over the weekend, Elon Musk limited the number of tweets users can read in a day, which he said was to prevent data scraping.
Context & Ripple Effects
Twitter's daily post-reading caps were introduced as an anti-scraping measure, with different limits for verified, unverified, and new accounts. The TweetDeck failures show that the new reading caps can affect a power-user interface unevenly: home timelines still work while notifications and columns do not.
This arrives amid broader signs of operational strain around Twitter access: paying API customers had already reported outages, bugs, and limited support. For TweetDeck users, the issue matters because columns and alerts are the product's core monitoring workflow, not peripheral features.
First-order effects
- TweetDeck users lose access to some live columns and notifications immediately, impairing multi-stream monitoring even where the home timeline continues to load.
- The read-limit rollout becomes a product-reliability problem for Twitter: a control aimed at scraping appears to disrupt a first-party interface's normal use.
Second-order effects
- Users and organizations that depend on TweetDeck alerts may shift work toward manual timeline checks or alternative monitoring tools until affected columns recover.
- The incident compounds concerns among API customers and other access-dependent users that platform restrictions and service behavior can change faster than support or tooling can adapt.
Third-order effects
- If access controls are deployed across the same systems that serve legitimate interfaces, social platforms will face a continuing trade-off between limiting data extraction and preserving reliable professional workflows.
- The episode is part of a broader move to treat public social data as controlled platform access rather than an implicitly available resource, increasing the value of clear permissions and resilient integrations.
The trend: Platforms are tightening public-data access to curb scraping, but the operational challenge is separating automated extraction from legitimate high-volume use.