Yeah this basically sounds like it takes the temporary container add on that I think was folded into Firefox at some point recently and basically just does it behind the scenes now on a per domain basis
phoneymouse@lemmy.world 3 weeks ago
Does this make containers unnecessary? Or basically built in?
Jessica@discuss.tchncs.de 3 weeks ago
snaggen@programming.dev 3 weeks ago
It is making the tracking protection part of containers obsolete, this is basically that functionality but built in and default. The containers still let you have multiple cookie jars for the same site, so they are still useful if you have multiple accounts on a site.
MediaSensationalism@lemmy.world 3 weeks ago
FREEEDOOOOOOOOOOOM
altima_neo@lemmy.zip 3 weeks ago
A lot different. Containers act as a separate instance of Firefox. So any sites you visit within a container can see each other as if you were using a browser normally. The containers can’t see the stuff from other containers though. So you have to actively switch containers all the time to make it work right.
This keeps cookies locked to each page that needs cookies. So a lot stronger.
phoneymouse@lemmy.world 3 weeks ago
So what you’re saying is, each site gets its own container?
PeachMan@lemmy.world 3 weeks ago
I think there’s some confusion here. You’re talking about Multi-Account Containers, that person was talking about the Facebook Container. Both Firefox features with confusingly similar names.
Facebook Container is similar to this TCP feature, but focused on Facebook. Now, Firefox has rolled it out for ALL apps, which is awesome and SHOULD HAVE BEEN HOW COOKIES WORKED IN THE FIRST PLACE!
stephen01king@lemmy.zip 2 weeks ago
Isn’t there just a non-extension container feature, I can’t tell what’s the difference between that one and multi-account containers.