Stick to baseball, 1/4/20.

Happy New Year! I skipped last week since it was the holidays and I was offline quite a bit, but in the last couple of weeks I had a bunch of year-end board game posts, including my top 10 games of 2019 for Paste, my best games of the year by category for Vulture, and the top 8 board game apps of 2019 for Ars Technica.

My free email newsletter will return on Monday, time and health (I’m sick yet again) permitting. My second book, The Inside Game, will be out on April 21st and is available for pre-order.

And now, the links…

Comments

  1. Possibly anecdotal, but everyone who had green bean casserole at Thanksgiving is healthy today. (I’m sick, too.)

  2. Muppet Christmas Carol is beyond awesome. I just wish that Disney would release the full version on Blu Ray instead of the edited version.

  3. Why did you block people on mobile devices from viewing your website?

  4. For the past few months, I often get a 403 error from my Verizon cell trying to access the site. Only when I’m on the Verizon network, all’s good if I’m on WiFi.

  5. Same with Jim and Chris – it’s not that you blocked people on mobile devices, it’s I (and others) can’t access the site unless I’m on WiFi. If I’m on LTE, no dice. I have Verizon as well.

  6. Chris Jones

    And for what it’s worth, last night after posting my comment I gave it a test and had the same issue. My IP at the time was 174.204.23.130.

    • Yeah, there is an issue, or perhaps issues, when I try to access through cell data. I’m on AT&T and all I get is a blank screen. I’ve heard T-Mobile users get the same experience as me. I don’t have a Mac so I can’t access Web Inspector on Safari to see what HTTP status code I’m getting or if it is a syntax error in PHP. There was a domain server change a few months ago, around the time this started, but that should only take a day or two to propagate. This probably is an ISP issue since the site works perfectly fine on WiFi, but I don’t know what AT&T/T-Mobile/Verizon would do to help.

    • There’s a security issue that you can manually fix by adding an ‘s’ after the http in the URL on mobile, although I’m trying to get the hosting company to fix it permanently, since this is a change they made on their end in early November. The idea that I would block all mobile users deliberately is ridiculous, though.

    • Making the URL HTTPS didn’t fix the issue on AT&T for me. Making it the URL HTTPS encrypts the data packet between the browser and the server. I’ve done a HTTP to HTTPS conversion for my wife’s blog and it took a long time to complete. 750+ pages took about six weeks.

      It is rather ridiculous to suggest you would want to block cell phone as I’m guessing that more than half of your traffic is from mobile devices.

  7. Thanks as always for the links.

    Two things you might enjoy reading.

    This thread on money laundering, Trump, Erogdan and Putin was pretty fascinating: https://threadreaderapp.com/thread/1213597148274511872.html

    This is a critique of “Why we Sleep” and I am not qualified to evaluate the merits of either. https://guzey.com/books/why-we-sleep/

  8. Chris Jones

    Forcing SSL didn’t fix it for me either. I had tried that awhile back, and just did again today, without success.