I just set up signal-cli and siggo on my ubuntu server to try it out. This is pretty awesome thank you.

Signal on my iPhone is the primary account. I added my signal-cli user with

signal link -n myname | tee >(xargs -L 1 qrencode -t utf8)

So I see this status message sometimes when I try to send a message, it seems like the flow is:

1. Open siggo after it being stopped
2. Send a message
3. See exit status 2, the message also doesn't send and is removed from the chat
4. Open Signal on my iPhone, send a message
5. Wait for message to show up in siggo
6. Once it shows up in siggo then I can send messages and it all seems to work fine. Eventually the chat will sync up but that can take a bit

• Any idea if this is a normal behavior for starting up siggo?
• Should I be doing something to run this as a daemon or in screen so that I don't need to start/stop siggo ?

I enabled debug mode but this didn't seem too helpful

time="2022-01-08T15:48:44-08:00" level=info msg="starting dbus daemon..."
time="2022-01-08T15:48:44-08:00" level=info msg="scanning stdout"
time="2022-01-08T15:48:46-08:00" level=error msg="exit status 2"
time="2022-01-08T15:48:46-08:00" level=debug msg="updating contact panel..."