I'm using firefox 4RC too, I just feel tired because of using two browsers at the same time. Using NoScripts. I think it'll be fine :)
I'm using firefox 4RC too, I just feel tired because of using two browsers at the same time. Using NoScripts. I think it'll be fine :)
I am using latest chrome in normal mode
The folloving sites were visited:none
So if this is what i get am I good to go with What and sb-i in the same browser?
Just to doublecheck
Last edited by @Freak; 13.03.11 at 14:44.
If you read Microsoft or Google (don't remember really) Words About this , they said that this is invade of user's privacy (you have no rights to know what websites i opened ) calling it a bug so they fixed it in the new versions except opera who said that the coders only fix bugs not a feature .
I didn't say I didn't agree nor that the Opera team shouldn't change that. You think I like letting trackers know where I've been?
The thing is, both whoever said that and the Opera guys are right. It is a privacy invasion that uses a standard CSS feature. It'd be nice if they did the same change as Firefox and Chrome, but as they see it there's no reason to do so.
"I just remembered something that happened a long time ago."
Am I safe with Google Chrome as long as I just delete my history before visiting a tracker? Should I delete my cookies too?
I am a little confused after reading the whole thread. Am I right on the following?
1. changing userContent.css can only solve PART of the problem;
2. disabling layout.css.visited_links_enabled should work;
3. using addon Noscript should be safe;
4. Firefox 4 and above should be safe.
For some reasons, I am still using Firefox 3.6. Also I feel Noscript is a little overkill. Does this mean that I have to use option 2 and lose the colouring feature for visited/unvisited links?
This can only prevent the "real" CSS only leak.
It can has some downsides though.
That one I'm not sure about, never used this option.
Not alone, this only prevents the JS based leak.
I don't know which version exactly fixed this leak, so I can't tell you for sure Firefox 4 fixed it.
Yes, you need to combine NoScript and the custom css, or just disable your history globally.
Also, using NoScript is always a good option.
And yes, you'll lose the coloring feature.
------------------------------>>>>>>>>>> <<<<<<<<<<------------------------------
FF12 and IE9 passed all test found in this thread, I guess this leak is fixed and no need to be afraid of running SB-I and trackers in same browser...
Bookmarks