how best to handle multiple public remote keys, fingerprints, verified statuses
Figure out how best to handle duplicate keys when doing the big merge
#1 Updated by hans about 4 years ago
- Subject changed from merge duplicates in the final keys to how best to handle multiple public remote keys, fingerprints, verified statuses
- Target version set to 0.3
for now, we're just including all public remote keys and verified fingerprints. Does that always make sense?