From 188e6c74a4c5d52fb9472e4e8077d4e7e7c91d08 Mon Sep 17 00:00:00 2001 From: Travis Ralston Date: Tue, 18 Apr 2023 14:29:08 -0600 Subject: [PATCH] Update for MSC1767 --- proposals/3954-extensible-events-emotes.md | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/proposals/3954-extensible-events-emotes.md b/proposals/3954-extensible-events-emotes.md index fdb0531b..9b52343a 100644 --- a/proposals/3954-extensible-events-emotes.md +++ b/proposals/3954-extensible-events-emotes.md @@ -10,8 +10,8 @@ are represented should not block the overall schema from going through. ## Proposal -MSC1767 allows for regular, non-emotive, text to be sent with an `m.message` event type and `m.markup` -content block. This MSC simply introduces a new `m.emote` event type taking a **required** `m.markup` +MSC1767 allows for regular, non-emotive, text to be sent with an `m.message` event type and `m.text` +content block. This MSC simply introduces a new `m.emote` event type taking a **required** `m.text` content block, enabling emotes in rooms supporting extensible events. An example: @@ -21,7 +21,7 @@ An example: // irrelevant fields not shown "type": "m.emote", "content": { - "m.markup": [{"body": "says hi"}] + "m.text": [{"body": "says hi"}] } } ```