On Tue, Apr 19, 2011 at 11:54 AM, Taylor Singletary <[email protected]> wrote:
> Site Streams does not support any of the > search/track features of the User Streams, so if your application requires > these capabilities, Site Streams may not be the right fit. Some developers > have asked for Site Streams access with the misunderstanding that it can > provide a greater percentage of the firehose than the self-serve options > available to them today -- this is also not the case. I haven't looked at Gnip recently - are the elevated levels of "filter" access available from them, or do they just sell 1/10 Firehose and 1/2 Firehose? Datasift? Seems to me like you're still going down the "two throats to choke" path - a user licenses part of the feed directly from Twitter and must license the rest of it from a third party "adding value". In my experience that's *not* how enterprises buy stuff - the "one throat to choke" philosophy is how they *got* to be an enterprise. ;-) -- http://twitter.com/znmeb http://borasky-research.net "A mathematician is a device for turning coffee into theorems." -- Paul Erdős -- 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
