xavi/qxmpp/src/client/QXmppCarbonManagerV2.cpp, branch fork Fork of the QXmpp library. https://gitea.privatedns.org/xavi/qxmpp/atom?h=fork 2023-03-14T22:31:52+00:00 CarbonManagerV2: Don't set 'to' address of carbon enable IQ 2023-03-14T22:31:52+00:00 Linus Jahn lnj@kaidan.im 2023-03-14T22:28:54+00:00 urn:sha1:a811aeb01bb0af1197434f73f6f1136e9cdc4873 RFC6120 says we MUST NOT set a to address for such stanzas. From section 8.1.1.1.: 2. A stanza sent from a client to a server for direct processing by the server (e.g., roster processing as described in [XMPP-IM] or presence sent to the server for broadcasting to other entities) MUST NOT possess a 'to' attribute. CarbonManagerV2: Fix enabling carbons 2023-03-09T14:16:17+00:00 Melvin Keskin melvo@olomono.de 2023-03-07T23:39:56+00:00 urn:sha1:5fffebeb5f636e4c050e61df5cd6d60032b55fc2 Introduce QXmppTask & QXmppPromise 2023-01-03T21:05:54+00:00 Linus Jahn lnj@kaidan.im 2022-08-16T19:00:15+00:00 urn:sha1:b17284ee7d674416e0d11f1699f73fcc606262d4 Closes #502. Co-authored-by: Jonah Brüchert <jbb@kaidan.im> Replace QXmpp::SendError with QXmppError everywhere 2022-12-30T22:35:47+00:00 Linus Jahn lnj@kaidan.im 2022-12-30T22:35:47+00:00 urn:sha1:6efebe555d30170c2ecfc2372113f342c513b0c2 Part of #501. CarbonManagerV2: Mention messageReceived() can also be used 2022-08-17T19:30:20+00:00 Linus Jahn lnj@kaidan.im 2022-08-17T19:29:30+00:00 urn:sha1:49b9466e434ac9b4863a1797952696f5bf14b688 Unhandled messages from the message pipeline are passed to the messageReceived() signal of the QXmppClient. CarbonManagerV2: Add ctor/dtor to allow later binary-compatible changes 2022-08-17T19:27:21+00:00 Linus Jahn lnj@kaidan.im 2022-08-17T19:27:21+00:00 urn:sha1:5b24ad448ca6d3ba3ae43c360218709613058fb4 Explicitly adds contructor and destructor, so we can later implement other features (like adding a d-ptr) without affecting binary compatibility. Don't use `using Manager =` to avoid doxygen errors 2022-08-15T11:54:51+00:00 Linus Jahn lnj@kaidan.im 2022-08-15T11:54:51+00:00 urn:sha1:64b69d0d0d3f61aae37969f5e339d6ea33b4a5cf Doxygen doesn't understand that the Manager alias here and in the OMEMO manager are different and so generated a lot of warnings. Message: Add isCarbonForwarded attribute 2022-08-14T15:32:53+00:00 Linus Jahn lnj@kaidan.im 2022-05-06T14:38:47+00:00 urn:sha1:b6d341f649dd12cd884d43fc6d21dfa8f1bdac95 It's now also possible to see which messages were carbon forwarded when using the CarbonManagerV2. Add new message carbons manager 2022-08-14T15:32:53+00:00 Linus Jahn lnj@kaidan.im 2022-08-13T20:12:50+00:00 urn:sha1:cb9a9db0649ce4eda1078f7904504fdfc21043bc The new manager automatically enabled carbons and the user doesn't need to do anything. Messages are injected into the message pipeline of the client instead of using a signal. This makes it possible to decrypt the messages in the next step or do any other possible post-processing on the message. Adapting the old manager was not possible because that would mean major behaviour change that could potentially lead to clients processing message twice.