| Commit message (Collapse) | Author | Age | Files | Lines |
| | |
|
| |
|
|
| |
Co-authored-by: Melvin Keskin <melvo@olomono.de>
|
| |
|
|
|
|
|
| |
This adds parsing, serialization and a test for the 'register' stream
feature of XEP-0077: In-Band Registration.
Co-authored-by: Linus Jahn <lnj@kaidan.im>
|
| |
|
|
|
| |
This adds parsing and serialization for XEP-0367: Message Attaching in
version 0.3.0.
|
| |
|
|
|
| |
Without this option `make` tool stops build after
first found build error.
|
| | |
|
| | |
|
| | |
|
| | |
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
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.
|
| |
|
|
|
| |
This implements the IQs for requesting and receiving upload slots as
defined by XEP-0363: HTTP File Upload in version 0.9.0.
|
| | |
|
| |
|
| |
I think this looks better.
|
| |
|
|
|
| |
The changes in the XEP only affected parts we haven't implemented yet,
so updating was rather easy.
|
| |
|
|
| |
This adds parsing and serialization of spoilers in the QXmppMessage class.
|
| |
|
|
|
|
|
|
|
| |
This implements the pubsub items for the MIX participants and info node
as defined by XEP-0369: Mediated Information eXchange (MIX) in version
0.14.2.
https://xmpp.org/extensions/xep-0369.html#participants-node
https://xmpp.org/extensions/xep-0369.html#info-node
|
| |
|
| |
The GuiClient / example 4 has been removed.
|
| |
|
|
|
|
|
|
| |
This adds the MIX extensions for roster queries as defined in XEP-0405:
Mediated Information eXchange (MIX): Participant Server Requirements in
version 0.4.0.
https://xmpp.org/extensions/xep-0405.html#mix-roster-capability-sharing
|
| |
|
|
|
|
|
|
| |
This implements the new presence extension defined by XEP-0405: Mediated
Information eXchange (MIX): Participant Server Requirements in version
0.4.0.
https://xmpp.org/extensions/xep-0405.html#usecase-user-presence-receive
|
| |
|
|
|
|
|
| |
This implements the new message extension specified by XEP-0369: Mediated
Information eXchange (MIX) in version 0.14.2.
https://xmpp.org/extensions/xep-0369.html#usecase-user-message
|
| | |
|
| | |
|
| | |
|
| |
|
|
|
|
| |
This implements all used IQ queries of XEP-0369: Mediated Information
eXchange (MIX) (v0.14.1) and XEP-0405: Mediated Information eXchange (MIX):
Participant Server Requirements (v0.3.1), including unit tests.
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
The previous logic was:
- use the preferred SASL mechanism if available
- otherwise use the first supported mechanism offered by the server
However RFC 6120, section 6.3.3 states:
"The initiating entity MUST maintain its own preference order independent
of the preference order of the receiving entity."
The new logic is:
- order our supported mechanisms from most secure to least secure
- if the user sets QXmppConfiguration::saslMechanism, put it first
- use the best mechanism supported by the server
|
| | |
|
| |
|
|
| |
See: https://bugs.debian.org/919487
|
| |
|
|
|
|
| |
Some tests are disabled by default as they require exporting additional
symbols which are not part of the public API. The BUILD_INTERNAL_TESTS
option makes it possible to enable these additional tests.
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| |
|
|
| |
See: https://en.wikipedia.org/wiki/MacOS
|
| | |
|
| |
|
|
|
|
| |
The QXmppVersionManager will use QSysInfo in Qt 5.4 or later to
determine the client's OS, so it will also contain the OS version or
some codenames.
|
| | |
|
| |
|
|
|
| |
Today this is most important for attaching URLs generated by XEP-0363:
HTTP File Upload for a very basic form of media/file sharing.
|
| | |
|
| | |
|
| |
|
|
|
| |
This commit is based on a pull request by fbeutel (GitHub) (see #87) and
was rebased and slightly modified by me.
|
| | |
|
| | |
|
| |
|
|
| |
Closes: #158
|
| | |
|
| |
|
|
| |
This fixes #141.
|