Twitter's updated API will limit users from performing simultaneous actions across multiple accounts and using automation; gives developers until 3/23 to comply
This February 2018 announcement is the opening move in a tightening sequence: it follows Twitter's earlier step of limiting the visibility of tweets from potentially abusive accounts, and frames multi-account automation as an abuse vector to be closed off with a hard March 23 compliance deadline.
Developers running multi-account management tools, scheduling services, and automation on Twitter's API have under a month to rework or shut down functionality that performs simultaneous actions across accounts.
Legitimate automation built on the same primitives — cross-posting, coordinated publishing — is caught in the same net as spam networks, since the rule targets behavior rather than intent.
Second-order effects
Developer pushback forces Twitter into serial delays — the compliance date slips within weeks, and the broader legacy API retirement is pushed to August — showing the company's enforcement timeline bends to ecosystem dependence.
Third-party clients like Tweetbot, whose push notifications and auto-refreshing timelines ride on these same APIs, are put on notice that their access is contingent on rules Twitter can redefine unilaterally.
Third-order effects
If the pattern holds, API access stops being an open developer platform and becomes a revocable license — the endpoint visible in 2023, when the developer agreement was amended to ban third-party clients entirely after years of incremental restriction.
Abuse-control justifications become the durable template for platform gatekeeping: each restriction is framed as targeting bad actors, but the cumulative effect is consolidating control of the client experience inside the company itself.
The trend: Platform APIs are shifting from open ecosystems toward tightly controlled, revocable access, with abuse prevention serving as the recurring justification for each round of restriction.
Today, we're clarifying our rules on automation using multiple accounts, as well as removing any possible ambiguity created by our own implementations. Please read, and note the March 23, 2018 deadline. https://blog.twitter.com/...
This is a classic of the “disrupt all sorts of marketing tools while probably not hindering bots/bad actors” genre The overlap between what we think of as social media marketing and malicious bots is interesting tho http://twitter.com/...
Twitter takes an important step in restricting bot armies. If only it would give 3rd party developers permission to help come up with better solutions, too... http://blog.twitter.com/...
If you read between the lines you can see what techniques the IRA LLC (and similar orgs) were doing to abuse the Twitter API for artificial engagement metrics. Lots of obviously automated stuff. http://blog.twitter.com/...
To keep Twitter safe and free from spam, today we are announcing changes to TweetDeck to no longer allow simultaneous actions from multiple accounts. Read more here https://blog.twitter.com/...
Did anyone get a “heads up” up from @Twitter @TwitterSupport prior to them purging followers? I'd give them benefit of doubt but they've been caught too many times censoring conservative accounts #TwitterLockOut https://twitter.com/...
I was about 3,000 down this morning, now it's recovered to -500 and still going. So I guess all those ‘Russian bots’ were real people after all? #TwitterLockOut pic.twitter.com/1owNBejL6U
Yesterday we took action against a number of accounts that we believe have violated our policies by creating new accounts after being suspended. This is a part of the work we're doing every day to improve Twitter.