| Commit message (Collapse) | Author | Age | Files | Lines |
| |
|
|
|
|
| |
(thanks Link Mauve/lovetox)
|
|
|
|
| |
(muc_room_allow_public/muc_room_allow_persistent)
|
| |
|
| |
|
|
|
|
| |
each_room
|
| |
|
|
|
|
|
|
|
| |
Lock expiry -> Reset
Admin wants to join -> Reset
Still locked -> cancel, gone
Don't return error in response to an error
|
|
|
|
| |
extensibility
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
|
|
|
| |
configuration format
|
| |
|
| |
|
| |
|
|
|
|
| |
https://xmpp.org/extensions/xep-0060.html#owner-subscriptions-modify
|
|
|
|
| |
https://xmpp.org/extensions/xep-0060.html#owner-subscriptions-retrieve
|
| |
|
|
|
|
| |
and transient
|
| |
|
| |
|
| |
|
| |
|
|
|
|
| |
What does `if can_see_real_jids(whois, occupant) then` do?
|
|
|
|
|
| |
It?s only sent to the creator so no need to have separate variants for
different kinds of participants.
|
| |
|
|
|
|
|
| |
List discussion here:
https://mail.jabber.org/pipermail/standards/2018-July/035228.html
|
|
|
|
| |
somwehere
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
|
|
|
| |
destroyed
|
| |
|
| |
|
| |
|
|
|
|
|
|
| |
outdated config
Only max_items is used anyways
|
|
|
|
|
|
| |
unavailable presence
Related issues: #505, #978
|
|
|
|
| |
useful info
|
| |
|
|
|
|
|
|
|
|
| |
This fixes room creation/joining from Gajim if a password has been set.
Otherwise the muc-occupant-pre-join event hook determines that the given
password differs from the unset password and joining is rejected, which
seems unhelpful.
|
| |
|
|\ |
|
| | |
|