70 requests per hour.

[Leonardo Faria]

hi dudes

i'm a brazilian developer that studying ruby on rails and twitter

i trying to make a twitter spy for public timeline, as digg spy
(digg.com/spy). however, there is a problem: the api limits the user
account to 70 requestes per hour.

my twitter spy reloaded the page each three or five seconds. so, 70
requests is nothing.

what can I do?

thanks

[S Potter]

Leonardo,

There is really nothing you can do unless you register a LOT of users
with twitter and cycle through those logins when you reach the 70
reqs/hr that is mandated by Twitter.com (it is NOT a Twitter4R
limitation).

I am *not* advocating registering a large number of users just to do
this (Twitter.com developers would not be impressed with that), but
unless you get the Twitter.com developers (rather than Twitter4R
developers) to allow a higher number of requests per second for your
application on the server-side (which is highly unlikely unless you
pay them, perhaps?) there is not other options for high frequency
applications currently.

HTH,
Susan

--
mailto:m...@susanpotter.net
www:http://susanpotter.net
blog:http://snakesgemscoffee.susanpotter.net
linkedin:http://linkedin.com/in/susanpotter