this post was submitted on 22 May 2024
1 points (100.0% liked)

XMPP

316 readers
1 users here now

XMPP (aka Jabber) is the community-owned standard for real-time federated messaging.

For a quick start click here

JoinJabber.org support chat

JoinJabber.org admin support chat

XMPP.net Provider List

Also see JoinJabber.org FAQ

founded 1 year ago
MODERATORS
 

“Profanity” is an XMPP app. (For those who got the wrong idea about the title)

What I use:

  • Debian with Profanity (preferred for the proper keyboard and TUI)
  • Android with Snikket

What my low-tech comrades use:

  • iOS with Snikket

It’s a bit of a disaster. One iOS-Snikket user gets my msgs but never a notification. Another iOS-Snikket user is plagued with that error msg (some bogus msg about OMEMO being unsupported). My comrades are at the edge of sanity since I’m the one who imposed xmpp+omemo on them, and they have little tolerance for all the problems.

I’m not sure what to try next. I would hate to replace Profanity because it’s the only decent text based option with official debian support. Would it help if the iOS users switch from Snikket to Monocles?

you are viewing a single comment's thread
view the rest of the comments
[–] [email protected] 0 points 5 months ago* (last edited 5 months ago) (6 children)

The server is snikket.chat.

I am not sure what causes the OMEMO error though as I am not a iOS user.

I believe Profanity is mostly to blame for those errors. Profanity loses track of keys and fingerprints of other users, and I think what it does is encrypts the msg to myself, then transmits it without encrypting to the recipient. Then the recipient gets a msg that’s encrypted to others but they cannot decrypt it. Then to worsen matters it seems XMPP uses the same incorrect error message for many different situations. Profanity really needs to change so if any of the recipients keys are not found, it should refuse to send the msg. I see a bogus error on my end as well, and the fix is to disable OMEMO the re-enable it (/OMEMO end; /OMEMO start).

In any case, thanks for the suggestion. I’ll see if I can get someone to try that app. I cannot be fussy about features. I really just need text msgs to work.

[–] [email protected] 0 points 5 months ago* (last edited 5 months ago) (2 children)

Hmm, yes if Profanity forgets the public keys of other chat participants then it can not encrypt messages for them. But it seems odd that Profanity would lose those keys. Most people complain about too many keys in XMPP apps ;) Is it possible to replicate the issue in Profanity so that you could open a bug report?

Otherwise, assuming you want to stick to TUI clients, maybe try https://poez.io/ ? It seems to be packages for Debian as well. There is also a new project that might be worth a try: https://github.com/paulfariello/aparte/

[–] [email protected] 0 points 5 months ago (1 children)

Thanks for the info.. i'll check out poezio for sure.

Regarding the bug, it has already been reported→ https://github.com/profanity-im/profanity/issues/1615

[–] [email protected] 0 points 5 months ago

Might also be worth looking at Libervia's TUI.

load more comments (3 replies)