Well even in the UI, if I come to Twitter at 1:15pm and it says "Twitter will be down for an hour" I think "An hour from when?" Imagine if you went to the bank at 12:30 and it was closed and there was a sign on the door "Closed for lunch be back in one hour" but you don't know when they LEFT for lunch.
Just a thought TjL ps - that said, I've been playing around with the API on the commandline and having a LOT of fun with it :-) On Thu, Feb 19, 2009 at 3:21 PM, Alex Payne <[email protected]> wrote: > > Apologies. That method is mostly meant to be displayed in the UI. > We'll try to provide parseable dates next time. > > On Wed, Feb 18, 2009 at 23:03, TjL <[email protected]> wrote: >> >> I'm sure I'm not the first one to point this out, so I apologize if >> I've missed earlier conversation on this, but this is my first time >> looking at API requests during downtime. >> >> <?xml version="1.0" encoding="UTF-8"?> >> <error reason="Planned maintenance" deadline="about an hour"> >> Twitter is down for Planned maintenance. It will return in about an hour. >> </error> >> >> It's the "about an hour" part that gets me. >> >> Twitter's been down for about an hour, and it still says "about an hour". >> >> Wouldn't it make a whole lot more sense to give an actual parse-able >> time-stamp at least in the 'deadline' field? >> >> It doesn't have to be updated during the outage, but "about an hour" >> doesn't really help much. >> >> TjL >> > > > > -- > Alex Payne - API Lead, Twitter, Inc. > http://twitter.com/al3x >
