firefox --no-remote --profile "$XDG_CACHE_HOME/firefox/home" --class="browser-home"
firefox --no-remote --profile "$XDG_CACHE_HOME/firefox/work" --class="browser-work"
firefox --no-remote --profile "$(mktemp -d)"
Opening a domain in a container, then other linked sites from that page, generally remains within the same containdr.
I use 1Password (most polished) and there's also Bitwarden (hosted, but open source) and others. And I use my password manager every day, so if there's a cost associated, it's worth it.
This is a good thing. Browsers should be good at browsing. Password managers should be good at managing passwords. The two should have API’s as necessary to interact so that the user can choose what’s best for them.
Lockwise, which admittedly requires an add-on but integrates with the built-in password manager, I think is pretty on par with its contemporaries.
- There are many times you need a password when you are not in a browser. For instance, on my phone where I don't even have FF installed, my bank's app can still get its password filled in automatically with LastPass.
- Using a separate password manager means you can use multiple browsers with no loss of password access. On my laptop I regularly use both Chrome and Firefox, and I have access to my passwords in both. On my phone, I can use my passwords from Safari.
I may be biased. My wife and share a LastPass account for all of our passwords. We have so many accounts, I can't imagine managing it any other way. Having access to the passwords on all our devices is really great.
Can you expound? After years of using various pw managers I found it being embedded in the browser very useful.
Edit: Though Lockwise is relatively new, and currently opt in. And misses features like importing passwords bulk from other password managers
Not true for Firefox. Just go the privacy settings, forms, saved logins.
I agree password managers like last pass fill this void quite nicely. But are not serviced to run on mobile without payment.
Besides the browser itself still has a lot of work to do. Apparently they had a known remote code execution vulnerability for 2 months waiting to be fixed. That is quite concerning and gives pause while deciding if we should make Firefox our primary browser.
Same. I've tried Firefox last month and it is the only no-go I've no. With Firefox profiles being a thing, I wonder if a front-end to manage them like in Chrome is in development.
1. You can open a new window, move the new tab in the "Work" container (if you use an extension [1] you can just type "co work" in the address bar), and use alt+c [2] to open new tabs in that window, ensuring they are all opened in your "Work" container.
2. You can create a separate profile for work, running "firefox -p" to first create it, and then create a desktop shortcut that links to that profile. This way you'll have two separate profiles on two separate Firefox "icons" that that you can launch at your will. There are ways to do this both on Windows and Linux (not sure about Mac, never used that), and the setup needs to happen only once. I've had separate Firefox profiles for years now that just keep working without any problem. I even ported some profile folders between different installs (same OS), and to my surprise they still didn't break.
[1] https://addons.mozilla.org/en-US/firefox/addon/search-and-sw...
[2] https://addons.mozilla.org/en-US/firefox/addon/new-container...
I had a similar issue on MacOS. After doing some research I found that exporting passwords from Chrome was literally impossible. It definitely worsened the experience of switching. Luckily I have most of my passwords in LastPass, and if I need a password that is only stored in Chrome, I'll add it to LastPass from Chrome on the fly.
It performs well, feels snappy, the dev tools are on par with Chrome's and everything feels right.
The only negatives are that container tabs are still taking a bit of getting used to (why can't I have a 'Work' window in which all the new tabs are 'Work' tabs by default?) and the initial migration of passwords was a bit of a pain.
However, I'm glad to be back.