The End for Third-Party Twitter Clients
January 15, 2023
Late last week, many third-party Twitter clients stopped working. It didn’t seem to affect all apps — Spring still works for me as of this writing — but the largest ones could no longer connect. Some speculated that this might be a bug. Twitter has had issues and downtime in the last several weeks, so that was plausible. There was pretty strong evidence that this was intentional, however.
Paul Haddad is the developer of Tweetbot, a prominent Twitter client for Apple platforms. Earlier today he tried to get around the outage by swapping out the app’s API keys. This worked briefly, but massively reduced the utility of the app. A few hours later and the app was unable to connect again.
I’ve been on Twitter for more than 15 years, but stopped wanting to post there a couple of months ago. At the beginning of the new Twitter era, many of the podcasters I follow said that the death of the third-party client would be their line in the sand. Several of them jumped off before then, but I’d bet this will be the final straw for many more.
From Twitter’s perspective, this probably doesn’t matter. Third-party clients never saw Twitter’s ads, as they were never included in the API. Third-party clients also couldn’t take advantage of any Twitter Blue functionality, as the APIs were never updated to expose those features. Twitter made some noise a few years ago about getting serious about the API, but that never really seemed to happen. This change could even be a strategy to force an algorithmic timeline on more users.
So from an immediate financial perspective, this move might make sense. Third-party apps were only used by a small percentage of people, so blowback will likely be limited. What’s maddening is that there’s been no official announcement. Are all third-party clients going to be banned? It seems likely, but who knows. It’s just something that’s happening. People are left to guess-and-test.
Whatever’s next, I can’t imagine wanting to trust the Twitter API under the current leadership. Even if this is only targeting third-party clients now, there’s no reason to believe a large API change won’t happen again. A responsible company would give some notice for a change like this. I’d even expect an irresponsible company to announce the change as it was going live. To make a change like this without acknowledging it? That’s reckless and craven.