• 3 Posts
  • 147 Comments
Joined 1 year ago
cake
Cake day: June 12th, 2023

help-circle





  • For the use cases you describe actually sound right on the mark? If you’re viewing a page and you want something summarised on there, it would be nice to not have to leave that page, but to stay in its context, for example. If you’re looking at the specs of a particular phone, ditto.

    (I don’t expect I’ll use this feature myself, but if I did, it sounds like I’d use it in that way. Luckily, I can just choose not to use it without any downsides.)






  • Here:

    When a user interacts with an ad or advertiser, an event is logged in the browser in the form of a value. That value is then split into partial, indecipherable pieces and then encrypted. Each piece is addressed to a different entity — one to Divvi Up at ISRG and one to Mozilla — so that no single entity is ever in possession of both pieces. (…) As an additional protection, the pieces are submitted to Divvi Up and Mozilla using an Oblivious HTTP relay operated by a third organisation (Fastly). This ensures that Divvi Up and Mozilla do not even learn the IP address of the indecipherable piece they receive.




  • That is a bit confusing, but the feature called “Fingerprint Protection” (i.e. blocking known fingerprinters) isn’t the only protection built in. I’m not motivated enough to find a full list right now, but it also includes e.g. limiting the information in the User Agent header. I did at least find a list of things that were worked on at some point by searching for “Tor uplift”, which is a good starting point if you’d like to find more: https://wiki.mozilla.org/Security/Fingerprinting

    I’d also add that actually blocking requests to known fingerprinters does help. It’s more like camera’s getting disabled when you’re around: sure, from the point of view of the camera, it’s suspicious that it stopped working, but it can’t see you, so it doesn’t know who is standing out.