Hi Mark, Thanks for your questions -- answers inline below:
On Mon, Mar 28, 2011 at 5:01 PM, Mark Krieger <markskrie...@gmail.com>wrote: > a. I applied for Site Streams Beta Whitelisting more than a week ago, > the application said it is looked at more or less once a week. Is this > accurate? When might I hear? (Company is MediaRoost) > > We're still processing applications for Site Streams beta on a regular basis, but it may take longer than a week or two for you to get access. b. We are using code to test in the meantime with User Streams, just > to get an idea of what to do. I can see how after initial REST calls > to prime the pump that Messages, Mentions, Timeline additions, > Follows, Favorites, User Profile changes, etc will be streamed, and I > can see how to deal with this. It is doable. However I do not > understand how to keep track of some info in the Streams API, and > wonder if these just will require the REST API 'forever': a:Consider > a User who is not me (the authenticated user). I want to see their > profile info. I do not see how the Site/User Stream will send that to > me. b: Consider a User who is not being followed. I want to get their > tweets (etc) via the streaming API. (I know how to get the tweets > they sent via the REST api.) BUT: Since they are not being followed I > will not have seen their tweets on the streaming API. Do I have to > always use the REST API for this? > > The data streamed through User Streams or Site Streams doesn't really involve a query-and-respond structure the way the REST API does -- you'll still want to utilize the REST API (and the specific user's access token) for obtaining metadata and "side" data like other user's timelines for incidental perusal -- basically anything related to a user action: favoriting, retweeting, replying, tweeting, examining alternate timelines, reading & working with lists, etc. Taylor -- 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
