Small correction: follow is full fidelity and will never be limited. Statuses delivered because of a match on track or locations will count against the same limit.
---Mark http://twitter.com/mccv On Thu, Apr 22, 2010 at 1:57 PM, Mark McBride <mmcbr...@twitter.com> wrote: > This is the correct interpretation. The track limiting is against the > total number of messages delivered to your stream, which means follow > + track + locations all count against the limit. > > ---Mark > > http://twitter.com/mccv > > > > On Thu, Apr 22, 2010 at 1:54 PM, Dima Brodsky <ddbrod...@gmail.com> wrote: >> Hi >> I have a question as to the behaviour when one specifies both a 'track' >> parameter and a 'follow' parameter. From my understanding from the wiki: >> >> statuses/filter >> >> Returns public statuses that match one or more filter predicates. At least >> one predicate parameter, follow, locations, or track must be specified. >> Multiple parameters may be specified which allows most clients to use a >> single connection to the Streaming API. Placing long parameters in the URL >> may cause the request to be rejected for excessive URL length. Use a POST >> request header parameter to avoid long URLs. >> >> Is that the parameters are treated as an 'or' clause and thus I would get >> everything, minus the usual limits, for a particular track predicate and >> everything for all the users I am following. Is this the correct >> interpretation. >> >> Also, if I was just following a track query and then I add a follow query, >> will the number of results in my track query go down because some amount is >> used up by the follow, or are the limits individually placed on track and on >> follow. >> >> Thanks! >> >> ttyl >> >> Dima >> > -- Subscription settings: http://groups.google.com/group/twitter-development-talk/subscribe?hl=en
