Post #1524219
2026-04-09 15:22 UTC
@phillip Two entirely unrelated things, though the notification settings mitigation may close this particular hole. (Depends on whether it's the app or the OS acting on those settings) This particular issue has nothing to do with "unified push" and concerns only an internal detail of iOS, where notifications are stored in a local on-device file outside of the signal app, which the phone also has to be jailbroken to access.
Signal already mitigates "unified push" to the point it exposes nothing to google/apple other than "this user possibly received a message." They only send a push to 'wake up' the app to fetch the content directly from signal's servers, with no content exposed (because they can't expose the content to apple/google, as they don't know it themselves)
Replies (1)
-
@phillip@social.lol 2026-04-09 15:30
@becomethewaifu afaik the notification setting is acted on by the Signal app itself, preventing even the on-device notification db from storing a copy of the message preview. I haven’t heard of Signal mitigating unified push like that, though I suppose it makes sense architecturally. I’ll update that bit on my OP, thanks! Do you know if Signal has any documentation on their notification architecture? I’d love to learn more about it Edit: actually I’m just dumb 🙃 sorry for the accidental misinformation