InformAction Forums

I wish to allow large swarths of domains but am not having any luck with using standard wildcards.

For instance using "*" or "?" has no functionality.

I have decided just to allow scripts from a domain extention as a last resort.

So how would I allow all from a domain with an extension like ".me"?

So I would like to allow say google.me but not google.com as a example.

Sorry I have no idea what you're talking about, and your last sentence accurately describes the most basic normal NoScript functionality - just set google.me to Trusted and set google.com to Default

Could you please be more specific and detailed about what you would like to do? What specifically would you ideally achieve here, i.e. not last resort?

barbaz wrote: ↑Sun May 14, 2023 5:12 pm Sorry I have no idea what you're talking about, and your last sentence accurately describes the most basic normal NoScript functionality - just set google.me to Trusted and set google.com to Default

Could you please be more specific and detailed about what you would like to do? What specifically would you ideally achieve here, i.e. not last resort?

No, Every .me domain, "*.me".

It's possible: NoScript Options > Per-site Permissions, manually add "me" (without the quotes) and set it to TRUSTED

But this is not safe - compare to https://classic.noscript.net/faq#qa1_11: here you're not trusting a specific entity, there's no telling what you are trusting as anyone can register a domain with .me TLD.

Thanks, its janky and will allow things t slip through but I guess its the best I can do.

did not work.

DummDumm wrote: ↑Tue May 16, 2023 10:02 pm did not work.

Yes it does, I tested it before posting.

Maybe missing something here, but you seem to still be focusing on this -

DummDumm wrote: ↑Sun May 14, 2023 4:55 pm I have decided just to allow scripts from a domain extention as a last resort.

(emphasis mine)

So, again,

barbaz wrote: ↑Sun May 14, 2023 5:12 pm What specifically would you ideally achieve here, i.e. not last resort?

https://mywiki.wooledge.org/XyProblem

barbaz wrote: ↑Tue May 16, 2023 11:30 pm

DummDumm wrote: ↑Tue May 16, 2023 10:02 pm did not work.

Yes it does, I tested it before posting.

I just tested it and it is still blocking that domain, possibly because I am using a early version on a portable depreciated browser.

barbaz wrote: ↑Sun May 14, 2023 5:12 pm Maybe missing something here, but you seem to still be focusing on this -

DummDumm wrote: ↑Sun May 14, 2023 4:55 pm I have decided just to allow scripts from a domain extension as a last resort.

(emphasis mine)

So, again,

barbaz wrote: ↑Sun May 14, 2023 5:12 pm What specifically would you ideally achieve here, i.e. not last resort?

I would like to allow scripts from a specific domain that fit a specific criteria.

In other words I want to allow 1.me through 50.me domain names but not 51.me or 100.me yet allow 101.me through 150.me and so on in no particular order.

DummDumm wrote: ↑Wed May 17, 2023 12:22 am I want to allow 1.me through 50.me domain names but not 51.me or 100.me yet allow 101.me through 150.me and so on in no particular order.

If you know the maximum number of these, one option might be to use an external program to programatically generate the list of allowed domains, then paste that into NoScript Options > Advanced > Debug, in the "trusted" list there. Make sure the pasted entries are in the same format as the existing entries, and watch for potential errors involving missing or trailing comma.

Another possibility might be to consider uBlock Origin custom static filters instead of NoScript for this task.

(A historical note: this would've used to be achievable in NoScript using ABE, but ABE has not yet come back to NoScript Webext.)