one of the killer features of Zulip is that when you mention your local datetime in a message the receiver sees that in their own timezone. So useful when teams are distributed.
Seems like there should be deadly sins for certain fields, and one such deadly sin is for an instant messenger to change what you send to people.
> A date picker will appear once you type `<time`.
> Our next meeting is scheduled for <time:2020-05-28T13:30:00+05:30>
> A person in San Francisco will see:
> Our next meeting is scheduled for Thu, May 28 2020, 1:00 AM.
> While someone in India will see:
> Our next meeting is scheduled for Thu, May 28 2020, 1:30 PM.
(Note that the sender opts in to this with a specific syntax; we don’t try to heuristically match anything that looks like a time.)
In the issue you linked, the root problem is that the anti-fingerprinting browser feature has the browser pretending that its preferred timezone is UTC, resulting in the user seeing all times displayed to them in UTC.
It has nothing to do with the "global times" feature -- that feature just renders an element in your message in the same timezone that it renders the timestamps.