News for hackers. Stuff that matters.

A comment on Meta and Yandex are de-anonymizing Android users' web browsing identifiers. Parent comment

Re:Meta and Yandex are de-anonymizing Android users' web bro... by afavour on Tuesday June 03, 2025 @10:32AM (#44170556)
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.
[ Parent | on HN ]
Re:Meta and Yandex are de-anonymizing Android users' web bro... by deepsun on Tuesday June 03, 2025 @12:51PM (#44172032)
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?

[ Parent | on HN ]
Re:Meta and Yandex are de-anonymizing Android users' web bro... by n2h4 on Wednesday June 04, 2025 @02:38AM (#44177785)
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

[ Parent | on HN ]
Re:Meta and Yandex are de-anonymizing Android users' web bro... by _Algernon_ on Wednesday June 04, 2025 @04:06AM (#44178322)
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.
[ Parent | on HN ]
Re:Meta and Yandex are de-anonymizing Android users' web bro... by cyberax on Wednesday June 04, 2025 @05:43AM (#44178910)
It is still enabled, just a bit hidden: chrome://geckoview/content/config.xhtml
[ Parent | on HN ]
Re:Meta and Yandex are de-anonymizing Android users' web bro... by Oxodao on Friday June 06, 2025 @03:04AM (#44198457)
Why are they CONSISTENTLY make Firefox worse? I really want to love it, and I use it because its basically the only choice but ffs
[ Parent | on HN ]
Re:Meta and Yandex are de-anonymizing Android users' web bro... by selcuka on Tuesday June 03, 2025 @10:10PM (#44176615)
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.

[ Parent | on HN ]
Re:Meta and Yandex are de-anonymizing Android users' web bro... by afavour on Wednesday June 04, 2025 @12:36AM (#44177273)
Because users understand what “microphone access” entails. “Use WebRTC?” means nothing to the average user.
[ Parent | on HN ]
Re:Meta and Yandex are de-anonymizing Android users' web bro... by selcuka on Wednesday June 04, 2025 @02:51AM (#44177855)
Fair point, but "cookies" didn't mean anything to the average user either, and "cookie consent" banners are the norm now.
[ Parent | on HN ]
Re:Meta and Yandex are de-anonymizing Android users' web bro... by Vinnl on Wednesday June 04, 2025 @07:34AM (#44179565)
I think very few people would argue that cookie consent banners in the form in which they are the norm are a good thing just like permission prompts for microphone access are.
[ Parent | on HN ]
Re:Meta and Yandex are de-anonymizing Android users' web bro... by mrguyorama on Wednesday June 04, 2025 @01:15PM (#44183069)
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.

[ Parent | on HN ]