Facebook Container for Firefox • Hacker News Board

Re: Facebook Container for Firefox

#61

Post by loeg » Wed, Apr 18, 2018, 12:38 AM UTC

forapurpose wrote: post #48

07d046 wrote: post #27

I used Firefox's containers for about a day, and then I discovered the privacy.firstparty.isolate option (in about:config), which effectively gives every site its own container with no user effort. That, combined with Cookie AutoDelete, seems to work well.

Any problems? For example, CDNs are in different domains. Some ecommerce sites use payment services from other domains.

I've definitely run into problems with ecommerce sites (really just Tarsnap) and embedded iframes from 3rd party payment services, while using the Chrome equivalent of this Firefox setting.

Re: Facebook Container for Firefox

#62

Post by Kequc » Wed, Apr 18, 2018, 12:40 AM UTC

I would like to isolate every website I visit into a container, such that cookies or other tracking mechanisms are unable to be effective while on other pages.

Re: Facebook Container for Firefox

#63

Post by Operyl » Wed, Apr 18, 2018, 12:40 AM UTC

briandear wrote: post #57

Operyl wrote: post #26

> In addition, websites that allow you to create an account or log in using your Facebook credentials will generally not work properly. Because this extension is designed to separate Facebook use from use of other websites, this behavior is expected. As much as I love these kinds of things, this is going to break something for my less tech-y family. As such, I can't let them use this kind of thing.

Maybe you should can’t let them use Facebook logins?

They have existing apps that wouldn't let them do that. I'm not about to control my mother's choices.

Re: Facebook Container for Firefox

#64

Post by _jal » Wed, Apr 18, 2018, 12:40 AM UTC

narag wrote: post #31

We're going from cold war to all-in. Not just a privacy question. Reddit nags me every time I hit the front page, even returning from a story, asking me to log in. For most sites I need to create ublock filters to prevent pop-ups with useless "we use cookies", subscription requests, ads or social media bars that fills half the screen, etc. etc. etc. Every newspaper I read has decided that autostarting video and strea…

It is super rude, and "giving up" is the right answer - to annoying sites. Screw them.

The single nicest thing you can do for yourself after an ad blocker is to get Javascript under control. I personally am using JS Blocker, which takes too much effort, but allows you to selectively load JS. There are others - I like the control JS Blocker offers, but it is a bit annoying.

This is not without problems; there are sites that don't work/don't work well. I frankly don't care about most of them, so that's fine with me, and I leak much less data to the various panty-sniffers[1].

Life is much nicer when you take back control of what runs on your machine.

[1] I block FB, Google and several others' IP space, but the smaller adtech/government/who-knows surveillance shops are impossible to keep up with, and, well, defense-in-depth is the way to go.

Re: Facebook Container for Firefox

#65

Post by guelo » Wed, Apr 18, 2018, 12:42 AM UTC

forapurpose wrote: post #48

07d046 wrote: post #27

I used Firefox's containers for about a day, and then I discovered the privacy.firstparty.isolate option (in about:config), which effectively gives every site its own container with no user effort. That, combined with Cookie AutoDelete, seems to work well.

Any problems? For example, CDNs are in different domains. Some ecommerce sites use payment services from other domains.

Things will break like logging in with Google/Facebook/other OAuths that use popup window redirects, iframe services like Disqus or Facebook comments, Google's captcha will become more annoying, less local caching will happen which means slower browsing in general.

Re: Facebook Container for Firefox

#66

Post by minot » Wed, Apr 18, 2018, 12:43 AM UTC

07d046 wrote: post #27

I used Firefox's containers for about a day, and then I discovered the privacy.firstparty.isolate option (in about:config), which effectively gives every site its own container with no user effort. That, combined with Cookie AutoDelete, seems to work well.

My use case is multiple Google accounts. I can log in to multiple Google accounts at the same time in different containers and answer emails very easily.

Re: Facebook Container for Firefox

#67

Post by guelo » Wed, Apr 18, 2018, 12:43 AM UTC

chrischen wrote: post #59

07d046 wrote: post #27

I used Firefox's containers for about a day, and then I discovered the privacy.firstparty.isolate option (in about:config), which effectively gives every site its own container with no user effort. That, combined with Cookie AutoDelete, seems to work well.

Wouldn't setting your cookie settings to strict (block all third party cookies) do the same thing?

It's more thorough than just cookies including various caches and data stores.

Re: Facebook Container for Firefox

#68

Post by andai » Wed, Apr 18, 2018, 12:44 AM UTC

loeg wrote: post #61

forapurpose wrote: post #48

Earlier quoted context omitted.

Any problems? For example, CDNs are in different domains. Some ecommerce sites use payment services from other domains.

I've definitely run into problems with ecommerce sites (really just Tarsnap) and embedded iframes from 3rd party payment services, while using the Chrome equivalent of this Firefox setting.

How do you do this in Chrome?

Re: Facebook Container for Firefox

#69

Post by StavrosK » Wed, Apr 18, 2018, 12:56 AM UTC

07d046 wrote: post #27

I used Firefox's containers for about a day, and then I discovered the privacy.firstparty.isolate option (in about:config), which effectively gives every site its own container with no user effort. That, combined with Cookie AutoDelete, seems to work well.

Doesn't Privacy Badger do about the same, but more granular and breaking fewer things?

Re: Facebook Container for Firefox

#70

Post by Someone1234 » Wed, Apr 18, 2018, 1:00 AM UTC

minot wrote: post #66

07d046 wrote: post #27

I used Firefox's containers for about a day, and then I discovered the privacy.firstparty.isolate option (in about:config), which effectively gives every site its own container with no user effort. That, combined with Cookie AutoDelete, seems to work well.

My use case is multiple Google accounts. I can log in to multiple Google accounts at the same time in different containers and answer emails very easily.

You can be logged into multiple Google Accounts at the same time without the extension. Just click the little profile icon in the top right and click "Add Account."

I'm logged into four, including a Gapps account.