Jump to content

コミュニティ要望調査2023年/複数ブロック

Phabricator プロジェクト:#multiblocks
From Meta, a Wikimedia project coordination wiki
This page is a translated version of the page Community Wishlist Survey 2023/Multiblocks and the translation is 27% complete.
Outdated translations are marked like this.

複数ブロック(Multiblocks)とはコミュニティ要望調査2023で第14位でした。この要望の目的とは、ブロックの重ね合わせです(つまり複数ブロック)。このページではまとめとして、この要望の提案に示されたニーズに関して担当のコミュニティ技術班の取り組み方を述べます。

編集者がページを荒らしたり編集合戦をする場合、管理者は編集者の動作を監視する必要があります。特定の利用者に対して、管理者はサイト全体のブロックを課すか、特定のページや名前空間を編集できないように部分的にブロックします。ただし現在、管理者が両方を同時に行うことは不可能です。たとえば1日だけ利用者をサイト全体で ブロックすることは不可能だが、特定のページの編集を無期限にブロックし続けることはできます。したがって(IP 範囲の場合と同様に)状況の深刻度に応じた適切なブロックを探すのは困難で、(IP 範囲のような)巻き添え被害を引き起こしたり、既存の部分ブロックを強制的に削除せずにサイト全体に一時的なブロックを課したりする場合があります。

More details on Phabricator. If you have any comments or questions, please leave them on the talk page.

See original Wish

Background & Problem Space

The number 14 wish on this year’s (2023) Community Wishlist Survey was Multiblocks. Wishes related to the blocking functionality appear regularly and frequently on the different wishlists.

Current status:

  • When one tries to layer blocks the previous one has to be removed.
  • It seems the former Anti-Harassment Tools team has considered multiple overlapping blocks.
Where do blocks exist in our Projects?
荒らし行為対策チームでは既に設計と探索を進行中。

既存の説明文書

Current Shortcomings of the Blocks

  • Unable to have both sitewide and partial block at the same time.
  • Can’t block different namespaces for different time periods.
  • Only one reason, shown to both the blocked user and to other admins.

用語集

ブロック
Manual:Mediawiki.org の用語集も参照
ブロックの再設定
Action by an administrator to edit an existing block to amend values in a block. The administrator that last updated a block will be the owner of the block.
被ブロック者
IP ブロックの適用対象となる IP アドレスまたはユーザー名。通常、その IP アドレスまたはユーザー名は破壊行為に関与。
ブロックの編集
管理者がブロックを編集すると、バックエンドで古い形式のブロックを削除、新しい形式を追加。「再ブロック」を参照してください。
ブロックの変更
ブロック再設定を目視確認。
ブロック解除
被ブロック者のブロックを解除。
ブロック解除
ブロック解除を目視確認。

作業の範囲および利用者の話

利用者のストーリーの要件

  • As an admin of the wikis, when I need to block users, I want to be able to block for a desired period of time, so that I can prevent malicious edits.
  • As an admin of the wikis, when I need to temporarily block users sitewide, I want to be able to combine partial and sitewide blocks, so that I know which blocks will remain in place after the temporary block expires.

範囲と制約

Not in scope:

  • Interaction with autoblocks/cookie blocks
  • GlobalBlocking
    • nb. GlobalBlocking does not have partial blocks, so this probably shouldn’t be in scope
  • Only minimal UI changes (i.e. no dialog like in the old designs)

技術面の調査

In the user interface, Special:Block will require major updates. Currently, when a user tries to block a target which is already blocked, they may elect to "reblock", which means to delete the old block and insert a new block. Simply inserting an additional block is not permitted. Similarly there is a reblocking concept in the action API's block action. These user-visible concepts of conflicting blocks and reblocking will need to be updated. API clients which perform block actions may need to be updated.

MediaWiki already has the CompositeBlock class, which represents multiple blocks on a given user. There is some technical debt in this area which we will try to rectify, but broadly, permissions checks and the Block hierarchy will continue to work as before.

The current schema has an ipblocks table with a unique index on the target fields. We plan to split this table, with a new block_target table for the target fields. Almost all queries on this table will have to be updated. In WMF production, there are approximately 6 affected write query callers and 18 affected read query callers. The Cloud Services replicas are also affected, although it would be feasible to provide a view for backwards compatibility.

この要望を採用した理由と手順は?

この要望は、2023年の優先順位付けプロセスで高スコアを獲得。14位であり、この作業の波及効果は荒らし行為に対する取り組みとして管理者にも、コンテンツの品質にも大きいと考えられます。

Updates

December 2024 - Design and product updates

As we are putting the final touches on Multiblocks, we wanted to share a few design updates and product notes so that Admins on local wikis can prepare for a world in which a target may have 2+ blocks.

In the current Special:Block page, Admins are able to search for a target (Username or IP Address) and then start applying blocking logic. But since Admins will soon be able to issue a sitewide block and a partial page block with varying expiration dates, they need a new interface. Example:

  • BadActor1 has made 1,000 edits to their local wiki, but recently made nefarious edits on the "John Lennon" article page, and was posting abusive messages on the "John Lennon" talk page. An Admin wants to send a warning message, and also block BadActor1 from editing "John Lennon" indefinitely.
  • The Admin can first block BadActor1 from editing "John Lennon" article indefinitely. Then, on the Special:Block page, they can block BadActor1 from editing the Talk Page namespace for 24 hours. Lastly, as a slap on the wrist, they issue a 2-hour sitewide block, also on the Special:Block page.
  • The Admin can issue these blocks in any order. When one block expires, the wiki will still respect the rules of other blocks.
  • Admins may also edit a block. To edit a block, Admins will search for a target; all active blocks will appear in the Active Block Log. Clicking "Edit" will populate the block's current logic. To update the block, admins click save.
  • Admins may also remove a block on the Special:Block page. To remove a block, Admins will search for a target; all active blocks will appear in the Active Block Log. Clicking "Remove" will populate a dialog that allows the Admin to provide a reason and watch the target. Removing one block will not interfere with any other existing blocks.
  • The Special:Block page is built using the Codex design system. Admins who disable javascript will have all the functionality of this page, with a slightly different layout.

To build multiblocks, we have rebuilt the entire Special:Block page to help admins issue, edit, and remove blocks from one place. Over time, we will direct Admins towards Special:Block instead of Special:Unblock.

We anticipate rolling these changes out in two subsequent phases. First, since there are some major UX changes to Special:Block, we anticipate rolling out updates to Special:Block in mid-late January. We plan to follow up with the rollout of Multiblocks in late Jan - February, unless there are unforeseen technical delays.

February 2024 – Design Updates

Over the last few weeks we’ve been designing the user experience and user interface while talking to some admins. Here are some design decisions we want to implement:

  • Landing page We’ve enhanced the Special: Block user page for Admins, making it a cleaner and more intuitive experience so that users can issue, modify, or remove blocks with ease. Changes include improving the page’s order of operations, adding descriptions, a condensed layout for easier block management, and UI components from Codex (Wikimedia’s design system).
  • Account filled in
    • Now that an “account” can have multiple blocks, it’s important that an Admin can see an account’s active blocks at the top of the page.
    • We moved the “block log” to the top of the page as well, so that an Admin won’t have to scroll.
  • Active blocks table displayed Admins can now remove or edit blocks from the Special: Block page. We hope this allows volunteers to make quick changes to the blocks on an account, should they need to.
  • Partial ban interaction The partial ban form is hidden behind one click, which allows us to condense information on the page. If an Admin wants to issue a partial ban, once they click “Partial” they will see the remainder of the content they need to fill out.
  • Edit/remove block menu Admins can now remove or edit blocks from the Special: Block page. We hope this allows volunteers to make quick changes to the blocks on an account, should they need to.
  • Editing an active block Admins can now remove or edit blocks from the Special: Block page. We hope this allows volunteers to make quick changes to the blocks on an account, should they need to.
  • Remove block When an Admin wants to remove an active block, they will remove the block using this dialog.
  • Block log The block log for the account will be displayed in the table, with the current design.
  • Setting expiration time We’ve removed the calendar date picker for now, so the expiration time will be set just with the dropdown menu. We haven’t changed any of the options in the menu.

December 2023 – Design Updates

利用者のジョブの話:複数のブロックを課す (T350485)

  • When ... a target is disruptive in multiple locations
  • ... I want to create more than one block for the target,
  • ... so that I can dissuade them from disruptive behavior while not completely driving them away from the wiki.

利用者のジョブの話:ブロックの閲覧 (T348682)

  • When I need to create/remove/re-block a target ...
  • ... I want to see the list of active and past blocks on a target,
  • ... so that I can make better decisions

利用者のジョブの話:ブロック解除の流れ (T350486)

  • 対象者のロックを解除する時 ……
  • ……シンプルで一貫したワークフローがないだろうか、簡単に探せて結果が予測可能なら、
  • ……こういう重要なタスクの管理が簡単になって他のボランティア活動とも平行してできる。

作業が成功したと判断する目安は?

  • 管理者層のうち要望調査でこの機能に賛成票を入れた、そして/もしくは使っていて満足した人たちを対象に調査することを検討
  • 当チームで複数ブロックの発動、(複数ブロックが)コミュニティで決めた方針により標準化された可能性を認識すること