So I am building a caching-proxy on my server to make requests to Twitter's databases when my subsites (100+ of them) want to pull user_timeline. Our rate limit seems to go over its limit too much and thus were going to cache responses from api.twitter, and allow our subsites to pull from there instead of directly from you guys.
I was wondering if its possible I can take advantage of the OAuth approach (350requests/hr) in our cache-proxy approach..? Is it possible that I can use our company twitter account as the authorization agent instead of sending the user to a twitter sign in everytime we want to request user_timeline? Or should we be looking into the Streaming API? -- Twitter developer documentation and resources: http://dev.twitter.com/doc API updates via Twitter: http://twitter.com/twitterapi Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list Change your membership to this group: http://groups.google.com/group/twitter-development-talk
