Skip to content

Clarify capability behaviour with respect to avatar_url and displayname in MSC4133 #4327

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 1 commit into from
Aug 13, 2025
Merged

Clarify capability behaviour with respect to avatar_url and displayname in MSC4133 #4327

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
3 changes: 1 addition & 2 deletions proposals/4133-extended-profiles.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -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
Expand Down