I think they're talking about the blog itself not being configured to use HTTPS. I had to add an exception in my HTTPS everywhere extension to read the article.