aboutsummaryrefslogtreecommitdiffstats
path: root/src/main/java/de/pixart/messenger/xmpp (unfollow)
Commit message (Collapse)AuthorFilesLines
2020-02-10catch more exceptions in JingleSocks5TransportChristian Schneppe1-1/+1
2020-02-05Networkstack: easy happy eyeball (#411)genofire1-68/+32
* Networkstack: easy happy eyeball * Networkstack: drop own implementation of DNS-Server selection Co-authored-by: Christian Schneppe <kriztan@users.noreply.github.com>
2020-01-31small jingle fixesChristian Schneppe1-2/+2
possibly fixes #417, but I couldn't check this, because I can't reproduce the problems. Feel free to reopen it with updated logs.
2020-01-24support registration via pars tokensChristian Schneppe1-1/+25
2020-01-02reset XmppConnection to parentChristian Schneppe1-1/+1
2019-12-24createOutputStream(): allow to disable decryptionChristian Schneppe1-1/+1
2019-12-13rework adhocinviteChristian Schneppe1-1/+3
2019-12-09jingle ibb: wait to receive ibbChristian Schneppe3-36/+53
previously we signalled succesfull file reception after receiving enough bytes on ibb; however that causes us to race with the session-info file hash. now the recipient will wait for <close/> and the sender will make sure to send the session-info before sending close.
2019-11-15check if sender is in contact list before accepting jingle fileChristian Schneppe1-2/+3
2019-11-15allow jingle state transition for fallback after proxy failureChristian Schneppe1-2/+6
2019-11-15make jingle state transitions less error proneChristian Schneppe1-2/+28
2019-10-26bookmarks2. introduce #compat namespaceChristian Schneppe2-1/+3
2019-10-26support for purge and deleteChristian Schneppe1-1/+1
2019-10-26support for delete bookmarks2Christian Schneppe1-1/+6
2019-10-26WIP Bookmarks 2 supportChristian Schneppe1-0/+9
2019-10-26show reason in error messageChristian Schneppe1-1/+6
2019-10-26mark cancelled jingle ft as such on both sidesChristian Schneppe3-75/+101
2019-10-26fully read port in socks connectionChristian Schneppe1-2/+3
incoming direct connections in receive mode wouldn’t clear the entire destination from the input stream; thus adding a leading 0x00 to the file
2019-10-26set shorter timeouts when using direct candidatesChristian Schneppe3-6/+13
2019-10-02report not-acceptable on jingle errorsChristian Schneppe2-19/+16
2019-09-20close correct socket after faulty jingle socks connectionChristian Schneppe1-1/+1
2019-09-20migrate to AndroidXChristian Schneppe2-2/+2
2019-09-12show language in message bubble if multiple language variants were receivedChristian Schneppe2-3/+5
XML and by inheritence XMPP has the feature of transmitting multiple language variants for the same content. This can be really useful if, for example, you are talking to an automated system. A chat bot could greet you in your own language. On the wire this will usually look like this: ```xml <message to="you"> <body>Good morning</body> <body xml:lang="de">Guten Morgen</body> </message> ``` However receiving such a message in a group chat can be very confusing and potentially dangerous if the sender puts conflicting information in there and different people get shown different strings. Disabling support for localization entirely isn’t an ideal solution as on principle it is still a good feature; and other clients might still show a localization even if Conversations would always show the default language. So instead we now show the displayed language in a corner of the message bubble if more than one translation has been received. If multiple languages are received we will attempt to find one in the language the operating system is set to. If no such translation can be found it will attempt to display the English string. If English can not be found either (for example a message that only has ru and fr on a phone that is set to de) it will display what ever language came first. Furthermore we will discard (not show at all) messages with with multiple bodies of the same language. (This is considered an invalid message) The language tag will not be shown if we receive a single body in a language not understood by the user. (For example operating system set to 'de' and message received with one body in 'ru' will just display that body as usual.) As a guide line to the user: If you are reading a message where it is important that this message is not interpreted differently by different people (like a vote (+1 / -1) in a chat room) make sure it has *no* language tag.
2019-09-09do not include scope in ipv6 annoucmentChristian Schneppe1-1/+12
2019-09-06JET uses plain text file sizeChristian Schneppe1-2/+9
2019-09-06do not include link local in direct candidatesChristian Schneppe3-16/+12
2019-09-06make Tor connections work with direct TLSChristian Schneppe1-60/+48
2019-09-06implemented support for for jingle encrypted transports (XEP-0396)Christian Schneppe2-10/+37
2019-09-06deleted wrong to jidChristian Schneppe1-1/+0
fixes #374
2019-09-03fix some crashesChristian Schneppe2-6/+22
2019-09-03use higher priority for proxy on receiving endChristian Schneppe2-5/+4
2019-09-03send fallback to ibb after proxy activation failedChristian Schneppe1-6/+17
2019-09-03also reply with direct connections on responseChristian Schneppe2-18/+34
2019-09-03bare minimum direct connectionsChristian Schneppe4-6/+153
2019-09-03order canditates by priority before attempting to connectChristian Schneppe2-25/+27
2019-08-31more ibb fixes (include sid in transport-accept)Christian Schneppe2-15/+25
2019-08-31fixed unlikely race between enabling carbons and discovering last MAM idChristian Schneppe1-3/+3
2019-08-31fixed pgp decryption of automatically accepted jingle ftChristian Schneppe1-10/+7
2019-08-31increased reconnection interval after policy violationChristian Schneppe1-1/+3
2019-08-31refactored filename and extension parsingChristian Schneppe1-32/+32
2019-08-31create empty disco result on error to fire advance stream features eventChristian Schneppe1-1/+14
2019-08-31fix SOCKS5 to IBB fallbackChristian Schneppe1-5/+4
2019-07-17use helper method to close socketChristian Schneppe1-10/+3
2019-07-01code cleanup & small fixesChristian Schneppe2-3/+3
2019-06-25Revert "Networkstack - let OS decide IPv4 or IPv6 (#267)"Christian Schneppe1-5/+26
This reverts commit e6a15597904019f68c02e6fd8f61fb6de0b13324. If there is IPv6 available but the server doesn't listen to it, the connection will not be established
2019-06-25implement client support for muc pushChristian Schneppe1-2/+2
Staying connected to a MUC room hosted on a remote server can be challenging. If a server reboots it will usually send a shut down notification to all participants. However even if a client knows that a server was shut down it doesn’t know when it comes up again. In some corner cases that shut down notification might not even be delivered successfully leaving the client in a state where it thinks it is connected but it really isn’t. The possible work around implemented in this commit is to register the clients full JID (user@domain.tld/Conversations.r4nd) as an App Server according to XEP-0357 with the room. (Conversations checks for the push:0 namespace on the room.) After cycling through a reboot the first message send to a room will trigger pubsub notifications to each registered full JID. This event will be used to trigger a XEP-0410 ping and if necessary a subsequent rejoin of the MUC. If the resource has become unavailable during down time of the MUC server the user’s server will respond with an IQ error which in turn leads to the MUC server disabling that push target. Leaving a MUC will send a `disable` command. If sending that disable command failed for some reason (network outage) and the client receives a pubsub notification for a room it is no longer joined in it will respond with an item-not-found IQ error which also disables subsequent pushes from the server. Note: We 0410-ping before a join to avoid unnecessary full joins which can be quite costly. Further client side optimizations will also suppress pings when a ping is already in flight to further save traffic.
2019-06-25fix jingle file transferChristian Schneppe3-4/+4
fixes #360
2019-06-22performance improvement of message expiryChristian Schneppe1-2/+2
2019-06-18self ping (xep-0410) after receiving invite to mucChristian Schneppe1-1/+1
2019-06-17disallow subsequent session-acceptChristian Schneppe1-13/+13