[CLOSED] Temporarily enable captcha domains

[pjk]

I don't enable JS on any domains that host captchas by default, to reduce tracking across the web.

This necessitates temporarily enabling JS on such domains on sites that A) won't work without them for login purposes, and B) I really need to view/use. After a successful login, I reset temporary permissions.

I'm aware of the contextual permission feature, but I think what I need here is some sort of a time-dependent permission. Long enough to keep the captcha happy during login, and then disabling JS on that captcha domain shortly afterwards. (In part because my usual tactic of globally disabling temporary perms after login to a captcha-requiring site often re-enables other domains as well, domains that I still want to remain enabled for the moment.)

Is there any automatic way to accomplish this?

TIA

[barbaz]

This is not possible, and would go against the design of NoScript.

NoScript is a security tool, not a privacy tool. In NoScript's security model, you either trust the site's interaction with the CAPTCHA domain or you don't, one allowance is all malicious activity would need. And anyway, if your concern is being tracked by the site hosting the CAPTCHA, you probably want to default-block more than just active content from that site - i.e. you want to block more than NoScript can block.

Could you please clarify why you think contextual permissions are insufficient for your case?

[pjk]

This is not possible

That's all you needed to say, instead of all the editorializing that followed.

Neither security nor privacy is a zero-sum game. There are ways to improve both of them which do not make you "100% secure" nor "100% private" yet are still demonstrably useful. And that's all I'm trying to do here. I do a variety of content-blocking, NS is only one part of that. (Not that it has any bearing on simply answering my question about whether this technical functionality is available or not, which you answered in the first 2% of your reply. Thanks for that part.)

...and would go against the design of NoScript.

NoScript is a security tool, not a privacy tool. In NoScript's security model, you either trust the site's interaction with the CAPTCHA domain or you don't, one allowance is all malicious activity would need. And anyway, if your concern is being tracked by the site hosting the CAPTCHA, you probably want to default-block more than just active content from that site - i.e. you want to block more than NoScript can block.

Could you please clarify why you think contextual permissions are insufficient for your case?

[barbaz]

This is not possible

That's all you needed to say,

Ok, if that's all there is to be said, then marking this thread Closed. Thanks for letting us know.

instead of all the editorializing that followed.

Neither security nor privacy is a zero-sum game. There are ways to improve both of them which do not make you "100% secure" nor "100% private" yet are still demonstrably useful. And that's all I'm trying to do here. I do a variety of content-blocking, NS is only one part of that.

not constructive.

(Not that it has any bearing on simply answering my question about whether this technical functionality is available or not, which you answered in the first 2% of your reply. Thanks for that part.)

That's all you needed to say. In future, please limit your approach to steering conversations away from unwanted directions to this part only. Thanks.