[OTR-dev] OTR encryption state

[verbal]

you dont need NEVER *and* MANUAL.  

In fact, you can replace NEVER and ALWAYS with MANUAL. just have
MANUAL off = NEVER and MANUAL on = ALWAYS.

to me, having MANUAL and OPPORTUNISTIC seems to be the simplist and
most intuitive design.

verbal

> 
> which returns information about what OTR features should and should not
> be enabled for this context?
> 
>     NEVER:  Pretend OTR isn't enabled at all for this user
>     ALWAYS: It is an error to send unencrypted data to this user.
>             If you try, you'll get a notify(ERROR) callback and
>             the message to be sent will be turned into an OTR Error
>             message that the other side will see.
>     OPPORTUNISTIC: (the current mode) probe the other side with the
>                    whitespace tag, and reply to any indication that he
>                    speaks OTR with a Key Exchange Message (if we're not
>                    already private)
>     MANUAL: Don't send the whitespace tag, and don't reply to one you
>             receive.  Respond to explicit OTR Query Messages and Key Exchange
>             Messages, but not other indications of OTR.  This mode is
>             useful if you for some reason want to communicate in the
>             clear, even though you know the other guy speaks OTR, and
>             also allow either side to start a private conversation
>             at any time.  [If you don't want to allow that last
>             condition, use NEVER instead.]
> 
>    - Ian
> _______________________________________________
> OTR-dev mailing list
> OTR-dev at lists.cypherpunks.ca
> http://lists.cypherpunks.ca/mailman/listinfo/otr-dev
>