-
Notifications
You must be signed in to change notification settings - Fork 176
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
CFR Recommends FBC on WhatsApp website but WhatsApp is not included in default domain list. #652
Comments
@WhyNotHugo On any site not inside the Facebook Container, all Facebook-specific resources (including Facebook analytics and their SDK) are blocked. Technically, Facebook isn't tracking users here, outside of any data sharing outside of Facebook front-end resources. However, this extension has changed a lot since #182. I'll reopen that issue and have the team revisit it. Thanks! |
Duplicate of #558 |
This is not a duplicate of #558. #558 discusses eventually adding whatsapp to the URL list. My issue here, is that Firefox suggest that I install this extension now when I visit web.whatsapp.com. However, the extension does not include whatsapp on the list. You're essentially recommending the extension to an audience for whom the extension does nothing. The issue here is that It would be prudent to stop suggesting this extension to whatsapp user until #558 has been discussed, resolved and deployed. |
Fair point. I'm re-opening and making the issue name constructive. Thanks! |
Related to #558 |
Linux aphrodite 5.7.0-arch1-1 #1 SMP PREEMPT Mon, 01 Jun 2020 22:54:03 +0000 x86_64 GNU/Linux
Steps to reproduce
web.whatsapp.com
web.whatsapp.com
and re open it.Actual behavior
Expected behavior
Notes
I see that #182 removed support for whatsapp web due to other issues. If that's the case, then don't prompt me to download the facebook container when visiting web.whatsapp.com -- if you don't do anything for whatsapp users, then don't recommend the addon to those users, it does nothing for them and adds a lot of confusion.
I'm fairly technical and figured out it wasn't working (and narrowed it down to #182), but it might install a false sense of additional privacy to users for whom it's doing nothing.
The real issue here isn't that we can still be tracked on web.whatsapp, but rather that users are being led to believe that it the contrary.
The text was updated successfully, but these errors were encountered: