From: Ed W <lists@wildgooses.com>
To: "Niccolò Belli" <darkbasic@linuxsystems.it>
Cc: lartc@vger.kernel.org,
"netfilter@vger.kernel.org" <netfilter@vger.kernel.org>,
Linux Networking Developer Mailing List <netdev@vger.kernel.org>
Subject: Re: [Announce] LARTC wiki available
Date: Mon, 02 Jan 2012 12:48:23 +0000 [thread overview]
Message-ID: <4F01A797.1040406@wildgooses.com> (raw)
In-Reply-To: <4EFC9FC2.1090503@linuxsystems.it>
On 29/12/2011 17:13, Niccolò Belli wrote:
> Il 29/12/2011 17:19, Hagen Paul Pfeifer ha scritto:
>> But I don't like the idea to outhouse the existing wiki. Why two wikis?
>
> Because if you need an invite to edit something then it isn't a wiki
> anymore, for example.
Wikis seem to be massive spam targets at the moment (I run a small wiki,
I added registration to try and limit spammers, then I added silly
captchas, then I added some auto spam word recognition. I'm now at the
point that for such a small and niche wiki I might just get people to
apply to me personally for an edit option, it's just too boring dealing
with the spam...)
Good luck
Ed W
next prev parent reply other threads:[~2012-01-02 12:48 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-12-28 15:52 [Announce] LARTC wiki available Niccolò Belli
2011-12-29 0:27 ` Hagen Paul Pfeifer
2011-12-29 9:37 ` Niccolò Belli
2011-12-29 16:19 ` Hagen Paul Pfeifer
2011-12-29 17:13 ` Niccolò Belli
2011-12-29 19:04 ` John A. Sullivan III
2011-12-29 19:04 ` John A. Sullivan III
2012-01-02 12:48 ` Ed W [this message]
2012-01-02 13:07 ` Niccolò Belli
2012-06-01 16:42 ` Niccolò Belli
2012-06-01 19:12 ` Julien Vehent
2012-06-01 19:12 ` Julien Vehent
2012-06-02 14:37 ` Andy Furniss
2012-06-02 14:43 ` Andy Furniss
2012-06-02 15:50 ` Eric Dumazet
2012-06-02 16:58 ` Andy Furniss
2012-06-03 2:36 ` Jesper Dangaard Brouer
2012-06-03 20:05 ` Philip Prindeville
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=4F01A797.1040406@wildgooses.com \
--to=lists@wildgooses.com \
--cc=darkbasic@linuxsystems.it \
--cc=lartc@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=netfilter@vger.kernel.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 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.