Sure, I'm just using a whitelisted account to query twitter for the
provided ID's. I then cache that data for 5 days as user id's don't
tend to change much. Combined with the various IPs that app engine
uses, it seems to do OK.
The service also provides for programmatic access to twitter avatars
(hence the name) and it's on use on a few different sites. When the
avatars get queried, I also populate the cache for the screen_name ->
id and vice versa.
It's all on appengine and currently serving about 100k-200k requests/
On Oct 6, 10:08 am, Michael Steuer <mste...@gmail.com> wrote:
> Would you mind sharing how you implemented that? And I assume that this is
> also limited by your rate limit? Are you whitelisted? Since it's not asking
> me to log in, I assume these requests are made over your account...
> On 10/6/09 10:05 AM, "Damon P. Cortesi" <d.lifehac...@gmail.com> wrote:
> > Hi Andrew,
> > I recently added this as a beta feature on my random twitter utility
> > app on appengine, TwitterAvatar.appspot.com.
> > Here's an example:
> > I don't currently have a hard limit on the number of names that can be
> > provided, but due to limitations on Google AppEngine you'll probably
> > need to limit it to about 100 at a time. (I haven't tested that,
> > tho.)
> > As a side note "ids_to_names?ids=1,2,3" would also work.
> > dpc
> > On Oct 3, 6:34 pm, Andrew McCloud <and...@amccloud.com> wrote:
> >> Is it possible to lookup lots of user_ids from screenames without
> >> being rate limited? I'm doing a 1 time import into our db and need to
> >> get it done asap.