The trick with noscript is that not all sites are transparent about what FQDN's are actually being called. The trick in those cases: reasoning through the list of blocked domains and sometimes the recently blocked sites list (after clearing it 1st) then doing trial & error enabling domains.
Worst case there is an allow all but only use it when you have one tab open for just the pita site then turn it of before browsing elsewhere. On Feb 4, 2012 4:36 PM, "Brian Weeden" <[email protected]> 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 >
