How would setting the registrar lock have helped in this case? The registrar lock can be unlocked by the current registrar... which was the target in this case.
It's good advice, but seems kind of irrelevant.
> It's worth noting that while some of Twitter's utility domains were redirected, Twitter.com was not -- and Twitter.com has a registry lock in place.
The former is with Verisign and cannot easily be removed by the registrar. The latter is with the registrar and can be removed by the registrar. In whois status codes "clientXXX" = registrar lock (weak). "serverXXX" = registry lock (stronger).
It's good advice, but seems kind of irrelevant.
> It's worth noting that while some of Twitter's utility domains were redirected, Twitter.com was not -- and Twitter.com has a registry lock in place.