Closed scusi closed 6 years ago
In the end it does not matter if you have to have the secureShareUsername or the users encodeID before you can add someone to the addressbook.
One good thing could be to have somewhat shorter usernames. Something along the commons.ShortID
On shorter usernames:
With commits
there is are new functions to create a shorter username, namely:
shortChecksum https://github.com/scusi/secureShare/blob/b1abb33276ec2ddcd0a94704c36427d6de7f5456/libs/server/common/common.go#L68-L81
There is also a small and simple command to generate a username
shorter usernames are now actually used, see commit https://github.com/scusi/secureShare/commit/61007b827121552d8f54a0ff154b7d31f1f5ec8d
secureShareUsernames now look like this: 89DMdTVFLa
or 5NAqYu27C
or 2kqK8cRKFf
also updated README with commit https://github.com/scusi/secureShare/commit/8f8c437a96d22d171371d62ba214c4bb4f146bb6
to add a contact to your addressbook is to complicated.
how about to reduce it to alias and pubKey?
secureShare -addContact flw -pubKey HZfb8HL4tL7bGJBZq2ha1oyQkf3ePTsLCBBqKog8ESz4y
The server side username could be found by asking the server OR by generating the username from the pubKey.