Left open by #24.
The special pages, API modules and username completion that name accounts are closed to members, and to nobody else. On a wiki that leaves reading public, which the README allows, an anonymous visitor therefore gets Special:ListUsers, list=allusers and username completion: the roster. On a wiki that restricts reading, anonymous visitors reach none of this, and the first two answers below are the same. Histories name only staff, since members cannot edit; these surfaces and the logs are the whole roster path.
Three answers, with what each costs:
- Members (today): anonymous visitors on a public-read wiki read the roster.
- Members and anonymous visitors: anonymous visitors lose account listings and username completion.
- Everyone who cannot manage members: every logged-in account without
memberaccess-manage loses user lists, username completion, and the list=allusers behind user fields and mention autocompletion — accounts the extension otherwise treats as staff, such as the ones single sign-on creates while it is not held to the allowlist.
The logs already use the third gate, but only because $wgLogRestrictions takes a right, not as a choice about the audience. Tightening later takes a working feature from live editors; loosening later takes nothing. A setting would hand the same question to every administrator.
Recommendation: the second. The extension knows two kinds of account, members and staff, and the public is neither. Whichever it is, it is one predicate in three handlers and a README sentence.
AI-authored — Claude Code, Fable 5 (max); split out of issue 24 while delegating its fix for @JeroenDeDauw, no steering on this text; not yet human-reviewed; the costs listed were checked against MediaWiki 1.43 source (which modules user fields and mentions call, what the log gate is) and one blind review pass applied.
Left open by #24.
The special pages, API modules and username completion that name accounts are closed to members, and to nobody else. On a wiki that leaves reading public, which the README allows, an anonymous visitor therefore gets
Special:ListUsers,list=allusersand username completion: the roster. On a wiki that restricts reading, anonymous visitors reach none of this, and the first two answers below are the same. Histories name only staff, since members cannot edit; these surfaces and the logs are the whole roster path.Three answers, with what each costs:
memberaccess-manageloses user lists, username completion, and thelist=allusersbehind user fields and mention autocompletion — accounts the extension otherwise treats as staff, such as the ones single sign-on creates while it is not held to the allowlist.The logs already use the third gate, but only because
$wgLogRestrictionstakes a right, not as a choice about the audience. Tightening later takes a working feature from live editors; loosening later takes nothing. A setting would hand the same question to every administrator.Recommendation: the second. The extension knows two kinds of account, members and staff, and the public is neither. Whichever it is, it is one predicate in three handlers and a README sentence.