add own JID to roster

Sounds like a great solution as it avoids adding an additional configuration option whilst keeping transparency.

appended patch detects when the own jid is added or removed from the roster.

It still needs to be displayed in the roster.

I think you forgot to type an $ sign in your patch:

invalid bareword "isownjid"
in expression "isownjid";
should be "$isownjid" or "{isownjid}" or "isownjid(...)" or ...
invalid bareword "isownjid"
in expression "isownjid";
should be "$isownjid" or "{isownjid}" or "isownjid(...)" or ...
    (parsing expression "isownjid")
    invoked from within
"if {isownjid} {
 if {!$jprefs(rost,showOwnJID)} {
     return
 }
    }"
    (procedure "::RosterTree::CreateItemBase" line 11)

fixed the bug in the patch, and rewored the remove jid stuff, and added a exception when adding the own jid

fixed patch again, and now own jid is shown in the roster too, still needs some cleanup and proper testing...

now correctly adds/removes the own jid from the roster. Also when there are multiple users marked for removal, the own jid is detected.

Its only still cluttered with debug output informations.

There may be some "little" things to discuss:
 * right now it adds the own JID in a group called MySelf
   * could be a different name, and made translatable
 * This group is just sorted alphabetically in the roster amongst the others
   * when involving the roster themes, it could be made to always show up on top or the like...
 * the user is not prevented to be edited
   * any changes done to the user are not propagated, i.e. putting the user into different groups, or changing the nick
 * the user can be dragged and dropped into other groups, but also here, the changes are not actually done

argh, after all that working on that, I just read the last version of the http://tools.ietf.org/html/draft-ietf-xmpp-3921bis-20#section-2.3.3 at the end of this section the following:

Interoperability Note: Some servers return a <not-allowed/> stanza
      error to the client if the value of the <item/> element's 'jid'
      attribute matches the bare JID <localpart@domainpart> of the
      user's account.

So I'll ask on <email address hidden> whether its now just OK to assume that servers that will comply with rfc3921bis will allow adding the own jid to the roster.

I'll close this one, since it seems now to be fine that a server saves the own jid of the user to the roster.
This makes live easier for me/us, since nothing needs to be changed in coccinella.
It will just not work with some of the servers, so the feature may not be available for everyone.