git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Jan Krüger" <jk@jk.gs>
To: Kevin Daudt <me@ikke.info>
Cc: "Taylor Blau" <me@ttaylorr.com>, "Jeff King" <peff@peff.net>,
	"Michal Suchánek" <msuchanek@suse.de>,
	"Jonathan Nieder" <jrnieder@gmail.com>,
	"Emily Shaffer" <emilyshaffer@google.com>,
	"Git List" <git@vger.kernel.org>
Subject: Re: Should we do something with #git-devel on Freenode?
Date: Thu, 27 May 2021 19:18:17 +0200	[thread overview]
Message-ID: <7e9683aee2c0fea2ff77b82bfa547e15@jk.gs> (raw)
In-Reply-To: <YK6o/j7P0JIGW0Q0@alpha> (sfid-20210526_220104_053000_A173AE59)

Here's a bit of an update on the situation.

freenode has, indeed, scorched the earth by destroying more than 700
channels, simply for mentioning Libera in the topic (before they even
added a rule that forbids this). I was willing to wait and see how the
"new" freenode was going to pan out, but with stuff like this happening
I don't see that as an option anymore. Basically I expect freenode to
keep destroying community with no prior notice whenever they feel like
it, and who wants to stay in a place like that?

On 26.05.2021 22:01, Kevin Daudt wrote:

> In the mean time, the ircops on libera helped us to register #git there
> pending the official namespace registration from Junio (they have a
> backlog, so they are working through that).

#git on Libera is already picking up steam, though the numbers aren't
quite on the same level yet. However, an arbitrary quorum of regulars 
has
decided that it's time to throw the switch.

* We've moved the gitinfo bot to Libera (which required a fair bit of
   code rewriting to support the differences between their respective
   ircds);
* The IRC logger has moved;
* The old channel's topic has a link to https://gitirc.eu/fnmove.html
   which explains the situation.

I expect that if anyone from freenode staff notices this, the channel
on freenode will get destroyed soon after...

  reply	other threads:[~2021-05-27 17:23 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-05-19 17:47 Should we do something with #git-devel on Freenode? Emily Shaffer
2021-05-19 19:08 ` Jonathan Nieder
2021-05-19 23:22   ` Junio C Hamano
2021-05-20  7:11   ` Michal Suchánek
2021-05-20 17:19     ` Jeff King
2021-05-20 18:08       ` Emily Shaffer
2021-05-20 21:20       ` Junio C Hamano
2021-05-21 11:19         ` Kevin Daudt
2021-07-02 12:15         ` Ævar Arnfjörð Bjarmason
2021-07-02 15:23           ` Junio C Hamano
2021-05-21 18:38       ` Felipe Contreras
2021-05-21 20:12         ` Randall S. Becker
2021-05-26 23:35         ` Ævar Arnfjörð Bjarmason
2021-05-26 23:59           ` Felipe Contreras
2021-05-27  0:24           ` Đoàn Trần Công Danh
2021-05-26 18:47       ` Taylor Blau
2021-05-26 20:01         ` Kevin Daudt
2021-05-27 17:18           ` Jan Krüger [this message]
2021-05-27 21:54             ` Ævar Arnfjörð Bjarmason
2021-05-28  1:26               ` Felipe Contreras
2021-05-28  1:36                 ` Taylor Blau
2021-05-28  3:29                   ` Felipe Contreras
2021-05-28  8:00               ` Jan Krüger
2021-05-28 14:37                 ` Phillip Susi

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=7e9683aee2c0fea2ff77b82bfa547e15@jk.gs \
    --to=jk@jk.gs \
    --cc=emilyshaffer@google.com \
    --cc=git@vger.kernel.org \
    --cc=jrnieder@gmail.com \
    --cc=me@ikke.info \
    --cc=me@ttaylorr.com \
    --cc=msuchanek@suse.de \
    --cc=peff@peff.net \
    /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).