-
-
Notifications
You must be signed in to change notification settings - Fork 75
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
The bridge is being rewritten in Go #372
Comments
Thinking of having a go/look at #1. In light of this, what are things to consider? |
Is the plan to link against libsignal (I have no idea how easy that is since it's written in Rust), or are you writing from scratch? |
Against libsignal using an FFI layer |
How about using the re-write as an opportunity to add something like "this might take a while" messages for commands that usually can take a while? Sometimes it is a bit confusing when not knowing whether the bridge is doing anything. :) Might be a good time for collecting suggestions anyway, right? |
Is there a roadmap for the golang rewrite? Will this be pushed into this repo? |
read the repo description:
|
It was pushed today. But I had issues, see #382. |
Sadly not working for me, bot doesn't respond to anything. |
The Python version will likely not receive any further updates. Once the Go bridge is ready for general use, it will be merged into this repository and replace the Python version. The new bridge will likely support a direct upgrade from the last old version (v0.4.3) preserving all portal rooms. However, Signal logins are currently managed by signald, which the new bridge will not use, so those will not be preserved and all users will have to re-link the bridge.
The text was updated successfully, but these errors were encountered: