[justcommenting]

this is extremely important and difficult work, and i support you and your team in working toward these and related goals, including financially.

but as one example, the amount of person-hours that go into building a functional NoScript surrogate that can be used to block google analytics tracking without breaking the functionality of major websites is significant, and most 'ad blockers' either don't block the most common trackers because they've been paid off by advertisers (adblock plus) or only block one or a handful of many known means of tracking users (e.g. the last time i looked at disconnect.me, it didn't touch TLS-based identifiers like SessionID, tickets, etc. that Google is thought to use).

i think we have to move past some of the opacity/ambiguity that undermined previous attempts to reconcile the interests of users and advertisers, too. for example in the eyes of PrivacyBadger, an advertising company hosting jQuery or a font basically meant that my preferences about the same company tracking me, persistently, across most of the world's major websites could be trivially circumvented as long as that company could interpolate their server logs with other information. privacybadger probably still improved many users' privacy, but i think there's a lot of nuance that's extremely important to clarify as mozilla's work on this progresses.

it's a big fight, but an important one.