[RESOLVED BY STICKY POST] Per-site whitelisting?
Posted: Sat Mar 31, 2012 12:44 am
First, thank you for NoScript, it's a very useful tool.
There is one itch I have though: how can I deal efficiently with very pervasive domains, such as content delivery nerworks? For instance, I have no problem running scripts from amazon's cloudfront.net when I am visiting a site I trust such as bitbucket.org, but it's another story to allow the domain globally... Same goes for Google analytics: there are sites I want to give my stats to, but others I'd rather not.
Of course, I can allow / forbid sites on temporary grounds using the already provided mechanism, but it's very tedious - did I miss or misunderstand something? If not, what about implementing per-site whitelists? What would be really cool is having a "Allow cloudfront.net from bitbucket.org" option, but I don't know if it's even doable.
There is one itch I have though: how can I deal efficiently with very pervasive domains, such as content delivery nerworks? For instance, I have no problem running scripts from amazon's cloudfront.net when I am visiting a site I trust such as bitbucket.org, but it's another story to allow the domain globally... Same goes for Google analytics: there are sites I want to give my stats to, but others I'd rather not.
Of course, I can allow / forbid sites on temporary grounds using the already provided mechanism, but it's very tedious - did I miss or misunderstand something? If not, what about implementing per-site whitelists? What would be really cool is having a "Allow cloudfront.net from bitbucket.org" option, but I don't know if it's even doable.