4 ms·
There is a clear and obvious path to implementing Manifest V3 in a way that best serves users overall and this path involves working with the uBlock Origin team
by zamadatix 6y ago
There is a clear and obvious path to implementing Manifest V3 in a way that best serves users overall and this path involves working with the uBlock Origin team/gorhill and the concerns they've brought up with the change. Until that happens I refuse to believe any train of thought that this is a user focused change and not a ad revenue focused change. To be clear that it has some benefit to users that can be pointed out does not make the change user focused in the same way putting a solar cellphone charger on a cargo ship doesn't make it environmentally friendly.
It'd be a different discussion if this was presented as an ad revenue focused change but it's presented as if it's user focus and the community is driving the direction of how it's implemented. Clearly this is not the case, in a conveniently true way, and it'd be such a simple thing to clear up. Even if the uBlock Origin team ends up saying "hmm, we really all got together and thought about it and there was nothing else to change that couldn't impact user privacy significantly" at least it removes the divide and controversy.
Throwing references from companies with shady practices that exclude Google ads from their blocking does nothing to show a willingness to work with developers on what's best for users, in fact it makes the situation look even more shady.
I don't know if gorhill reads HN but on the off chance he does thank you for your work.
- Groxx 6y agoThere's also the option of just adding declarativeNetRequest. Then 1) uBlock Origin and others keep working un-modified, 2) they could adopt declarativeNetRequest for cases where they're able (say as a pre-filter or if you only use those rules), and 3) blockers that only use declarativeNetRequest can exist. Let them all compete on performance-vs-features-vs-privacy. There's nothing about introducing a new API that requires removing an older one - this is a political change, not a technical one. It's hard to see it as anything but ad-revenue motivated.
- alooPotato 6y agoDo you think users would understand the difference and the privacy trade-off?
- Groxx 6y agoIn part that's an issue with their permission model and how they communicate it, and it's not done well now either. I'm pretty sure that people care at least a little in most cases, but the tradeoffs are far more complex than you can grasp easily so I'm not sure "privacy" is fundamentally a thing that can be provided while allowing anything except almost uselessly restricted extensions. So: mostly no, nor do I expect it to improve with manifest v3. Tracking/malicious extensions will just continue to request access to `*` and send their info via some other means, and users will continue to install them. This doesn't stop that or really change it at all.
- alooPotato 6y agoI think that shows that "just adding declarativeNetRequest" wouldn't really accomplish much? Developers would continue using the old API and users wouldn't hold them accountable because they wouldn't know the difference or what the tradeoffs hard. Not saying V3 is a perfect or even good solution but just thought the option you suggested doesn't seem like it would work.
- Groxx 6y agoIt lets developers opt into a less-sensitive and higher-performance API, losing flexibility as a tradeoff. That seems like a perfectly acceptable reason for an API to exist, and a reasonable tradeoff. Follow up with big angry warnings about extensions that use the less-safe APIs, and let users choose. As opposed to now, where all permissions are quite calmly displayed. "Half of all malicious extensions use this API, we strongly advise you to look for an alternative"[1] is very different than "x wants permission to modify requests". The failings of the current permissions system doesn't mean users are incapable of deciding. It means the current system doesn't work for users. Either it's unsolvable for the majority (unlikely IMO), or it's not matching what users need to know to decide. I thoroughly support making better APIs (declarativeNetRequest is plenty useful, and makes decent tradeoffs), but that doesn't have to be at the cost of other things, nor is some "make everything safe" dream the only option. [1]: https://blog.chromium.org/2019/06/web-request-and-declarative-net-request.html https://blog.chromium.org/2019/06/web-request-and-declarativ...
- vbezhenar 6y agoIt already added and works fine.