| Summary: | Implement Avatars correctly wrt MSN Content Roaming | ||
|---|---|---|---|
| Product: | Telepathy | Reporter: | Simon McVittie <smcv> |
| Component: | butterfly | Assignee: | Telepathy bugs list <telepathy-bugs> |
| Status: | RESOLVED MOVED | QA Contact: | Telepathy bugs list <telepathy-bugs> |
| Severity: | enhancement | ||
| Priority: | medium | CC: | ali.sabil, nekohayo |
| Version: | unspecified | ||
| Hardware: | Other | ||
| OS: | All | ||
| Whiteboard: | |||
| i915 platform: | i915 features: | ||
Rob has told me this is actually perfectly possible with the current Avatars API, so reassigning to butterfly. How to do it: * Implement GetAvatarTokens and GetKnownAvatarTokens as asynchronous * Delay (queue up) replies to either of those methods if called for the self-handle, until you have downloaded the avatar from the content-roaming server and started publishing it As far as I know, content roaming is not even implemented for nickname and personal message. https://bugs.freedesktop.org/show_bug.cgi?id=21990 -- GitLab Migration Automatic Message -- This bug has been migrated to freedesktop.org's GitLab instance and has been closed from further activity. You can subscribe and participate further through the new bug through this link to our GitLab instance: https://gitlab.freedesktop.org/telepathy/telepathy-butterfly/issues/1. |
Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.
Currently, the Avatars interface copes with two types of avatar support: * Server-stored (e.g. Gabble): you push your avatar to a central server, and everyone else pulls it from the central server. When you disconnect and reconnect, your old avatar is still there. * Transient (e.g. Salut): everyone pulls your avatar directly from you. When you disconnect and reconnect, you have to "re-publish" your avatar (that is: our client pushes the avatar to our connection manager, so that other people can pull the avatar from our connection manager). For the moment, we've agreed that telepathy-butterfly should follow the second model. However, MSN does in fact have centralized avatar storage - it's just that only the owner of the avatar can download it! Edited IRC transcript: 13:45 < smcv> asabil: am I right in thinking that the following hypothetical scenario is a reasonable caricature of how MSN behaves, with more familiar protocols substituted? 13:46 < smcv> in a hypothetical protocol called NSM, other users get the avatar from us directly 13:46 < smcv> this means if you sign on to your account from two different computers, the second doesn't have the avatar that was set by the first 13:47 < smcv> so as a workaround, you email the avatar to yourself whenever you set it 13:47 < asabil> lol 13:47 < asabil> that's exactly it 13:47 < smcv> and when you sign on on a different computer, you grab the most recent avatar from your mailbox with IMAP, and set it 13:50 < asabil> smcv: that's almost it 13:50 < asabil> just do a s/IMAP/SOAP/ We're not sure how the Avatars interface should represent this.