Yes to two different accounts for sampling and filtering. You can filter by keyword (track) and userid (follow) on the same connection. Their limits don't interfere with each other. We encourage this behavior, as our cost is somewhat vaguely aligned with the number of connections and the rate of connections.
The only downside is that you can't, currently, get elevated access for both on the same connection. We can bump track, which leaves follow at the default level, or we can bump follow, but track is at the default level. If this becomes and issue, we'll create some hybrid access levels. The default level is currently pretty generous, most applications don't need anything more. -John Kalucki http://twitter.com/jkalucki Services, Twitter Inc. On Oct 7, 2:04 pm, Damon C <d.lifehac...@gmail.com> wrote: > I've got a quick question on the rate limiting of the streaming API. > The documentation states the following: > > "Each account may create only one standing connection to the Streaming > API." > > Does this mean that I have to use two separate accounts if I want to > connect to both statuses/sample and statuses/filter? > > Similarly, do I have to use separate accounts if I want to access both > the track and follow predicates of the filter stream? > > I'm assuming the answer is yes, but I just wanted to verify. > > Thanks, > > dpc
