Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Facebook Container for Firefox

mozilla.org

Post reply on HN
Print view View original

341–350 of 406 posts

Re: Facebook Container for Firefox

#341

Post by pedroaraujo »

baq wrote: post #318
andrewaylett wrote: post #258

Earlier quoted context omitted.

It sounds like you're after Temporary Containers: https://github.com/stoically/temporary-containers That gets you a clean container every time you click the button. Very useful for development testing, too :).

what's the use case difference between that and porn mode browsing? i can't really tell when i should use one and the other.

The best feature (at least for me) is that you can whitelist some specific websites to always open in a new temporary container, without any extra effort, while leaving the rest of your websites like they are today.

For example, I have YouTube (and any other Google website) to always open on a temporary container but other sites like HN and Reddit are on a normal and permanent container.

Re: Facebook Container for Firefox

#343

Post by billysielu »

07d046 wrote: post #277
r3bl wrote: post #230

Earlier quoted context omitted.

In short: site breakage. We're so deep in this that a first party isolation would break almost every single website. In a cooperation with Tor, Mozilla actually ported the first-party isolation feature in mainstream Firefox (available in Nightly, don't know about stable), but since it would break almost every single website, there are no plans to turn it on by default. You can, of course, enable it yourself by turnin…

I've been using first party isolation for the last year or so, and I can't think of anything it's broken.

Good to know, I'm gonna try this starting now.

Using the extention: https://addons.mozilla.org/en-US/firefox/addon/first-party-i...

Re: Facebook Container for Firefox

#344

Post by billysielu »

amelius wrote: post #259
cherimoya wrote: post #234

Earlier quoted context omitted.

Some sites rely on multiple domains to work. E.g. open auth, cdns are usually a separate domain, a lot of big corporates create new domains for “microsites” when they want to do something new but are tied down by slow moving corporate practices (although the world would be a better place without microsites). Basically, you couldn’t do it without breaking a large part of the internet.

They could build a whitelist and distribute it with Firefox (?)

I agree FPI should be on by default and have a whitelist.

Re: Facebook Container for Firefox

#345

Post by billysielu »

yAnonymous wrote: post #272
Tepix wrote: post #220

Earlier quoted context omitted.

Indeed. Safari blocks 3rd party cookies by default, I see no reason why Firefox can't do the same. The fact that they don't is a direct contradiction to their claims that they care about user privacy. The only explanation I have is that they do not want to anger their long-time money sources Google and other advertisers.

I agree, but blocking third-party cookies does break a whole lot of sites. Apple can do this, because they have a limited yet consistent market share that mostly consists of their own customers. But Firefox? If they block third-party cookies and Chrome does not, they might just end up losing even more users.

A large percentage of things that break SHOULD BREAK. That's the whole point isn't it?

Re: Facebook Container for Firefox

#346

Post by billysielu »

cbr wrote: post #306
joosters wrote: post #303

Earlier quoted context omitted.

What sites are broken by Safari because of its default cookie options? I haven't encountered any.

Any site which iframes in another site where you're expected to be logged in. For example, Disqus comments, Facebook like buttons, Youtube embeds (which work, but show ads even if you've paid for no ads). There are also lots of one-off cases where developers split functionality across multiple domains in ways that were fine at the time but now get blocked. These are all fixable, unlike the iframing case, but it's sti…

We need to redefine 'break' into:

Breaks because it was abusing lack of FPI.

Breaks innocently.

Re: Facebook Container for Firefox

#347

Post by ocdtrekkie »

rtkwe wrote: post #340
ocdtrekkie wrote: post #123

Earlier quoted context omitted.

My thought is that they can certainly find good indicators that they're related, but that signing into them at the same time directly in their website confirms the relationship. Bear in mind, everything coming from say, a corporate network, won't be distinguishable by IP, and browser fingerprinting is likely less helpful in an environment with a hundred PCs running identical system images. Your home device may not li…

Even in a corporate network there's some plugin drift over time depending on job role especially for developers. And GP specifically has installed a container add-on which probably makes him/her fairly unique among all the corporate traffic coming from that IP/group of IPs.

Most good corporate environments should be controlling what plugins they allow users to install in their browsers. (For the few users we permit to use Chrome, for example, all extensions are disabled.)

But again, the issue is not your specific configuration (or GP's specific configuration), the point is that Google cannot assume same IP or browser fingerprint is a definitive association of identity, whereas signing in additional users in Google's app definitely does.

Re: Facebook Container for Firefox

#350

Post by kbenson »

infogulch wrote: post #145
kbenson wrote: post #71

Earlier quoted context omitted.

I actually have a few cases like this as well, but they are very common cases I encounter 20-30 times a day. I thought containers were clunky too until I went looking for bug reports for the functionality I wanted (always open domain in container) and found out I just wasn't using them right. I'm actually really impressed with how polished it is given the complexities it entails

Is there an official article/tutorial detailing how to use them and use cases with examples?

From searching I just found a Mozilla help page[1] that seems to have much of the useful info, along with some links to other articles.

Not sure of it or something similar was referenced at some point during the extension install process.

1: https://support.mozilla.org/en-US/kb/containers

Post reply on HN