aboutsummaryrefslogtreecommitdiff
path: root/src/client/QXmppMessageReceiptManager.cpp
Commit message (Collapse)AuthorAgeFilesLines
* Introduce QXmppTask & QXmppPromiseLinus Jahn2023-01-031-0/+1
| | | | | | Closes #502. Co-authored-by: Jonah Brüchert <jbb@kaidan.im>
* Disable Qt keywords completelyLinus Jahn2022-12-261-1/+1
| | | | | | | | | | | | | | | Previously we had the policy that no qt keywords were allowed in headers that may be included by users. However since there was no automatic test verifying that in some places keywords were still used. This now disables qt keywords completely, also in tests and examples. Qt keywords are in general no good or really good idea as they even conflict with the standard library (`emit` at least). In some cases in the examples I just removed the slot tag if the functions didn't need to be slots (anymore). Closes #503.
* Stanza: Move E2eeMetadata into own header fileLinus Jahn2022-07-111-0/+1
|
* MessageReceiptHandler: Implement MessageHandlerLinus Jahn2022-05-201-10/+4
|
* Convert copyright headers to REUSELinus Jahn2022-01-141-23/+4
|
* Update copyright years (2022 edition)Linus Jahn2022-01-091-1/+1
|
* Update copyright headers to 2021Linus Jahn2021-02-191-1/+1
|
* QXmppMessageReceiptManager: Ignore all error messagesLinus Jahn2020-07-031-1/+4
| | | | | Not only receipt requests, but also receipts from error messages should not be used.
* QXmppMessageReceiptManager: Fix receipts are sent on error messages (#269)Blue2020-03-271-1/+1
| | | This fixes that behaviour and extends the tests for QXmppMessageReceiptManager.
* Run clang-format also on all cpp filesLinus Jahn2020-02-031-5/+2
|
* clang-format: Enable regrouping and sorting of includesLinus Jahn2020-02-031-3/+3
|
* Bump copyright year to 2020Linus Jahn2020-01-061-1/+1
|
* MessageReceiptManager: Don't accept receipts from other resourcesLinus Jahn2019-05-051-1/+7
| | | | | | | | | | | | | | | | | | | | | | | | | | | There were some problems with buggy clients leading to that some messages were already marked as received, even though only another resource of the used account has got the message. Here is an example: [outgoing]: <message id="tH9OkRw" to="42@example.com" from="lnj@kaidan.im/kaidan.PR29" type="chat"> <body>test</body> <n1:request xmlns:n1="urn:xmpp:receipts"/> </message> [incoming]: <message to="lnj@kaidan.im/kaidan.PR29" from="lnj@kaidan.im/dino.dc02d539" id="410b33c3-1cd3-433e-8699-74a7583c2560"> <n1:received xmlns="urn:xmpp:receipts" id="tH9OkRw"/> </message> Here the other client "dino.dc02d539" sent an <received/> tag, although it actually received this message over carbons. To avoid that we need to ignore messages also from our bare JID.
* Bump copyright year to 2019Jeremy Lainé2019-01-081-1/+1
|
* clarify the fact QXmppConstants_p.h is not APIJeremy Lainé2016-09-081-1/+1
|
* update project homepageJeremy Lainé2014-03-281-1/+1
|
* update project homepageJeremy Lainé2014-03-271-1/+1
|
* update copyright notice to 2008-2014Jeremy Lainé2014-03-261-1/+1
|
* doc fixesJeremy Lainé2012-07-211-0/+2
|
* update copyright yearJeremy Lainé2012-07-181-1/+1
|
* start moving client-specific codeJeremy Lainé2012-02-081-0/+72