Last week, Tweetbot, Twitterific, and other third-party Twitter apps stopped working. At the same time, it was unclear what caused the malfunction. Then, according to user reports, the Tweetbot app started working again, albeit with some limitations.
Users could log into Tweetbot and view posts. However, they couldn’t post their own messages because when they tried to post, they got an error saying “data limit” was reached. But then such work of Tweetbot stopped – the program again completely lost its functionality, and users cannot log into it.
Tweetbot co-creator Paul Haddad wrote in Mastodon that some old, unused API keys stopped working. According to him, this proves that the failure is intentional, and its target is the developers of alternative Twitter clients. Haddad commented on the situation to The Verge and clarified that the team did not receive any messages from Twitter and decided to start using the new API keys and see if that solves the problem.
This is a proof that #Twitter has deliberately suspended @tweetbot. Developers have well created a new Twitter API app and received new credentials. App works, albeit with limits. Twitter API is not broken. If the platform clicked on the resort to such works, it is always at home
— Mysk ???? (@mysk_co) January 15, 2023
Course
TEAM MANAGEMENT
Gather your dream team and lead them towards a common goal.
REGISTER!
This allowed Tweetbot to temporarily avoid any disruptions to the service, even if it brought it to a semi-functional state. However, the new API keys have restrictions from Twitter – the service imposes restrictions on new applications. As a result, Tweetbot users faced issues when trying to post, as they were limited to 300 posts per 15 minutes.
The version about an “intentional” failure in the work of third-party Twitter clients is confirmed by the internal correspondence of the company’s engineers in Slack. This was reported by The Information resource.
“Suspension of third-party applications is intentional,” said the message on the channel that the company’s engineers use to detect service failures.
On Friday morning, a Twitter partner employee asked when his team could expect a list of “approved discussion topics” related to “revocation of third-party customer access.” Another report said Twitter was preparing to issue statements to developers affected by the outage, though it was unclear when they would be ready.
Twitter did not comment on this information. The fact is that after the purchase of the company by Elon Musk and reductions in it, Twitter no longer has a communications department.
Source: The Verge, Engadget, The Information
