Can't agree more with 2. Please guys, you need to convey a consistant and *visible* message to your users.
On 16 août, 05:21, Jonathan George <jonat...@jdg.net> wrote: > 1. It's been roughly 10 hours. How about an update? > > 2. It'd be great if you would post this to status.twitter.com, in > addition to the developer mailing list. Status is seen by more users, > and the last update you have on it is rather ambiguous. When users > see that the Twitter web interface is up and running, they expect the > apps to be up and running as well. > > best, > jonathan > > On Aug 15, 1:08 pm, Doug Williams <d...@twitter.com> wrote: > > > Hi all --If you have been monitoring our status blog [1] or been to > > Twitter.com today you have noticed that we are once again experiencing > > problems due to external causes. The issues causing the downtime require > > that we once again take measures to bring the site back online. > > > The first step our operations team must take will likely cause API downtime, > > especially affecting OAuth. We apologize for the inconvenience and we will > > work quickly to reduce the impact to the API. We appreciate your patience > > and I will update you as soon as we know more. > > > Thanks, > > Doug
