Seriously? What you have is not a "server", it's a PC in a rack chassis. Any decent computer designed to go into a datacenter will have a redundant PSU, and a BMC that will log and alert you that one same has failed. I'm responsible for computers that I've literally never seen, and it's really not that big a deal.

The only reason you wouldn't be able to remotely enter in a boot-time decryption password, is if you don't have any remote management capabilities on this server. If this is the case, you should get just better hardware.

I have never been asked that in my life. SSN, mother's maiden name, billing address, but never for characters of my password for the account in question. Where did you run into this, so I can make sure never to do business with them?

The real WTF is that all those passwords were in the clear. What the hell business does anyone have these days, doing anything more than storing a one-way hash?

Just as a point of comparison, the typical latency you want in pro audio applications between when a guitarist plucks a string, and when they hear the note, is less than 15ms. This makes me think that the 80ms might be *acceptable*, but it's by no means ideal.

Clojure, Rails, Hadoop, jeez - what's next, white belts and fixed-gear bicycles? This is probably what these guys look like.

You can't help but wonder if these failures aren't a coincidence.

2x more powerful, is included in the set of "up to" 1000x more powerful.

You see, unlike us savage Americans, the British know that it's not a violation of privacy if the government are the ones watching you.

Google should just cut a deal with parliament to use the 88,000,023 cameras already installed across the UK.

Good tip - you can also set the "scale" variable for FP rounding: :-) me@fuzzy:~$ bc
5/4
1
scale=2
5/4
1.25
scale=10
22/7
3.1428571428