New simplified timestamp in message application is lacking/has rounding issue

asked 2019-08-01 16:59:26 +0300

Mohjive gravatar image

updated 2019-08-02 11:22:02 +0300

I know that you can tap a message and get the exact timestamp. This is about the default behaviour, and not having to tap a message to get valid information.

For each message in the new message applicaiton there are simplified timestamps, e.g. "1 hour ago", "3 hours ago" etc. However the resolution is lacking/has rounding error when the conversation is within the "hour" interval.

Now, at 15:50, I have two messages showing "1 hour ago", but one has timestamp at 13:58 and the other at 14:22. They are different conversations and I want to know how far apart they were (one is actually very close to 2 hours).

Another example, one message could have "59 minutes ago" and another "1 hour ago", hinting that they are close in time but actually be 1 hour apart (the latter being sent/received 1 hour 59 minutes ago).

I think that this coarse distribution is OK once you are beyond a certain timespan, say 3-4 hours. Last hour is too close in time to get rid of this resolution.

edit retag flag offensive close delete

Comments

1

If you remove the last paragraph which makes no sense without a definition of conversation I could probably agree with you.

ljo ( 2019-08-01 18:42:14 +0300 )edit

@ljo: imo conversation: frequent, continuous exchange of messages.

I was thinking that if we have a conversation and send messages between each other every few minutes only timestamp for start of that conversation is necessary imo. If enough time passes between messages, what is a good threshold I don't know, but in the vicinity of 15-20 minutes, a new timestamp is inserted, for the new message, which indicates start of a "new" conversation.

Mohjive ( 2019-08-01 19:05:33 +0300 )edit
1

I hate the simplified timestamp! I'd like to switch it off, ideally systemwide.

Pohli ( 2019-08-01 22:42:07 +0300 )edit