mirror of
https://github.com/matrix-org/matrix-spec
synced 2026-03-28 22:14:10 +01:00
Apply suggestions from code review
Co-authored-by: Patrick Cloke <clokep@users.noreply.github.com>
This commit is contained in:
parent
f7e8b6ccc7
commit
b8ab467e60
|
|
@ -6,7 +6,7 @@ type: module
|
||||||
|
|
||||||
{{% added-in v="1.4" %}}
|
{{% added-in v="1.4" %}}
|
||||||
|
|
||||||
Threads allow users to visually branch their conversations in a room. Typically most used
|
Threads allow users to visually branch their conversations in a room. Typically mostly used
|
||||||
when a room is discussing multiple topics, threads provide more organisation of communication
|
when a room is discussing multiple topics, threads provide more organisation of communication
|
||||||
that traditional [rich replies](#rich-replies) can't always offer.
|
that traditional [rich replies](#rich-replies) can't always offer.
|
||||||
|
|
||||||
|
|
@ -142,7 +142,7 @@ A specific error code is not currently available for this case: servers should u
|
||||||
alongside the HTTP 400 status code.
|
alongside the HTTP 400 status code.
|
||||||
{{% /boxes/note %}}
|
{{% /boxes/note %}}
|
||||||
|
|
||||||
##### Server-side aggreagtion of `m.thread` relationships
|
##### Server-side aggregation of `m.thread` relationships
|
||||||
|
|
||||||
Given threads always reference the thread root, an event can have multiple "child" events which
|
Given threads always reference the thread root, an event can have multiple "child" events which
|
||||||
then form the thread itself. These events should be [aggregated](#aggregations) by the server.
|
then form the thread itself. These events should be [aggregated](#aggregations) by the server.
|
||||||
|
|
|
||||||
Loading…
Reference in a new issue