caml-list - the Caml user's mailing list
 help / color / mirror / Atom feed
From: Adrien Nader <>
Subject: Re: [Caml-list] IRC channels available on
Date: Wed, 26 May 2021 16:01:02 +0200	[thread overview]
Message-ID: <> (raw)
In-Reply-To: <>


Due to the behaviour of the new team on freenode, the future is clear
and has occurred much earlier than I had thought. The former freenode
staffers had been fairly good at doing things with people; the new
staffers seems to not prioritize communication and seems to have a BOFH
attitude instead.

As such everyone is quickly moving to and the control of
the #ocaml channel on freenode has been lost. Please point to instead of in all your links.
The matrix bridge is not available but should happen soon. As for the
dicord bot, I have no control about it. In any case, it's not worth
waiting to change your links because #ocaml on freenode has been
bleeding users, which means there are far far fewer people there to
answer questions.

An explanation of what happened today. A few hours ago, it all channels
mentioning "libera" in the topic and without a group registration but
using a single # in their names have been automatically changed to
automatically redirect people to their counterparts with double ##.
Their topic has been changed. While this comes from a long-time freenode
policy, the the channel has existed for almost 18 years and staffers
never enforced it (and the group registration stuff was impossible
during a decade).  That this only applies to channels which mentioned
"libera" in their topic exemplifies well the attitude of the new



  reply	other threads:[~2021-05-26 14:01 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 [this message]
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

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:

* 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).