Signald not started automatically with Pyre-Qt client
Currently the client fails somewhat silently if started without signald providing a socket at /var/run/signald/signald.sock
While it is totally reasonable for a bot to exhibit this behavior, a messaging client probably shouldnt do this.
There are a number of potential solutions
- display a dialogue to user telling them to turn on a system wide signald daemon
- try to start a system-wide signald daemon
- manage a local signald daemon and start it with the client
I think that it is most reasonable to go with number 3. Given that signald will persistently contain state that is related to signal-qt it is important that we not allow other signald applications access to our signald instance. In fact, later on down the road if we are keeping an application local signald distribution we can perform authentication maneuvers like encrypting it when not in use.
TL;DR: We should figure out the best way to bundle signald with Pyre-Qt, and run it as a subprocess of our application.