We have an application we are building / testing that requires SiteStream functionality. We will need to monitor on our server all our users feeds for specific items in order to provide notification like functionality. As the dev, the current functionality is that we follow each user and monitor that single userstream for our application. Obviously this is not ideal as in certain cases, a users tweets are not exposed to our following account. Besides this, everything works fine. The application for SiteStreams asks:
Do you already have userstreams working for your users? *
This lets us know if you're ready for site streams.
Despite this, it is clear from other sources that Twitter does not want us to create a multi-connection userstream implementation: "Do not open more than a few connections to User Streams from a server application." (from: https://dev.twitter.com/docs/streaming-api/user-streams).
With these factors in mind, do we qualify for SiteStreams because we have a working userstream implementation or do we not qualify because we are expected to use a multi-connection?
I hope my question makes sense, if you need clarification feel free to ask :) Thanks!
Replies
If Site Streams were out of beta today, you would be a prime candidate for the use of it. The scenario you describe is a right fit, provided you also have access tokens for the users you want to stream.
Though we can't add all applicants to the beta (it's still constrained by capacity and undergoing active development), you can apply for candidacy here: http://bit.ly/sitestreams
Thank you very much for the response, very clear. Appreciate it!