I understand. There’s a reason I still label this as beta. It is not usable if you’re not willing to put time into reporting and debugging some issues. Given the technical debt that we are working through (and catching up on), the complexity of Signal itself (which we are catching up on), and the fact that we have to build our own ecosystem of support libraries (unlike Telegram with TDlib), this is probably one of the more complex applications that are being written for SailfishOS. We’re closing in on 0.6.0, and I would urge you to take a look again when we reach that point.
I agree on most of what you say here. However, there are very specific use cases where a Tor-style access to a network is useful, and the sealed sender socket is very probably one of them. These are one-shot, anonymous, unidentified sockets that are accessed per-recipient. Mapping those sockets on single-use Tor circuits should quite effectively help to totally hide your endpoint from Signal.
At least, in theory. Part of such an endeavour would be the evaluation in practice, which is something we can actually try out, thanks to Whisperfish.

