Step 1. Kill the most popular class of clients of an API, one of the few that could afford to pay money for access.
Step 2. Start charging for the API.

But hey at least 1 weeks notice this time…

A Twitter API->nMastodon API bridge server that covers a handful of the most popular API calls would probably be really popular. Yeah I know it's an easy migration but people (myself included) are lazy, the less work to move over the better.

The real big brain move is announcing that you are going to move to a paid model without announcing what the prices are.

You have a week to deal with edge functionality on your app/website breaking, you can wait and hope for the best or just nuke it right away. I know which choice I'd make.

People have been asking if this means Tweetbot might come back. Well it's a possibility if the new pricing is reasonable and ... HAHAHAHAHA
@paul have to say I was so pissed to log on Tweetbot a few weeks back and see it not working and eventually seeing your tweets, I hate Twitter more and more everyday and it’s just a broken platform with no one there who knows what to do next. I have since downloaded ivory and subscribed again to keep supporting, this is probably my first message on the platform, im still getting to grips with it all. Lol
@pugzillah imagine how we felt/feel…
@paul I can’t even begin to imagine, i felt terrible for you guys as soon as I realised what had happened.