You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
@@ -1086,7 +1086,7 @@ To start OTR, type `/otr start` - Profanity will show *OTR session started (untr
To authenticate your chat partner, type `/otr question foo? bar` where `bar` is an answer to `foo?` which only the person you assume to be speaking with can answer. If the person answers correctly, Profanity will show *Authentication successful* followed by *OTR session trusted* - now you can be sure the connection is encrypted and authenticated.
To connect from an Android client, use an XMPP client like [Conversations](https://conversations.im/) or [Chat Secure](https://play.google.com/store/apps/details?id=info.guardianproject.otr.app.im).
To connect from an Android client, use an XMPP client like ~~[Conversations](https://conversations.im/)~~ (do not use the Conversations app - its quality is [dubious](https://github.com/siacs/Conversations/issues/2908) and author's intentions are questionable) or [Chat Secure](https://play.google.com/store/apps/details?id=info.guardianproject.otr.app.im).
Start the app and sign in. If you receive a warning that the certificate is not signed by a known authority, verify it using the step below.
The reason will be displayed to describe this comment to others. Learn more.
What? Omemo is much more secure anyway (and verification done properly) and Conversations might get OTRv4 support at some point.
The old OTR was just a pain in the butt
So, the bottom line is that OTR in Conversations was knowingly poorly implemented for its lifetime, and now we should either continue using that legacy version or trust that this attitude won't apply to the current version going forward. Given the general opaqueness of the reasons for the decision and the continuing avoidance of questions posed above, I have no faith that the attitude has changed.
I am of the same opinion and seeing the author describe the change in his own words has decimated my trust in and opinion of Conversations. I have no opinion on OMEMO, because it's relatively new and I have not spent significant time studying it yet. OTR, however, has been around for over a decade and is an established technology in this domain. These circumstances make me sad.
bde7c28There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
What? Omemo is much more secure anyway (and verification done properly) and Conversations might get OTRv4 support at some point.
The old OTR was just a pain in the butt
bde7c28There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@BlauerHunger please see @rharvest's update on that bug:
I am of the same opinion and seeing the author describe the change in his own words has decimated my trust in and opinion of Conversations. I have no opinion on OMEMO, because it's relatively new and I have not spent significant time studying it yet. OTR, however, has been around for over a decade and is an established technology in this domain. These circumstances make me sad.