There's a balance between breaking the web and being as strict as possible. Saying we fully allow Facebook tracking isn't right , but we admittedly need more strict-mode like settings for privacy conscious users.
We do block Facebook at least as good as uBlock origin with EasyPrivacy. The referenced code is in a separate component which does the same as Disconnect blocking.
We're taking this seriously internally and we'll iterate on where we are to improve the situation. We're looking at if we can polyfill a local JS resource instead for example as one option if it doesn't make further requests.
a better solution for what, i wonder
Also I just realized that is an archived repo that isn't used any more.
I took a quick look through the newer repos and couldn't find any kind of hard coded whitelist like that.
Am I missing something?
I'm trying to figure out if the code is still active case, but this is a quite recent ticket (after the release of the Chromium-based edition, and updated 4 days ago)
The whitelist is in both versions
It is still whitelisted in current.
> // Temporary whitelist until we find a better solution
This post is sensationalist, flagged.
Can you substantiate this? Because that would be extremely relevant to the conversation. Making statements with absolutely no context just seems sensationalistic.