Google is finally killing uBlock Origin in Chrome for good(protonprivacy.substack.com) |
Google is finally killing uBlock Origin in Chrome for good(protonprivacy.substack.com) |
No issues with UBO on Edge 149 (stable) and it's still available on the Edge Add-ons (it was featured by Microsoft, funnily enough, a few months back):
https://microsoftedge.microsoft.com/addons/detail/ublock-ori...
Did I miss something? Microsoft's official statement is that "The Microsoft Edge team is currently in the process of updating this MV3 migration timeline". Now, they've been working on that timeline since at least May 2025, so maybe with Chromium 150 / 151, they'll make it more concrete?
https://learn.microsoft.com/en-us/microsoft-edge/extensions/...
I also expect Google to be a bad actor and do everything in its power to pointlessly refactor the chromium codebase specifically to make keeping MV2 alive as painful as possible.
http://infolab.stanford.edu/~backrub/google.html
"The Anatomy of a Large-Scale Hypertextual Web Search Engine"
-> "Appendix A: Advertising and Mixed Motives"
-> "The goals of the advertising business model do not always correspond to providing quality search to users."
Not browser specific, but they understood the problem well.
They threw the book at Microsoft for the Windows and Office monopoly of the 90s and 2000s, but in comparison did absolutely nothing to Google over their search and browser monopoly of the 2010s -today, especially given how influential and important the web is today compared to desktop operating systems which just became launchers for the web browser.
No browser can load these ads.
I've considered doing the pi-hole thing for family, but doesn't ublock etc do a lot of fixing to make sure pages aren't broken when ads are missing?
Or does pi-hole/your implementation do the same?
Consider the simplest possible case: I run ojford.com and take money from Acme Inc in exchange for displaying their advert. They send me acme-banner.jpg, and I serve it at /static/current-ad.jpg with an <img id="banner-ad" src="/static/current-ad.jpg"> in my header or whatever.
A DNS block covering the ad would block my whole site. Effective, but useless. (Unless you actually intend to boycott anyone who advertises.)
uBlock however can block the #banner-ad element. (Whether community-curated or by you specifying it yourself.)
More realistically this might be say YouTube or googleusercontent subdomains that serve both ads and 'real' content.