From b7912eba0575150ea6b730e65bbf12289c4f6285 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?K=C3=A9vin=20Commaille?= Date: Wed, 22 Apr 2026 12:21:15 +0200 Subject: [PATCH] Add links to event definitions MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit Signed-off-by: Kévin Commaille --- content/client-server-api/_index.md | 12 ++++++------ 1 file changed, 6 insertions(+), 6 deletions(-) diff --git a/content/client-server-api/_index.md b/content/client-server-api/_index.md index b74a0ee2..6f43061c 100644 --- a/content/client-server-api/_index.md +++ b/content/client-server-api/_index.md @@ -4214,13 +4214,13 @@ an automatic propagation event to occur, informing likely-interested parties of the new values. This change is conveyed using two separate mechanisms: -- an `m.room.member` event (with a `join` membership) is sent to every - room the user is a member of, to update the `displayname` and +- an [`m.room.member`](#mroommember) event (with a `join` membership) is sent + to every room the user is a member of, to update the `displayname` and `avatar_url`. -- an `m.presence` presence status update is sent, again containing the - new values of the `displayname` and `avatar_url` keys, in addition - to the required `presence` key containing the current presence state - of the user. +- an [`m.presence`](#mpresence) presence status update is sent, again + containing the new values of the `displayname` and `avatar_url` keys, in + addition to the required `presence` key containing the current presence + state of the user. Both of these should be done automatically by the homeserver when a user successfully changes their display name or avatar URL fields.