You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Toots are displayed in (someone's) local time, but the machine readable date is always rendered in UTC.
The machine readable date should be rendered as an ISO8601 timestamp with the same timezone offset that the human readable date is rendered as. That applies both here and here.
The text was updated successfully, but these errors were encountered:
toots are displayed in client-side local time though? it would be
impossible to render them with a timezone offset.
what would be the point of this anyway? the machine readable date should
always be utc for consistency
I didn't realize that was changing the displayed time client-side.
Using Z for the offset is the lazy way to avoid the problem. As long as the timezone offset is included in the timestamp, it still refers to an absolute point in time and can be easily converted to other timezones. (e.g. 2018-07-08T06:57:00-0700)
Ideally the timestamps should be rendered in the timezone the post was authored in, as that can provide additional context for a post (did they post this in their morning or late at night?) But, if you don't have that information available then there isn't much you can do.
Toots are displayed in (someone's) local time, but the machine readable date is always rendered in UTC.
The machine readable date should be rendered as an ISO8601 timestamp with the same timezone offset that the human readable date is rendered as. That applies both here and here.
The text was updated successfully, but these errors were encountered: