Return-Path: Delivered-To: apmail-xml-cocoon-dev-archive@xml.apache.org Received: (qmail 39506 invoked by uid 500); 15 Mar 2003 11:59:34 -0000 Mailing-List: contact cocoon-dev-help@xml.apache.org; run by ezmlm Precedence: bulk list-help: list-unsubscribe: list-post: Reply-To: cocoon-dev@xml.apache.org Delivered-To: mailing list cocoon-dev@xml.apache.org Received: (qmail 39488 invoked from network); 15 Mar 2003 11:59:33 -0000 Received: from unknown (HELO f1.internuscorp.com) (210.19.205.240) by daedalus.apache.org with SMTP; 15 Mar 2003 11:59:33 -0000 Received: from localhost ([210.19.205.254]) (authenticated) by f1.internuscorp.com (8.11.2/8.11.2) with ESMTP id h2FCBAB27633 for ; Sat, 15 Mar 2003 20:11:10 +0800 Content-Type: text/plain; charset="iso-8859-1" From: Niclas Hedhman To: cocoon-dev@xml.apache.org Subject: Re: [heads-up] wiki abuse: your advice please Date: Sat, 15 Mar 2003 19:52:03 +0800 X-Mailer: KMail [version 1.4] References: In-Reply-To: X-Accept-Language: en en_us MIME-Version: 1.0 Content-Transfer-Encoding: quoted-printable Message-Id: <200303151952.04130.niclas@hedhman.org> X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N On Saturday 15 March 2003 18:29, Matt Sergeant wrote: > On Friday, Mar 14, 2003, at 13:46 Europe/London, Steven Noels wrote: > > while briefly checking the Wiki, I was confronted with some apparent > > abuse: people uploading attachments which don't have much to do with > > Cocoon (possibly just making benefit of the bandwidth we are > > sponsoring), people playing around on certain non-Sandbox pages, even > > to the extreme of erasing the Main page, and various other > > not-so-funny things. I'm very happy to see some people go in and > > correct, and the new 'restore latest version' feature of JSPWiki sure > > helps with this. > > > > Nevertheless, I'm annoyed a bit by the lack of adult behaviour by som= e > > IP addresses, and was wondering whether (and how) I should block them= =2E > > I know this sounds pretty harsh, and that's why I'm polling you guys > > to see what you would think would be a fair policy. > > FYI, when people do this on the Apache AxKit Wiki, I block their IP at > our firewall. Harsh, but fair. And no complaints so far. If I have malicious intent, I just dial-up an ISP and go ahead with it. Y= our=20 remedy is not effective. I have proposed a simple login instead... Just make you accountable is a = great=20 deterent.