Re:Signal-cli: command-line and dbus interface to Signal
by justinsaccount on Saturday February 11, 2017 @04:58PM
(#13625080)
Ah, thanks! I came across that a while ago but had forgotten about it. It seems to have come along quite a ways.
[ Parent
| on HN ]
Re:Signal-cli: command-line and dbus interface to Signal
by nextos on Saturday February 11, 2017 @06:40PM
(#13625565)
Yes, their web & mobile client https://riot.im is very polished now. They are also rolling e2e crypto.
Re:Signal-cli: command-line and dbus interface to Signal
by justinsaccount on Saturday February 11, 2017 @07:01PM
(#13625670)
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 :-)
Re:Signal-cli: command-line and dbus interface to Signal
by kscz on Sunday February 12, 2017 @02:46AM
(#13627325)
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
by justinsaccount on Sunday February 12, 2017 @07:08PM
(#13632036)
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
by nextos on Monday February 13, 2017 @06:01AM
(#13634445)
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.