This add on has purpose similar to RequestPolicy and Ghostery and NoScript ABE Rule And any simillar tracker blocker my self tested and work with Firefox 30 and later and much better than RequestPolicy and Ghostery and easier than useing ABE Rule of NoScript https://addons.mozilla.org/en-US/firefox/addon/policeman/
Cool I will check it out, lately Ghostery has become a bit crappy on FF. And RequestPolicy is way too complex for me.
No RP is not complex, it's just annoying to use. This addon a little reminds me of HTTPSB. Also, in case anyone missed the little note, it's still preliminarily reviewed by Mozilla.
Nice to see RequestPolicy back to life and now this addon. In my opinion people are using RequestPolicy in a bad-complicated way. I prefer to have anything allowed by default and I blacklist everything I don't think is useful. I have a few hundreds of untrusted domains in NoScript that gathered with years. And for images and other things where NoScript doesn't help I use adblock (90 rules here).
i just uninstalled RP After install this addon .its read RP rule and add them to Policeman rule just maked some global reject for frame,media,script,object then maked some allow rule for websites that i visit them everyday.so far good
What I mean with complex, is too many options and not easy to figure out how to make stuff work. Which makes it indeed annoying. Actually, the same goes for HTTP Switchboard, I'm more into simple script-blockers.
This morning I received a popup from Avast Anti-virus saying that Policeman 0.7 addon has very poor performance and should be removed. <edit>Disabled popup for extentions
FWIW, I unzipped the policeman v0.7 xpi last night and audited the code. It is solid, well-considered. Performance-wise, it shouldn't be any heavier than RequestPolicy (given an comparably sized ruleset), and considerably less heavy than ABP.
Agreed, I don't have a problem setting up RP for websites that I visit frequently. I suppose it could be annoying, if your like my dad and spend your entire day browsing a 100 different websites before lunch and starting back to the computer before and after dinner. Then again, I don't mind being inundated with requests for permission to allow certain scripts, etc. Except during schooling, during which I fall back to a vanilla browser with some minor config hardening.
Thanks, I like to try new add-ons, especially when development on an add-on stops or add-ons become bloated.
I think adblock is handling blocking from a visual point of view much better than RequestPolicy or Policeman.
i get slowdown in Firefox but because of too many rule (over 1600 rule then after remove them everything back normal). i think it resolved in a later version just maked some global reject rules then make allow rule for site i trust them
I would appreciate reading facts here instead of opinions. If you can't resist opining, at least include a reasonably detailed explanation. Let's have a "discussion", not a chatroom. The authors of the policeman extension and the requestPolicyContinued extension are actively engaged at github. If you have a legit gripe, or a heartfelt wishlist item, open an issue/ticket at github.
version 0.13 https://addons.mozilla.org/en-US/firefox/addon/policeman/versions/ Fixed various application-specific links (e.g. magnet, irc, ircs) Faster rules list update on preferences page. Also added sorting and multiple selection. Added Internationalized domain name support. Configurable blocked elements processing (remove them, replace with placeholder, or ignore). now its support 12 content type!
About Ghostery, it simply does not work correctly in FF (GUI and blocking problems), seems like they introduced some bugs in the code with newer versions. About RequestPolicy and HTTP Switchboard, they are too complex for me, too many options, I prefer simple scriptblockers like ScriptKeeper. https://addons.opera.com/nl/extensions/details/scriptkeeper/?display=en
Regarding HTTPSB I disagree. It's extremely flexible to use, e.g., like Noscript if you prefer that. It's just that most people do not seem to know this. This also applies to µMatrix, of course.
I never understood what was so complicated about whitelisting something, then never having to worry about it again. Same thing regarding HIPS. Or even to never whitelist anything, and in the rare instances you need to allow scripts or cookies for proper functionality (rare in my case, anyway), just make 2 mouse clicks... one on the icon, and then to "temporarily allow". I only ever need to do it really for Youtube, and to log into email (and now this site too for cookies). NoScript, CS Lite Mod, & RequestPolicy I don't consider any hassle at all. Ghostery, I have my reasons for not trusting, plus it's mostly overlap anyway considering other measures I take.
The hastle becomes when you enter a new website that you need to work 100% correctly and it doesnt work until you uninstal NS.
Yes, I've read that µMatrix will be a bit more like the "simple" script-blockers, with that I mean, it will be easier to make sites work, without a lot of tweaking. Seems like HTTP Switchboard already offered a way to do that. But it was also the interface, that was a bit confusing to me.
The point is that the HTTPSB interface - I guess you're talking about the matrix - allows for a very granular control over what your browser is allowed to do or not. But nobody is forced to use it that way. There is no need to whitelist each single cell one by one, you can, e.g., also whitelist the whole domain by clicking the respective cell (just ONE click and, okay, a second one to save the new rules). Again, HTTPSB (and µMatrix) is very flexible to use at one's personal discretion. But it seems that no one cares to read its documentation.
@ tlu Yes, sometimes it's also a matter of being too lazy to figure it all out, especially if you're used to "simple" script-blockers. See link for an example. http://www.ghacks.net/2013/10/04/scriptblock-chrome-blocks-scripts-running-automatically-websites/
Sure, but you can easily configure µMatrix like that. Just whitelist all columns except the script column in the global scope. From now on, all that's left in the domain-specific scopes is to allow scripts -> a "simple script-blocker". But I'm sure that you are aware that a lot of what µMatrix protects against is deactivated by using it that way. But hey - let every man seek heaven in his own fashion
@ tlu To clarify, these "simple script-blockers" give you an option to automatically allow scripts from the "top level domain" + same origin scripts. This will block a lot of third party scripts and trackers.
