From 5653fe1884d722a29e6044ee6f9c59e4bd1dc038 Mon Sep 17 00:00:00 2001 From: Timo Date: Tue, 2 Jul 2024 17:21:25 +0200 Subject: [PATCH] add reference to MSC4143 (MatrixRTC) --- proposals/4140-delayed-events-futures.md | 3 +++ 1 file changed, 3 insertions(+) diff --git a/proposals/4140-delayed-events-futures.md b/proposals/4140-delayed-events-futures.md index 298990271..851556818 100644 --- a/proposals/4140-delayed-events-futures.md +++ b/proposals/4140-delayed-events-futures.md @@ -25,6 +25,9 @@ The motivation for this MSC is: Updating call member events after the user disconnected by allowing to schedule/delay/timeout/expire events in a generic way. +It is best to first read [MSC4143](https://github.com/matrix-org/matrix-spec-proposals/pull/4143) and in particular +the section: ["Reliability requirements for the room state"](https://github.com/matrix-org/matrix-spec-proposals/blob/toger5/matrixRTC/proposals/4143-matrix-rtc.md#reliability-requirements-for-the-room-state) to understand the MatrixRTC usecase of this MSC. + It turns out that there is a big overlap to other usecases in Matrix which can also be implemented using the proposed concept: - Updating call member events after the user disconnected.