Bug 119437

Summary: Kopete should warn you if buddylist contains SN that's not on AIM server
Product: [Unmaintained] kopete Reporter: Mats Ahlgren <ahlgren>
Component: generalAssignee: Kopete Developers <kopete-bugs-null>
Status: RESOLVED FIXED    
Severity: normal    
Priority: NOR    
Version: unspecified   
Target Milestone: ---   
Platform: Ubuntu   
OS: Linux   
Latest Commit: Version Fixed In:
Sentry Crash Report:

Description Mats Ahlgren 2006-01-03 09:05:28 UTC
Version:            (using KDE KDE 3.4.3)
Installed from:    Ubuntu Packages

If one's buddy list contains an SN that isn't on the server-side list, that SN will forever appear offline; this is very dangerous behavior. For example, imagine if this happened to the SN of your girlfriend/boyfriend; then you might be tricked into thinking they were never online anymore, all because Kopete doesn't give you the proper warning message (that a buddy on your buddy list is no longer on the AIM server-side buddy list).

Solution:
On startup, grab the entire buddy list/group structure from the AIM servers and compare it with the local Kopete buddy list. If a buddy on the local list is not on the server list, then prompt the user to add the SN to the server-side list (or else abort and go offline). If a buddy on the server list is not on the local list, prompt the user to add the SN to the local list (or else abort and go offline). This also should be streamlined with a "yes to all" option incase this is the first time the user uses Kopete. Sanity checks should also be made for groups.
Comment 1 Matt Rogers 2006-01-04 01:51:37 UTC
Kopete 0.11 (w/ KDE 3.5) already does this.
Comment 2 Mats Ahlgren 2006-01-05 00:47:26 UTC
Not fixed: Kopete 0.10.4 does not do this after adding a buddy via the contextual menu; I added someone and they appeared offline though they were online. I logged into another IM client and found they weren't on my buddy list.

(They also appeared offline as I was talking to them before I added them to my buddy list.)
Comment 3 Matt Rogers 2006-01-05 01:25:22 UTC
I said 0.11 not 0.10.4