public inbox for linux-media@vger.kernel.org
 help / color / mirror / Atom feed
From: Johannes Stezenbach <js@linuxtv.org>
To: "H. Langos" <henrik-dvb@prak.org>
Cc: linux-media@vger.kernel.org
Subject: Re: wiki on linixtv.org locked
Date: Mon, 27 Apr 2009 19:37:41 +0200	[thread overview]
Message-ID: <20090427173741.GA20847@linuxtv.org> (raw)
In-Reply-To: <20090427164321.GN2895@www.viadmin.org>

On Mon, Apr 27, 2009 at 06:43:21PM +0200, H. Langos wrote:
> 
> Yesterday a stupid kid vandalized a bunch of pages on the linuxtv wiki and 
> a sysop locked to database to undo the damage. 
> 
> I would have preferred to undo that damage by simply taking a look at 
> the users contribution page and using the handy-dandy undo function as a
> mere wiki user. 
> 
> It would have deprived that individual the satifaction of gaining the 
> sysop's attention with his anti-social behavior, but thats probably a 
> policy decision that is not mine to make.

The damage was done by a bot script and it affected as many pages
as the edit rate limiter would allow it to do until I noticed it.
If you search for "GRAWP'S MASSIVE" you'll see this is not
limited to linuxtv.org.

> Anyway .. Now, after about 24h the wiki is still locked.
> Any reason for that?

It is locked until I had time to take measures to prevent
similar damage from happening again right away. I'm
open to suggestions if someone has experience with this.


Johannes

  reply	other threads:[~2009-04-27 17:37 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-04-27 16:43 wiki on linixtv.org locked H. Langos
2009-04-27 17:37 ` Johannes Stezenbach [this message]
2009-04-27 20:29   ` H. Langos
2009-04-27 22:14     ` Johannes Stezenbach
2009-04-27 23:21       ` H. Langos
2009-04-28  8:20         ` Johannes Stezenbach
2009-04-28  8:25           ` H. Langos

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=20090427173741.GA20847@linuxtv.org \
    --to=js@linuxtv.org \
    --cc=henrik-dvb@prak.org \
    --cc=linux-media@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox