"Privacy Badger automatically learns to block invisible trackers" may be confusing to some users

[sillyjaybird]

"Privacy Badger automatically learns to block invisible trackers" is still used to describe the extension at:

EFF FAQ [https://privacybadger.org/#How-is-Privacy-Badger-different-from-Disconnect%2c-Adblock-Plus%2c-Ghostery%2c-and-other-blocking-extensions]
[https://chrome.google.com/webstore/detail/privacy-badger/pkehgijcmpdhfbdbbnkijodmdjhbjlgp?]
[https://microsoftedge.microsoft.com/addons/detail/privacy-badger/mkejgcgkdlddbggjhhflekkondicpnop?hl=en-US]
[https://addons.mozilla.org/en-US/firefox/addon/privacy-badger17/]

Now that learning mode is disabled by default this only leads to confusion like issues #2781 #2782 . Clarifying descriptive language at these sites will create cohesion, clarity and help inform users.

[ghostwords]

Hello and welcome!

The thing is, Privacy Badger does still automatically learn to block invisible trackers. Unlike almost every other privacy tool out there, Privacy Badger still learns what to block based on how domains behave. No manually-maintained tracker lists needed or used.

The issues you linked to do not seem relevant to this discussion. Could you go more into what made you open this issue?

[sillyjaybird]

@ghostwords Thank you. I posted this issue with the intention of improving descriptive info, e.g. in FAQ, on web store pages, etc. for clarity and consistency. Indeed, auto-learning is still available but must be enabled by users who may not be tech savvy. Issues #2781 & #2782 appear to have been opened to clarify and assist users as well, and led to my opening of this issue. A proposed solution is simple editing of the pertinent descriptive info on FAQ and web store pages. That is all.

[ghostwords]

To be clear, "Privacy Badger automatically learns to block invisible trackers" is true regardless of whether you enable local learning or not. Privacy Badger learns automatically, period. If you leave local learning disabled, your Privacy Badger still learns automatically, just not on your computer.

[ghostwords]

I understand that you would like to help improve Privacy Badger's descriptions. Thank you!

However, I still don't understand where you are coming from. Could you talk more about why you think "Privacy Badger automatically learns to block invisible trackers" is confusing? You read that Privacy Badger no longer learns locally by default somewhere. Did you read our announcement article, or was it something else? Perhaps something on Reddit?

[ghostwords]

Also, I agree that we should update some of our FAQ entries to reflect Privacy Badger no longer learning locally by default.

We might also want to remind users that they should consider enabling local learning.

[sillyjaybird]

Yes, I read the announcement article, tech sites, forums, etc. and I understand that Privacy Badger still auto-learns via web crawler and that local learning may be enabled or not. _What may not presented clearly and readily to some users is the option to enable local learning (in the same way WebRTC leak protection is misunderstood by some and you advised removal in issue 2782*). _Maybe you don't see the similarity of these two issues, i.e. possible user confusion from poor descriptions or design, ignorance, etc. As this is my first time opening or commenting on an issue at GitHub, I should have clarified this in the title - which was evidenced by my clumsy attempts at editing it. You wrote in that issue:

…

This is an off-by-default, advanced user feature ... that persistently confuses users. ... It's too easy to misunderstand what this setting actually does. This setting does NOT hide your public IP. Additionally, we made a mistake by trying to shoehorn this setting into a checkbox. Some advanced users may want to set this setting to the strictest level, but the strictest setting can break all WebRTC applications unless the user configured a proxy...