Keychat currently has three avatar mechanisms for users:
1. Default Avatar:
By default, each Keychat user’s avatar is a cartoon image generated from their user ID. The advantage of this approach is that once you know someone’s ID, you automatically know their avatar. It doesn’t require storing avatars on a media server or distributing them separately.
2. Microblog ID Avatar:
If a user logs in to Keychat with their microblog ID, their Keychat avatar inherits the avatar from that microblog ID. This avatar is publicly uploaded to a media server.
3. Custom Avatar:
Users can also set their own custom avatar in Keychat. See the note below for more details.
Currently, there’s a bug affecting the second avatar mechanism — avatars from microblog IDs are not displaying correctly.
We are considering whether to remove this second mechanism and only keep the first and third ones. If we decide to keep it, we will fix the bug.
We hope you’ll like Keychat’s custom-avatar approach.
1. We believe a chat app user’s avatar is different from a microblogging app user’s avatar and shouldn’t be publicly uploaded to relays.
2. Keychat can’t rely on a media server that promises long-term avatar storage. With the current avatar model, there’s no need for a long-lived media server.
View quoted note →
View quoted note →