Well, I am querying to update user stats (# of followers, location, etc), mostly because the app "ranks" the lawyers, and lawyers are a ridiculously competitive bunch that find it beyond cool that they get ranked.
So since I have the user object, might as well update the URL field in my DB too, right? On Jan 7, 2009, at 2:57 PM, Stuart wrote: > > 2009/1/7 Patrick Minton <[email protected]>: >> Since you get user objects 100 at a time, you would have to query >> about an unreasonable number of users for this to be a problem imho. >> >> Lextweet.com follows about 700 lawyers. This may grow to 2000. 20 >> API calls an hour is a problem for the API? I doubt it. If it is, >> though, I'd be more than happy to reduce the frequency. > > My point was that there's no need to hit the API at all unless you get > a 404 from the avatar URL. Why call the API if you don't need to? > Seems like a pointless waste of resources to me. > > -Stuart > > -- > http://stut.net/ > >> On Jan 7, 2009, at 1:45 AM, Stuart wrote: >> >>> >>> 2009/1/7 Patrick Minton <[email protected]>: >>>> Yes, but once you have the url, why store the actual .png locally? >>>> Sure, if a user changes their profile image you may have a broken >>>> link, but >>>> you can update profile info every hour or so, thus making it a non- >>>> issue. >>> >>> I don't think Twitter would see it as a non-issue if your service >>> has >>> more than a few users and you start requesting their details every >>> hour. A better option is to attempt to download their avatar and >>> only >>> request their profile and update it if you get a 404. >>> >>> -Stuart >>> >>> -- >>> http://stut.net/ >> >> Patrick Minton >> IT Director >> LexBlog, Inc. >> +1 206 697 4548 >> >> >> >> Patrick Minton IT Director LexBlog, Inc. +1 206 697 4548
