Earlier quoted context omitted.
Mozilla released the extension "Facebook Container", which is great, but that's only one of the FANG companies notorious for invading privacy. Where is the "Google Container" extension from Mozilla? There exists such an extension but it's by a third party, not by Mozilla. It would be nice to see it from Mozilla since I trust them more than I trust some random extension developer; I can feel confident in recommending…
Those container extensions are just the "Firefox Multi-Account Containers" extension developed by Mozilla with some default settings for Facebook and Google. https://github.com/mozilla/multi-account-containers
Firefox to Block All 3rd Party Trackers by Default
111–120 of 190 posts
Re: Firefox to Block All 3rd Party Trackers by Default
#112Earlier quoted context omitted.
How can first-party cookies used to track users across multiple properties?
You send tracking events to your analytics/tracking partner from your backend instead of from the browser and they combine the cookie ids.
Re: Firefox to Block All 3rd Party Trackers by Default
#113Re: Firefox to Block All 3rd Party Trackers by Default
#114My work laptop is a very fast upper end macbook and I can somewhat reliably run Firefox on that. My personal laptop is an older macbook pro retina model and whenever I use firefox on that it gets incredibly slow and from time to time the computer just freezes for 20-40 seconds. So, sadly, I can't use firefox on that. At one point someone on HN posted a link to the bug report on mozilla's bug tracker about this issue…
Re: Firefox to Block All 3rd Party Trackers by Default
#115Re: Firefox to Block All 3rd Party Trackers by Default
#116One thing mentioned on the responses that might be really concerning is the fact that this will mean that for a lot of analytics it will look like firefox usage is close to zero. No usage data, devs caring less about firefox, users having more problems when using firefox, less users using firefox, less users having 3rd party trackers blocked, chrome monopoly growing.
Re: Firefox to Block All 3rd Party Trackers by Default
#117Earlier quoted context omitted.
You send tracking events to your analytics/tracking partner from your backend instead of from the browser and they combine the cookie ids.
The next step is that they will let third-parties inject javascript from the backend. At that point all is lost and the web will die a horrible death.
Re: Firefox to Block All 3rd Party Trackers by Default
#118Earlier quoted context omitted.
You send tracking events to your analytics/tracking partner from your backend instead of from the browser and they combine the cookie ids.
The next step is that they will let third-parties inject javascript from the backend. At that point all is lost and the web will die a horrible death.
It's not death anyway; it's just that blockers will have to adjust to blocking bits of third party content.
Re: Firefox to Block All 3rd Party Trackers by Default
#119Earlier quoted context omitted.
I don't believe that many users are blocking first-party cookies. Source: I'm a web analyst managing large sites and can see how many visitors block all cookies. It's minimal. Also blocking first-party cookies requires a degree of tech-savviness and it prevents many websites from working properly.
To add with that the parent comment said, I do as well, in two ways: - IE prompts me if I want to block cookies on a website, so unless I trust it, I block by default. - I have an extension on Firefox that is "Cookie Autodelete", so I visit a site and unless I whitelist it, all cookies will be deleted when I leave. I wondering if you are not seeing blocked cookie because of the second one. I'm not blocking it, but as…
Re: Firefox to Block All 3rd Party Trackers by Default
#120Firefox's Container's approach has been quite interesting to use, but if a suggestion could get out to the Firefox team, I would advise improved streamlining of workflow for the extension, including with sync and returning browser setup, and for organizing and setting up new containers (configuring them to always open for a domain, putting them in folders).
Yeah the UX of Multi-Account Containers is awful. The number of steps the user is required to follow to make a website always open in a particular container is absurd. 1) Create a new container 2) Open a new tab with that container 3) Open the website in that container 4) Check "Always open in [container name]" 5) Open a new tab and load that page again. 6) Click "Remember my decision" 7) Click "Open in [container na…
This commonly called the paradox of choice. Satisfaction is often higher when choosing from a limited set of good options than choosing from a large set of options with varying quality.
(YMMV, it is also used as an excuse for being inflexible, or for forcing bad options on users a.l.a. a false dilemma, and to be honest I'm not sure how to tell the difference as an outsider)