[twitter-dev] Re: Too many requests in this time period. Try again later.

2009-07-17 Thread winrich
are you calling the verify credentials call? they started limiting that call to 15 requests per hour due to an attack vulnerability. I started getting that error today too. On Jul 17, 4:03 pm, J.D. jeremy.d.mul...@gmail.com wrote: Today I started getting this error, even only after a handful of

[twitter-dev] Re: Too many requests in this time period. Try again later.

2009-07-18 Thread winrich
yeah, its being limited even when i call it with a valid OAuth sig. On Jul 18, 11:39 am, Chad Etzel jazzyc...@gmail.com wrote: Can someone verify if it is being limited even if the credentials are *correct*? -Chad On Sat, Jul 18, 2009 at 4:46 AM, Swarooprh.swar...@gmail.com wrote: This

[twitter-dev] Re: twitter api server seems to be down (getting invalid signature) since 5.15 pm pst

2009-07-27 Thread winrich
mine broke too. i wonder though, i'm using the oauth python libraries On Jul 27, 6:35 pm, chinaski007 chinaski...@gmail.com wrote: Doug: Does this mean that Marcel made a fix for this?  Or rather that we should examine our code to find the culprit? Thanks, Peter Bray On Jul 27, 6:24 pm,

[twitter-dev] Re: twitter api server seems to be down (getting invalid signature) since 5.15 pm pst

2009-07-27 Thread winrich
ok guys. so my calls were failing on the verify_credentials call and not on the update or timeline calls. the only difference i saw was the the verify_credential call wasn't secured. i changed it to https and it worked. ??? lol On Jul 27, 9:19 pm, Chad Etzel jazzyc...@gmail.com wrote: On