43
Meta and Yandex are de-anonymizing Android users’ web browsing identifiers (arstechnica.com)
submitted 1 year ago by to c/privacy@lemmy.dbzer0.com
6 comments fedilink hide all child comments

all 6 comments

sorted by: hot top controversial new old
[–] 6 points 1 year ago (1 child)

Is this kind of thing why uBO added the localhost / localnet filter? Or does this go beyond that?

  • permalink
  • fedilink
  • source
  • hideshow 1 child comment
    •
  • [–] 3 points 1 year ago

    I think so.

    Some browsers for Android have blocked the abusive JavaScript in trackers. DuckDuckGo, for instance, was already blocking domains and IP addresses associated with the trackers, preventing the browser from sending any identifiers to Meta. The browser also blocked most of the domains associated with Yandex Metrica. After the researchers notified DuckDuckGo of the incomplete blacklist, developers added the missing addresses.

  • permalink
  • fedilink
  • source
  • parent
    • [–] 5 points 1 year ago (3 children)

    Firefox with the EFF Privacy Badger extension.

    That is all.

  • permalink
  • fedilink
  • source
  • hideshow 3 child comments
    •
  • [–] 12 points 1 year ago (2 children)

    It's not all. Not by a long shot.

    https://abrahamjuliot.github.io/creepjs/

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 2 child comments
    •
  • [–] 2 points 1 year ago (1 child)

    Any recommendations for additions to the arsenal?

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 1 child comment
    •
  • [–] 1 point 1 year ago

    It depends entirely on your threat model. Start with privacyguides.org

    For anyone simply not wanting to have their data scooped up en mass, you still have to defeat IP triangulation, browser fingerprinting, and shadow profiling. Our data is extremely valuable to some people, and they go to great lengths to get it.

  • permalink
  • fedilink
  • source
  • parent