exquo

I've thought about incorporating this change into scli, but couldn't think of what problem that would solve. Since scli is a single-user application, it has to know which account to...

Gotcha. There might be some advantages in listening to dbus output rather then using stdout, but a big disadvantage is that signal-cli's dbus interface's features often lag behind the stdout...

Signal-cli has a newer [JSON-RPC API](https://github.com/AsamK/signal-cli/discussions/679) with the most comprehensive functionality. The dbus interface ["will likely always lag behind"](https://github.com/AsamK/signal-cli/discussions/799#discussioncomment-2069250). JSON-RPC would be the best choice for scli, but switching to...

Yes, history is currently saved on exit. Being able to protect it from OS crashes, power failures, etc would be an improvement.

@NK308, thanks for the suggestion! I've added a handler for the `SIGTERM` and `SIGHUP` signals. It attempts to close and save everything gracefully, like it currently does for `SIGINT` (`Ctrl...

@obnoxiousish, the signals handling should be taken care of, AFAICT, but feel free to make a PR with additional changes for this or other issues. Yes, the code documentation is...

For the purposes of saving the conversations history, in scli there should be no difference between messages-to-self and messages to others. I have just tested sending a message to another...

Normally, on shutdown the system sends a `SIGTERM` to all processes, and then `SIGKILL` to those that are still running after a timeout has passed (typical timeout = 90s). There...

I've tried some of those shutdown commands on a DebianVM - all gave me the same `SIGHUP` message as `sudo shutdown now` above ([apparently](https://stackoverflow.com/a/39275997), systemd sends `SIGHUP` in addition to...

This might be a good stop-gap measure until we implement a proper database.