Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

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

github.com

Post reply on HN
Print view View original

21–27 of 27 posts

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

#21

Post by privong »

finnn wrote: post #20
privong wrote: post #19

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?

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

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.

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

#22

Post by finnn »

privong wrote: post #21
finnn wrote: post #20

Earlier quoted context omitted.

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

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.

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.

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

#23

Post by gepoch »

justinsaccount wrote: post #12

Along these lines.. Is there currently a messaging platform that provides secure communication with e2e encryption and also has mobile apps and apis for automating messages and writing bots? I want to build things like [1] but I don't want my messages being readable by a 3rd party. I may end up just running an irc server+tls or something like rocket.chat [1] https://www.facebook.com/notes/mark-zuckerberg/building-jar…

The newly released keybase chat supports this! It's not in the announcement, but malgorithms described the apis here: https://news.ycombinator.com/item?id=13600427

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

#24

Post by kscz »

justinsaccount wrote: post #18
nextos wrote: post #16

Earlier quoted context omitted.

Yes, their web & mobile client https://riot.im is very polished now. They are also rolling e2e crypto.

It may be a little over engineered for what I want it for, but it does work! I started up the reference server in a docker container and wrote a quick bot using the provided python-sdk and can interact with it using the client on my phone. The main downside(from my perspective) is that it's a lot of moving parts, and I think I'd be more happy with just irc over tls since I at least know how that works :-)

It's mostly a question of mobile support: IRC (over TLS or otherwise) requires a continuous connection, where matrix and signal are designed to support polling a push notification endpoint.

Out of curiosity: what makes you say Matrix is over-engineered?

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

#25

Post by Trolldemorted »

finnn wrote: post #20
privong wrote: post #19

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?

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

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

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

#26

Post by justinsaccount »

kscz wrote: post #24
justinsaccount wrote: post #18

Earlier quoted context omitted.

It may be a little over engineered for what I want it for, but it does work! I started up the reference server in a docker container and wrote a quick bot using the provided python-sdk and can interact with it using the client on my phone. The main downside(from my perspective) is that it's a lot of moving parts, and I think I'd be more happy with just irc over tls since I at least know how that works :-)

It's mostly a question of mobile support: IRC (over TLS or otherwise) requires a continuous connection, where matrix and signal are designed to support polling a push notification endpoint. Out of curiosity: what makes you say Matrix is over-engineered?

Oh.. maybe not over-engineered, but just more involved than what I need. I mostly just want a way to move messages back in forth. I don't need voice or video calls or anything like that.

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

#27

Post by nextos »

justinsaccount wrote: post #26
kscz wrote: post #24

Earlier quoted context omitted.

It's mostly a question of mobile support: IRC (over TLS or otherwise) requires a continuous connection, where matrix and signal are designed to support polling a push notification endpoint. Out of curiosity: what makes you say Matrix is over-engineered?

Oh.. maybe not over-engineered, but just more involved than what I need. I mostly just want a way to move messages back in forth. I don't need voice or video calls or anything like that.

One of the use cases Matrix was designed for is Internet of Things, so I think it's just fine for you.

Video calls come thanks to WebRTC in browsers, Matrix is just a transport protocol. I think it's quite light.

Post reply on HN