Bug 28301

Summary: accessor for cached avatars on offline accounts
Product: Telepathy Reporter: Simon McVittie <smcv>
Component: tp-glibAssignee: Telepathy bugs list <telepathy-bugs>
Status: RESOLVED MOVED QA Contact: Telepathy bugs list <telepathy-bugs>
Severity: enhancement    
Priority: medium CC: xclaesse
Version: git master   
Hardware: Other   
OS: All   
Whiteboard:
i915 platform: i915 features:

Description Simon McVittie 2010-05-28 06:36:25 UTC 
From Bug #27269:

> The avatar token doesn't seem very useful when you can only get a cached avatar
> via a TpContact - we'll probably have to add API to telepathy-glib to see
> whether a cached avatar is still available, and if so, return them. This will
> require the connection manager name and the protocol name (both derivable from
> the TpAccount name), and can't be done for non-Telepathy avatars.

Proposed API: one or both of

    GFile *tp_account_get_cached_avatar (TpAccount *account,
        const gchar *avatar_token);

    GFile *tp_contact_get_cached_avatar (const gchar *cm_name,
        const gchar *protocol_name,
        const gchar *avatar_token);

(either would return NULL if not found).
Comment 1 Xavier Claessens 2013-11-15 22:39:27 UTC 
Tokens are really implementation details that clients shouldn't have to know about. With bug #55920 the CM will expose only an URI as a contact attribute. With bug #62378 CMs stores contact attributes (including avatar URI) on disk and accessible via TpOfficeContact object.

So I think those 2 bugs together fix this one.
Comment 2 GitLab Migration User 2019-12-03 20:03:00 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-glib/issues/33.

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.