Should be noted that this is about mod_pep which implements a bare minimum needed for PEP.
titleQuerying pubsub items using PubSub fails with "service-unavailable"
Hold on, why does it do a service discovery query? I don't see anything in either 384 or 163 mandating support for this.
> Devices MUST subscribe to 'urn:xmpp:omemo:0:devicelist' via PEP
Followed by an example notification that would received after subscribing via the normal PEP +notify method.
Zash: Thats because I use PubSub to query my own device list node
Zash: Smack does a disco query at the node in order to determine, whether it is a LeafNode or a CollectionNode. This is done only once, but fails on prosody.
Here you can find some logs: https://pads.pirateparty.gr/p/nodes
The issue title is not correct. It should be:
> Querying a PEP node using disco#info fails with "service-unavailable".
It is XEP-0060 § 5.3 failing. It appears that XEP-0163 does not explicitly require support for the "Discover Node Information" (XEP-0060 § 5.3) use case, XEP-0163 § 5. only mentions "node discovery". I tend to believe that a PEP service requires support for discovery node information use case, as otherwise we need to resort to ugly workaround in order to determine if a PEP node is a leaf or collection node (Or are all PEP nodes besides the root node required to be leaf nodes?).
titlemod_pep: Querying pubsub items using PubSub fails with "service-unavailable"