From ea0277649b90f0bc3d064f2a72c32956aa9fff60 Mon Sep 17 00:00:00 2001 From: Tom Foster Date: Thu, 31 Jul 2025 14:19:41 +0100 Subject: [PATCH] Update data/api/client-server/capabilities.yaml Co-authored-by: Johannes Marbach --- data/api/client-server/capabilities.yaml | 8 ++++---- 1 file changed, 4 insertions(+), 4 deletions(-) diff --git a/data/api/client-server/capabilities.yaml b/data/api/client-server/capabilities.yaml index 205ccfe7..71d8618c 100644 --- a/data/api/client-server/capabilities.yaml +++ b/data/api/client-server/capabilities.yaml @@ -101,10 +101,10 @@ paths: type: object title: ProfileFieldsCapability description: Capability to indicate if the user can set or modify extended profile fields via - [`PUT /_matrix/client/v3/profile/{userId}/{keyName}`](/client-server-api/#put_matrixclientv3profileuseridkeyname). - If absent, clients should assume custom profile fields are supported, provided the - response from [`/versions`](/client-server-api/#get_matrixclientversions) indicates - support for a sufficiently recent spec version. + [`PUT /_matrix/client/v3/profile/{userId}/{keyName}`](/client-server-api/#put_matrixclientv3profileuseridkeyname). + If absent, clients SHOULD assume custom profile fields are supported, provided the + homeserver advertises a specification version that includes `m.profile_fields` in the + [`/versions`](/client-server-api/#get_matrixclientversions) response. properties: allowed: type: array