- Sep 22, 2019
-
-
Daniel Gultsch authored
-
Daniel Gultsch authored
-
- Sep 21, 2019
-
-
Daniel Gultsch authored
-
Daniel Gultsch authored
-
- Sep 20, 2019
-
-
Daniel Gultsch authored
-
- Sep 19, 2019
-
-
Daniel Gultsch authored
-
Daniel Gultsch authored
-
Daniel Gultsch authored
-
- Sep 18, 2019
-
-
Daniel Gultsch authored
-
Daniel Gultsch authored
-
Daniel Gultsch authored
-
- Sep 16, 2019
-
-
Daniel Gultsch authored
-
Daniel Gultsch authored
-
- Sep 15, 2019
-
-
Daniel Gultsch authored
-
Daniel Gultsch authored
finishing (sending a key transport message in response to pre key message) as well as reparing sessions will leak resource and availability and might in certain situations in group chat leak the Jabber ID. Therefor we disable that. Leaking resource might not be considered harmful by a lot of people however we have always doing similar things with receipts.
-
- Sep 13, 2019
-
-
Daniel Gultsch authored
-
- Sep 12, 2019
-
-
Daniel Gultsch authored
-
Daniel Gultsch authored
-
Daniel Gultsch authored
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. Disabeling 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 Conversations now shows the displayed language in a corner of the message bubble if more than one translation has been received. If multiple languages are received Conversations 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 Conversations will discard (not show at all) messages with with multiple bodies of the same language. (This is considered an invalid message) The lanuage tag will not be shown if Conversations received 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.
-
Daniel Gultsch authored
-
- Sep 11, 2019
-
-
Daniel Gultsch authored
-
Daniel Gultsch authored
-
- Sep 10, 2019
-
-
Daniel Gultsch authored
-
- Sep 09, 2019
-
-
Daniel Gultsch authored
-
- Sep 08, 2019
-
-
Daniel Gultsch authored
-
Daniel Gultsch authored
-
- Sep 06, 2019
-
-
Daniel Gultsch authored
-
- Sep 05, 2019
-
-
Daniel Gultsch authored
-
Daniel Gultsch authored
-
- Sep 04, 2019
-
-
Daniel Gultsch authored
-
- Sep 02, 2019
-
-
Daniel Gultsch authored
-
- Sep 01, 2019
-
-
Daniel Gultsch authored
-
Daniel Gultsch authored
-
Daniel Gultsch authored
-
Daniel Gultsch authored
-
- Aug 29, 2019
-
-
Daniel Gultsch authored
-
Daniel Gultsch authored
-
Daniel Gultsch authored
-
Daniel Gultsch authored
-
- Aug 26, 2019
-
-
Daniel Gultsch authored
-