William Sullivan

I should have checked how it looked in twentyeleven before I wrote the above. It still looks all messed up with the older theme, so I am guessing the real culprit is the new Gist embed code from GitHub and not necessarily the twenty twelve theme.

It still is broken, but only in an interesting situation. Unfortunately, that situation obtains every time I use my site. 🙂

When I looked at this page: (https://enkrates.com/2012/01/14/installing-gnu-wget-on-os-x-10-7/) in chrome while logged in, I got my tiny gravatar image from http://www.gravatar.com (http://www.gravatar.com/avatar/bbdcc6a88ae2eea37ac1a2366f085344.jpg?s=25), which naturally breaks the SSL. The tiny gravatar says this next to it: “You are commenting using your Writing Near Hills [My blog’s name] account.” So, it’s attached to the account in my blog, rather than some other service (wordpress.com or another one perhaps?) and maybe that’s crossing some wires in its logic?

If I don’t log in, and look at that same page and open up the comment block, I get a perfectly secure tiny generic gravatar from secure.gravatar.com (https://secure.gravatar.com/avatar/ad516503a11cd5ca435acc9bb6523536?s=25&forcedefault=y&d=retro). So, everything is basically performing as expected, except that my own tiny gravatar is served over http when I’m logged into my own blog. So, it seems like it might be tricky to get this condition, but it happens to me all the time. 🙂

Please let me know if I can help with this further. I’d love to keep running jetpack, but I prefer https if I have to choose.