Prioritize a password entry for a particular website

General information

• Browser + version: Any
• Information about the host app:
  • How did you install it?: prebuilt binary
  • version ($ browserpass-linux64 --version): Browserpass host app version: 3.0.10
• Information about the browser extension:
  • How did you install it?: chrome webstore
  • Browserpass extension version as reported by your browser: 3.7.2

Feature Request

To mark a particular entry from a site as “priority” if there are multiple issues

Current Beavior

If multiple accounts are associated with a site (e.g. github.com is a subdirectory in the password store), then, autofilling the login form (with Ctrl+Shift+f) will sometimes result in an unintended password to be filled in.

Proposed Feature

A method to mark a particular account as “priority”. So, if there are multiple accounts, that account with priority will be used to autofill the login form.

[maximbaz]

A very simple approach could be renaming the files, as in absence of any usage data, browserpass would sort them alphabetically… It’s actually what I personally do, now that you mention it 😅 I name the primary entry github.com.gpg, and all the additional ones I put in a folder, like github.com/secondary-account.gpg. Just keep in mind that as you login on a particular domain at least once, then in this browser the sorting would no longer be alphabetical, but would take usage counts into account - this is done, among other reasons, to make it easy to login with Ctrl+Shift+F on websites which first ask for a username, and on the next page as for password.

[hyperupcall]

I think my main argument would be that in my experience it’s hard to remember what login I used last, but it’s easy and natural to remember what login I typically use. I believe it’s what @hyperupcall refers to as well, in the second to last paragraph above.

Yup 👍

What do you guys think? slightly_smiling_face

I like this! For me it works in more cases out of the box, and the reset frequency makes it flexible enough in case users switche the account that they use the most.

So let me ask, which one should it be, supersede frequency data, or completely ignore it, if for a given domain we have both?

Since now the entries are listed by frequency rather than recency, I think a better strategy might be to store the frequency data in the .browserpass.json file, and just not do the priority feature. I originally proposed the priority feature due to inherent issues with recenty ordering of the entries, but now since those are fixed, the only issue remaning is cross-browser and cross-computer syncing of the frequency data. I think having a priority feature would also be redundant, since the most frequently used entries are naturally the highest priority. So I guess your example wouldn’t really be applicable in this case - I’d only sort by frequency.