add per-user OTR policy setting

[pesco]

... akin to the global otr_policy one.

this would be stored in the otr connection context, i.e. independently from bitlbee's settings.

accordingly, the command would probably be

otr policy <user> (never|opportunistic|manual|always)

[pesco]

Replying to pesco:

this would be stored in the otr connection context, i.e. independently from bitlbee's settings.

actually, i was mistaken on this one. libotr gives us a connection context in a callback and asks which policy to apply. we have to store it somewhere.

so since we have (afaik?) no central mechanism to store per-user settings, the easiest way would be to save to our own file. since there is no complicated structure in the data, this could be as straight-forward as an ascii text file with lines like this: john@doe.net/jabber opportunistic

[zx2c4]

+1