Skip to content

Commit

Permalink
Clarify optional ability to not always federate every field
Browse files Browse the repository at this point in the history
  • Loading branch information
tcpipuk authored Jan 20, 2025
1 parent c4fa474 commit 7ca83db
Showing 1 changed file with 4 additions and 2 deletions.
6 changes: 4 additions & 2 deletions proposals/4133-extended-profiles.md
Original file line number Diff line number Diff line change
Expand Up @@ -102,8 +102,10 @@ method SHOULD NOT delete the key but rather retain it with a `null` value. Serve

## Server-Server API Changes

The federation endpoint [`GET /_matrix/federation/v1/query/profile](https://spec.matrix.org/v1.13/server-server-api/#get_matrixfederationv1queryprofile)` will mirror the client-server
API changes to ensure profile information is consistent between local and federated users.
The federation endpoint [`GET /_matrix/federation/v1/query/profile](https://spec.matrix.org/v1.13/server-server-api/#get_matrixfederationv1queryprofile)`
will mirror the client-server API changes to facilitate profile information consistency
between local and federated users, though homeservers MAY decide specific fields are not
published over federation.

As per the current stable endpoint, it accepts an optional `field` query string parameter to
request a single field. At the time of writing, the Matrix specification says:
Expand Down

0 comments on commit 7ca83db

Please sign in to comment.