You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: proposals/4036-room-organization-by-promoting-threads.md
+20-4Lines changed: 20 additions & 4 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -1,4 +1,4 @@
1
-
# MSC436: Room oranization by promoting threads
1
+
# MSC436: Room organization by promoting threads
2
2
3
3
Sometimes, having a discussion in a busy room can be difficult.
4
4
People are often simply replying with a message event which is technically not related (`m.relates_to`) using replies (`m.in_reply_to`) or threads (`m.thread`) with the previous messages of the conversation making separation of one conversation from others difficult.
@@ -10,7 +10,7 @@ This MSC solely proposes client-side behavior.
10
10
11
11
## Proposal
12
12
13
-
Standardize a room state `m.promote_threads` (`dev.coffeeco.promote_threads` for non-finalized implementations of this MSC) with a Boolean value or an object, defaulting to `false`.
13
+
Standardize a room state `m.promote_threads` (`dev.coffeeco.MSC4036.promote_threads` for non-finalized implementations of this MSC) with a Boolean value or an object, defaulting to `false`.
14
14
15
15
The value SHOULD NOT be set to an object
16
16
but clients MUST consider an object as implicating a value of `true` (possibly with additional behavior changes)
@@ -56,15 +56,31 @@ The object may contain a strings,
56
56
for example to specify the label of the button to access the message input box outside the scope of a thread
0 commit comments