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

[–] leetnewb@beehaw.org 1 points 5 months ago (1 children)

One other thought. I was under the (possibly faulty) impression that the first login of a snikket client helps the omemo process. Have you logged in with the mobile client yet?

I've had mixed results with omemo shenanigans on snikket iOS. Not sure how well PWAs work on iOS, but I considered encouraging my users to try one over the native client.

[–] activistPnk 1 points 5 months ago

I started with the snikket android app, which I actually rely on for inbound messages because if my desktop is shutdown when a msg arrives, Profanity will never get it. I occassionally send a msg using the Snikket app and it has a better success rate than Profanity.