From b2f4c9c2b6494a01bf5885ccfbf772a92f9f55da Mon Sep 17 00:00:00 2001 From: Tulir Asokan Date: Thu, 10 Jul 2025 19:08:59 +0300 Subject: [PATCH] Fix image src --- 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 09b684581..06e81ce16 100644 --- a/proposals/4291-room-ids-as-hashes.md +++ b/proposals/4291-room-ids-as-hashes.md @@ -54,7 +54,7 @@ This creates a chicken/egg problem when upgrading rooms because: - The create event of the new room needs the tombstone event ID in `content.predecessor.event_id`. - The `m.room.tombstone` event needs ... -Creator chicken egg problem +Creator chicken egg problem To break this cycle, this MSC removes the `content.predecessor.event_id` field from the `m.room.create` event. There appear to be no security