Fully specify room versions (#3432)
* Fully specify room versions * Misc typo clarifications * Try to clarify redactions a bit * Update content/client-server-api/_index.md Co-authored-by: Richard van der Hoff <1389908+richvdh@users.noreply.github.com> * Update content/rooms/v6.md Co-authored-by: Richard van der Hoff <1389908+richvdh@users.noreply.github.com> * Update content/rooms/v6.md Co-authored-by: Richard van der Hoff <1389908+richvdh@users.noreply.github.com> * Better describe client considerations * Doc template params * Move redaction "new stuff" to v3 * Remove unhelpful sentences about "here follows unchanged stuff" * Simplify event signing text * Clean up handling redactions sections * Move v4's event schema to unchanged section * Update content/rooms/v4.md Co-authored-by: Richard van der Hoff <1389908+richvdh@users.noreply.github.com> Co-authored-by: Richard van der Hoff <1389908+richvdh@users.noreply.github.com>
This commit is contained in:
parent
b873ba984c
commit
241e01c332
19 changed files with 1082 additions and 439 deletions
|
@ -1598,7 +1598,9 @@ content from the databases. Servers should include a copy of the
|
|||
when serving the redacted event to clients.
|
||||
|
||||
The exact algorithm to apply against an event is defined in the [room
|
||||
version specification](/rooms).
|
||||
version specification](/rooms), as are the criteria homeservers should
|
||||
use when deciding whether to accept a redaction event from a remote
|
||||
homeserver.
|
||||
|
||||
When a client receives an `m.room.redaction` event, it should change
|
||||
the affected event in the same way a server does.
|
||||
|
|
Loading…
Add table
Add a link
Reference in a new issue