Thread:Talk:Requests for comment/Page protection as a component/Granularization/Misconceptions?

This seems to have a lack of understanding or is mis-stating what our protection system already supports.

Autoconfirmed protection is not limited to "the user has been around for 4 days". Autoconfirmed can be configured to be based on any length of time and/or how many edits a user has (wgAutoConfirmAge, wgAutoConfirmCount). Additionally autoconfirmed is not the only group you can do this for. You can configure as many autopromoting user groups you want ('newbie' => 1 day & 10 edit; 'trusted' => 7 days & 200 edits; 'regular' => 4 weeks & 1000 edits). See. And I don't know if we have a hook there. But if we don't I would be completely open to having some sort of "AutoPromote" hook that allows extensions to autopromote users to groups based on really special conditions.

Additionally you are not limited to two levels (sysop, and autoconfirmed). It is very rarely used. In fact so rarely used I almost thing it's broken and might need some fixing (or maybe that's just cause I always also tried using ). But using it's already possible to add a set of (potentially autopromoted) groups to the protection list. So the protection list can be based of something like that newbie, trusted, regular list I just mentioned as an example.

I'm not opposed to the idea of also supporting a better ACL system. But such a thing can already be done using hooks. Or by building a brand new ACL system in core. Then implementing a copy of the old behaviour using a subset of your ACL system's API. Then offering a configuration switch, say $wgUseACLs which switches the wiki's interface between using the traditional simple protection system and showing a full-blown ACL system.