Rated 3 out of 5 stars

by another Winston Smith on Nov. 23, 2009 · permalink

Good Idea but Too Much .... that is if you have assembled the programs you need to make a reliable policy choice - NoScript,Ghosteray, CounterPixel, etc.

They not only give you a choice of detailed information needed to answer RequestPolicy, but they are already taking steps to either block a site or draw its fangs.

If I approve something in NoScript, which takes action, doing what I need to do to lower the Red Flag is a bit redundant.

The cure would be for the author to work with NoScript - a fantastic program at blocking intruders known or unknown to you, Ghosteray, for some reason Not As Popular because it ID's infotheft organizations ala DoubleClick, and, without EVER SAYING SO (I've suggested this to author) BLOCKING every one it can name, Counterpixel, which, as far as I've determined, neither blocks nor shows the offending screen pixels, the (untested here) PluginChecker, which should block or at least ID plug-ins installed by persons other than those at your keyboard, etc.
(oh, I'm leaving NettiCat's work out and a dozen others)
AND producing a single policy program - what is allowed always, what is NEVER allowed without a specific unlock from the User, what policies are site- or even page-related, permanently or just for a d/l.
THAT'S what we desperately need, a single report on EVERYTHING a site is throwing at us, so we can give appropriate answers - and what we do not have ... yet.

Good Idea which does too much of what others still do better E for Effort.