Changes
use more concise notation
== Definitions ==
A message m is '''fully-acked''' (from the POV of a given member ''u'') iff, for all recipients ''r'', ''u'' has accepted a message by ''r'' whose sender-where seqnum(parent is (r)) &gegt; m's seqnum(m).
* ''recipients'' possibly includes u, but certainly excludes m's sender
* ''accepted'' means delivered locally, i.e. received, then decrypted-verified including parent hash checks; all causally-previous messages must already be accepted** we assume a server-dictated ordering, so accepting a message at seqnum i means we have already accepted all messages j ≤ i.
== Consistency ==
Ensure that messages received out-of-order are highly visible to the user.
A message m is ''out-of-orderunsynced'' if its sender-parent's seqnum is < (parent(m's )) < seqnum (m) - MAX_UNSYNC_COUNT)
* MAX_UNSYNC_COUNT may either be constant, or a linear function of the number of members, TBD.
These messages should be highlighted in some way in the UI that is not too severe. They are still valid messages, ; the user should just be informed that they refer to older contextthat may be surprising.
This definition is globally consistent (or else transcript consistency breaks) so it's easier to reason about, and the warning is simpler to explain than MAX_RTD.
[[Category: mpOTR]]
