-
Notifications
You must be signed in to change notification settings - Fork 380
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Timestamp time zone? #1468
Comments
It is UTC, although yes: all mentions of it should say it's a unix epoch timestamp. |
unix timestamps don't have a timezone really - that's one of the nice things about them! |
@richvdh Well, according to https://en.wikipedia.org/wiki/Unix_time:
The fact that they are (supposed to be) in UTC is important, because otherwise the time zone would have to be carried separately. It also makes conversion to local time easier, because conforming implementations (e.g. Emacs's |
I think we're agreeing. The point is that the number of milliseconds since the epoch is independent of your timezone, because the epoch is at a defined point in time. |
I guess it depends on whether you consider UTC a "time zone." :) |
Signed-off-by: Stuart Mumford <stuart@cadair.com>
I looked at every mention of "timestamp" in https://matrix.org/docs/spec/client_server/r0.3.0.html, and searched for mentions of "time zone" or "timezone", but I found no explanation of what time zone timestamps are in--the spec only says that they are "Timestamp in milliseconds on originating homeserver." Some of the mentions of "timestamp" also say "Unix epoch," which may (or even should) imply UTC. However, I think that the time zone should be made explicit in the spec.
The text was updated successfully, but these errors were encountered: