I think the purpose of this blog post was to try to reclaim this*'s reputation after the incident, but for me it just solidified that i should never, ever use thiswebhost.
I think the purpose of this blog post was to try to reclaim this*'s reputation after the incident, but for me it just solidified that i should never, ever use thiswebhost.
what are the alternatives ? that guy seems to be a company owner and the registrant of the domain, ie. basically the guy _is_ the company :)
More realistically, though, he could've found some PR person after seeing the fallout from his own attempts to calm the storm. If he sticks with it, that would actually be quite smart of him.
What I'm unclear on is why Bernardo can't be invited back. Was his account deleted in such a way that it's unrecoverable? If so, they're keeping someone who deleted potentially months of a customer's work and data, and claiming it's within reason over one use of the f-bomb.
What if another client's Twitter account is hacked? This policy sounds like an open invite to malicious third parties.
Apparently so..
> So let’s just recap a little; we have 1 account that is suspended with full access to a backup of their data and their domain names. We have another account that is fully terminated, with all data removed, due to severe breach of our terms.
The why seems to be swept under the rug in Doug's post.
Scary.
I am impressed that the company had the foresight to realize that the people they currently have on suck at CS and need to be replaced with someone better at it.
That is a very self-aware decision.
Also you can't cut your nose off despite your face. Jules is clearly a talented tech lead and you can't boot the only guy out the door that understands the inner workings of such a technical company/service.
I am impressed with how this small company is dealing with this; they are doing the best they possibly can.
The proof will be in the long-term-pudding for sure, but I think these are all sensible moves.