...and all the 3rd parties are shocked.
TechCrunch:
They’ve updated the API Terms of Service to reflect all of this.
“Developers have told us that they’d like more guidance from us about the best opportunities to build on Twitter. More specifically, developers ask us if they should build client apps that mimic or reproduce the mainstream Twitter consumer client experience. The answer is no,” Sarver writes very matter-of-factly.
“If you are an existing developer of client apps, you can continue to serve your user base, but we will be holding you to high standards to ensure you do not violate users’ privacy, that you provide consistency in the user experience, and that you rigorously adhere to all areas of our Terms of Service. We have spoken with the major client applications in the Twitter ecosystem about these needs on an ongoing basis, and will continue to ensure a high bar is maintained,” he continues.
....................
“We need to move to a less fragmented world, where every user can experience Twitter in a consistent way. This is already happening organically – the number and market share of consumer client apps that are not owned or operated by Twitter has been shrinking,”
In other words none of this datascraping, filtering twts, blocking Ads, etc etc. Who ever could have predicted it...
(That's
right, us....and many, many others)
As we wrote some years ago, being a 3rd party application on someone else's platform is always uncomfortable, especially if you do what the main platform also does - like, say, providing access to Twitter's datastream. There is a relationship not akin to
Tracked: Jul 25, 12:41