You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
There are probably a number of different reasons people use this plugin, but for many it will be to avoid browser fingerprinting. Sites can create a hash of a user's User-Agent and various other HTTP headers, along with values discovered from Javascript, such as screen width, and use the hash to uniquely identify a user.
Varying the User-Agent header is a way to combat this.
But it would be nice to also be able to vary some other headers. For example, all my HTTP requests include:
Changing or removing existing values from these lists can break sites, but adding random additional values with very low "q" scores should keep sites working while confounding efforts to fingerprint users.
Add checkboxes to the preferences allowing these headers to be randomized. The browser's genuine Accept-Language and Accept headers would be appended to, so the original values remain.
Accept-Language should have one or two additional valid ISO language codes included with q=0.01. As an additional level of randomness, q=0.02 and q=0.03 could be used occasionally.
Accept should have a random application/x-foo media type included with q=0.01, where foo is a random alphanumeric string. As additional levels of randomness, a second dummy media type could occasionally be included, and q=0.02 and q=0.03 could be used.
These would be randomized on the same schedule as the User-Agent string.
Is there an existing issue for this?
Describe the problem to be solved
There are probably a number of different reasons people use this plugin, but for many it will be to avoid browser fingerprinting. Sites can create a hash of a user's User-Agent and various other HTTP headers, along with values discovered from Javascript, such as screen width, and use the hash to uniquely identify a user.
Varying the User-Agent header is a way to combat this.
But it would be nice to also be able to vary some other headers. For example, all my HTTP requests include:
Changing or removing existing values from these lists can break sites, but adding random additional values with very low "q" scores should keep sites working while confounding efforts to fingerprint users.
For example:
Suggest a solution
Add checkboxes to the preferences allowing these headers to be randomized. The browser's genuine
Accept-Language
andAccept
headers would be appended to, so the original values remain.Accept-Language
should have one or two additional valid ISO language codes included withq=0.01
. As an additional level of randomness,q=0.02
andq=0.03
could be used occasionally.Accept
should have a randomapplication/x-foo
media type included withq=0.01
, wherefoo
is a random alphanumeric string. As additional levels of randomness, a second dummy media type could occasionally be included, andq=0.02
andq=0.03
could be used.These would be randomized on the same schedule as the User-Agent string.
Additional context
https://amiunique.org/fp
The text was updated successfully, but these errors were encountered: