| Commit message (Collapse) | Author | Age | Files | Lines |
... | |
| | | | | |
|
| | | | |
| | | | |
| | | | |
| | | | | |
defined-condition.
|
| | | | | |
|
| | | | | |
|
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
This most likely was copied from the handling of <retract/>, where it actually
is required by the spec (XEP-0060 §7.2.2.1), but this attribute doesn’t exist
for purge.
|
| |\ \ \ \ |
|
| | | | | | |
|
| | | | | | |
|
| | | | | | |
|
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | | |
It triggers on bidi-related routing where this to/from is flipped.
Removing since I don't think we have ever seen this potential bug.
|
| | | | | | |
|
| | | | | |
| | | | | |
| | | | | |
| | | | | | |
incoming traffic
|
| | | | | | |
|
| | | | | |
| | | | | |
| | | | | |
| | | | | | |
Where did these messages come from???
|
| | | | | |
| | | | | |
| | | | | |
| | | | | | |
These were added by s2sout.lib
|
| | | | | | |
|
| |\ \ \ \ \ |
|
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | | |
The changes in the temporary fork were merged into mainline luasec ca
2013 and included in the 0.5 release in 2014.
|
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | | |
Affiliation data is passed as a loop variable so no need to retrieve it
|
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | | |
A protocol built on this API now allows showing a list of unread
conversations with a counter, ordered by either oldest or newest
message, along with the text body itself.
|
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | | |
For completeness along with most recent timestamp. Might be nice to be
able to order by oldest unread message.
|
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | | |
Clients may want to show a list of conversations ordered by how
timestamp of most recent message.
The counts allow a badge with unread message counter.
|
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | | |
Eg might want to include last message, timestamp, chat state or other info.
|
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | | |
(thanks MattJ)
|
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | | |
instead of SHA-1
This will currently require a hard reset of all passwords back to plain.
This will be least painful on new deployments.
|
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | | |
Last remaining nice feature from mod_profile.
Allows setting eg nickname and avatar as completely public while
restricting private details in vcard4 to only contacts.
|
| |\ \ \ \ \ \ |
|
| | | | | | | | |
|
| | | | | | | | |
|
| | | | | | | |
| | | | | | | |
| | | | | | | |
| | | | | | | | |
vcard-temp -> vcard4 worked previously but not the other way around
|
| | | | | | | | |
|
| | | | | | | |
| | | | | | | |
| | | | | | | |
| | | | | | | |
| | | | | | | |
| | | | | | | |
| | | | | | | |
| | | | | | | |
| | | | | | | |
| | | | | | | |
| | | | | | | |
| | | | | | | | |
`remote-server-not-found` is reported for problems occurring without a
reply `<stream>` having been opened, e.g. DNS records were not found or
no TCP stream could be established to a functioning XMPP entity.
`remote-server-timeout` is reported for problems that occurring after a
stream has been opened, such as configuration problems, inability to
perform TLS or unsuccessful certificate validation.
Related: #770
|
| | | | | | | |
| | | | | | | |
| | | | | | | |
| | | | | | | |
| | | | | | | |
| | | | | | | | |
Taken care of by loggingmanager now
Mass-rewrite using lua pattern like `tostring%b()`
|
| | | | | | | |
| | | | | | | |
| | | | | | | |
| | | | | | | |
| | | | | | | | |
This should be simpler and more efficient, as well avoid problems caused
by using filters.
|
| |\ \ \ \ \ \ \ |
|
| | | | | | | | |
| | | | | | | | |
| | | | | | | | |
| | | | | | | | | |
Don't need to construct it from components again
|
| | | | | | | | | |
|
| | | | | | | | |
| | | | | | | | |
| | | | | | | | |
| | | | | | | | | |
`data` is a stanza and always truthy
|
| | | | | | | | | |
|
| | | | | | | | | |
|
| | | | | | | | |
| | | | | | | | |
| | | | | | | | |
| | | | | | | | | |
Both now operate on the same complete set of c2s sessions
|
| | | | | | | | |
| | | | | | | | |
| | | | | | | | |
| | | | | | | | | |
easier reuse
|
| | | | | | | | |
| | | | | | | | |
| | | | | | | | |
| | | | | | | | | |
This way both incomplete connections and hibernating c2s sessions are shown.
|
| | | | | | | | |
| | | | | | | | |
| | | | | | | | |
| | | | | | | | |
| | | | | | | | | |
#results is only correct for backwards queries, the table is unused for
forward queries.
|
| | | | | | | | | |
|
| | | | | | | | |
| | | | | | | | |
| | | | | | | | |
| | | | | | | | |
| | | | | | | | | |
Helps when trying to figure out why some queries fail, ie when paging
using an archive id that doesn't exist.
|
| | | | | | | | |
| | | | | | | | |
| | | | | | | | |
| | | | | | | | |
| | | | | | | | | |
The storage engine will usually make a lot of noise for serious errors,
but not always.
|
| | | | | | | | |
| | | | | | | | |
| | | | | | | | |
| | | | | | | | | |
Saves you from counting messages sent
|
| | | | | | | | |
| | | | | | | | |
| | | | | | | | |
| | | | | | | | | |
Should make it easier to find related log messages
|
| | | | | | | | | |
|