Hi Gili, I have a doubt here, which requires some clarification for your (hybrid) proposal, "Browser caches the permissions for some particular website to use the same permissions for the next time", my doubt in this statement is, If I open a website and gave permission to access my camera, after some time if my wife want to open the same app in the same computer/mobile, where she don't want to give permission to the camera. Chances are there for providing permissions to camera unknowingly. I don't know whether I understood it correctly or is there any misunderstanding, Thanks, Kiran. On Tue, Sep 24, 2013 at 3:36 AM, Martin Thomson <martin.thomson@gmail.com>wrote: > I tend to agree with this conclusion. That said, the guidance I've > received indicates that this is a little better understood than Anne > suggests. That guidance is pretty clear: it is not currently a good idea to > talk to users about fingerprinting risks, no matter how the question is > formulated. But times, and people, change, so putting this side for now > seems wise. > On Sep 24, 2013 7:55 AM, "Anne van Kesteren" <annevk@annevk.nl> wrote: > >> On Mon, Sep 23, 2013 at 1:17 AM, Harald Alvestrand <harald@alvestrand.no> >> wrote: >> > Adding directly the 3 people who I think you have to convince >> explicitly. >> >> I think we need to revisit this at some point in a more general >> context. I think being able to indicate somehow (declarative maybe, >> manifest) what you need and having success/failure for these as the >> user starts using the respective features (or you might grant a few if >> the user bookmarks the app) might make sense. >> >> I don't think we're quite there yet though in fully understanding what >> an app on the web is. It's fine to experiment, but too soon to >> standardize. >> >> >> -- >> http://annevankesteren.nl/ >> >
Received on Wednesday, 25 September 2013 05:01:32 UTC