Skip to content

Commit 2dde2c1

Browse files
committed
add m.new_content
1 parent 8627fb7 commit 2dde2c1

File tree

1 file changed

+9
-1
lines changed

1 file changed

+9
-1
lines changed

proposals/1849-aggregations.md

Lines changed: 9 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -221,8 +221,12 @@ An edit would be:
221221
{
222222
"type": "m.room.message",
223223
"content": {
224-
"body": "Hello! I'm an edit",
224+
"body": "s/foo/bar/",
225225
"msgtype": "m.text",
226+
"m.new_content": {
227+
"body": "Hello! My name is bar",
228+
"msgtype": "m.text",
229+
},
226230
"m.relates_to": {
227231
"rel_type": "m.replace",
228232
"event_id": "$some_event_id",
@@ -508,6 +512,10 @@ Do we need to support retrospective references?
508512
ref+target). We can cross this bridge when we get there though, as a 4th
509513
aggregation type
510514

515+
What power level do you need to be able to edit other people's messages, and how
516+
does it fit in with fedeation event auth rules?
517+
* 50, by default?
518+
511519
## Federation considerations
512520

513521
In general, no special considerations are needed for federation; relational

0 commit comments

Comments
 (0)