What’s the purpose of keeping a history of seen notifications in a database? That shit should be being automatically purged if it needs to exist to show it, after its been dismissed.
I wonder if this revelation will trigger a change in how it works, since apple has often tried to do things securely?
My android shows a history of notifications. Not sure what the retention period is. It does add conveniece by allowing me to check dismissed notifications. It allows some monitoring about the type, content, and frequency of notifications as well as control to block them.
It certainly now appears the convenience isn’t worth the loss of privacy, though.
Once in a while I get a notification that, for one reason or another, doesn’t actually bring me to the content it was supposed to link to and instead brings me to the main page of an app, and sometimes it’s difficult or impossible to find where the link was supposed to go
But going in through the notification history, the second try usually takes me where it was supposed to go
Ive had that issue as well, deeplinks can be fickle creatures if the app isnt perfectly set up and youre potentially in a spot it fails in.
Control.
Apple has gone out of their way to fuck with the government trying to get data from people phones, I really don’t think this was something done on purpose to help them.
The data has to be stored somewhere to be shown, so a temporary spot existing isn’t a surprise. It almost sounds more like lazy developers not thinking the government could access the history that only gets purged after X amount of time, instead of continually being pruned.
No way, it’s for the data collection.
They dont want to share it, that’s right, but it’s very much not done by accident.
Did you read the headline?
Use Molly as your Signal client instead. It solves this.
Molly is always the answer.
Clever. Not much you can do for this except not subscribe your app to the notifications API, or take extra steps to attempt to clear them, but I don’t remember that being an option on iOS. Going to be an interesting fix.
On iOS, under Settings > Notifications > Notification Content
I’m assuming that changes what it actually displays, but is there confirmation that those data dont enter the notification system on the back end?
This is for the client display only, and not the iOS API interface as I’m discussing. It’s not very plainly laid out in the docs, but one would assume any queuing of content into the notification system would be stored or cached if not cleared. There doesn’t seem to be a way to have a client of that system to clear it’s own data once it’s in there, just cancel last notification.
deleted by creator
You know, I’m starting to think that maybe the “drive bay full of thermite” guy way back in the day WASN’T crazy…
my signal notification history is a lot of “Locked message”
Not allowing notifications has been SOP since the beginning.
Go through your settings. There’s almost certainly some app doing something you don’t prefer.
Any software allowed on an appstore can be backdoored and decrypted many different ways. Even if the notification routing was turned off to prevent this, you still have a virtual keyboard that can be debugged at the system level or in one of the secure enclaves running on an iPhone. All of it is an illusion of security being sold for profit. Even the devices allowed to be sold must be backdoored many differnet ways by the state. In other words, anything that actually provided security and anonymity either from a hardware or software level would never be allowed on the market in the first place.
