From cafeaa6a75ca7dc1bcad829671d1c35e7929c2e9 Mon Sep 17 00:00:00 2001 From: Matthew Hodgson Date: Wed, 16 Jul 2025 00:04:01 +0100 Subject: [PATCH] Update proposals/4291-room-ids-as-hashes.md Co-authored-by: Andrew Morgan <1342360+anoadragon453@users.noreply.github.com> --- proposals/4291-room-ids-as-hashes.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/proposals/4291-room-ids-as-hashes.md b/proposals/4291-room-ids-as-hashes.md index a685cae24..96e29a80d 100644 --- a/proposals/4291-room-ids-as-hashes.md +++ b/proposals/4291-room-ids-as-hashes.md @@ -40,7 +40,7 @@ The following changes on a new room version are made: > > Must contain less than or equal to 10 events. Note that if the relevant auth event selection rules are used, > this restriction should never be encountered. - > **NEW: MUST NOT contain the create event ID (room ID).** + > **NEW: MUST NOT contain the create event ID. This is already implied by the `room_id` field.** * The "Description" field for `room_id` is adjusted to state: > Required: Room identifier. Omitted on `m.room.create` events. - Concerning [auth rules](https://spec.matrix.org/v1.14/rooms/v11/#authorization-rules):