Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

implement axolotl/omemo for xmpp compatibility #538

Closed
pravi opened this issue Aug 23, 2015 · 6 comments
Closed

implement axolotl/omemo for xmpp compatibility #538

pravi opened this issue Aug 23, 2015 · 6 comments
Assignees
@daniele-athome
Labels
duplicate This issue or pull request already exists

Comments

@pravi
Copy link

pravi commented Aug 23, 2015

As discussed in #492 , axolotl would be useful for kontalk compatbility with xmpp. Conversations released version 1.6.0 with axolotl support (called omemo) today. They are drafting an xep already. Since code for this already exist, I think it would be easy to implement.
@daniele-athome daniele-athome added the pending Issue is pending further analysis label Aug 24, 2015
@daniele-athome daniele-athome self-assigned this Aug 24, 2015
@h-2
Copy link

h-2 commented Sep 1, 2015

👍
This would be super great and eliminate all "but foobar is more secure that Kontalk" claims.

OTR is definetely not need if we have this...

@iNPUTmice
Copy link

some general information about OMEMO and links to the XEP can be found here: conversations.im/omemo

@daniele-athome
Copy link
Member

Thanks @iNPUTmice, I'll take a serious read at that as soon as possible.

@h-2 h-2 mentioned this issue Sep 26, 2015
Closed
@pravi pravi mentioned this issue Mar 15, 2016
Open
@pravi
Copy link
Author

pravi commented Mar 20, 2016

@daniele-athome see LibreSignal/LibreSignal#10 (comment) I think implementing this feature can convince some LibreSignal contributors to join kontalk instead.

@daniele-athome
Copy link
Member

Thanks for the feedback @pravi.

@daniele-athome daniele-athome added duplicate This issue or pull request already exists and removed pending Issue is pending further analysis labels Mar 21, 2016
@daniele-athome
Copy link
Member

Merged into #132. Set for release 3.3 for now (no precise estimate though).

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@daniele-athome daniele-athome

Labels
duplicate This issue or pull request already exists
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
4 participants
@iNPUTmice @pravi @h-2 @daniele-athome