4 ms·

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

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.

INTPenis 2y ago
That seems confusing to me. It would be better if Zulip just added the local timezone to the time instead of modifying what you send to people. Do you mean it shows it in a hover or tooltip? 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.
- infogulch 2y ago
  It appears that you have to type it in a specific format, and the localized time is displayed with different formatting than the rest of the message. See: https://zulip.com/help/global-times https://zulip.com/help/global-times > 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.
  - tyzoid 2y ago
    Discord recognizes <t:{{unix_time}}:format> https://discordtimestamp.com/ https://discordtimestamp.com/
    - tabbott 2y ago
      That's effectively an API feature only: There's no button or typeahead for entering it. Zulip's version is a first-class feature with a compose box button and typeahead, designed to be convenient enough that humans routinely use it rather than typing "10 Pacific time".
- anderskaseorg 2y ago
  Here’s a message where you can see what this feature looks like (no login required): https://chat.zulip.org/#narrow/stream/101-design/topic/clock.20icons/near/1728695 https://chat.zulip.org/#narrow/stream/101-design/topic/clock... (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.)
  - INTPenis 2y ago
    Yup that was how I imagined it, makes a lot of sense. Thanks for clarifying.
pushcx 2y ago
Unfortunately it's bugged and doesn't use the timezone setting. I just ran into this recently. https://github.com/zulip/zulip/issues/30856 https://github.com/zulip/zulip/issues/30856
- tabbott 2y ago
  Zulip is designed to use your OS/browser's timezone for this and all other displays of times (say, when messages were sent). This is usually what you want, since it means you just need to make sure your computer's clock is correct and not manually update every app you're using. 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.

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.

INTPenis 2y ago

That seems confusing to me. It would be better if Zulip just added the local timezone to the time instead of modifying what you send to people. Do you mean it shows it in a hover or tooltip? 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.

infogulch 2y ago
It appears that you have to type it in a specific format, and the localized time is displayed with different formatting than the rest of the message. See: https://zulip.com/help/global-times https://zulip.com/help/global-times > 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.
- tyzoid 2y ago
  Discord recognizes <t:{{unix_time}}:format> https://discordtimestamp.com/ https://discordtimestamp.com/
  - tabbott 2y ago
    That's effectively an API feature only: There's no button or typeahead for entering it. Zulip's version is a first-class feature with a compose box button and typeahead, designed to be convenient enough that humans routinely use it rather than typing "10 Pacific time".
anderskaseorg 2y ago
Here’s a message where you can see what this feature looks like (no login required): https://chat.zulip.org/#narrow/stream/101-design/topic/clock.20icons/near/1728695 https://chat.zulip.org/#narrow/stream/101-design/topic/clock... (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.)
- INTPenis 2y ago
  Yup that was how I imagined it, makes a lot of sense. Thanks for clarifying.

pushcx 2y ago

Unfortunately it's bugged and doesn't use the timezone setting. I just ran into this recently. https://github.com/zulip/zulip/issues/30856 https://github.com/zulip/zulip/issues/30856

tabbott 2y ago
Zulip is designed to use your OS/browser's timezone for this and all other displays of times (say, when messages were sent). This is usually what you want, since it means you just need to make sure your computer's clock is correct and not manually update every app you're using. 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.