Hi again, guys

This is just a heads up that I've been working today on all of this.

I've compiled and packaged for maemo libcurve25519, libaxolotl (it's now called Signal), which is the basis of the encryption protocol. The package for libaxolotl-dev is still defective, but it's basically a non issue that will get resolved when there is something ready to be sent to the autobuilder.

Thanks to these two packages, I've also compiled and packaged coderus' libwa, which I've had to backport to use QT4 instead of QT5.

This library makes use of libaxolotl to manage encryption, so this is the solution to the non-received (in truth non decyphered) messages.

I've already begun porting Yappari to make use of libwa API. First module ported has been Registration, which only by itself is not very useful yet, but is nonetheless required.

These are all huge steps, and the thing looks promising. There are two tasks remaining, which although not extremely hard are quite time consuming.

First task is upgrading the protocol. I've been inspecting S40 source code and I've already upgraded the protocol based on this, but it is yet to be tested. Luckily, Chat-API team is gonna release their update soon, so I'll be able to compare implementations and find bugs before anyone (me, primarly) gets banned.

Second task is finishing the port of Yappari to the new API. This is the thing that will take more time, as there are lots of API calls that need to be modified.

However, if everything progresses fine, I could release incomplete versions with reduced functionality (for example, no group chats), so little by little I could be finishing the port while still releasing useful partial implementations.

Now, please, take all of this with a grain of salt. Latest 48 hours have been intense and I can't promise I'll be able to spend so much energy on this, nor that it will blossom onto something that is useful, stable and safe.

I'll be posting everything I can tell you guys, just so you can know what to expect.