Housekeeping: When They Go Low, We Go High Edition

As of today, I’m enforcing HTTPS redirection to this site both on mobile and desktop. The purpose of this is to both to secure the login information of our contributors and to put a very mild brake on the DoS attacks. Since we outsource some of the image hosting to non-secure sources, you may see “orange” instead of “green” on the site information bar.

If this change affects your browsing experience in a negative way, please let me know. Thank you!

9 Replies to “Housekeeping: When They Go Low, We Go High Edition”

  1. Eric L.

    You did this to stave off Google SEO penalties, admit it. I love the author of n-gate.com’s commentary on https: http://n-gate.com/software/2017/07/12/0/

    In his weekly satirizing of Hacker News, he reminds the reader every time it comes up that his site will never use HTTPS, thwarting Lets Encrypt’s “100% HTTPS” goal.

    Made with ❤⃠

    [clap emoji here]

    Reply
  2. Dirty Dingus McGee

    I noticed a while back, last year I think, that if I bring up the site on my iPotato using Safari I get a different “version” of the site. That version is basically an overview (I guess) of the topics. If you “click” a topic you can read the post, but neither read or post comments. If I bring up the site using DuckDuckGo or Startpage it gives full access to the site. Don’t know if others noticed that issue, or it’s just me and my limited knowledge of how these infernal contraptions work.
    It’s NOT a problem because I have absolutely no issues about using the other search engines, as Safari rarely gives me the results I’m needing.
    Just thought I would mention it.

    Reply
  3. CGHill

    You gotta do what you gotta do. And at least it’s easy(ish) to do on WordPress. When I did the migration, I had to move 8000 static pages by hand. (Well, by script updated by hand, anyway.)

    Reply
    • Ben Johnson

      A clever trick is to leave your webserver alone, and stick a reverse proxy web-server in front of it that slaps on the SSL goodness between the original webserver and the browser. It sounds complicated but it’s not hard at all – all sorts of tutorials for NGINX that take about ten minutes to do if you know what you’re doing, and about two hours if you’ve never used NGINX before.

      Reply

Leave a Reply

Your email address will not be published. Required fields are marked *

This site uses Akismet to reduce spam. Learn how your comment data is processed.