2 ms·

This would have been a savvy move from Twitter about say, 4 years ago when it was clear people were going to be sharing a lot of images. As regards developers,

This would have been a savvy move from Twitter about say, 4 years ago when it was clear people were going to be sharing a lot of images. As regards developers, their message is to not build "client apps that mimic or reproduce the mainstream Twitter consumer client experience". However, the mainstream Twitter client experience may at any time be expanded to include whatever you're doing already. That's always a danger when building on someone else's API like this, but the 'inflection point' comes when a company actually starts replacing 3rd party developers' tools with official products. That should help developers decide what to do next... In my case, it's more clear that I don't want to have anything to do with the Twitter API.

tptacek 15y ago
Sounds about right. Twitter seems happy to be one of the best ways to add a social component to otherwise standalone applications, but doesn't seem to care at all about facilitating applications that do nothing but "enhance" Twitter itself. Building applications that are nothing but Twitter enhancements is probably not a good bet; at least, not if it's your only bet.
robgough 15y ago
4 years ago weren't they still struggling with the sheer amount of tweets that were being sent? Adding images into the mix wouldn't have helped much, and may have killed off any momentum they had going? Saying that, it would have been nice if they'd got there sooner.