One way to approach this problem: For each user's tweets that you want to track -- do you want to require that user to be an authenticated member of your site and opt-in to having you track their tweets, likely in the context of providing a (mostly private) Twitter client experience on the web for them? If the answer here is "yes", then Site Streams is a fantastic choice.
However, I think you want to track the publicly created tweets of arbitrary users, whether they are members of your site or not. In this case, Brian's original recommendation to utilize the standard Streaming API's track / follow facilities is best. Like all of our APIs, it does have limitations -- only public statuses are returned, and you can "only" track up to 5,000 users without enhanced streaming permissions. It's best not to worry about requesting additional access levels until you need them. There are some other limitations around tweet velocity and relative percentages of the firehose, but the use case you've detailed here suggests you'd likely not him them. Taylor On Tue, Nov 16, 2010 at 2:01 PM, Neil Sheth <sheth.n...@gmail.com> wrote: > Hi Taylor, > > We are pulling in tweets into our site for various twitter users and > displaying their tweets. The part that confuses me is whether we need to > build the API stream that Brian described in his email (Statuses/Filter) or > the site_streams API as mentioned by our developers? Also, just to check if > we don't build the site_streams one, is this something we're going to have > to build anyway at a later stage? > > Regards > Neil > > On 16 November 2010 21:55, Taylor Singletary <taylorsinglet...@twitter.com > > wrote: > >> Hi Neil, >> >> What are you particularly trying to accomplish with your Twitter >> Integration? How are tweets used in the application? What APIs were you >> leveraging when you were planning a REST-only solution? >> >> While Site Streams is "officially beta" right now, it's very reliable -- >> but whether it's the right solution for you really depends on what you're >> looking to accomplish. >> >> Thanks, >> Taylor >> >> On Tue, Nov 16, 2010 at 1:32 PM, Neil <sheth.n...@gmail.com> wrote: >> >>> We have previously raised a request to obtain twitter whitelisting but >>> have been told by Twitter (Brian) that we have built the wrong >>> solution. Our developers are struggling to understand which solution >>> they need to build for our site www.mystweet.com in order to get >>> whitelisted. They have stated that they are unsure which one to >>> choose: >>> >>> 1) http://dev.twitter.com/pages/site_streams - twitter recommend >>> this for the kind of solution which we want to implement, but this is >>> still in beta >>> >>> 2) http://dev.twitter.com/pages/user_streams_suggestions - but this >>> is not what they would allow for our case. >>> >>> Can you please advise what solution needs to be built? We're hoping >>> to correct this before they go on their holidays >>> >>> Thanks >>> >>> >>> PREVIOUS EMAIL FROM BRIAN >>> >>> Hi Jessel, >>> Sorry about this! There is currently an issue that removes the >>> "rejection reason" from some whitelist emails. Your requests have >>> rejected because we encourage you to use our Streaming API instead to >>> accomplish your purposes. As described onhttp:// >>> dev.twitter.com/pages/streaming_api_methods >>> , you may use the statuses/filter method with the follow parameter to >>> receive a real-time stream of tweets from all the users you're >>> interested in. I apologize for any inconvenience this causes to your >>> project. >>> >>> Thanks for your understanding, >>> Brian >>> >>> -- >>> >>> Twitter developer documentation and resources: >>> http://dev.twitter.com/doc >>> API updates via Twitter: http://twitter.com/twitterapi >>> Issues/Enhancements Tracker: >>> http://code.google.com/p/twitter-api/issues/list >>> Change your membership to this group: >>> http://groups.google.com/group/twitter-development-talk >>> >> >> -- >> Twitter developer documentation and resources: http://dev.twitter.com/doc >> API updates via Twitter: http://twitter.com/twitterapi >> Issues/Enhancements Tracker: >> http://code.google.com/p/twitter-api/issues/list >> Change your membership to this group: >> http://groups.google.com/group/twitter-development-talk >> > > -- > Twitter developer documentation and resources: http://dev.twitter.com/doc > API updates via Twitter: http://twitter.com/twitterapi > Issues/Enhancements Tracker: > http://code.google.com/p/twitter-api/issues/list > Change your membership to this group: > http://groups.google.com/group/twitter-development-talk > -- Twitter developer documentation and resources: http://dev.twitter.com/doc API updates via Twitter: http://twitter.com/twitterapi Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list Change your membership to this group: http://groups.google.com/group/twitter-development-talk
