Page MenuHomePhabricator

Temporary Account Autoblock all related Accounts: Existing Blocks should not be overwritten
Open, Needs TriagePublic

Description

When blocking related accounts, existing blocks should not be overwritten.

The problem: If an account is blocked and multiple new accounts are created, and an admin blocks the new ones and uses the automatic blocking feature, this also overwrites the original reason for blocking the first account. This results in, for example, the reason for blocking the first account being changed to "block evasion."
Example:
https://www.wikidata.org/w/index.php?title=Special:Log/block&page=User%3A%7E2026-24976-02

Event Timeline

Aklapper renamed this task from Temoprary Account Autoblock all related Accounts: Existing Blocks should not be overwritten. to Temporary Account Autoblock all related Accounts: Existing Blocks should not be overwritten.Sun, May 17, 1:05 PM
Aklapper updated the task description. (Show Details)

@WikiBayer: Thanks for reporting this. For future reference, please use the bug report form (linked from the top of the task creation page) to create a bug report, and fill in all the sections in the template. Thanks.

The existing block has not been overwritten – thanks to MultiBlocks both exist in parallel: https://www.wikidata.org/w/index.php?title=Special:BlockList&wpTarget=%7E2026-24976-02
Per T419949#11921313 this appears to be intentional – and I don't think it's much of an issue?

OK, I think that doesn't make sense.
On Special Central Auth, for example, only the current block is displayed and the block hiszory in the log is also unnecessary long.

It sounds like you mean the TA massblock SHOULD overwrite existing blocks? If so, we will probably need to require user interaction when the target TAs already have multiple blocks, since there would otherwise be no way for the system to decide which block to overwrite. This could interrupt the administrative workflow to some extent, so this likely requires a deeper discussion.