| Commit message (Collapse) | Author | Age | Files | Lines |
| |
|
| |
|
| |
|
| |
|
|
|
|
| |
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.
|
| |
|
|\ |
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| |
| |
| |
| | |
users to invite others in a members-only room
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| |
| |
| |
| | |
(previously only owners/admins could do this)
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|