Re: Communication Suggestion for LiveCode (RunRev)

2015-05-07 Thread Richmond
On 05/07/2015 10:49 PM, Terence Heaford wrote: An acronym from my old employer before retirement, sums it up I think. C.A.R.E. Customer Awareness Rewards Everyone All the best Terry Well said that man! Much better than: W.L.T.W.S.O.I.O. We Listen To What Serves Our Interests Only.

Re: Communication Suggestion for LiveCode (RunRev)

2015-05-07 Thread Richmond
On 05/07/2015 10:12 PM, Matthias Rebbe | M-R-D wrote: I suggested such an info page, which informs about planned and urgent maintenance or about any other related stuff, a long time ago. I mentioned that this also would reduce the urgent support requests, because in cases of a server fault th

Re: Communication Suggestion for LiveCode (RunRev)

2015-05-07 Thread Terence Heaford
An acronym from my old employer before retirement, sums it up I think. C.A.R.E. Customer Awareness Rewards Everyone All the best Terry > On 7 May 2015, at 20:29, AndyP wrote: > > Very much agree that more information would have gone a long way to reducing > the uncertainty and hostilit

Re: Communication Suggestion for LiveCode (RunRev)

2015-05-07 Thread AndyP
Very much agree that more information would have gone a long way to reducing the uncertainty and hostility vented. I do not understand why such info was not posted on the server status page, it seems the obvious place? I still have two sites down and I am still waiting (patiently) for a response f

Re: Communication Suggestion for LiveCode (RunRev)

2015-05-07 Thread Matthias Rebbe | M-R-D
I suggested such an info page, which informs about planned and urgent maintenance or about any other related stuff, a long time ago. I mentioned that this also would reduce the urgent support requests, because in cases of a server fault the users could see there is already someone working to fix