(In reply to comment #60) > (In reply to comment #50) > > Could we also get a config option that turns this whole feature on/off? I > > ask because some industries (like the one where I work) require that all > > electronic communications related to the business get recorded and reviewed > > by compliance officers and made available to regulatory agencies upon > > request. > > I think we do need a connection parameter to control this. I think the > possible sensible settings are: > > - never use OTR, behave exactly as though it was not implemented > > - start an OTR conversation if the local user or remote peer explicitly > requests it > > - try to start OTR conversations automatically > > I think that would be most comprehensible as two booleans: something like > "enable-otr" (default false initially, default true after a couple of > releases) and "enable-opportunistic-otr" (not implemented in Xavier's patch, > but someone could add it). > > The writer of Comment #50 would explicitly set enable-otr to false; the > people getting excited about this bug would explicitly set enable-otr to > true, and when implemented, probably also set enable-opportunistic-otr to > true.
It can be done later. ATM the policy is MANUAL and it's the right thing until we have an explicit option. I would consider this non-blocker future enhancement. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/296867 Title: empathy needs to support OTR encryption To manage notifications about this bug go to: https://bugs.launchpad.net/empathy/+bug/296867/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
