3 ms·
"After Hudson rightfully said no, the engineer responded by hijacking the site, right down to the domain name. And he did a pretty good job of it. No one could
by nbpoole 15y ago
"After Hudson rightfully said no, the engineer responded by hijacking the site, right down to the domain name. And he did a pretty good job of it. No one could help. Other engineers didn’t have the required credentials. His hosting provider had no means to solve the problem. And even GoDaddy (where he registered the domain) couldn’t figure out a good way around the hack that the engineer had devised to hold the site and its contents hostage."
It's strange to me that the registrar would acknowledge that a takeover had happened but wouldn't be able to fix it, unless the domains were transferred to another registrar. The article doesn't give any details, but if that's the case, the lesson there is not to give other people access to your account at that level (GoDaddy provides a feature to prevent exactly that situation: http://www.godaddy.com/account/accountexec.aspx http://www.godaddy.com/account/accountexec.aspx).
- dpcan 15y agoWe must have to assume the developers registered the domain for the client and it was in their name and the client had no way of actually proving that the domain belonged to them - probably because it was an obscure name, and not the name of their company.
- magic_haze 15y agoSo, essentially, incompetence mixed with blackmail. Can't really blame technology for that. (edit: I think there's a big part of the story we're missing here. Seriously, what company that claims to be a "new and promising internet business" outsources its engineering?)