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

Commit b0d209a

Browse files
committed
mark outdated section
1 parent 0b85372 commit b0d209a

File tree

1 file changed

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

1 file changed

+10
-9
lines changed

docs/Protocol Specifications/P2 Extensions/chat.md

Lines changed: 10 additions & 9 deletions
Original file line numberDiff line numberDiff line change
@@ -26,12 +26,6 @@ title: polyproto-chat
2626
- [2.1.1 Private messages](#211-private-messages)
2727
- [2.1.2 Group messages](#212-group-messages)
2828
- [2.2 Guilds and Guild channels](#22-guilds-and-guild-channels)
29-
- [3. Encrypted channels and groups](#3-encrypted-channels-and-groups)
30-
- [3.1 Encrypted guild channels](#31-encrypted-guild-channels)
31-
- [3.2 Encrypted direct messages](#32-encrypted-direct-messages)
32-
- [3.3 Encrypted group messages](#33-encrypted-group-messages)
33-
- [3.4 Joining new devices from existing users](#34-joining-new-devices-from-existing-users)
34-
- [3.5 Best practices](#35-best-practices)
3529
- [polyproto-chat specific glossary](#polyproto-chat-specific-glossary)
3630
- [General glossary](#general-glossary)
3731

@@ -209,6 +203,12 @@ end
209203
*Fig. 3: Sequence diagram, showing Alice sending a message to a guild channel accessible to both
210204
Alice and Bob.*
211205

206+
!!! bug "Legacy"
207+
208+
The below "fenced" text is considered out-of-date. Useful information will be migrated soon, though
209+
most of the information is deprecated.
210+
211+
```txt
212212
## 3. Encrypted channels and groups
213213
214214
Note, that in the below sequence diagrams, the MLS Welcome message and the MLS Group notify
@@ -245,7 +245,7 @@ a->>s: Encrypted MLS Welcome
245245
s->>b: Forward: Notify group of new member: c
246246
s->>c: Forward: Notify group of new member: c
247247
s->>c: Forward: encrypted MLS Welcome
248-
```
248+
\```
249249
250250
Fig. 3: Sequence diagram of a successful encrypted channel join in which Alice acts as a gatekeeper.
251251
The sequence diagram assumes that Alice can verify Charlies' public key to indeed belong to
@@ -273,7 +273,7 @@ Alice->>Server: Notify group of new member: Bob
273273
Server->>Alice: Encrypted MLS Welcome
274274
Server->>Bob: Forward: New group member: Bob
275275
Server->>Bob: Forward encrypted MLS Welcome
276-
```
276+
\```
277277
278278
Fig. 4: Sequence diagram of a successful encrypted direct message creation.
279279
@@ -308,7 +308,7 @@ Server->>Alice: Encrypted MLS Welcome
308308
Server->>Bob: Forward: New group member: Charlie
309309
Server->>Charlie: Forward: New group member: Charlie
310310
Server->>Charlie: Forward encrypted MLS Welcome
311-
```
311+
\```
312312
313313
Fig. 5: Sequence diagram of a successful encrypted group creation with 3 members.
314314
@@ -324,6 +324,7 @@ accepted by default.
324324
- Joining an encrypted channel, even from an already established member with a new device,
325325
should be an event distinctly visible to all members of the channel. This is to prevent a
326326
malicious user from joining a channel without the other members noticing.
327+
```
327328

328329
---
329330

0 commit comments

Comments
 (0)