3 ms·
Embrace, extend, extinguish. Oldest play in the Microsoft book. I sincerely think Microsoft can't be trusted.
by bediger4000 2y ago
Embrace, extend, extinguish. Oldest play in the Microsoft book.
I sincerely think Microsoft can't be trusted.
- zfg 2y agoThis play is actually in Google's book. Microsoft is going along for the ride.
- EdgeFanSan 2y agoLooks like this was a bug in Edge. I dont see this prompt anymore. Also, the pop-up message said Chrome and not Edge.
- TheCleric 2y agoIt is their original play. However I think this is just “Chrome is going to do this anyway and we’re not about to write custom code to work around it.”
- hirsin 2y agoThis. It's extremely expensive to keep core functionality like this in a fork. Every single surface that manifest v2 touches (js runtime, extension hosting, permissions, network, APIs, chrome even) that gets changed upstream has to be redone to account for v2. Every new system built into Chrome that only works with v3 has to be effectively back ported to v2. The only other option is to keep v2 in chromium itself and have Chrome disable it... While still paying the cost of supporting it in all new feature dev. There's no world where Microsoft spins up a new engineering team solely to deal with the extra cost of keeping v2 around. That said this sucks. I got my first internship on the Internet Explorer team by talking about how hard it was to install an ad blocker in IE, compared to Chrome.
- hulitu 2y ago> It's extremely expensive to keep core functionality like this in a fork Modularity in SW is still a challenge after 50 years of progress.
- out_of_protocol 2y agoNo one cares for specifically V2, it's just V3 is intentionally crippled. Just allow functionality required for more feature-rich extensions like uBO and everyone will forget V2 very fast. V3 does allow extensions to monitor and sell network data (no privacy improvements), but blocks modifications (no cutting out ads)
- pjmlp 2y agoActually this is Google's doing, you know the folks that do Chrome, that Chrome Edge builds upon. https://www.pcworld.com/article/2595287/ublock-origin-is-officially-dead-for-chrome-but-ad-blockers-live-on.html https://www.pcworld.com/article/2595287/ublock-origin-is-off... But by all means, keep the EEE story.
- greyadept 2y agoMicrosoft doesn't have to do this. The chromium-based Brave has committed to supporting uBlock Origin: https://x.com/brave/status/1725622768262128006 https://x.com/brave/status/1725622768262128006
- kernal 2y agoThey’ll cave eventually and walk it back if history is anything to go by.
- porridgeraisin 2y agoThey implement ublock origin compatible adblocking in the browser, not as an extension. Manifest v2/3 is irrelevant to brave's adblock capabilities.
- lmm 2y agoAnd we all know what a credible organisation they are.
- pjmlp 2y agoSure, lets see for how long they will keep their fork.
- bagacrap 2y agoI really doubt Brave will be able to support manifest v2 for long after chromium deletes that part of the codebase. Brave does not have the resources to maintain a fork in perpetuity. They are really just a reskin with a marketing team (privacy conscious individuals being the mark).