I’m sad

API call eaten up...

OK, I work up this am, refreshed my browser and immediately burnt through my 150 API calls in a matter of seconds... Something seems to be very wrong. What else is odd, is I must have uncovered some bug that kills the server too as the rest of the TM was running just so so so so so slow. After hitting refresh I was told I burnt through 2000 API calls in 20 seconds. YIKES!!! Sorry I'm not that big a power user.. not in 25 seconds.

OK heres a screen shot of what happened when it went haywire.

Also, do to the fact i can not have any tweets fire while at work, I had to revoke access from TM from within twitter as I'm not sure when my rolling tweets were to start... they can't start till after work...long story there...

1 person has
this question