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

MSC3881: Remotely toggle push notifications for another client #3881

Open
wants to merge 18 commits into
base: main
Choose a base branch
from
Open

MSC3881: Remotely toggle push notifications for another client #3881

Changes from 1 commit
Commits
Show all changes
18 commits
Select commit Hold shift + click to select a range
18818cd
first cut
Sep 5, 2022
1844be0
add tables
Sep 5, 2022
08c45ed
exlcude non-pusher notifs
Sep 5, 2022
62eb149
tweak headings
Sep 5, 2022
75ff4df
add msc number
Sep 5, 2022
eef3fc5
Update proposals/3881-remote-push-notification-toggling.md
Sep 9, 2022
ae4ec9f
invert is_disabled field to enabled
Sep 9, 2022
8492d15
format
Sep 9, 2022
e653dcf
make device_id nullable
Sep 13, 2022
2a843ef
remove device_id illegal in post para
Sep 22, 2022
8a78282
use optional throughout
Sep 22, 2022
f93afcb
add support flag to /versions
Sep 22, 2022
b82104c
remove copy paste mess
Sep 22, 2022
469d540
Update proposals/3881-remote-push-notification-toggling.md
Nov 21, 2022
8fc3851
Update proposals/3881-remote-push-notification-toggling.md
Nov 21, 2022
ec835f1
move migration section under unstable prefix heading
Nov 21, 2022
5da3d98
further description about how users might use remote push toggle
Nov 21, 2022
8a6bc04
Merge branch 'kerry/remote-push-toggle' of github.com:matrix-org/matr…
Nov 21, 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
Prev Previous commit
Next Next commit
Update proposals/3881-remote-push-notification-toggling.md 
Co-authored-by: Travis Ralston <[email protected]>
  • Loading branch information
@turt2live
Kerry and turt2live authored Nov 21, 2022
commit 8fc3851cd0b9d50fc6a64b16220afd77fe6fd174
2 changes: 1 addition & 1 deletion proposals/3881-remote-push-notification-toggling.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -61,7 +61,7 @@ MSC.
Home servers should indicate their support of this MSC by adding `org.matrix.msc3881` and `org.matrix.msc3881.stable` in
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I guess we should also explain the difference between the 2 values: with or without stable prefix. Or add a link to a spec/doc explaining this difference.

The stable suffix seems to indicate that stable fields for the feature are now exposed from the server and can now be used in clients. This enables client to know whether it should use the stable or unstable fields.

the response of `/_matrix/client/versions`.

Clients that connect to a home server that doesn't yet support this proposal should interpret a missing `enabled` value
Clients that connect to a homeserver that doesn't yet support this proposal should interpret a missing `enabled` value
as `true`.

Home servers should migrate pushers that were registered before this proposal so that `enabled` is `true`
Expand Down