diff options
| author | Daniel Gultsch <daniel@gultsch.de> | 2019-11-12 11:12:05 +0300 |
|---|---|---|
| committer | Daniel Gultsch <daniel@gultsch.de> | 2019-11-12 11:12:05 +0300 |
| commit | 432fd3e3bfc4ff4a0141db4ce283e805fab7cecf (patch) | |
| tree | b38ebbaca20d641ccb2a1985d67bc96bd10cc74d /README.md | |
| parent | eb943619af3e7fef82151e183561029683b189c9 (diff) | |
remove mentioning of Conversations Legacy
Diffstat (limited to 'README.md')
| -rw-r--r-- | README.md | 2 |
1 files changed, 0 insertions, 2 deletions
@@ -389,8 +389,6 @@ Read more about the concept on https://gultsch.de/trust.html #### What happened to OTR support? OTR was removed because it was highly unreliable. It didn’t work with multiple devices and was never really specified to work with XMPP. The codebase was a mess (There was an HTML parser in there for crying out loud to deal with the garbage some OTR clients would send.) Verification was implemented in a non-blocking way. It would tell you if the current session was using an unknown fingerprint but it didn’t actively stopped you from sending messages until you have confirmed the new fingerprint. (Like Conversations would do now with BTBV after verification or when BTBV is turned off.) Considering the previous points there was little to no desire from my point to fix this potential security issue or clean up the code base. Another reason for the removal was that people would use it *accidentally* even to communicate between two Conversations clients because they read somewhere that OTR is good. -OTR is still available in [Conversations Legacy](https://github.com/siacs/Conversations/tree/legacy). - ### What clients do I use on other platforms There are XMPP Clients available for all major platforms. #### Windows / Linux |