From 5da3d986451e55e11e72839bedcd38bd7ab0b959 Mon Sep 17 00:00:00 2001 From: Kerry Archibald Date: Mon, 21 Nov 2022 16:56:04 +1300 Subject: [PATCH] further description about how users might use remote push toggle --- proposals/3881-remote-push-notification-toggling.md | 5 ++++- 1 file changed, 4 insertions(+), 1 deletion(-) diff --git a/proposals/3881-remote-push-notification-toggling.md b/proposals/3881-remote-push-notification-toggling.md index 3dd915d4c..d4ec673aa 100644 --- a/proposals/3881-remote-push-notification-toggling.md +++ b/proposals/3881-remote-push-notification-toggling.md @@ -11,7 +11,10 @@ This is limiting because it means that push notifications can only be en- or dis them. When the latter isn't currently at hand, this can become a point of frustration. The current proposal solves this problem by making the connection between HTTP pushers and Matrix devices explicit and -assigning an enabled state to every pusher. +assigning an enabled state to every pusher. This enables clients to remotely silence (and un-silence) notifications for +other devices. For users with multiple active devices, this means they can avoid unwanted interruptions or duplicate +pings without having to switch context and physically retrieve each device to change settings. A common example is +silencing a mobile device once you sit down at your desktop. ## Proposal