On Wed, Oct 6, 2010 at 5:48 PM, Tom van der Woerdt <i...@tvdw.eu> wrote:

> I will indeed correct you: rate limits are based on account when using
> oauth.
>

Really? Can someone second that. I re-read the documentation and it doesn't
look like it to me. Are the IP limits ignored when you log in as a user. I
know that is the case for the REST api in most cases but I'm talking about
streaming and search.



>
> Tom
>
>
> On Oct 6, 2010, at 11:39 PM, Matthew Terenzio <mteren...@gmail.com> 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>http://dev.twitter.com/doc
> API updates via Twitter: <http://twitter.com/twitterapi>
> http://twitter.com/twitterapi
> Issues/Enhancements Tracker:
> <http://code.google.com/p/twitter-api/issues/list>
> http://code.google.com/p/twitter-api/issues/list
> Change your membership to this group:
> <http://groups.google.com/group/twitter-development-talk>
> 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
>

-- 
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

Reply via email to