This is confusing as not all clients are always on and always receiving drop messages.
E.g. the time when the server received the message is preferable.
A workaround would be to let the clients state "received a moment ago" instead of "a moment ago" to clarify the confusion but it would be better to have more meaningful timestamps.
@thechauffeur commented on Tue Oct 04 2016
This is confusing as not all clients are always on and always receiving drop messages.
E.g. the time when the server received the message is preferable.
A workaround would be to let the clients state "received a moment ago" instead of "a moment ago" to clarify the confusion but it would be better to have more meaningful timestamps.
@audax commented on Thu Oct 13 2016
I don't think it works this way: https://github.com/Qabel/qabel-core/blob/master/chat/src/main/java/de/qabel/chat/service/MainChatService.kt#L161
The time shown is the creation date of the drop message, thus it depends on the correctness of the senders clock.
@julianseeger commented on Thu Oct 13 2016
It's a bug in the desktop. The code bridge in the DropDaemon doesn't keep the creationDate. Thus, the default
new Date()
is used here