Alex Bikadorov

@daniele-athome > There are two ways of approaching this: using a random string and a phone number/JID mapping table or using phone numbers directly in the JID. Please no phone...

> Ok, so we agree on not using the phone number in the JID anymore? I'm sorry, are you talking about not using phone numbers at all - not even...

Yes, it's definitely a good idea to move the {phoneNumber->JID} algorithmen exclusively to the server side. It will be needed once the JID cannot be directly derived from the phone...

I also find this very annoying. I use the "Edit track information" functionality a lot and have to remove the Album tag every time before saving. How can a new...

I'm still unsure about this. Kontalk is a mobile messenger network, the desktop client is (or was) only intended as an addition. The account creation could be integrated (with still...

I get your concerns but if we use a strong symmetric encryption with fixed password length (

Eh, what exactly is your general idea? The desktop client establishes a temporary XMPP connection, and the Android client sends the key?

[uhh I almost forgot about this thread again] In general it sounds good. One improvement idea: The Android app should generate a secure password for the user (26chars, lower letters...

> the problem with this approach is that the token is client generated. That is not acceptable sorry, the token has to be generated by the server, it's too important...

> Maybe not clients directly, but the server will have access to a hashed version of the passphrase. I don't like it. Private key related content should never go through...