9front - general discussion about 9front
 help / color / mirror / Atom feed
From: stanley lieber <sl@stanleylieber.com>
To: 9front@9front.org
Subject: Re: [9front] State of the 9front mailing list archives
Date: Fri, 03 Jun 2016 14:45:42 -0400	[thread overview]
Message-ID: <D6AA6E32-A60B-406F-90C6-0540DC844FC7@stanleylieber.com> (raw)
In-Reply-To: <acc41739e9fdec695f36b5976275415b@felloff.net>

In the case of the guy trying to update his auth server, the information was already in the fqa. Granted, the requirement for performing this procedure after the old protocol was disabled by default was never made clear to anyone. Shit just suddenly broke. If someone happened to be on IRC when people were discussing it they might have picked up a clue. I probably could have handled this better by at least putting a notice in a release announcement.

In my previous mail I was responding more to the same discussion that gets held over and over on IRC by the same people about how accessing the mailing list archive is awkward and slow. Everyone always concludes they haven't studied the problem closely and then the topic dies for a while until it's time to complain again. The solutions always involve handing off responsibility to some third party service (read: Linux).

In this case I think gmane is a great idea. Hopefully the person who suggested it will contact me and tell me what I need to do to make it happen.

sl



  reply	other threads:[~2016-06-03 18:45 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-06-03 18:23 stanley lieber
2016-06-03 18:29 ` [9front] " cinap_lenrek
2016-06-03 18:45   ` stanley lieber [this message]
2016-06-03 20:27     ` cinap_lenrek
2016-06-04  6:31     ` BurnZeZ
2016-06-04 14:54       ` Benjamin Purcell
2016-06-04 21:35       ` arisawa
2016-06-03 18:51 ` Kurt H Maier

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=D6AA6E32-A60B-406F-90C6-0540DC844FC7@stanleylieber.com \
    --to=sl@stanleylieber.com \
    --cc=9front@9front.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).