Skip to content
This repository was archived by the owner on Aug 15, 2025. It is now read-only.

Commit 3995fb0

Browse files
committed
Clarify guild channel encryption rationale
1 parent c524c85 commit 3995fb0

File tree

1 file changed

+10
-1
lines changed
  • docs/Protocol Specifications/P2 Extensions

1 file changed

+10
-1
lines changed

docs/Protocol Specifications/P2 Extensions/chat.md

Lines changed: 10 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -176,7 +176,16 @@ Unlike messaging groups, guild channels are not encrypted by default.
176176
!!! question "Why are guild channels not encrypted by default?"
177177

178178
In the real world, most guilds are used as spaces for open communities where people join and leave
179-
freely.
179+
freely. Encrypted communications channels are useful when the communication between actors is potentially
180+
sensitive. Additionally, for encryption to be effective, you must at least somewhat trust the
181+
parties able to decrypt your messages.
182+
183+
The potential for anyone to join a chat and receive the entire encrypted history undermines the
184+
purpose of encryption. Therefore, we don't offer cross-actor encrypted chat history distribution,
185+
even for guild channels.
186+
187+
Encrypted guild channels are available, but without cross-actor encrypted chat history
188+
distribution, their user experience is not fit for a "default" status.
180189

181190
## 3. Encrypted channels and groups
182191

0 commit comments

Comments
 (0)