On Apr 26, 3:11 am, Abraham Williams <[email protected]> wrote:
> 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.
Caching is not a solution to everything. If I'm whitelisted and I have
200 users who want to see their feed updates, I can get those for them
100 times per hour. If I have 400 users, I can only get them 50 times
per hour, which is still good. 800 users and it's 25 - now
capabilities are quickly degrading. Caching can't fix that.
The way it stands now, whitelisting is a good idea if your app is
using its own single account, or making a lot of unauth'd requests
from a single IP. If you're acting on behalf of an arbitrary number of
users, you don't really need that many of them before their collective
rate limit is much better than your whitelisted one, so whitelisting
becomes "not your friend".
But yes, point B is a good idea. I suspect they'd work with you.
