Hi Zach, This sounds strange. I'll look into this. You can file this as a bug if you like at http://code.google.com/p/twitter-api/
First a few more diagnostic questions: Are you on a shared network at all? Is your IP address dedicated to your operations alone? Is this IP address used for any other family/co-worker/etc. computing? What specific API methods are you calling? Are you passing authentication credentials at all? Are there any other programs running on the server? What language/libraries are you using? Thanks, Taylor On Mon, Jan 17, 2011 at 7:08 AM, Zach Gardner <z.gard...@hotmail.com> wrote: > This happened again at midnight of the 16th. The last request I made > on the 15th was at 11:59:15 PM with a reset of 12:27:54 AM and a > remaining of 144. The next request I made was at 12:19:15 AM with the > same reset and a remaining of 0. The next successful request I made > was at 12:29:15 AM. > > Is there a better place I should be posting this? Like some sort of > bug tracking application rather than just a development talk? > > -Zach > > -- > Twitter developer documentation and resources: http://dev.twitter.com/doc > API updates via Twitter: http://twitter.com/twitterapi > Issues/Enhancements Tracker: > http://code.google.com/p/twitter-api/issues/list > Change your membership to this group: > http://groups.google.com/group/twitter-development-talk > -- Twitter developer documentation and resources: http://dev.twitter.com/doc API updates via Twitter: http://twitter.com/twitterapi Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list Change your membership to this group: http://groups.google.com/group/twitter-development-talk
