> Can't this be "emulated" in Chromium by resolving the hostnames using DNS over HTTPS in JSON format?
> - This would require uBO to send browsing history information to a remote server, this is anti-uBO.
> - Chromium does not support non-blocking webRequest.onBeforeRequest listeners, so this can't work reliably when the result depends on an asynchronous operation such as a DNS lookup.
> - Chromium's webRequest.onBeforeRequest blocking ability is being deprecated with Manifest V3, so even without the above issues, this would be wasted development efforts.
I suspect (and suspected) that Ublock Origin may eventually be deprecated for Chrome after the V3 changes shipped the same way it was deprecated for Safari, although to the best of my knowledge Gorhill hasn't made any kind of official announcement about that -- so I want to be clear that it's purely conjecture on my end.
This thread reinforces that suspicion. I don't know if Gorhill has explicit plans to do anything with Chrome, but I suspect that in the future it will become more and more annoying to support the browser.
I also previously made a prediction[1] that within 2 years, Firefox would have clearly better tracker-blocking extensions than Chrome (65% likelyhood). This is roughly in line with what I would expect to see with that prediction -- a few rare fringe-case scenarios that creators can quickly address in Firefox, but that require more extensive work and conversations around Chrome. If this kind of issue becomes more common in the future, then I'll feel more confident about that prediction.
One possibly good outcome would be if Chrome's embrace of V3 is the catalyst that causes Firefox usage to shoot up again. By most measures, around 40% of users use ad blockers.
I would be surprised if uBlock Origin continues to be published/available for Chrome at all in its current form. In order to comply with the new restrictions Google are placing on it, it would have to be severely neutered. They are not giving uBO an option to continue support. Any post-Manifest V3 ad blocker would essentially be a different product.
> Can't this be "emulated" in Chromium by resolving the hostnames using DNS over HTTPS in JSON format?
> - This would require uBO to send browsing history information to a remote server, this is anti-uBO.
> - Chromium does not support non-blocking webRequest.onBeforeRequest listeners, so this can't work reliably when the result depends on an asynchronous operation such as a DNS lookup.
> - Chromium's webRequest.onBeforeRequest blocking ability is being deprecated with Manifest V3, so even without the above issues, this would be wasted development efforts.
I suspect (and suspected) that Ublock Origin may eventually be deprecated for Chrome after the V3 changes shipped the same way it was deprecated for Safari, although to the best of my knowledge Gorhill hasn't made any kind of official announcement about that -- so I want to be clear that it's purely conjecture on my end.
This thread reinforces that suspicion. I don't know if Gorhill has explicit plans to do anything with Chrome, but I suspect that in the future it will become more and more annoying to support the browser.
I also previously made a prediction[1] that within 2 years, Firefox would have clearly better tracker-blocking extensions than Chrome (65% likelyhood). This is roughly in line with what I would expect to see with that prediction -- a few rare fringe-case scenarios that creators can quickly address in Firefox, but that require more extensive work and conversations around Chrome. If this kind of issue becomes more common in the future, then I'll feel more confident about that prediction.
[0]: https://github.com/uBlockOrigin/uBlock-issues/issues/780#iss...
[1]: https://news.ycombinator.com/item?id=21506330