From 1e782284670bd1bf971bd88ef61710c7eab8ec17 Mon Sep 17 00:00:00 2001 From: Victor Farazdagi Date: Thu, 13 Apr 2017 08:15:05 +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 7368cbe..6c527d0 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/24888385/c44058bc-1e6b-11e7-93c8-9ab81718b478.png)](https://cloud.githubusercontent.com/assets/188194/24888385/c44058bc-1e6b-11e7-93c8-9ab81718b478.png) +[![image](https://cloud.githubusercontent.com/assets/188194/24991110/39e8a194-2021-11e7-9438-9b01a873f196.png)](https://cloud.githubusercontent.com/assets/188194/24991110/39e8a194-2021-11e7-9438-9b01a873f196.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 `ChatID` and `Chat SymKey` so that newcomers can add their devices to subscribers list).