Sorry, but exactly this portion of the documentations goes above my head. Can you please explain a bit more to me how a default access account can be used along with the elevated access account to minimize the data loss?
Thanks, Alam Sher On Thu, Feb 25, 2010 at 7:15 PM, John Kalucki <j...@twitter.com> wrote: > Yes, this is indeed what you should be doing. If you have a low tolerance > for data loss, you will then use a total of four accounts: 2 elevated and 2 > default access accounts. If you can tolerate a few missing tweets on each > reconnect, you can just use the two elevated accounts. > > -John Kalucki > > http://twitter.com/jkalucki > Infrastructure, Twitter Inc. > > > On Thu, Feb 25, 2010 at 2:06 AM, Alam Sher <alamshe...@gmail.com> wrote: > >> So in case, if I have 20K users and I have to, say track 60K keywords >> for them + also have to follow all of them. I should be applying for 2 >> higher access accounts one for track predicates and other for follow >> predicate. Does this make sense? >> >> Thanks, >> >> On Feb 25, 8:44 am, John Kalucki <j...@twitter.com> wrote: >> > 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 Kaluckihttp://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 >> > > -- _______________ Alam Sher Khan +92 331 505 5549
