I like the idea of information that is public (eg. a blog, as opposed to your activity in your favorite webapp) being easily cached. You might appreciate your

I like the idea of information that is public (eg. a blog, as opposed to your activity in your favorite webapp) being easily cached. You might appreciate your ISP's web proxy cache if you live in New Zealand, for example. It would be nice if everything magically worked in this case, but I don't think we're really there yet. And I'll admit there's a downside - SSL also buys you data integrity (eg. was the blog post modified in transit?) and you don't get that here. Still, I'm not convinced about SSL-by-default for general public information websites (with an obvious exception for sensitive health or political sites, etc). I also don't buy the "protect your readers' privacy" angle. To me, that's "provide your readers an illusion of privacy", since they still have to trust $random_website to not leak the logs they are able to gather. Readers who want identity privacy should use Tor or similar, and not be misled by https-everywhere.