Livecode.com server down
pystcat at gmail.com
Fri Feb 16 08:09:02 EST 2018
The problem with that, Heather, was I didn't see anything wrong with your tone.
I think someone was reading waaaay to much into your answer and feeling a little hurt by what had happened to them.
> On Feb 16, 2018, at 4:38 AM, Heather Laine via use-livecode <use-livecode at lists.runrev.com> wrote:
> Folks. I think I'm due to issue an apology for the tone I used. I did not intend it to come over the way it did, I'm sorry.
> Let us move on. Any lessons that can be learned, will be learned, we never stand still on these things.
> Best Regards to all
>> On 15 Feb 2018, at 22:12, Mark Wieder via use-livecode <use-livecode at lists.runrev.com> wrote:
>> On 02/15/2018 01:35 PM, Richmond Mathewson via use-livecode wrote:
>>> This IS the way the world goes round these days: nobody will accept responisibility for their
>> ...backing down a bit on this...
>> The whole LC team has been through a harrowing couple of days dealing with this, and it's not "their mistakes". Yes, this does have, in some cases severe, repercussions for us and there are ways to ameliorate the problem (failover servers in different regions, for instance, something easy to accomplish with aws). But pointing the finger at RunRev for a dDos attack isn't fair.
>>> One said to me, just before the New Year; "You wouldn't have these problems if you used Windows".
>> Heh. Yep. You'd have *different* problems.
>> Mark Wieder
>> ahsoftware at gmail.com
>> use-livecode mailing list
>> use-livecode at lists.runrev.com
>> Please visit this url to subscribe, unsubscribe and manage your subscription preferences:
> use-livecode mailing list
> use-livecode at lists.runrev.com
> Please visit this url to subscribe, unsubscribe and manage your subscription preferences:
More information about the Use-livecode