The documentation specifies that the GET request to /users/{username}/activity/current always specifies that the started field is in UTC time (by including the Z at the end):
I believe the same problem exists for all other timestamps that are returned from any endpoint. We already have an issue in the frontend for this, but I think it would be best to fix in the backend.
Also, it seems that the duration field is a number instead of a string.
The easiest thing would be just to use DateTimes that include a timezone (most likely just UTC). This could be achieved with minor database refactoring.
The documentation specifies that the GET request to
/users/{username}/activity/current
always specifies that thestarted
field is in UTC time (by including theZ
at the end):However, in reality that "Z" is not included. Here is an example response that I got:
I believe the same problem exists for all other timestamps that are returned from any endpoint. We already have an issue in the frontend for this, but I think it would be best to fix in the backend.
Also, it seems that the
duration
field is a number instead of a string.