I am in the UK. During winter we use the GMT time zone which is the same as UTC, and during summer we go one hour forwards into British Summer Time (BST) which is what is known as Daylight Savings Time (DST).
I recently created an event for 1600 the next day, while we were in GMT. However, overnight we changed to BST at 1AM, making our UTC offset +1. The event kept its time of 1600 for me but moved it one hour earlier for everyone else who was not in the UK.
This is convenient for me as the time has been updated in line with my time zone, but my server is global and has people from all over the world in it. Ideally, the time should be fixed and not dependent on my time zone. People who sign up to the event should not be surprised later on when they find that Discord is notifying them about it at a different time to the one they originally read.
- Discord events should have a static start time that is global (follows UTC internally).
- When creating an event, a time zone could be supplied by the creator (e.g. UTC).
Whatever solution gets implemented, I think it's important to preserve the functionality where the event's start time is converted into a client's own time when they view the event.
Please sign in to leave a comment.