Relay pubsub/PEP to bare JID for MUC occupant JIDs

[mwild1]

Is your feature request related to a problem? Please describe.

• When sending stanzas to a MUC occupant JID (i.e. room@service/nick), those stanzas are typically forwarded to the occupant's real full JID. This behaviour is usually correct.
• However, certain <iq/> requests to a user should be addressed to the user's account (bare JID) instead of one of their devices (full JID).
• Such requests include vcard-temp, as well as requests to PEP nodes.
• ejabberd already routes vcard-temp requests to the bare JID :+1:
• ejabberd does not currently route pubsub/PEP queries to the bare JID :-1:

Describe the solution you'd like

The current behaviour implemented for the vcard-temp namespace should be extended to include at least http://jabber.org/protocol/pubsub and possibly urn:ietf:params:xml:ns:vcard-4.0 (Prosody also does the latter, but general consensus has been to remove the custom iq from the vcard4 XEP, so it may be deprecated soon).

This change would allow clients to support OMEMO, vCard4 and other PEP-based protocols within MUCs.

[poVoq]

Specifically, this would allow sending OMEMO encrypted PMs in an unencrypted public channel, which already works on Prosody hosted MUCs and some clients.

[licaon-kter]

MUC-PM, this is when one user is a moderator/admin/owner so they see real XMPP address of the other?

[mwild1]

With this change implemented, the users will not need to see real JIDs for OMEMO to work.

[prefiks]

So does this require anything else than relying of <pubsub xmlns="http://jabber.org/protocol/pubsub"> queries?

[prefiks]

I commited d961f7f667b0c21f5256c1ba0c61878ea6754d74 that should be doing this.

[prefiks]

Make that 62d3d7a32d2dbae84dc16a85cd389ab814cefc15

[mwild1]

So does this require anything else than relying of <pubsub xmlns="http://jabber.org/protocol/pubsub"> queries?

Nope, that should be all :)

[mremond]

As I understand it, it should work now with ejabberd 23.10.