Google Photos is overcompensating for the Daylight Saving Time switch on yesterday’s pictures. Photos taken at 6:00pm are labeled as 7:00pm. Everything from this summer/early fall (which might as well have been summer) is off, in the app anyway (the website shows the right time in PDT), which at least makes more sense than if it had only been one day. The weird thing: it’s not even showing the time in today’s timezone by mistake. It’s adjusting it the other way.

My best guess: There used to be a DST bug in Google Photos, but they adjusted for it. Now the bug’s been fixed, but the adjustment is still there.

Obligatory XKCD link:

The Verge ponders: Has the internet been overtaken by the eldritch horror of Yog-Sothoth?

We’ve got this dimension right next to ours, that extends across the entire planet, and it is just brimming with nightmares. We have spambots, viruses, ransomware, this endless legion of malevolent entities that are blindly probing us for weaknesses, seeking only to corrupt, to thieve, to destroy.
Astercrash

It’s a joke, of course. And it would make for an interesting story. But it’s scarier that we’ve created the awfulness ourselves.

Update Feb 2023: With some of the AI-generated art and writing going around these days, the cosmic horror comparison seems even more apt.

Homemade spider jockey costume (a composite Minecraft monster consisting of a skeleton archer riding a giant spider). Kid-sized, built by Katie (I assisted, mainly with painting, but the design, planning, and most of the construction was her).

Mostly cardboard, covered with paper to smooth it out and provide a painting surface. Heavy fabric and dowels to form the frame for the center of the spider body, with paracord to hold the legs on. For the skeleton: felt panels, some pinned to a black shirt, some to the suspenders. Which, incidentally, were made from old Comic-Con lanyards.

I didn’t even see a Halloween aisle this time, but Christmas was on full display.

You know, I’ve been posting examples of holiday creep for over a decade now, and what’s changed the most is the quality of the camera I have with me when shopping. I mean, what the heck was I even carrying in 2005:

Christmas aisle

It was probably my first cameraphone (back when we actually called them that). I know I had a better digital camera at the time, but this definitely wasn’t it!

Is that help with flashing? Help responding to flashing? Help that flashes.

Maybe I don’t want “flashing help.”

And what am I supposed to know about what happens when it’s on its way? There’s a missing half sentence here!

(Or maybe they just need to pick their line breaks better!)

I figured out exactly what bugs me about Twitter and Facebook showing your friends’ “likes” in the timeline. It’s not just that they’re public — that’s true on Tumblr or Flickr or Instagram too, but you only see them when you choose to look for them.

It’s that broadcasting likes in the newsfeed blurs your intent.

  • A “like” is a message to the original post’s author (and a bookmark for yourself).
  • A retweet or share is a message to your friends or followers.

Putting them in your followers’ feeds turns a “like” into a message to them as well, even though it’s not what you intended. (If you wanted to share it, you would have shared it, right?) It’s a step above completely frictionless sharing, but it still messes with the signal/noise ratio of the timeline.

Smoke rises from Mt. Wilson above Los Angeles on Tuesday around noon. The wildfire has threatened the observatory and critical communications towers. Today it’s too hazy to see anything but the barest suggestion of the downtown skyline, much less the mountains behind it. Not that it looked quite this clear even on Tuesday – I ran the photo through auto white balance to make everything easier to see.

I’m reminded of the last time the mountaintop complex was threatened by fire, during the 2009 Station Fire… and the photos I scanned from a 1992 tour of the observatory, wondering if that had been my only chance to see it.