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

Are these actually supported? #9

Closed
saghul opened this issue Sep 2, 2024 · 7 comments · Fixed by #10
Closed

Are these actually supported? #9

saghul opened this issue Sep 2, 2024 · 7 comments · Fixed by #10

Comments

@saghul
Copy link

saghul commented Sep 2, 2024

We currently use libolm in Jitsi Meet and since it got deprecated I was considering upgrading to vodozemac but:

  • There is no published package that I can find
  • These bindings are pinned to a vodozemac version which is over 2 years old
  • There is zero tests or documentation
  • No updates for 2 yuears in this repo

What is the path forward here, for those of us using libolm in JS, from a browser?

@IgorKhomenko
Copy link

IgorKhomenko commented Sep 4, 2024

In a case it helps, this is how the lib can be connected to Web project:

  • Go to matrix-org/vodozemac-bindings and run the following command wasm-pack build --target web --dev
  • Move the generated files from the pkg folder to the vendors/vodozemac folder in YOUR project
  • Declare the folder in package.json as a built-in library: "vodozemac-javascript": "file:vendors/vodozemac"
  • Import everything from the library, call it to initialize it in the project, and now you can use it anywhere in the project
import initVodozemac, { Account } from "vodozemac-javascript";

initVodozemac().then((res) => {
   const a = new Account();
});

@poljar
Copy link
Collaborator

poljar commented Sep 4, 2024

For what its worth, we're going to discuss this tomorrow in a meeting.

@saghul
Copy link
Author

saghul commented Sep 4, 2024

In a case it helps, this is how the lib can be connected to Web project:

  • Go to matrix-org/vodozemac-bindings and run the following command wasm-pack build --target web --dev

  • Move the generated files from the pkg folder to the vendors/vodozemac folder in YOUR project

  • Declare the folder in package.json as a built-in library: "vodozemac-javascript": "file:vendors/vodozemac"

  • Import everything from the library, call it to initialize it in the project, and now you can use it anywhere in the project


import initVodozemac, { Account } from "vodozemac-javascript";



initVodozemac().then((res) => {

   const a = new Account();

});

I know how to do that, but I shouldn't need to. In addition that doesn't solve the fact that the bindings are 2 years behind the library they bind.

@saghul
Copy link
Author

saghul commented Sep 4, 2024

For what its worth, we're going to discuss this tomorrow in a meeting.

Thank you!

@poljar
Copy link
Collaborator

poljar commented Sep 5, 2024

Sadly the answer is, no, these are not supported.

I kinda expected this situation and pulled the Python bindings, which I'm personally invested in, into a separate repo: https://github.com/matrix-nio/vodozemac-python.

Some other folks seem to have pulled the c++ bindings out as well: https://github.com/matrix-nio/vodozemac-python.

It would probably make most sense to do the same with the WASM bindings.

Sorry.

@poljar
Copy link
Collaborator

poljar commented Sep 5, 2024

Opened #10 to make this more prominent and official.

@saghul
Copy link
Author

saghul commented Sep 5, 2024

I appreciate the honesty.

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

Successfully merging a pull request may close this issue.

3 participants