I'm developing a Twitter visualizer application. Currently it stores tweets in a DB based on a hashtag using the Streaming API, and then looks up the friends (as in friends/ids) lists of those who've tweeted and stores those lists in a DB.
In essence, it shows how people tweeting with the same hashtag are connected to each other. At least for iteration 1. I'm having a problem with rate limiting because I need to do a friends list lookup for every unique user that has tweeted with the hashtag. My application is conferences, and for larger ones it's very easy to get above several hundred unique users per hour. That doesn't even account the fact that my list could get dirty fairly quickly when conference attendees see someone else in the visualizer and decide to follow them on-the-spot. Simply testing the application has been difficult for this very reason. Is there another way get a list of people a user follows without very quickly running into the rate limit? -- Twitter developer documentation and resources: https://dev.twitter.com/doc API updates via Twitter: https://twitter.com/twitterapi Issues/Enhancements Tracker: https://code.google.com/p/twitter-api/issues/list Change your membership to this group: https://groups.google.com/forum/#!forum/twitter-development-talk
