A service and its interface are not the same thing.
For years, Twitter users could read the same network through clients such as Twitterrific, Tweetbot, Fenix and Echofon. Those applications used Twitter’s API but supplied their own interface, notification behavior, accessibility choices and power-user features. Some third-party clients were older than Twitter’s own native mobile apps.
That arrangement ended abruptly in January 2023.
The clients stopped first
On January 13, multiple third-party Twitter clients stopped working. Their developers reported failed API requests and suspended credentials without a clear explanation from Twitter. Ars Technica documented the failures while noting that Twitter-owned TweetDeck still worked.
https://arstechnica.com/tech-policy/2023/01/third-party-twitter-clients-are-broken-whether-by-policy-or-glitch/
A few days later, Twitter said it was enforcing “long-standing API rules.” Then on January 19, its developer agreement was changed to prohibit using licensed materials to create a substitute or similar service to Twitter’s own applications. TechCrunch and Ars both documented the new clause and the timing of the change.
Twitter officially bans third-party clients after cutting off prominent devs
https://arstechnica.com/tech-policy/2023/01/twitter-retroactively-changes-developer-agreement-to-ban-third-party-clients/
The practical meaning was uncomplicated: if an app’s purpose was to provide another way to use Twitter, that app was no longer welcome.
Alternative clients provide more than different colors
Third-party clients can compete on things the platform owner does not prioritize.
One may use denser timelines. Another may offer stronger filtering, keyboard navigation, different notification controls, or a cleaner experience with fewer distractions. A client can also remain comfortable for users who built years of muscle memory around it.
None of that requires a separate social network. The user keeps the same identity, follows the same people and reads the same conversations.
That is exactly why client choice matters. It separates the network from one mandatory presentation of the network.
The official interface becomes part of the price
Once alternative clients disappear, changing interfaces means changing services.
A user who dislikes the official application cannot simply choose another front end while keeping the same social graph. The remaining options are to accept the official interface, use whatever limited alternatives the platform still permits, or leave the network entirely.
There can be legitimate reasons to restrict APIs: security, abuse prevention, infrastructure cost and product consistency are real concerns. But banning substitute clients goes further than limiting abusive requests. It makes the platform’s own interface a condition of participation.
The network may contain the same people the next morning.
The choice around how to reach them is gone.