#1643 OMEMO bundle option max_items=max is not supported
Reporter
Maximilian Wuttke
Owner
Zash
Created
Updated
Stars
★ (1)
Tags
Compliance
Status-Fixed
Priority-Medium
Type-Defect
Milestone-0.12
Maximilian Wuttke
on
According to <https://xmpp.org/extensions/xep-0384.html#impl>:
> The pubsub service MUST support 'max' as a value for the 'pubsub#persist_items' node configuration.
However, setting `pubsub#max_items=max` in the bundle publishing stanza (cf. Example 3 in XEP 0384) yields the following error:
> error: max_items: not a number
Zash
on
Thanks for the report.
We don't want to implement it like that, since we like the type validation we added to our data-form parser.
After some debate in the XSF it was decided to do this another way, and we are currently waiting for https://github.com/xsf/xeps/pull/988 to assign a name for it.
There's already code written and will be merged after that.
Changes
owner Zash
tags Status-Blocked
Zash
on
XSF PR merged. Unfortunately there's a piece missing, XEP-0122 says that a registered prefix is needed, but no such prefix was registered.
Did some work to get the Prosody branch into shape, but it's still missing that prefix.
Clients probably wouldn't care about that anyway, so doesn't have to block merging.
Will likely merge it into 0.12/trunk.
According to <https://xmpp.org/extensions/xep-0384.html#impl>: > The pubsub service MUST support 'max' as a value for the 'pubsub#persist_items' node configuration. However, setting `pubsub#max_items=max` in the bundle publishing stanza (cf. Example 3 in XEP 0384) yields the following error: > error: max_items: not a number
Thanks for the report. We don't want to implement it like that, since we like the type validation we added to our data-form parser. After some debate in the XSF it was decided to do this another way, and we are currently waiting for https://github.com/xsf/xeps/pull/988 to assign a name for it. There's already code written and will be merged after that.
ChangesXSF PR merged. Unfortunately there's a piece missing, XEP-0122 says that a registered prefix is needed, but no such prefix was registered. Did some work to get the Prosody branch into shape, but it's still missing that prefix. Clients probably wouldn't care about that anyway, so doesn't have to block merging. Will likely merge it into 0.12/trunk.
ChangesDone in https://hg.prosody.im/trunk/rev/6641ca266d94 Still waiting for https://github.com/xsf/registrar/pull/37
Changes