From 1ff30d4b24cc1cac8a4f2ee1d0c5fdc32ecf6c46 Mon Sep 17 00:00:00 2001 From: Johannes Marbach Date: Wed, 17 Sep 2025 16:06:02 +0200 Subject: [PATCH] Make proposal compatible with MSC4027 Signed-off-by: Johannes Marbach --- proposals/4356-recent-emoji.md | 6 ++++++ 1 file changed, 6 insertions(+) diff --git a/proposals/4356-recent-emoji.md b/proposals/4356-recent-emoji.md index 4206c3e0e..7eaaae4e8 100644 --- a/proposals/4356-recent-emoji.md +++ b/proposals/4356-recent-emoji.md @@ -32,6 +32,11 @@ this nested array is the emoji, the second element is a counter for how often it When an emoji is used in a message or an annotation, the sending client moves (or adds) it to the beginning of the `recent_emoji` array and increments (or initializes) its counter. +When an image is sent as an inline image or in a reaction (using [MSC4027]), the `mxc://` URI of the +image MAY be used as the "emoji" in this event. Clients which do not support such use of images MUST +tolerate the existence of `mxc://` entries, e.g. by ignoring the entries when deciding what to +display to the user, while still preserving them when modifying the list. + As new emoji are being used, clients SHOULD limit the length of the `recent_emoji` array by dropping elements from the end. A RECOMMENDED maximum length is 100 emoji. Apart from this, no other mechanism for resetting counters is mandated. [RFC7159] suggests an upper boundary of 2^53-1 for @@ -66,4 +71,5 @@ While this MSC is not considered stable, `m.recent_emoji` should be referred to None. + [MSC4027]: https://github.com/matrix-org/matrix-spec-proposals/pull/4027 [RFC7159]: https://datatracker.ietf.org/doc/html/rfc7159