[prev in list] [next in list] [prev in thread] [next in thread] 

List:       otr-users
Subject:    Re: [OTR-users] Re: Ignored Messages
From:       Ian Goldberg <ian () cypherpunks ! ca>
Date:       2005-03-28 22:55:24
Message-ID: 20050328225524.GK30200 () smtp ! paip ! net
[Download RAW message or body]

On Mon, Mar 28, 2005 at 05:35:17PM -0500, Jed Hassell wrote:
> How does OTR detect whether the other client speaks OTR?  This would
> be of great help.  Currently I'm trying to figure out how to use the
> toc_rvous_propose and toc_rvous_accept methods but there just isn't
> enough documentation on these methods to prove worthwhile.  If you
> could explain how OTR detects if other clients are capable of
> understanding OTR messages, I could work this into my own
> implementation and just forget about the ignored messages.

[I don't know what toc_rvous_propose and toc_rvous_accept are.]

There are two ways OTR uses:

1. If an OTR-enabled client sees any OTR protocol message coming from a
   buddy, it assumes the buddy can speak OTR.
2. If an OTR-enabled client sees a special whitespace pattern in a
   message coming from a buddy, it assumes the buddy can speak OTR.

If your client is in the so-called "opportunistic" mode, it will append
the whitespace pattern to the first message it sends to any buddy.  If
they're OTR-enabled, they'll recognize it and start an OTR session.

Trillian uses a different method for its SecureIM protocol:

3. The AIM/ICQ network allows clients to publish lists of
   "capabilities".  SecureIM is one of those capabilities; any client
   can tell if yours supports SecureIM.

   - Ian

[prev in list] [next in list] [prev in thread] [next in thread]