Hacker Newsnew | past | comments | ask | show | jobs | submitlogin



thanks for the clarification, I haven't looked at add-ons for other browsers for quite a while, and at the time I remember discussions about adblock not being possible to be done anywhere else like in FF due to the add-on model, glad to see this does not seem to be the case anymore


well, one could frame it differently

  - adblock pioneered on firefox
  - deemed useful
  - chrome implements necessary APIs
  - can finally be implemented on chrome too
For that to work you first need a permissive enviornment where the addon developers can think outside the box and do things not covered by the standard APIs.

Just like you can, as ultima ratio, write kernel modules if your system has no other way to support whatever you need to be do.


I think the big difference is being able to pre-emptively block/modify requests, vs. changing what is displayed after the fact.


that was what I thought as well, however I went to the umatrix github page and if you look at the top it links this page[1] that discusses how umatrix needs permission to disable prefetching so no network connections are made for blocked sites, which seems to imply it can do the pre-emptive blocking as opposed to just hiding of elements.

I am wondering though now if I am mixing things up in my brain and the issues were with safari add-ons as opposed to chrome/chromium: there is no umatrix for safari[2] that I can see, ublock seems available but not ublock origin, but I am not sure if ublock on safari just hides or actually pre-emptively blocks.

[1] https://github.com/gorhill/uMatrix/releases/tag/0.9.1.2

[2] https://github.com/gorhill/uMatrix/issues/96


> umatrix needs permission to disable prefetching so no network connections are made for blocked sites

Disabling pre-fetching is to prevent a TCP connection to be established at all, and this is something that needs to be also dealt with in Firefox -- it's not just a Chromium thing. This ensures that no TCP connection is established before it has been decided whether a network request must be blocked or not.

Chromium used to not be able to support the pre-emptive blocking of network requests, but that has been remediated in 2012 with its webRequest API in Chrome 17.

[1] https://developer.chrome.com/extensions/webRequest


Which brings us back to the point that one cannot develop any new, unforseen kind of extension unless you either have the option to directly interface with the browser's internals or somehow get that API included in the browser.


thanks for clarifying and thanks a lot for continuing to work on your great add-ons!




Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: