I just had to explain to someone that rather than parsing the last component of an Account's object path, they should:
• Get the "Parameters" property on the Account;
• Look up the "account" key in that dict.
It's confusing enough that there's a property called Parameters (I always get these two confused), but to have one of the parameters of an Account be "account" is perverse...
Incompatible change => for 1.0.
Heh. On IRC, 'username' is your UNIX login name-type thing, and 'account' is your nickname …
"username" is not generic enough, and may not even be obviously obtainable:
in XMPP you may not know your eventual bound JID until you authenticate with whatever the auth handler supplies for it (a certificate from your smart ID card, for example).
So, what was the use case?
(In reply to comment #3)
> So, what was the use case?
For renaming “account”? Just human confusion.
I totally agree that for what we use it in telepahy, username is better.
Here's a patch. Let's finally do this.
What do you think?
(In reply to comment #6)
> What do you think?
I've decided I can't be bothered writing yet more annoying migration code in mission-control right now; we've got better things to do.
I'll leave the bug open as it's still valid enough, but I'm removing the blocking bug.
-- GitLab Migration Automatic Message --
This bug has been migrated to freedesktop.org's GitLab instance and has been closed from further activity.
You can subscribe and participate further through the new bug through this link to our GitLab instance: https://gitlab.freedesktop.org/telepathy/telepathy-spec/issues/49.