Skip to content
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

Suggestion: Easy disabling of FB container on a per-website basis #568

Closed
fortyfive60 opened this issue Jan 12, 2020 · 1 comment
Closed

Comments

@fortyfive60
Copy link

I've actually got a couple suggestions...

  1. Consider renaming to Social Media Container. I know it's longer but now that it blocks instagram as well, I do think it's nice that it clarifies it a bit. I know I'm less technical than 99% of people on here but also am definitely above average compared to the world in general. I never thought to click on the tiny button on the bottom that reveals that instagram is blocked too. I got confused because I honestly thought it was only facebook. But I wondered for a while (particularly trying to stream stuff) why there were select few sites that just didn't seem to work on FF and was stuck using Chrome (bleh). And that brings me to...

  2. I think there needs to be a simple way of disabling the container functions on a per-website basis easily by clicking a button similar to the way you can easily click on the shield and click the "off" switch on tracking protection. This is helpful when you're viewing a page with a lot of embedded instagram and/or facebook links and you actually do want to see the photos on that website.

Sorry for wall of text. Let me know if this function is already there and I'm just confused. I would have thought turning off the tracking protections would be enough to disable FB container stuff, but still cant see embeds after refresh.

@maxxcrawford
Copy link
Collaborator

We're considering a settings panel in a future release to include options like allowing Instagram embedded posts

Note that Facebook and Instagram share tracking information with each other so we don't expect to by default not block Instagram.

We have been discussing internally also updating the add-on description to better highlight that this add-on blocks more than just Facebook, so we appreciate the feedback on that end.

Marking this as a duplicate of #402 and #370

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants