Earlier quoted context omitted.
How is it different/better from incognito mode ?
Incognito isn't as private as the name suggests. I was surprised one day to open a tab in Incognito and see the site I visited knew who I was. That's because I had logged in to a related site in a tab I'd forgotten about in another Incognito window. My assumption up to then was that each newly opened Incognito tab or window was it's own private session, but this turned out to be wrong - they all share state, as if yo…
Multi-Account Containers
151–160 of 254 posts
Re: Multi-Account Containers
#152Earlier quoted context omitted.
Is there a good native way now to set up url patterns (domain, sub domain, regex etc) to open in a specified container? I've been using a non add-on store addon for this.. and no idea why something basic like that would not be in the core or this add-on
I am not sure what you mean by non addon store addon. Containerise is on amo and supports glob and regex patterns. https://addons.mozilla.org/en-GB/firefox/addon/containerise/
Re: Multi-Account Containers
#153Re: Multi-Account Containers
#154I've used these for over a year. Where the experience falls short is when using OAuth flows where either the requestor or provider is in a different container. E.g. Slack (work) => Twitter (social media) => ~~broken~~ as the redirect doesn't go back to the (work) container. I can't think of a fix because any there is would break the privacy of containers.
In some cases though I do have to switch my default browser to Chrome, log in, then switch it back.
Re: Multi-Account Containers
#155Why don't we have complete main domain isolation as an option? It would work like containers, but they would be automatically created for each domain you visit. Go visit youtube.com and anything loaded from that page is in the same container. You'd have to log into each google property as the sites would be separated from one another, and there would probably be a need to merge these containers if say www.example.com…
This add-on has that functionality.
Did I miss something in the settings?
Re: Multi-Account Containers
#156This is so much more powerful than first party isolation in Chrome. Firefox is on the only browser with something like this. I love having multiple tabs open and logged into the same website with different accounts/cookies. I also use this in conjunction with Temporary Containers so every tab is a new container automatically. If I left-click a link it will navigate keeping the same container. If I control+click it wi…
Re: Multi-Account Containers
#157Coolest feature is per container socks5 support so each container can send traffic through a different socks 5 server. Any VPN offering socks5 on their gateways should work. I'm using IVPN which expose socks5 on each of their WireGuard servers - there is demo on their blog - https://www.ivpn.net/blog/socks5-proxies-app-based-vpn-tunne...
Re: Multi-Account Containers
#158Earlier quoted context omitted.
Yep, only thing it doesn't work well with for me it's teams web (because teams is so boneheaded in that you can't be logged in to two tenants at the same time). Osteen the container tab gets stuck in a reload loop and then the dropped icecream picture "Oops something went wrong".
Not even with two separate containers?
This is what it was like a while ago though, I haven't tested it recently because I haven't had a need to log in to other tenants anymore since I moved jobs.
Re: Multi-Account Containers
#159Re: Multi-Account Containers
#160Earlier quoted context omitted.
Tab Groups were better when they were baked into the browser. They were extremely buggy when the code was removed and moved into an extension. Not only often losing all of my tabs - but completely forgetting all of my tab groups altogether. Causing me to lose not only important data but also having to re-organize all my tabs into tab groups only to inevitably have to redo all the work next time FF decided it wanted t…
> Tab Groups were better when they were baked into the browser. They were extremely buggy when the code was removed and moved into an extension. Not only often losing all of my tabs - but completely forgetting all of my tab groups altogether. Causing me to lose not only important data but also having to re-organize all my tabs into tab groups only to inevitably have to redo all the work next time FF decided it wanted…
The release notes honestly weren't all that helpful - but looking over the Git repo, it looks like a lot of the major crashing/session restoration bugs were squashed in 2020-2021 and the backup functionality was improved enough to make backups more user friendly and somewhat more automated (aka: worth using and not 4 days out of date). There are still some flaws but those flaws come from the extension suffering the limitations of being a web extension - which is a tangentially related but another huge gripe of mine.
Now if only I could find a way to restore my context-menu tab switching - a feature lost when FireGestures was killed off. I didn't use any of the other gesture functionality at all - I only used the "[Popup] List All Tabs" feature which worked great with tab groups back in the day. (See: "Wheel Gestures" http://www.xuldev.org/firegestures/features.php)
E: (moments before I was about to post...)
Holy. Shit. Gesturefy recreated that functionality - and around the time I had given up on FF too. Back to Firefox I go! I had tried Foxy Gestures thinking it was the successor to FireGestures but I never gave Gesturefy a chance back then. In case I was bad at describing it, you can test it out yourself after setting it up in the settings: "[Popup] All Tabs" as a wheel gesture - it is an absolute game changer and I am SO GLAD I can go back to my circa-2013~2016 workflow after all these years. Only downside is continuing to scroll doesn't highlight tabs to change - so a small step back - wonder if it is even possible with how WE's are limited.