>From that same post : >http://groups.google.com/group/twitter-development-talk/browse_thread/thread/1acd954f8a04fa84/688b8bfe26a5c178
> Developers > interested in elevated access to the Twitter stream for the purpose of > research or analytics can contact our partner Gnip for more > information. >From http://gnip.com/ > Gnip and Twitter have partnered to bring more Twitter feeds to Gnip > customers. Check out Power Track for 100% guaranteed coverage firehose > filtering and all commercial Twitter data, only from Gnip. >From http://gnip.com/twitter/power-track > • The only feed of its kind: Twitter firehose filtering with 100% > coverage guaranteed > • Boolean operators, unwound URLs, and matching within unwound URLs > supported > • Keyword, username, and location filtering supported > • Unlimited capacity: no restrictions on filter parameters or results > volume - Premium Feed > • Pay for what you get - pricing depends on Tweet volume delivered - > Premium Feed > • Contact [email protected] for more information - Premium Feed HTH On 15 Mar 2011, at 15:04, manusis wrote: > Thanks Augusto. > > But the same thread indicates that tools like Streaming API will > replace whitelisting. So it does not make sense for me for Streaming > API to put under the same umbrella as whitelisting. > > "Since then, we've added new, more efficient tools for developers, > including lookups, ID lists, authentication and the Streaming API. > Instead of whitelisting, developers can use these tools to create > applications and integrate with the Twitter platform." > > > > > > On Mar 15, 7:41 pm, Augusto Santos <[email protected]> wrote: >> I think the answer is you never will. >> This kind of benefit might follow the same rules that whitelist, that will >> no longer be supported just as the thread below >> said.http://groups.google.com/group/twitter-development-talk/browse_thread... >> >> >> >> >> >> >> >> >> >> On Tue, Mar 15, 2011 at 6:58 AM, manusis <[email protected]> wrote: >>> The streaming API mentions about different access roles but does not >>> indicate how one could apply for them. >> >>> "The default access level allows up to 400 track keywords, 5,000 >>> follow userids and 25 0.1-360 degree location boxes. Increased access >>> levels allow 100,000 follow userids (“shadow” role), 400,000 follow >>> userids (“birddog” role), 10,000 track keywords (“restricted track” >>> role), 200,000 track keywords (“partner track” role), and 200 0.1-360 >>> degree location boxes (“locRestricted” role). Increased track access >>> levels also pass a higher proportion of statuses before limiting the >>> stream." >> >>> For our product, we need "shadow" and "partner track" access roles. >>> Could somebody shed any light on how one could apply for the increased >>> access levels? >> >>> Thanks, >>> Rajiv >> >>> -- >>> 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
