I will indeed correct you: rate limits are based on account when using oauth.
Tom On Oct 6, 2010, at 11:39 PM, Matthew Terenzio <[email protected]> wrote: > > > There would be one more issue which requires mentioning: JavaScript's > "Same-origin policy". You can't make a request directly to the Twitter > API via JavaScript: you *will* need a proxy on your own server. > > > Which seems to put web developers at a sever disadvantage for search and > streaming APIs since rate limits are based on IP addresses. Meaning all my > web users count as one whereas the rate limiting is spread out among all the > users a given desktop client. I asked a while back about this and didn't get > a response. It just don't seem fair. Seems impossible to build a web app of > anything more than a couple hundred users if those users want to use search > and or streaming. Or correct me. > -- > 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 -- 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
