GTK Rust mobile Linux client for Signal

[Be.]

I am not really a dev so this is an honest question :

if the issue with axolotl is that it uses its own implementation in go, and signal just released a great rust library. Isn't the best choice to contribute (or fork) to axolotl by switching from the go implementation to the rust library?

Otherwise this really feels like a waste to have to redo a new GUI etc. Reinventing the wheel.

I don't know Go and I'm not especially interested in learning it. I have not looked very deep into the Axolotl code but it's IMO a rather strange architecture that I'm personally not very enthusiastic about working with. The Signal protocol code in Axolotl is a completely independent implementation in Go which is wrapped in a WebSocket that communicates with a Vue.js frontend running in QWebEngine. I also don't know Vue.js and I'm not particularly interested in learning web stuff. Whisperfish is written in Rust with a QML GUI, which are both technologies I have been wanting to learn for a while. Whisperfish has been using the libsignal-protocol-c library with their own Rust bindings, which is better than a complete reimplementation. The transition to the new upstream Rust library is almost done. Most of the work to get Whisperfish running on PinePhones will be adapting the QML to use either the proprietary Sailfish QML libraries or KDE's Kirigami QML library. Fortunately there are a few other applications like PureMaps which have already done this so we'll be reusing code from that.