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
They refer to "3pm pst" when DST is in effect. The bot takes this literally and conversion is then an hour out, because they really meant "3pm pdt".
The bot needs to assume people are wrong when they use time zones in a time period where they are not in effect. For example, if they specify "3pm pst", assume they meant "3pm pt" ("3pm pdt") if the Pacific time zone on that date (and time) is PDT.
No amount of telling people that they're using the wrong time zone will get them to specify time correctly.
The text was updated successfully, but these errors were encountered:
You state in that issue that it only determines DST if not explicitly specified. This issue concerns people explicitly specifying the wrong DST status.
People frequently can't use timezones correctly.
They refer to "3pm pst" when DST is in effect. The bot takes this literally and conversion is then an hour out, because they really meant "3pm pdt".
The bot needs to assume people are wrong when they use time zones in a time period where they are not in effect. For example, if they specify "3pm pst", assume they meant "3pm pt" ("3pm pdt") if the Pacific time zone on that date (and time) is PDT.
No amount of telling people that they're using the wrong time zone will get them to specify time correctly.
The text was updated successfully, but these errors were encountered: