From 49b4982af0e701965eff0f28eff7a746aa43c906 Mon Sep 17 00:00:00 2001 From: Johanna Stuber Date: Thu, 21 May 2026 12:27:30 +0200 Subject: [PATCH] add links from the Client-Server spec to the Olm message definitions --- content/client-server-api/modules/end_to_end_encryption.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/content/client-server-api/modules/end_to_end_encryption.md b/content/client-server-api/modules/end_to_end_encryption.md index 75acd93b..4d12310d 100644 --- a/content/client-server-api/modules/end_to_end_encryption.md +++ b/content/client-server-api/modules/end_to_end_encryption.md @@ -1623,9 +1623,9 @@ An event encrypted using Olm has the following format: ``` `ciphertext` is a mapping from device Curve25519 key to an encrypted -payload for that device. `body` is a Base64-encoded Olm message body. +payload for that device. `body` is a Base64-encoded [Olm message body](/olm-megolm/olm/#the-olm-message-format). `type` is an integer indicating the type of the message body: 0 for the -initial pre-key message, 1 for ordinary messages. +initial [pre-key message](/olm-megolm/olm/#pre-key-messages), 1 for [normal messages](/olm-megolm/olm/#normal-messages). Olm sessions will generate messages with a type of 0 until they receive a message. Once a session has decrypted a message it will produce