Compare commits

..

No commits in common. "24204a4161279b0cdcce32f2a565c60511a0826d" and "e064e4391e13ce10d027ae2bbeb51d8503c64e46" have entirely different histories.

View file

@ -3,9 +3,9 @@
{{% added-in v="1.18" %}} {{% added-in v="1.18" %}}
This module enables clients to track a user's cumulated emoji usage across different This module enables clients to track a user's cumulated emoji usage across different
devices. The data is stored in the [`m.recent_emoji`](#mrecent_emoji) devices. The data is stored in the [`m.recent_emoji`](/client-server-api/#mrecent_emoji)
global [account data](#client-config) and can, among other things, be used to global account data event and can, among others, be used to generate recommendations
generate recommendations in emoji pickers. in emoji pickers.
#### Events #### Events
@ -28,13 +28,9 @@ SHOULD limit the length of the `recent_emoji` array by dropping elements from
its end. A RECOMMENDED maximum length is 100 emoji. its end. A RECOMMENDED maximum length is 100 emoji.
To enable future extension, clients MUST tolerate and preserve array elements To enable future extension, clients MUST tolerate and preserve array elements
within `recent_emoji` regardless of whether they understand or support the within `recent_emoji` that they don't understand or support. This means ignoring
contained `emoji` value. This means ignoring entries with unrecognised values the entries when deciding what to display to the user while retaining them when
of `emoji` when deciding what to display to the user while retaining them when
modifying the array (unless the modification is for truncation). modifying the array (unless the modification is for truncation).
To prevent undefined behavior, clients SHOULD remove array elements that
don't conform to the event schema such as elements with negative counters.