The discussion revolves around improving how Discourse displays local dates in emails, which currently causes confusion due to ambiguous time zone presentation. sam highlights that emails show dates like May 19, 2018 9:03 AM without clear time zone context, proposing a three-phase fix: (1) immediately append time zone (e.g., Australia/Sydney), (2) store user’s detected time zone via JS for personalized email times, and (3) let users manually set preferred time zones. codinghorror urges prioritizing the immediate fix for the 2.0 release. j.jaffeux clarifies that emails currently show multiple time zones (e.g., (Australia: Sidney)), which can be verbose, and confirms a fix is underway to show only one time zone — or UTC if preferred. codinghorror questions why all time zones are shown, suggesting UTC as a short-term fallback; j.jaffeux agrees one time zone is sufficient and submits a PR to implement this fix. Later, loginerror suggests additional enhancements: (1) emails should respect the original post’s specified time zone (e.g., EST), (2) improve time zone formatting options in settings (e.g., full names or custom display), and (3) allow admins to choose a default email time zone via a toggle setting. The consensus leans toward simplifying time zone display in emails while laying groundwork for future personalization.
The Discourse local time displays wonderful dates in the web UI. However in emails it can be very very confusing.
For example: May 18, 2018 11:03 PM will display as May 19, 2018 9:03 AM in an emails which leaves recipients very confused.
I propose a multi step approach to improving this.
Immediate change… just display time zone with the time in emails so we would have May 19, 2018 9:03 AM Australia/Sydney
Longer term change, start storing local time zone in the user profile table (detect via JS and hand to server with a header). Then in emails we can send the times in the “last know local timezone”
Longer Longer term, allow users to control preferred timezone in user profile (automatic vs manually set to something)
Working on it, but I still don’t understand why you say that it will display as May 19, 2018 9:03 AM in an email. This is not what will happen, it will display:
May 19, 2018 09:03 AM (Australia: Sidney)
The issue is that it will display all timezones set when configuring the date, and you might end up with something very verbose. So yes we will need step2, to have something cool here, so you say send this email to this user living in Australia/Sidney timezone
Email timezone to be based on the original timezone set in the post
If I set my timezone value as [date=2019-12-15 time=23:59:00 timezone="EST"]
It should be sent out via email as such.
Allow better formatting of the timezone within this forum setting:
Currently it is a bit limited:
(just in case we would like to display the full name of the timezone or some other fancy formatting)
Currently it is a bit limited:
Alternatively, allow the admin to choose the timezone they want to send the emails with in the setting, maybe a toggle such as:
discourse local dates email format timezone