https://bugs.freedesktop.org/show_bug.cgi?id=14540
Simon McVittie <simon.mcvittie at collabora.co.uk> changed:
What |Removed |Added
----------------------------------------------------------------------------
Summary|Nicknames interface |Names interface - Aliasing
| |replacement with separate
| |nickname, local alias etc.
CC| |youness.alaoui at collabora.co
| |.uk
--- Comment #12 from Simon McVittie <simon.mcvittie at collabora.co.uk> 2010-05-24 06:02:37 PDT ---
(In reply to comment #11)
> No worries Simon, I'd like to give my opinion and explain how it works with MSN
> anyways, so thanks for CC-ing me.
> So, with MSN you have a nickname (the one the contact sets), which you can
> override (The official client just puts an 'annotation' on the contact's data
> called 'AB.Nickname' and the UI uses it to replace the contact's nickname).
OK, good, that's how I'd understood it too. The one the contact sets on
themselves is Telepathy's "nickname", and the override is Telepathy's
"local-alias".
> You can also have a 'friendly name' which is a bit different, it's the nickname
> to be shown for a *single* message in the chat window.. This is used for
> example by groups.im (a single bot contact that acts like an IRC channel with
> bip), where the groups.im contact uses this friendly name to show you the
> correct nickname of who is sending the message.
This is inaccessible except on messages, right? So you'd never want it to be
shown in a contact list, because you can't display it until you've received at
least one message in the current session?
If it was possible to pull this from the server somehow, we could make it
available as a third attribute on the Names interface, but at the moment we
just map it to a "sender-nickname" key in each message on the Messages
interface. Is that basically equivalent to what aMSN does?
> Anyways, in aMSN, we make a distincition between the 'nickname' and the 'custom
> nickname' (petname). I also believe the UI needs to have access to both
> information
Right, making this possible in Telepathy is the purpose of this bug.
--
Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the QA contact for the bug.