From ccbc88ee5d9dc794dcdf47fdba18a322acf24e26 Mon Sep 17 00:00:00 2001 From: Matthew Hodgson Date: Mon, 3 Sep 2018 16:49:36 +0100 Subject: [PATCH] reword to spell out to when device list updates should be sent --- specification/server_server_api.rst | 7 ++++--- 1 file changed, 4 insertions(+), 3 deletions(-) diff --git a/specification/server_server_api.rst b/specification/server_server_api.rst index 4f8e2e3b..e3427b69 100644 --- a/specification/server_server_api.rst +++ b/specification/server_server_api.rst @@ -1013,9 +1013,10 @@ on the remote server. However, subsequent updates to the cache should be applie by consuming ``m.device_list_update`` EDUs. Each new ``m.device_list_update`` EDU describes an incremental change to one device for a given user which should replace any existing entry in the local server's cache of that device list. Servers must send -``m.device_list_update`` EDUs to all the servers whose users participate in their rooms, -and must be sent whenever a local user's device list changes (i.e. new or deleted devices, -or changes of identity keys). +``m.device_list_update`` EDUs to all the servers who share a room with a given +local user, and must be sent whenever that user's device list changes (i.e. for new or +deleted devices, when that user joins a new room, or changes of device information such as +human-readable name). Servers send ``m.device_list_update`` EDUs in a sequence per origin user, each with a unique ``stream_id``. They also include a pointer to the most recent previous EDU(s)