InformAction Forums

I saw mention of the Host Permissions addon recently at GHacks, and the idea looks very interesting: control images+redirects+frames+plugins+scripts on a per-site basis. Kind of a mixture of some NoScript, RequestPolicy, and built-in Firefox permissions.

However, it has been stuck in Experimental status on AMO for a while. Has anyone examined/tried it?

There are similar extensions by the same author for Bookmark Permissions and Tab Permissions. Haven't looked into them.

Similarly, Tahoe Data Manager.
It's part & parcel of SeaMonkey, & as it is really wouldn't recommend it.
Eh, but being an extension (for FF users) suppose it can't hurt to try out.

Just an update on this: I use Tab Permissions and Host Permissions these days, just for image-blocking. You could possibly use them to achieve site-specific permissions, but in a somewhat clunky and non-intuitive way, because default-deny is only available using Tab Permissions, which is tab-based rather than domain-based. And then to whitelist a site, you set it in Host Permissions, which overrides Tab Permissions, *if* the whitelisted site is the first one loaded in that tab. Confusing until you get used to it.

Still, if anyone wants to experiment, it might be interesting to combine them with NoScript's 'Allow top-level sites by default' option, and then use Tab/Host Permissions to manage the top-level site.

Those who are interested in 'allow globally for this tab' (therube?) may want to try installing Tab Permissions, leaving it with default settings (allow all), then when you want to globally allow, first set Tab Permissions to block scripts by default. I think it only applies to newly-opened tabs, though.

As mentioned previously, you could also try blocking scripts by default in Tab Permissions, but allowing top-level sites by default in NoScript, then manage top-level sites on a per-tab basis instead of a per-domain basis. You can still whitelist domains using Host Permissions.