Timestamps are client-assigned, so if we're chatting, and my device and your device disagree on what time it is by more than a few seconds, than we could have messages showing up in an undesirable order -- usually all mine showing up after yours (when my clock is faster), or yours showing up after mine (when your clock is faster/ahead).
Or if someone's timezone is wrong.
One possible solution: Backchannel (and perhaps other CrypTag apps) could have 2 different views on data (messages) -- the chronological view that we are using right now, as well as a sort of linked-list view, where every messages says what it believes the previous message to be (e.g., each message could be tagged with parentrow:${id_tag_of_last_message_seen_in_chat}).
Timestamps are client-assigned, so if we're chatting, and my device and your device disagree on what time it is by more than a few seconds, than we could have messages showing up in an undesirable order -- usually all mine showing up after yours (when my clock is faster), or yours showing up after mine (when your clock is faster/ahead).
Or if someone's timezone is wrong.
One possible solution: Backchannel (and perhaps other CrypTag apps) could have 2 different views on data (messages) -- the chronological view that we are using right now, as well as a sort of linked-list view, where every messages says what it believes the previous message to be (e.g., each message could be tagged with
parentrow:${id_tag_of_last_message_seen_in_chat}).