caml-list - the Caml user's mailing list
 help / color / mirror / Atom feed
From: Jim Tittsler <jimt@onjapan.net>
To: Caml-list <caml-list@inria.fr>
Subject: Re: [Caml-list] Riot.im
Date: Tue, 5 Mar 2019 19:20:16 +0900	[thread overview]
Message-ID: <20190305102016.GA26111@onjapan.net> (raw)
In-Reply-To: <7KJq72wmmMloabH_YrMOM_Qzx8o2vg0V0mA9bmnwtKyXkWWYvPWZ8A8SOAE6Txd9USWaRVXclqOTZHOzuE6LlDizKR7GjGSi-UB_XIU4Gvg=@rj95.be>

On Mon, Mar 04, 2019 at 04:47:29PM +0000, RJ wrote:
> Is anyone interested in using the Matrix protocol as a form of
> communication via Riot.im? Its bridge functionality, reasonably
> well-designed GUI, [...]

I monitor the #ocaml IRC channel using the Riot client thanks to
the IRC bridge.  This makes it easy to review activity during
periods when I am not online.
  https://riot.im/app/#/room/#freenode_#ocaml:matrix.org




  reply	other threads:[~2019-03-05 10:20 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-03-04 16:47 RJ
2019-03-05 10:20 ` Jim Tittsler [this message]
2019-03-12 11:20 ` Andreas Poisel

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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20190305102016.GA26111@onjapan.net \
    --to=jimt@onjapan.net \
    --cc=caml-list@inria.fr \
    /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 NNTP newsgroup(s).