{"id":1397,"date":"2012-01-03T21:02:20","date_gmt":"2012-01-04T03:02:20","guid":{"rendered":"http:\/\/www.wiredprairie.us\/blog\/?p=1397"},"modified":"2012-01-03T21:02:20","modified_gmt":"2012-01-04T03:02:20","slug":"a-post-not-related-to-nest-thermostat-hardware","status":"publish","type":"post","link":"https:\/\/www.wiredprairie.us\/blog\/index.php\/archives\/1397","title":{"rendered":"A post not related to Nest thermostat hardware…."},"content":{"rendered":"
I typed in https:\/\/www.nest.com<\/a> this evening and instead of the nice looking Nest.com web site, I got this:<\/p>\n <\/a><\/p>\n What?! I hadn\u2019t actually noticed that I\u2019d typed https at first, so I was a bit baffled for a moment. After closer investigation, Nest doesn\u2019t have HTTPS apparently for their marketing\/support web site setup on their Amazon CloudFront account (which is what cloudfront.net is).<\/p>\n They really should fix that. <\/p>\n I was having some serious performance issues with their remote access web site earlier. It was barely usable. <\/p>\n That inspired me to dig a little to see what JavaScript libraries they might be using, the chatter on the network, etc. Here\u2019s what I dug up.<\/p>\n JavaScript libraries:<\/p>\n An interesting DIV and solution to a problem with web fonts (found on their main page):<\/p>\n And a method for activating DEBUG mode:<\/p>\n\n
<<\/span>div<\/span> id<\/span>="digits"<\/span>><\/span>\n <!-- Some browsers suffer unfortunate lag the first time they<\/span>\n draw text in fonts loaded over the network. We pre-render<\/span>\n these digits to avoid this lag, and this gets removed at<\/span>\n the same time the loading message is removed. --><\/span>\n 1234567890\n<\/<\/span>div<\/span>><\/span><\/pre>\n
N.DEBUG = ('False'<\/span> == 'True'<\/span>) || (document.location.search.indexOf('debug'<\/span>) > -1) || (C.USERNAME.indexOf('@nestlabs.'<\/span>) > -1);<\/pre>\n