Comcastbonnie confirms this is not unusual:
http://twitter.com/ComcastBonnie/statuses/13083585494
That this error happens for some and not others is not surprising.
With new focus on the Search API this type of issue can be addressed :)
Probably related to this:
http://groups.google.com/group/twitter-development-talk/msg/3af17ba93d66abbf
On Thu, Apr 29, 2010 at 11:52, mikawhite mikawh...@me.com wrote:
Comcastbonnie confirms this is not unusual:
http://twitter.com/ComcastBonnie/statuses/13083585494
That this error happens
