remaining_hits isn't updated
Hi, I realized the remaining_hits that the returned value of the rate_limit_status API was counted down when I tried the other APIs each time till reset_time. The design of my application uses this value to know how often I can use APIs. # The way to get it is the remain seconds (reset_time - current time) will be devided by it. But now, the remaining_hits is already returned 100. My application seems to get my friends' timeline in so high frequency. Did you change the rate_limit_status API and announce it anywere? Forgive my English. -- @nipotan
Re: remaining_hits isn't updated
I realized the remaining_hits that the returned value of the rate_limit_status API was counted down when I tried the other APIs each time till reset_time. The design of my application uses this value to know how often I can use APIs. # The way to get it is the remain seconds (reset_time - current time) will be devided by it. But now, the remaining_hits is already returned 100. My application seems to get my friends' timeline in so high frequency. Did you change the rate_limit_status API and announce it anywere? Are you sure you're authenticating? In TTYtter, I can see the rate limit drop correctly with each request (this is .json). Is this something you're seeing with another format? -- personal: http://www.cameronkaiser.com/ -- Cameron Kaiser * Floodgap Systems * www.floodgap.com * [EMAIL PROTECTED] -- Jesus at a disco: Help! I've risen and I can't get down! -
