Signal-cli: command-line and dbus interface to Signal

Re:Signal-cli: command-line and dbus interface to Signal by privong on Saturday February 11, 2017 @07:29PM (#13625791)

Is it possible to use this along with the smartphone app (i.e., by "registering" with the same phone number) or does this CLI effectively represent an independent registration which would supersede the one on the phone? The README said something specific on this – so I assume it's the latter?

[ Parent | on HN ]

Re:Signal-cli: command-line and dbus interface to Signal by finnn on Saturday February 11, 2017 @08:49PM (#13626112)

Yes, it's possible to use this from with a smartphone. The README did say something specific, like, how to do it. In the app go to Settings -> Linked Devices -> add a new one. Decode the URL in the QR code, then add it to signal-cli like this:

signal-cli -u USERNAME addDevice --uri "tsdevice:/…"

As outlined in the README under the "Linking other devices" section

[ Parent | on HN ]

Re:Signal-cli: command-line and dbus interface to Signal by Trolldemorted on Sunday February 12, 2017 @04:17AM (#13627549)

Settings -> Linked Devices -> add a new one won't give you a QR code.

The QR codes are encoded tsdevice:// links which are presented by ready-to-mate slave devices.

If you want to link a signal-cli instance to an Android, you have to encode the cli's tsdevice link into an qrcode and scan it.

If you want to link an Android to a signal-cli instance, you have to use my fork. https://github.com/Trolldemorted/Signal-Android/tree/multide...

[ Parent | on HN ]

Re:Signal-cli: command-line and dbus interface to Signal by privong on Saturday February 11, 2017 @09:05PM (#13626197)

Thanks. Though the README also says:

> To be able to receive messages signal-cli uses a patched libsignal-service-java, because libsignal-service-java does not yet support registering for the websocket support nor provisioning as a slave device.

So maybe you can add a smartphone if you've already registered via the CLI but not the reverse? The wording is unclear to me.

[ Parent | on HN ]

Re:Signal-cli: command-line and dbus interface to Signal by finnn on Saturday February 11, 2017 @09:13PM (#13626228)

That line is explaining why signal-cli doesn't use the real libsignal, but a modified copy of it. They've modified it to support shit like that. However, https://github.com/AsamK/signal-cli/issues/49 makes it sound like you may have other issues.

[ Parent | on HN ]