| Commit message (Collapse) | Author | Age | Files | Lines |
... | |
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
|
|
|
|
| |
XEP-0060 4.1 Affiliations
> All affiliations MUST be based on a bare JID
|
|
|
|
|
| |
This fixes eg publishing from a full JID when the affiliation has been
set on the bare JID, as would be common in XMPP.
|
|
|
|
| |
access
|
| |
|
|
|
|
|
|
| |
No need to be set as owner, it has all privileges anyways. Since it’s a
boolean instead of a string, its presence may cause weirdness in other
code expecting all affiliations to be string JIDs.
|
| |
|
| |
|
| |
|
| |
|
|
|
|
| |
max_items changes
|
| |
|
|
|
|
| |
subscribe)
|
|
|
|
| |
(thanks jonasw)
|
|
|
|
| |
form (util.pubsub should be protocol-agnostic)
|
|
|
|
|
| |
util.pubsub should stay agnostic of what data types are published and
this depended on util.stanza
|
| |
|
| |
|
|
|
|
| |
back to creating a new one
|
|
|
|
| |
by modules)
|
| |
|
|
|
|
|
| |
This makes the backend able to obtain the publisher without changing
the API.
|
|
|
|
|
| |
This allows the backend to know the node name, when it needs to
differentiate it at storage for example.
|
|
|
|
| |
using util.cache (thanks walduhu)
|
| |
|
| |
|
| |
|
|
|
|
| |
return them in a table at the end
|
| |
|
|
|
|
| |
to 20)
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
|
|
|
| |
(thanks jonas)
|
| |
|
| |
|
| |
|
| |
|
| |
|