Top Themes from the Hacker News discussion
1️⃣ OSes keep notification previews unencrypted
“iOS stores the previously displayed notifications in an internal database, which was used to access the data. It’s outside of Signal’s control, they recommend disabling showing notification content in their settings to prevent this attack vector.” – shantara
The notification database persists after the app is removed, allowing forensic extraction of message text.
2️⃣ Signal’s default notification settings are insecure
“The default setting is actually not the insecure one…” – nickburns (linking a screenshot)
“The Show Previews setting is “When Unlocked (Default)”. “Name only strikes me as a fairer compromise…” – JumpCrisscross
Most users never change the default, so the app shows full message bodies on the lock screen by default.
3️⃣ Push notifications are just a “wake‑up” ping; the app decrypts locally but the OS stores the plaintext
“Signal’s FCM and APN notifications are empty and just tell the app to wake up, fetch encrypted messages, decrypt them, and then generate the notification ourselves locally.” – greysonp (Signal developer)
Even though the payload is encrypted, iOS/Android store the decrypted preview in a shared database.
4️⃣ Community frustration over security‑vs‑usability defaults
“Security is not a binary, but a spectrum… the vendor selects the best configuration for its average user, which is not the most secure configuration.” – amazingman
Many commenters argue the defaults should be the most privacy‑preserving and that users should not have to hunt through settings to stay secure.
These four themes capture the most‑repeated concerns and arguments in the thread.