From: Hanno Perrey <hanno@hoowl.se>
To: emacs-orgmode@gnu.org, Russell Adams <RLAdams@adamsinfoserv.com>
Subject: Re: [ANN] org-jami-bot
Date: Wed, 19 Apr 2023 09:44:26 +0200 [thread overview]
Message-ID: <0F31C4E0-6070-4FB4-B663-EE11F00E99DD@hoowl.se> (raw)
In-Reply-To: <ZD6H9D4MAv/b4xH8@swain.private>
>Hanno, this is brilliant.
>
>I rely heavily on using XMPP notifications with my Emacs/Org setup for
>appointments. I run a local program for send-xmpp to fire off messages
>that alert my multiple PC's and my cell phone on my XMPP account.
>
>I hadn't considered sending data BACK. That's awesome!
>
>How hard would it be to port this to a message agnostic style where
>other methods could be used?
>
>I've used Jami before, but I consider it VOIP software trying to
>become messenger, where XMPP is messenger trying to become VOIP. I've
>had battery problems in the past with Jami, but that was back when it
>was called Ring.
>
>I may have to try and adapt this to my workflow.
Hej Russell!
Thank you! I am very glad that you liked the idea and consider adding it to your workflow!
With some refactoring, it should absolutely be possible to make the bot and capturing more protocol-agnostic. The stack would be more like
jami.el/xmpp.el->chat-bot.el->org-capture-bot.el
So some more abstraction would be needed but it could be doable without too much work and make sense from a code re-usability perspective.
Do you know of a maintained XMPP client written in Elisp to start looking into?
I'd be happy to discuss this in mode detail with you if you are up for working together in this direction! :)
Best wishes,
Hanno
next prev parent reply other threads:[~2023-04-19 7:45 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-17 19:22 [ANN] org-jami-bot Hanno Perrey
2023-04-18 4:51 ` Marcin Borkowski
2023-04-18 11:34 ` Ihor Radchenko
2023-04-19 7:30 ` Hanno
2023-09-01 11:59 ` Ihor Radchenko
2023-04-18 12:07 ` Russell Adams
2023-04-19 7:44 ` Hanno Perrey [this message]
2023-04-20 9:08 ` Ihor Radchenko
2023-04-20 7:27 ` Max Nikulin
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.orgmode.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=0F31C4E0-6070-4FB4-B663-EE11F00E99DD@hoowl.se \
--to=hanno@hoowl.se \
--cc=RLAdams@adamsinfoserv.com \
--cc=emacs-orgmode@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.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
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).