3 ms·
Why does this need to be a daemon? What does this offer that other signal clients do not?
by CameronNemo 6y ago
Why does this need to be a daemon? What does this offer that other signal clients do not?
- finnn 6y agoThis is a tool to build Signal clients with. It handles the Signal-specific stuff, clients can communicate with via a unix socket.
- CameronNemo 6y agoRight but you can already communicate with the official signal server using a socket.
- pseudalopex 6y agoDo you mean using a network socket after you reimplement the Signal protocol? Or do you think signal-cli is official?
- askvictor 6y agoDaemon presumably to handle receiving messages and triggering actions based on that. Do other signal clients allow CLI usage, or integrating with other software? (I'm genuinely not sure)
- CameronNemo 6y agoThere is a CLI client. Notifications/subscriptions may not be available. I think someone mentioned later in the thread that signald is a fork of signal-cli. https://github.com/AsamK/signal-cli https://github.com/AsamK/signal-cli
- finnn 6y agosignald also comes with a cli called signaldctl: https://signald.org/signaldctl/ https://signald.org/signaldctl/
- finnn 6y agoThis daemon handles as much of the weird signal-specific stuff and exposes an easier to use API. It handles things like encrypting and decrypting messages, generating and storing keys, syncing with linked devices and a bunch of others. signald doesn't really "trigger actions" or anything, but it would be pretty easy to write something that does using it.
- nine_k 6y agoI suspect that a next step could be a browser-based client, or a Pidgin plugin, etc, something where you cannot just run Java code, or even open a socket.
- finnn 6y agoa pidgin (libpurple) plugin actually exists already: https://github.com/hoehermann/libpurple-signald https://github.com/hoehermann/libpurple-signald I'd like to improve the website to better showcase the clients