From 240d6502cbcddb1a52acc1df6c88768c1793f411 Mon Sep 17 00:00:00 2001 From: Kegan Dougal <7190048+kegsay@users.noreply.github.com> Date: Thu, 2 Oct 2025 11:04:59 +0100 Subject: [PATCH] Update proposals/4354-sticky-events.md Co-authored-by: Travis Ralston --- proposals/4354-sticky-events.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/proposals/4354-sticky-events.md b/proposals/4354-sticky-events.md index e45a357b3..c254fc9fb 100644 --- a/proposals/4354-sticky-events.md +++ b/proposals/4354-sticky-events.md @@ -348,7 +348,7 @@ The `/versions` response in the CSAPI includes: ## Addendum This section explains how sticky events can be used to implement a short-lived, per-user, per-room key-value store. -This technique would be used by MatrixRTC to synchronise RTC members. +This technique would be used by MatrixRTC to synchronise RTC members, and should land in the spec as a suggested algorithm to follow. ### Implementing an ephemeral map