From: David Woodhouse <dwmw2@infradead.org>
To: "Jason A. Donenfeld" <Jason@zx2c4.com>, Joe Doss <joe@solidadmin.com>
Cc: WireGuard mailing list <wireguard@lists.zx2c4.com>
Subject: Re: Dealing with list volume
Date: Fri, 08 Dec 2017 09:02:05 +0000 [thread overview]
Message-ID: <1512723725.1996.9.camel@infradead.org> (raw)
In-Reply-To: <CAHmME9r4tqFcVXQMaH-sfiNZZEjHjR2PyYbomWOCBObJ6E2+uw@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 799 bytes --]
On Fri, 2017-12-08 at 03:33 +0100, Jason A. Donenfeld wrote:
>
> I've recently been vortexing people who need super basic help toward
> #wireguard, in order to leave this list for discussion of all sorts,
> whether it's discussion of interesting user related things ("how do I
> do this new and interesting thing I couldn't find any documentation
> about?") or development things or bikeshedding or whatever else.
How does that work out for you? That same class of (potential) users
has a tendency to fire up an IRC client for the first time ever, join
the IRC channel they were directed to, say "hi" or *perhaps* if we're
lucky actually ask their question... and then disconnect again 30
seconds later if they don't get instant gratification.
At least in email you can follow up :)
[-- Attachment #2: smime.p7s --]
[-- Type: application/x-pkcs7-signature, Size: 4938 bytes --]
next prev parent reply other threads:[~2017-12-08 8:55 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
2017-12-08 2:33 ` Jason A. Donenfeld
2017-12-08 9:02 ` David Woodhouse [this message]
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=1512723725.1996.9.camel@infradead.org \
--to=dwmw2@infradead.org \
--cc=Jason@zx2c4.com \
--cc=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).