←back to thread

290 points XzetaU8 | 1 comments | | HN request time: 0.001s | source
Show context
jadamson ◴[] No.44657903[source]
I'm curious about the last paragraph relating to Signal. How, exactly, have Brave managed this without also blocking screenshots? Is there a flag Signal missed?
replies(3): >>44657929 #>>44657931 #>>44660961 #
Svip ◴[] No.44657929[source]
According to the same paragraph, it's because Signal isn't a "browser app":

> Given that Windows doesn’t let non-browser apps granularly disable Recall, Signal cleverly uses the DRM flag on their app to disable all screenshots.

(emphasis mine)

Apparently, Microsoft consider browsers special:

> While it’s heartening that Microsoft recognizes that Web browsers are especially privacy-sensitive applications, we hope they offer the same granular ability to turn off Recall to all privacy-minded application developers.

replies(1): >>44657960 #
1. jadamson ◴[] No.44657960[source]
Oops. Yeah, I shouldn't have missed that.

Still, does this mean Microsoft maintains an approved browser list for this? Would the various other less-known Chromium/Firefox forks be unable to take advantage of the same thing?

Edit: https://learn.microsoft.com/en-us/windows/ai/recall/recall-w...

> To make sure that Recall doesn't save your user's browsing history while in modes like this, your app can use the SetInputScope function, setting the input scope to IS_PASSWORD.

> Your app must also have a http or https protocol handler registered before SetInputScope will support the behavior described in this article.

I now wonder if you can register a handler that never gets used since you won't be the default browser (and if you do end up as the default somehow, warn the user when called).