Thank you all, looks like I picked a tricky issue for my first
question here.
After reading all the threads I understand the behavior, although
still a bit confused about the rational behind it. At least I am not
the only one confused about it :)
On Aug 16, 9:16 pm, Bill Kocik wrote:
> I thi
I think the number of "So how does whitelisting really work?" threads
that have taken place, and continue to take place on this list
indicate a lack of clarity in documentation. Perhaps someone from
Twitter can take the task of updating the rate limiting docs to more
explicitly spell out how it a
http://groups.google.co.in/group/twitter-development-talk/browse_thread/thread/e75daf87a23a0a61#
On Sun, Aug 16, 2009 at 7:37 PM, Sam Street wrote:
>
> Necessary, for example, if you use a particular account to notify your
> users of a certain event (sending them notifications). Large apps with
Necessary, for example, if you use a particular account to notify your
users of a certain event (sending them notifications). Large apps with
high traffic might need to send over 150 alerts from the bot account
per hour.
Im thinking it's also used for apps that try to deliver tweets in
'realtime'
