From 7d0289ea4b0b1d0a143a3c4e5e6728a182d922b4 Mon Sep 17 00:00:00 2001 From: z0ccc Date: Sun, 5 Jun 2022 23:35:42 -0400 Subject: [PATCH] readme update --- README.md | 10 ++++++++++ 1 file changed, 10 insertions(+) diff --git a/README.md b/README.md index 69b7f39..aafe45a 100755 --- a/README.md +++ b/README.md @@ -14,12 +14,22 @@ You can test and compare Vytal and other extensions on https://vytal.io Vytal contains no ads and signup is not required. +## Advantages of chrome.debugger API + +Most extensions that provide anti-fingerprinting features rely on content scripts to inject script tags into webpages. Code injected with the script is used to spoof data points. There are many limitations to script tag injection method which you can read about here: https://palant.info/2020/12/10/how-anti-fingerprinting-extensions-tend-to-make-fingerprinting-easier/ + +The chrome.debugger API allows data points to be spoofed without the limitations of script tag injection's. + ## Limitations ### Tab initialization There is a slight delay between when a new tab is opened and the debugger starts mocking the data. This allows for websites to get the original value of the data before it is changed. After the initial loading of a tab, this will no longer be an issue. +### Debugging bar + +While the chrome.debugger API is active, a bar under the address bar is displayed. The only way to hide the ba + ### Locale override does not mock language data Unlike the Chrome devtools location sensor, overriding the locale does not change language data (such as navigator.language or navigator.languages). There is an open ticket about this here: https://bugs.chromium.org/p/chromium/issues/detail?id=1320419