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.
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).
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.
Will definitely have a look.
And of course, I meant “using XMPP on my own, secure server”. WhatsApp requires no configuration, the XMPP server I use is a different story. It was hard enough to get them to move away from WhatsApp, imagine asking them now to use yet another one.
But thanks for the link, will definitely be looking into it.
deleted by creator
deleted by creator
deleted by creator
deleted by creator
deleted by creator
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.
deleted by creator
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).
deleted by creator
I think it was maybe a month ago or so.
deleted by creator
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.
deleted by creator
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.
deleted by creator
They do exist?
deleted by creator
Nobody in my family is going to configure their chat app to use XMPP. So yes, it exists. But no one is using it.
deleted by creator
Will definitely have a look. And of course, I meant “using XMPP on my own, secure server”. WhatsApp requires no configuration, the XMPP server I use is a different story. It was hard enough to get them to move away from WhatsApp, imagine asking them now to use yet another one. But thanks for the link, will definitely be looking into it.