@syntax
I want to set up Prosody as well.
Got any tips and/or links to good instructions for me?
@FreePietje Update: It seems the latest versions of Profanity support OMEMO, but the deb packages for these versions aren't available in stable repo: https://packages.debian.org/testing/profanity
@syntax
And they won't be due to Debian Stable's policy.
But there are packages in Buster-backports. They're not (yet?) as up-to-date as the ones in Bullseye/Sid, but they do support OMEMO.
I'm not really a fan of Pidgin, so thanks for alerting me to the existence of Profanity :)
@FreePietje Yeah Profanity is nice. I tested it and it works fine. I'm just not sure whether I want the hassle of manually installing a newer version from source, as I'll hardly be using XMPP much anyway. I just wanted to consider it as a backup E2E encrypted, decentralised messaging solution in place of Signal etc. I really like Session messenger too, but again no one I know uses it... It took long enough persuading people to install Signal!
@FreePietje Just installed Profanity 0.9x through backports. Hope OMEMO works...
@syntax
Please do report whether OMEMO works, as that is for me the most important feature.
@FreePietje It works :) I've just tested it as follows:
1. Launch profanity on Debian and log into server with my admin user;
2. Launch Conversations on LineageOS and "enable" my other, test user;
3. In Profanity, run "/carbons on", then "/omemo gen", then initiate a chat with test user;
4. In Profanity chat window, run "/omemo fingerprint test@<domain>", then "/omemo trust <fingerprint>", then "'/omemo start" (you should see "OMEMO" replace "unencrypted" at top of chat window [1/2]
@FreePietje [2/2] Sending a message now should be E2E encrypted. I'm pretty sure this is how I did it and now the messages are all showing as secure.
@syntax
That is awesome 👍
Thanks so much :)
@FreePietje No problem, I want to use it in place of Signal now! In case this helps too: https://profanity-im.github.io/guide/latest/omemo.html
@syntax
Stable(/Buster) Backports are binary .deb packages, so you'd install/update it just like any other package. IOW, it's not 'installing from source'.
https://backports.debian.org/Instructions/
One of my (main) reasons to install/use #XMPP is precisely because a friend doesn't want to install Signal. Another one, somewhat related, is that it's actually decentralized.
I share your dilemma of trying to convert ppl yet again, so I won't do that for (quite) a while.