Hacker News Reader

Comment by kevindong | Hacker News Reader

I'm inclined to say that there is a small handful of cases where apps should actively prevent/modify screenshots:

* apps that show sensitive personal info (e.g. credit card numbers, SSN, etc.) should ideally self censor the sensitive info to help prevent accidental leaks

* corporate devices where the phone and all of the data within it belongs to the employer

View on HN

I can agree with corporate policy, however I don't need my banking app or my web browser (private browsing mode) deciding whether I know how to handle a screenshot securely on my own device. You certainly won't find these restrictions on a Windows 10 machine running Chrome. Why should it be on mobile?

The real solution would be making the images directory not a free for all. There should be an OS filepicker which gets used to allow an app access to photos rather than the app having access directly. That way a screenshot is not instantly leakable.

It isn't a free for all already and that's not a "real solution" as there's a real need & use for some apps to have access to some/all images. Such as those that do automatic backup & syncing of them.

What's missing is just a user override of "no really screenshot this that wasn't an accident", that's about it.

What about the analog hole?

When it comes to piracy of copyrighted music and movies, the analog hole is deemed to offer a significantly degraded signal and therefore DRM is still effective enough.

When it comes to screenshots, I think a native screenshot and a photo of a screen offer more similarities than differences and therefore it's not worth blocking one without blocking both.

Reply on news.ycombinator.com