Last night the whole family got into a multiplayer Minecraft game for the first time in a while. Weirdly enough, *one* system was showing way to many materials as copper. Even stuff like snow. WTF?

Well, we realized it was after 7 PM local time, which meant on UTC time it was already April 1, so it must be this year’s April Fool’s joke for Minecraft. (Or in this case, one of the mods.) But why only on one computer?

Then it hit me: The host was a Windows machine, which means the hardware clock is set to local time (instead of being set to UTC and just displaying local time). I was connecting from a Linux box that dual-boots, so I’d long since set the hardware clock to local time so Windows wouldn’t fight with it. The one showing all copper, all the time, was a Mac, which doesn’t dual boot, and uses Unix under the hood, so its hardware was set to UTC, and it was the only computer of the three that was already running in April 1.

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:

ยปAll pages site-wide with this tag