androidclient icon indicating copy to clipboard operation
androidclient copied to clipboard

Stronger XMPP federation features

Open daniele-athome opened this issue 10 years ago • 7 comments

  • [ ] add user-defined JIDs
  • [ ] service discovery for Kontalk-specific capabilities (e.g. encryption)

daniele-athome avatar Jul 06 '15 08:07 daniele-athome

FWIW even if Kontalk federates with regular jabber servers, I think the server should not keep track of your contact list and you should not be able to "add user". Instead Kontalk should add jabber users if the android contact includes a jabber account for someone.

I am also a little worried that including outside jabber users weakens the crypto. Right now I can tell everyone: "If you use Kontalk, everything will be safe". If regular jabber is supported it would be important to have other crypto, as well, like OTR. Non-encrypted chat should be off by default IMHO,

h-2 avatar Jul 07 '15 12:07 h-2

FWIW even if Kontalk federates with regular jabber servers, I think the server should not keep track of your contact list and you should not be able to "add user".

Why not?

I am also a little worried that including outside jabber users weakens the crypto. Right now I can tell everyone: "If you use Kontalk, everything will be safe". If regular jabber is supported it would be important to have other crypto, as well, like OTR. Non-encrypted chat should be off by default IMHO,

This can be regulated in the app somehow, by warning users or blocking unencrypted messages until the user explicitly approves them.

daniele-athome avatar Jul 07 '15 14:07 daniele-athome

FWIW even if Kontalk federates with regular jabber servers, I think the server should not keep track of your contact list and you should not be able to "add user".

Why not?

Because this way all relevant data is stored on the user side (in the address book) and not on the server. For example in the conversations chat client, some of the people represent people in my address book, some of them don't and some of them do, but the accounts are not connected and a different picture is shown. This is very confusing for the user, the behaviour should always be the same!

This can be regulated in the app somehow, by warning users or blocking unencrypted messages until the user explicitly approves them.

Yes, that would be good!

h-2 avatar Sep 07 '15 10:09 h-2

I was just trying to connect another XMPP account to my Kontalk account, and I noticed that I can send messages to Kontalk (unencrypted of course), but Kontalk won't send messages back (complains about missing public key).

Is that at least easy to "fix"? I know that means degrading the encryption.

ameenross avatar May 12 '16 12:05 ameenross

@ameenross you'll have to disable encryption for now. If either #633 or #376 is implemented, encryption will become interoperable.

pravi avatar May 12 '16 12:05 pravi

Sorry @ameenross, but @pravi is right, although I think you made a typo: #376 refers to a different matter (maybe you meant #271?).

daniele-athome avatar May 12 '16 17:05 daniele-athome

@daniele-athome I meant #132 (OMEMO).

pravi avatar May 16 '16 12:05 pravi