Alexei

Hi itsnotlupus! Could you elaborate on your first statement please? To clarify, when I wrote "dynamically identifying" fingerprinting resources above, I meant connecting fingerprinting-associated property accesses (navigator.plugins, ...) and techniques...

Tor masquerading has been removed in the master branch.

Chameleon in the master branch no longer attempts to masquerade as Tor Browser, in preparation for #1. Note that Chameleon never did anything to hide your real IP address. I'll...

That's what I meant when I wrote Chameleon no longer attempts to masquerade as Tor Browser. In the future, Chameleon will do a combination of subtle randomization of properties (don't...

Right, it's not implemented yet.

If you generate fifteen different fingerprints over fifteen browsing instances, you should be more private, right? You are making it harder for persistent tracking to occur. Tracking within a browsing...

No ETA, sorry. There is much to do here yet, and I am interested in continuing; it's a matter of finding the time. Thanks for your interest!

Hi @chrcoluk, please see https://github.com/ghostwords/chameleon/issues/26.

Hi pde, thanks for the bug report and the suggestions! We could also provide compatibility settings (auto-whitelisting) for high profile websites, where desirability/usability outweigh tracking concerns.

I just added [detection of WebRTC initialization](https://github.com/ghostwords/chameleon/commit/2eda7d20a3cc32a8c0bffd952d188edb989db1af). This should help me find use of WebRTC by fingerprinters in the wild, using [Chameleon Crawler](https://github.com/ghostwords/chameleon-crawler). Once I have some samples, I will...