| Commit message (Collapse) | Author | Age | Files | Lines |
| |
|
| |
|
| |
|
| |
|
|
|
|
| |
The 'publisher' is only on <item> in the schema.
|
|
|
|
| |
broadcast
|
|
|
|
|
|
|
|
| |
This moves some XEP-0060 awkwardness out of util.pubsub and into mod_pubsub
A retraction is broadcast in an <items> container, whereas most other
kinds of broadcasts are in a container with a name matching the 'kind'
attribute.
|
|
|
|
| |
util.pubsub to avoid duplication
|
|
|
|
|
|
| |
unsubscribed but nothing else
Can't revoke their subscriptions on change of access model otherwise
|
|
|
|
|
|
| |
Like ca5228a7d907 did for mod_pep
Thanks pep.
|
|
|
|
| |
There is already a set_service()
|
| |
|
|
|
|
|
| |
'presence' and 'roster' makes more sense for PEP
'auithorize' needs additional code for authorization flow
|
|
|
|
| |
Like aefb96a52f5f
|
|
|
|
| |
extensibility
|
| |
|
| |
|
| |
|
| |
|
|
|
|
| |
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
|
|
|
|
| |
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
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
|
|
|
| |
[luacheck]
|
| |
|
| |
|
|
|
|
| |
It confused pubsub.lib handler names with util.pubsub service methods
|
| |
|
|
|
|
| |
on archive storage
|
|
|
|
| |
are also persisted)
|
| |
|
|
|
|
| |
persistence)
|
| |
|
| |
|
| |
|
| |
|
| |
|
|
|
|
| |
name of the node and always present)
|
|
|
|
| |
does not return true)
|
|
|
|
| |
Flow)
|
| |
|
| |
|
| |
|