This post has been transferred from Access to user avatars? · Issue #35 · webxdc/webxdc_docs · GitHub
We now have selfName and selfAddr.
I thought that avatars would also make sense.
I remember we talked about replacing selfName and selfAddr with some faceless UUIDs. I think it needs to be reconsidered.
@simon said:
I remember we talked about replacing selfName and selfAddr with some faceless UUIDs. I think it needs to be reconsidered.
replacing email address makes sense, also we should provide sender information with each update outside of the payload (put there by core):
{
payload:{...},
author: { id: /* local contact id hashed together with chat id */, displayname: string}
}
For avatars we can then have a virtual directory (served by core) inside of the webxdc that serves the avatar pictures:
/webxdc-avatars/{author.id}.jpg
@singpolyma says:
Avatars and display names can both change over time. It might make sense to have a webxdc.getUserProfile(author.id) call that can return relevant display name / virtual path / anything else