To add to Matt's comment - we at Gnip haven't yet announced a coverage- based product that mimics Twitter's stream.twitter.com/statuses/ filter, but stay tuned (http://twitter.com/gnip). We'll be announcing several new firehose-based products in the near future as soon as we bring them online.
Any nondisplay companies or developers who want to participate in the private beta period of our new commercial Twitter products are welcomed to drop us a note at i...@gnip.com. - Rob Johnson On Nov 22, 1:06 pm, Matt Harris <thematthar...@twitter.com> wrote: > Hi Colin, > > I've answered your questions inline: > > * does the usage of the statuses/filter method on the streaming api impacted > by the Gnip announcement? > > Quoting Ryan Sarver. "Our default levels like Spritzer, Follow and Track > will not be changing, and will remain free and available directly from > Twitter." > > * do we know the maximum rate (or approximation) allowed through > the statuses/filter method? (incidentally, at which point in terms of ratewe > have to consider firehosing, therefore, Gnip options? > > The limits of the free APIs are documented on: > http://dev.twitter.com/pages/streaming_api > > If you need elevated access to the Streams for analysis or > non-display products you should work with Gnip to find the right data > product for your needs. > > Best, > Matt -- 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