I'm not sure I really follow your logic, and sorry in advance I don't mean to say you're wrong, I'm just trying to understand deeper. It seems that you're comp

I'm not sure I really follow your logic, and sorry in advance I don't mean to say you're wrong, I'm just trying to understand deeper. It seems that you're comparing a PM with a fully featured app, vs an early-stage idea that I'm proposing. I'm comparing 2 core algorithms, vault vs deterministic. Assume I will release an app very similar to 1password, but with "my" core algorithm. Or, if you prefer, assume you don't have your PM handy. But, I think, the comparison should be fair. What I'm trying to say is that all the features you're proposing can be implemented/applied to my core algo as well, they don't deal with how you generate a secret, but more on how do you manage many of them. On changing the password there's another case. If your master password for a group is leaked, and you fear that the vault is also exposed, then you have to change all the passwords in the group. If you think to "high mobility" uses, like using your PM also on untrusted/partially trusted devices, the exposure of the vault is not really something you can exclude. I believe that the core difference between vault and deterministic is this one. Vault, you have completely random passwords, you always need the PM to retrieve them. Deterministic, you can recover your passwords without the PM (some of them, if you remember the info) -- my algo attempts to really go full in that direction. Everything else is "management" features, that you can build on top of the core.