I don't think they user cares why Twitter is overloaded, so simply telling them that its overloaded should be enough.
Ryan Sent from my DROID On Jan 20, 2010 7:13 AM, "eco_bach" <[email protected]> wrote: Noticing quite a few ' "temporarily overloaded" 503 Service Unavailable messages when trying to log in lately. I assume Twitter is aware of and trying to correct this, but in the meantime, when building applications, are there any guidelines or best practices to follow when your application is presented with a 503 status? SImple tell the user 'the service is unavailable, please try again later'? Or perhaps a more detailed message, explaining why the service is unavailable?
