3 ms·
Oh, I was originally confused about this because I had thought the push notifications were end-to-end encrypted, so they couldn't be cached in readable form by
by modeless 6mo ago
Oh, I was originally confused about this because I had thought the push notifications were end-to-end encrypted, so they couldn't be cached in readable form by the push notification service, and only decrypted by the app on device upon receiving the notification. But it seems like after the notification was decrypted by the app and shown to the user using OS APIs, the notification text was was then stored by the OS in some kind of notification history DB locally on the device?
- saagarjha 6mo agoSomething of that sort.
- bigyabai 6mo ago> I had thought the push notifications were end-to-end encrypted Much of the metadata is plaintext, in both Apple and Google's Push Notification architecture.
- modeless 6mo agoMy understanding is that in Signal's implementation of push notifications the message text is end-to-end encrypted by Signal and decrypted on device by the Signal app. The decryption is not handled by the OS's push notification system.
- tadfisher 6mo agoIf I am reading this right, your understanding is incorrect. Signal's "new messages" push message payload is empty. Upon receiving a message of this type, the Signal app wakes up, fetches the actual messages, and (optionally) displays local notifications for them. At no point does the push message payload contain message text or metadata, encrypted or not.