contacts store should allow more than one public key per recipient email address

[tomholub]

Currently, I believe we restricted maximum of 1 public key per recipient in the db, and also in Settings -> Contacts.

We should instead allow more than one public key per recipient. With this, Settings -> Contacts should get updated - next to each email it should say something like (1 public keys) or (3 public keys) with 50% opacity.

Once I click on it to view the public key, instead of the single public key view that is there now, I should instead view the user's email address and then a list of public keys with details about them, some sort of large clickable "cards".

Once I click on one of the public key cards, then I'll see the current view public key activity with more details about the public key, and on top right the icons to share/copy/delete the public key.

Each card should have:

Fingerprint: (primary fingerprint in small letters so it fits the line)
Primary user: some@example.com
Created: some date
Expires: some date or "never"

[sosnovsky]

@tomholub I found possible issue (or may be it should work this way) - I added second mail account to Flowcrypt app and now when I open Settings -> Contacts screen it shows contacts for both accounts. Should it show separate contacts lists for different accounts?

[tomholub]

On other platforms, we have one joint contact list for all accounts. So far we didn't run into issues doing that, it seems to work out well. Therefore working as intended. Thanks for asking!

Btw no migration is needed for this issue either

[sosnovsky]

@tomholub I implemented deletion for public keys, but now I receive such error when trying to send email to contact with removed public key

How should app react in this case? Automatically generate new key?

[tomholub]

No, no, no :-) you can't generate any keys for recipients. They have to give the public key to you, because that public key has to match the recipient private key. Else the recipient can't open any message that you send them.

When there is no public key available for the recipient, the recipient bubble has to be gray color. And the message that it's showing is the right message. In the future, we'll add options to manually import public key for that recipient, in case the sender got the key through some other means (downloaded from someone's website for example).