Cannot figure out how to get NS 10 to act like NS 5 re ads

[MyNameHere]

I've skimmed through many of the posts about the new UI, but I haven't seen anything that addresses my question.

I know NoScript is not marketed as an ad blocker, but it certainly used to cause a lot of ads not to appear.

There are several webpages that I visit every day. Before FF Quantum (using NoScript 5), I was only seeing a few ads here and there.

Now, with FF Quantum and NoScript 10.1.2, I started seeing a lot more ads, some of them obscuring the material I wanted to look at. So I knew there was a difference.

I went through the new NoScript UI and turned everything to "Default," so it showed the circle/slash icon. It made no difference.

I then went through the NoScript UI and switched everything to Untrusted. Now the ads are blocked.

Based on what I read in some posts, I don't understand why Default (circle/slash) is different from Untrusted (circle/slash). Why, when the default showed the circle/slash on all domains, did it start blocking more scripts when I explicitly set everything to Untrusted?

Also, the fact that I had to change the settings to get behavior like I had in NoScript 5 suggests that NoScript 10 is not using my old NoScript 5 settings--and/or the "Default" setting isn't working right.

????

Thanks!

[Guest]

I've skimmed through many of the posts about the new UI, but I haven't seen anything that addresses my question.

I know NoScript is not marketed as an ad blocker, but it certainly used to cause a lot of ads not to appear.

There are several webpages that I visit every day. Before FF Quantum (using NoScript 5), I was only seeing a few ads here and there.

Now, with FF Quantum and NoScript 10.1.2, I started seeing a lot more ads, some of them obscuring the material I wanted to look at. So I knew there was a difference.

I went through the new NoScript UI and turned everything to "Default," so it showed the circle/slash icon. It made no difference.

I then went through the NoScript UI and switched everything to Untrusted. Now the ads are blocked.

Based on what I read in some posts, I don't understand why Default (circle/slash) is different from Untrusted (circle/slash). Why, when the default showed the circle/slash on all domains, did it start blocking more scripts when I explicitly set everything to Untrusted?

Also, the fact that I had to change the settings to get behavior like I had in NoScript 5 suggests that NoScript 10 is not using my old NoScript 5 settings--and/or the "Default" setting isn't working right.

????

Thanks!

Click on "default" remove all checkmarks -> win.

You can click on all the presets and configure them. Where there way only a "yes no" in NS5, now there are specifics of what types of scripts specifically.
If the default setting allows some scripts, pages IN the default group will run those scripts.

Accordingly if you disallow certain things in the "trusted" preset, even sites IN the trusted group will not run that content.

[MyNameHere]

Thanks for the explanation. Please bear with me if I don't understand right away.

Maybe I have a glimmer here.

Do you mean that "Default" is one setting that applies to every domain? So if I uncheck all the boxes under Default for one domain, then all the boxes will be unchecked for every domain that is set to Default? That is, it doesn't matter which "Default" button I click, the checkmarks I change will change for all Default domains?

[Pansa]

Thanks for the explanation. Please bear with me if I don't understand right away.

Maybe I have a glimmer here.

Do you mean that "Default" is one setting that applies to every domain? So if I uncheck all the boxes under Default for one domain, then all the boxes will be unchecked for every domain that is set to Default? That is, it doesn't matter which "Default" button I click, the checkmarks I change will change for all Default domains?

It applies to every domain that is not in any other group. If there isn't a rule for it, what you defined as default behaviour for pages you haven't decided on, yet, applies.
Likewise the "trusted" settings. If you set something to "trusted" all trusted addresses behave like you configured trusted pages to behave.
That's why the 4th group is named "custom". That one creates a custom ruleset for that address alone.

you can go to the options and click the "debug" button at the bottom, that shows you how the config file looks like.

[MyNameHere]

It applies to every domain that is not in any other group. If there isn't a rule for it, what you defined as default behaviour for pages you haven't decided on, yet, applies.
Likewise the "trusted" settings. If you set something to "trusted" all trusted addresses behave like you configured trusted pages to behave.
That's why the 4th group is named "custom". That one creates a custom ruleset for that address alone.

you can go to the options and click the "debug" button at the bottom, that shows you how the config file looks like.

I believe that is kind of what I said (certainly is what I meant), but it illustrates how difficult it is to explain how the new NoScript works, and how well users are doing at deducing how it works. Obviously, what we need is a good, clearly written "user manual," probably written by a user because I think we now know enough to do that, and I'm sure Giorgio has other things to do.

On the other hand, maybe the UI or functionality will change. Personally, I think the UI is not intuitive, especially in two regards:
1. The "Default" icon is the circle/slash. I realize this is the NoScript icon, but it also looks like it means things are blocked. Seems like a default button should have some other kind of icon.
2. You pick any of the Default, Trusted, or Untrusted buttons to change the behavior of those buttons for all the domains that are set to that status. I think it would be better to have a separate line that you use to set the global (really, these are the default) checkmarks for each of those buttons, then the only thing the buttons on a domain would do is apply the global (default) list of things to allow or disallow for that button. And the Custom button would do what it does now.

But I'm impressed at what Giorgio has managed to produce in such short order.

[Pansa]

Considering that the addon is a one man job, having to deal with Mozilla removing the ability to do it the old way from under him...

It's not that it is objectively unintuitive, really. It is mostly unintuitive from the perspective of NS5 user.

Not gonna lie, it took me a bit of trying around till I realised that the buttons meant applying presets, but you can see that quickly wondering why page 2 now runs scripts and has scripts enabled in it's default, even though you only changed something for page 1. And that was when clicking something in custom changed what was shown in default (which was a bug).

But it IS more in line with how most other security programs deal with these things.
You set "groups" and put members into groups, so that that groups rules apply.

I believe that is kind of what I said (certainly is what I meant)

I wasn't really sure, so I wrote it in a way that makes it look as obvious as I could. Once you don't try to force "how it was before" on it, it IS very much what it says.
Except for the odd (read buggy) behaviour, for something put together in a short time the interface is quite internally consistent by saying what it does.

Looking at the "debug" stream in the options also helps a lot to understand what is done.