Live data from Hacker News

Facebook Container for Firefox

mozilla.org

331–340 of 406 posts

Re: Facebook Container for Firefox

#331
post #262
post #231

Earlier quoted context omitted.

Ever encountered Google ReCaptcha when you've turned off third party cookies or while in incognito/private mode? It's a nightmare, even if you're logged into a Google account. You can be shown upto 7-8 challenges, painfully slow loading images and Google's insistence that they encountered malicious traffic from your IP when attempting to use the audio version. What's even worse is they track your mouse movements and…

The optimist in me thinks that if browsers started to disallow third party cookies, ReCaptcha might have to adapt to the change and make it easier to solve if third party cookies are blocked. After all, if they didn't, they'd risk website owners moving away from ReCaptcha because visitors could no longer interact with the site. The pessimist in me thinks that if a browser were to disallow third party cookies, users m…

I don't think it has so much to do with reCAPTCHA as much as it has to do with Cloudflare and website owners themselves. Most reCAPTCHA challenges come in the form of Cloudflare challenge passage pages. Website owners have 5 options to choose from regarding challenges:[1]

— Essentially off: Challenges only the most grievous offenders

— Low: Challenges only the most threatening visitors

— Medium: Challenges both moderate threat visitors and the most threatening visitors

— High: Challenges all visitors that have exhibited threatening behavior within the last 14 days

— I’m Under Attack!: Should only be used if your website is under a DDoS attack (Visitors will receive an interstitial page while we analyze their traffic and behavior to make sure they are a legitimate human visitor trying to access your website)

I think a lot of companies set it to "High" and forget about it, not realizing that it's ruining the experience for a lot of users.

[1]: https://www.cloudflare.com/a/firewall/ebelinski.com#security...

Re: Facebook Container for Firefox

#332
post #324
post #262

Earlier quoted context omitted.

The optimist in me thinks that if browsers started to disallow third party cookies, ReCaptcha might have to adapt to the change and make it easier to solve if third party cookies are blocked. After all, if they didn't, they'd risk website owners moving away from ReCaptcha because visitors could no longer interact with the site. The pessimist in me thinks that if a browser were to disallow third party cookies, users m…

> The optimist in me thinks that if browsers started to disallow third party cookies, ReCaptcha might have to adapt to the change and make it easier to solve if third party cookies are blocked. That needs to bring everybody to the same table, Firefox will not do that alone and Google Chrome is not there for nothing. Basically, Google must accept the proposal of disabling third-party cookies by default which will effe…

Chrome already has a "Block third-party cookies" feature in Privacy and security > Content settings > Cookies.

Kinda hard to find though.

Re: Facebook Container for Firefox

#333

Heck yeah, I've been dreaming of this for a while. Or really, something that can work on _any_ website you configure it to work on, not just fb. Or specifically, I'd love one that worked for google search (not neccesarily all google products, which would be hard, but one which let me search without being able to tie me to my other internet use including other google products).

Checkout Ghostery. It does a pretty good job with blocking trackers of any type. Ghostery is owned by a company that is backed by Mozilla, and claims to not share any data with third parties.

Re: Facebook Container for Firefox

#334
post #243

Earlier quoted context omitted.

The security model of the internet is whack. Javascript should be opt-in, especially from 3rd party sources. "This website wants/requires javascript for an enhanced viewing experience [allow/deny]". Instead not only will any stock browser gladly run anything thrown at it, it will also accept any cookies and now run WebGL code, trigger DRM engines and various other things. All that because the engineers who wrote the…

> a turing complete language with access to such a large API surface (from the DOM to the GPU to threads to a lot of the browser state) could be successfully sandboxed. I wonder why you say that. I concede that web has evolved from no-security in the 90s, when random applets and ActiveX controls were 1-click away from rooting your machine, through faulty security in 2000s, where stack smashing IE was a hobby of mine,…

>Which do work, sandbox evasion zero days have become very rare and remote execution has largely ceased to be an infection vector against the masses.

I consider that the widespread fingerprinting and user tracking is a form of sandbox evasion but I agree that it goes way beyond JS. The only identifying info that ought to be sent to some website by default is your IP address since it's necessary to actually send you back the data. Having the size of my view port, the version of my browser and OS, the type of video codecs I support and other shenanigans shouldn't leave my browser without my consent. The problem is that I can easily spoof most of my browser's info but JS makes it almost impossible to sanitize everything.

>The problem with 3rd party tracking is not technological, the web was deliberately engineered to work in this manner. The browsers work exactly as specified, and that specification is the problem

How is that not a complete contradiction? I'm not saying it's a bug, I know very well it's just a huge dump of features that keeps pouring in year after year. I'm just saying that web standards are the embodiment of "we were so preoccupied with whether or not we could that we didn't stop to think if we should".

IMO there are broadly two different use cases for the web currently: Web applications like Google Docs on one hand and glorified PDF reader for mostly static content like HN, internet forums, news websites, Wikipedia etc... on the other. Web Apps are the part that require this ridiculous complexity to expose rich content. That's the stuff you'd use Java applets, XUL, Flash or ActiveX for in the past. Those apps could be whitelisted on a site-by-site basis in the same way that you install an app on your smartphone for instance. You know that you expose yourself to bugs and privacy leakages but you know what you're in for.

99% of the websites I browse everyday don't expose any functionality that ought to require any form of interactive scripting or advanced features beyond displaying text and images (and maybe video). Yet my browser will gladly let them access all these advanced APIs by default, load custom fonts, let them run code on my GPU, make 3rd party requests, mine cryptocurrencies... That's just ridiculous.

The safest code is code that doesn't run.

>When I'm thinking like this is usually a sign of age

Come on, we're not old, we're wise! At least I hope so...

Re: Facebook Container for Firefox

#335
I normally avoid posting on threads like this, because there's more pile-on then there is coherent discussion, but I think there are some things missed here, and I want to elevate the discussion.

Let's take a step back for a moment from the fact that this is extremely one-sided, since there are many sites used all over the web which have a view on most of your browsing traffic, like Google Analytics (try and pry that from the cold, dead hands of administrators), to reddit, to other ad networks. I'll assume that the reader would just respond that we should do this for all sites.

Think a bit about the generalized business model of contracting out to third-party vendors. When you go the supermarket, it's very likely that the cash registers came from IBM (at least in the US). When you go to a restaurant, your payments are likely to be handled by Authorize.net (not to mention the credit networks), when you go to a hotel, the wifi is handled by some third-party company.

In each of these cases, there is a valuable service being provided to a company, and any service that has a large enough market penetration has access to a large amount of information about you. Third-party vendor relationships are not going to go away.

So what does this mean for the net? What effect will this have on the world? In the best case for anyone who thinks this is a good idea, it won't catch on, doesn't go mainstream, and a small amount of invisibility is granted to the few users who adopt this. But what happens if this were to become the default way the web works? Think about the wrench/security XKCD ( https://xkcd.com/538/ ). If browsers started doing this, than the companies who depend on these services will just find other solutions. Already, many sites use url redirectors in order to accomplish this (think: Google Search), if we try to prevent redirects, then you break the web.

Okay, nuclear option, we decide to break the web, and require all users to manually confirm before doing redirects. There will be sites concerned enough about the drops in traffic that would be caused by forcing redirects that they'll stop using them. Does that mean this practice will stop?

Of course not! The next step is out-of-band network requests. You request data from a site, they ping the third-party, no muss, no fuss, and you're never the wiser. Well, what happens in that case? Suddenly, you go from a situation where companies are using third-party services via the browser, where the end user's interface to the third-party is entirely secured from the company receiving the service, to a world where all of this information is proxied the third party, meaning that instead of less companies being able to track you, suddenly more companies are able to track you.

I for one, hope that this does not catch on. Not because I care one way or the other about the tracking (I think there are better solutions) but because I think this is an effort that will hurt both the web, and eventually users.

My thoughts on this: I find this akin to state surveillance. It's inevitable. The 'solution' to state surveillance is not hoodies and masks, but instead sousveillance (which means granting distributed surveillance powers to the masses, like way a large number of police issues came to light). Put the power in the hands of the people. How does this apply to web traffic? Same thing, instead of having traffic available to a few companies, make it scattershot, and make sure everyone has access. Surfing the web? Make browsers overfetch. DNS lookup for the letter p? grab everything from park to porn to production. That way, there is no loss of power

Re: Facebook Container for Firefox

#336
post #235

I have a similar need for Google. I have two gmail accounts. One is to preserve my privacy. But I can only open one at the time. That's acceptable since I forward mails. But then, everything I do at Google is tracked and associated with this opened gmail account. Once we are connected to Google, we are kind of logged in Google. They can track everything we do, even searches. The problem I'm facing is that I can't kee…

Why not use different browsers, like chrome and firefox, or, purely within firefox, different browser profiles?

Or, purely within the same Firefox profile, different containers? (I recognize that that's coming back to square one.)

Re: Facebook Container for Firefox

#337
post #6

Earlier quoted context omitted.

It's got Facebook in the name to ride the hate wave? I'm so glad Mozilla hired a Marketing team... /s

IIRC, this was just one engineer's side project to take their existing container tech, which might be too 'advanced' for most users, and make a one-off addon that more users might be interested in. Do you think that Mozilla's marketing of Firefox as more privacy focused is a bad thing?

> Do you think that Mozilla's marketing of Firefox as more privacy focused is a bad thing?

Not at all. This just strikes me as desperation, jumping on the hate train against Facebook because it's easy. Instead I'd like to see them actually develop their container functionality into a mainstream feature for the browser that might gain enough attention to make people start asking why Chrome, Safari, or Edge don't do the same.

I could see it very easily existing somewhere between the "New Window" and "New Private Window" menu options. They'd just need to rebrand it as something other than "containers" for the masses to understand it. "Private Window" would have been good but unfortunately that's been taken, in hindsight they should have gone with something that more clearly convey's the "burned after reading" forgetful nature of the private window because I think private conveys secret/isolated without the self destruction that comes with a Private/Incognito window..

People understand the Private/Incognito window, it wouldn't be hard to explain that a container window exists somewhere between a regular window and Private/Incognito. They could also easily surface or suggest sites you might want to containerize.

Re: Facebook Container for Firefox

#338
post #312

Earlier quoted context omitted.

Google didn't elect Trump

Yeah, the American people elected Trump in an extremely rare case of the public taking back the election from corporate behemoths. But let's pretend that Google hasn't had enormous sway over the White House and hasn't been rubbing shoulders with Obama and other Democrats [1][2][3][4]. Let's also ignore the fact that much of Silicon Valley publicly supported Hillary and opposed Trump, with big outspoken critics includ…

This is off-topic, and your idea of how Trump got elected is not the only — or even one of the popular — view.

Closer to the topic: what Facebook enabled was far more effective targeting, by agents not authorized by the targets, on a massive scale. That's a lot different than the "bunch of Russians locked away in some computer lab single-handedly elected" rhetoric.

Re: Facebook Container for Firefox

#339
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…

We ran a breakage study near the end of last year. First-Party Isolation (FPI) did have the highest breakage scores: ~18-19% of users reported problems with it, and 9-10% of FPI users disabled the study. Those are low relative numbers, but at entire-market scale, they are big absolute numbers. :/ https://blog.mozilla.org/data/2018/01/26/improving-privacy-w...

It would be great if we could have "FPI on by default with whitelist".

I think the stats are iffy because a lot of the breakages are things I would want broken.

Re: Facebook Container for Firefox

#340
post #77

Earlier quoted context omitted.

If they wanted to they could associate them other ways by just looking at the IP address and/or browser fingerprinting.

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.
Post reply on HN