We already know why some third-party Twitter clients don’t work. The social network is blocking its API

At the end of last week, third-party Twitter clients like Tweetbot and Twitterrific stopped working. The causes of the problem were not known.although it was believed that this scenario could be caused by two possible reasons: a temporary failure or an API blockage.

Part of the doubts have been resolved and we know what is happening. Twitter has limited access to its API, that is, the set of protocols that developers use to access the social network’s features and data and use it in their own applications.

Twitter stops working on various third-party clients

It has been the social network itself that, through its developer profile, has recognized the movement this Tuesday night. “Twitter is enforcing its longstanding API rules. That may result in some apps not working.” has indicated in a message

The truth is that Twitter’s statement leaves many doubts. As it does not link to “long-standing API rules”, so there is not enough information to know which rules would have been violated or what would have been the problem with certain applications requesting API access.

Apparently, Twitter has not communicated with the developers and, simply, they have seen how their apps They stopped working. In the case of Tweetbot, the company behind the app claims that it has tried to communicate with Twitter, but that they have not received a response.

“We hope this is temporary,” they say. Of course, it should be noted that other apps such as Albatross and Fenix ​​continue to work normally, so the problems are only affecting some applications. For now, we know that access to the API has been limited.

Images: Twitter | tapbots | mamewmy

In Xataka: Twitter closes Revue: the great commitment to monetized newsletters ends less than two years later