What does HackerNews think of disconnect-tracking-protecti?

Right, but Firefox’s enhanced tracking protection mode blocks Statcounter’s JS (see https://github.com/disconnectme/disconnect-tracking-protecti... which is where, I believe, Mozilla source their ETP blocklist from). Given the userbase for Firefox these days, I’d be very surprised if Statcounter is even vaguely accurate.
Yes, this is what I meant. Facebook properties are allowed to load resources from Facebook domains. https://github.com/disconnectme/disconnect-tracking-protecti...
If statcounter is in the list of blocked trackers, and trackers are blocked by default, then assuming there is a huge list of untracked users is only fair. Because it would be everyone not specifically disabling the tracking protection, which no one does. Statcounter would only count outdated FF installations that also do not use an adblocker (3% seems high for that, but not absurdly high).

But I'm not certain that this is the case. https://disconnect.me/trackerprotection claims to link to lists that show which trackers are only identified and which are identified and blocked, but those links just go to https://github.com/disconnectme/disconnect-tracking-protecti..., where I do not see such a distinction being made.

> One day I woke up to a chart showing browser market share of FF at around 4%, which surprised me - as I thought many people would understand the implications and directions.

Its certainly low, but I also think FF usage is under reported due to built-in tracker blocking. For reference, FF uses the level 1 disconnect.me block list, which blocks StatCounter scrips from loading on 3rd party sites [1].

[1] https://github.com/disconnectme/disconnect-tracking-protecti...

Firefox is willing to add specific technical countermeasures to specific domains that are attempting to bypass the tracking policy: "If a party attempts to circumvent the technical solutions we’ve outlined in this policy, we may without notice add additional restrictions to that party to prevent the circumvention." It seems they use the list of tracking domains at https://github.com/disconnectme/disconnect-tracking-protecti... .

(Safari, as far as I can tell, tries to avoid having site-specific policies, so maybe the question is "What is Repixel doing that is exploiting a security bug in Safari, and how can Safari fix it?")

> this would block pretty much all the major analytics

The list [1], which includes many APIs, also breaks hundreds of websites [2] that access those APIs

[1] https://github.com/disconnectme/disconnect-tracking-protecti...

[2] https://bugzilla.mozilla.org/show_bug.cgi?id=1101005

It looks as if in the next several months Firefox will become all but invisible from most 3rd party trackers as Firefox ”will strip cookies and block storage access from third-party tracking content, based on lists of tracking domains by Disconnect.” [1]

The full list of trackers that will be blocked by default is substantial. [2]

1 https://blog.mozilla.org/futurereleases/2019/02/20/enhanced-...

2 https://github.com/disconnectme/disconnect-tracking-protecti...