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.

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

add (link to) omemo backend implementations/libraries #92

Open
azrdev opened this issue Jan 31, 2018 · 6 comments
Open

add (link to) omemo backend implementations/libraries #92

azrdev opened this issue Jan 31, 2018 · 6 comments

Comments

@azrdev
Copy link

azrdev commented Jan 31, 2018

In addition to the client support of omemo, a list of implementing libraries would be useful for those who want to add support for a particular client (using one of said libraries). Useful attributes to track would be:

  • links to website and source code
  • programming language
  • actively developed? (esp. w.r.t. security issues)

may omemo.top be a place for that too?

@bascht
Copy link
Owner

bascht commented Jan 31, 2018

I could imagine having this on a separate page – probably as a plain, simple markdown page that just lists all available libraries with their specs and acts as a addressable #anchor for the client page.

@bascht
Copy link
Owner

bascht commented Apr 9, 2018

@azrdev I've just merged #40 – so I'm happy for every feedback / suggestions for more + detailed information. 😸

@azrdev
Copy link
Author

azrdev commented Apr 9, 2018

@bascht you imagine that we add the info (+ link to that separate implementation list page) which implementation is used to the new (with #94 ) client sections ?

@nogweii
Copy link
Contributor

nogweii commented Apr 10, 2018

I could see this project supporting an additional subfolder of _data, called libraries. Keeping track a list of the libraries that support OMEMO would make omemo.top a useful resource to developers as well: "Here's a list of libraries to get you started on adding OMEMO support to your IM application."

@bascht
Copy link
Owner

bascht commented Apr 16, 2018

@l29ah Yup, something along what @evaryont detailed. I don't think there are enough libraries (I guess < 10, no?) to justify moving them into data files yet. We could just add a single HTML file with all the available libraries as jump-able HTML anchors so they can be referenced from the clients.

@l29ah
Copy link
Contributor

l29ah commented Apr 16, 2018

wat

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

4 participants