Jump to content

Community Wishlist Survey 2021/Admins and patrollers/CentralAuth lock should trigger global autoblocks

From Meta, a Wikimedia project coordination wiki

CentralAuth lock should trigger global autoblocks

  • Problem: When stewards are locking vandal accounts, their IP address is not globally blocked, meaning they can continue vandalizing using their IP. Now stewards need to go to loginwiki to check an IP and block it. It would save a lot of time if we don't need to do the check afterwards.
  • Who would benefit: Stewards
  • Proposed solution: Automatically block an IP of a locked account
  • More comments:
  • Phabricator tickets: T19929
  • Proposer: Stryn (talk) 11:07, 17 November 2020 (UTC)[reply]


  • Good idea. This proposal is something I will like to raise also. Camouflaged Mirage (talk) 11:08, 17 November 2020 (UTC)[reply]
  • I would want to see the ability to enable autoblocks when locking. Dreamy Jazz talk to me | enwiki 23:54, 19 November 2020 (UTC)[reply]
  • Your idea is good to save 80% of Stewards work on this, but I didn't fully agree to implement "automatically block an IP of a locked account", instead of this we could have an check box "Block the IP globally" during global (un)lock, if any of those account need to be unlocked then remove from check box. Why did I propose this? Some of Wikimedian work for WMF for a contract period, when their contract ended their user ID also locked as "no longer with WMF". If automatically block an IP of a locked account, those good users will have to find excepcional way for their volunteer account. Regards, ZI Jony (Talk) 17:13, 21 November 2020 (UTC)[reply]
  • This is a good idea provided that, similarly to local blocks, there is an option to disable autoblocks. This shouldn't hamper the overall request though. Best, KevinL (aka L235 · t) 06:41, 1 December 2020 (UTC)[reply]
  • Caution needed: a single IP address is often used by multiple people. An obvious example is when a device is used by multiple people in the same family, university, business etc. Another example is when multiple machines in the same institution (or with the same ISP) use the same gateway. I understand the reasons for wanting autoblocking, but in the past I have seen entire networks of affiliated schools using the same gateway being blocked from editing as a result of an unknown user (probably some unknown student/ex-student from an affiliated school) getting the school's/schools' IP address blocked (possibly years ago), causing havoc for teachers. I believe this problem still continues to happen (and needs to be fixed). Autoblocking, without some form of safeguard to prevent this, will compound the problem. Can anybody comment on safeguards?--Fh1 (talk) 22:38, 15 December 2020 (UTC)[reply]