Opened 10 years ago

Last modified 9 years ago

#9648 new enhancement

XMPP: Use display name from vCard immediately after loading roster

Reported by: markp Owned by: deryni
Milestone: Patches welcome Component: XMPP
Version: 2.5.8 Keywords: jabber vcard display name shared roaster
Cc:

Description

Currently if you have a jabber-setup with a shared roster on server side, pidgin displayes only the JabberID after first login. You have to load each user's vCard manually to switch to display name from vCard.

There are already some tickets regarding this issue especially for "adding users from search". But it is much more annoying if you have a big list from a shared roaster and each client has to click through the whole list to see the real names.

So it would be great, if the vCard of all users is loaded immediately after loading the roster after login. And if the vCard is loaded immediately after adding a new user, the problem with "adding users from search" is also fixed.

Great thanks!

Change History (5)

comment:1 Changed 10 years ago by deryni

vCards are potentially large, fetching them can be costly, especially for large rosters. They can also change at any time without notice, so a single fetch may miss new data and pidgin can't constantly request it. In a shared roster environment the server should be pushing nicknames on the roster entries as well as just the roster entries.

comment:2 follow-up: Changed 10 years ago by markp

Okay ... but then there should be a possibility to update all Nicknames at once manually. For example in the context menu of the jabber account. And eventually an option to activate automatic updating at login which is not enabled by default.

comment:3 in reply to: ↑ 2 Changed 10 years ago by markp

Regarding to your second argument: Is it possible for example with ejabberd to push the nicknames? I can only set the vCard fields, but only the entries are pushed, not the nicknames.

comment:4 Changed 10 years ago by deryni

  • Milestone set to Patches welcome

I don't believe (though I haven't checked) that ejabberd supports pushing anything more than the JID as part of their shared roster implementation.

An account action for "fetch all vcards" is not a terrible idea, but not one I am excited about supporting either as it is still a substantial amount of traffic.

Ideally, clients and servers will be moving away from using vcards for "basic" information like this and will move to PEP/etc. instead because that allows pushing/better notification of changes.

I would likely accept a patch to add this option as long as it included a warning dialog and a short delay between the fetches.

comment:5 Changed 9 years ago by darkrain42

Ticket #12568 has been marked as a duplicate of this ticket.

Note: See TracTickets for help on using tickets.
All information, including names and email addresses, entered onto this website or sent to mailing lists affiliated with this website will be public. Do not post confidential information, especially passwords!