Am Sa., 29. Aug. 2020 um 08:16 Uhr schrieb Ruslan N. Marchenko <[email protected] >:
> > The way I read it initially was "pubsub service MUST support persitent > items" but it seems it really mandates pubsub default config rather than > feature support? > No, and why do you think that? > Then "'max' as value to persisy_items" I persume is a typo and should read > as 'max' value to 'max_items' when used together with 'persist_items'? > > Yes is a typo, should be fixed > After I implemented publish-options, configure-node, persist-items, > multi-items, delete-items (and retract-item which seem to be redundant) I > still see the omemo merely sets access-model to open (as in XEP's example) > but not others. > What do you mean by "omemo merely sets .." what is omemo in that context? > And since my default pep node config is no persist, max 1, pam=presence it > only flips pam to open and the rest remains as is (no persistence, max=1). > Is it just conversations specific or the XEP really mandates defaults on > the PEP node? It should be fairly easy to set the rest of the required > options in publish options instead of mandating the defaults. > Conversations does not implement the XEP version you are referring to, maybe that answers your question. regards Philipp
_______________________________________________ Standards mailing list Info: https://mail.jabber.org/mailman/listinfo/standards Unsubscribe: [email protected] _______________________________________________
