11–20 of 120 posts
> I’m not sure whether that is because Mozilla consider it unsafe, unpractical, or don’t want to commit to maintain the feature in future releases. I imagine it was implemented for the container tabs.
I guess trackers will just ask websites to route analytics traffic through their own infrastructure. Would it be enough for example.com to setup a dns alias pointing tracking.example.com to tracking.com?
(To be clear, I think this is a good thing)
I guess trackers will just ask websites to route analytics traffic through their own infrastructure. Would it be enough for example.com to setup a dns alias pointing tracking.example.com to tracking.com?
I've been running at home and at work with first-party isolation enabled for a few months now. Google login works fine for me, as does login with Google. It's broken a few internal tools, especially when people do things like hotlink across internal systems (which would have been broken at least some of the time for most people anyway, until they realise that to view _this_ page properly they need to log in over _the…
> I’m not sure whether that is because Mozilla consider it unsafe, unpractical, or don’t want to commit to maintain the feature in future releases. I imagine it was implemented for the container tabs.
The main problem I see with account containers — still — is that you can't say "this container can only have certain websites in it". For example, if you put reddit in a "social" container, but click on links to the stories, then you have all of your cookies and stuff polluting the social container.
I guess trackers will just ask websites to route analytics traffic through their own infrastructure. Would it be enough for example.com to setup a dns alias pointing tracking.example.com to tracking.com?
That breaks cross-domain tracking, though; before, cookies set on analytics.com (pulled on SiteA) would be sent back to them when pulled from SiteB. If you now use different domains on each site, that doesn't work. (To be clear, I think this is a good thing)
I've been running at home and at work with first-party isolation enabled for a few months now. Google login works fine for me, as does login with Google. It's broken a few internal tools, especially when people do things like hotlink across internal systems (which would have been broken at least some of the time for most people anyway, until they realise that to view _this_ page properly they need to log in over _the…
The best strategy is to not use Google however. It's not like you need to in 2018 anymore. There are better services for almost anything out there, although you may have to pay a few dollars for some of them. Well worth it since they are superior to Google. For email, Fastmail is king.
> I’m not sure whether that is because Mozilla consider it unsafe, unpractical, or don’t want to commit to maintain the feature in future releases. I imagine it was implemented for the container tabs.
I guess trackers will just ask websites to route analytics traffic through their own infrastructure. Would it be enough for example.com to setup a dns alias pointing tracking.example.com to tracking.com?
This is a possible work-around, but it adds a lot of complexity to get HTTPS and stuff worked-around. Either the third-party must handle HTTPS for their partners who setup CNAMEs, or the first-party must handle HTTPS and proxy the requests back to the third-party. It’s doable but it will significantly slow things down to the point where even shitty websites would consider it unacceptable.