2017 Community Wishlist Survey/Admins and stewards/Allow further user block options ("can edit XY" etc.)

From Meta, a Wikimedia project coordination wiki
Jump to: navigation, search

⬅ Back to Admins and stewards The survey has concluded. Here are the results!


  • Problem: Admins can only block users from editing any page at all (the one exception being that user's talk page). If a blocked user is given the right to edit on a specific page or specific pages, the block still has to be lifted completely. This could be confusing, as the community has still decided to block them from other pages.
  • Who would benefit: Administrators and blocked users.
  • Proposed solution: Create options for users to edit pages to appeal the block, edit or not edit certain pages or namespaces, or do certain actions such as registering an account, use email or upload files.
  • More comments:
  • Proposer: → «« Man77 »» [de] 19:36, 14 November 2017 (UTC)

Discussion

  • good idea. maybe add a possibility to block only specific namespace. For example block the main namespace but not draft namespace. - yona B. (D) 13:26, 15 November 2017 (UTC)
    • added → «« Man77 »» [de] 18:28, 15 November 2017 (UTC)
  • For some of my research into blocking tools, I've found several other requests for similar functionality to add extra levels of granularity into blocking tools. Here's a list of what I've found so far. I think this would be a very beneficial feature to explore/build. We'll need to decide how all of this is logged and stored appropriately. — Trevor Bolliger, WMF Product Manager 🗨 18:56, 15 November 2017 (UTC)
  • We Steward often have problems with abusive uploads by accounts in specific ranges, for example filesharing on Wikimedia Commons through Wikipedia Zero. If we could disallow uploads for IPs or IP ranges, that would help a lot.
  • Further, we have trolls which only create abusive user names but rarely edit. At the moment, we can only full-block ranges when it would be more useful to only disallow account creations while users could still edit. Can you add that to this proposal, should I ask at #Specialised blocks, or should I create another proposal, Man77? —DerHexer (Talk) 13:12, 18 November 2017 (UTC)
    • DerHexer: Please feel free to add further options to the list above, if you think it fits in here. For my part, I think that IP range block options could also be dealt with separately. However, the better strategy could also be not to atomize the proposals in order to get all the votes her ;) → «« Man77 »» [de] 14:00, 18 November 2017 (UTC)
      • I tried to make the change as little as possible. Are you okay with that? Best, —DerHexer (Talk) 11:34, 19 November 2017 (UTC)
  • The Community Tech team would like to merge this and 2017 Community Wishlist Survey/Admins and stewards/Specialised blocks. Are you fine with us doing that? /Johan (WMF) (talk) 17:47, 20 November 2017 (UTC)
  • Endorse I really don't want Wikimedia Commons to miss good quality images because a user misbehaves outside of uploading such as here. And for Wikipedia's this would be largely beneficial for the encyclopedia as most of the time content creators get banned not for bad edits in the mainspace but for insults and hot-headed debates in talk pages. --Donald Trung (Talk 🤳🏻) 09:20, 24 November 2017 (UTC)
  • Also with this idea 💡 topic bans and interaction bans can finally be enforced. --Donald Trung (Talk 🤳🏻) 09:21, 24 November 2017 (UTC)
  • I think that you can do this all using the abuse filter (called as edit filter somewhere), though it's not so easy for non technical users. Stryn (talk) 19:02, 27 November 2017 (UTC)
  • Can the reverse of this happen? For example, X is blocked due to BLP issues, but their edits on dinosaurs are sound. So in other words, can X be blocked from editing all articles in Category:Living people, but edit other articles? Lugnuts (talk) 18:44, 4 December 2017 (UTC)
  • Hello all — This item did not make the Top 10 for the 2017 Wishlist, but the Wikimedia Foundation's Anti-Harassment Tools team is already looking into building better blocking tools in early 2018. Support for this proposal and the comments are already being taken into account. Read more and participate in the discussion at Community health initiative/Blocking tools and improvements. Thank you, and I hope to see you there! — Trevor Bolliger, WMF Product Manager 🗨 23:07, 14 December 2017 (UTC)

Voting

  • Support Support Reception123 (talk) 20:01, 27 November 2017 (UTC)
  • Support Support Goldzahn (talk) 23:02, 27 November 2017 (UTC)
  • Support Support Matiia (talk) 00:37, 28 November 2017 (UTC)
  • Support Support - yona B. (D) 05:47, 28 November 2017 (UTC)
  • Support Supportviciarg414 08:11, 28 November 2017 (UTC)
  • Support Support --Donald Trung (Talk 🤳🏻) (My global lock 🔒) (My global unlock 🔓) 08:13, 28 November 2017 (UTC)
  • Support Support β16 - (talk) 10:09, 28 November 2017 (UTC)
  • Support Support Jo-Jo Eumerus (talk, contributions) 10:28, 28 November 2017 (UTC)
  • Support Support --Liuxinyu970226 (talk) 12:37, 28 November 2017 (UTC)
  • Support Support Jianhui67 talkcontribs 14:09, 28 November 2017 (UTC)
  • Support Support Jc86035 (talk) 14:43, 28 November 2017 (UTC)
  • Support Support Sakretsu (talk) 17:03, 28 November 2017 (UTC)
  • Support Support Yiyi (talk) 18:50, 28 November 2017 (UTC)
  • Support Support Gripweed (talk) 21:26, 28 November 2017 (UTC)
  • Support Support Thomas Obermair 4 (talk) 21:34, 28 November 2017 (UTC)
  • Support Support MichaelSchoenitzer (talk) 00:15, 29 November 2017 (UTC)
  • Support Support Drm310 (talk) 19:08, 29 November 2017 (UTC)
  • Support Support Niklem (talk) 19:11, 29 November 2017 (UTC)
  • Support Support --Christian Ferrer (talk) 19:18, 29 November 2017 (UTC)
  • Support Support Or even namespace blocks. --Ruthven (talk) 19:34, 29 November 2017 (UTC)
  • Support Support EVinente (talk) 19:43, 29 November 2017 (UTC)
  • Support Support Aunva6 (talk) 20:10, 29 November 2017 (UTC)
  • Support Support Pallanz (talk) 20:13, 29 November 2017 (UTC)
  • Support Support Patar knightchat/contributions 20:42, 29 November 2017 (UTC)
  • Nominal support, but Community Tech should not be working on this. Their resources are better spent elsewhere while the Anti-Harassment team tackles this. MER-C (talk) 20:52, 29 November 2017 (UTC)
  • Support SupportMeiræ 21:55, 29 November 2017 (UTC)
  • Support Support MGChecker (talk) 22:02, 29 November 2017 (UTC)
  • Support Support (a first step towards a namespace block, useful for when you'd need to force a user to temporarily work only in ns0) --g (talk) 23:48, 29 November 2017 (UTC)
  • Support Support This would also help in handling users who showed selective problematicity on some arguments/articles while being good contributors elsewhere.--L736Etell me 07:34, 30 November 2017 (UTC)
  • Support Support Winston (talk) 08:38, 30 November 2017 (UTC)
  • Support Support Winston Spencer (talk) 13:11, 30 November 2017 (UTC)
  • Support Support Strongly needed. —DerHexer (Talk) 16:08, 30 November 2017 (UTC)
  • Support Support Laurel Lodged (talk) 19:38, 30 November 2017 (UTC)
  • Support Support Tropicalkitty (talk) 20:07, 30 November 2017 (UTC)
  • Support Support Dromedar61 (talk) 20:25, 30 November 2017 (UTC)
  • Support Support Daniel Case (talk) 00:32, 1 December 2017 (UTC)
  • Support Support DonBarredora (talk) 01:24, 1 December 2017 (UTC)
  • Support Support Good idea. AndyAndyAndyAlbert (talk) 07:59, 1 December 2017 (UTC)
  • Support Support HaythamAbulela 18:16, 1 December 2017 (UTC)
  • Support Support ديفيد عادل وهبة خليل 2 (talk) 20:54, 1 December 2017 (UTC)
  • Support Support but perhaps not with Community Tech per MER-C. J947 03:33, 2 December 2017 (UTC)
  • Support Support Operator873 (talk) 05:35, 2 December 2017 (UTC)
  • Support Support Wostr (talk) 10:10, 2 December 2017 (UTC)
  • Support Support --Bubo 11:43, 2 December 2017 (UTC)
  • Support Support ~Cybularny Speak? 11:57, 2 December 2017 (UTC)
  • Support Support Szoltys (talk) 12:02, 2 December 2017 (UTC)
  • Support Support Ented (talk) 12:24, 2 December 2017 (UTC)
  • Support Support«« Man77 »» [de] 13:52, 2 December 2017 (UTC)
  • Support Support Emir of Wikipedia (talk) 15:40, 2 December 2017 (UTC)
  • Support Support Tacsipacsi (talk) 16:57, 2 December 2017 (UTC)
  • Support Support TheCatalyst31 (talk) 16:58, 2 December 2017 (UTC)
  • Support Support Otapka (talk) 18:43, 2 December 2017 (UTC)
  • Support Support Kostas20142 (talk) 21:17, 2 December 2017 (UTC)
  • Support Support Wiklol (talk) 21:24, 2 December 2017 (UTC)
  • Support Support yes please, more granularity! Chris Keating (The Land) (talk) 21:33, 2 December 2017 (UTC)
  • Support Support Sometimes a full block would be too heavy-handed. NinjaRobotPirate (talk) 07:24, 3 December 2017 (UTC)
  • Support Support Mz7 (talk) 10:22, 3 December 2017 (UTC)
  • Support Support -- seth (talk) 10:37, 3 December 2017 (UTC)
  • Support Support -- Dolotta (talk) 13:59, 3 December 2017 (UTC)
  • Support Support Winged Blades of Godric (talk) 16:22, 3 December 2017 (UTC)
  • Support Support rxy (talk) 22:17, 3 December 2017 (UTC)
  • BA candidate.svg Weak oppose unnecessary complication, I think that edit-protected pages and template editors at english wikipedia are already a complication, and adding fine-grained blocks is another even greater complication, instead we need better review system so that new edits and newcomers receive attention at the time they make their first edit. Add more volunteers who help with this process. English Wikipedia has not enough helpers and assisting persons and resolving this by fine graining the blocks sounds like an overkill in my personal opinion. --Gryllida 00:31, 4 December 2017 (UTC)
  • Support Support Ciao • Bestoernesto 02:27, 4 December 2017 (UTC)
  • Support Support: This would vastly improve our ability to deal with disruption but often-good editors we want to retain. It should be possible to a) block editors with a PoV problem from articles by name or by category; and b) unblock blocked editors for particular pages by name or category (including, e.g., ArbCom, ANI, and other dispute resolution pages, as well as selective content pages).  — SMcCandlish ¢ ≽ʌⱷ҅ʌ≼  07:03, 4 December 2017 (UTC)
  • Support Support Jpcomic (talk) 10:22, 4 December 2017 (UTC)
  • Support Support - Great idea!, I've seen it more than once on EN where an editor is blocked but they've been given the opportunity to comment for instance at Arbcom or ANI and have been told under no certain terms if they edit any other page they'll be blocked (rightly so) so having this would give those blocked the oppertunity to defend themselves or have their say - Ofcourse if they abuse it it'll be revoked. –Davey2010Talk 15:15, 4 December 2017 (UTC)
  • Support Support Ronhjones (talk) 18:10, 4 December 2017 (UTC)
  • Support Support Yeza (talk) 23:03, 4 December 2017 (UTC)
  • Support Support as much as I believe editors should be mature enough to not require the community to babysit them, the reality is that some editors get indeffed because they cannot control a small aspect of their onwiki behaviour, while the rest of their activity is an asset. enL3X1 ¡‹delayed reaction›¡ 03:39, 6 December 2017 (UTC)
  • Support Support I do agree that certain users might be able to contribute on certain points, if not all Yohannvt (talk) 11:53, 6 December 2017 (UTC)
  • Support Support Ixocactus (talk) 01:37, 7 December 2017 (UTC)
  • Support Support Chealer (talk) 03:51, 7 December 2017 (UTC)
  • Support Support Ealdgyth (talk) 13:35, 7 December 2017 (UTC)
  • Support Support X:: black ::X (talk) 14:38, 7 December 2017 (UTC)
  • Support Support Ahm masum (talk) 21:17, 7 December 2017 (UTC)
  • Support Support --jdx Re: 18:45, 8 December 2017 (UTC)
  • Support Support. Basically we need anything between a full lock and a full editing. There are many possible options, including block from editing a namespace (e.g. user cannot edit templates), from editing a group of pages (e.g. user cannot edit articles about living politicians), from editing a specific page (e.g. user cannot edit a page where they were engaged in an edit war) or vice versa (e.g. user can edit only a specific page, which already happened in a real life case where a user violated rules but had to prepare a page of an offline event at the same time). Having at least some of these options would be a huge plus — NickK (talk) 20:21, 8 December 2017 (UTC)
  • Support Support -- Amanda (aka DQ) 18:19, 10 December 2017 (UTC)
  • Support Support Perrak (talk) 20:43, 10 December 2017 (UTC)
  • Support Support Jnanaranjan sahu (talk) 06:38, 11 December 2017 (UTC)
  • Support Support HakanIST (talk) 12:24, 11 December 2017 (UTC)
  • Support Support Facenapalm (talk) 12:36, 11 December 2017 (UTC)
  • Support Support — Luchesar • T/C 13:08, 11 December 2017 (UTC)
  • Support Support Pxos (talk) 14:20, 11 December 2017 (UTC)
  • Support Support --Meno25 (talk) 15:38, 11 December 2017 (UTC)
  • Support Support Braveheart (talk) 16:48, 11 December 2017 (UTC)
  • Support Support Support; could replace "bans" or similar verdicts, that have to be monitored by all admins to be effective (unlikely), including those that were not involved in the actual discussion (most unlikely) He3nry (talk) 17:07, 11 December 2017 (UTC)
  • Support Support KPFC💬 17:15, 11 December 2017 (UTC)