headers
Naoko Komura | 6 Apr 2010 00:07
Picon

Re: The change in the interface is coming

Hello.

A quick update:  The deployment of the new interface takes place at 06:00 UTC on April 6.  (11pm PDT, April 5) 

Updates during the deployment will be posted at twitter with the hashtag #wmvector

The questions and answers pages is still evolving, but the discussion page is dedicated to capture issues we couldn't surface from the conversations through the village pump and administrators' noticeboard.

http://usability.wikimedia.org/wiki/What%27s_new,_questions_and_answers

Administrators are putting together a site notice in multiple languages. If you speak a language other than English, German and French, please help out.

http://commons.wikimedia.org/wiki/MediaWiki_talk:Sitenotice#Interface_change

Thanks!

- Naoko





On Thu, Mar 25, 2010 at 8:48 PM, Naoko Komura <nkomura <at> wikimedia.org> wrote:
Hello.

The usability beta has been tried out by over 570,000 users across all Wikimedia projects and roughly 80% of those beta users continue using it [1]. As for Commons, about 7,500 users tried out the beta as of end of February and 86% of users are still using it. The usability team is planning to roll out the current beta interface including the new toolbar as the default interface in April and May; please refer to these blogs for more details.[2][3]

As the acceptance rate of the beta by Commons users is relatively high, we would like to make the switch for Commons at first in the second week of April. In order to facilitate the transition and to avoid critical issues, we would like to ask as many of you as possible to try Beta before that date, so that most issues are discovered and fixed before we go default. You can opt-in via the 'Try Beta' link at the top of your interface.

We appreciate that Commons heavily relies on custom user scripts and site-specific JavaScript; Our changes are not especially related to multimedia usability, but we need your help to make sure the most used tools are compatible with the new interface. If you encounter issues using the beta, please share your feedback on the dedicated page [4].

Many thanks in advance.

Naoko Komura and the User Experience Programs Team
Wikimedia Foundation

[1] http://usability.wikimedia.org/wiki/Beta_Feedback_Survey
[2] http://blog.wikimedia.org/2010/03/25/wikimedia-gets-ready-for-some-big-changes/
[3] http://techblog.wikimedia.org/2010/03/the-change-in-interface-is-coming/
[4] http://commons.wikimedia.org/wiki/Commons:Usability_issues_and_ideas

--
Support Free Knowledge:  http://wikimediafoundation.org/wiki/Donate



--
Support Free Knowledge:  http://wikimediafoundation.org/wiki/Donate
_______________________________________________
Commons-l mailing list
Commons-l@...
https://lists.wikimedia.org/mailman/listinfo/commons-l
Permalink | Reply | 0 comments |
headers
Krinkle | 8 Apr 2010 16:12
Picon
Gravatar

Counter Vandalism Unit - Looking for helpers !

Hi everybody.

First of all, for those of you who haven't been here, or didn't get the complete picture, here is a short summary of some recent events:
 * Last March, I started the Counter Vandalism Unit on Commons <http://commons.wikimedia.org/wiki/Commons:Counter_Vandalism_Unit>
 * Later that month, the edit-patrol function was enabled on Commons <http://commons.wikimedia.org/wiki/Commons:Village_pump/Archive/2010Mar#Marking_edits_as_patrolled>
 * After a Sitenotice, a few users have signed up to be "patrollers"; and with a small team of 3 to 4 regular patrollers, we keep a checklist of anonymous edits. <http://commons.wikimedia.org/wiki/COM:ANO#Anonymous_edits>


The Problem 

Vandalism on Commons is a big problem, which generates a large backlog. Commons is the primary media depository for most media used throughout Wikimedia. Vandalism on Commons therefore has a greater likelihood of affecting local projects.
And, this also brings along the source of vandalism: Vandals. 
Local vandals are only a click away from Commons. Some don't even realise they are no longer on the local wiki.
Some, whether or not knowing they've been blocked on a local project, continue vandalising on Commons.

So, having that said, we are looking for help !
The most important areas, for now, are live watches on IRC or recent changes, and the Checklists mentioned above.

Live watch

For a long time Commons has it's own cvn-channel on Freenode: #cvn-commons <irc://irc.freenode.net/#cvn-commons>.
Although there are about a dozen idling users and a bot at any one time, use of the channel for vandal-fighting is not as frequent as desired.

Watching live is probably the easiest and most effective way to fight vandalism.
Also, for those who don't have the time to patrol an entire daypart-checklist, this is a great way to contribute when they only have a spare few minutes. One can leave and join at any time, and click/patrol for all edits that are reported in the channel.

In comparison to the checklists, the CVN-channel has a couple of advantages. JelteBot (the recent-changes bot in #cvn-commons) emphasises edits based on blacklists and watchlists, making it easier to detect potential vandalism. (If you monitor other channels too, you could add /Warning!/ to your IRC-stalklist.)

So I recommend the "patroller" right for anybody who wishes to participate, which you can ask for here: http://commons.wikimedia.org/wiki/Commons:Requests_for_rights. Please feel free to join #cvn-commons, or Commons' main channel #wikimedia-commons, for more information about other ways to get involved.
Every user in the counter-vandalism channel, watching and reacting to the stream, reduces the backlog even more.

Watching live means the user can be reverted and warned directly; s/he will either get blocked if they continue disruption, or (not unlikely) the vandal will stop when s/he reads the warning.

Doing this live, instead of afterwards, prevents more vandalism, and thus generate less edits in the backlog.

Checklists

Since it's unlikely (though the impossible goal of Live watch) to click and patrol each and every link in the IRC channel, lots of links are missed.
Either because no-one was on watch, or it got lost in the fast stream of links.

For that, we have the checklists. These contain all unpatrolled anonymous edits from a certain time frame.
These are, until we have a much bigger team, the primary and most time-consuming ways of fighting vandalism.

Also, when you can't access IRC, or don't like it for some reason, the RecentChanges-page is a good alternative:

If you don't know how this works, check the following links to get you up to speed:
- http://www.youtube.com/watch?v=eJXvZ65ttQ4 (short video tutorial on the CVU)

Then visit the CVU and check out a portion/day-part:


Thank you for reading,

Yours,
Krinkle


--
Greetings,
Krinkle
A Wikipedia Volunteer
- Wikipedia, the free encyclopedia
 

_______________________________________________
Commons-l mailing list
Commons-l@...
https://lists.wikimedia.org/mailman/listinfo/commons-l
Permalink | Reply | 9 comments |
headers
Eusebius | 8 Apr 2010 16:38
Picon
Gravatar

Re: Counter Vandalism Unit - Looking for helpers !

Hi,

Thanks for this initiative. On my side I've significantly failed to build something for recent uploads patrolling.
Is there something like a patrolled upload on MediaWiki? Because I've always found recent uploads more problematic than recent edits, and being able to tell between patrolled and unpatrolled uploads would be GREAT.

Regards,
Eusebius

Krinkle a écrit :
Hi everybody.

First of all, for those of you who haven't been here, or didn't get the complete picture, here is a short summary of some recent events:
 * Last March, I started the Counter Vandalism Unit on Commons <http://commons.wikimedia.org/wiki/Commons:Counter_Vandalism_Unit>
 * Later that month, the edit-patrol function was enabled on Commons <http://commons.wikimedia.org/wiki/Commons:Village_pump/Archive/2010Mar#Marking_edits_as_patrolled>
 * After a Sitenotice, a few users have signed up to be "patrollers"; and with a small team of 3 to 4 regular patrollers, we keep a checklist of anonymous edits. <http://commons.wikimedia.org/wiki/COM:ANO#Anonymous_edits>


The Problem 

Vandalism on Commons is a big problem, which generates a large backlog. Commons is the primary media depository for most media used throughout Wikimedia. Vandalism on Commons therefore has a greater likelihood of affecting local projects.
And, this also brings along the source of vandalism: Vandals. 
Local vandals are only a click away from Commons. Some don't even realise they are no longer on the local wiki.
Some, whether or not knowing they've been blocked on a local project, continue vandalising on Commons.

So, having that said, we are looking for help !
The most important areas, for now, are live watches on IRC or recent changes, and the Checklists mentioned above.

Live watch

For a long time Commons has it's own cvn-channel on Freenode: #cvn-commons <irc://irc.freenode.net/#cvn-commons>.
Although there are about a dozen idling users and a bot at any one time, use of the channel for vandal-fighting is not as frequent as desired.

Watching live is probably the easiest and most effective way to fight vandalism.
Also, for those who don't have the time to patrol an entire daypart-checklist, this is a great way to contribute when they only have a spare few minutes. One can leave and join at any time, and click/patrol for all edits that are reported in the channel.

In comparison to the checklists, the CVN-channel has a couple of advantages. JelteBot (the recent-changes bot in #cvn-commons) emphasises edits based on blacklists and watchlists, making it easier to detect potential vandalism. (If you monitor other channels too, you could add /Warning!/ to your IRC-stalklist.)

So I recommend the "patroller" right for anybody who wishes to participate, which you can ask for here: http://commons.wikimedia.org/wiki/Commons:Requests_for_rights. Please feel free to join #cvn-commons, or Commons' main channel #wikimedia-commons, for more information about other ways to get involved.
Every user in the counter-vandalism channel, watching and reacting to the stream, reduces the backlog even more.

Watching live means the user can be reverted and warned directly; s/he will either get blocked if they continue disruption, or (not unlikely) the vandal will stop when s/he reads the warning.

Doing this live, instead of afterwards, prevents more vandalism, and thus generate less edits in the backlog.

Checklists

Since it's unlikely (though the impossible goal of Live watch) to click and patrol each and every link in the IRC channel, lots of links are missed.
Either because no-one was on watch, or it got lost in the fast stream of links.

For that, we have the checklists. These contain all unpatrolled anonymous edits from a certain time frame.
These are, until we have a much bigger team, the primary and most time-consuming ways of fighting vandalism.

Also, when you can't access IRC, or don't like it for some reason, the RecentChanges-page is a good alternative:

If you don't know how this works, check the following links to get you up to speed:
- http://www.youtube.com/watch?v=eJXvZ65ttQ4 (short video tutorial on the CVU)

Then visit the CVU and check out a portion/day-part:


Thank you for reading,

Yours,
Krinkle


--
Greetings,
Krinkle
A Wikipedia Volunteer
- Wikipedia, the free encyclopedia

_______________________________________________ Commons-l mailing list Commons-l-RusutVdil2icGmH+5r0DM0B+6BGkLq7r@public.gmane.org https://lists.wikimedia.org/mailman/listinfo/commons-l 

_______________________________________________
Commons-l mailing list
Commons-l@...
https://lists.wikimedia.org/mailman/listinfo/commons-l
Permalink | Reply | 8 comments |
headers
Krinkle | 8 Apr 2010 16:46
Picon
Gravatar

Re: Counter Vandalism Unit - Looking for helpers !

Hi Eusebius,

There is actually something that is 99% like what you are describing:


It's the NewPage-patrol, with the namespace filter set to "File", which is pretty much always an upload.

(though theoraticly there could be uploads without a page, and a page without an upload)

Please note that, like any patrollable action the action leaves the unpatrolled queue automaticly after 720 hours (30 days).
if you like, I could create a checklist-system for this aswell.

--
Greetings,
Krinkle

Op 8 apr 2010, om 16:38 heeft Eusebius het volgende geschreven:

Hi,

Thanks for this initiative. On my side I've significantly failed to build something for recent uploads patrolling.
Is there something like a patrolled upload on MediaWiki? Because I've always found recent uploads more problematic than recent edits, and being able to tell between patrolled and unpatrolled uploads would be GREAT.

Regards,
Eusebius

Krinkle a écrit :
Hi everybody.

First of all, for those of you who haven't been here, or didn't get the complete picture, here is a short summary of some recent events:
 * Last March, I started the Counter Vandalism Unit on Commons <http://commons.wikimedia.org/wiki/Commons:Counter_Vandalism_Unit>
 * Later that month, the edit-patrol function was enabled on Commons <http://commons.wikimedia.org/wiki/Commons:Village_pump/Archive/2010Mar#Marking_edits_as_patrolled>
 * After a Sitenotice, a few users have signed up to be "patrollers"; and with a small team of 3 to 4 regular patrollers, we keep a checklist of anonymous edits. <http://commons.wikimedia.org/wiki/COM:ANO#Anonymous_edits>


The Problem 

Vandalism on Commons is a big problem, which generates a large backlog. Commons is the primary media depository for most media used throughout Wikimedia. Vandalism on Commons therefore has a greater likelihood of affecting local projects.
And, this also brings along the source of vandalism: Vandals. 
Local vandals are only a click away from Commons. Some don't even realise they are no longer on the local wiki.
Some, whether or not knowing they've been blocked on a local project, continue vandalising on Commons.

So, having that said, we are looking for help !
The most important areas, for now, are live watches on IRC or recent changes, and the Checklists mentioned above.

Live watch

For a long time Commons has it's own cvn-channel on Freenode: #cvn-commons <irc://irc.freenode.net/#cvn-commons>.
Although there are about a dozen idling users and a bot at any one time, use of the channel for vandal-fighting is not as frequent as desired.

Watching live is probably the easiest and most effective way to fight vandalism.
Also, for those who don't have the time to patrol an entire daypart-checklist, this is a great way to contribute when they only have a spare few minutes. One can leave and join at any time, and click/patrol for all edits that are reported in the channel.

In comparison to the checklists, the CVN-channel has a couple of advantages. JelteBot (the recent-changes bot in #cvn-commons) emphasises edits based on blacklists and watchlists, making it easier to detect potential vandalism. (If you monitor other channels too, you could add /Warning!/ to your IRC-stalklist.)

So I recommend the "patroller" right for anybody who wishes to participate, which you can ask for here: http://commons.wikimedia.org/wiki/Commons:Requests_for_rights. Please feel free to join #cvn-commons, or Commons' main channel #wikimedia-commons, for more information about other ways to get involved.
Every user in the counter-vandalism channel, watching and reacting to the stream, reduces the backlog even more.

Watching live means the user can be reverted and warned directly; s/he will either get blocked if they continue disruption, or (not unlikely) the vandal will stop when s/he reads the warning.

Doing this live, instead of afterwards, prevents more vandalism, and thus generate less edits in the backlog.

Checklists

Since it's unlikely (though the impossible goal of Live watch) to click and patrol each and every link in the IRC channel, lots of links are missed.
Either because no-one was on watch, or it got lost in the fast stream of links.

For that, we have the checklists. These contain all unpatrolled anonymous edits from a certain time frame.
These are, until we have a much bigger team, the primary and most time-consuming ways of fighting vandalism.

Also, when you can't access IRC, or don't like it for some reason, the RecentChanges-page is a good alternative:

If you don't know how this works, check the following links to get you up to speed:
- http://www.youtube.com/watch?v=eJXvZ65ttQ4 (short video tutorial on the CVU)

Then visit the CVU and check out a portion/day-part:


Thank you for reading,

Yours,
Krinkle


--
Greetings,
Krinkle
A Wikipedia Volunteer
- Wikipedia, the free encyclopedia

_______________________________________________ Commons-l mailing list Commons-l-RusutVdil2icGmH+5r0DM8Xa4x6EXUF0@public.gmane.orgg https://lists.wikimedia.org/mailman/listinfo/commons-l

_______________________________________________
Commons-l mailing list
Commons-l-RusutVdil2icGmH+5r0DM8Xa4x6EXUF0@public.gmane.orgg
https://lists.wikimedia.org/mailman/listinfo/commons-l

_______________________________________________
Commons-l mailing list
Commons-l@...
https://lists.wikimedia.org/mailman/listinfo/commons-l
Permalink | Reply | 7 comments |
headers
Eusebius | 8 Apr 2010 17:08
Picon
Gravatar

Re: Counter Vandalism Unit - Looking for helpers !

Hi,

Thanks for your link.

Apparently, this only shows the page creations without upload, like before a Flickr upload bot action. "Standard" uploads do not seem to show.
Independently from this, even if a page could list all unpatrolled uploads, I think it wouldn't be suitable, because (for the patrolled edit be efficiently applied to recent uploads) a file upload should be marked as patrolled/unpatrolled independently of the edits on the file page. Indeed, recent edit patrollers will look for vandalism, and recent uploads patrollers will look for copyright violations, bad sources, missing permisions, etc. Depending on the experience and "patrolling profile" of both kinds of patrollers, patrols can have very different ("colliding") outcomes. This is why I suspect a different notion could be justified for patrolled uploads.

Here's what we tried to begin about recent uploads, for info: http://commons.wikimedia.org/wiki/Commons:Recent_uploads_patrol

Regards,
Eusebius

Krinkle a écrit :
Hi Eusebius,

There is actually something that is 99% like what you are describing:


It's the NewPage-patrol, with the namespace filter set to "File", which is pretty much always an upload.

(though theoraticly there could be uploads without a page, and a page without an upload)

Please note that, like any patrollable action the action leaves the unpatrolled queue automaticly after 720 hours (30 days).
if you like, I could create a checklist-system for this aswell.

--
Greetings,
Krinkle

Op 8 apr 2010, om 16:38 heeft Eusebius het volgende geschreven:

Hi,

Thanks for this initiative. On my side I've significantly failed to build something for recent uploads patrolling.
Is there something like a patrolled upload on MediaWiki? Because I've always found recent uploads more problematic than recent edits, and being able to tell between patrolled and unpatrolled uploads would be GREAT.

Regards,
Eusebius

Krinkle a écrit :
Hi everybody.

First of all, for those of you who haven't been here, or didn't get the complete picture, here is a short summary of some recent events:
 * Last March, I started the Counter Vandalism Unit on Commons <http://commons.wikimedia.org/wiki/Commons:Counter_Vandalism_Unit>
 * Later that month, the edit-patrol function was enabled on Commons <http://commons.wikimedia.org/wiki/Commons:Village_pump/Archive/2010Mar#Marking_edits_as_patrolled>
 * After a Sitenotice, a few users have signed up to be "patrollers"; and with a small team of 3 to 4 regular patrollers, we keep a checklist of anonymous edits. <http://commons.wikimedia.org/wiki/COM:ANO#Anonymous_edits>


The Problem 

Vandalism on Commons is a big problem, which generates a large backlog. Commons is the primary media depository for most media used throughout Wikimedia. Vandalism on Commons therefore has a greater likelihood of affecting local projects.
And, this also brings along the source of vandalism: Vandals. 
Local vandals are only a click away from Commons. Some don't even realise they are no longer on the local wiki.
Some, whether or not knowing they've been blocked on a local project, continue vandalising on Commons.

So, having that said, we are looking for help !
The most important areas, for now, are live watches on IRC or recent changes, and the Checklists mentioned above.

Live watch

For a long time Commons has it's own cvn-channel on Freenode: #cvn-commons <irc://irc.freenode.net/#cvn-commons>.
Although there are about a dozen idling users and a bot at any one time, use of the channel for vandal-fighting is not as frequent as desired.

Watching live is probably the easiest and most effective way to fight vandalism.
Also, for those who don't have the time to patrol an entire daypart-checklist, this is a great way to contribute when they only have a spare few minutes. One can leave and join at any time, and click/patrol for all edits that are reported in the channel.

In comparison to the checklists, the CVN-channel has a couple of advantages. JelteBot (the recent-changes bot in #cvn-commons) emphasises edits based on blacklists and watchlists, making it easier to detect potential vandalism. (If you monitor other channels too, you could add /Warning!/ to your IRC-stalklist.)

So I recommend the "patroller" right for anybody who wishes to participate, which you can ask for here: http://commons.wikimedia.org/wiki/Commons:Requests_for_rights. Please feel free to join #cvn-commons, or Commons' main channel #wikimedia-commons, for more information about other ways to get involved.
Every user in the counter-vandalism channel, watching and reacting to the stream, reduces the backlog even more.

Watching live means the user can be reverted and warned directly; s/he will either get blocked if they continue disruption, or (not unlikely) the vandal will stop when s/he reads the warning.

Doing this live, instead of afterwards, prevents more vandalism, and thus generate less edits in the backlog.

Checklists

Since it's unlikely (though the impossible goal of Live watch) to click and patrol each and every link in the IRC channel, lots of links are missed.
Either because no-one was on watch, or it got lost in the fast stream of links.

For that, we have the checklists. These contain all unpatrolled anonymous edits from a certain time frame.
These are, until we have a much bigger team, the primary and most time-consuming ways of fighting vandalism.

Also, when you can't access IRC, or don't like it for some reason, the RecentChanges-page is a good alternative:

If you don't know how this works, check the following links to get you up to speed:
- http://www.youtube.com/watch?v=eJXvZ65ttQ4 (short video tutorial on the CVU)

Then visit the CVU and check out a portion/day-part:


Thank you for reading,

Yours,
Krinkle


--
Greetings,
Krinkle
A Wikipedia Volunteer
- Wikipedia, the free encyclopedia

_______________________________________________ Commons-l mailing list Commons-l-RusutVdil2icGmH+5r0DMw@public.gmane.orgorg https://lists.wikimedia.org/mailman/listinfo/commons-l

_______________________________________________
Commons-l mailing list
Commons-l-RusutVdil2icGmH+5r0DMw@public.gmane.orgorg
https://lists.wikimedia.org/mailman/listinfo/commons-l

_______________________________________________ Commons-l mailing list Commons-l-RusutVdil2icGmH+5r0DM0B+6BGkLq7r@public.gmane.org https://lists.wikimedia.org/mailman/listinfo/commons-l 

_______________________________________________
Commons-l mailing list
Commons-l@...
https://lists.wikimedia.org/mailman/listinfo/commons-l
Permalink | Reply | 6 comments |
headers
Krinkle | 8 Apr 2010 17:13
Picon
Gravatar

Re: Counter Vandalism Unit - Looking for helpers !

Hi Eusebius,

Ah, indeed. I was wondering why it listed so few new files (the link I gave earlier). Uploads do indeed not get listed there. 
Special:NewFiles does but doesn't allow patrolling, I understand your request now.

That project definitely needs attention aswell.
I'll see if I can find a way to "patrollise" that.

--
Greetings,
Krinkle

Op 8 apr 2010, om 17:08 heeft Eusebius het volgende geschreven:

Hi,

Thanks for your link.

Apparently, this only shows the page creations without upload, like before a Flickr upload bot action. "Standard" uploads do not seem to show.
Independently from this, even if a page could list all unpatrolled uploads, I think it wouldn't be suitable, because (for the patrolled edit be efficiently applied to recent uploads) a file upload should be marked as patrolled/unpatrolled independently of the edits on the file page. Indeed, recent edit patrollers will look for vandalism, and recent uploads patrollers will look for copyright violations, bad sources, missing permisions, etc. Depending on the experience and "patrolling profile" of both kinds of patrollers, patrols can have very different ("colliding") outcomes. This is why I suspect a different notion could be justified for patrolled uploads.

Here's what we tried to begin about recent uploads, for info: http://commons.wikimedia.org/wiki/Commons:Recent_uploads_patrol

Regards,
Eusebius

Krinkle a écrit :
Hi Eusebius,

There is actually something that is 99% like what you are describing:


It's the NewPage-patrol, with the namespace filter set to "File", which is pretty much always an upload.

(though theoraticly there could be uploads without a page, and a page without an upload)

Please note that, like any patrollable action the action leaves the unpatrolled queue automaticly after 720 hours (30 days).
if you like, I could create a checklist-system for this aswell.

--
Greetings,
Krinkle

Op 8 apr 2010, om 16:38 heeft Eusebius het volgende geschreven:

Hi,

Thanks for this initiative. On my side I've significantly failed to build something for recent uploads patrolling.
Is there something like a patrolled upload on MediaWiki? Because I've always found recent uploads more problematic than recent edits, and being able to tell between patrolled and unpatrolled uploads would be GREAT.

Regards,
Eusebius

Krinkle a écrit :
Hi everybody.

First of all, for those of you who haven't been here, or didn't get the complete picture, here is a short summary of some recent events:
 * Last March, I started the Counter Vandalism Unit on Commons <http://commons.wikimedia.org/wiki/Commons:Counter_Vandalism_Unit>
 * Later that month, the edit-patrol function was enabled on Commons <http://commons.wikimedia.org/wiki/Commons:Village_pump/Archive/2010Mar#Marking_edits_as_patrolled>
 * After a Sitenotice, a few users have signed up to be "patrollers"; and with a small team of 3 to 4 regular patrollers, we keep a checklist of anonymous edits. <http://commons.wikimedia.org/wiki/COM:ANO#Anonymous_edits>


The Problem 

Vandalism on Commons is a big problem, which generates a large backlog. Commons is the primary media depository for most media used throughout Wikimedia. Vandalism on Commons therefore has a greater likelihood of affecting local projects.
And, this also brings along the source of vandalism: Vandals. 
Local vandals are only a click away from Commons. Some don't even realise they are no longer on the local wiki.
Some, whether or not knowing they've been blocked on a local project, continue vandalising on Commons.

So, having that said, we are looking for help !
The most important areas, for now, are live watches on IRC or recent changes, and the Checklists mentioned above.

Live watch

For a long time Commons has it's own cvn-channel on Freenode: #cvn-commons <irc://irc.freenode.net/#cvn-commons>.
Although there are about a dozen idling users and a bot at any one time, use of the channel for vandal-fighting is not as frequent as desired.

Watching live is probably the easiest and most effective way to fight vandalism.
Also, for those who don't have the time to patrol an entire daypart-checklist, this is a great way to contribute when they only have a spare few minutes. One can leave and join at any time, and click/patrol for all edits that are reported in the channel.

In comparison to the checklists, the CVN-channel has a couple of advantages. JelteBot (the recent-changes bot in #cvn-commons) emphasises edits based on blacklists and watchlists, making it easier to detect potential vandalism. (If you monitor other channels too, you could add /Warning!/ to your IRC-stalklist.)

So I recommend the "patroller" right for anybody who wishes to participate, which you can ask for here: http://commons.wikimedia.org/wiki/Commons:Requests_for_rights. Please feel free to join #cvn-commons, or Commons' main channel #wikimedia-commons, for more information about other ways to get involved.
Every user in the counter-vandalism channel, watching and reacting to the stream, reduces the backlog even more.

Watching live means the user can be reverted and warned directly; s/he will either get blocked if they continue disruption, or (not unlikely) the vandal will stop when s/he reads the warning.

Doing this live, instead of afterwards, prevents more vandalism, and thus generate less edits in the backlog.

Checklists

Since it's unlikely (though the impossible goal of Live watch) to click and patrol each and every link in the IRC channel, lots of links are missed.
Either because no-one was on watch, or it got lost in the fast stream of links.

For that, we have the checklists. These contain all unpatrolled anonymous edits from a certain time frame.
These are, until we have a much bigger team, the primary and most time-consuming ways of fighting vandalism.

Also, when you can't access IRC, or don't like it for some reason, the RecentChanges-page is a good alternative:

If you don't know how this works, check the following links to get you up to speed:
- http://www.youtube.com/watch?v=eJXvZ65ttQ4 (short video tutorial on the CVU)

Then visit the CVU and check out a portion/day-part:


Thank you for reading,

Yours,
Krinkle


--
Greetings,
Krinkle
A Wikipedia Volunteer
- Wikipedia, the free encyclopedia

_______________________________________________ Commons-l mailing list Commons-l-RusutVdil2icGmH+5r0DM8Xa4x6EXUF0@public.gmane.orgg https://lists.wikimedia.org/mailman/listinfo/commons-l

_______________________________________________
Commons-l mailing list
Commons-l-RusutVdil2icGmH+5r0DM8Xa4x6EXUF0@public.gmane.orgg
https://lists.wikimedia.org/mailman/listinfo/commons-l

_______________________________________________ Commons-l mailing list Commons-l-RusutVdil2icGmH+5r0DM8Xa4x6EXUF0@public.gmane.orgg https://lists.wikimedia.org/mailman/listinfo/commons-l

_______________________________________________
Commons-l mailing list
Commons-l-RusutVdil2icGmH+5r0DM8Xa4x6EXUF0@public.gmane.orgg
https://lists.wikimedia.org/mailman/listinfo/commons-l

_______________________________________________
Commons-l mailing list
Commons-l@...
https://lists.wikimedia.org/mailman/listinfo/commons-l
Permalink | Reply | 5 comments |
headers
Eusebius | 8 Apr 2010 17:19
Picon
Gravatar

Re: Counter Vandalism Unit - Looking for helpers !

Even without the patrolled edit thing, what we tried to launch would have been useful if people (admins) actually patrolling uploads had used it.
Maybe it's a usability/interface issue of some kind, but it most certainly is a kind of "sub-community building" issue.

"Patrolled uploads" would just be a nice bonus, maybe.

Regards,
Eusebius

Krinkle a écrit :
Hi Eusebius,

Ah, indeed. I was wondering why it listed so few new files (the link I gave earlier). Uploads do indeed not get listed there. 
Special:NewFiles does but doesn't allow patrolling, I understand your request now.

That project definitely needs attention aswell.
I'll see if I can find a way to "patrollise" that.

--
Greetings,
Krinkle

Op 8 apr 2010, om 17:08 heeft Eusebius het volgende geschreven:

Hi,

Thanks for your link.

Apparently, this only shows the page creations without upload, like before a Flickr upload bot action. "Standard" uploads do not seem to show.
Independently from this, even if a page could list all unpatrolled uploads, I think it wouldn't be suitable, because (for the patrolled edit be efficiently applied to recent uploads) a file upload should be marked as patrolled/unpatrolled independently of the edits on the file page. Indeed, recent edit patrollers will look for vandalism, and recent uploads patrollers will look for copyright violations, bad sources, missing permisions, etc. Depending on the experience and "patrolling profile" of both kinds of patrollers, patrols can have very different ("colliding") outcomes. This is why I suspect a different notion could be justified for patrolled uploads.

Here's what we tried to begin about recent uploads, for info: http://commons.wikimedia.org/wiki/Commons:Recent_uploads_patrol

Regards,
Eusebius

Krinkle a écrit :
Hi Eusebius,

There is actually something that is 99% like what you are describing:


It's the NewPage-patrol, with the namespace filter set to "File", which is pretty much always an upload.

(though theoraticly there could be uploads without a page, and a page without an upload)

Please note that, like any patrollable action the action leaves the unpatrolled queue automaticly after 720 hours (30 days).
if you like, I could create a checklist-system for this aswell.

--
Greetings,
Krinkle

Op 8 apr 2010, om 16:38 heeft Eusebius het volgende geschreven:

Hi,

Thanks for this initiative. On my side I've significantly failed to build something for recent uploads patrolling.
Is there something like a patrolled upload on MediaWiki? Because I've always found recent uploads more problematic than recent edits, and being able to tell between patrolled and unpatrolled uploads would be GREAT.

Regards,
Eusebius

Krinkle a écrit :
Hi everybody.

First of all, for those of you who haven't been here, or didn't get the complete picture, here is a short summary of some recent events:
 * Last March, I started the Counter Vandalism Unit on Commons <http://commons.wikimedia.org/wiki/Commons:Counter_Vandalism_Unit>
 * Later that month, the edit-patrol function was enabled on Commons <http://commons.wikimedia.org/wiki/Commons:Village_pump/Archive/2010Mar#Marking_edits_as_patrolled>
 * After a Sitenotice, a few users have signed up to be "patrollers"; and with a small team of 3 to 4 regular patrollers, we keep a checklist of anonymous edits. <http://commons.wikimedia.org/wiki/COM:ANO#Anonymous_edits>


The Problem 

Vandalism on Commons is a big problem, which generates a large backlog. Commons is the primary media depository for most media used throughout Wikimedia. Vandalism on Commons therefore has a greater likelihood of affecting local projects.
And, this also brings along the source of vandalism: Vandals. 
Local vandals are only a click away from Commons. Some don't even realise they are no longer on the local wiki.
Some, whether or not knowing they've been blocked on a local project, continue vandalising on Commons.

So, having that said, we are looking for help !
The most important areas, for now, are live watches on IRC or recent changes, and the Checklists mentioned above.

Live watch

For a long time Commons has it's own cvn-channel on Freenode: #cvn-commons <irc://irc.freenode.net/#cvn-commons>.
Although there are about a dozen idling users and a bot at any one time, use of the channel for vandal-fighting is not as frequent as desired.

Watching live is probably the easiest and most effective way to fight vandalism.
Also, for those who don't have the time to patrol an entire daypart-checklist, this is a great way to contribute when they only have a spare few minutes. One can leave and join at any time, and click/patrol for all edits that are reported in the channel.

In comparison to the checklists, the CVN-channel has a couple of advantages. JelteBot (the recent-changes bot in #cvn-commons) emphasises edits based on blacklists and watchlists, making it easier to detect potential vandalism. (If you monitor other channels too, you could add /Warning!/ to your IRC-stalklist.)

So I recommend the "patroller" right for anybody who wishes to participate, which you can ask for here: http://commons.wikimedia.org/wiki/Commons:Requests_for_rights. Please feel free to join #cvn-commons, or Commons' main channel #wikimedia-commons, for more information about other ways to get involved.
Every user in the counter-vandalism channel, watching and reacting to the stream, reduces the backlog even more.

Watching live means the user can be reverted and warned directly; s/he will either get blocked if they continue disruption, or (not unlikely) the vandal will stop when s/he reads the warning.

Doing this live, instead of afterwards, prevents more vandalism, and thus generate less edits in the backlog.

Checklists

Since it's unlikely (though the impossible goal of Live watch) to click and patrol each and every link in the IRC channel, lots of links are missed.
Either because no-one was on watch, or it got lost in the fast stream of links.

For that, we have the checklists. These contain all unpatrolled anonymous edits from a certain time frame.
These are, until we have a much bigger team, the primary and most time-consuming ways of fighting vandalism.

Also, when you can't access IRC, or don't like it for some reason, the RecentChanges-page is a good alternative:

If you don't know how this works, check the following links to get you up to speed:
- http://www.youtube.com/watch?v=eJXvZ65ttQ4 (short video tutorial on the CVU)

Then visit the CVU and check out a portion/day-part:


Thank you for reading,

Yours,
Krinkle


--
Greetings,
Krinkle
A Wikipedia Volunteer
- Wikipedia, the free encyclopedia

_______________________________________________ Commons-l mailing list Commons-l-RusutVdil2icGmH+5r0DMw@public.gmane.orgorg https://lists.wikimedia.org/mailman/listinfo/commons-l

_______________________________________________
Commons-l mailing list
Commons-l-RusutVdil2icGmH+5r0DMw@public.gmane.orgorg
https://lists.wikimedia.org/mailman/listinfo/commons-l

_______________________________________________ Commons-l mailing list Commons-l-RusutVdil2icGmH+5r0DMw@public.gmane.orgorg https://lists.wikimedia.org/mailman/listinfo/commons-l

_______________________________________________
Commons-l mailing list
Commons-l-RusutVdil2icGmH+5r0DMw@public.gmane.orgorg
https://lists.wikimedia.org/mailman/listinfo/commons-l

_______________________________________________ Commons-l mailing list Commons-l-RusutVdil2icGmH+5r0DM0B+6BGkLq7r@public.gmane.org https://lists.wikimedia.org/mailman/listinfo/commons-l 

_______________________________________________
Commons-l mailing list
Commons-l@...
https://lists.wikimedia.org/mailman/listinfo/commons-l
Permalink | Reply | 1 comment |
headers
Cary Bass | 8 Apr 2010 18:31
Picon

Re: Counter Vandalism Unit - Looking for helpers !

This is an excellent tool for patrolling new uploads:

<http://toolserver.org/~para/Commons:Special:NewFiles>

Cary

Eusebius wrote:
> Even without the patrolled edit thing, what we tried to launch would
> have been useful if people (admins) actually patrolling uploads had
> used it.
> Maybe it's a usability/interface issue of some kind, but it most
> certainly is a kind of "sub-community building" issue.
>
> "Patrolled uploads" would just be a nice bonus, maybe.
>
> Regards,
> Eusebius
>
> Krinkle a écrit :
>> Hi Eusebius,
>>
>> Ah, indeed. I was wondering why it listed so few new files (the link
>> I gave earlier). Uploads do indeed not get listed there. 
>> Special:NewFiles does but doesn't allow patrolling, I understand your
>> request now.
>>
>> That project definitely needs attention aswell.
>> I'll see if I can find a way to "patrollise" that.
>>
>> --
>> Greetings,
>> Krinkle
>>
>> Op 8 apr 2010, om 17:08 heeft Eusebius het volgende geschreven:
>>
>>> Hi,
>>>
>>> Thanks for your link.
>>>
>>> Apparently, this only shows the page creations without upload, like
>>> before a Flickr upload bot action. "Standard" uploads do not seem to
>>> show.
>>> Independently from this, even if a page could list all unpatrolled
>>> uploads, I think it wouldn't be suitable, because (for the patrolled
>>> edit be efficiently applied to recent uploads) a file upload should
>>> be marked as patrolled/unpatrolled independently of the edits on the
>>> file page. Indeed, recent edit patrollers will look for vandalism,
>>> and recent uploads patrollers will look for copyright violations,
>>> bad sources, missing permisions, etc. Depending on the experience
>>> and "patrolling profile" of both kinds of patrollers, patrols can
>>> have very different ("colliding") outcomes. This is why I suspect a
>>> different notion could be justified for patrolled uploads.
>>>
>>> Here's what we tried to begin about recent uploads, for info:
>>> http://commons.wikimedia.org/wiki/Commons:Recent_uploads_patrol
>>>
>>> Regards,
>>> Eusebius
>>>
>>> Krinkle a écrit :
>>>> Hi Eusebius,
>>>>
>>>> There is actually something that is 99% like what you are describing:
>>>>
>>>> http://commons.wikimedia.org/w/index.php?title=Special:NewPages&hidepatrolled=1&namespace=6
>>>> <http://commons.wikimedia.org/w/index.php?title=Special:NewPages&hidepatrolled=1&namespace=6>
>>>> reversed: http://commons.wikimedia.org/w/index.php?title=Special:NewPages&hidepatrolled=1&namespace=6&dir=prev
>>>> <http://commons.wikimedia.org/w/index.php?title=Special:NewPages&hidepatrolled=1&namespace=6&dir=prev>
>>>>
>>>> It's the NewPage-patrol, with the namespace filter set to "File",
>>>> which is pretty much always an upload.
>>>>
>>>> (though theoraticly there could be uploads without a page, and a
>>>> page without an upload)
>>>>
>>>> Please note that, like any patrollable action the action leaves the
>>>> unpatrolled queue automaticly after 720 hours (30 days).
>>>> if you like, I could create a checklist-system for this aswell.
>>>>
>>>> --
>>>> Greetings,
>>>> Krinkle
>>>>
>>>> Op 8 apr 2010, om 16:38 heeft Eusebius het volgende geschreven:
>>>>
>>>>> Hi,
>>>>>
>>>>> Thanks for this initiative. On my side I've significantly failed
>>>>> to build something for recent uploads patrolling.
>>>>> Is there something like a patrolled upload on MediaWiki? Because
>>>>> I've always found recent uploads more problematic than recent
>>>>> edits, and being able to tell between patrolled and unpatrolled
>>>>> uploads would be GREAT.
>>>>>
>>>>> Regards,
>>>>> Eusebius
>>>>>
>>>>> Krinkle a écrit :
>>>>>> Hi everybody.
>>>>>>
>>>>>> First of all, for those of you who haven't been here, or didn't
>>>>>> get the complete picture, here is a short summary of
>>>>>> some recent events:
>>>>>>  * Last March, I started the Counter Vandalism Unit on Commons
>>>>>> <http://commons.wikimedia.org/wiki/Commons:Counter_Vandalism_Unit>
>>>>>>  * Later that month, the edit-patrol function was enabled on
>>>>>> Commons
>>>>>> <http://commons.wikimedia.org/wiki/Commons:Village_pump/Archive/2010Mar#Marking_edits_as_patrolled>
>>>>>>  * After a Sitenotice, a few users have signed up to
>>>>>> be "patrollers"; and with a small team of 3 to 4 regular
>>>>>> patrollers, we keep a checklist of anonymous
>>>>>> edits. <http://commons.wikimedia.org/wiki/COM:ANO#Anonymous_edits>
>>>>>>
>>>>>>
>>>>>> *The Problem *
>>>>>>
>>>>>> Vandalism on Commons is a big problem, which generates a large
>>>>>> backlog. Commons is the primary media depository for most
>>>>>> media used throughout Wikimedia. Vandalism on Commons therefore
>>>>>> has a greater likelihood of affecting local projects.
>>>>>> And, this also brings along the source of vandalism: Vandals. 
>>>>>> Local vandals are only a click away from Commons. Some don't even
>>>>>> realise they are no longer on the local wiki.
>>>>>> Some, whether or not knowing they've been blocked on a local
>>>>>> project, continue vandalising on Commons.
>>>>>>
>>>>>> So, having that said, we are looking for help !
>>>>>> The most important areas, for now, are live watches on IRC or
>>>>>> recent changes, and the Checklists mentioned above.
>>>>>>
>>>>>> *Live watch*
>>>>>>
>>>>>> For a long time Commons has it's own
>>>>>> cvn-channel on Freenode: #cvn-commons
>>>>>> <irc://irc.freenode.net/#cvn-commons>.
>>>>>> Although there are about a dozen idling users and a bot at any
>>>>>> one time, use of the channel for vandal-fighting is not as
>>>>>> frequent as desired.
>>>>>>
>>>>>> Watching live is probably the easiest and most effective way to
>>>>>> fight vandalism.
>>>>>> Also, for those who don't have the time to patrol an entire
>>>>>> daypart-checklist, this is a great way to contribute when they
>>>>>> only have a spare few minutes. One can leave and join at any
>>>>>> time, and click/patrol for all edits that are reported in the
>>>>>> channel.
>>>>>>
>>>>>> In comparison to the checklists, the CVN-channel has a couple of
>>>>>> advantages. JelteBot (the recent-changes bot in #cvn-commons)
>>>>>> emphasises edits based on blacklists and watchlists, making it
>>>>>> easier to detect potential vandalism. (If you monitor other
>>>>>> channels too, you could add /Warning!/ to your IRC-stalklist.)
>>>>>>
>>>>>> So I recommend the "patroller" right for anybody who wishes to
>>>>>> participate, which you can ask for
>>>>>> here: http://commons.wikimedia.org/wiki/Commons:Requests_for_rights. Please
>>>>>> feel free to join #cvn-commons, or Commons' main channel
>>>>>> #wikimedia-commons, for more information about other ways to get
>>>>>> involved.
>>>>>> Every user in the counter-vandalism channel, watching and
>>>>>> reacting to the stream, reduces the backlog even more.
>>>>>>
>>>>>> Watching live means the user can be reverted and warned
>>>>>> directly; s/he will either get blocked if they continue
>>>>>> disruption, or (not unlikely) the vandal will stop when s/he
>>>>>> reads the warning.
>>>>>>
>>>>>> Doing this live, instead of afterwards, prevents more vandalism,
>>>>>> and thus generate less edits in the backlog.
>>>>>>
>>>>>> *Checklists*
>>>>>>
>>>>>> Since it's unlikely (though the impossible goal of Live watch) to
>>>>>> click and patrol each and every link in the IRC channel, lots of
>>>>>> links are missed.
>>>>>> Either because no-one was on watch, or it got lost in
>>>>>> the fast stream of links.
>>>>>>
>>>>>> For that, we have the checklists. These contain all unpatrolled
>>>>>> anonymous edits from a certain time frame.
>>>>>> These are, until we have a much bigger team, the primary and most
>>>>>> time-consuming ways of fighting vandalism.
>>>>>>
>>>>>> Also, when you can't access IRC, or don't like it for some
>>>>>> reason, the RecentChanges-page is a good alternative:
>>>>>> - <http://commons.wikimedia.org/w/index.php?title=Special:RecentChanges&hidepatrolled=1&days=1&limit=50&hideliu=1&hidemyself=1
>>>>>> <http://commons.wikimedia.org/w/index.php?title=Special:RecentChanges&hidepatrolled=1&days=1&limit=50&hideliu=1&hidemyself=1>>
>>>>>>
>>>>>> If you don't know how this works, check the following links to
>>>>>> get you up to speed:
>>>>>> - http://commons.wikimedia.org/wiki/Commons:Patrol
>>>>>> - http://commons.wikimedia.org/wiki/Commons:Counter_Vandalism_Unit (last
>>>>>> few headings on File and Tools)
>>>>>> - http://www.youtube.com/watch?v=eJXvZ65ttQ4 (short video
>>>>>> tutorial on the CVU)
>>>>>>
>>>>>> Then visit the CVU and check out a portion/day-part:
>>>>>> http://commons.wikimedia.org/wiki/COM:ANO#Anonymous_edits
>>>>>>
>>>>>>
>>>>>> Thank you for reading,
>>>>>>
>>>>>> Yours,
>>>>>> Krinkle
>>>>>>
>>>>>>
>>>>>> --
>>>>>> Greetings,
>>>>>> Krinkle
>>>>>> A Wikipedia Volunteer
>>>>>> krinkle@... <mailto:krinkle@...>
>>>>>> - Wikipedia, the free encyclopedia

--

-- 
Cary Bass
Volunteer Coordinator, Wikimedia Foundation

Support Free Knowledge: http://wikimediafoundation.org/wiki/Donate
Permalink | Reply | 0 comments |
headers
Platonides | 8 Apr 2010 18:56
Picon

Re: Counter Vandalism Unit - Looking for helpers !

Krinkle wrote:
> Ah, indeed. I was wondering why it listed so few new files (the link I
> gave earlier). Uploads do indeed not get listed there. 
> Special:NewFiles does but doesn't allow patrolling, I understand your
> request now.
> 
> That project definitely needs attention aswell.
> I'll see if I can find a way to "patrollise" that.
> 
> --
> Greetings,
> Krinkle

Note that file uploads are reported on irc at #commons-image-uploads
with whitelist/blacklist + some image consistency checks.

Would be even nicer if gmaxwell fixed it so it reports deleted reuploads
again, though.
Permalink | Reply | 2 comments |
headers
Krinkle | 8 Apr 2010 18:59
Picon
Gravatar

Re: Counter Vandalism Unit - Looking for helpers !

#cvn-commons reports file-uploads aswell, but only of new users,  
blacklisted users or watched filenames.
Would be nicer if the blacklists were shared between the two.

--
Greetings,
Krinkle

Op 8 apr 2010, om 18:56 heeft Platonides het volgende geschreven:

> Krinkle wrote:
>> Ah, indeed. I was wondering why it listed so few new files (the  
>> link I
>> gave earlier). Uploads do indeed not get listed there.
>> Special:NewFiles does but doesn't allow patrolling, I understand your
>> request now.
>>
>> That project definitely needs attention aswell.
>> I'll see if I can find a way to "patrollise" that.
>>
>> --
>> Greetings,
>> Krinkle
>
> Note that file uploads are reported on irc at #commons-image-uploads
> with whitelist/blacklist + some image consistency checks.
>
> Would be even nicer if gmaxwell fixed it so it reports deleted  
> reuploads
> again, though.
>
>
> _______________________________________________
> Commons-l mailing list
> Commons-l@...
> https://lists.wikimedia.org/mailman/listinfo/commons-l
Permalink | Reply | 0 comments |

Gmane