- cross-posted to:
- technology@lemmy.world
- cross-posted to:
- technology@lemmy.world
This seems to be about recovering push notifications of incoming messages from the phone. Still not good.
HN discussion: https://news.ycombinator.com/item?id=47703573
You must log in or # to comment.
Signal already has a setting that blocks message content from displaying in push notifications; the case highlights why such a feature might be important for some users to turn on.
That’s a different vector.
What’s your vector, Victor?
Requesting clearance, Clarence.
Roger roger
notification is extractable
notification has no data
safe data remains safe
The real question is why Apple isn’t doing cleanup of their logs. There’s no reason to maintain that information after a notification has been acknowledged.
Why would any phone / desktop keep notification history? I already don’t get the notification feature in default KDE Plasma desktop.
If you accidentally dismiss a notification, you can go back in the history to see it. Or if you dismiss a message notification that you want to respond to later. Or if a notification keeps popping up and disappearing and you want to investigate.
Fair enough. But I don’t think more than 24h of notification history would ever be needed, right ?
Debatable. But I have it enabled on my Android phone, it and indeed only shows me the last 24 hours.
Sometimes I try to swipe up and the phone interprets it as a sideways swipe and dismisses something I hadn’t read. So I’ve hit the history feature to see what that might have been.
Now, what I’d prefer is an undo button, and I wouldn’t have expected that history to persist more than 10 minutes, but it’s not 100% useless.
10 minutes is fair
Dunst has one by default. I have used it twice. Once when I was very tired and couldn’t output something into a file for some reason (I think it was a full disk) and piped it into a notification instead and once when a program put some error message in there and the notification expired before I read it.
It can also be fun for seeing how your perception of notifications compares to the ones that actually show up. It is however important to remember that it exists and to not let important data end up there.
We’re going to need phone cases that require a password, and destroy the phone if tampered with. And a signal blocking bag for occasions.
That would not have helped in this instance
They can’t extract anything from a device that’s no longer a device. Even if the defendant is required to hand over passwords, there is opportunity to eliminate the device before it’s out of control of the defendant, prior to receiving a legal order to preserve it, or the execution of a search.
Basically make a burner phone that’s literally a burner.
A case wont get to the Emmc. You know what will do the same without being explosive whatsoever? Using something secure.
Look at the duress options on GrapheneOS for example.
GrapheneOS is limited to specific hardware. And a strip of thermite will absolutely end any flash memory, while being stable and safe to handle. 300c isn’t that hard to reach.
Legally the problem becomes the existence of data. If it exists, it can be subpoenaed, and you can rot in jail until you comply. Destruction has a simpler hurdle of making sure it happens due to others negligence or before it’s under other jurisdiction.
