Page MenuHomePhabricator

Warn and confirm for self global locks
Open, Needs TriagePublic

Description

As it happens with Special:Block, and in order to avoid accidents, please have CentralAuth warn users that are about to globally lock themselves and have the user explicitly confirm they intend indeed to perform a self-global lock. Thank you.

Event Timeline

I wonder if we can just get rid of the global locking interfaces when T17294: Allow globally blocking of accounts is done, instead of duplicating all the behaviors of the blocking interfaces?

Global locks also prevent users from logging in. Until we solved T222281: Add a way to prevent user from log in and disable a users session when blocking and also have a similar option in GlobalBlocking, global blocks and locks should co-exist; compromised accounts should still be locked (and globally banned users may, though not must, be locked instead of blocked). Edit: to enforce global bans, what is more important is blocks/locks of banned users should not be able to be locally disabled, even if we can disable global blocks locally.