| Commit message (Collapse) | Author | Age | Files | Lines |
|---|
| |
|
|
|
| |
Logging of 'why not' is already done. Why not both? Will make more sense
when the rules evolve a bit.
|
| |
|
|
|
| |
Meant to improve readability and ease further improvements to this
algorithm.
|
| |
|
|
|
| |
Both mediated invites defined by XEP-0045: Multi-User Chat and direct
invites defined by XEP-0249: Direct MUC Invitations
|
| | |
|
| | |
|
| | |
|
| |
|
|
| |
Improves readability, easier to see structure.
|
| |
|
|
|
|
|
|
| |
It is somewhat ambiguous where an error really comes from in the case of
an external component.
Setting by to the bare host at least distinguishes it from JIDs with a
node- or resourcepart.
|
| | |
|
| |
|
|
| |
presence
|
| |
|
|
| |
occupant presence
|
| |\ |
|
| | |
| |
| |
| | |
On error, the second return value is the error condition, not the third.
|
| | |
| |
| |
| | |
Backport of f90abf142d53 from trunk
|
| |\| |
|
| | | |
|
| | |
| |
| |
| |
| |
| |
| |
| | |
The LuaSec :info() method gathers info using the OpenSSL function
SSL_get_current_cipher(). Documentation for this function states that it
may return NULL if no session has been established (yet). If so, the
LuaSec functions wrapping this return nil, triggering a nil-indexing
error in mod_admin_telnet.
|
| | | |
|
| | |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
This gives service admins a way to set an arbitrary affiliation in any
room. Enables various administrative use cases such as room ownership
reassignment or recovery.
Reduces the need for the admins-as-owners feature, as this can be used
by admins to make themselves owner in any room when needed, instead of
being owners all the time.
|
| | |
| |
| |
| |
| |
| |
| |
| | |
RFC 6121 §3.4 says:
> If a server supports subscription pre-approvals, then it MUST
> advertise the following stream feature during stream negotiation.
The feature itself (#686) was added in f0e9e5bda415
|
| | |
| |
| |
| |
| |
| |
| |
| | |
Based on the currently-deferred XEP-0317. The protocol differs
a little (because XEP-0317 is incomplete), therefore currently
we use a custom namespace.
The plan is to update and finish XEP-0317.
|
| | | |
|
| | |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
Changing the default setting of `new_muc_storage_format` from false to true.
The code supports reading both formats since 0.11, but servers with MUCs stored
using the new format will not be able to downgrade to 0.10 or earlier.
The new format is clearer (less nesting for the most commonly-accessed data),
and combined with the new map-store methods, allows for some operations to become
more efficient (such as finding out which MUCs on a service a given user is affiliated
with).
|
| | |
| |
| |
| | |
Activated when muc#roomconfig_presencebroadcast includes the "none" role.
|
| | | |
|
| | |
| |
| |
| |
| |
| | |
Detailed explanation in de607875d4bd. A presence with role="none"
(which is always type="unavailable") should only be broadcast if
available presence was previously broadcast for that occupant.
|
| | |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
Currently there is what amounts to a hack in presence_broadcast.lib.lua to
make it always broadcast presence with roles of "none". This is to ensure
that if you previously saw available presence for someone, you will also
see the unavailable presence (which always has role="none").
The correct approach is to take into account what the previous role was (
i.e. answer the question: "Was the available presence for this occupant
a role for which presence broadcast is enabled?).
The logic is already in place to do this correctly, but most call sites
do not provide the previous role (prev_role argument) of the occupant,
which causes it to not be used. In its place the hack to always broadcast
presence of role="none" has allowed things to continue to work.
The intention is that a subsequent commit will remove the unconditional
broadcast of role="none".
|
| |\| |
|
| | |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
(fixes #1504)
This lets Prosody handle socket related work between each step in the
cleanup in order to prevent the server from being completely blocked
during this.
An async storage backend would not need this but those are currently
rare.
|
| | | |
|
| | | |
|
| | | |
|
| | | |
|
| |\| |
|
| | | |
|
| |\| |
|
| | |
| |
| |
| | |
Caused by a plugin sending a message from the room itself.
|
| | | |
|
| | | |
|
| | |
| |
| |
| |
| | |
Lets you select what hosts to list http services on. In particular, this
enables listing global http services, which was not possible before.
|
| | |
| |
| |
| |
| | |
This seems to be the one place handling MUC-PMs. This event is added so that
plugins (such as muc_occupant_id) can edit them without having to redo the work.
|
| | |
| |
| |
| | |
the latter
|
| | |
| |
| |
| |
| |
| |
| | |
get_hosts_with_module(a component, mod) would still filter out
components since they don't have type="component" instead of "local"
Introduced in 4d3549e64489
|
| | | |
|
| |\| |
|
| | |
| |
| |
| |
| | |
0c00274528a4 moved it one step too far, so the check was performed
before connecting to the database instead of after.
|
| | |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
When responding to a ping from elsewhere in the same Prosody the send
function will be host_send from core.hostmanager, which does not return
anything. Tailcalling it therefore lets the iq event fall trough to
handle_unhandled_stanza in core.stanza_router, which responds with an
error. This error also goes into handle_unhandled_stanza which discards
it.
Noticed because I have a module that points out when a stanza error
reply is created without a text argument.
|
| |\| |
|
| | |
| |
| |
| |
| | |
The check was only performed if sql_manage_tables was set to true (the default)
It should always be performed
|
| | | |
|
