18
edits
Difference between revisions of "XEP-Remarks/XEP-0373: OpenPGP for XMPP"
Jump to navigation
Jump to search
XEP-Remarks/XEP-0373: OpenPGP for XMPP (view source)
Revision as of 19:11, 30 August 2018
, 19:11, 30 August 2018Add note about Singleton Node
(Add note about Singleton Node) |
|||
| Line 9: | Line 9: | ||
* Use a timestamp, possibly in XEP-0082 DateTime profile format, as item IDs | * Use a timestamp, possibly in XEP-0082 DateTime profile format, as item IDs | ||
* Use a fixed string for the PubSub/PEP node names (like it is already done right now for the metadata nodes) | * Use a fixed string for the PubSub/PEP node names (like it is already done right now for the metadata nodes) | ||
* Use Singleton Node (XEP-0060) for the metadata node, public key node, secret key node. The option max_items=1 when retrieving the node content is an optional feature not supported by all servers. There is no need to have more than one item in these nodes, there should at any point always only one public key list, one public key per public key node and one secret key item. Force all Clients to publish with the same item id "current" (XEP-0060) to prevent problems with multiple items in the node. | |||
Although there appears to be no direct way to query the PubSub/PEP service if it supports pubsub#deliver_payloads, it may be possible for entities to probe the availability of this feature by attempting to create a "dummy" node where pubsub#deliver_payloads is set to true. IIRC recent changes to XEP-0060 require services to return an error on unknown configuration values. But this is fragile until this requirement is deployed widely. So ultimately, the entity possibly also wants to verify if setting has been respected and became effective. | Although there appears to be no direct way to query the PubSub/PEP service if it supports pubsub#deliver_payloads, it may be possible for entities to probe the availability of this feature by attempting to create a "dummy" node where pubsub#deliver_payloads is set to true. IIRC recent changes to XEP-0060 require services to return an error on unknown configuration values. But this is fragile until this requirement is deployed widely. So ultimately, the entity possibly also wants to verify if setting has been respected and became effective. | ||