diff options
author | Maximilian Wuttke <mwuttke97@posteo.de> | 2021-03-09 17:48:29 +0100 |
---|---|---|
committer | Maximilian Wuttke <mwuttke97@posteo.de> | 2021-03-09 17:48:29 +0100 |
commit | 2b1ada772256a9a661eabedf723702af5f6bfa83 (patch) | |
tree | 1a7598c6cbd07300d135254a916a13e3bc2b6d88 /docs/profanity.1 | |
parent | 68469149cd960a5a8fb9cd6ec4a5dd4ca139a4a7 (diff) | |
download | profani-tty-2b1ada772256a9a661eabedf723702af5f6bfa83.tar.gz |
[OMEMO]: Fix bundle publishing
Use the following options in `omemo_bundle_publish()`: - "pubsub#persist_items" = "true" - "pubsub#access_model" = "open" The same options are also used in Gajim. I've tested this on two different servers. The bundle was successfully added as a new PEP node. Test cases: 1. Normal use on my main account 2. Log in into a fresh tesst account on a different server 3. `/omemo clear_device_list`. In this case, the client(s) may have to be restarted. Note: In `_omemo_bundle_publish_result`, there's a route that is taken when the bundle publish stanza failed. In this case, the node is configured manually, i.e. the access_model is set to 'open'. I have manually tested this case, but this case didn't naturally occur for me. Note: The option "pubsub#max_items=max" is REQUIRED for the bundle publication, as per XEP-0384. However, this is not done in other clients (I've checked the source code of Gajim and Conversations), and it is also not supported by Prosody. Cf. <https://github.com/xsf/xeps/pull/988>.
Diffstat (limited to 'docs/profanity.1')
0 files changed, 0 insertions, 0 deletions