xavi/qxmpp - Fork of the QXmpp library.

	Commit message (Collapse)	Author	Age	Files	Lines
*	CarbonManagerV2: Don't set 'to' address of carbon enable IQ	Linus Jahn	2023-03-14	1	-3/+2
\| \| \| \| \| \| \| \| \| \| \|	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	Melvin Keskin	2023-03-09	1	-3/+5
\|
*	Introduce QXmppTask & QXmppPromise	Linus Jahn	2023-01-03	1	-1/+1
\| \| \| \| \| \|	Closes #502. Co-authored-by: Jonah Brüchert <jbb@kaidan.im>
*	Replace QXmpp::SendError with QXmppError everywhere	Linus Jahn	2022-12-30	1	-7/+9
\| \| \| \|	Part of #501.
*	CarbonManagerV2: Mention messageReceived() can also be used	Linus Jahn	2022-08-17	1	-1/+2
\| \| \| \| \|	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	Linus Jahn	2022-08-17	1	-0/+3
\| \| \| \| \| \|	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	Linus Jahn	2022-08-15	1	-6/+5
\| \| \| \| \|	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	Linus Jahn	2022-08-14	1	-0/+3
\| \| \| \| \|	It's now also possible to see which messages were carbon forwarded when using the CarbonManagerV2.
*	Add new message carbons manager	Linus Jahn	2022-08-14	1	-0/+165
	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.