From: Joe Doss <joe@solidadmin.com>
To: wireguard@lists.zx2c4.com
Subject: Re: Dealing with list volume
Date: Thu, 7 Dec 2017 10:34:26 -0600 [thread overview]
Message-ID: <1463e6b8-2aff-b5f6-4375-dbce686f66c2@solidadmin.com> (raw)
In-Reply-To: <CAHmME9qmjgDJ3bXhWaZ86=iuLi+kDVmLqC0iZnU=3QHA0wBDMg@mail.gmail.com>
On 11/30/2017 07:03 AM, Jason A. Donenfeld wrote:
> Recently XDA learned about WireGuard, which has resulted in an influx
> of teenagers writing in, sometimes with their mailing addresses, and
> generally decreasing the overall quality of discussion here. As
> WireGuard becomes more well known, this kind of thing is expected to
> continue. I'd prefer for this list to stay one where it's easy to stay
> up to date and "read every post". I'll be enabling some mailman
> filters in the coming days to try and filter some things out and keep
> things sane around here. If you all have any suggestions or requests
> with regards to this, I'm happy to listen to them.
We do need a place for users to communicate that isn't going to collide
with devel chatter. https://www.discourse.org/ is pretty great for
users, easy to use and not terrible to self host. I think it would be
good to give users a non mailing list place to self help on their problems.
I would be willing to donate the server needed to run one for WireGuard
and the time/energy to set it up and keep it running. If you want to
keep things in email, set up a wg-users list and call it a day.
Joe
--
Joe Doss
joe@solidadmin.com
next prev parent reply other threads:[~2017-12-07 16:27 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-11-30 13:03 Jason A. Donenfeld
2017-11-30 13:59 ` Mytril
2017-11-30 14:03 ` Jason A. Donenfeld
2017-12-01 23:01 ` Ferris Ellis
2017-12-03 14:03 ` Jason A. Donenfeld
2017-12-07 16:34 ` Joe Doss [this message]
2017-12-08 2:33 ` Jason A. Donenfeld
2017-12-08 9:02 ` David Woodhouse
2017-12-08 16:44 ` Joe Doss
2017-12-08 17:56 ` Daniel Kahn Gillmor
2017-12-08 18:09 ` Joe Doss
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=1463e6b8-2aff-b5f6-4375-dbce686f66c2@solidadmin.com \
--to=joe@solidadmin.com \
--cc=wireguard@lists.zx2c4.com \
/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).