Mirrors/chatmail-core
1
0
Fork 0
mirror of https://github.com/chatmail/core.git synced 2026-05-09 01:46:30 +03:00
Code Issues Packages Projects Releases Wiki Activity

small refinements

Browse Source
This commit is contained in:
holger krekel
2020-02-19 13:39:33 +01:00
parent 702c7382a7
commit ffe3c84e7c
1 changed files with 5 additions and 3 deletions
Download Patch File Download Diff File Expand all files Collapse all files

8
draft/group-sync.rst
View File

@@ -26,8 +26,9 @@ solution: memorize+attach (possible encrypted) chat-meta mime messages
which is, apart from the added/removed member, not consistent which is, apart from the added/removed member, not consistent
with our own view, send a "Chat-Group-Member-Correction" message out, with our own view, send a "Chat-Group-Member-Correction" message out,
attaching the original added/removed mime-message for all mismatching contacts. attaching the original added/removed mime-message for all mismatching contacts.
If we have no relevant add/del information, don't send a correction message out.
- When receiving added/removed attachments don't do the - Upong receiving added/removed attachments we don't do the
check_consistency+correction message dance. This avoids recursion problems check_consistency+correction message dance. This avoids recursion problems
and hard-to-reason-about chatter. and hard-to-reason-about chatter.
@@ -39,9 +40,10 @@ Notes:
We could extend it to also include the payload and store mime unconditionally We could extend it to also include the payload and store mime unconditionally
for member-added/removed messages. for member-added/removed messages.
- multiple member-added/removed messages can be attached in a single message - multiple member-added/removed messages can be attached in a single
correction message
- is minimal on the number of overall messages to reach group consistency - it is minimal on the number of overall messages to reach group consistency
(best-case: no extra messages, the ABCD case above: max two extra messages) (best-case: no extra messages, the ABCD case above: max two extra messages)
- somewhat backward compatible: older clients will probably ignore - somewhat backward compatible: older clients will probably ignore