Musk’s Twitter Intentionally Suspended Tweetbot, Third-Party Apps, Messages Show

The mysterious outage of Tweetbot and other third-party Twitter clients that began Thursday night was an intentional suspension, according to internal messages viewed by The Information. The suspension cut off the ability of people to use Twitter on outside apps, forcing them to go to Twitter’s ...

The Information

DF has a good summation of this latest revelation.

https://daringfireball.net/linked/2023/01/14/information-twitter-slack-confirmation

Even without these leaks if you add up the lack of communication, only impacting the top 25-50 Twitter API clients and clients showing up as suspended in the dev. dashboard. The only conclusion at this point is that it was intentional and not any kind of bug.

For the record, still no official or even unofficial communication from anyone within Twitter.

If You Needed Any More Confirmation, Internal Slack Messages at Twitter Show That Cutting Off Third-Party Clients Was ‘Intentional’

Link to: https://www.theinformation.com/articles/musks-twitter-intentionally-suspended-tweet-bot-third-party-apps-messages-show?rc=jfy0lk

Daring Fireball
And I really want an official public statement. We have a large number of sub. renewals for year 3 of Tweetbot coming up in a couple of weeks. If we're permanently cut off I need to know so we can remove the app from sale and prevent those. Which obviously I'd rather not do.
@paul Also, what is stopping you from getting a new API key? I’m sure they’d shut that one down too, but seeing as they are cherry-picking keys to suspend, they’d have to realize it first.

@tekcor Technically? Absolutely nothing, I have API keys that aren't suspended and have the ability to remotely update them in probably 5-10 minutes.

Practically? I'm not going to play silly games and I don't want to worry about getting sued by someone with an unlimited legal budget.

@paul @tekcor FWIW, there’s no reason to assume this is permanent and not a bug. Right now it’s still just gossip.

If there’s no official statement, then technically you’re still responsibile to your customers to fix it ASAP. Switch keys, get in the fix, and push to the App Store. Better to get it done and have options, than not get it done and have none.

@radley @paul That’s a tough decision to make. While I don’t think Twitter has anything to sue over when using a system they provide, it doesn’t really matter if they weigh TB down in nuisance proceedings that still have to be paid for.