This doesnt look right:

whois facebook.com @8.8.8.8

Whois Server Version 2.0

Domain names in the .com and .net domains can now be registered with many different competing registrars. Go to http://www.internic.net for detailed information.

FACEBOOK.COM.DISABLE.YOUR.TIMELINE.NOW.WITH.THE.ORIGINAL.TIMELINE-REMOVE.NET FACEBOOK.COM.GET.ONE.MILLION.DOLLARS.AT.WWW.UNIMUNDI.COM FACEBOOK.COM.LOVED.BY.WWW.SHQIPHOST.COM FACEBOOK.COM.MORE.INFO.AT.WWW.BEYONDWHOIS.COM FACEBOOK.COM.ZZZZZ.GET.LAID.AT.WWW.SWINGINGCOMMUNITY.COM FACEBOOK.COM

To single out one record, look it up with "xxx", where xxx is one of the records displayed above. If the records are the same, look them up with "=xxx" to receive a full display for each record.

>>> Last update of whois database: Tue, 27 Jan 2015 06:56:04 GMT <<<

Appears to return hosts with name starting with search term, which doesn't make a lot of sense but has likely always been the case. Also @ flag is a dig thing, not whois.

It's just the way whois lookups work. Do a whois lookup of any big site (google.com, microsoft.com, etc) and you'll get a similar response.

You get the info that you're looking for if you do

whois =facebook.com

I've run WHOIS queries on FB before and gotten the same(ish) thing more than a few times -- assumed it was temporary tampering before

It's been that way for a while now and happens with any large site. Try google.com for example and you'll see the same thing.

(Nobody tell him to lookup Microsoft.com)

"Facebook finally figures out that sex /still/ sells better than advertising"

oh yeah, bike courriers have been around in NYC for over a decade. Same goes for every major metropolis in the USA.

"over a decade", heh - I was one 30 years ago.

That's a very tough call to make. Making changes at off-peak times makes some sense, especially if you think there's a likelihood of disruption. But if you're planning for the unexpected, it can be best to make changes when people are their most alert and when plenty of help is around and available. Also, in a fast moving quickly growing business, there's really only so often you can come in at very anti-social hours before burning out.

It is always day somewhere (see this visually specifically to github: http://aasen.in/github_globe/). Best do the work when YOUR A-Team is available, awake, and alert.

I doubt there is a time when they wouldn't have disrupted a significant part of their userbase. Even if you assume a specific place has the majority of users (San Fransisco, Germany, whatever) developers tend to work odd hours anyway.

Firstly, deploying during the day is good because if something goes wrong, the entire team is physically present to deal with it. Second, Github is used worldwide, which means 24 hours a day, so there isn't a "night" to deploy during.

What is the difference between day and night when your users are worldwide?

There is significant variance in population per timezone, and even more significant variance in internet-usage per time zone. Much of this variance is just demographic, but most of it is actually geographic. An interesting and convenient thing about the present layout of the world is that the Pacific Ocean takes up almost half of it, and almost half of the world's land masses are uninhabitable tundra and desert (that's not so relevant to time peaks though).

This has the great effect of lowering the median travel times and information transmission latencies between the world's population centers, and it means that for at least this geological epoch; we're always going to have daily global peak and off-peak times for human-driven activity.

A reasonable approximation is to model a sine wave per region with peak amplitude based on typical usage patterns. For example entertainment services will peak in evenings and at weekends, business services will peak during typical core hours Monday to Friday. With enough users spread across enough regions you never have a good time for all users so in practice it is better to engineer things so you can do deploys / maintenance whenever is best for the teams working on the service.

The Registry database contains ONLY .COM, .NET, .EDU domains and Registrars. Domain Name: CLOUDEMAILAPP.COM Registrar URL: http://www.godaddy.com Updated Date: 2013-06-20 10:37:36 Creation Date: 2012-08-06 09:04:01 Registrar Expiration Date: 2014-08-06 09:04:01 Registrar: GoDaddy.com, LLC Registrant Name: Valentine Orehov Registrant Organization: Registrant Street: 175 Varick St. #646 Registrant City: New York Registrant State/Province: New York Registrant Postal Code: 10013 Registrant Country: United States Admin Name: Valentine Orehov Admin Organization: Admin Street: 175 Varick St. #646 Admin City: New York Admin State/Province: New York Admin Postal Code: 10013 Admin Country: United States Admin Phone: +1.6462574133 Admin Fax: Admin Email: [email protected] Tech Name: Valentine Orehov Tech Organization: Tech Street: 175 Varick St. #646 Tech City: New York Tech State/Province: New York Tech Postal Code: 10013 Tech Country: United States Tech Phone: +1.6462574133 Tech Fax: Tech Email: [email protected] Name Server: NS3.OPTIMIZINGVIDEO.COM Name Server: NS4.OPTIMIZINGVIDEO.COM

wow. they work in my building in wework.

CloudEmailApp, Inc. 175 Varick St. 6th Floor New York, NY 10013

thanks guys! This is pretty much the way I was feeling about it.

this sorta feels like a spam site.

FWIW, the official .nyc site from NYC GOV: http://www.mydotnyc.com/

these are kinda pricey for what they are. fab.com has awesome prints likes these on sale every now and then for half the price and now free shipping. just saying.

seriously. id call up a friend or family member to donate $28 and then just pay them back later or something.