| Commit message (Collapse) | Author | Age | Files | Lines |
... | |
| |
| |
| |
| | |
Meant to reduce user confusion over what's reloaded and not.
|
| |
| |
| |
| |
| | |
This ensures rules in mod_mam apply to some extent. Messages worth
archiving are probably worth sending to other clients.
|
| |
| |
| |
| | |
Ensures that all your clients know about sent messages that failed.
|
| | |
|
| | |
|
|\| |
|
| |
| |
| |
| |
| |
| |
| | |
27f5db07bec9 fixed this wrong. The code is supposed to check if the
stanza is NOT sent to your bare JID. A MUC PM is always sent to your
full JID. Hopefully nobody sends MUC invites to full JIDs, because those
would be skipped by this as well.
|
| | |
|
| |
| |
| |
| |
| |
| | |
This is the subset of mod_mam rules I believe makes sense in MUC.
Note that mod_muc_mam does not have its own rules, but uses these.
|
| |
| |
| |
| | |
This isn't normal, but is it invalid? Likely a client bug in any case.
|
| |
| |
| |
| |
| | |
Unclear if clients normally ever send error messages, but there may be
locally generated bounces sent on behalf of local sessions.
|
| |
| |
| |
| |
| | |
Should be more obvious that all iq stanzas are considered important.
Changes behavior for invalid things in the default namespace.
|
| | |
|
| |
| |
| |
| |
| | |
This case was previously handled by fall-trough at the end of the
function.
|
| |
| |
| |
| | |
This was already the case for presence and iq stanzas but not messages.
|
| |
| |
| |
| | |
Copy-paste mistake presumably
|
| |
| |
| |
| |
| | |
When the reason is reported as an util.error object the `reason` field
is empty and the reason text should be extacted from the error object.
|
| |
| |
| |
| | |
Probably because autocomplete.
|
| |
| |
| |
| | |
(thanks Ge0rG)
|
| |
| |
| |
| | |
Causes util.stanza to throw an error, which helps detect mistakes
|
| | |
|
| |
| |
| |
| |
| |
| |
| |
| | |
The 'max' 'count' and 'index' fields are integers and should be encoded
as such on the wire.
Care needs to be taken because tostring(1.0) in Lua 5.3+ returns to "1.0"
while in previous Lua versions it would return "1".
|
| | |
|
| |
| |
| |
| | |
Based on examples from XEP-0059
|
| | |
|
|\ \ |
|
| | |
| | |
| | |
| | | |
Logic using full vs bare JID addressing may return in the future.
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
The intent was to not store MUC groupchat messages, which are sent from
the MUC to local full JIDs, while allowing for potential future
account based group chat. However, since this function handles messages
in both directions and outgoing MUC messages are sent to the bare room
JID, those were stored.
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
In Lua 5.3 difftime() takes integers as argument but returns a float,
and then tostring() serializes it with a decimal point. This violates
XEP-0012.
Like #1536
|
| | | |
|
| | |
| | |
| | |
| | | |
Somehow it got SHA1's 20 byte output instead of the proper 32 = 256/8
|
| | | |
|
| | |
| | |
| | |
| | |
| | | |
Since these XEPs are subject to change we may need come back and double
check these in the future.
|
| | |
| | |
| | |
| | |
| | | |
Makes it possible to learn of delivery failure even if it came bouncing
back while you were offline.
|
| | | |
|
| | |
| | |
| | |
| | |
| | | |
no-store is used in an example in XEP-0313, so obviously this is the
preferred hint
|
| | |
| | |
| | |
| | | |
If it is with a body then it execution does not get this far
|
| | | |
|
| | |
| | |
| | |
| | |
| | |
| | | |
The intent is to capture errors to stanzas sent by the local user, so
that they can see why a message failed to be delivered even if the error
came after they went offline.
|
| | |
| | |
| | |
| | | |
Happy now Ge0rG?
|
| | |
| | |
| | |
| | | |
Mostly just lifted from mod_csi_simple
|
| | |
| | |
| | |
| | | |
Improved readability and early returns definite yes/no answer.
|
| | |
| | |
| | |
| | |
| | | |
This is based on code in mod_csi_simple and aiming towards being more
flexible and maintainable than a couple of tests for when not to store.
|
| | |
| | |
| | |
| | |
| | | |
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
|
| | |
| | |
| | |
| | | |
When run on Lua 5.3 produces an issue similar to #1536
|
| | |
| | |
| | |
| | |
| | | |
Once the Prosody is up, who cares when it comes down?
That's not my department, says scanison.
|
| | |
| | |
| | |
| | | |
The passage of time does not need test coverage, just look in a mirror.
|
| | |
| | |
| | |
| | | |
Why was this module enabled in the config for tests if it wasn't tested?
|