Comment by afavour
6 days ago
That feels pretty useless. You might as well do what happens today: enable it by default and allow knowledgable power users to disable it. If it's disabled, show a message to the user explaining why it's needed.
6 days ago
That feels pretty useless. You might as well do what happens today: enable it by default and allow knowledgable power users to disable it. If it's disabled, show a message to the user explaining why it's needed.
Today there's no way to disable it, I searched through my Firefox Mobile settings. So I'd say it's for very "power" users.
And why enable it by default, why not disable by default?
Also, sibling comments say iOS is already asking for the permission, why not just copy it?
it does exist in `about:config`, which could be made as a UI setting instead:
`media.peerconnectin.enabled`.
on cromite[1], a hardened chromium fork, there is such a setting, both in the settings page, as well as when you click on the lock icon in the address bar.
[1]: https://cromite.org
IIRC the standard mobile firefox version no longer makes about:config available. You need to be on a beta or nightly build to access it.
2 replies →
Why not? How is this different than, say, location access, or microphone access?
I want to be able to configure this per web site, and a permission prompt is a better interface than having an allow/deny list hidden in settings.
Because users understand what “microphone access” entails. “Use WebRTC?” means nothing to the average user.
Fair point, but "cookies" didn't mean anything to the average user either, and "cookie consent" banners are the norm now.
1 reply →
Mobile apps require location permissions to use Bluetooth right now, even though that's a hard to understand situation for average people.
If a feature can be used to track people, you have to flag it off or else you are just contributing to the tech Big Brother apparatus.