From: Phillip Susi <phill@thesusis.net>
To: "Jan Krüger" <jk@jk.gs>
Cc: "Ævar Arnfjörð Bjarmason" <avarab@gmail.com>,
"Kevin Daudt" <me@ikke.info>, "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: Fri, 28 May 2021 10:37:36 -0400 [thread overview]
Message-ID: <87k0niapmq.fsf@vps.thesusis.net> (raw)
In-Reply-To: <b8e48d464858c0ef6da2629dab507ebc@jk.gs>
Jan Krüger writes:
> If that was all that had happened, I would totally agree. Unfortunately,
> they did quite a bit more than that. They made a script that
> automatically ran the following actions on channels that mentioned
> "libera" in the topic:
>
> * sent a vague message about a ToS violation to the channel;
> * dropped the registration, including the full access list;
> * set the channel to moderated;
> * removed all ops;
> * set an auto-forward to a similarly named topic channel (e.g.
> #git-devel forwarded to ##git-devel);
> * made no attempt to give control of the topic channel to the previous
> community, i.e. the new channel would usually end up completely
> op-less and thus impossible to register at all. If it had been
> squatted by unrelated people beforehand, it would stay in their
> control.
Oh wow. That's crossing a line for me.
prev parent reply other threads:[~2021-05-28 14:39 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
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 [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=87k0niapmq.fsf@vps.thesusis.net \
--to=phill@thesusis.net \
--cc=avarab@gmail.com \
--cc=emilyshaffer@google.com \
--cc=git@vger.kernel.org \
--cc=jk@jk.gs \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.