←back to thread

369 points zeech | 1 comments | | HN request time: 0.2s | source
Show context
wiseowise ◴[] No.43800405[source]
> There is no easy way to close this privacy opening

Sure there is.

Hide screenshot taking behind permission and slap down hard apps that refuse to operate without them.

replies(2): >>43800602 #>>43801037 #
o11c ◴[] No.43800602[source]
It says "screenshots of themselves". The application is responsible for rendering the screen in the first place so it fundamentally doesn't need a permission.

Now, what could reasonably be a permission is "access the internet", but our overlords don't approve of that thought.

(Contrast this to web pages, which do not render themselves and thus can sensibly be blocked from screenshotting)

replies(2): >>43800801 #>>43805909 #
gretch ◴[] No.43800801[source]
I mean yeah technically the website can’t screenshot, but it can do many functionally equivalent things.

For example, it can capture the entire DOM and send it off, including the contents of input fields that have not been submitted.

That DOM capture can be replayed on a browser to show what the user sees. So what’s the difference?

replies(1): >>43801217 #
Thorrez ◴[] No.43801217[source]
Well, blocking javascript would stop that. Noscript is a thing that some people use.
replies(2): >>43802779 #>>43807669 #
1. beeburrt ◴[] No.43807669[source]
Ublock origin also has that ability