The way the internet handles time it is actually quite easy to get some very strange things.I'm not well read in temporal mechanics. Even with a time machine, how can you get a message with a later date arrive before it was sent?
The device is virtual and (currently) remote. It takes its time from the host PC, and that is not wrong (nor is it ever).Maybe your device hadn't got round to changing its day/date
I'm sure I've received things sent at odd times - ie. the middle of the night. These have usually been automated lists or stuff from the Americas. Thinking about it, if you received something from Australia or New Zealand it could appear to have been sent before it arrived. I always thought the time on most things was recorded when it arrived - "our" time. Then you look at some things on Twitface and realise the times are quite often shot.The way the internet handles time it is actually quite easy to get some very strange things.
Epoch time has caused me some problems. Then there is taking account of daylight saving time. Should "just work", often doesn't.Time is a complete pain from a programmer's point of view.
Shirley they just imported an existing presentation function, and that function (being general purpose) already had "future tense" built in?What I find most strange is the developers considered the likelihood of future timestamps and built 'Later today' into the alert messages.
Yes. It probably uses the same set of time 'handling' functions as the calendar, for which that is a valid string.Shirley they just imported an existing presentation function, and that function (being general purpose) already had "future tense" built in?
I thought that was how it worked, but the implementation by some software is ... a bit lacking?None of this confusion should happen if all IT time was expressed in a single standard (eg UT) plus a separate local time offset parameter.
If you read the analysis of the hmt file you'll see a lineIs that what @EEPhil meant by "epoch time"?
0x0280 4 byte 0x11223344 Recording start time (Epoch format)
But I expect you knew that.epochconverter.com said:What is epoch time?
The Unix epoch (or Unix time or POSIX time or Unix timestamp) is the number of seconds that have elapsed since January 1, 1970 (midnight UTC/GMT), not counting leap seconds (in ISO 8601: 1970-01-01T00:00:00Z). Literally speaking the epoch is Unix time 0 (midnight 1/1/1970), but 'epoch' is often used as a synonym for 'Unix time'.