Page MenuHomePhabricator

$wgCookieSetOnAutoblock should perhaps spread autoblocks when the cookie matches
Open, NormalPublic2 Story Points

Description

For reference see T5233.

So right now, you only get an autoblock if you try to make an edit while logged in as the direct target of the block. Thus in the case of a cookie based block, no new autoblocks are handed out in the event of the cookie matching.

Instead maybe we should also trigger autoblocks when the cookie matches.

Proposed new workflow:

  • User:Malory gets blocked
  • User:Malory gets a different IP address. He's not stupid enough to edit with the same account, so he registers User:Malory2
  • Since the cookie is still present, User:Malory2 is blocked via cookie [Up to this point is the current behaviour]
  • A new autoblock is set for the IP that Malory2 tried to edit from [This would be the new proposed behaviour]
  • Possibly (not sure), an autoblock should be placed on the user account Malory2, so that if he clears cookies, that account is still blocked.

Event Timeline

Bawolff created this task.Dec 12 2016, 12:45 PM
Restricted Application added a subscriber: Aklapper. · View Herald TranscriptDec 12 2016, 12:45 PM

This seems to make sense. We should double-check that autoblocks don't spawn their own cookies, otherwise it'll be spawning autoblocks all over the place.

kaldari triaged this task as Normal priority.Dec 15 2016, 6:46 PM
kaldari updated the task description. (Show Details)
kaldari updated the task description. (Show Details)Dec 15 2016, 6:48 PM
kaldari raised the priority of this task from Normal to High.Jan 31 2017, 10:39 PM
kaldari lowered the priority of this task from High to Normal.Jan 31 2017, 10:41 PM
DannyH added a subscriber: DannyH.Jan 31 2017, 10:41 PM

Putting this back in the backlog, not vital for shipping this.