Login
You're viewing the discuss.systems public feed.
  • Sep 7, 2023, 11:48 PM

    @dalias @ricci OR maybe I am confusing 2 things as the FAQ at support.mozilla.org/en-US/kb/c says "Are Firefox containers and Multi-account containers the same? Firefox Containers and Multi-Account Containers are complementary features that help you keep your online activities organized. While both options allow you to separate your browsing into different container tabs, the Firefox Containers feature allows you to always open new tabs in containers."

    💬 1🔄 0⭐ 0

Replies

  • Sep 8, 2023, 12:03 AM

    @pmevzek @ricci Multi-Account Containers sounds sketchy (integration with their VPN partner stuff) and like it does unwanted things (automatically switching to a container context based on which site you're loading, vs locking to a context and always opening links in that container context) that harm privacy instead of preserving it.

    💬 4🔄 0⭐ 0
  • 💬 1🔄 0⭐ 0
  • Sep 8, 2023, 12:07 AM

    @dalias @ricci I don't remember now why, but I had to install the extension, so anyway I live with it now. I do use the "automatically assign site X to container Y", avoids some errors, having a dozen or so containers. Anyway the logical followup would be not to have to do that and each tab/site in its own container by default, with only the possibility to "open it" to other sites/containers, but otherwise fully restricted by default.

    💬 0🔄 0⭐ 0
  • 💬 0🔄 0⭐ 0
  • 💬 2🔄 0⭐ 0
  • 💬 0🔄 0⭐ 0
  • 💬 0🔄 0⭐ 0
  • Sep 9, 2023, 10:13 AM

    @dalias
    There's also an unofficial extension called Temporary Containers which can, if you configure it that way, open any new site in a brand new container that will get removed a few minutes after you close last tab from that container.
    Yes, it can break spectacularly on sites that redirect between domains for authentication.
    @pmevzek @ricci

    💬 1🔄 0⭐ 0
  • Sep 17, 2023, 1:34 PM

    @viq @dalias @pmevzek @ricci

    Yes, redirected auth can be a pain but it can be fixed by using the "always open this domain in the same container" feature and have the auth site open in the target site container.

    Not the perfect isolation but good enough for most cases.

    The only thing that still requires me to disable temp-containers is for using paypal. But then again, it's a simple disable-pay-enable.

    💬 1🔄 0⭐ 0
  • 💬 2🔄 0⭐ 0
  • 💬 1🔄 0⭐ 0
  • 💬 1🔄 0⭐ 0
  • Sep 17, 2023, 7:40 PM

    @dalias
    Interesting, I'll need to have a look.
    With temporary containers if you open a site say by first opening new tab and then going there, or by clicking from "somewhere else", you'll end up in a new container, whereas to my understanding with first party isolate it will be "same session". Both of which may or may not be desirable 🤷
    @d00b @pmevzek @ricci

    💬 0🔄 0⭐ 0
  • Sep 18, 2023, 10:44 AM

    @dalias @viq @pmevzek @ricci

    Temp containers create a new session/tab every time I click on a URL whose base domain is different from the one in the address bar. First party isolation seems less restrictive (or not?).

    💬 1🔄 0⭐ 0
  • Sep 18, 2023, 10:49 AM

    @d00b @dalias @pmevzek @ricci
    New container, yes.
    But, say, you click on a link someone sent you in email, and you end up on reddit. And you click on a search result, and you end up on reddit. Do you want those two reddit tabs to share cookies etc, or not?
    Different people have different answers for that. For *me*, for *most* of my browsing, the answer is "no". But that's not necessarily true for everyone.

    💬 1🔄 0⭐ 0
  • Sep 18, 2023, 11:13 AM

    @viq @dalias @pmevzek @ricci

    Same for me: the answer is almost always NO and that's the cool thing about temp containers: it defaults to NO while still giving me the ability to decide otherwise.

    In the end, it's up to me to decide how trackable my sessions will be.

    💬 0🔄 0⭐ 0