caml-list - the Caml user's mailing list
 help / color / mirror / Atom feed
From: Romain Calascibetta <romain.calascibetta@gmail.com>
To: Gabriel Scherer <gabriel.scherer@gmail.com>
Cc: Adrien Nader <adrien@notk.org>, caml users <caml-list@inria.fr>,
	 whitequark <whitequark@whitequark.org>
Subject: Re: [Caml-list] IRC channels available on libera.chat
Date: Fri, 18 Jun 2021 11:52:57 +0200	[thread overview]
Message-ID: <CAOc4sy8YXd7CXD3cw0rUif6fkuM1iMt65_ARUetMUKA1XvKq_g@mail.gmail.com> (raw)
In-Reply-To: <CAPFanBGRw=OTa8c+GZ+BWAr1Ua96y=a4APH9s3Vh1mVameCn2w@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 1986 bytes --]

Hi all,

Just to let you know that I spent a time to re-implement the IRC protocol
in OCaml and to deploy a simple MirageOS as
a logger to save discussions into a Git repository. The bot is currently
deployed, the explanation is available here:
https://github.com/dinosaure/cri/tree/master/unikernel
And used for #mirage@irc.libera.chat

It's a nice example about MirageOS/unikernel and I may deploy one to save
#ocaml@irc.libera.chat as whitequark already does with her bot.

Thanks,

Le ven. 18 juin 2021 à 11:48, Gabriel Scherer <gabriel.scherer@gmail.com> a
écrit :

> 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
>   https://freenode.irclog.whitequark.org/ocaml/
>
> 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
> cc-ed whitequark.)
>
> Best
>
>
> On Thu, May 27, 2021 at 10:35 AM Adrien Nader <adrien@notk.org> wrote:
>
>> Hello,
>>
>> 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.
>>
>> Thanks,
>>
>> --
>> Adrien
>>
>

-- 
Romain Calascibetta - http://din.osau.re/

[-- Attachment #2: Type: text/html, Size: 3149 bytes --]

      parent reply	other threads:[~2021-06-18  9:53 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
2021-05-30 17:46       ` whitequark
2021-06-18  9:52       ` Romain Calascibetta [this message]

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=CAOc4sy8YXd7CXD3cw0rUif6fkuM1iMt65_ARUetMUKA1XvKq_g@mail.gmail.com \
    --to=romain.calascibetta@gmail.com \
    --cc=adrien@notk.org \
    --cc=caml-list@inria.fr \
    --cc=gabriel.scherer@gmail.com \
    --cc=whitequark@whitequark.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 NNTP newsgroup(s).