When an oversighter HideUser-blocks a user accidentially, it's impossible to restore the visibility of the log entry regarding the block action now as it's in the suppress log page. To make it public, one have to unblock and reblock the user. It may be possible to create a suppressed block log entry on block too, and it can be unhidden when needed.
Version: 1.21.x
Severity: normal
| Status | Subtype | Assigned | Task | ||
|---|---|---|---|---|---|
| Stalled | None | T47064 Create block log entries on HideUser blocks | |||
| Declined | None | T150422 Special:CentralAuth should report user account existense even if hidden |
Change 49234 had a related patch set uploaded by Siebrand:
(bug 45064) Create block log entries on HideUser blocks too
@liangent: Still working on this (as you are set as assignee), or should this be unassigned?
Adding a suppressed entry in the public block log looks kinda useless to me... The whole point of hideuser is to remove an user from public view without leaving a trace. I fail to see the usefulness of this, specially when the block form now sends to a warning when you're about to block an user with hideuser. Suggest decline.
Stuff being unable to be unhidden sounds like a legitimate bug to me. Decline request declined?
I don't think he refers to that. If I block an account with hideuser, no public block log entry is created -obviously-. What if later I notice that I applied hideuser in error? The solution is simple: change the block settings or unblock and reblock. This is the same as in T31216. Creating entries in the logs no one can see looks useless for me. Best regards.
Unfortunately as per above, even if possible it won't be easy, and still lack supports from SWAT
@liangent: Hi, I'm resetting the task assignee due to inactivity. Please feel free to reclaim this task if you plan to work on this - it would be welcome! Also see https://www.mediawiki.org/wiki/Bug_management/Assignee_cleanup for more information - thanks!