I have a specific container for my secondary Twitter account
I have a Twitter container defined in containerise
When I want to get to my secondary account, I open a new tab in the specific container for this account and go to twitter.com with it. However, since the URL matches twitter.com, it reopens the tab in the Twitter container, which has local storage, cookies, etc. for my primary account. This makes it impossible for me to access my secondary account.
It would be nice if containerise could (possibly as an opt-in option) check whether the new tab is already in a container, and if so, don't do anything.
go2null
commented
4 years ago
My setup for e.g. Twitter would be:
When I want to get to my secondary account, I open a new tab in the specific container for this account and go to twitter.com with it. However, since the URL matches twitter.com, it reopens the tab in the Twitter container, which has local storage, cookies, etc. for my primary account. This makes it impossible for me to access my secondary account.
It would be nice if containerise could (possibly as an opt-in option) check whether the new tab is already in a container, and if so, don't do anything.