4 ms·
The author is concerned that an ad might be able to surreptitiously turn on the camera or microphone You are correct, that is the author's concern. The reason
by reaperducer 5y ago
The author is concerned that an ad might be able to surreptitiously turn on the camera or microphone
You are correct, that is the author's concern.
The reason the rest of us are concerned is because the general public has been conditioned by Google and others to just press "Accept" any prompt that pops up, no matter how dangerous.
- ethbr0 5y agoThis is a catch-22 though. If something dangerous to privacy is being widely used in the world, then putting it behind a prompt creates an avalanche of prompts, and results in user apathy. But not prompting requires you to choose a default, which either default to block and breaks things (if it was actually required) or defaults to allow.
- Hallucinaut 5y agoI would happily set all browsers to always deny all ads and untrusted domains the ability to use microphone and camera at all times. So there's no need for an avalanche of alerts, it just shouldn't be permissible for a resource from an untrusted source. It may be widely used, but for a highly concentrated set of sites. I can't think of an occasion I've used it beyond Google, Microsoft, and Zoom properties. Perhaps Slack and Discord too? So there must be a better way.
- noahtallen 5y ago> deny… untrusted domains the ability to use microphone and camera at all times I believe this is the default for most browsers now, right? (Or have I been spoiled by Firefox?) This is the best way, where the camera is always inaccessible, unless you enable it for a domain which needs it. Since I rarely ever see the camera/mic request option, I don’t think we’ve been conditioned to allow this type of request. (Compared to cookies, which show up on nearly every site.) If you want to disable permissions dialogues altogether, then what’s a trusted domain? Just zoom and a handful of others? If you write yourself a nice app which uses the mic, do you have to email Google to get yourself added to the list of trusted domains? That would be pretty bad for the open web, so permissions dialogues are the alternative
- smichel17 5y agoThe solution to this is simple, but not easy: block everything by default and do not prompt to enable it (but do show an indicator of what has been blocked). This is how Firefox tracker protection, uMatrix, noscript, and a plethora of ad blockers and other privacy tools work.
- jeffbee 5y agoWhat? In what way have you been conditioned to accept prompts?
- fault1 5y agoI think there is most definitely conditioning going on. I watched my fiance click on one of the "accept all cookies" GDPR-prompts (it's become an antipattern) a few days ago. She almost automatically did it without thinking. I went to the same site on my laptop and if you clicked decline, it immediately brought up modal dialogs that made that site unusable. I can see why 99% of people would be conditioning to just hit yes.
- jeffbee 5y agoAnd you blame Google for that, instead of some brain-dead Eurocrat?
- mrtranscendence 5y agoWho said anything about blaming google for users clicking “ok” without thinking about it?
- jeffbee 5y agoThe person to whom I replied!
- theWreckluse 5y agoTo be fair, he said Google and others. I still don't know how much Google is responsible though.
- hetspookjee 5y agoGoogle goes way further and doesn't even serve a prompt. Instead they show you a opt-out plugin that you can download to run in your browser. Most blatant disregard of rules and feeling better than the rest behaviour if you ask me.
- jefftk 5y agoIn this case there isn't a prompt: access to the camera and microphone is disallowed by default in cross-origin iframes. The site would have to specifically delegate permission to the ad before it could even trigger a prompt.
- denton-scratch 5y ago> just press "Accept" any prompt that pops up I auto-press [Accept]. I use an ad-blocker. I reject 3rd-party cookies. I disable JS by default, and re-enable it selectively for sites that refuse to work without JS. If that re-enablement involves more than a few clicks, I'll close the site - there are other fish in the sea. What am I doing wrong?