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
in the example above, my reply has a timestamp that appears to be one minute later than the original message, but it obviously happened after the user's question, even if by a short delay.
Probably the user's system clock is used to determine the time, and while small discrepancies are tolerated in order to keep a connection to the p2p network, it will lead to such events in edge cases.
Idea, compare the system clock with a set of external free atomic time services?
Edit: What's weirder, is that I just noticed the user's details popup reports that he was last active some 20 minutes before his message showed up.
This issue comes up with a non-trivial frequency.
The text was updated successfully, but these errors were encountered:
Can you post a screenshot with the date visible (mouse over)?
My side of the chat showed the time of my reply ending with ":50" and the user's question being posted at ":51".
A few minutes later I had gone to check again and noticed how the user's online status dot was orange even if I had just seen his question, so I checked in the popup, and I noticed "last online 23 minutes ago".
Since an image is worth a thousands words:
in the example above, my reply has a timestamp that appears to be one minute later than the original message, but it obviously happened after the user's question, even if by a short delay.
Probably the user's system clock is used to determine the time, and while small discrepancies are tolerated in order to keep a connection to the p2p network, it will lead to such events in edge cases.
Idea, compare the system clock with a set of external free atomic time services?
Edit: What's weirder, is that I just noticed the user's details popup reports that he was last active some 20 minutes before his message showed up.
This issue comes up with a non-trivial frequency.
The text was updated successfully, but these errors were encountered: