9front - general discussion about 9front
 help / color / mirror / Atom feed
From: Stanley Lieber <sl@stanleylieber.com>
To: 9front@9front.org
Subject: Re: [9front] [FQA] some fixes
Date: Wed, 26 Jan 2022 14:23:48 +0000	[thread overview]
Message-ID: <AB72A5C6-0D42-425D-9974-74D51595CC24@stanleylieber.com> (raw)
In-Reply-To: <YfEhou/sPekMy6oV@wopr>

On January 26, 2022 10:25:38 AM UTC, Kurt H Maier <khm@sciops.net> wrote:
>On Wed, Jan 26, 2022 at 09:19:53AM +0100, cinap_lenrek@felloff.net wrote:
>> i never heard of #9front, wtf is going on?
>> 
>> --
>> cinap
>
>When we decamped to oftc I registered both #cat-v and #9front.  I think
>we had the idea of moving to #9front so that people would talk about
>9front instead of bloggers asking about harmful.cat-v.org and the stuff
>Uriel's not around to defend.  
>
>I'll hang onto both, regardless of the documentation decision.
>
>khm
>

my memory of this is that several years ago (when i was still regular on irc), #cat-v was flooded with nonsense, and we all decided to remove #cat-v from the 9front documentation. this was at a time when freenode/#9front existed and was populated. evidently i did a poor job of documenting this in the fqa hg log, so i can't point to any exculpatory commit messages.

sl

  reply	other threads:[~2022-01-26 14:28 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-01-17 20:13 mkf
2022-01-17 23:19 ` sirjofri
2022-01-23 23:07   ` mkf9
2022-01-24  2:53     ` ori
2022-01-25  2:17 ` Stanley Lieber
2022-01-26  6:53   ` mkf9
2022-01-26  8:19     ` cinap_lenrek
2022-01-26  8:34       ` Sigrid Solveig Haflínudóttir
2022-01-26 10:47         ` sirjofri
2022-01-26 14:10           ` hiro
2022-01-26 14:25           ` Stanley Lieber
2022-01-26 10:25       ` Kurt H Maier
2022-01-26 14:23         ` Stanley Lieber [this message]
2022-02-03  2:29 ` sl
2022-02-04 10:21   ` mkf9

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=AB72A5C6-0D42-425D-9974-74D51595CC24@stanleylieber.com \
    --to=sl@stanleylieber.com \
    --cc=9front@9front.org \
    --subject='Re: [9front] [FQA] some fixes' \
    /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

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