If your app gets to the point where you are hitting 20k limit you should a) re-engineer your caching and b) talk to Twitter.
On Sat, Apr 25, 2009 at 22:54, Bill Kocik <bko...@gmail.com> wrote: > > > > On Apr 25, 9:08 pm, Cameron Kaiser <spec...@floodgap.com> wrote: > > > This has changed and I stand corrected; it is documented also on > > > > http://apiwiki.twitter.com/Rate-limiting > > Thanks for the documentation pointer, I hadn't realized that was > there. > > It's surprising, it turns out that if you're going to be making lots > of auth'd requests on behalf of users, there's a tipping point at > which whitelisting begins to work against you, and it's at only 200 > simultaneous users. If you're gonna be above that, you're better off > not being whitelisted. > -- Abraham Williams | http://the.hackerconundrum.com Hacker | http://abrah.am | http://twitter.com/abraham Web608 | Community Evangelist | http://web608.org This email is: [ ] blogable [x] ask first [ ] private.
