-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
Anon Sricharoenchai wrote:
However, could you please answer the following questions?
- Is there a plan to prohibit local account creation of existing
ununified username?
Not presently as such, however at some point automatic migration of all remaining accounts may be initiated.
Prohibiting local account creation of existing ununified usernames would be essentially equivalent, as it would require people wanting to create such accounts to (manually) initiate a migration before continuing with the additional account setup.
- While the selection is still depend on edit count, but why you not
collect the edit count of the subset sharing email or password, as stated in http://meta.wikimedia.org/wiki/Single_login_specifications ? (``GROUP 2: If an account name exists in multiple subsets, the subset with the highest edit count "wins".'') While the edit count still be used for activeness measurement, I'm please to write a patch for counting the subset's edit count, to make the selection be more reasonable.
It's not possible to group multiple wikis by password until all passwords have been manually entered, but we need to make a selection ahead of time in order to determine if the presently logged-in account matches the home account. So it's perhaps a bit of a catch-22 there. :)
I suspect it's fairly unlikely that the results would change significantly based on making such a change, though of course there may be some outlying cases.
- Why haven't you told me why sysop should take precedence in getting
global account?
To avoid disruption, impersonation, etc, privileged accounts are given priority.
- -- brion