From 2bb34224dd1610adc43200e1bb538ffd4f517540 Mon Sep 17 00:00:00 2001 From: Johannes Marbach Date: Wed, 13 Aug 2025 13:01:59 +0200 Subject: [PATCH] Clarify capability behaviour with respect to avatar_url and displayname in MSC4133 (#4327) --- proposals/4133-extended-profiles.md | 3 +-- 1 file changed, 1 insertion(+), 2 deletions(-) diff --git a/proposals/4133-extended-profiles.md b/proposals/4133-extended-profiles.md index cd6e818c3..b78183873 100644 --- a/proposals/4133-extended-profiles.md +++ b/proposals/4133-extended-profiles.md @@ -148,8 +148,7 @@ Clients MAY check for this capability before attempting to create or modify a pr (or all) changes, it SHOULD use the capability to advertise this, improving the client experience. - **When `enabled` is `false`**: Clients SHOULD expect to display profiles but NOT create or update - fields. Any attempt to do so SHOULD result in a `403 Forbidden` error. This does not affect - `avatar_url` and `displayname` fields, which are allowed for compatibility purposes. + fields. Any attempt to do so SHOULD result in a `403 Forbidden` error. - **When `enabled` is `true`**: Clients SHOULD allow users to create or update fields, except those keys listed in the `disallowed` array. Servers MAY specify an `allowed` array to allowlist fields