During registration, allow the user to select an avatar image. Ideally we will provide some options, or allow the user to upload one.
Either way, the image should be uploaded to IPFS (de-dupe is automatic, so each user can just add their image file to IPFS and the profile can reference the CID).
A second system-provided avatar image will also be displayed, this image will be generated from the user's public key. An Identity component should control the display of a user's identity. This component should be used in the feed, and in the Publish component when listing users for mentions.
The display would be something like:
avatar | username (short code) | key-derived avatar (identicon).
+-----------+
| O X | +--+
| X ^^ | Username (short code) |01|
+-----------+ +--+
Avatar is user-select and may not be unique.
Username is user-selected and may not be unique.
short-code is the first 7 bytes of the public key hash, unique.
key-derived avatar is generated using the public key hash, unique
btimby
commented
3 years ago
During registration, allow the user to select an avatar image. Ideally we will provide some options, or allow the user to upload one.
Either way, the image should be uploaded to IPFS (de-dupe is automatic, so each user can just add their image file to IPFS and the profile can reference the CID).
A second system-provided avatar image will also be displayed, this image will be generated from the user's public key. An
Identitycomponent should control the display of a user's identity. This component should be used in the feed, and in thePublishcomponent when listing users for mentions.The display would be something like:
https://barro.github.io/2018/02/avatars-identicons-and-hash-visualization/