Well if you chose to use color or non default elements then you would have to make sure your customizations were also updated to still maintain usability.
That aside, I am curious to know if you disagree that putting padding on the browser would make viewing your site more enjoyable?
The blog post is riddled with the words "luck" and "timing" which brings doubt into my mind that the team can actually take full responsibility for their actions.
"aware of the potential security threat " but they left it for the next week, who honestly here would do that?
I have also seen comments around the web of migrating to Php Fog because of how they handled the situation. If you are one of these people please enlighten my mind as to how you came to such a logical decision or how much you get paid per year.
Also if Php Fog could enlighten us on how their terms of agreement will work in the case where our intellectual property is stolen on no fault of our own.
Save your sympathy for the sites that are still down, four days and counting
I couldn't agree more. The phpFog team cut corners to deliver quickly. We (devs) all do it. The important part is to clean up after yourself.
The whole blog post seems a bit melodramatic. I mean seriously, who here hasn't spent 3 all nighters in a row fixing a mistake? sack up and do what you should've done before deploying other people's data.
...and who would seriously sue these kids? they handled it poorly but they're smart (definitely smarter than i was at 16) you're lucky it was curious kids, rather than malicious (and experienced) hackers that would've been harder to catch. Do you really want to burden them with a criminal record for life?
Am I the only one who becomes functionally useless after the first 24 hours? I'm nearly 30 now, but the maximum I'd have done 10 years ago was 36 hours.
Exactly. This post tries very hard to trivialize the security holes, and blame their problems on bad luck. They had problems because they decided not to fix glaring security holes immediately.
My understanding is that this is all caused by an unsecured failover server. Hopefully, we get a bit more details of how this came to be and learn what they intend to do with future server deployments.
"aware of the potential security threat " but they left it
for the next week, who honestly here would do that?
Just about everyone. There are always 'potential security threats' that are deemed unlikely to be exploited and that you therefore do not give priority above the multitude of other tasks you have to do. They took a chance and I don't doubt everyone here does that on occasion.
