ಆಯ್ಕೆಮಾಡಿದರೆ, ನಿಮ್ಮ ನಗರ ಅಥವಾ ನಿಖರ ಸ್ಥಳದಂತಹ ಸ್ಥಳ ಮಾಹಿತಿಯನ್ನು ವೆಬ್ ಅಥವಾ ಮೂರನೇ-ಪಾರ್ಟಿ ಅಪ್ಲಿಕೇಶನ್ಗಳಿಂದ ನೀವು ಸೇರಿಸಬಹುದು. ನಿಮ್ಮ ಟ್ವೀಟ್ ಸ್ಥಳ ಇತಿಹಾಸವನ್ನು ಅಳಿಸುವ ಆಯ್ಕೆಯನ್ನು ನೀವು ಸದಾ ಹೊಂದಿರುತ್ತೀರಿ. ಇನ್ನಷ್ಟು ತಿಳಿಯಿರಿ
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 forwardhttps://blog.twitter.com/official/en_us/topics/product/2018/investing-in-the-best-twitter-experience-for-you.html …
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.
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
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
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
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
We’ve heard feedback (#breakingmytwitter) 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
We know we have a lot of work to do. Thank you for working with us to get there.
I use Tweetbot so I can read tweets in reverse chronological order from the people I chose to follow. I also like easy access to lists which are also presented in order. Allow me to opt out of your algorithms and I'd begrudgingly consider your apps.
Understand the sentiment. If you do try our iOS/android apps, you may want to consider turning off “show best Tweets first”. It’s not entirely the solution and will still feel different, but you might find it to be closehttps://help.twitter.com/en/using-twitter/twitter-timeline …
Thanks for the feedback.
"Thanks for the feedback" is twitter employee for "lol get fucked"
yup. I just want a normal, chronological feed and will switch to whatever service offers it.
Sir, this is not reasonable. It doesn't matter if you *intended* to kill third party clients; killing third party clients is what you just did. The remaining 3p API is flat-out not adequate. Ppl are switching away from 3p apps en masse today because they're *no longer functional*
Appealing to "well, we broke the thing that made twitter reasonable to you fit badly with our roadmap" doesn't help. You are thinking like a developer, and justifying your decisions as if to your supervisor. But we're users, and we don't care *why* you made things broken.
We only care that you did break it. And it *is* broken now— maybe for "less than 1%" of use cases, but that 1% is your heaviest and most professional (sometimes literally) users.
That power user set is never going to be fully satisfied by your general "main" client (because it's optimized for the average case). This would be true even if the official client is good, which it is not. Many people switching to official today are aghast at how messy it is.
A lot of people are on the verge of switching away from Twitter wholesale due to your persistent policy support for harassment and white supremacy. You are doing a *lot* right now to provide that extra little push to convince people to quit and use a different service.
And if the people you're pushing to leave are that 1% who are such site power users they need a third party app, the chances are heavy that that 1% are the ones writing the content other people stay for. If they go, maybe much more than 1% go with them.
also note that he mentioned "APIs that are used by less than 1% of Twitter developers", smartly avoiding the number of _users_ of the software that this 1% of devs build. I wouldn't be surprised if way more than 1% are on third party clients.
Twitter ಸಾಮರ್ಥ್ಯ ಮೀರಿರಬಹುದು ಅಥವಾ ಕ್ಷಣಿಕವಾದ ತೊಂದರೆಯನ್ನು ಅನುಭವಿಸುತ್ತಿರಬಹುದು. ಮತ್ತೆ ಪ್ರಯತ್ನಿಸಿ ಅಥವಾ ಹೆಚ್ಚಿನ ಮಾಹಿತಿಗೆ Twitter ಸ್ಥಿತಿಗೆ ಭೇಟಿ ನೀಡಿ.
