Desktop clients are the most likely source of clock skew issues that may cause the timestamp of a message to be off far enough that it affects the order of messages as they are sorted on the client trusting the message's timestamp.
We have the opportunity to use the GETMETADATA response for /shared/vendor/deltachat/turn to check how far off the clock is and issue a Device Message to the client to let them know there's a potential issue worth investigating.
GETMETADATA "" /shared/vendor/deltachat/turn
chat.feld.me:3478:1781029481:cShWiPn89yo0qzQP8Lrcw4IuiOM=
If the profile has multiple relays we can even use voting logic to figure out if it's really a client or server problem.
Desktop clients are the most likely source of clock skew issues that may cause the timestamp of a message to be off far enough that it affects the order of messages as they are sorted on the client trusting the message's timestamp.
We have the opportunity to use the GETMETADATA response for /shared/vendor/deltachat/turn to check how far off the clock is and issue a Device Message to the client to let them know there's a potential issue worth investigating.
If the profile has multiple relays we can even use voting logic to figure out if it's really a client or server problem.