Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Clarify that reply chain fallback for threads may not be present #1439

Merged
merged 3 commits into from
Feb 21, 2023
Merged

Clarify that reply chain fallback for threads may not be present #1439

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
3 commits
Select commit Hold shift + click to select a range
8dfec73
Clarify that reply chain fallback for threads is not required
jplatte Feb 16, 2023
e71bb02
Add changelog file
jplatte Feb 16, 2023
f263163
Update changelogs/client_server/newsfragments/1439.clarification
richvdh Feb 21, 2023
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
1 change: 1 addition & 0 deletions changelogs/client_server/newsfragments/1439.clarification
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -0,0 +1 @@
Clarify that reply chain fallback for threads may not be present.
2 changes: 1 addition & 1 deletion content/client-server-api/modules/threading.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -74,7 +74,7 @@ Clients which understand how to work with threads should simply do so, however c
might not be aware of threads (due to age or scope) might not be able to helpfully represent
the conversation history to its users.

To work around this, events sent by clients which understand threads include [rich reply](#rich-replies)
To work around this, events sent by clients which understand threads SHOULD include [rich reply](#rich-replies)
metadata to attempt to form a reply chain representation of the conversation. This representation
is not ideal for heavily threaded rooms, but allows for users to have context as to what is
being discussed with respect to other messages in the room.
Expand Down