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
Most/all datetime are built around the idea very specific timestamps, often with minute or second precision. In some cases we're getting data like "on 2019-07-28" or "1 day ago" which is rather inaccurate. We could try to translate "2019-07-28" into "2019-07-28 00:00:00" but it would be hard to tell if we mean "at some point at that day" or "exactly at this time". "1 day ago" is even worse because this is usually range of "24h-48h59m".
The text was updated successfully, but these errors were encountered:
This is a bit of a larger problem/thought.
Most/all datetime are built around the idea very specific timestamps, often with minute or second precision. In some cases we're getting data like "on 2019-07-28" or "1 day ago" which is rather inaccurate. We could try to translate "2019-07-28" into "2019-07-28 00:00:00" but it would be hard to tell if we mean "at some point at that day" or "exactly at this time". "1 day ago" is even worse because this is usually range of "24h-48h59m".
The text was updated successfully, but these errors were encountered: