This deal with Gnip is all about *elevated access* you can build whatever product you want (as long as it adheres to the Twitter API Rules) with the basic APIs and basic levels of access.
As to the second part of your question we are setting the pricing as to ensure that their sole position isn't exploited. With that being said, you might find the products to be expensive, but we feel this is premium data and we're mostly focused on consumer facing businesses where the business model is promoted products and the data is free to developers. On Wed, Nov 17, 2010 at 12:51 PM, M. Edward (Ed) Borasky <zn...@borasky-research.net> wrote: > Ryan, what about User Streams? I'm building something around User Streams > but it is a "non-display" analytics application. Am I at risk for Twitter > inserting another business into *my* data stream as well? And I'm curious > how some of the other Streaming consumers are going to react to insertion of > a monopoly middleman into their data source. I briefly dealt with Gnip a > while back and found their API hard to use and their pricing exorbitant. > -- > M. Edward (Ed) Borasky > http://borasky-research.net http://twitter.com/znmeb > > "A mathematician is a device for turning coffee into theorems." - Paul Erdos > > > Quoting Ryan Sarver <rsar...@twitter.com>: > >> Dewald, >> >> The basic levels of all of the streaming APIs -- Spritzer, Follow, >> Track -- will remain open, free and direct from us. Elevated levels >> for non-display use will be served through Gnip. >> >> Hope that answers the question. >> >> Best, Ryan >> >> On Wed, Nov 17, 2010 at 5:44 PM, Dewald Pretorius <dpr...@gmail.com> >> wrote: >>> >>> Ryan, >>> >>> The Gnip blog post states: >>> >>> [QUOTE]Twitter Decahose. This volume-based product is comprised of 10% >>> of the full firehose. Starting today, developers who want to access >>> this sample rate will access it via Gnip instead of Twitter. Twitter >>> will also begin to transition non-display developers with existing >>> Twitter Gardenhose access over to Gnip.[/QUOTE] >>> >>> How does this affect the basic statuses/sample method of the Streaming >>> API? Are you discontinuing it? If so, when? >>> >>> -- >>> 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 >>> >> >> -- >> 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 >> > > > > -- 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
