[Bug 25120] Account: clarify expected behaviour of Nickname

[bugzilla-daemon at freedesktop.org]

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

--- Comment #1 from Simon McVittie <simon.mcvittie at collabora.co.uk> 2010-08-06 06:36:21 PDT ---
(In reply to comment #0)
> 13:40 < sjoerd> does the alias-before-connect override the server alias? should 
>                 it ?

I think it should override what's on the server if you've changed it while
offline, or the server should override the local setting if the local setting
has not changed since the last time we connected (this is the same logic we use
for avatars). Unfortunately, Aliasing makes this impossible, because we can't
tell for sure whether the alias is server-stored; we should fix this in Names.

That means that (to continue the example from IRC discussion) if you alternate
between Pidgin on laptop and Telepathy on N900, with one at a time connected,
occasionally changing your name on the current device, the right things will
happen.

> 13:39 < smcv> I think that might be a good rationale for MC's current behaviour
> 13:39 < smcv> suppose I'm logged in using Telepathy on N900 and Pidgin on laptop
> 13:40 < smcv> and I change my nickname in Pidgin
> 13:40 < smcv> MC on the N900 should pick up the change for next time, ideally?

Implementation detail: it does, mostly in mcd-connection.c.

> 13:40 < smcv> but then there's also an interaction with changing your nickname 
>               on the laptop while the N900 is offline, and then logging in with 
>               the N900

However, this is currently mis-handled in MC due to deficiencies of Aliasing.
The N900's MC will override what the laptop set:

    /* FIXME: ideally, on protocols with server-stored nicknames, this should
     * only be done if the local Nickname has been changed since last time we
     * were online; Aliasing doesn't currently offer a way to tell whether
     * this is such a protocol, though. */

-- 
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.