Twitter | Search | |
Rob Johnson Aug 16
I shared the following message with our Twitter team this morning
Reply Retweet Like
Rob Johnson Aug 16
Replying to @robjohnson
We just published a blog post about our priorities for Twitter client experiences. I want to share some insight on how we reached these decisions, and how we’re thinking about 3rd party clients moving forward
Reply Retweet Like
Rob Johnson Aug 16
Replying to @robjohnson
First, some history. 3rd party clients have had a notable impact on the Twitter service and the products we built. Independent developers built the first Twitter client for Mac and the first native app for iPhone. These clients pioneered product features we all know and love.
Reply Retweet Like
Rob Johnson Aug 16
Replying to @robjohnson
We love that developers build experiences on our APIs to push our service and technology forward. We deeply respect the time, energy, and passion they’ve put into building amazing things using Twitter
Reply Retweet Like
Rob Johnson Aug 16
Replying to @robjohnson
We’ve shared with developers repeatedly that our roadmap for our APIs does not prioritize 3rd party client use cases — even as we’ve continued to maintain a couple specific APIs used heavily by these clients and quietly granted user cap exceptions. We haven't been clear enough
Reply Retweet Like
Rob Johnson Aug 16
Replying to @robjohnson
It’s now time to make the hard decision to end support for these legacy APIs — acknowledging that some aspects of these clients will be degraded as a result. We are facing technical and business constraints we can’t ignore and need to turn these off
Reply Retweet Like
Rob Johnson Aug 16
Replying to @robjohnson
We introduced the Account Activity API as a faster & more streamlined way for developers building customer service and brand engagement tools, chatbots, + more. As this new API doesn’t include home timeline data, it is not intended as a solution for 3rd party clients
Reply Retweet Like
Rob Johnson
We’ve heard feedback () from our customers about the pain this causes. We’re committed to understanding why people hire 3rd party clients over our own apps, and we’re going to do better with communicating changes
Reply Retweet Like More
Rob Johnson Aug 16
Replying to @robjohnson
We know we have a lot of work to do. Thank you for working with us to get there.
Reply Retweet Like
Ben Zanin Aug 16
Replying to @robjohnson
In case you're open to feedback: I "hire" 3rd party clients because (1) your offerings betray my trust & don't honour my preferences (or even outright configurations), and (2) I believe in using software I can read and modify to suit my needs as my understanding of them evolves.
Reply Retweet Like
Rob Johnson Aug 16
Replying to @gnomon
Understand the sentiment. I like more control myself. Thanks for the feedback.
Reply Retweet Like
Buster Aug 16
Replying to @robjohnson
Ouch, Rob. I was honestly hoping this was gonna take us back to the other timeline.
Reply Retweet Like
Rob Johnson Aug 16
Replying to @buster
Sorry, “other timeline”? You mean chronological timeline?
Reply Retweet Like
Buster Aug 16
Replying to @robjohnson
Ha. Sorry. No, the light-filled happy timeline. The one that increased investment in the ecosystem rather than reducing it.
Reply Retweet Like
Rob Johnson Aug 16
Replying to @buster
Thanks for the feedback.
Reply Retweet Like