Age | Commit message (Collapse) | Author |
|
|
|
|
|
|
|
ref #3273
|
|
ref #3273
|
|
fix #3273
|
|
|
|
fix #3339
|
|
|
|
|
|
|
|
fix #3337
Because apparently the IDs are not always incrementing. We still use them to
know the order of two messages that were received at the same second (in
this case, the ID will always be incrementing).
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Because it’s only supported in gcc>=5.0
|
|
|
|
|
|
fix #3325
|
|
fix #3320
|
|
fix #3324
|
|
|
|
fix #3328
|
|
We check that the device and inode numbers are actually the same as the
JOURNAL_STREAM value, instead of just checking that the value exists.
This fixes the logger unit tests
|
|
|
|
|
|
These requests are only meant to be received by the room itself. The
participant must answer with not-implemented instead.
fix #3323
|
|
fix #3322
|
|
See https://xmpp.org/extensions/xep-0045.html#privatemessage
fix #3321
|
|
|
|
|
|
Fix a somewhat big memory leak
|
|
|