Community Wishlist Survey 2023/Admins and patrollers/Layering/timing of blocks

Add links
From Meta, a Wikimedia project coordination wiki

Layering/timing of blocks

  • Problem: Twofold:
    • The introduction of partial blocks was long overdue. However, admins are still limited to one or the other. When a user has, say, edit-warred on an article but contributes constructively elsewhere, we can either block sitewide for a short time or partial block for a long time. Both options present a tradeoff. The shorter sitewide block may seem unfair to the blocked user since it was only one article, and for other editors on the page it is entirely possible that once the block expires the blocked user just goes back to the edit warring because, y'know, they were right. But a longer partial block may seem too lenient if the edit warring on the one article was particularly egregious (i.e., one or two reverts a day, incivil edit summaries, etc.).
    • I was asked a while back by a user to block sitewide a range that was already under long-term partial block on several other articles; they may have been at the limit. I had to decline since changing to a sitewide block would completely wipe out the partial block ... i.e., once the sitewide block expired the range would be free.
  • Proposed solution: Allow blocks to be layered, with a partial block running concurrently with a shorter sitewide block. I've read that this is not possible technically at the moment. If it indeed isn't, perhaps we could set things up so that the partial block would begin only upon the expiration of the sitewide block, i.e., User X is blocked 24 hours for violating 3RR and then for a week from the article or articles where the violation occurred. Yes, you could do this all manually now, but it gets kind of messy.
  • Who would benefit: Editors who will know that there is a greater risk to edit warring or generally tendentious/disruptive behavior, facilitating more constructive collaboration; editors blocked for such conduct who will have the chance to show that they can edit constructively off a certain article/topic, and admins working to prevent such disruption.
  • More comments: It would also be useful to allow this same functionality for page protection ... i.e. page Foo will be extended-confirmed protected for, say, a month, and then automatically drop down to semi-protection for the next five or whatever. Daniel Case (talk) 05:09, 6 February 2023 (UTC)[reply]
  • Phabricator tickets: phab:T194697
  • Proposer: Daniel Case (talk) 20:20, 3 February 2023 (UTC)[reply]

Discussion

We have an important update about this wish – October 17, 2023

Hello Daniel Case, and everyone supporting this request about blocks.

We have selected this wish for fulfillment, and as usual, we have created a project page to share information about our approach and give you space to give feedback.

Please note that the project has been renamed Multiblocks.

Visit the project page to learn more about the scope of work, constraints, and the status of our technical investigation into this wish.

Please read what we have presented, and give us feedback immediately if you disagree with anything. We would also like to know if you agree with our approach.

Thank you. ––– STei (WMF) (talk) 22:25, 17 October 2023 (UTC)[reply]

We have updated the project page – November 10, 2023

We have added more information in November 2023 about our technical investigation of the wish, and a brief glossary of terms used on the project page. Please check and give feedback on the project talkpage.

–– STei (WMF) (talk) 19:00, 10 November 2023 (UTC)[reply]

Pinging users: –– STei (WMF) (talk) 19:00, 10 November 2023 (UTC)[reply]

Voting

Retrieved from "https://meta.wikimedia.org/w/index.php?title=Community_Wishlist_Survey_2023/Admins_and_patrollers/Layering/timing_of_blocks&oldid=26165055"