Localised timezone prefix

Gatorrex

• March 19, 2020 06:07

Different timezones are annoying and can cause confusion to international tournament organisers and players. There should be a prefix like typing <<0900>> for 9am at your local time and have it show to everyone else in their local times. For dates, it can be also adding extra parameters like <<DD/MM/YYYY 0000>> or <<DD/MM 0000>>.

15

• 

  Sylvenmyst

  • May 14, 2020 19:10

  I am totally onboard with a smart localized time feature like this one. It would be so helpful for coordination of events in my servers. There are several other requests/posts that mention something similar.

  My recommendation is to cross upvote on each of them if you see this as a good feature to have regardless of its implementation so that discord can get a better understanding of how many users actually want a smart local timezone embed feature.

  Here are the links:

  https://support.discord.com/hc/en-us/community/posts/360048439132-Mentioned-Timestamps

  https://support.discord.com/hc/en-us/community/posts/360047234111-Add-markup-for-automatic-locale-conversions

  https://support.discord.com/hc/en-us/community/posts/360045756912-Chatmessage-with-timestamp-in-users-local-time

  https://support.discord.com/hc/en-us/community/posts/360061983631--Feature-request-Time-date-stamp-link-that-changes-according-to-system-time-time-zone

  1
• 

  Kanef

  • May 18, 2020 23:22

  I too would love to have this feature!  However, I vote for the ISO-8601 version of this request.  I'm happy to type the international standard date format, 2020-04-29.  Even if it's unfamiliar to many of us Americans, it's not confusing.  But we have this weird medium/small/big format in our local, so even if we mean well we're likely to type June 1 as 06/01/2020, not 01/06/2020. 

  If you mean that it should parse whatever format the user's locale (set by the Language preference) specifies, I'm guessing that would be more work for the Discord developers, especially since there are many acceptable variants even in a single country, like two-digit years and leading zeros.  Whereas with output, they've apparently already written the code; it's used on the message-creation timestamp.  It may also be impossible to do localized parsing.  Am I right in guessing that what the user types is stored as is, with no record of what locale they had set, or what timezone they were in when they typed it?  That would rule out some of the other suggestions.  If the markup says "01/05/20", it would mean May 1 if typed in the U.K. and January 5 if typed in the U.S., so it would have no way to know whether to display `01.05.20` or `05.01.20` for a German user.  If so, ISO is the way to go.

  1

Please sign in to leave a comment.