Skip to content

Commit a399fda

Browse files
committed
Allow editing per-message profiles
1 parent b24060e commit a399fda

1 file changed

Lines changed: 6 additions & 0 deletions

File tree

proposals/4144-per-message-profile.md

Lines changed: 6 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -32,6 +32,12 @@ The field is allowed for all message events, which currently means
3232
`m.room.message` and `m.sticker`. A future MSC may expand the field to other
3333
events, such as reactions.
3434

35+
Modifying per-message profiles using edits is allowed, i.e. clients SHOULD
36+
include the per-message profile object in `m.new_content` when sending edits
37+
and read it when receiving edits. Including the per-message profile object in
38+
the edit fallback at the top level is not necessary, as all clients that support
39+
per-message profiles can be assumed to support edits.
40+
3541
### Field limits
3642
After JSON decoding, `id` and `displayname` MUST be at most 255 bytes of UTF-8
3743
and every code point MUST be a Unicode scalar. Null bytes (`\u0000`) are not

0 commit comments

Comments
 (0)