Odds and Ends

Welcome back! The site is now available over http, as you can see. Supporting https will take a few days– a timeline defined not by me, but by our reverse-proxy/CDN service, which also handles TLS for us.

During the interim, don't worry about SSL errors; just skirt them by approaching us through http. Likewise, there may be small anomalies such as mixed content or the occasional missing piece of flair. Thanks for your patience. Once all the small pieces fall into place, we'll be good to go. Or to stay. Or whatever it is we do here.

Last 5 posts by David Byron


  1. John says

    A technical note:

    The icon font here isn't loading, so you just get boxes or blank spaces instead of the quote marks on blockquotes, previous/next arrows, social media icons, etc. This seems to be an same-origin policy issue, with the links to fonts and similar things pointing to "www.popehat.com" while the site is now just "popehat.com," no "www."

  2. says

    Yeah, I noticed that last night on my Nexus while fiddlin' with the collapsing sidebars. There are probably many minor issues that'll require tweakage in the days ahead. Thanks for pointing this one out.

  3. Grifter says


    I get the basic benefits to https generally speaking, I guess I just don't really get the cost/benefit ratio on this site–so I was wondering if it's just the principle of the thing or what. I mean, there's not really passwords for us proles, nor is there commerce stuff, so there didn't seem to be a specific reason that jumped out at me to make the hassle worth it.

    Also you'd think that the first question on that FAQ would be "Why use HTTPS Everywhere?"

  4. Shieldfoss says

    You may want to tweet out that https isn't working yet – I mainly access through a https browser and wondered why you were claiming (on twitter) that you site was working again when it clearly wasn't.

  5. Jim says

    The site is inaccessible to my Windows 7 computers regardless of browser. Linux/OSX machines work fine. The Windows 7 Firefox says "Secure Connection Failed" and "An error occurred during a connection to http://www.popehat.com. SSL received a record that exceeded the maximum permissible length. (Error code: ssl_error_rx_record_too_long). The page you are trying to view cannot be shown because the authenticity of the received data could not be verified. Please contact the website owners to inform them of this problem." If I attempt to remove the https: in the URL it redirects back to the https URL. Help!

  6. Shieldfoss says


    If I attempt to remove the https: in the URL it redirects back to the https URL. Help!

    My first guess would be that you're using the browser extension HTTPS Everywhere, which will automatically substitute HTTPS for HTTP on every site that has a registered HTTPS connection (Which includes popehat, even if it isn't technically working right now).

    For comparison, I am currently at a WIN7 computer. The site loads fine for IE but does not load in FF unless I disable HTTPS Everywhere.

  7. Jim says

    Shieldfoss: Many thanks for your assistance, but I must ask: Where can I find the control for HTTPS Everywhere? I cannot find it amongst my add-ons or other extensions. I am relatively tech capable but cannot find a means to disable it, nor do I recall installing it. And this is across a number of similar machines, desktops and laptops. No problem with OSX/Linux machines.

  8. says

    "Fear of browsing problems"? Whatevs….

    We decided to support https (even though our readers do not log in or share sensitive information) because we were keen to swap out the cries of "Why don't you encrypt?!" for equally irksome cries of "Why don't you encrypt in my preferred way?!"

  9. Autolukos says

    For the last day or two, I've been getting a cached version whenever I visit, even when there is new content; does this fall into the expected small anomalies?