I recall - ages ago - that we were going to, at one point, mention that if you change your nickname, you should send unavailable persence after the change to the old nick:

C: <presence to='room@service/new_nick'/>
S: <presence from='room@service/old_nick' type='unavailable'>...110/303...</presence>
S: <presence from='room@service/new_nick'/>
C: <presence to='room@service/old_nick' type='unavailable'/>

The problem being that currently, the server must track directed presence, and so if you change your nickname, the server keeps tracking the old nickname too - and will eventually have to send an unavailable anyway.

In addition, there's a small possibility that this could be used by unscrupulous rooms as a presence leak, by both the unavailable presence to the old nick and by using the response to probes (potentially).

Dave.
--
Dave Cridland - mailto:[email protected] - xmpp:[email protected]
 - acap://acap.dave.cridland.net/byowner/user/dwd/bookmarks/
 - http://dave.cridland.net/
Infotrope Polymer - ACAP, IMAP, ESMTP, and Lemonade

Reply via email to