So if assuming your normal yearly rate is a respectable $100k, and you're on a consulting gig where your annual is effectively 3x that, or $300k, your hourly rate comes out to roughly $144 /hr.

For a short-term engagement, that's not bad at all, but it's awfully high for a 4-year stint. I'd love to learn more about how you came into the position, what it entails, etc. Would you be willing to share here, or at least privately?

DNS RFCs **require** that your MX records refer to IP addresses, not A or CNAME, which you'd get via a Dynamic DNS service.

I don't recall which RFC(s) at the moment, sorry.

Nice FUD. Most Cisco gear is assembled in Mexico from parts sourced worldwide.

This would be fine if Google (and others) didn't constantly mis-locate my home and work IPs. In fact, today, Google thinks that my office IPs are coming from the UK. My range is an old UUNet IP block, hasn't changed in 13 years, and whois (still) shows things properly registered to my physical address. In the past 12 months, Google has considered my office IPs to have been "in" Canada, California, UK, and Japan (should be NY state).

My home IP(s) (VZ FiOS) have had me in Virginia, Canada, and NJ in the same timeframe.

The problem doesn't seem to be limited to Google, either. www.elgato.com showed me their UK site this morning, too, but I can't be sure if they geolocated me by IP address, or by an AdWords session cookie. At the same time, cnn.com, apple.com, etc. see me where I should be, as do a few "what is my IP address" websites.

Anyone have any ideas how this whole geolocation thing actually works nowadays?

Gears of War series. This is how CoOp should be done.

+1 HILARIOUS

From TFA: "The process defined a data center as any room larger than 500 square feet dedicated to data processing..."