Train of Lights on the Niles Canyon Railway.
Time-lapse panning over the San Francisco bay area from the Gardner Lookout at the east peak of Mount Tamalpais.
Could be anything...
I haven't checked Klout for a long time - while I was away they've decided I'm a expert in Indian politics. Explains a lot...
By default compression doesn't work in CloudFront for a website backed by an Amaxon S3 bucket.
The first step is pretty obvious - switch on compression in CloudFront:
To get to this setting open you distribution, go to the Behaviors tab and edit your behavior(s). Scroll down to the bottom and toggle Compress Objects Automatically to On. Save and drum your fingers while the distribution updates.
The less obvious piece is that CloudFront will only compress files between 1,000 and 10,000,000 bytes (as of writing this post) and it detects the filesize from the Content-Length header. What the documentation doesn't mention is that S3 does not send the Content-Length header by default and so no compression is applied.
Go to S3 and open the properties for your bucket (not for individual files). Expand Permissions and then click Edit CORS Configuration. You need to add Content-Length as an allowed header like this:
The overall message is good - focus on making your users actually awesome rather than you looking awesome with some concrete strategies to find out what that is and how to get there. A central theme is removing barriers to effective usage. The product here is a book. It was hell to read on my phone. Now if the graphics were large and central to the message and couldn't be done other than in some weird non-standard way I might forgive this. But all I needed to on every page was zoom in to get rid of the needless massive borders. That's all it took. Hundreds of times. So I'd recommend this if you still like paper books or are some sort of tablet toting throwback but on phone? No.