From 91635d30d56f752a8f9992d622cc3d098b902eb7 Mon Sep 17 00:00:00 2001 From: Victor Farazdagi Date: Fri, 14 Apr 2017 09:57:25 +0300 Subject: [PATCH] Updated Whisper Push Notifications (markdown) --- Whisper-Push-Notifications.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/Whisper-Push-Notifications.md b/Whisper-Push-Notifications.md index 811254b..a6e7980 100644 --- a/Whisper-Push-Notifications.md +++ b/Whisper-Push-Notifications.md @@ -8,7 +8,7 @@ It is crucial to understand what is **Whisper Notification Service** is designed ## High-Level Overview of the process -[![image](https://cloud.githubusercontent.com/assets/188194/24991150/72bb9f44-2021-11e7-80c0-39699e8aeaae.png)](https://cloud.githubusercontent.com/assets/188194/24991150/72bb9f44-2021-11e7-80c0-39699e8aeaae.png) +[![image](https://cloud.githubusercontent.com/assets/188194/25035829/b3cf02aa-20f8-11e7-882b-1a4958bcda13.png)](https://cloud.githubusercontent.com/assets/188194/25035829/b3cf02aa-20f8-11e7-882b-1a4958bcda13.png) The crux here is how to allow `DeviceB` to trigger notifications on `DeviceA`, all this w/o knowing much of which wnode is used, or details of `DeviceA`. And `Chat SymKey` solves this issue elegantly (the beauty is that it works for both one-on-one and group chats, all you need to ensure is share a secret, namely `Chat SymKey`, so that newcomers can add their devices to subscribers list).