Caching the data seems like the right solution. Profile ins't the sort of stuff that changes daily. I would think you could update an individual profile daily (or less).
On Aug 1, 7:14 pm, Scott Aikin <haw...@gmail.com> wrote: > I've got an OAuth site that lets people register through Twitter to > create a profile and post to my site. When you see comments or posts > by these users I show their Twitter profile information and have been > retrieving it with users/show. The problem is that I can only show > this information 150 times each hour which quickly runs out. What is > the best-practices method for accomplishing this? Do I need to cache > their profile information and update it via my crontab? I like the > real-time nature of my current solution, but with the 150 limit it's > just not going to work. Any suggestions?
