search

mozilla / contain-facebook

Facebook Container isolates your Facebook activity from the rest of your web activity in order to prevent Facebook from tracking you outside of the Facebook website via third party cookies.
Mozilla Public License 2.0
975 stars 176 forks source link

Alert the user when they have already assigned facebook to a Container #35

Open TanviHacks opened 6 years ago

TanviHacks commented 6 years ago

If we find that a user has already assigned facebook.com to a Container using Multi-Account Containers, alert the user that this addon won't work. With text something like:

Looks like you use Multi-Account Containers and have already assigned facebook.com to a Container. Since we do not want to interfere with your setup, Facebook Containers will not work to ensure that you don't visit any other sites in your Facebook Container. If you would like this additional protection, uninstall Facebook Containers, unassign facebook.com in the Multi-Account Container extension, and then reinstall Facebook Containers.

Copy needs some work.

Not sure what kind of UI we have the ability to create in an addon. An alert box? The UI doesn't need to be particularly fancy, since this is a one-time thing for a certain class of users that is savvy enough to have already assigned Facebook to a Container.

@ryanfeeley do you have ideas?

ryanfeeley commented 6 years ago

What are you detecting exactly? That they have Facebook history or cookies inside one or more containers? How can they remove Facebook from an existing container?

TanviHacks commented 6 years ago

We detect if facebook.com has already been assigned to a Container with the Multi-Account Containers addon. Multi-Account Containers has an API that we call into to see if facebook has already been assigned.

If it has, this addon does not do anything. That is the best way around this problem. The question is 1) do we message the user to tell them our addon isn't doing anything. 2) How do we send that message - what does the UI look like?