From eebb9cabff00a568e85174d9d750c4c14bb30a52 Mon Sep 17 00:00:00 2001 From: Patrick Cloke Date: Thu, 21 Mar 2024 16:07:01 -0400 Subject: [PATCH] Do not allow setting m.push_rules account data directly. --- content/client-server-api/modules/account_data.md | 7 ++++++- 1 file changed, 6 insertions(+), 1 deletion(-) diff --git a/content/client-server-api/modules/account_data.md b/content/client-server-api/modules/account_data.md index 12233bcd..0d81cca3 100644 --- a/content/client-server-api/modules/account_data.md +++ b/content/client-server-api/modules/account_data.md @@ -28,4 +28,9 @@ These events can also be received in a `/events` response or in the Servers MUST reject clients from setting account data for event types that the server manages. Currently, this only includes -[m.fully\_read](#mfully_read). +[`m.fully_read`](#mfully_read) and [`m.push_rules`](#mfully_read). +This applies to both global and room-specific account data. + +Servers must allow clients to read the above event types as normal. Note that +`m.fully_read` only exists for room-specific account data and `m.push_rules` +only exists for global account data.