From: Gabriel Scherer <email@example.com>
To: Adrien Nader <firstname.lastname@example.org>
Cc: caml users <email@example.com>, whitequark <firstname.lastname@example.org>
Subject: Re: [Caml-list] IRC channels available on libera.chat
Date: Sun, 30 May 2021 18:22:48 +0200 [thread overview]
Message-ID: <CAPFanBGRw=OTa8c+GZ+BWAr1Ua96y=a4APH9s3Vh1mVameCn2w@mail.gmail.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 1246 bytes --]
Dear Adrien (and list),
Thanks for taking care of the migration!
I don't use IRC regularly anymore (it eats my time and makes my content
hard to find again), but I have made good use of whitequark's excellent IRC
log services over the last decade
Currently the log looks like #ocaml on freenode is still being logged, but
this channel is now empty.
(Of course logs still exist for any past discussions.)
Is there a similar log service for the libera.chat channel?
whitequark's webpage has a "Contact whitequark if your channel migrated to
another network" message, has anyone done so for #ocaml? (If not, I just
On Thu, May 27, 2021 at 10:35 AM Adrien Nader <email@example.com> wrote:
> Hopefully this is the last part of the story.
> Yotam Barnoy has set up the discord bot to use libera.chat.
> The matrix bridge is unofficially available now. The schema has changed
> and is now #ocaml:libera.chat . Some downtime should be expected in the
> near future but the fact is that the bridge is available.
> If you have control over something that still mentions freenode.net,
> please update it to use libera.chat instead.
[-- Attachment #2: Type: text/html, Size: 1914 bytes --]
next prev parent reply other threads:[~2021-05-30 16:24 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-05-20 8:16 Adrien Nader
2021-05-26 14:01 ` Adrien Nader
2021-05-27 8:34 ` Adrien Nader
2021-05-30 16:22 ` Gabriel Scherer [this message]
2021-05-30 17:46 ` whitequark
2021-06-18 9:52 ` Romain Calascibetta
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:
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
* 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).