2 ms·
I would assume Google uses this data to optimise its blocklist and determine impact. By Apple blocking this data they are reducing the effectiveness of the Safe
by sschueller 6y ago
I would assume Google uses this data to optimise its blocklist and determine impact. By Apple blocking this data they are reducing the effectiveness of the Safe Browsing list.
This is one item I would not block, we already have huge issues with this list providing false positives. Giving Google even less data to make adjustments make this worse.
- tonfa 6y agoI don't think that's even correct, the article is somewhat contradictory: > Since Apple uses a hashed prefix, Google cannot learn which website the user is trying to visit. Up until iOS 14.5, Google could also see the IP address of where that request is coming from. > And setting up a proxy server to filter Google Safe Browsing traffic just so Google cannot users’ browsing activity will be a welcome move for a lot of users. IIRC the safe browsing was designed to avoid disclosing user traffic: https://developers.google.com/safe-browsing/v4/update-api https://developers.google.com/safe-browsing/v4/update-api > The Update API is designed for clients that require high frequency, low-latency verdicts. Several web browsers and software platforms use this API to protect large sets of users. > If you are concerned about the privacy of the queried URLs or the latency induced by a network request, use the Update API.
- ViViDboarder 6y agoThis only prevents Google from harvesting IP address of the users. They don’t need that information to tell if the place I’m going is bad.