Mailing List Archive

vandalism
Maybe this has been asked before, anyway: couldn't a script be writtten
for administrators to roll back all changes made by a certain user or ip
address after a certain date/time, provided noone else has updated
since.

Links to articles that have been updated by someone else than the vandal
could be stored in a special Vandalism/Userxxxx/Versionyyy article for
easy reference.

Erik Zachte
Re: vandalism [ In reply to ]
Erik Zachte wrote:

>Maybe this has been asked before, anyway: couldn't a script be writtten
>for administrators to roll back all changes made by a certain user or ip
>address after a certain date/time, provided noone else has updated
>since.
>
>
I wrote about just that 10 minutes ago; didn't my mail make it through?

Anyway, on user contributions, all edits of a user that are still
current revision are now marked with "(top)". Makes it easier to see
what still needs reverting. Online for en and de.

Magnus
Re: Vandalism [ In reply to ]
> > - Send warning mail to Sysop (who solicited it) when a user modify some
> > pages in strange ways (articles size seriously reduced, too many articles
> > modify in a short laps, ...)
>
> Hmm...

Or more simple :
If a big sized article become very small, just display this update in red (or something visible) in the RecentChange page.

The problem is that the french Wikipedia is not as visited as the english version. We are afraid a vandal act when nobody is logged there.

Aoineko
Re: Vandalism [ In reply to ]
Brion Vibber wrote:

>Guillaume Blanchard wrote:

>>- Allow Sysop to have an easy way to block a logged user (in RecentChange if
>>possible).

>Hmm, right now it would be fairly easy to set it up to ban a username, but
>they could still log out and continue with the raw IP or a new username,
>which you'd have to block separately again...

If we block the raw IP, then the logged in user is also blocked.
So what we really need is a way to see the IP of a logged in user.
(No additional blocking functionality is needed, just IP viewing functionality.)

If moreover changes are tracked by IP as well as user name
(I believe that these are already separate entries in the database tables),
then we could track the effects of our bans better
(in the case of dynamic IPs that might be used by good logged in contributors)
by seeing *all* the contribs by an IP, not just anonymous contribs.


-- Toby