Why is Privacy Badger blocking Duolingo?
Since the site revision, I’ve had to disable Privacy Badger to use Duolingo on the desktop. Could you please look into this? I rely on Privacy Badger as part of my security suite on the web, and I’m uncomfortable disabling it just to use this site… Why is Duolingo triggering Privacy Badger anyway? Are you using tracking cookies, or sketchy scripts?
I’ve had to disable Privacy Badger to use Duolingo on the desktop. [...] I’m uncomfortable disabling it just to use this site…
Privacy Badger doesn't have a whitelist?
I don't know Privacy Badger but most applications/extensions blocking things do have a whitelist exactly for cases like yours: to not have to disable it only for one website.
Why is Duolingo triggering Privacy Badger anyway? Are you using tracking cookies, or sketchy scripts?
Just to let you know that only staff could answer and forums being "for the users BY the users", don't expect too much to have an official answer (even if it could happen if you are very lucky).
Yes, to clarify, I’ve got the site working again by whitelisting Duolingo under Privacy Badger’s Options, but that’s just a more convenient way of disabling the extension on a per site basis. You’re still going unprotected on this domain. :|
I’ve never had to whitelist a domain to regain functionality on a site before, so it’s worrying that I have to do it for Duolingo. What’s going on to trigger the extension?
Posting here because I already tried posting on the Duolingo subreddit with no official response (also primarily for users, though sometimes vonahn pops his head in and he said the staff lurks on the sub.) If there’s a more effective way of communicating with the devs please let me know.
If there’s a more effective way of communicating with the devs please let me know.
To communicate as in a "both way" discussion, no.
But as in a "one-way" (=you say something directly to them), yes: the "Bug Report" form is the way to send a message to staff (but don't expect an answer).
It’s the Electronic Frontier Foundation, and I’ve opened an issue on their GitHub page here:
Let’s see which devs reply first. :þ
I got frustrated trying to determine which domains were causing the issue and wound up just uninstalling the extension.
I then reinstalled, and since the tracking domain list was wiped out, Duo is working again for me now.
As you browse, Privacy Badger repopulates the list, but I’m crossing my fingers that this go around Duo won’t get caught in the crossfire. Or if it does, my blocklist won’t be so long that it’ll be easier to figure out which domain is the culprit. I’ll post again if I’m able to narrow down the issue further.
You’re welcome. :) Sorry for going so long without an update.
To sum up for anyone else experiencing a conflict between Duo and Privacy Badger—you have two options:
Go through your list of blocked domains and turn them off and on one by one until you ID which one’s at fault.
The nuclear option. Uninstall and reinstall. This will kill your whole list, but it will get Duo working again. Privacy Badger will rebuild on its own.