InformAction Forums

You're welcome! https://i.psyche.me/thumbsup_right.gif Yes. As long as it shows green/allowed in uBlock Origin logger, you can safely ignore it and not touch it. If you do need site-specific dynamic rules to keep it green/allowed, I would exceptionally use allow for this instead of noop, to ensure ...

Thanks for your reply! I'm thankful for it. Is the "TypeError: Failed to fetch" from when you click the arrow on the far right of the entry in the uBlock Origin logger? Yes, that's right. The reason NoScript uses [ff00::]/... URLs for its internal requests is because those URLs are invalid...

As long as NoScript is what blocked these requests and caused them to fail to fetch, this is not a problem. This is an implementation detail of NoScript due to limitations of WebExtensions APIs. NoScript makes and then blocks these requests as a means of sending itself needed information in time. I...

Noscript shows up in the dynamic filter list of uBlock Origin as [ff00::] and the UBO logs show a lot entries like this: Logger output: +0 en.wikipedia.org 3 get xhr https://[ff00::]/nscl/common/SyncMessage/request.json?id=6c79033d-596c-4017-ae97-d22fab6c6053%3Ade205c92-cae4-44c5-bfba-340a1f5254cf +...

@Giorgio Maone
Thank you for clarifying! I'm glad you answered my questions.

Quoting the mandatory permission justification note I provided to the Chrome Store editors on submission: Using the debugger API is the only way to reliably inject scripts into workers, especially service workers, on Chrome: https://github.com/hackademix/nscl/blob/main/service/patchWorkers.js On Fi...