Skip to content

Commit

Permalink
Spec propagate=false
Browse files Browse the repository at this point in the history
  • Loading branch information
turt2live committed Oct 23, 2023
1 parent 58f726b commit 8e6e8ac
Showing 1 changed file with 8 additions and 0 deletions.
8 changes: 8 additions & 0 deletions proposals/4069-inhibit-profile-propagation.md
Original file line number Diff line number Diff line change
Expand Up @@ -29,6 +29,14 @@ Request error code is returned.
* [`PUT /avatar_url`](https://spec.matrix.org/v1.8/client-server-api/#put_matrixclientv3profileuseridavatar_url)
* [`PUT /displayname`](https://spec.matrix.org/v1.8/client-server-api/#put_matrixclientv3profileuseriddisplayname)

When `false`, `m.room.member` and `m.presence` events are *not* emitted automatically by the server
during execution of the above two endpoints. Servers should still perform this bit of the spec,
however:

> Additionally, when homeservers emit room membership events for their own users, they should
> include the display name and avatar URL fields in these events so that clients already have these
> details to hand, and do not have to perform extra round trips to query it.
With respect to [MSC3911](https://github.com/matrix-org/matrix-spec-proposals/pull/3911), when the
user updates their profile's avatar with `?propagate=false`, the media they use is *not* cloned nor
used in event updates. The client can manually clone the media if they prefer using MSC3911's copy
Expand Down

0 comments on commit 8e6e8ac

Please sign in to comment.