Frequently Asked Questions
- OTR session using bitlbee fails to start
- weechat-otr fails to load
- Is it safe to use the same key for different IRC servers?
bitlbee can have its own OTR implementation. When bitlbee OTR is set to opportunistic it can intercept OTR messages before they get to weechat-otr and interfere with session establishment. To disable bitlbee OTR type set otr_policy never in the bitlbee buffer. See http://wiki.bitlbee.org/bitlbee-otr
Ask in #weechat-otr on Freenode if you still need help.
By default, weechat-otr will generate a unique key per nick/server combination. This is for maximum separation between servers and identities. Users who want to use the same key on multiple accounts (to publish a single fingerprint for example) can set /set otr.general.defaultkey nick@server. When this is set, the key for nick@server will be copied for new accounts. Copying and renaming the key and fingerprint files in ~/.weechat/otr also works.