This technique works for updating any filter predicate. The count parameter should work on a shadow account. It won't work on a default access account. We have a number of very large integrations using this technique with Birddog access -- it should scale down to Shadow access just fine.
The documentation makes it clear which cases are supported and which ones are not: http://apiwiki.twitter.com/Streaming-API-Documentation#count The count parameter isn't supported on track streams for computational complexity reasons, and it isn't supported on the default access role for policy reasons. -John Kalucki http://twitter.com/jkalucki Infrastructure, Twitter Inc. On Wed, Feb 24, 2010 at 2:31 PM, Jonathan Strauss < jonat...@snowballfactory.com> wrote: > On Feb 24, 2:06 pm, John Kalucki <j...@twitter.com> wrote: > > The documentation should be pretty clear on this topic. One main > connection, > > and perhaps an auxiliary connection to manage query velocity. > > Hey John, > > Do you recommend this kind of 2 connection setup for updating our user > list when using the follow predicate? > > We've been trying unsuccessfully to use the count parameter when > reconnecting to add new users to our follow list. I've found several > oblique mentions of the count parameter only working in some cases, > but no specifics on how or why. > > We currently have shadow role access for the TweetPo.st app. We're > trying to update our Streaming API connection when new users signup > for TweetPo.st without losing tweets for existing users during > reconnect. Any suggestions on the best way to do this would be greatly > appreciated. > > Thanks! > -jonathan > > ===== > Jonathan Strauss, Co-Founder > http://snowballfactory.com > > Campaign tracking for social media - http://awe.sm > A smarter way to update Facebook from Twitter - http://tweetpo.st > Sharecount button for Facebook - http://www.fbshare.me >