From 7725f74d04b0b30b28c24bc613fc9e6ba6b5f3db Mon Sep 17 00:00:00 2001 From: Kegan Dougal <7190048+kegsay@users.noreply.github.com> Date: Thu, 18 Sep 2025 14:08:12 +0100 Subject: [PATCH] Update proposals/4354-sticky-events.md Co-authored-by: Johannes Marbach --- proposals/4354-sticky-events.md | 2 ++ 1 file changed, 2 insertions(+) diff --git a/proposals/4354-sticky-events.md b/proposals/4354-sticky-events.md index 9d0dacb6e..98c79cd80 100644 --- a/proposals/4354-sticky-events.md +++ b/proposals/4354-sticky-events.md @@ -37,6 +37,8 @@ This new primitive can be used to implement MatrixRTC participation, live locati Message events can be annotated with a new top-level `sticky` key, which MUST have a `duration_ms`, which is the number of milliseconds for the event to be sticky. The presence of `sticky.duration_ms` with a valid value makes the event “sticky”[^stickyobj]. Valid values are the integer range 0-3600000 (1 hour). +For use cases that require stickiness beyond this limit, the application is responsible for sending another +event to make it happen. ```json {