Brian/Josh/Thane,
Yes I understand this. Well sort of. Sadly, I forgot about 'whitelist.'
Now I seem to be
driven to quickly construct my own personal whitelist to finally stop
falling back to
my usual 'temporarily allow all' usage w/NoScript. I have no plan to
disable NoScript.
I allow it to update automagically w/o my input.
I got the impression years back that NoScript is a mandatory
add-on/extension to the FF
Browser. I do admit to some fear about playing under the hood in NoScript.
I'd like to think my query was about where in the blinding number of
NoScript faqs did I
view a very long list (20+ printed pages?) of how to retrofit NoScript.
I swear that I bookmarked the page; but now when I do need it, I can not
find it again live,
and, it appears that NoScript may NOT allow their faq pages to be
bookmarked(?).
Age, memory, and, patience are problems for me. I am now working on my
whitelist!
Duncan
On 02/04/2012 19:36, Brian Weeden wrote:
There are many websites that require JavaScript to function properly,
especially for things like menus and dynamic content. So increasingly more and
more websites are breaking if you run NoScript. But there are still a lot of
malware that requires JavaScript to run,
So if you run it, expect to have sites that don't function right. But you can
always whitelist those sites in NoScript, it just takes a couple clicks. There
are still many people who find the inconvenience of having to whitelist a good
trade off for security.
-------
Brian Weeden
Secure World Foundation
+1 202 683-8534
On Feb 4, 2012, at 19:31, DSinc<[email protected]> wrote:
Ever since starting the FF Browser I have included the add-on/extension
No-Script.
I never asked why. I just trusted the Collective.
I let No-Script mostly auto-update itself on one client. Then, I go update my
other
two clients. No harm, no foul.
Now, I seem to be going blind reading 'No-Script' faqs about how to get
No-script to,
perhaps, back off a bit. Perhaps I am dealing with 'personalization.'
Is this normal with other No-Script devotees?
Thanks,
Duncan
