If a service is ever compromised, you would have chosen to consolidate information that would lead you to be more greatly vulnerable than if you had spread over multiple services.

A (small) part of not putting all your eggs in one basket is also avoiding vender lock-in. Having your personal email with proton, and your password manager with them makes it very difficult to switch in the future if you need to.

On a side note, I use anonaddy (now Addy.io). It allows you to create email aliases on the fly. So when I sign up for a new account somewhere, I generally make up some email like “example@my-account.anonaddy.com” for the email and save that right to bitwarden.

Looks like simplelogin supports the same thing https://simplelogin.io/blog/subdomains/

PS. Using your own domain name is a great way to avoid vender lock-in =)

The idea is quite simple. If you put all your eggs into one basket, if that basket breaks, you’re screwed.

If we put this into context, this would mean that you would, for example, use all of Proton’s services and when Proton does something bad, now your entire suite of services is fucked.

in the case of technology (specifically anything cloud based * ) – if you have your needs split across multiple services, if one of them goes down / gets hacked / goes belly up, you only lose access to what was stored on that service – if everything is on one service, then you lose access to everything

* the cloud is just someone else’s computer

deleted by creator

I don’t put my passwords in the cloud in the first place, so what it means to me is: keep backups.

Don’t depend completely on something or someone, if at some point it goes to the fuck you will also go to the fuck…

That’s basically the main point into that phrase.

You can have bitwarden auto generate simplelogin emails as well when generating usernames. You just need to fetch an API key from simplelogin :)