[Bug 28037] TpContact should have helper API to set alias

bugzilla-daemon at freedesktop.org bugzilla-daemon at freedesktop.org
Tue Jul 13 14:36:32 CEST 2010


https://bugs.freedesktop.org/show_bug.cgi?id=28037

--- Comment #4 from Simon McVittie <simon.mcvittie at collabora.co.uk> 2010-07-13 05:36:32 PDT ---
(In reply to comment #3)
> Note that TpAccount has tp_account_set_nickname_async(), I actually picked the
> API from it.

That's to set our own nickname. There are two orthogonal concepts:

* nickname: X's nickname is chosen by X, so by definition, we can only set the
SelfHandle's nickname

* local-alias: X's local alias is chosen by the SelfHandle: if supported by the
protocol, we can set anyone's local alias

Aliasing mixes the two; Names won't (see Bug #14540).

An API for local alias on TpContact would have undefined results if used on the
self-handle's corresponding contact. Under Aliasing, it sets the self-handle's
local alias *and* nickname (implementation detail: in Gabble, it only sets the
local alias if the self-handle is already on the roster).

Under Names, the naive version would be to put the self-handle on the roster
and set its local alias; one possible refinement would be to ignore this for
the self-handle, or ignore this for the self-handle if it isn't already on the
roster.

The Account API anticipates Names, by calling the local user's name for
themselves "Nickname" rather than "Alias". At the moment MC uses Aliasing to
set the self-handle's nickname, perhaps with the side-effect of changing the
local alias; when Names happens, MC should be changed to try to set the
nickname via that first, falling back to Aliasing.

-- 
Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the QA contact for the bug.
You are the assignee for the bug.



More information about the telepathy-bugs mailing list