| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
|
|
| |
outdated config
Only max_items is used anyways
|
| |
|
| |
|
| |
|
| |
|
|
|
|
| |
now persistent
|
| |
|
|
|
|
|
| |
The ‘item’ argument is optional, so it needs to handle it not being
included, or util.stanza will throw an error in add_child
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
|
|
|
|
|
|
| |
supported yet)
This was actually to silence luacheck warnings options andoptions_tag
variables.
|
| |
|
| |
|
|
|
|
| |
See https://xmpp.org/extensions/xep-0060.html#impl-body
|
|
|
|
|
| |
This adds support for the pubsub#notification_type field in the node
config form.
|
|
|
|
|
|
|
| |
https://xmpp.org/extensions/xep-0060.html#impl-bounce
> a pubsub service SHOULD ensure that the <message/> stanza for each
> event notification it generates possesses an 'id' attribute with a
> value
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
|
|
|
| |
(thanks lovetox)
|
| |
|
|
|
|
| |
[luacheck]
|
| |
|
| |
|
| |
|
| |
|
|
|
|
| |
form (util.pubsub should be protocol-agnostic)
|
|
|
|
| |
It confused pubsub.lib handler names with util.pubsub service methods
|
| |
|
| |
|
|
|
|
| |
pubsub#max_items to prevent unbounded query (thanks Martin and lovetox)
|
| |
|
| |
|
|
|
|
| |
on archive storage
|
| |
|
|
|
|
| |
are also persisted)
|
| |
|
| |
|
| |
|