You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Proposal (and I offer to help here) to add some lines of text how messages and attachments are received → would be helpful.
I managed to install signal-cli and run it as a systemd service, and also used the receive.py to see everything working and received also attachments to /var/lib/signal-cli/attachments directory. Of course, journalctl -f -u signal-cli lists the received messages as well.
However, in my view as a beginner to the wonderful (and sometimes weird) world of signal-cli, it would be nice to have some basic information (or methods inside signal-cli), how received messages and attachments could be automatically stored and logged into for example mbox-like structures, or using the -o json format or to trigger some other useful things on the server.
I saw for example the signal-to-mail gateway, but one or two smaller examples would be perhaps helpful, too.
This discussion was converted from issue #915 on May 26, 2022 13:30.
Heading
Bold
Italic
Quote
Code
Link
Numbered list
Unordered list
Task list
Attach files
Mention
Reference
Menu
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
Proposal (and I offer to help here) to add some lines of text how messages and attachments are received → would be helpful.
I managed to install signal-cli and run it as a systemd service, and also used the receive.py to see everything working and received also attachments to /var/lib/signal-cli/attachments directory. Of course,
journalctl -f -u signal-cli
lists the received messages as well.However, in my view as a beginner to the wonderful (and sometimes weird) world of signal-cli, it would be nice to have some basic information (or methods inside signal-cli), how received messages and attachments could be automatically stored and logged into for example mbox-like structures, or using the -o json format or to trigger some other useful things on the server.
I saw for example the signal-to-mail gateway, but one or two smaller examples would be perhaps helpful, too.
What are your thoughts?
And, by the way, the https://github.com/AsamK/signal-cli/blob/master/man/signal-cli.1.adoc page should be linked from the (present) Wiki Home page.
Beta Was this translation helpful? Give feedback.
All reactions