InformAction Forums

Unfortunately WebExtensions can't read about:config prefs either.

If there's anything for NoScript to do here, it would likely need to be based on its existing means to detect Tor Browser. (I'm not sure how that detection works.)

I fully agree with barbaz on both points. [...] 2) I prefer the old icon as well. Apparently I didn't make myself clear about the icon. I wasn't expressing a preference about the icon. I'm not sure if I have a preference at this stage. I was just wondering if the specific change I pointed out was a...

I don't feel that I can reasonably make many comments without having the new UI in front of me in a functional NoScript. But a couple things really jumped out at me: 1) Even as an experienced NoScript user, I have NO idea what "Allow affiliated scripts" means. Intuitively, and ignoring a lot of cont...

This is thread for anon (== without annoying registration) ABE bug reports? No, it's only for the specific bug report of the OP. Posting anywhere in this ABE section of the forum, including creating new threads, does not require registration. Guest, I split your post to https://forums.informaction....

Sorry but there is currently no way for a WebExtension to read environment variables.

adrelanos wrote: ↑

Thu Sep 19, 2019 11:27 am

Related:
https://trac.torproject.org/projects/tor/ticket/31798

This sounds like a Tor Browser issue, reporting to them was the right place.

Are you running Firefox in some kind of sandbox, e.g. firejail?

Laurens wrote: ↑

Mon Sep 16, 2019 3:12 pm

Please, please please consider getting a real UI person to design

already happening - viewtopic.php?f=10&t=25643

That said following the suggested fix which changes about:config and forbiding disabling the tool bar has a strange side effect. When you work (yes work) to open the Noscript menu, web site addresses and status symbol (red green lock) are not displayed instead a blank section (polar bear in snow st...

therube wrote: ↑

Wed Sep 11, 2019 3:53 pm

google-unveils-dns-over-https-doh-plan-mozillas-faces-criticism

How does Chrome determine the user's DNS provider? And will that method be able to detect and respect a setup like I have, which is not conventionally used for filtering?

Since Sandboxie has been discussed a fair amount in this forum, thought this might be worth noting here - https://www.ghacks.net/2019/09/10/sandb ... en-source/

Try this - javascript:%28%66%75%6E%63%74%69%6F%6E%28%29%7B%66%6F%72%28%6C%65%74%20%61%20%6F%66%20%64%6F%63%75%6D%65%6E%74%2E%67%65%74%45%6C%65%6D%65%6E%74%73%42%79%54%61%67%4E%61%6D%65%28%27%61%27%29%29%7B%6C%65%74%20%75%3D%6E%65%77%20%55%52%4C%28%61%2E%68%72%65%66%2C%77%69%6E%64%6F%77%2E%6C%6F%63%6...

What would be the point of such bookmarklet? Isn't this just going to break websites, like it would this forum?

Looks like Mozilla is trying to address my big concerns about this - While we would like to encourage everyone to use DoH, we also recognize that there are a few circumstances in which DoH can be undesirable, namely: Networks that have implemented some sort of filtering via the default DNS resolver....