Except that I find status.twitter.com is the last place to look for any information about faults. We're getting the flak from users for around 3-4 hours before anything relating to the issue appears on status, and the only official tweets come from the twitterapi account which none of the users follow.
Ryan On 20 July, 07:22, Matt Harris <thematthar...@twitter.com> wrote: > We continue to work on the issues and will be posting updates > tohttp://status.twitter.comas we have news. Please check there for the most > up to date details. > > Thanks for your patience and support as we work through these issues. > > Best, > Matt > > On Mon, Jul 19, 2010 at 10:08 PM, Jason LaFollette < > > > > > > jason.lafolle...@gmail.com> wrote: > > Incase it helps anyone investigating... > > > users/lookup.json returns a complete response when I access it through > > a web browser or fiddler.net > > > users/lookup.json returns a partial response when I access it > > programmatically through a .NET WebRequest or through curl from an OSX > > command line > > > I originally thought it might be http request headers, but I've > > stripped out ever header except Auth within fiddler and I continue to > > get full responses. > > > On Jul 20, 12:59 am, goodtest <goodtest...@gmail.com> wrote: > > > +1 > > > > On Jul 19, 9:25 pm, Cameron Kaiser <spec...@floodgap.com> wrote: > > > > > > Any update on these messed up responses? I'm currently seeing users/ > > > > > lookup.json responses get truncated if I request more than a small > > > > > number of users. > > > > > Ditto for direct_messages.json, although the main timeline is a bit > > better. > > > > > -- > > > > ------------------------------------ personal: > >http://www.cameronkaiser.com/-- > > > > Cameron Kaiser * Floodgap Systems *www.floodgap.com* > > ckai...@floodgap.com > > > > -- When you don't know what you're doing, do it neatly. > > ----------------------- > > -- > > Matt Harris > Developer Advocate, Twitterhttp://twitter.com/themattharris
