From f8932dced142ec5ea633bfb163bfc7579ac38a07 Mon Sep 17 00:00:00 2001 From: Thorin-Oakenpants Date: Sun, 7 Nov 2021 06:48:45 +0000 Subject: [PATCH] remove ambiguous line The point was that google have said (stated in policy, but fuck knows where that is located these days) that it is anonymized and not used for tracking. It's an API used by **_4 billion devices_** - the API has privacy policies for use. If a whistleblower or someone else found out that google was using this to enhance their user profiling, then all hell would break loose. And they don't even need this to fuel their ad revenue. It is provided, gratis, to the web to help ensure security - they wouldn't dare taint it and get it caught up in a privacy scandal involving **+4 billion devices_**. And in all this time (since 2007), there has been no such whistleblower or proof it is used to track or announcements by google of changes to the contrary. Anyway, a quick search brings up - Here is their policy - https://www.google.com/intl/en_us/privacy/browsing.html - it's empty and points to - https://www.google.com/intl/en/chrome/privacy/ - and if you scroll down to "Safe Browsing practices" it doesn't say anything about privacy policies for the API itself (or the owner of the API) - it just spells out what happens in chrome - I'm not going to bother to look any further and find a history of policy changes Anyway, this is Firefox and hashes are part hashes bundled with other real hashes - and we turned off real time binary checks. So this line can fuck the fuck off. It was meant to reassure those who want the security of real-time binary checks, that privacy "shouldn't" be an issue, but I'm not going to expand on it --- user.js | 1 - 1 file changed, 1 deletion(-) diff --git a/user.js b/user.js index bc2d1d5..68d5560 100644 --- a/user.js +++ b/user.js @@ -242,7 +242,6 @@ user_pref("extensions.webcompat-reporter.enabled", false); // [DEFAULT: false] to Google, only a part-hash of the prefix, hidden with noise of other real part-hashes. Firefox takes measures such as stripping out identifying parameters and since SBv4 (FF57+) doesn't even use cookies. (#Turn on browser.safebrowsing.debug to monitor this activity) - FWIW, Google also swear it is anonymized and only used to flag malicious sites. [1] https://feeding.cloud.geek.nz/posts/how-safe-browsing-works-in-firefox/ [2] https://wiki.mozilla.org/Security/Safe_Browsing