dandri/simplex-chat
1
0
Fork 0
mirror of https://github.com/simplex-chat/simplex-chat.git synced 2026-07-18 22:36:41 +00:00
Code Issues Packages Projects Releases Wiki Activity

deploy: 937c79bc3c

Browse Source
This commit is contained in:
epoberezkin
2026-07-14 14:20:03 +00:00
parent 85890f8f2b
commit 033eed8a92
184 changed files with 228 additions and 197 deletions
Download Patch File Download Diff File Expand all files Collapse all files
docs/protocol/channels-protocol.html
+1 -1
View File
@@ -1092,7 +1092,7 @@ brokerTs = 8*8 OCTET ; UTC system time
<li>If a duplicate is found, the message is silently dropped (in channels with relays).</li>
<li>In non-relay groups, duplicate detection triggers a <code>x.grp.mem.con</code> notification to the forwarding member.</li>
</ul>
<p>This is essentially cache coherence verification - comparing what was received from one cache node against another. TODO: Currently, deduplication only detects the presence of duplicates. The protocol design includes provisions for detecting differences between relay-delivered copies of the same message (hash comparison, UI indicators for discrepancies). This is described in the <a href="https%3A//github.com/simplex-chat/simplex-chat/blob/stable/simplex-chat/docs/rfcs/2025-08-11-channels-forwarding.md">channels forwarding RFC</a> and is not yet implemented.</p>
<p>This is essentially cache coherence verification - comparing what was received from one cache node against another. TODO: Currently, deduplication only detects the presence of duplicates. The protocol design includes provisions for detecting differences between relay-delivered copies of the same message (hash comparison, UI indicators for discrepancies). This is described in the <a href="https://github.com/simplex-chat/simplex-chat/blob/stable/docs/rfcs/2025-08-11-channels-forwarding.md">channels forwarding RFC</a> and is not yet implemented.</p>
<h3 id="channel-as-sender-messages" tabindex="-1">Channel-as-sender messages</h3>
<p>Owners can send messages attributed to the channel rather than to themselves. When <code>asGroup = True</code> is set in the message container, the relay forwards the message with a channel-as-sender tag instead of attributing it to a specific member. On the subscriber side, such messages are displayed as coming from the channel (using the channel's profile image and name) rather than from a specific owner.</p>
<p>This will be useful for channels with multiple owners (not yet implemented at application level) where the identity of the specific sender should not be visible to subscribers. The relay must respect this directive; ignoring it and revealing the sending owner's identity is a threat vector (detectable out-of-band by members communicating with the owner).</p>