Noscript should also prevent loading of feedburner images

[pascal]

My goal is to ensure that Google does not know any website that I visit. Currently, Noscript does not ensure this goal is met.

Feedburner is owned by Google. Requests to feedburner.com are stored on google's servers.
I would therefore like to request that Noscript extension blocks the images from Feedburner.com.

In particular, the feedburner "feed count" images are found on many popular websites. Example request for a feedburner image:

Code: Select all

http://feeds.feedburner.com/~fc/FeedForMkyong?bg=99CCFF&fg=444444&anim=1

Thank you for noscript & looking forward to hearing feedback, or seeing this request implemented

[Alan Baxter]

looking forward to hearing feedback

I use Adblock Plus to block that and recommend you do it that way too. Add the following filter to ABP.

Code: Select all

||feedburner.com^$third-party,image

[pascal]

Alan, thank you for the answer, very appreciated!

It turns out that adblockplus is probably more the right tool for my goal (not being tracked by google).
I will now use a combination of Ghostery and Adblockplus with the feedburner filter.

If you have any more tip as to what filters to set to ensure that we are not tracked by big corporations when browsing the Internet, please share here. I will publicize on my popular website these solutions for all to enjoy.

[Alan Baxter]

I found that filter on Fanboy's Annoyances list. To cut down on tracking I recommend Adblock Plus with either of:
EasyList plus EasyPrivacy subscriptions or
Fanboy's Adblock plus Fanboy's stats subscriptions
and Fanboy's Annoyances in addition to either of the preceding pairs.

[DJ-Leith]

My goal is to ensure that Google does not know any website that I visit.

I recommend that you also consider the combination of NoScript (to block scripts etc) and
RequestPolicy (to block cross-site requests).

The loading of images, [including Adverts] and other cross-site requests - 'connections away from the site you thought your were at' are used to track visitors.

Both work on the principal: everything is blocked unless you allow it - default deny.
Both have Whitelists.

I find that my Whitelists, for both RequestPolicy and NoScript, are very small.
I TA (Temporarily Allow) when required.

See the discussion in this Thread:
A few requests for next versions
http://forums.informaction.com/viewtopi ... 50&p=35457

Also, search this Forum for "RequestPolicy" (one word) - you will find plenty of tips on how to use it in combination with NoScript.

DJ-Leith

[Giorgio Maone]

Notice also that the same effect can be obtained by leveraging just NoScript, with the following ABE rule to be added in the USER ruleset:

Code: Select all

Site .feedburner.com
Deny INC(IMAGE)

[pascal]

Regarding Request Policy, I was talking to a privacy advocate recently, who is using Request Policy, but he mentioned spending quite a bit of time adding external servers to the white list.
This is because these days lots of websites use external domains to load static content (to allow browser to parallelize requests more efficiently)

I am quite happy with Adblockplus and Ghostery at the moment. If you can think of any way this setup is not efficient in being not tracked by google, please let me know

PS: that said, Noscript is fantastic and thank you for developing and maintaining it