Problem: (1) Given a category of user or user talk pages, determine which have or have not been globally locked. (2) Given a page (e.g. a sockpuppet investigation page), somehow highlight accounts that have been globally locked.
Proposed solution: It is not possible to determine efficiently whether a list of accounts has been locked. It is now one API request per user, instead of the 1 request for 50 or even 500 users. Solve the API problem and gadget writers can do the rest.
Who would benefit: Stewards, those dealing with cross-wiki sockpuppets and spam, admins who deal with block appeals, etc. Also a small reduction in the amount of cross-wiki abuse.
Personally, I think we should have a blocklist and a lock list of all globally blocked IPs and locked users. The list can't be found in any special pages. And I think we need to have the ability to lock users with an expiration (so a lot of proposals about global blocking for accounts). Thingofme (talk) 08:44, 14 January 2022 (UTC)[reply]
What about list of global locks? The list only represent logs, not represent like the list of local blocks, and so it's not having a table-styled list. Thingofme (talk) 09:43, 15 January 2022 (UTC)[reply]
There is a phabricator proposals about only global blocking the accounts, and that mean users can log into the account and receive an error of not able to edit in Wikimedia wikis. Can't log in is too much. We want to prevent editing, not logging in. Thingofme (talk) 15:35, 15 January 2022 (UTC)[reply]
@Thingofme: we who? Locking exists explicitly to prevent logging on. If you want to talk about creating "global blocks" for accounts - please open another item, and reference phab:T17294. — xaosfluxTalk01:04, 17 January 2022 (UTC)[reply]
Support - STSC (talk) 04:55, 29 January 2022 (UTC)