From: James Thomas <jimjoe@gmx.net>
To: help-gnu-emacs@gnu.org
Subject: Re: XMPP with OMEMO?
Date: Thu, 02 Jan 2025 18:48:02 +0530 [thread overview]
Message-ID: <86v7uxs6b9.fsf@gmx.net> (raw)
In-Reply-To: <87jzbmdplv.fsf@librehacker.com> (Christopher Howard's message of "Thu, 26 Dec 2024 13:52:12 -0900")
Christopher Howard wrote:
> Are there any Emacs XMPP clients out there which support OMEMO? I'd
> like to give up my Gajim and do my XMPP comms over Emacs, but I don't
> want to give up OMEMO. The only client I'm seeing on the wiki is
> JabberEl, which does not support encryption.
I used to use ricrc + bitlbee + lurch (but eventually got bit by
bugs[1]). So have now shifted to purple-presage for the latter (not
XMPP) and life's good again.
1: https://github.com/gkdr/lurch/issues/173 (I think)
--
next prev parent reply other threads:[~2025-01-02 13:18 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-12-26 22:52 XMPP with OMEMO? Christopher Howard
2024-12-27 10:48 ` Jean Louis
2024-12-27 23:49 ` W. Greenhouse via Users list for the GNU Emacs text editor
2025-01-02 13:18 ` James Thomas [this message]
2025-01-02 16:36 ` Christopher Howard
2025-01-02 19:25 ` James Thomas
2025-01-03 2:52 ` James Thomas
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=86v7uxs6b9.fsf@gmx.net \
--to=jimjoe@gmx.net \
--cc=help-gnu-emacs@gnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).