Mercurial > hg
view mcabber/doc/help/en/hlp_otrpolicy.txt @ 2269:766666eb6928
Link with the tinfo library
On some systems we have to explicitly link with libtinfo.
pkg-config cannot be used on every system with ncurses,
see discussion in https://bugs.gentoo.org/show_bug.cgi?id=457530#c18
For now we'll use the same fix as Mutt:
https://dev.mutt.org/hg/mutt/rev/c84aa0d62ce3
Thanks to Wolfram Schlich for the report and troubleshooting!
author | Mikael Berthe <mikael@lilotux.net> |
---|---|
date | Mon, 12 Sep 2016 22:39:04 +0200 |
parents | a6d71ddf927f |
children |
line wrap: on
line source
/OTRPOLICY /OTRPOLICY (default|jid) (plain|manual|opportunistic|always) You can use the shortcut-jid "." for the currently selected contact. /otrpolicy Prints all OTR policies to the status buffer /otrpolicy (default|jid) (plain|manual|opportunistic|always) Sets either the default policy or the policy for the given jid The plain policy should never be used, because you won't be able to receive or send any OTR encrypted messages. If you set the policy to manual, you or your chat partner have to start the OTR encryption by hand (e.g. with /otr start). The policy "opportunistic" does that itself by sending a special whitespace-sequence at the end of unencrypted messages. So the other OTR-enabled chat client knows, that you want to use OTR. Note that the first message will always be unencryted, if you use this policy. With the policy "always" no message will be sent in plain text. If you try to sent the first message unencrypted, mcabber will try to establish an OTR channel. Please resend your message, when you get the information that the channel was established. If someone sends you plaintext messages while the policy is set to "always", you'll be able to read the message but it won't be saved to the history.