So I wake up this morning, stumble over to the laptop to see what I missed at SDMB. The timestamps are “Today” but after local time. No problem; that just means I’ve not refreshed that page for 22 hours or so. Click! No help.
Come to think of it, I think this happens every year. I am NOT concerned about it — I think this SDMB rendition of my clock will become correct again when Chicago springs forward a couple of hours from now.
This obviously is not an important problem compared with your 504’s, 505’s, 666’s and whatever these timeouts are. I’m presenting it as a puzzle. WHY does the SDMB clock appear an hour ahead?
We have no DST here, so I have DST corrections set to OFF. Setting it to AUTOMATIC gets the same result. If I set corrections to ON, your clock appears TWO hours ahead!
And I like your numbered timeouts, especially 666. Reminds me of the one time someone posted that to get through the telephone menu he had to enter all the digits of pi. 666 also happens to be the bus route that takes me to Wal-Mart here. Coincidence?
When I apply Beijing time to my options, it’s correct. I changed it to Central Time and it seems to be two hours off now. I’m going to change it back to Beijing time so it won’t bug me. (Sorry about the horrible pun.)
Feh. Yesterday I showed up to a location a hour early because of the time showing on my phone. Figuring I must have nudged the time zone setting or something I check. Nope, Automatic time and date - use network provided time. Okay. Lessee, Automatic time zone - Use network-provided time zone is set an-n-nd Verizon has the time zone as Denver - Mountain Daylight Time - UTC -6 hr. Apparently they figure the zone stops at the Rockies. If anything, the zone should be Phoenix - Mountain Standard Time - UTC-7 hrs. Phoenix, after all has a bigger population than Denver, Salt Lake City, Boise, and El Paso combined.
Nope that’s not how palindromes work. It reads the same backwards and forwards. You have to ignore punctuation in this one, which I think is pretty common. To get efilth you’d have to add an E.
Phoenix, being in Arizona, doesn’t observe Daylight Saving so technically just setting to “Mountain Daylight Time” isn’t necessarily going to give you the correct time.
You’re right, Arizona should be it’s own time zone and Verizon erred if it put you in the same time zone as Denver using location data.
That works, septimus, because the “r” is in both. The one I’m talking about doesn’t have the “e” (which in your examle has an “r” in the “pivot point”) in it.
