| From my perspective for DO which I host email, web and my SVN on. I'd be happy to roll out production apps on it as well (in fact I'm doing that today). * No verification required for me. Perhaps this is a step when paying by paypal? I've been asked many times for more info when using that. If they pulled this on me, my backup MX will handle email until I get to sort it. * AMS1 was unfortunate. I signed up when it wasn't available and I'm in Europe. I moved my machine to AMS2 when that came up (after their first day of scary high load). I had my host in NYC2 to start with and it was perfectly usable from London, UK over SSH. I couldn't tell the difference between it and my server in the house. * Custom kernels. This is one of two gripes for me. I really want FreeBSD but failing that I want the latest Debian kernel. Keeping an eye on this one. I've got ufw/iptables up front which I have my fingers crossed will protect from any network level issues, logwatch, fail2ban etc to monitor casual attempts and patches are tracked. * SSH key generation: I always regen my SSH keys anyway if I didn't see it happen so this would have been a non issue for me. This is crypto paranoia on my part (and well justified). * Wiping data: when I saw the "securely destroy my data" checkbox I ticked it. Why would you not tick it? To be fair, for $5/month it's not bad. Having played with shared hosting for 17 years, managed massive colo custom deployments and paid through the nose for other hosting, it's the best compromise so far. I looked at Linode but the bottom end was slightly too expensive and I'd rather have SSDs behind it as IO contention on VPSs is usually rather high so that got ruled out. I tried an Amazon EC2 micro instance and it was horribly slow so they didn't get my cash. |
And it's actually ticked by default in the GUI, just not in the API (which is dumb, yes).