Epic: ⚡️ Partial blocks
Open, Needs TriagePublic

Description

Full site blocks are like a sledgehammer, how can we build flyswatters to address misconduct that is not egregious enough for a full site block?

Sequence of development for the Anti-Harassment Tools team in 2018:

  1. T196578: 👩‍👧 MVP for partial blocks (block a user from pages only)
  2. T179110: 👩‍👧 Implement namespace blocking support
  3. T197621: If a user is partially blocked from a namespace, they should not be allowed to rename/move pages into or out of that namespace
  4. T6995: Allow users to be blocked from uploading files only
  5. T104099: Allow users to be blocked from using Special:EmailUser only
  6. T202776: Determine then implement page limit for partial blocks
  7. T202781: Determine then implement the proper way to log partial blocks
  8. T203171: Do not display "this user is blocked" messages on user & user_talk pages for partial blocks
  9. T206031: "You are blocked" messages should be contextually specific when a partially blocked user is performing non-editing actions (upload, email user, move page, etc.)
  10. T202773: Update Special:Block to match the design
  11. T202775: Update Special:Contributions to match the design for Partial Blocking
  12. T202774: Update Special:BlockList to match the design
  13. T191549: Allow users to see a list of partial blocks, filterable to the page or namespace on Special:BlockList
  14. T200938: Special:CentralAuth should not indicate if a user is partially blocked
  15. T199918: Allow a user to be blocked from creating pages only
  16. T194529: Allow a user to be blocked from moving/renaming articles
  17. Other tickets may crop up as needed based on production testing

Potential future work — all unprioritized — is captured in T204903: Epic ⚡️ unprioritized Partial Blocks features

Related Objects

StatusAssignedTask
OpenNone
OpenNone
OpenNone
OpenNone
InvalidNone
DuplicateNone
DeclinedNone
OpenNone
OpenNone
OpenNone
DeclinedNone
ResolvedTBolliger
OpenNone
Resolveddmaza
OpenNone
OpenNone
OpenNone
OpenNone
OpenNone
ResolvedTBolliger
OpenNone
Opennettrom_WMF
Restricted Application added subscribers: MGChecker, Aklapper. · View Herald TranscriptMar 21 2018, 9:59 PM

This is good idea. (Subscribing) (y)

TBolliger updated the task description. (Show Details)Apr 5 2018, 5:45 PM
MER-C added a subscriber: MER-C.Jun 7 2018, 10:48 AM
TBolliger updated the task description. (Show Details)Jun 11 2018, 9:25 PM
TBolliger renamed this task from Epic: ⚡️ Granular types of blocking to Epic: ⚡️ Partial blocks.Jun 12 2018, 10:31 PM

I collated the wikis from the 88 voters on the 2017 Community Wishlist Survey proposal for partial blocks to see which wikis were most represented from the voters. I only counted wikis where the user had 1,000+ edits (not including wikidata.)

Wiki(s)Number of users
en41
de17
meta15
it7
pl, mediawiki6
simple5
ru, es4
zh3
pt, it.wikisource, hu2

zh.wikivoyage, uk, ua.mediawiki, tr.wikiquote, tr, species, ro, or, nl, ka, ja, incubator, hu.wikibooks, he, fr, fi.wikisource, fi.wikiquote, fi, en.wikivoyage, en.wikibooks, ca.wikiquote, ca, bn, bg, bar, arz, ar.wikiversity, ar.wikitonary, ar.wikisource, ar.wikiquote, ar.wikinews, ar.wikibooks, ar were each represented by 1 user.

Keeping in mind that I have little intuition of how this would actually be implemented, or even what would be desirable from either a technical or a community perspective, it seems that a reasonable angle of attack would be to allow blocking a user from exercising a given userright(s), at least for handling the "Actions" component of this functionality, otherwise it seems likely that we'll just keep ending up back here with additional desired blockable actions.

TBolliger updated the task description. (Show Details)Sep 19 2018, 11:29 PM