starred/twofactor_gateway-nextcloud

Fork 0

mirror of https://github.com/nextcloud/twofactor_gateway.git synced 2026-04-25 00:55:52 +03:00

[GH-ISSUE #664] State of Signal Messenger Support #127

New issue

Open

opened 2026-02-26 05:33:26 +03:00 by kerem · 3 comments

kerem commented

2026-02-26 05:33:26 +03:00

Owner

Originally created by @rotdrop on GitHub (Sep 22, 2025).
Original GitHub issue: https://github.com/nextcloud/twofactor_gateway/issues/664

Issue

There were some open issues

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!).

Originally created by @rotdrop on GitHub (Sep 22, 2025). Original GitHub issue: https://github.com/nextcloud/twofactor_gateway/issues/664 ### Issue There were some open issues - #574 - #578 - #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!).

kerem commented

2026-02-26 05:33:27 +03:00

Author

Owner

@vitormattos commented on GitHub (Sep 22, 2025):

Adding the issues codes as a markdown list will display the issue title, like this:

- #574
- #578
- #579

@vitormattos commented on GitHub (Sep 22, 2025): Adding the issues codes as a markdown list will display the issue title, like this: ```markdown - #574 - #578 - #579 ```

kerem commented

2026-02-26 05:33:27 +03:00

Author

Owner

@rotdrop commented on GitHub (Sep 23, 2025):

See #668.

@rotdrop commented on GitHub (Sep 23, 2025): See #668.

kerem commented

2026-02-26 05:33:27 +03:00

Author

Owner

@rotdrop commented on GitHub (Sep 23, 2025):

I am keeping this open until the backports to NC31 / NC32 have been finalized. This issue is to be closed afterwards.

@rotdrop commented on GitHub (Sep 23, 2025): I am keeping this open until the backports to NC31 / NC32 have been finalized. This issue is to be closed afterwards.

No milestone

No project

No assignees

1 participant

Notifications

Due date

The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference

starred/twofactor_gateway-nextcloud#127

No description provided.

Rows
Columns