Page MenuHomePhabricator

uBlock blocks EventLogging
Closed, DeclinedPublic

Description

uBlock prevents EventLogging from working due to the EasyPrivacy filter (which seems to be enabled by default; also used on an opt-in basis by AdBlock) containing ||wikipedia.org/beacon/.

uBlock allegedly has some 15M users and AdBlock / AdBlock Plus a further 140M so the effect is probably nontrivial. Would it be worth reaching out and seeing if they are willing to make the filter opt-in (given that we have have strict privacy policies, don't use the collected data to display ads and don't keep it for long)?

Event Timeline

Restricted Application added a subscriber: Aklapper. · View Herald Transcript

This was discussed back in December 2014, see the thread starting with https://lists.wikimedia.org/pipermail/analytics/2014-December/002864.html

At the time the consensus was that this was ok (https://lists.wikimedia.org/pipermail/analytics/2014-December/002892.html), but I think that was considering that EasyPrivacy was opt-in on AdBlock (Plus?), but I can confirm uBlock enables it by default. My personal opinion is that this is fine, and if users want to use a tool that increases their privacy, we should respect that.

Milimetric subscribed.

If there's any disagreement with Lego's thoughts, please re-open, but I agree.

I think most people use ad blockers to prevent ads, and maybe to prevent ad companies from tracking them, not to prevent the websites they use from collecting the data they need to improve their services, and users actively opting into minimizing tracking should be respected, it's unfortunate when that gets bundled together with ad blocking, probably without the user being aware of the details.

Anyway I don't plan to do any outreach on this myself so no objection to closing.

is there a way to whitelist eventlogging here? I know we tried that before with adblock with not much success

Either reaching out to the EasyPrivacy authors or to the uBlock authors and asking their advice, given that we don't share personal data and have fairly high standards in how we use it. (The first is less likely to be useful, EasyPrivacy does exactly what it says it does: EasyPrivacy is an optional supplementary filter list that completely removes all forms of tracking from the internet, including web bugs, tracking scripts and information collectors, thereby protecting your personal data)

Maybe the whole thing is not worth the effort, I don't know how much we care. We could also just create our own whitelist so Wikimedia developers have a one-click install option do make sure they are not affected (I filed this task after losing a fair bit of time debugging why the EL patch I have just deployed doesn't work in my in-browser testing).

We really did try and ping people several times about blocking *pageview* (which catches our pageview-api). We submitted a patch, I think Kaldari even knew some devs on there and tried to hook us up, but it never got anywhere. They were skeptical of us, and stayed skeptical despite us explaining our stance on privacy. Sorry to be pessimistic, but I think any attempt to fix this will just get lost in the noise of the world.