*** Bug 133353 has been marked as a duplicate of this bug. ***

I can't think of a single reason to allow you to have yourself on the contact list. It makes no sense and serves no purpose.

I can't think of a single reason not to "allow" me to have myself on the contact list. It makes no sense and serves no purpose.
Having myself on my contact list gives me an oppurtunity to see how others view my status, as well as giving a method for testing certain things.
If AIM allows me to have myself on my contact list, Kopete should too.

Also, as per Bug 133353:

"Allowing one to have themself on their contact list is supported by the AIM protocol, which is why my username is on my contact list, it is stored on the AIM server. Other AIM clients support this just fine. Besides removing the annoying system modal error message (the entire desktop becomes sluggish until I hit Okay), it is a useful feature to have oneself on their contact list to test away messages. "

> I can't think of a single reason not to "allow" me to have myself on the contact list. It makes no sense and serves no purpose.


I agree. I want to have my jabber self-contact, so that if I'm logged
in on two computers I can send messages between them.

It doesn't matter if you don't see a reason for the feature.  It is supported by protocols(AIM isn't the only one) and not supporting it is a bug.  More importantly its a pretty major bug because most buddy list are stored on the remote server so not adding the contact to the list means you can't even fix the problem through Kopete because the user is never added to your local list for removing.

This is one of the main annoyances I've had with Kopete and it keeps driving me back to Gaim because like Chani I have reasons for keeping a copy of myself on my account.  Even in AIM, sending a msg to yourself will let you see if you've timed out.

Please fix this!

*** This bug has been confirmed by popular vote. ***

Yahoo protocol supports this, and I use it on Miranda on Windows to see my contact picture and my status message.

It's a pity that I cannot do this with Kopete, gaim can do it.

It's like a mirror, you guys use a mirror in real life :)

Personally, I have myself on my contact lists because sometimes, when I log into Oscar services, I wind up in some sort of unfortunate half-connected state where it says I'm logged in, but I can't see anybody online. So I use it to make sure I'm really connected.

Also, I tend to send messages to myself to test logging settings.

These are in addition to the userpic, away message, and startup irritation reasons already stated.

My wife and me use the same jabber account. When I'm at work, the only way for my wife to send me a message is to use the self contact and send it to, say, "husband@work" resource. And I can send my messages to "wife@home" resource. This is the only reason my wife and are still using Psi. I've tried Kopete, but the lack of this feature makes it totally unusable for me :(

The above description is not the only possible scenario for using a self contact. My friend allows his roommate to use his computer (without logging out), when he's at the university, and it would be nice if he could contact the friend by jabber resource "home" from the resource "laptop". 

This seems to be quite an old bug. Bug #66249 (which IMO is a dupe of this one) was opened in 2003. IMO there is nothing new to implement, just to remove this hmm... thoughtless restriction. For the beginning, the self contact may be treated like any other (see Gaim) and if desired, some code may be added later to treat it a little bit different (see Psi, which has the self contact feature "built in" and you don't need to add yourself to your contact list). 

Kopete is the only jabber client known to me, which prevents their users from having a self contact. It's not sounds good and attractive to the users...

Actually, if I understand it right, the reason they did this is because there was a crashing bug if you sent yourself a message. This was their "fix".

Hi, guys! This bug is not ICQ/AIM specific (e.g. jabber plugin behaves the same), so can it be moved to the generic section, not component-specific? Probably, it has a better chance to be fixed, if the fact that it affects the whole kopete will be emphasized.
Besides the specified in previous comments, this bug may be one of the major issues for those migrating from Gaim/Pudgin, since they just used to have a self-contact in a list.

IMO it should be fixed before KDE4. Is there something I can help? I have no specific experience with Qt/KDE programming, but C++ is not a problem for me. 

*** Bug 143377 has been marked as a duplicate of this bug. ***

*** Bug 146817 has been marked as a duplicate of this bug. ***

The text of the Bug 146817 with a reason why this bugs makes kopete unuseable for me:

I want to add my own account in the contact list. The reason for this is, that I do not trust the status icon of the network. Sometimes it happens, that the network (e.g. ICQ) is shown as online, but every contact is shown as offline (happens especialli with WLAN).

An easy detection is to add youre own account to the contact list. If you see than youre self as offline, you know that something is wrong. If you haven't added youre contact you can not be sure, if there is realy no one of youre contacts online, or something is wrong.

But this is not possible with kopete. If you try to add youreself you get a warning that this is not possible. But many other IMs can do this (e.g. GAIM). 

I've been seeing a lot of activity recently.  I was wondering, is anyone in the KDE Project actually working on this?

If nothing else it would be an awesome thing to see in kde4. I've taken a look at it a couple times myself though a while back.  It appears to need some fairly important API changes that I wasn't comfortable undertaking on my own. If there is someone working on in it or someone closer to the project that has ideas about how functions should change to handle this I'd be happy to help in banging out some patches.

*** Bug 143377 has been marked as a duplicate of this bug. ***

+1

I can confirm this with KDE 4.0.85 (KDE 4.1 >= 20080703) openSUSE packages 

*** Bug 143917 has been marked as a duplicate of this bug. ***

I have some patch for this but will apply it only for KDE 4.3 (after trunk is unfrozen) because it changes behavior in all protocols.

Anyway there is a workaround for this bug. If you have AIM screen name for
instance "test1@aol.com" then if you remove the old account from Kopete and add new one with screen name "Test1@aol.com" then it will work (the screen name has to have one or more uppercase letters).

SVN commit 953154 by rjarosz:

Allow user to add self contact into contact list if protocols supports it.
The main change is that const QHash<QString, Contact*>& Account::contacts()
doesn't contain internal myself contact anymore.

Can break some protocols see: FIXME: what about myself?? in code.

BUG: 133621
BUG: 166443



 M  +1 -1      kopete/chatwindow/chatmessagepart.cpp  
 M  +2 -2      kopete/contactlist/contactlistmodel.cpp  
 M  +1 -1      libkopete/kabcpersistence.cpp  
 M  +10 -21    libkopete/kopeteaccount.cpp  
 M  +1 -1      libkopete/kopeteaccount.h  
 M  +3 -2      libkopete/kopeteaccountmanager.cpp  
 M  +4 -1      libkopete/kopetecontact.cpp  
 M  +2 -2      libkopete/kopetecontactlist.cpp  
 M  +1 -1      libkopete/kopetefileengine.cpp  
 M  +8 -2      libkopete/kopeteprotocol.cpp  
 M  +6 -1      libkopete/kopeteprotocol.h  
 M  +5 -5      plugins/history/historylogger.cpp  
 M  +4 -4      protocols/bonjour/bonjouraccount.cpp  
 M  +11 -13    protocols/gadu/gaduaccount.cpp  
 M  +1 -1      protocols/gadu/gaduaddcontactpage.cpp  
 M  +2 -2      protocols/gadu/gadudcctransaction.cpp  
 M  +1 -1      protocols/gadu/gadueditcontact.cpp  
 M  +1 -3      protocols/groupwise/gwaccount.cpp  
 M  +1 -1      protocols/groupwise/gwmessagemanager.cpp  
 M  +1 -1      protocols/jabber/jabberprotocol.cpp  
 M  +8 -2      protocols/jabber/jabbertransport.cpp  
 M  +1 -1      protocols/meanwhile/meanwhileaccount.cpp  
 M  +1 -1      protocols/meanwhile/meanwhileprotocol.cpp  
 M  +4 -6      protocols/meanwhile/meanwhilesession.cpp  
 M  +1 -1      protocols/oscar/aim/aimprotocol.cpp  
 M  +1 -1      protocols/oscar/icq/icqaccount.cpp  
 M  +6 -8      protocols/oscar/oscaraccount.cpp  
 M  +2 -2      protocols/oscar/oscarprotocol.cpp  
 M  +1 -1      protocols/oscar/oscarprotocol.h  
 M  +7 -7      protocols/qq/qqaccount.cpp  
 M  +2 -2      protocols/qq/qqchatsession.cpp  
 M  +3 -3      protocols/skype/skypeaccount.cpp  
 M  +1 -1      protocols/skype/skypechatsession.cpp  
 M  +1 -1      protocols/sms/services/gsmlib.cpp  
 M  +1 -1      protocols/testbed/testbedaccount.cpp  
 M  +3 -3      protocols/winpopup/wpaccount.cpp  
 M  +3 -4      protocols/winpopup/wpprotocol.cpp  
 M  +20 -20    protocols/wlm/wlmaccount.cpp  
 M  +13 -14    protocols/wlm/wlmchatmanager.cpp  
 M  +5 -6      protocols/wlm/wlmchatsession.cpp  
 M  +7 -11     protocols/wlm/wlmtransfermanager.cpp  
 M  +5 -3      protocols/yahoo/yahooaccount.cpp  
 M  +1 -2      protocols/yahoo/yahooconferencemessagemanager.cpp  
 M  +1 -1      protocols/yahoo/yahooprotocol.cpp  


WebSVN link: http://websvn.kde.org/?view=rev&revision=953154

I just upgraded from KDE 4.3.1 to 4.3.2 and am suddenly getting this "You are not allowed to add yourself to the contact list" error when I sign into my LiveJournal Jabber account.  Has the fix posted in Comment #23 not made it into KDE 4.3.2?  Does this bug need to be reopened?

I have experience it also in 4.3.2...

I just upgraded from jaunty to karmic, which is KDE 4.3.2, Kopete 0.80.2.

This bug has suddenly started happening. I have changed nothing from a Kopete configuration that has been working fine for ages.

It happens when Kopete starts, and also sporadically thereafter. I suggest that this bug be re-opened; it looks like there's been a regression.

doc.evans which protocol?

For me it was in Yahoo!

(In reply to comment #27)
> doc.evans which protocol?

Seems to be jabber. I have jabber and yahoo, and I saw a post somewhere that sort-of suggested that maybe the bug was caused by having two accounts online simultaneously, so I set the yahoo to offline. When I came in this morning there were about a dozen messages all containing this error; so since I had gone offline with yahoo last night, my tentative conclusion is that it was jabber sending the error.

If there's a more definitive way to test which protocol is causing it, please let me know.

I've discovered that every time I leave the computer for a few hours, I come back to a slew of repetitions of this error message which have to be clicked through. 

This is sufficiently serious that I think that, with reluctance, I'm going to have to look at using another client until this is fixed.

I see that this bug is still officially marked as RESOLVED/FIXED, though, so I'm a bit confused about its status and whether anyone's likely to look into the problem.

I created a new bug: 212704 so it is new and fresh. Put your comments there.

For me it is 100% caused when I enable the yahoo accounts...