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
I think that all of these public histories/ledgers should actually display UTC, and not local time. They are for public communication so they should all display a common time.
The text was updated successfully, but these errors were encountered:
I looked at Wikipedia and it also seems to show local time without timezone. That makes more sense to me, otherwise users need to manually convert every time to figure out what the utc time means for them.
I looked at Wikipedia and it also seems to show local time without timezone. That makes more sense to me, otherwise users need to manually convert every time to figure out what the utc time means for them.
Fundamentally, all that matters for a edit history is the time of one edit relative to another. The rationale that I had behind using UTC only is for standardization. All editors would reference UTC instead of having to convert between each others times if editors were comparing. I don't really think the local time is all that important — why would one really even need to know what time someone else's edit happened locally? All that matters is that people have a common time to compare, necessitating the conversion between timezones only adds an obstacle in the middle of that process.
I have so far found that the diff viewer and edit history viewer both render the stored UTC time in local time, as shown in the following files:
ibis/src/frontend/pages/diff.rs
Line 33 in 8fa4fb1
ibis/src/frontend/pages/article/history.rs
Line 41 in 8fa4fb1
using the following function that converts to local time:
ibis/src/frontend/mod.rs
Lines 58 to 63 in 8fa4fb1
I think that all of these public histories/ledgers should actually display UTC, and not local time. They are for public communication so they should all display a common time.
The text was updated successfully, but these errors were encountered: