Mentioned Timestamps
Similar to how you can @ a username which is then encoded to <@user_id>, there should be a similar system for dates and times.
On the discord client you should be able to @ and select a date and time from the UI in your local time. It should then encode to a standardized format, such as ISO 8601 (https://en.wikipedia.org/wiki/ISO_8601). e.g. <@2019-08-07T21:10:32+00:00>
Each user should then see that timestamp in a readable format in their local time.
-
There was another similar feature request about a year ago (https://support.discord.com/hc/en-us/community/posts/360045756912-Chatmessage-with-timestamp-in-users-local-time) and a newer similar feature request (https://support.discord.com/hc/en-us/community/posts/360061983631--Feature-request-Time-date-stamp-link-that-changes-according-to-system-time-time-zone?page=1#community_comment_360010548051)
My recommendation is that everyone who is interested in some local timezone awareness feature cross upvote on all similar features to try to get this up the queue for discord.
0 -
Maybe ISO-8601 could be its own markup without need for the `<@` `>`, especially if it were a fixed subset, required to end with `Z` for UTC. After all, URLs are recognized that way, and converted to links.
Knowing nothing of the innards of Discord, I'm guessing it has no existing code for localized _parsing_ of times a user inputs, but does have code for localized _formatting_ of times, since it formats message-creation times based on the Language setting. So any of these feature requests would require their developers to write parsing code. I'll bet this one is the easiest for them. The others would require parsing based on locale. I'm in the U.S. where we use a weird ordering (medium, small, large) for dates, and we use slashes just like the U.S.Am I right in assuming that what the user types is stored as is, with no record of what locale ("Language" preference) 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 -
I like the idea of using a time-and-date picker, equivalent to the pop-up with a list of user names. Trying to get it functional on everything from the web to apps on mobile might be a chore, but most UIs (not all, maybe) have some form of built-in picker that could be called. Easier than parsing, and more certain since it doesn't require the poster to calculate UTC or be sure of standard vs daylight time for the chosen date.
2 -
What if the markup were
@2020-07-22T20:30:00Z
a subset of ISO-8601 that would be even easer to detect than URLs? (It might display in various locales in UTC+2 as)
@2020-07-22T20:30:00Z (7/22/2020 10:30 PM)
@2020-07-22T20:30:00Z (22/07/2020 22:30)
@2020-07-22T20:30:00Z (22.07.2020 22:30 Uhr)
For assisting the user in typing this subset-of-ISO8601 format, any chance of adding a calendar widget to help create the time string so the user doesn't need to do the time zone conversion in their head (or even worry about the format)?
Or, how about just recognizing that the user is typing a date and provide feedback? Typing `@` already brings up a widget with username suggestions, so that `@k` lists usernames containing "k". What if `@2`, instead of listing usernames containing `2`, switched to a prompt of
Type a date and time in this format: yyyy-mm-ddThh:mmZ to have it displayed in each user's time zone and format.
Hit Enter for today at 11:00 AM
and typing "@2020" prompted with something like, depending on Language and timezone
Hit Enter for 05/18/20 11:00 AM.
........ 18.05.20 11:00 Uhr.
and typing "@2020-07" prompted with something like
Hit Enter for 07/01/20 11:00 PM.
........ 01.07.20 5:00 Uhr.
and typing "@2020-07-22" prompted with something like
Type "T", or hit Enter for 07/22/20 5:00 PM.
........ for 22.07.20 5:00 Uhr.
and so on, finally inserting, say,
@2020-07-22T20:30:00Z
1 -
The giveawaybot uses this
0 -
This feature has been added https://discord.com/developers/docs/reference#message-formatting-timestamp-styles ... but of all the formatting options available the one they left out was the one that has a global standard (ISO-8601). (╯°□°）╯︵ ┻━┻
0
U moet u aanmelden om een opmerking te plaatsen.
Opmerkingen
7 opmerkingen