Sebastian Scheibner

That version should work, you can get more details with the `-vv` parameter.

The signal-cli database implementation started the first point, i.e. get a new connection for each operation. Then when implementing the storage sync it was extended to use existing connections so...

Those are the native libs that signal-cli uses, normally they get removed when signal-cli exits cleanly. Which signal-cli container are you using? Maybe it has some unusual config or a...

There's currently no machine-readable documentation. The JSON-RPC commands are based on the cli arguments (see [JSON-RPC man page](https://github.com/AsamK/signal-cli/blob/master/man/signal-cli-jsonrpc.5.adoc) and [cli man page](https://github.com/AsamK/signal-cli/blob/master/man/signal-cli.1.adoc)) I've had some ideas for creating a new...

Can you provide the complete stack trace please, it doesn't contain the part where the call starts in signal-cli.

Looks like a bug, can you provide more lines of the stack trace? Storage sync doesn't work, but receiving/sending messages should still work normally. The last line is unrelated, i...

Can't figure out why the UNIQUE constraint is being violated here. With verbose logging (`-v`) there should a log message starting with `Got separate recipients for high trust identifiers ...`...

Maybe look at other issues, that got it working: e.g. #760

The first step would be to design a cli interface for sending stories (maybe `sendStoryMessage`) and managing distribution lists for story groups (maybe `listStoryDistributionLists` and `updateStoryDistributionList`) with parameters for all...

I would have to dig deeper into the code to check whether it's actually required. It will definitely be more efficient to use distribution lists when sending multiple stories to...