A lot of the other ad blocking extensions are malicious and collude with the advertising industry through some kind of whitelist program. Their license might also not be permissive enough to allow this.
> Why not include NoScript + Containers by default?
NoScript requires lots of manual intervention, uBlock Origin with the default lists is still seamless and rarely causes breakage thus very little need for manual intervention.
I am not convinced that Containers does anything at all. Browser fingerprinting & IP address tracking defeats it very easily.
> And some UserAgent Switch capability
This is absolutely needed and I'm baffled this isn't offered natively, though this would be less for privacy and more as a developer tool.
> And more fine grained cookie storage options (currently available via add-ons), et cetera?
I find the whole craze around cookies overblown. Your IP address is a relatively persistent cookie you can't clear. The only way is to prevent requests made to the malicious actors to begin with, with some kind of blacklist like what uBlock Origin provides.
> how to discriminate what to include, what not
I'd argue that if your mission is to make the web better and protect people's privacy then including a proper ad blocker is a no brainer.
> does it do any good
That is up to discussion with the add-on author (the author of UBO has repeatedly declined donations and seems to be doing his efforts out of passion and/or hatred for ads, so he should be onboard), but otherwise, the secret sauce isn't really the blocker per-se but the blocklists such as EasyList/Fanboy's lists, and Mozilla has enough resources to reimplement a compatible client from scratch if needed.
> how to deal with edge cases
Contribute back to the lists to fix any edge-cases by adjusting an over-reaching blocking rule, and offer an easy way for users to temporarily disable the blocking on a per-site basis.
> I find the whole craze around cookies overblown. Your IP address is a relatively persistent cookie you can't clear. The only way is to prevent requests made to the malicious actors to begin with, with some kind of blacklist like what uBlock Origin provides.
In my personal opinion, no one should be connecting to the internet in this day and age without using a VPN service wherever possible.
A lot of the other ad blocking extensions are malicious and collude with the advertising industry through some kind of whitelist program. Their license might also not be permissive enough to allow this.
> Why not include NoScript + Containers by default?
NoScript requires lots of manual intervention, uBlock Origin with the default lists is still seamless and rarely causes breakage thus very little need for manual intervention.
I am not convinced that Containers does anything at all. Browser fingerprinting & IP address tracking defeats it very easily.
> And some UserAgent Switch capability
This is absolutely needed and I'm baffled this isn't offered natively, though this would be less for privacy and more as a developer tool.
> And more fine grained cookie storage options (currently available via add-ons), et cetera?
I find the whole craze around cookies overblown. Your IP address is a relatively persistent cookie you can't clear. The only way is to prevent requests made to the malicious actors to begin with, with some kind of blacklist like what uBlock Origin provides.
> how to discriminate what to include, what not
I'd argue that if your mission is to make the web better and protect people's privacy then including a proper ad blocker is a no brainer.
> does it do any good
That is up to discussion with the add-on author (the author of UBO has repeatedly declined donations and seems to be doing his efforts out of passion and/or hatred for ads, so he should be onboard), but otherwise, the secret sauce isn't really the blocker per-se but the blocklists such as EasyList/Fanboy's lists, and Mozilla has enough resources to reimplement a compatible client from scratch if needed.
> how to deal with edge cases
Contribute back to the lists to fix any edge-cases by adjusting an over-reaching blocking rule, and offer an easy way for users to temporarily disable the blocking on a per-site basis.