The way I like to use NoScript (and RequestPolicy, for that matter) is to periodically assign temporary permissions. I have very few sites "permanently" allowed; basically, it's sites that have already broken by the time their blocked requests even come up to be allowed...and it's a bill-paying site or something that can be a big deal if I have to reload the wrong page, etc etc (the alternative, though, is to write down all those other sites and manually type them in as temporary before going to the site, since there's no entry in the pop-up menu for them).
As you can imagine, this results in quite a bit of overhead. Mostly I'm fine with it; I don't mind "putting my money where my mouth is" when it comes to security, and the higher you turn up the security, the more speed bumps you put in your own way...and that's cool. Buuuut, it sure would be nice if I could do something like:
1) Browse to "https://billpay.powercompany.com/"
2) A Firefox extension recognizes the domain name (or the hostname) and presents a status bar icon (or a submenu of the NoScript status bar icon) with a list of "temporary permissions profiles".
3) I click on one I've named "Make power company site work"
4) The extension goes through and adds a temporary allow for "powercompany.com", as well as "paymentgateway.com". In a perfect world, it would also add a temporary RequestPolicy allow for "powercompany.com -> paymentgateway.com"...but that would be dependent upon RequestPolicy's having some kind of API, I suppose.
These temporary rules would work just like any other temporary rules...it would just be possible to add them all at once and without having to remember each individual thing. For example, when I go to a page on "break.com", I got it narrowed down to this:
[NS] break.com
[NS] ajax.googleapis.com
[RP] break.com -> googleapis.com
...but if you look at the actual list of stuff, it's HUGE. It'd be nice to not have to always remember which sites to allow for everything.

A couple of other things that I think would maximize the usefulness of something like this:
1) Ability to associate each profile with one or more hostname patterns: "google.com *.google.com" for example. Regular expressions here might be overkill, but personally I wouldn't complain.

2) Ability to add rules to other extensions in the future...for example, if there were an extension that did with cookies what NoScript does with active content, etc (of course, these other extensions would have to have their own API). This is one thing that made me think it might be better as a separate extension, since at that point you're almost talking about going for a per-site auto-configuration framework down the road.
Anyway, the basic functionality of being able to do batch adds of temporary permissions would be super useful. Thanks for reading!
