> It's practically a principle of the Signal project to discourage third-party clients It depends on what you call "client". At the protocol level sure, you're

> It's practically a principle of the Signal project to discourage third-party clients It depends on what you call "client". At the protocol level sure, you're supposed to behave just like any official client. But to do that you just have to use their client library[0] and implement whatever you want on top of this, like signal-cli[1] has been doing successfully for quite some time now. Some forks exist here and there (from memory, there's one with WhatsApp import, another with UI features), there's just no interest for a completely new client. There's only so much space for innovation for what is mostly a messaging app. To be fair, the absence of an API (which Telegram has) also limits possibilities. [0]: https://github.com/signalapp/libsignal-client https://github.com/signalapp/libsignal-client [1]: https://github.com/AsamK/signal-cli https://github.com/AsamK/signal-cli