Check out the rate limiting documentation:
http://apiwiki.twitter.com/Rate-limiting
On Fri, Dec 4, 2009 at 10:39, Daniel Silva wrote:
> Humm. ok. But if I navigate through my application, list three/four times
> 20 users. Then I get no requests for an hour.
> Are you thinking of increasing reques
Humm. ok. But if I navigate through my application, list three/four times 20
users. Then I get no requests for an hour.
Are you thinking of increasing requests?
2009/12/2 Abraham Williams <4bra...@gmail.com>
>
> http://groups.google.com/group/twitter-development-talk/browse_thread/thread/42ba883b
http://groups.google.com/group/twitter-development-talk/browse_thread/thread/42ba883b9f8e3c6e?tvc=2
On Tue, Dec 1, 2009 at 19:44, dmsiva wrote:
> I send http://twitter.com/statuses/user_timeline.xml request with one
> screen_name attribute. Then server give's me a list of status of this
> user.
I send http://twitter.com/statuses/user_timeline.xml request with one
screen_name attribute. Then server give's me a list of status of this
user. Each status have a user tag that contains following attribute.
This following attribute refers to authenticated user? Why sometimes
this attribute is nu