Taylor,
I don't any longer have the details of the errors during that 18-24
hour period.
But, all seems to be good now.
On Jul 15, 10:57 am, Taylor Singletary
wrote:
> Dewald, you mentioned having problems with user/show -- can you elaborate?
>
>
>
> On Wed, Jul 14, 2010 at 2:47 PM, Dewald Pret
Dewald, you mentioned having problems with user/show -- can you elaborate?
On Wed, Jul 14, 2010 at 2:47 PM, Dewald Pretorius 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 wrote:
>
Yes come on twitter, we demand higher SLA's for your free
service!!
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 faul
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 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, De
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 wrote:
> We all need something to tell our users. Telling them Twitter is
> falling apart is not an option.
