Thank you for reporting the problem. We will look at it as soon as possible.

Hi,

I modified the Presence plug-in to handle nickname in subscription.

Source Code Disclaimer: Yes;

What is status of the ticket? If not completed, provide work estimates.

I've verified the report and my conclusion is that the patch is not applicable and thus I would reject the submission.

XEP-0172: User Nickname defines a protocol for signalling user preferred nickname to the contact, but (in terms of including <nick/> payload in <message/> ore @presence@) doesn't define handling of such. From the specification it looks like it's more of a client-side signalling protocol and receiving contact client should display such suggested nickname to the contact but it's to the contact (to whom we've send the packet) to define the handle for the roster item. This would be consistent with the general idea in XMPP should not modify other entity roster (similar to presence sub: "server should not add any contact on user behalf without user confirmation").

Hi,

you are right, but there is a problem here, server does not send this nickname to the receiver of the subscription request, which means nickname will be ignored.

I've just tested it and complete stanza is being delivered to the client.

S:

<presence  to='tigase_1@atlantiscity' type='subscribe'>
  <nick xmlns='http://jabber.org/protocol/nick'>Ishmael</nick>
</presence>

R:

<presence from="admin@atlantiscity" type="subscribe" to="tigase_1@atlantiscity">
<nick xmlns="http://jabber.org/protocol/nick">Ishmael</nick>
</presence>

Tigase doesn't strip Presence stanza.