Logged-in Facebook users will also be transmitting information about their travels around the net to Facebook servers whenever they visit a page deploying the Like button, regardless of whether they actually click that button or not. Facebook also plans to transmit user data to some web services ahead of their visit — so that when you visit the site, it’s “instantly personalized.” In practice, this means that if you are new to the music site Pandora, they’ll have a custom station waiting for you based on the music you’ve liked in your profile.
It doesn't seem that either EasyList or EasyPrivacy are doing anything about this, so I wrote up these rules. They are perhaps too expansive, but they're a good start.
People who publicly announce their personal details on such social networking sites should realise that their online activities can be monitored by the domain. To avoid this, the user should simply log out of their account.
If there are any items that specifically track the user I will consider adding filters for them to EasyPrivacy.
Michael wrote:People who publicly announce their personal details on such social networking sites should realise that their online activities can be monitored by the domain. To avoid this, the user should simply log out of their account.
If there are any items that specifically track the user I will consider adding filters for them to EasyPrivacy.
Err, non registered users are also tracked by facebook, so this is a site that should be added to easyprivacy?!
I just noticed that Engadget has a box at the side which displays facebook activities. I think these third party info-sharing things should be blocked by Easy Privacy.
I googled the ^ character but still don't quite grasp what it does. I'm assuming that OP's filters blocks everything from facebook that's not on facebook. would the other filters listed be necessary then?
Could someone please help write the filter(s) that blocks all of facebook on everything except facebook?
Michael wrote:The second filter should be fbcdn.net^$domain=~facebook.com. Alternatively, fbcdn.net^$third-party would have the same effect.
i ain't sure about that at the beginning when i used $third-party the filter wasn't working, because the images hosted there are loaded from another domain (facebook.com instead of fbcdn.net), this is why i managed to do the job using $domain=~facebook.com
bye!!!!!!!!!!!!!!
The bee is more honored than others, not because the bee labors, but because the bee labors for others.
SMT wrote:why is it it uses easylist what is different other then the UI.
I don't think the adblockers for chrome support the same (as many) switches and filter options as ABP. And at the time of writing I don't think they (chrome ones) actually "block" content, rather they hide everything.