[kopete-bugs] [Bug 245754] New: Jabber rename propagation can be a problem

Lapo Luchini lapo at lapo.it
Mon Jul 26 11:26:14 CEST 2010


https://bugs.kde.org/show_bug.cgi?id=245754

           Summary: Jabber rename propagation can be a problem
           Product: kopete
           Version: unspecified
          Platform: FreeBSD Ports
        OS/Version: FreeBSD
            Status: UNCONFIRMED
          Severity: normal
          Priority: NOR
         Component: Jabber Plugin
        AssignedTo: kopete-bugs at kde.org
        ReportedBy: lapo at lapo.it


Version:           unspecified (using KDE 4.4.5) 
OS:                FreeBSD

I think the automatic rename propagation offered by Kopete's implementation of
the Jabber protocol is very cool, but I'd like an option to opt-out of it as it
might be sometimes not the best thing to do.

Reproducible: Always

Steps to Reproduce:
Since GTalk uses GContacts (using the "first + last name" field instead of
"nickname" field, strangely enough!) I was forced to use full real name in
Kopete unless I want to lose that data in my addressbook, as Kopete sends the
rename to the server even though it was done on a metacontact whose name source
I selected was not Jabber but "Custom".

The situation is even worse since I added Facebook Jabber to the meta-contacts,
as it doesn't support server-side renames and forces its names to the
meta-contact, which in turn forces them to my GCalendar address book (and for
some people using nicknames or lengthy middle names, that's not what I like in
my address book).

This is usually a desiderable feature, but I think it should have an opt-out
method (or maybe simply don't send the rename update when the name source is
set to "custom" in the meta-contact page).

-- 
Configure bugmail: https://bugs.kde.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.


More information about the kopete-bugs mailing list