All browser prompts need a "Lie" function in addition to Allow and Block.
<Website> wants to:
* Know your location
* Use your camera
[ Allow ] [ Block ] [ Lie ]
@polychrome When would you want to use "Block"? Why note replace Block with Lie?
@robryk
in cases where, if it were a real-lifenexchange, you would say "thanks but no", instead of either " fuck off!" or looking straight ahead and avoiding eye contact.
Those exist. There may be sites/services which you would allow to access you camera *some* of the time, like video conferencing.
@polychrome
The site has the opportunity to have their own UI that allows me to choose whether I want to use the camera there before requesting the browser permission. Sites that expect users to sometimes, but not always, allow them to access the camera, and that are not trying to push their users to allow access always, usually recognise that they would want to ask the user first themselves, so on well-behaved sites I would not get the prompt unless I actually wanted to give them camera access.
@robryk
Hmm... not sure. Wouldn't it be nice if the site operator didn't have to implement that stuff themselves but could simply use the existing implementation in the browser?
@polychrome
@Mr_Teatime @polychrome The implementation in the browser allows me to say "always allow". I might do that if I trust the site. It doesn't mean that when I click a link that points me at a meeting room on that site I want my video to be immediately published to other participants.
@Mr_Teatime @polychrome That said, I'd agree with you if the API allowed the website to say "please actually ask the user, even if they gave a blanket approval" and if it allowed the site to describe who else will be getting the stream (a VC client would normally provide you with a list of usernames of other participants, or something hopefully equivalent).
