[Bug 34640] Use Protocol.IdentifyAccount to choose accounts' object paths

[bugzilla-daemon at freedesktop.org]

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

--- Comment #1 from Simon McVittie <simon.mcvittie at collabora.co.uk> ---
Hijacking this a bit: ExternalPasswordStorage and AccountStorage, which are
related to this, are *still* drafts...

(In reply to comment #8)
> Actually, no, they're still marked as DRAFT in the spec. Let's just undraft
> them: the implementation in MC isn't great, but it'll do.

I noticed they don't have any regression test coverage, started writing a test,
ran into "ugh, how much of a CM do I need to implement?" and lost interest for
now.

I'd like to fix the fact that it calls IdentifyAccount() repeatedly - I think
it ought to call it exactly once, on account creation, and save the result in
the account, as Will said on Bug #34416.

I wonder whether telepathy-haze should even persist libpurple accounts on disk,
and use the AccountStorage interface to manage them... although it would
probably have to make sure that all accounts are disabled at the libpurple
level before it connects any of them.

-- 
You are receiving this mail because:
You are the QA Contact for the bug.
You are the assignee for the bug.