Re: [w3c/permissions] Explicitly limit permission lifetimes (#231)

I appreciate the points made above, and agree with @jyasskin and @martinthomson. It'd be useful to discuss whether (and if) how long a capability is given out is a reasonable thing to consider during privacy reviews (as part of HR or otherwise).

However, I don't think this issue is the right place for that discussion.  This issue, the links given in the discussion, and the 👍  and comments in support of the issue, are all specific to geolocation.  Further, an outcome of this issue could be that geolocation requires greater, lesser or just otherwise different protections than other permission'ed capabilities. Its also possible that limits on how long sites held permission to geolocation functionality could/should be defined in a way thats outside of the permissions API.

Finally, I am not aware of a requirement that privacy (or any other) issues need a PR to stick / stay.  I have though made a specific suggestion in https://github.com/w3c/permissions/issues/231#issuecomment-652041324 and if turning that into a PR would help discussion, thats fine with me too.

@marcoscaceres please kindly move this issue back to its previous location, and re-add the labels that it had previously (if that last part is not possible, i can do so). I'd then be happy to follow @jyasskin suggestion and open a new issue in this repo, to discuss whether permissions in generally should include lifetime limitations. 

-- 
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/w3c/permissions/issues/231#issuecomment-809625618