quentinv57 wrote:

Closing the bug, as now stewards have the choice between simply hiding a user from public lists and oversighting it completely. Hope that's what you meant.

quentinv57 wrote:

Reopened.

Apparently I'm wrong on Comment #1.

Now the account can be :

• viewable from everybody
• hidden from public lists (don't know what that clearly implies)
• completely oversighted

What I think Mike meant was to add some new possibility here to hide the users at an admin-only level, which is not the [hide from public lists]. Hope I'm true.

In T20723#225984, quentinv57 wrote:

• hidden from public lists (don't know what that clearly implies)

It means that the account can no longer be viewed at Special:GlobalUsers. It differs on global account suppression that global account hidding logs the action in the suppress log and hids the user on the Special:GlobalUsers page, but does nothing more (if it's also locked, the account won't be able to login as you know). Suppression will do the above plus going wiki and will locally block the account with hideuser flag enabled, making the user virtually "dissapear" from logs and histories.

What I think Mike meant was to add some new possibility here to hide the users at an admin-only level, which is not the [hide from public lists]. Hope I'm true.

Yes, I think that's also what he meant. This bug proposes that when we lock + hid an account, CentralAuth should also set local blocks only visible to administrators (that is, revision-deleted local entries).

However I'm not sure of its current usefulness. Deletion and blocking policies are a matter of local wikis, and unless the user is abusive block logs should not be hidden. If the account name is abusive enough to fall under criterion #4 of the OS policy, then we or local oversighters will suppress the account entirely for everyone.

Suggest declining.