Make protection customizable

Jump to: navigation, search

I think if the page protection scheme is going to be redone, it should allow for customizable protection levels. The current none/autoconfirmed/sysop configuration is highly inflexible and often results in people being forced to choose the lesser of the evils.

It should be possible to specify that a certain page can't be edited or moved or created by people whose accounts are newer than X or who have fewer than Y edits. I'm not sure if this belongs in a separate proposal or should be incorporated into this one, I just think it's desperately needed and that any rewrite of the protection logic should include it.

MZMcBride01:03, 5 August 2011

It is just about possible to implement this logic, but I agree that it's horribly painful to do so. On the other hand, I think direct fine-grained logic like this is probably best implemented in the AbuseFilter; I'd say that protection should continue to be based on user groups.

Happymelon16:09, 5 August 2011
 
Personal tools
Namespaces

Variants
Actions
Navigation
Support
Download
Development
Communication
Toolbox