The letter S in a light blue, stylized speech bubble followed by SpeakBits
SpeakBitsThe letter S in a light blue, stylized speech bubble followed by SpeakBits
Trending
Top
New
Controversial
Search
Groups

Enjoying SpeakBits?

Support the development of it by donating to Patreon or Ko-Fi.
About
Rules
Terms
Privacy
EULA
Cookies
Blog
Have feedback? We'd love to hear it!

Private Browsing 2.0

webkit.org
submitted
a year ago
byiareuniquetotechnology

Summary

Apple added new privacy protections to Private Browsing in Safari 17.0 and 17.2. Apple believes that users should not be tracked across the web without their knowledge or their consent. New protections include blocking network loads of known trackers and blocking ad-tracking.

The new Privacy Protection option is available in the latest version of Apple’s iOS 8 software. The new Privacy protection option is also available in Apple ’S Safari software. It allows users to opt out of the Privacy Protection feature by clicking a button.

Safari 17.0 adds the following protections for all users: Encrypted DNS queries are used to resolve server hostnames into IP addresses, which is a necessary function of accessing the internet. Private Browsing uses Oblivious DNS over HTTPS by default, which encrypts and proxies DNS queries to protect the privacy and integrity of these lookups.

Fingerprinting is the process of creating a unique identifier for each user. The unique identifier can be used to track a user's location, or to make it easier to find them. It can also be used as part of a user’s profile to show that they are in a certain location.

We view cross-site tracking and per-site user recall as privacy problems to be addressed by browsers. This could mean altering the APIs, gating them behind user permissions, or not implementing them. With Safari’s advanced fingerprinting protections enabled, Safari applies tiny amounts of noise to pixels on the canvas.

In Safari 17.5, we made audio noise injection more robust in the following ways. Instead of using a uniform distribution for the injected noise, we now use normally-distributed noise. We’ve refactored the noise injection mechanism to support arbitrary levels of noise injection.

The intent of the API is to help advertisers target users with ads based on each user’s interests. The user doesn’t get told upfront which topics Chrome has tagged them with or which topics it exposes to which parties. It all happens in the background and by default.

Privacy Enhancements in Both Browsing Modes are enabled by default in both regular browsing and Private Browser. In Safari 17.2, cross-site Blob URLs are partitioned by first-party web sites. When a tab in Safari is closed, all of the session storage associated with it is destroyed.

 web site website internet site site screen CRT screen notebook notebook computer cash machine cash dispenser automated teller machine automatic teller machine automated teller automatic teller ATM-0
15

11 Comments

5
practicalmagic
a year ago
First I'm hearing of that Topics API... that is absolutely bullshit! Why do I want some random ass website to be able to know what topics I've been to!?
4
kaiserseahorse
a year ago
They really snuck this in last year huh? I heard all about the v3 manifest but not this.
4
practicalmagic
a year ago
Yup, when I read it in the article, I though that can't be right...
4
eldiscipulo
a year ago
Yea... there are quite a few concerns with it
3
practicalmagic
a year ago*
Thanks for finding that! I'm glad to see I'm not the only one that would be worried about this access!
4
joseph
a year ago
Is there a comparison to how this works in regards to the controversial new feature Firefox introduced?
2
iareuniqueOP
a year ago
They both ultimately force anonymizing your data to ensure some level of privacy.
3
froggyweather
a year ago
I'm glad two browsers are trying their best to combat the privacy violations of the third.
2
iareuniqueOP
a year ago
Everyone should just jump ship from Chrome honestly
1
froggyweather
a year ago
Chromium too since they're pushing a lot of this stuff into it as well
2
iareuniqueOP
a year ago
I usually lump them together since Google controls the whole stack anyway