Yeah but if it is a Twitter fault there isn't much you can do than say there is a Twitter fault.
Thats also a reason I changed the messages for HTTP status code errors to something meaningful such as 'Twitter is overloaded, please try again later'. At least users can see it's not your app at fault in that instance. On Jul 14, 10:47 pm, Dewald Pretorius <dpr...@gmail.com> wrote: > Because things may not be really falling apart internally, even though > it may appear that way from the outside. > > On Jul 14, 2:59 pm, Dossy Shiobara <do...@panoptic.com> wrote: > > > Why not? I tell my users that all the time, if it's the truth. > > > What benefit is there in lying to your users? > > > On Jul 14, 11:42 am, Dewald Pretorius <dpr...@gmail.com> wrote: > > > > We all need something to tell our users. Telling them Twitter is > > > falling apart is not an option.
