You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Jun 13, 2022. It is now read-only.
Our international and local customers are sometimes bugged by having a UTC time on incidents and other messages. which shouldn't be a problem
In order to make it clear for everyone an (optional) display of a JS powered UTC and local-clock would solve close to weekly discussions about "wrong time on statuspage", "why're you reporting earlier / later ..." and the like.
What does the proposed API look like?
How should this be implemented in your opinion?
new Date().toUTCString() and new Date() formatted to the default of statusfy.
Are you willing to work on this yourself?**
We'll add it to our Backlog.
If anyone wants to tackle this one before we do - please go ahed.
The text was updated successfully, but these errors were encountered:
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Feature request
What problem does this feature solve?
Our international and local customers are sometimes bugged by having a UTC time on incidents and other messages. which shouldn't be a problem
In order to make it clear for everyone an (optional) display of a JS powered UTC and local-clock would solve close to weekly discussions about "wrong time on statuspage", "why're you reporting earlier / later ..." and the like.
What does the proposed API look like?
How should this be implemented in your opinion?
new Date().toUTCString()
andnew Date()
formatted to the default of statusfy.Are you willing to work on this yourself?**
We'll add it to our Backlog.
If anyone wants to tackle this one before we do - please go ahed.
The text was updated successfully, but these errors were encountered: