[twitter-dev] Update on Whitelisting

2011-02-10 Thread Ryan Sarver
Beginning today, Twitter will no longer grant whitelisting requests. We will continue to allow whitelisting privileges for previously approved applications; however any unanswered requests recently submitted to Twitter will not be granted whitelist access. Twitter whitelisting was originally

Re: [twitter-dev] Update on Whitelisting

2011-02-10 Thread Edward Hotchkiss
Well I guess this old blog article is irevs now: How Twitter Dropped The Ball on Whitelisting Apps: If you've been wondering about whitelisting and why your app never got Approved [or Denied] then read on. Several weeks ago I posted a ticket per Twitter

Re: [twitter-dev] Update on Whitelisting

2011-02-10 Thread Adam Green
Thanks for finally making this clear, Ryan. I've been critical of the way Twitter was handling whitelisting for months now. Hiding and ignoring are not good ways to build a developer community. While it would be great to have the possibility of whitelisting, it is much worse to offer that promise

Re: [twitter-dev] Update on Whitelisting

2011-02-10 Thread M. Edward (Ed) Borasky
On Thu, 10 Feb 2011 17:26:17 -0500, Adam Green 140...@gmail.com wrote: Now the next step in opening up this marketplace is to create multiple resellers of Twitter API data, and let them compete on price. Giving Gnip a monopoly over this market makes no sense. Twitter's biggest problem is the

Re: [twitter-dev] Update on Whitelisting

2011-02-10 Thread Taylor Singletary
Hi Ed, Some quick answers to a few specific points below: That brings up an interesting question. Suppose I'm using a web-based service like HootSuite that *isn't* using Site Streams (at least, I think they aren't using Site Streams). They're then getting 350 API calls per hour via oAuth in

Re: [twitter-dev] Update on Whitelisting

2011-02-10 Thread M. Edward (Ed) Borasky
On Thu, 10 Feb 2011 15:11:09 -0800, Taylor Singletary taylorsinglet...@twitter.com wrote: Hi Ed, Some quick answers to a few specific points below: With authentication, whitelisting works at the junction of a user and an application. @znmeb using Twitter for iPhone has 350 requests per hour.

Re: [twitter-dev] Update on Whitelisting

2011-02-10 Thread Taylor Singletary
Correction, Ed: Rate limiting is considered on an IP + user basis only at this time, while authenticated, not by client + user. Hold-over from the old world. Taylor On Thu, Feb 10, 2011 at 3:11 PM, Taylor Singletary taylorsinglet...@twitter.com wrote: Hi Ed, Some quick answers to a few

Re: [twitter-dev] Update on Whitelisting

2011-02-10 Thread Umashankar Das
Hi Taylor, Could you please elaborate on IP + user ? Does this mean that the rate of 350/hour is applicable per user? Alternatly, does this mean I can have more than 1 user using the same IP and having seperate rate buckets( 350 each per hour). Thanks Regards Umashankar Das On Fri, Feb 11,

Re: [twitter-dev] Update on Whitelisting

2011-02-10 Thread Carlos Eduardo
Ideally then Twitter limits the maximum number of followers, because what good the company had many followers and not speak to them, my project for example needed to talk to each follower individually, not to be in the same time could divide this into three or four days, but with the limit of Dm