I would recommend making a Facebook VM if you really want to get on. This helps on two fronts:
1) You must REALLY want to get on facebook if you go through the extra step of booting up a VM
2) They can track all they want inside your VM since you use it ONLY for facebook.
/s/facebook/any other social service you intend to use.
Better yet, use Fluid[1] and create a single site browser for Facebook. Make sure you use the paid version of Fluid App, so you get separate cookie storage for each SSB you set up.
There is not much use switching browser.
They tracks you using cookies even if you dont login(like button and other plugins)
You need to block/remove all the facebook related cookies.
Cookies do not cross browsers. If he's using a second browser, Facebook cannot read the cookies set in the first browser. They could use some IP matching logic or something, but it would be prone to a lot of false positives.
I believe this isn't always the case. If you're using multiple browsers in OS X all built on Webkit for instance, they share the same cookie store.
Firefox and multiple firefox profiles isolate cookie storage and I also use Fluid on OS X to build site-specific browsers. The paid version offers a feature to isolate cookie storage within each app.
In my limited understanding it's the difference between the webkit engine that OS X provides to developers to use, as opposed to Chrome which probably does something different in that regard. Besides site-specific browsers, there are plenty of makeshift OS X tools that implement their own built in browser, and these applications do indeed share cookies with Safari.
The easiest way to test this is with Safari and any of the OS X site-specific browser or http debugging tools.
The Flash Player's "Shared Objects" (aka Flash cookies) are stored in a common directory, so the same Flash data is accessible from any browser (running as the same user). I do not believe Facebook's tracking is this nefarious, but the method would be quite easy to implement.
Chrome, Chromium and Safari absolutely don't share the same cookies on Mac OSX. This is easily verifiable. Not sure about other browsers... (what other browsers?).
I think you're referring to other applications which embed Safari's rendering engine. I wouldn't really call those browsers.
If users must visit social websites like Facebook in privacy mode in separate browsers, perhaps they should rethink whether they should be using Facebook at all.
The convenience/security trade-off varies user to user, but for something as simple as FB, it might be considered overkill by most.
I would encourage browsers that support isolated profiles, multiple browsers that don't share cookie storage, or using a jailed site-specific browser approach.
