Bug 245754

Summary:	Jabber rename propagation can be a problem
Product:	[Unmaintained] kopete	Reporter:	Lapo Luchini <lapo>
Component:	Jabber Plugin	Assignee:	Kopete Developers <kopete-bugs-null>
Status:	RESOLVED WORKSFORME
Severity:	normal	CC:	dreamwalker
Priority:	NOR
Version First Reported In:	unspecified
Target Milestone:	---
Platform:	FreeBSD Ports
OS:	FreeBSD
Latest Commit:		Version Fixed/Implemented In:
Sentry Crash Report:

Description Lapo Luchini 2010-07-26 11:26:12 UTC

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).

Comment 1 Radosław Jan Ganczarek 2010-09-15 09:10:30 UTC

Still existent in KDE 4.5.1 on Linux

Comment 2 Andrew Crouthamel 2018-11-05 03:10:27 UTC

Dear Bug Submitter,

This bug has been stagnant for a long time. Could you help us out and re-test if the bug is valid in the latest version? I am setting the status to NEEDSINFO pending your response, please change the Status back to REPORTED when you respond.

Thank you for helping us make KDE software even better for everyone!

Comment 3 Andrew Crouthamel 2018-11-16 05:25:50 UTC

Dear Bug Submitter,

This is a reminder that this bug has been stagnant for a long time. Could you help us out and re-test if the bug is valid in the latest version?

Thank you for helping us make KDE software even better for everyone!

Comment 4 Justin Zobel 2022-12-09 22:13:12 UTC

Thank you for reporting this issue in KDE software. As it has been a while since this issue was reported, can we please ask you to see if you can reproduce the issue with a recent software version?

If you can reproduce the issue, please change the status to "REPORTED" when replying. Thank you!

Comment 5 Bug Janitor Service 2022-12-24 05:23:43 UTC

Dear Bug Submitter,

This bug has been in NEEDSINFO status with no change for at least
15 days. Please provide the requested information as soon as
possible and set the bug status as REPORTED. Due to regular bug
tracker maintenance, if the bug is still in NEEDSINFO status with
no change in 30 days the bug will be closed as RESOLVED > WORKSFORME
due to lack of needed information.

For more information about our bug triaging procedures please read the
wiki located here:
https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging

If you have already provided the requested information, please
mark the bug as REPORTED so that the KDE team knows that the bug is
ready to be confirmed.

Thank you for helping us make KDE software even better for everyone!

Comment 6 Bug Janitor Service 2023-01-08 05:16:58 UTC

This bug has been in NEEDSINFO status with no change for at least
30 days. The bug is now closed as RESOLVED > WORKSFORME
due to lack of needed information.

For more information about our bug triaging procedures please read the
wiki located here:
https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging

Thank you for helping us make KDE software even better for everyone!