[Telepathy] Account and AccountManager objects

Simon McVittie simon.mcvittie at collabora.co.uk
Wed Jan 23 07:19:30 PST 2008

Hash: SHA1

I begin to wonder whether we should have a section in the Telepathy spec
with protocol-specific notes, like the recommended mapping between
JIDs/etc. and handles.

On Wed, 23 Jan 2008 at 14:09:46 +0000, Will Thompson wrote:
> On Tue, Jan 22, 2008 at 05:38:41PM +0000, Simon McVittie wrote:
> > - Haze: it's anyone's guess what libpurple does for any given protocol.
> * MSN: the account parameter is your .net Passport (or whatever it's
>   called this week) ID, so something that looks like an email address;
>   normalized handles are the same, lowercased.

Good. Same as Butterfly.

> * ¿¡Yahoo‽: the account parameter is your username (something like
>   "lignojmik"); normalized handles are the same, lowercased.  The Yahoo
>   <-> MSN bridge doesn't work in either direction in libpurple as far as
>   I know, so I don't know how such contacts look.

We don't know how bridged contacts ought to look either...

> * XMPP: the account parameter is your jid, optionally qualified with a
>   resource.  (I just remembered this; it's now fd.o bug #14212)
>   Normalized handles are the lowercased, resourceless JID.

Good, same as Gabble if you fix #14212.

> * AIM: these days, screennames can either be alphanumeric string
>   starting with an letter, ignoring spaces and case, or a valid email
>   address, or numeric strings, which are ICQ accounts.  The account
>   parameter can be any of these; normalized handles are lowercased and
>   have whitespace removed.  (libpurple doesn't actually care whether you
>   supply an AIM screen name or an ICQ UIN when creating an AIM account —
>   it just magically treats it as an ICQ account in the latter case.
>   This is probably a bug.)
> * ICQ: as above.  (You can talk to ICQ people from an AIM account.)

Sounds good.

> * Myspace: account parameter is the email address you sign up to myspace
>   with.  Normalized handles are either such email addresses, or the
>   alphanumeric string "nnnrgh" of a profile URL like
>   <http://www.myspace.com/nnnrgh>.  There's normalization from one form to
>   the other (I can't remember the direction), which doesn't always work
>   (kind of like the protocol plugin in general, actually, but the
>   developer has just reappeared so maybe it'll improve!).

Urgh. If I remember correctly, every myspace account is uniquely ID'd by
an email address, and some (but not all) myspace accounts have a short
name too? I doubt we particularly care about 100% correct semantics
though :-P

> Protocols I know about that people (who aren't me and aren't excessively
> bored) don't use through Haze:
> * local-xmpp: as Salut, except you have to supply an account parameter,
>   which is a bug.

Yeah... but you can make it optional at the Tp level, and if missing,
use the same algorithm as Salut, right? :-)

> * IRC: account parameter is "resiak at irc.freenode.net" (fd.o bug #14213).
>   Normalized handles are lowercased nicknames; e.g. "resiak".  The
>   inconsistency is undesirable, but no-one uses IRC through Haze.

This should get synced with Idle, when we've worked out what Idle should
be doing.



More information about the Telepathy mailing list