API consume
trante opened this issue · 5 comments
I'm sorry if this is wrong place to ask.
To get user's avatar we still must consume RESTFUL Api?
We can't make it with streaming api which isn't rate limited?
So how do you manage it in "http://twivatar.herokuapp.com/"
Don't you consume API rates.?
AFAIK there is no whitelisted application.
Thank you.
Just point the avatar to:
http://twitter.com/api/users/profile_image/<screen_name>
ie.
On 11 April 2012 09:27, trante
reply@reply.github.com
wrote:
I'm sorry if this is wrong place to ask.
To get user's avatar we still must consume RESTFUL Api?
We can't make it with streaming api which isn't rate limited?So how do you manage it in "http://twivatar.herokuapp.com/"
Don't you consume API rates.?
AFAIK there is no whitelisted application.
Thank you.
Reply to this email directly or view it on GitHub:
#1
Ok. Thank you.
I suppose "http://twitter.com/api/users/profile_image/<screen_name>" is also rate limited?
Regarding to link
But your app (http://twivatar.herokuapp.com/[screen_name) is not rate limited, or..
Per user - so it's client side, but possibly - check their
documentation. I suspect it's around 2000 per hour, but it could be
more.
On 11 April 2012 15:16, trante
reply@reply.github.com
wrote:
I suppose "http://twitter.com/api/users/profile_image/<screen_name>" is also rate limited?
Regarding to <a href="https://dev.twitter.com/docs/api/1/get/users/profile_image/:screen_name"
link
Reply to this email directly or view it on GitHub:
#1 (comment)
I was thinking that rate limit is per application but it is per user.
Where 350 request/hour is reasonable, so that's ok.
https://dev.twitter.com/docs/rate-limiting/faq
Thank you again.