gorhill · HackerTrans

3 か月前議論

Best is to report the issue using the "Report an issue" in the popup panel while on Reddit site. There could be other issues causing this, for instance if you didn't grant uBOL the permission to inject scripts on the site. Depending on which browser/os the issue occurs, we should be able to narrow down potential causes.

gorhill

3 か月前議論

Reddit's sponsored posts are blocked by default in uBOL when using _optimal_ (default) or _complete_ mode.

gorhill

5 か月前議論

I never transferred the extension in the Chrome store. The Chrome store extension has always been the one from the repository I control, and I've had full control of it since when I created it back in June 2014.

gorhill

9 か月前議論

Those "adblock test" sites misinform people, they should never be used as they lead people to make bad decisions regarding their choice of content blockers.[1]

[1] https://bugzilla.mozilla.org/show_bug.cgi?id=1985170#c3

gorhill

10 か月前議論

When trying to diagnose performance or memory issues with a browser, always start with the installed and enabled extensions.

gorhill

11 か月前議論

> it claims to use zero CPU

There is no claim of "zero CPU". The claim is that the service worker wakes up only when necessary -- it is designed to be suspended by default from the ground up.

In Optimal and Complete modes, the content scripts will of course execute, without the service worker being unsuspended if no filtering occurs, but perform only the necessary work and bail out ASAP if not needed.

In Basic or "No filtering" modes, no content scripts are injected.

---

Edit: Sorry, I do say "uBOL itself does not consume CPU/memory resources while content blocking is ongoing". When I say "itself" I am referring to the service worker as seen in Chromium's Task Manager. The service worker isn't required for examples when navigating to `example.com` or here at `news.ycombinator.com`. All top content blockers I have looked at do require their service worker to execute, even for merely just switching between tabs. Some even use tricks to prevent their service worker to be suspended at all.

gorhill

11 か月前議論

Those webpages used to "test" blockers are frowned upon, see: https://x.com/gorhill/status/1583581072197312512

There are many reasons that sort of online tools are not able to reliably test a content blocker:

- Many content blockers are designed to fool pages to think no content blocker is installed

- Content blockers filter according to real, actual cases, not synthetic cases used in their tests

gorhill

昨年議論

> Doctor Feng, or similar, though I can't find

DirectorFeng: https://www.youtube.com/channel/UCbzzMQ1mNKjAaDwbELsVYcQ

gorhill

昨年議論

When you enable "Developer mode" in the "Extensions" page of your browser, you can open the developer tools for the extension by clicking the "service worker" link, and from there select the "Network" tab, you will be able all the network requests made by the extension from within its service worker.

gorhill

昨年議論

It's working fine on Youtube in Optimal mode. If you have still issue, you will have to go through self-diagnosing steps[1] to rule out all the myriad other ways you suffer such issues -- most commonly another extension is interfering negatively.

[1] https://github.com/uBlockOrigin/uAssets/issues/27415

gorhill

昨年議論

I randomly browsed the site with Firefox stable and I couldn't see any obvious malfunction. What exactly is not working? Is there a specific webpage where the malfunction can be seen?

gorhill

2 年前議論

No competent content blocker tests "ten thousand regexp matches" for each request URL to match, this is not how it works.

To simplify, and speaking from uBO's perspective, consider that nine distinct tokens can be extracted from the URL in the address bar for the current webpage:

  https
  news
  ycombinator
  com
  reply
  id
  41758007
  goto
  item%3Fid%3D41757178%2341758007

To match such URL against the tens of thousand of filters, there is only a need to lookup filters for these nine tokens, and for most of these tokens there won't be any filters to test, such that in the end for any given URL only a few to no filters will end up being tested, and the majority of these filters are not regex-based, they are just plain string matching.

This is the overall simplified explanation of how it really works, in reality it's a bit more complex because there are a lot of other optimizations on top of this.

There is a built-in benchmark tool in uBO, accessible through the dashboard, _Support_ pane, _More_ button, _SNFE: Benchmark_ button[1].

When running the benchmark against a set of 230,364 URLs, I get an average of 11-12 µs per request to perform a match test against the default filter lists in uBO.

* * *

[1] https://github.com/gorhill/uBlock/wiki/Advanced-settings#ben...

gorhill

7 年前議論

> Ublock origin (in advanced mode)

You can wholly block JavaScript in uBlock Origin without having to enable advanced mode, by using the per-site JavaScript master switch.[1]

* * *

[1] https://github.com/gorhill/uBlock/wiki/Per-site-switches#no-...

gorhill

8 年前議論

> in stead of stripped after the download (like with uBlock)

That's quite an erroneous statement, especially given how easy it is to verify.

You can see for yourself by using uBlock Origin along with your pi-hole: your pi-hole will see _less_ network requests with uBO (or any other similar blockers really).

Everything which is blocked by uBO will not be seen by your pi-hole, and this simple observation contradicts your statement.

gorhill

9 年前議論

> This article is all about Facebook, but I have also scaled back my use of other big services like Google

The issue is with whatever 3rd parties which are ubiquitous enough.

The difficulty is, how do we find which 3rd parties are ubiquitous enough so as to warrant that we take action against it?

This is why I wrote uBO-Scope[1], its whole purpose is to inform users of which 3rd parties out there are ubiquitous, according to their own browsing history, and according to which 3rd parties were allowed to connect on any given site.

The extension observes network traffic on all pages you visit and from the data it collects over time, and will inform you about which 3rd parties are in a position to collect how much of your browsing history using a per-base domain heatmap of privacy exposure.

It's a side-side-project, and hopefully I will find time again to further improve it. The whole motivation is that I want people to become aware of what is happening when they browse the net, and in the spirit of informed consent, to encourage them to take action to reduce their privacy exposure.

[1] https://github.com/gorhill/uBO-Scope#preamble

コメント