aboutsummaryrefslogtreecommitdiffstats
path: root/src/main/java/de/pixart/messenger/xmpp (follow)
Commit message (Collapse)AuthorAgeFilesLines
* fix resolving IP if SRV violences RFC2782Christian Schneppe2020-04-071-17/+31
|
* WIP: happy eyeball with dns caching for 5min (#464)genofire2020-02-191-3/+12
| | | | | | * happy eyeball: fix dnssec for plain ip an srv-cname * reimplement dns resolver cache + add timeout for cache
* catch more exceptions in JingleSocks5TransportChristian Schneppe2020-02-101-1/+1
|
* Networkstack: easy happy eyeball (#411)genofire2020-02-051-68/+32
| | | | | | | | * Networkstack: easy happy eyeball * Networkstack: drop own implementation of DNS-Server selection Co-authored-by: Christian Schneppe <kriztan@users.noreply.github.com>
* small jingle fixesChristian Schneppe2020-01-311-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.
* support registration via pars tokensChristian Schneppe2020-01-241-1/+25
|
* reset XmppConnection to parentChristian Schneppe2020-01-021-1/+1
|
* createOutputStream(): allow to disable decryptionChristian Schneppe2019-12-241-1/+1
|
* rework adhocinviteChristian Schneppe2019-12-131-1/+3
|
* jingle ibb: wait to receive ibbChristian Schneppe2019-12-093-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.
* check if sender is in contact list before accepting jingle fileChristian Schneppe2019-11-151-2/+3
|
* allow jingle state transition for fallback after proxy failureChristian Schneppe2019-11-151-2/+6
|
* make jingle state transitions less error proneChristian Schneppe2019-11-151-2/+28
|
* bookmarks2. introduce #compat namespaceChristian Schneppe2019-10-262-1/+3
|
* support for purge and deleteChristian Schneppe2019-10-261-1/+1
|
* support for delete bookmarks2Christian Schneppe2019-10-261-1/+6
|
* WIP Bookmarks 2 supportChristian Schneppe2019-10-261-0/+9
|
* show reason in error messageChristian Schneppe2019-10-261-1/+6
|
* mark cancelled jingle ft as such on both sidesChristian Schneppe2019-10-263-75/+101
|
* fully read port in socks connectionChristian Schneppe2019-10-261-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
* set shorter timeouts when using direct candidatesChristian Schneppe2019-10-263-6/+13
|
* report not-acceptable on jingle errorsChristian Schneppe2019-10-022-19/+16
|
* close correct socket after faulty jingle socks connectionChristian Schneppe2019-09-201-1/+1
|
* migrate to AndroidXChristian Schneppe2019-09-202-2/+2
|
* show language in message bubble if multiple language variants were receivedChristian Schneppe2019-09-122-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.
* do not include scope in ipv6 annoucmentChristian Schneppe2019-09-091-1/+12
|
* JET uses plain text file sizeChristian Schneppe2019-09-061-2/+9
|
* do not include link local in direct candidatesChristian Schneppe2019-09-063-16/+12
|
* make Tor connections work with direct TLSChristian Schneppe2019-09-061-60/+48
|
* implemented support for for jingle encrypted transports (XEP-0396)Christian Schneppe2019-09-062-10/+37
|
* deleted wrong to jidChristian Schneppe2019-09-061-1/+0
| | | | fixes #374
* fix some crashesChristian Schneppe2019-09-032-6/+22
|
* use higher priority for proxy on receiving endChristian Schneppe2019-09-032-5/+4
|
* send fallback to ibb after proxy activation failedChristian Schneppe2019-09-031-6/+17
|
* also reply with direct connections on responseChristian Schneppe2019-09-032-18/+34
|
* bare minimum direct connectionsChristian Schneppe2019-09-034-6/+153
|
* order canditates by priority before attempting to connectChristian Schneppe2019-09-032-25/+27
|
* more ibb fixes (include sid in transport-accept)Christian Schneppe2019-08-312-15/+25
|
* fixed unlikely race between enabling carbons and discovering last MAM idChristian Schneppe2019-08-311-3/+3
|
* fixed pgp decryption of automatically accepted jingle ftChristian Schneppe2019-08-311-10/+7
|
* increased reconnection interval after policy violationChristian Schneppe2019-08-311-1/+3
|
* refactored filename and extension parsingChristian Schneppe2019-08-311-32/+32
|
* create empty disco result on error to fire advance stream features eventChristian Schneppe2019-08-311-1/+14
|
* fix SOCKS5 to IBB fallbackChristian Schneppe2019-08-311-5/+4
|
* use helper method to close socketChristian Schneppe2019-07-171-10/+3
|
* code cleanup & small fixesChristian Schneppe2019-07-012-3/+3
|
* Revert "Networkstack - let OS decide IPv4 or IPv6 (#267)"Christian Schneppe2019-06-251-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
* implement client support for muc pushChristian Schneppe2019-06-251-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.
* fix jingle file transferChristian Schneppe2019-06-253-4/+4
| | | | fixes #360
* performance improvement of message expiryChristian Schneppe2019-06-221-2/+2
|