[thinkling]

Deleting cookies isn't enough anymore to prevent tracking. Facebook knows your home IP address, your browser user-agent, and likely your browser finger print. Should they care to, they don't need a cookie to connect you with data they already have about you.

[FridgeSeal]

I wonder if there's a good way to get around some of these problems.

In my country, and with my ISP we have dynamic IP's, so I don't have a 'home IP' as such. Browser user agent's are pretty easy to spoof/mock/etc. Browser fingerprinting is super hard to work around though - especially stuff like the canvas fingerprinting, because blocking it outright can also be used as a unique identifier when combined with other data.

Would it be possible to build some kind of public repository of canvas fingerprints, then whenever a site tries to build one, rather than outright blocking it, you return one of the public fingerprints from the repository. Get the repo big enough and used by enough people (especially if you could extend it out to other identifiers like fonts) and I imagine you would have a good chance of driving down one's uniqueness in a privacy conscious manner.

I'm not familiar with JS or the mechanics of how these fingerprints are generated, so I don't know if this is possible, but I imagine that if you can block them (Firefox 'Canvas Blocker' extension, you could intercept them?

[AlexAffe]

I use noscript and a cookie manager (protection of wanted cookies, deletion of all others upon shortcut). I havent seen facebook tracking pixels by now, are they being used? From an img src request they could still see my IP and user agent, plus knew which site I am on, but as far as I can tell they just use script src, and that gets blocked.