Earlier quoted context omitted.
“Starting Feb 1st using a third part client will require Twitter Blue.” That’s all it would have taken. Probably would have made a huge increase in subscribers too. This is 100% a control move. He wants full control over how everyone experiences Twitter (not sure why). So this was pulled. Of course you can NEVER go back from this move.
I think that is right. A public API radically slows down product iteration since each feature needs to be considered in terms of its blast radius to third party clients. It probably burned the bridge for good this time, but killing the API to speed up product velocity isn’t an insane move if you value that more than the existing 3rd party ecosystem.
The biggest issue isn’t what they’ve done but how they did it: dismissively, without warning, justified days later with a flimsy provably false excuse.
> A public API radically slows down product iteration since each feature needs to be considered in terms of its blast radius to third party clients.
Twitter’s public API was already lacking. There are several features, like polls, third-party clients never had access to. No one would be surprised if the API remained static forever.
> killing the API to speed up product velocity isn’t an insane move if you value that more than the existing 3rd party ecosystem.
The API wasn’t completely disabled, it’s still working for smaller clients.