Would like to start out by saying that this is a HUGE add to nuNoScript, and I'm *so* glad that it's finally on the table. You folks are bluddy geniuses!!
So, I just thought I'd put up a thread here to ask if there were any key differences (perhaps under the hood) to how nuABE differs to the old, text based, ABE, that had us building incomprehensible (!) text rules like the ones at the end of this post. Asking at a high level, of course, for dummies like me .
I also appreciate that there's a description of nuABE on the site, now ... & This thread is more me asking (hopefully for the benefit of others) to see how this handles/does things differently, and if there's things that we should ensure that we do differently as a result with this.
For example, questions that quickly jump into my head (I'm not literally asking these for response, just examples):
- Is the "Enable these capabilities when top page matches" broadly equivalent to "Deny" or is it more like "Deny INC" / "Deny INCLUSION" in old ABE, or does it work slightly differently to either option?
- Regarding #1, though, does it handling that differently, and should we do anything differently as a result?
- Similarly, if for example, I'm setting lets say ampproject.org for independent.co.uk, then later, also set it for hackademix.net. Would this affect other sites?
- Is an improved editing of these more granular options on the map for the GUI's future?
Just to show that I'm using them as examples, I've done my best to try to explain/understand:
- I believe it's broadly a Deny INC/INCLUSION. Since we can clearly pick and choose *various* elements that INC handled as a whole in the 'custom' options there. I may obviously be missing stuff here, as I don't understand the underlying technology at play.
- No idea.
- Based on the below export excerpt it's done on a per parent site basis, then *within* the scope of that domain it has fields for each parent domain that uses it, and their functionality level inherently.
- No idea, obvs.
Code: Select all
"https://cdn.jsdelivr.net": {
"capabilities": [
"script",
"object",
"media",
"frame",
"font",
"webgl",
"fetch",
"other",
"ping",
"lan"
],
"contextual": {
"§:cclonline.com": {
"capabilities": [
"script",
"object",
"media",
"frame",
"font",
"webgl"
],
"temp": false
},
"§:meshcomputers.com": {
"capabilities": [
"script",
"object",
"media",
"frame",
"font",
"webgl"
],
"temp": false
}
},
"temp": false
}
---
Partially Blocking Specific Domains
So, I'll phrase using recaptcha as an easy example, since it's now bloody everywhere. However, I might wish to separate the 'Accept'/'Anonymize'/'Sandbox' listings from Google's other services.
If I wanted to ensure that the Google-owned recaptcha service only worked on certain sites, I needed to also preface my main google rule.
So, I would have (not my actual rule) this Google rule:
Code: Select all
### google.com containment rule
Site ^(.*)google\.com((?!recaptcha).)*$ ^(.*)gstatic\.com((?!recaptcha).)*$ .blogspot.com .gmail.com
Accept from .google.com .gstatic.com .google.co.uk .gstatic.net .googleapis.com .youtube.com .ytimg.com insertSomeSiteYouWantThatUsesSiteSearch.com
Anonymize from .startpage.com
Deny INC
Code: Select all
#fucking recaptcha
#https://www.google.com/recaptcha/api.js
Site .recaptcha.com .recaptcha.net .google.com/recaptcha/* .gstatic.com/recaptcha/* https://www.google.com/recaptcha/api2/
Accept from .recaptcha.com .recaptcha.net .google.com/recaptcha .gstatic.com/recaptcha ajax.googleapis.com
Anonymize from .pornhub.com .yahoo.com .fightcade.com
Deny INC
(I appreciate that I may have some of the above wrong, and happily accept corrections! Like, I'm pretty sure that 'Anonymize' doesn't work, but worry that Sandbox from .pornhub.com would potentially group it in with yahoo and fightcade allowing big G to associate my use away from obvious IP stuff).
If no-one could follow that, then put basically: I am pretty sure that I'm essentially specifically calling out the recaptcha service for a very separate set of allowed sites. As opposed to the domains that I allow Google's to access otherwise. Doing so by *restricting* the Google rule (^(.*)google\.com((?!recaptcha).)*$) from applying itself to recaptcha.
---
Either way again, supreme congrats on getting this going in nuNoScript, it's a HUGE undertaking and I'm sure everyone is super happy and proud of you lovely lot!
And again, I'm happy to break out my question to a separate thread to be more specifically answered if you like.
Best
MMM
((( incidentally the linked changelog - https://classic.noscript.net/abe/changelog - appears to be blank, and removing the 'classic' redirects to the abe page )))