Bug 12832 - Support XEP-0084 User Avatars (PEP-based)
Summary: Support XEP-0084 User Avatars (PEP-based)
Alias: None
Product: Telepathy
Classification: Unclassified
Component: gabble (show other bugs)
Version: unspecified
Hardware: All All
: low enhancement
Assignee: Telepathy bugs list
QA Contact: Telepathy bugs list
URL: http://www.xmpp.org/extensions/xep-00...
Depends on:
Reported: 2007-10-17 03:47 UTC by Simon McVittie
Modified: 2019-12-03 19:17 UTC (History)
3 users (show)

See Also:
i915 platform:
i915 features:


Description Simon McVittie 2007-10-17 03:47:38 UTC
XEP-0084, (PEP-based) User Avatars, is in Last Call. We should consider implementing it, with vCard-avatar backwards compatibility, much like the way we support both PEP-based and legacy nicknames.

It looks reasonably simple to implement. A metadata PEP node (to which we're meant to subscribe) pushes out metadata updates, which replace the SHA-1 seen in presence; a data PEP node (to which we're *not* meant to subscribe) contains the avatar itself, replacing the vCard.
Comment 1 Ferdinand Stehle 2016-08-18 22:52:49 UTC
I implemented XEP-0084 and it seems to work with my contacts that use Conversations*.


* Note: Conversations publishes avatars in the webp-format and your gtk/gdk installation may miss the decoder. A solution is available here: https://github.com/aruiz/webp-pixbuf-loader
Comment 2 Dennis Schridde 2016-08-19 06:47:23 UTC
(In reply to Ferdinand Stehle from comment #1)
> I implemented XEP-0084 and it seems to work with my contacts that use
> Conversations*.

Thanks for working on this!
Comment 3 GitLab Migration User 2019-12-03 19:17:10 UTC
-- 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-gabble/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.