Bring back the Streaming APIs
Streaming was a VERY good+easy way to get low key sampling data, without digging into heavy duty "last x million tweets" data dumps. A couple of lines of code (ie minimum wasted researcher time) and you could start collecting/analysing data.
It is very much missed.
Not to mention, of course, the damage removing streaming has done to the general Twitter ecosystem: http://apps-of-a-feather.com/
Si Dawson
shared this idea
3 comments
-
Hi Maziyar- you'll notice that this item is now in the 'nesting' column on our roadmap, under "Follow Graph" functionality (Labs): https://trello.com/b/myf7rKwV/twitter-developer-platform-roadmap
-
Maziyar PANAHI
commented
Hi Pipes,
I do appreciate the new streaming API in Lans as it's called Filtered Stream, however, it does miss the Follow feature as we still have in status/filter API that supports following up to 5000 UserID. Sorry, I couldn't find anything regarding that in Trello.
-
The streaming API (also known as statuses/filter) still exists and has exactly the same access criteria as previously. As part of the Labs efforts, we have announced plans to create a new version of this API in the future - see https://trello.com/c/Z8E40gpV/43-filtered-stream-labs
In my experience, the statuses/filter endpoint has been a very common way for researchers to gather data. Code that calls the statuses/filter endpoint continues to work just fine for collecting Tweets today.
You mention "removing streaming", and it's important to clarify that the functionality that was retired last year was *user* streams, which provided home timeline and notification streaming for user events. This has been partially replaced by the Account Activity API.
There are no current plans to build a direct replacement for user streams.
