3 ms·
> Here are the parameters used by Pirsch to generate a fingerprint: > * the IP is the most obvious choice. It might change, as IPs are reused by ISPs as they o
by hnlmorg 6y ago
> Here are the parameters used by Pirsch to generate a fingerprint:
> * the IP is the most obvious choice. It might change, as IPs are reused by ISPs as they only have a limited pool available to them, but that shouldn't happen too frequently
> * the User-Agent HTTP header contains information about the browser and device used by the visitor. It might not be filled though, but it usually is
A couple of questions:
1. Does anyone know of a decent Firefox plugin that can subtly change the User-Agent string for each new tab? I'm not thinking changing it to a different browser rendering engine string but maybe add a random key like
hash-buster/$randomstring
2. Isn't Chrome making its User-Agent string static? (ref: https://www.osnews.com/story/131177/google-is-seeking-to-deprecate-chromes-user-agent-string/ https://www.osnews.com/story/131177/google-is-seeking-to-dep...). @marvinblum (looks like you're the maintainer?) wouldn't this then skew your results?
- marvinblum 6y agoOh well that's sound bad for my solution. I'm unsure how well it would work with just the IP, but it's possible to add more headers, like the accepted languages and file types. If you really need precise tracking you probably won't get around tracking on the client side.