From f97e4e64cd2be6c46fd582ce09dd5e35d90cc814 Mon Sep 17 00:00:00 2001 From: Matthew Hodgson Date: Mon, 25 Nov 2024 09:48:06 +0000 Subject: [PATCH] clarify that non-empty delayed membership events are invalid --- proposals/4143-matrix-rtc.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/proposals/4143-matrix-rtc.md b/proposals/4143-matrix-rtc.md index 4fe6fc01a..5b950c5fc 100644 --- a/proposals/4143-matrix-rtc.md +++ b/proposals/4143-matrix-rtc.md @@ -151,8 +151,8 @@ The `leave_reason` is added so clients can be more verbal about why a user disco Receiving clients will be able to detect if the delayed event request was recognised by the presence of the `has_delayed_overwrite: true` unsigned property. If the property is missing the event is invalid. -This also invalidates delayed leave events that are send with a valid membership content. They do not contain the -`has_delayed_overwrite: true` unsigned property. +This also ensures that delayed leave events that are incorrectly sent with a non-empty membership content are invalidated, +as they will not contain the `has_delayed_overwrite: true` unsigned property. #### Historic sessions