XMPP is very much e2e encrypted by default. It uses the same system as Signal in their OMEMO implementation, which is widely supported by XMPP clients.
And clients like Conversations also have a really nice and mass market compatible UI.
I think it’s supported but not turned on by default. At least when I tried conversations recently it was not default in one on ones, and not available at all in group chats.
Odd, for me it defaults in 1:1 chats, when was the last time you tried?
For group chats it AFAIK is enabled automatically if the group-chat creator has made the right settings for it to work (OMEMO can not work with pseudonymous chats and history disabled).
OMEMO can not work with pseudonymous chats and history disabled
OMEMO works fine in a private group chat, it’s disabled in public channels as there’s no point doing encryption there (when anyone can join and it’s impossible for verify everyone’s fingerprints).
If the other side of the 1:1 chat uses a client that does not support OMEMO by default, then something like that can happen. Did you at least get the big red warning sign that the 1:1 chat isn’t encrypted?
Conversations actually follows the Material guidelines from Google. Which puts it in an odd spot in that It looks “too new” for those that want a classic look, and “too old-fashion” for those that want a flashier look.
For me personally, it doesn’t look horrendous and it works, so I’m happy with it.
Please do some research and stop perpetuating this myth.
XMPP is not E2E encrypted by default.
Conversations does OMEMO by default.
There isn’t a single other XMPP client out there that does OMEMO by default, not one. They have support for it, but they very much do not enable it by default.
Every time a friend of mine uses a different messenger, I have to remind after getting a load of unencrypted messages to hit the damn padlock icon in their new client.
Easy, it doesn’t help if your friend goes onto discover another XMPP messenger (cause they want their messages on their laptop/iOS or something else).
There’s no global OMEMO option for these either, you have to remember to enable OMEMO for every single conversation. The community has been asking for this for years on github, but the developers just never bother to enable it.
XMPP is very much e2e encrypted by default. It uses the same system as Signal in their OMEMO implementation, which is widely supported by XMPP clients.
And clients like Conversations also have a really nice and mass market compatible UI.
OMEMO is not default. Even in the list you linked, half of the clients do not fully support it.
It is the default in the clients that cover like 95% of the user-base.
I think it’s supported but not turned on by default. At least when I tried conversations recently it was not default in one on ones, and not available at all in group chats.
Odd, for me it defaults in 1:1 chats, when was the last time you tried?
For group chats it AFAIK is enabled automatically if the group-chat creator has made the right settings for it to work (OMEMO can not work with pseudonymous chats and history disabled).
OMEMO works fine in a private group chat, it’s disabled in public channels as there’s no point doing encryption there (when anyone can join and it’s impossible for verify everyone’s fingerprints).
Yes, that is what I wrote ;)
I think it was maybe a month ago or so.
If the other side of the 1:1 chat uses a client that does not support OMEMO by default, then something like that can happen. Did you at least get the big red warning sign that the 1:1 chat isn’t encrypted?
Conversations UI can be MUCH improved to compete with the looks of some other common chat apps like messenger and imessage imho.
Conversations actually follows the Material guidelines from Google. Which puts it in an odd spot in that It looks “too new” for those that want a classic look, and “too old-fashion” for those that want a flashier look.
For me personally, it doesn’t look horrendous and it works, so I’m happy with it.
Please do some research and stop perpetuating this myth.
So compared to other messengers that have only one single official client, how is this any worse? If you use Conversations it is the same but better.
Easy, it doesn’t help if your friend goes onto discover another XMPP messenger (cause they want their messages on their laptop/iOS or something else).
There’s no global OMEMO option for these either, you have to remember to enable OMEMO for every single conversation. The community has been asking for this for years on github, but the developers just never bother to enable it.
How is that worse than Signal, Threema or Whatsapp where no such clients even exist?
They do exist?
All of which have a single client, similar to using Conversations only on XMPP.
Please show me how I can run Conversations on:
Once you’ve done that, feel free to join us at https://github.com/privacytools/privacytools.io/issues/1838 where people are actually trying to fix the issue.
Please show me how to run Signal or Whatsapp on a Desktop PC. Threema only has an unofficial and not very well working Desktop client.
iPhone is total crap, so I don’t care about that, but apparently there are some similar XMPP clients for it.