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

MSC3676: Transitioning away from reply fallbacks #3676

Merged
merged 7 commits into from
Feb 2, 2022
Merged

MSC3676: Transitioning away from reply fallbacks #3676

Changes from 1 commit
Commits
Show all changes
7 commits
Select commit Hold shift + click to select a range
fd34ea9
MSC3676: Transitioning away from reply fallbacks
ara4n Jan 26, 2022
0857b9d
msc number
ara4n Jan 26, 2022
d7c7641
md fails
ara4n Jan 26, 2022
80e5529
typoe
ara4n Jan 26, 2022
e9aeb4c
Update proposals/3676-transitioning-away-from-reply-fallbacks.md
ara4n Jan 26, 2022
8a78065
incorporate feedback
ara4n Jan 26, 2022
d179d6f
consolidate justification
ara4n Jan 26, 2022
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
10 changes: 8 additions & 2 deletions proposals/3676-transitioning-away-from-reply-fallbacks.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -43,8 +43,10 @@ make reply fallbacks best effort. Specifically:
* In practice only `m.room.message` events with msgtype `m.text` or similar
(`m.emote`, `m.notice`) would be able to express reply fallbacks (using the
`m.body`, `format` and `formatted_body` fields).
* Thread events using replies as a fallback representation for threads would
not include a textual reply fallback at all.
* Thread events using replies as a fallback representation for threads should
not include a textual reply fallback at all (and so avoid threaded messages
triggering notifications). The same would apply for any other usage which uses
ara4n marked this conversation as resolved.
Show resolved Hide resolved
replies as a fallback.

This means that we can still use reply fallbacks for notification purposes
until that is properly fixed by [MSC2781](https://github.com/matrix-org/matrix-doc/pull/2781)
Expand All @@ -70,6 +72,10 @@ MSC handles thread+fallback notification interaction). However, as per
above, this feels lower priority than the importance of adding threads to
Matrix, which would be unblocked rapidly by this MSC.

We could not use `m.in_reply_to` as a fallback for clients which don't
understand `m.thread`, but this would result in an unnecessarily
terrible fallback for older/transitional/WIP/simple clients.

## Security

By temporarily keeping reply fallbacks around on a best effort basis, we're
Expand Down