From: Tomasz Chmielewski <mangoo@wpkg.org>
To: kvm@vger.kernel.org, avi@redhat.com
Subject: Re: Call for help: moving the kvm wiki
Date: Fri, 10 Oct 2008 16:32:28 +0200 [thread overview]
Message-ID: <48EF677C.80901@wpkg.org> (raw)
> As you may have noticed, the kvm wiki is overrun by spammers. It the
> past I've regularly cleaned up the spam, but some time ago I've given up.
>
> So I'm looking for a volunteer to locate a spam-free public wiki host
> (candidates include wiki.kernel.org and fedorahosted.org) and transfer
> the contents (minus the spam). I don't think we need to transfer the
> editing history, but the conversion should adapt to the target's wiki
> syntax.
Just use captcha or a similar system with your existing wiki.
My experience with administering wikis is:
* if you don't use any preventive measures, your wiki will turn into a
collection of garbage very soon, unless you spend lots of time
monitoring changes
* requiring users to register before using the wiki results in:
- much less contributions from users - very big disadvantage,
- fewer spam, but bots can register, so some spam will go through
* using captcha or a similar system prevents 100% of spam
- lots of people don't like captchas very much, as often they are hard
to read
- personally, on my site (http://wpkg.org) user has to solve a simple
mathematics equation before the changes are accepted, like:
10 + 7 = ... [Accept button]
So I suggest going through a list of extensions/plugins for MoinMoin
(this is the wiki KVM uses), choosing something appropriate, and the
spam should be gone.
--
Tomasz Chmielewski
http://wpkg.org
next reply other threads:[~2008-10-10 14:32 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-10-10 14:32 Tomasz Chmielewski [this message]
2008-10-12 9:33 ` Call for help: moving the kvm wiki Avi Kivity
-- strict thread matches above, loose matches on Subject: below --
2008-10-09 12:59 Avi Kivity
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=48EF677C.80901@wpkg.org \
--to=mangoo@wpkg.org \
--cc=avi@redhat.com \
--cc=kvm@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.