![]() This could be mitigated by (manually) keeping record of which domains are operated by the same company and thus should go to the same sandbox. The only downside of using a browser profile per domain/tab I can think of is that if you login to a site like a stack exchange using another site like Google, then you need to enter your password again, even though in principle, in the "" browser profile you are already logged in. All this without reducing usability noticeably. ![]() Combine this with spoofing some additional information (screen resolution, os, browser version, plugin versions, etc.) and there is absolutely no way left to track you but for your IP address, which you likely share with quite some other people so it's not usually used for tracking. A browser with the features I describe would have most of the features needed to foil most of that tracking save for very advanced one. Rationale: It's going on my nerves to get tracked all over the internet. For Multifox it might be doable with an acceptable amount of work, I think). If I do I'll be sure to answer my own question here. More and better possible solutions would be nice, otherwise I'll need to dive into the code of those two mentioned plugins and figure out what I need to know and add the missing features (which actually sounds like work and I'm lazy, but who knows, maybe I'll do it. What I don't know for both of them is if they actually separate tabs properly, or if they just separate (ordinary, not flash or dom) cookies, which should be enough for most log ins (which is their stated purpose after all) but not for a privacy and security enhancement? Would still need some more configuration options to really answer my question.
0 Comments
Leave a Reply. |