(In reply to comment #69) > 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.
That's OK, but only if MANUAL specifically means "do not initiate *or accept* OTR sessions without user input". (In reply to comment #70) > I would consider this non-blocker future enhancement. Atm I'm not proposing > the spec to be included in tp-spec, only private to gabble<>empathy. I don't like private APIs. They have a nasty habit of becoming de facto public APIs as soon as you commit them (and we only recently managed to get rid of Renaming being a private API, despite it not having changed for 5 years). We have API versioning now, so if it's good enough to merge, it's good enough for the spec. -- 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
