Ghostery does a great job of this already... However, the problem with these types of tools is they frequently break some type of (needed) functionality on the site.

7 caught on Slashdot right now.

I think you mean website developers are so reliant on JS these days, that they think they can't write a site without such heavy use of it that sneezing at it will break their site.

However, the problem with these types of tools is they frequently break some type of (needed) functionality on the site.

I imagine if any plugin gets /really/ popular, the tracking bugs will get modified so they work again, OR publishers/advertisers may start modifying their content to include tests to ensure the health of the tracking bug, before allowing the visitor to view content.

Maybe you just get half a sheet of text, or the first 1.3 windowfuls, then the site will pick up on the tracking bug being broken, and stop rendering content -- while displaying an error about the need to disable such and such plugin to use the site, or waiting until "countermeasure against tracker bug blocking" succeeds.

Considering the very high rates of red/green colour-blindness, the visual warning is fucking useless. I do not understand how, in a predominantly male industry, programmers don't realise the uselessness of Red Green indicators. Is it so incredibly hard to do blue, red, black? Or some combo that will read for even fray scale colorblindness?

It isn't that it's hard, people just don't know that some colours might be inconvenient. If you want to solve the problem, create an extension to remap the colors, either only on the webpage or the whole screen, into something visible. Not trivial, but certainly much easier than convincing web-designers that their colour-scheme isn't perfect.

I'm guessing that most web sites are made by young women who fancy themselves to be graphic designers

Get the fuck out with your stupid techie misogyny.

If your "guessing" involves generalization to the point of an ugly absurdity, you should check yourself. You make it sound like you have a particular beef, maybe with a particular woman (or women) and now you believe that all bad web code is caused by women. It's a bad place to be.

If you want to say, "I have encountered some young women who fancy themselves graphic designers..." you would at least be on more reasonable ground, but then you need to ask yourself, "Does the fact that this group of people were women really have any impact on my statement?"

Now knock it off. People get skeeved out by misogyny and it's pretty easy to pick up on, so the next time you're looking for a job you might just walk away wondering, "That didn't seem to go well, it's probably because of that woman who interviewed me. They're all whores you know".

you guys are aware that scraping the logs of the webservers also gives you some overview of the usage of the site? Is reverse dns-lookup also considered tracking?

my point: monitoring your own site to make it better is fair use, giving this data to other entities is not.

I'm interested to know what theories other people have about the poor use of Javascript.

You mean other than, "Bitches, man, they just don't know how to code, you know? *fistbump*"