State of Signal Messenger Support #664
Description
Issue
There were some open issues
- Support https://gitlab.com/morph027/python-signal-cli-rest-api in add… #574
- Support https://gitlab.com/morph027/python-signal-cli-rest-api ... #578
- Feature/use signal cli json rpc #579
and a couple of changes in my own fork at
https://github.com/rotdrop/twofactor_gateway/
addressing the Signal messenger which were closed (rightfully) after @vitormattos took over maintenance (thank you!!!). The purpose of this issue is to eventually push support for the current signal-cli into twofactor_gateway.
In particular
https://github.com/rotdrop/twofactor_gateway/tree/production/stable32/cafevdb
But please don't use it. The purpose of this issue is to track merging / abandoning of my changes into the main project in order to keep things together.
Why?
In "ancient" times signal-cli had no usable network service point, but this has changed, actually quite some time ago. Signal-cli is still there, actively maintained, and its network service points have stabilize. Just use them.
The current state of the Signal messenger support in this app is that rather outdated "legacy" interfaces of third-third-party projects are used. In particular, the native end-points of the signal-cli project cannot be used in this app which is IMHO very unfortunate.
Goal
Support for https://github.com/AsamK/signal-cli using the network-API endpoints it already provides, perhaps with a focus on the the Debian packages by https://packaging.gitlab.io/signal-cli/
Just to make it clear -- as there are also third-third-party packages -- this issues just exists to track support for the API provided by the signal-cli package. https://packaging.gitlab.io/signal-cli/ was only mentioned as thoes Debian packages make it easier to use the native signal-cli API for Debian and related (e.g. Ubuntu) systemsi. Those are just systemd integration service files for the signal-cli provided end-points.
Timeline
I hope to be able to provide new pull-requests before the end of the year. My private branch supports the current state of signal-cli very well, but got now out of sync w.r.t. to the main project (this one) which got a new maintainer (hurray!).