RE: Request Policy scripts vs identical NoScript scripts
I keep seeing people use Request Policy and I've included mentioning in my threads posted in the Avast forums previously that I would really like to use Request Policy, tried it 3 times, and gave up very quickly each time. I just recently tried it a 4th time, and, again...shortly after trying it, I ran into a problem with NoScript allowing the exact same things that Request Policy was blocking (or vice versa?), so I gave up once more; plus I couldn't understand why I would need to devote time adjusting two different extensions for the very same items.
QUESTION:
Since I don't understand its use but realize it is a security extension, what do I do when both extensions list the exact same items but conflict with allowing/blocking privileges? I assume it will take time for the Request Policy to allow my own personal adjustments with it, but if I'm to simply verify what NoScript is showing first before making Request Policy match, then why do I need Request Policy? It is supposed to be different than NoScript, and this is very confusing "to me". Any suggestions?
EDIT: PLEASE DISREGARD THIS POST OF MINE...Problem is solved:
I just got done reviewing "Request Policy", again, and I've changed my mind...I do NOT want it.
So please forgive me for taking up space here and/or perhaps even wasting anyone's time. I'm sorry!
