Page MenuHomePhabricator

Restrict page moves to autoconfirmed users on all WMF wikis
Closed, ResolvedPublic

Description

Author: spacebirdy

Description:
Hello all,
please change the permission to move pages,
it should not be allowed for new users, just like editing semiprotecting pages.
The reason is, there is too much move-vandalism besides new users should first get the hang of a project before moving something.

Many thanks in advance,
Elisabeth Anderl [[:wikt:is:Notandi:Spacebirdy]]


Version: unspecified
Severity: enhancement
URL: all wikimedia projects

Details

Reference
bz12071

Event Timeline

bzimport raised the priority of this task from to Medium.Nov 21 2014, 9:59 PM
bzimport set Reference to bz12071.
bzimport added a subscriber: Unknown Object (MLST).

koneko wrote:

I warmly +1 that. (see also the latest comments at [[bugzilla:1454]])

le.korrigan wrote:

I just tested : as a new user, I cannot rename a page on fr.wikipedia, and neither on en.wikipedia (I don't have the "move" button, and if I try with the URL I get a "permission error"). So this bug is "WORKSFORME".

But maybe you want to ask for something else in order to limit page-move vandalism... this would be for a new bug.

le.korrigan wrote:

Woops sorry, I just tried on is.wiktionary (your home project), and there it seems that I can rename pages... so I reopen the bug. Sorry for closing it too quickly.

spacebirdy wrote:

it is not only like this on is.wiktionary but on most projects (maybe on the big ones it is already turned off)

osoyoos wrote:

Ho! It's not the case already? Renaming a page cannot be reverted by a regular user, it needs to be requested to sysop... and probably they're tired to treat those useless requests! Thanks for considering! Antaya

spacebirdy wrote:

(In reply to comment #6)

Ho! It's not the case already? Renaming a page cannot be reverted by a regular
user, it needs to be requested to sysop... and probably they're tired to treat
those useless requests! Thanks for considering! Antaya

Sorry, it is not about reverting a renamed page, it is about disallowing a _new_ registered user to move a page in the first place,
best regards

jeluf wrote:

This change needs community approval. Since this would be WMF-wide, I think meta would be the place where this discussion should take place. Please find consensus there and come back when this has been discussed.

le.korrigan wrote:

I disagree with this : when such a change was done on en.wikipedia and fr.wikipedia, I don't remember any sort of "community decision", I believe it was more a simple call to the developers like "hey, we've got page-move vandalism, can you do something about it ?". And you did, and this was fine for everybody, at least on fr.wikipedia ("that's the wya the software is").

You can look at it the other way around : this feature could be the default behaviour, and communities which want to change it could do so after a common agreement. Now, we're talking about problems the inter-wiki patrolling team has, which is about he hundreds of small wikis without much of a community. It would make much more sense to apply this feature by default.

If you can't do it for all wikis, maybe you could do it for all wikis patrolled by the SWMT (see http://meta.wikimedia.org/wiki/SWMT).

spacebirdy wrote:

Hello, I must also disagree, voting on Meta only would reflect a global community decision if it were announced globally.

Changing the move to autoconfirmed would not harm the communities because it would only prohibit _new_ users to move pages, the existing users are not affected.

Regarding the links I provided this is also happening on wikis with no communities, so there would probably only be support of the swmt from which some already expressed their support and interest here.

If You need more links to reflect the global problem I will provide them, but I can't do that before the end of this week because I am very busy.

Thank You for Your attention.

spacebirdy wrote:

(In reply to comment #8)

This change needs community approval. Since this would be WMF-wide, I think
meta would be the place where this discussion should take place. Please find
consensus there and come back when this has been discussed.

JeLuF, I thought about it this night and came to the following logic:

*IPs are not allowed to move pages
*IPs are not allowed to edit semiprotected pages

*new Users are allowed to move pages
*new Users are not allowed to edit semiprotected pages

The sense of disallowing IPs page moves is not intelligible for me if they could just easily create an account and then move pages.
Imho, it would be equally incomprehensible to allow new users to edit semiprotected pages.

Please reconsider Your decision, thanks.

mduce wrote:

The poll at the Metapub has been running for almost a month now. In my opinion, there seems to be consensus to enable but let certain projects opt out.

Mitch

spacebirdy wrote:

Thanks for reopening.

Please see http://meta.wikimedia.org/wiki/Metapub#set_pagemoves_to_autoconfirmed_-_please_read_and_comment
for the votes, this discussion link was sent to all project mailinglists and published on wikizine to reach as many communities as possible.

Please leave out

  • en.wikinews

according to http://meta.wikimedia.org/wiki/Metapub#Opt_out_list

Thanks.

adam.brookes wrote:

Could a developer confirm whether or not this has been set for enwikinews. If this hasn't on the basis of http://meta.wikimedia.org/wiki/Metapub#Opt_out_list then I'd dispute the decision. A single user listed enwikinews as wanting an opt-out but as I've noted there this does not reflect the feelings of the community when this has been discussed. There isn't really consensus either way so I'd suggest that we stick to the new default and have no opt-out unless consensus emerges in favour of this.

I can confirm there is no such exception for enwikinews.

spacebirdy wrote:

How is this possible:
http://km.wikipedia.org/w/index.php?title=Special:Log&user=Yamamoto_Shinsu

Registered today, page moves today. Please set km.wiki to autoconfirmed too, thanks.

spacebirdy wrote:

hm, the account seems to have been created before, sorry.