InformAction Forums

No it is not spying on you, the most ridiculous thing I have heard. And the most ridiculous thing I've heard is Maone praising WebExtensions on mozilla blog. Have you ever read the documentation? No, I have not. Since when do extensions have documentation other than the text on their AMO page or in...

Attempted to allow (or temporarily allow) firefox.com and got this:

What does firefox.com have to do with noscript.net? I didn't opt in for any tracking of my actions in noscript's settings.
Should I firewall noscript.net?

Hello, I've just updated NS to 2.9.5.1 (I skipped 2.9.5.0, but I guess it was the version that introduced the issues, since it has huge list of changes over previous version). 2 issues appeared for me after updating NS: 1. now 'Home' button on nav-toolbar does nothing, it doesn't even generate any e...

Sometimes ABE rules block a site's functionality and then I have to open NS options in order to toggle ABE. I'd like NS button's menu have a menuitem to quickly toggle ABE.

The info is shown for the previous time's popup.

barbaz wrote:

Thrawn wrote:if something goes horribly wrong, then use Cancel instead of OK!

To note, clicking Cancel won't discard changes to ABE rules, and that isn't a bug.

Yeah, these guys are ridiculous. They can explain any bug as 'not-a-bug-but-cool-feature'.

Also, is that okay that ABE rules work even when user selects "Allow scripts globally"? I don't think so.

The ABE UI is known to be very limited, and does not interact at all with the regular script-blocking. Theoretically ABE is supposed to be usable without NoScript. Are you aware that ABE logs its results to the Browser Console? So why not use those data to display different icons for globally allow...

The thing is that currently it's quite hard to understand why the page is not working on a page with multiple scripts, when they all are generally allowed, but some are forbidden for this page by some ABE rule. Currently, they get shown as "unblocked" scripts, while actually they are block...

thanks, that worked fine.

How to allow scripts from "site.com" on "domain.site.com", but forbid on "site.com" itself, on all other sub-domains and on all other sites?

about:config is made for one-time settings.
Why not move all the noscript's gui to about:config then?
That's console mania.

Thrawn wrote:I really do recommend trying RequestPolicy. AFAIK, it's actively maintained, and it does most of what you seem to what.

https://github.com/jsamuel - just take a look at his activity. If that's what you call "being actively maintained" - well, I have nothing to say.

Thanks, Thrawn.
But there is no whitelist for sites to allow redirections.

thunderscript wrote:Possible? Yes. It is also possible for websites to serve blank pages for instance. What do you recommend? Block all pages from loading so we never get the hypothetical blank page?

I recommend the user to have control over all redirections, so the user decides whether to block or to allow them.