Helloes!
Don't understand why this was reverted without any explanation and consensus finding...
See, it was an experiment "what will happen if I revert Domas". If people lack understanding of code flow, reverting someone who does without going into explanation and consensus finding is bad too ;-)
isn't Usercan an official hook of mediawiki ?
So is configuration option, telling that wiki is read-for-all :) 0
Doing this is simply bypass this documented hook !?
For completely-read-all wikis, yes.
Don't know how duesentrieb can rewrite extension since the hook is bypassed
Probably by allowing userCan to provide with access, in case default access is false. See, whitelisting pages doesn't work too if access is allowed to everyone by default.
Perhaps i have missing something...
Yup, you're missing the fact, that someone is making mediawiki not suck performance wise. For example Tim made delayed optimization of objects, but that gets broken by very start of code tree. The idea, that even with bytecode cache installed, one can set multiple tweaks to make mediawiki much faster than default deployment, is already quite bad. It should be fastest out of the box already, cause not everyone goes googling around for 'making mediawiki faster' (and landing in http://dammit.lt/2007/01/26/ mediawiki-performance-tuning/ ;-)
BR,