(In reply to comment #61) > I would really like im-channel to implement o.fd.Telepathy.Securable - as a > starting point we can have the two booleans not be requestable, and just > have them set by the OTR code calling a new > gabble_im_channel_indicate_security > (GABBLE_SECURABLE_ENCRYPTED|GABBLE_SECURABLE_VERIFIED) (or only one of > those, or neither of those, as appropriate). > > I notice we never specified how those properties did change notification, > because our only use of them so far was for SASL channels. Let's retcon them > to "they emit PropertiesChanged" in the 0.x and 1.0 spec.
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. -- 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
