We're continuing to fight with the limits of MySQL scalability. This is contributing to problems with user related data such as social graph lists, which is resulting in 500s. Operations is working hard and focusing on the fix. Thanks, Doug --
Doug Williams Twitter Platform Support http://twitter.com/dougw On Mon, Jun 1, 2009 at 11:02 AM, Trevor Livingston <[email protected]>wrote: > > > Seems to be working now. Would like to know why this might have been > failing though... > > On Jun 1, 11:28 am, Trevor Livingston <[email protected]> wrote: > > I said "tlivings" in the original message. That is the only user that > > seems to fail. > > > > Thanks! > > > > Trevor. > > > > On Jun 1, 10:49 am, Matt Sanford <[email protected]> wrote: > > > > > Hi there, > > > > > The rate limit returns HTTP 400, as stated in the documentation > > > [1]. A 500 indicates some server-side error so knowing what user this > > > is for might help us find the root cause. > > > > > Thanks; > > > – Matt Sanford / @mzsanford > > > Twitter Dev > > > > > [1] -http://apiwiki.twitter.com/Rate-limiting > > > > > On Jun 1, 2009, at 8:37 AM, Trevor Livingston wrote: > > > > > > If I make the callhttp://twitter.com/statuses/friends.xmlorfriends/ > > > > username.xml (or json format), I get a 500 error, but only with one > > > > username. If I test against tlivings, 500 error; anyone else no > > > > problem. > > > > > > Is this indicative of an api limit? It happens from my office as well > > > > as my home. > > > > > > Thanks. >
