Jump to content

維基媒體應用程式/團隊/安卓系統(Android)/反破壞工具

From mediawiki.org
This page is a translated version of the page Wikimedia Apps/Team/Android/Anti Vandalism and the translation is 68% complete.
Languages:

背景

安卓系統（Android）團隊收到了來自不同語言社群的請求，希望透過應用程式提高編輯品質。 社群成員希望擁有公平且無偏見的跨維基管理工具。 團隊的目標是強化現有的管理流程，同時確保它的公平性。您可以在2022 願望清單中找到其中一個例子。

隨著應用程式最近的更新，例如原生監視清單、貢獻記錄、編輯歷史，以及在編輯差異頁面上添加撤銷和回退按鈕，我們有機會制定改善應用程式管理工具的方案。此改善方案將建立在現有的手機版微貢獻流程的基礎上。

團隊計劃開發一個反破壞工具（V1），以滿足各個語言維基上經驗豐富的管理員的需求。同時，團隊將引入培訓任務，以幫助編輯經驗豐富但沒有巡查經驗的編者學習巡查。我們將與社群密切合作來完成此項工作。該團隊同時將與研究團隊合作改進 ORES 等工具，並與處理移動版網頁上此問題的管理員工具（Moderator tools）團隊合作，確保跨平台用戶獲得無縫體驗。

產品需求：

  • 編輯者可以查看各個編輯的差異
  • 編輯者可以選擇「恢復」或「跳過」更改建議
  • 可以顯示最近來自不同語言的維基的編輯
  • 編輯者可以建立並儲存警告訊息，以便在撤銷編輯時使用
  • 後續版本（V2）將容許有經驗的編者在應用程式上進行巡查

技術限制

目前單一介面中無法同時存在來自不同語言的維基的編輯，但使用者將可以在語言之間進行切換。

假設與驗證

假設與假定

我們認為，簡化巡邏任務並將其建構成高級任務將是有益的。 沒有管理員或回退權限的經驗豐富的編者可以被分配較容易的巡查或培訓任務，一旦他們達到初始巡查活動的門檻，他們就可以晉升到更高的級別。 為了實現這一目標，我們計劃從驗證概念開始，即由擁有回退權限用戶通常的巡查開始。

我們知道，與 NPP（新頁面巡查）、AFD（待刪除文章）和 AFC（待創建文章）等任務相比，巡查最近編輯是一項優先任務，並且更適合行動裝置。此外，我們希望社群能夠就跨不同語言實施培訓任務達成共識。

驗證

  • 關鍵指標 1：65% 使用該工具的目標成熟受眾認為這有助於維護維基的質量，並將推薦給其他巡查者
  • 關鍵指標2：成熟受眾的編輯量增加5%
  • 關鍵指標 3：10% 的目標成熟受眾參與過濾器偏好
  • 關鍵指標 4：65% 的目標成熟受眾在 30 天內至少使用該工具 3 次
  • Guardrail：沒有回滾權限的經驗豐富的用戶，無論是否使用過替代巡邏工具，都應該同樣了解工作流程
  • Guardrail：不應有關於該工具根據應用程式內報告機制對代表性不足的內容或貢獻者進行負面定位的報告

了解一些有幫助的事情

  • 在查看 MediaWiki 標籤（SWViewer、Huggle 和 Twinkle）時，與其他巡查工具相比，我們的工具的使用情況如何
  • 我們是否看到撤消/回滾/感謝事件增加
  • 相對於其他「建議編輯」任務，此任務在我們的目標受眾中受歡迎程度如何？
  • 該功能中哪些操作最受歡迎？

Risk management

Risk Cause Level Response Response Action Trigger Contingency Plan
Tool causes a decrease in new editor retention on wikis where it's available Editors use the tool to increase the volume of edits they're able to revert, but do not leave talk page messages to explain the revert, leaving new editors confused and unmotivated. Medium Monitor Measure the retention rate of editors who had a revert from the patroller task. If they got a talk message, did that increase their retention? Qualitative complaints If a user has not left a talk page message after using undo or rollback and attempts to move to next edit, add a prompt asking/requiring them to leave a Talk Page message
Policy disagreements between existing patrollers and newer patrollers using Edit Patrol / New patrollers use the tool a way that confuses other patrollers. Behavior and/or communication from App patrollers is seen as insufficient or lacking by other patrollers. A new group of editors are able to start patrolling at scale using Edit Patrol, but they are not aware of existing policies or norms. Medium Mitigate Post updates, and invite to office hours patrolling groups (CVU, recent changes patrol, small wiki monitoring team, stewards, global sysops, global rollbackers) before full release. Share Example Messages with communities. Qualitative complaints from patrollers Add more policy and template onboarding to tool, and revisit Example Messages after Community Configuration 2.0 is released. Continue work on building training task.
An increase in edit wars Patrollers reviewing the same feed of edits go back and forth reverting each other's changes because revisions or rollbacks made in the tool appear in the feed for the next person (if no filters are applied). Low Accept - Qualitative complaints Add more onboarding about policies surrounding Edit Wars. Add in-app warning for edit-war behavior.
The tool is being used to negatively target underrepresented content or contributors. Patrollers are systematically reverting good faith edits for particular users or languages, harassing, or mistreating contributors through the tool. Low Mitigate Unless otherwise requested per wiki, the tool available to those with rollback rights. Qualitative complaints, in-app reporting mechanisms, guardrail analysis by Product Analyst Add universal code of conduct onboarding to tool.
The tool causes an increase in vandalism, and increase in amount of work for existing patrollers Vandals use the streamlined interface to quickly revert or rollback large quantities of good faith edits. Low (Dormant) Mitigate Unless otherwise requested per wiki, the tool available to those with rollback rights. Qualitative complaints and anomalies surfaced in data reporting Implement a maximum number of undos/rollbacks that can be done in a range of time.
Someone is exposed to vandalism or there is a copyright violation in Example Messages provided in-app A vandal has edited the Example Messages or pasted copyright material in using Community Configuration 2.0 or Translate.wiki, and they automatically appear in everyone's app Low (Dormant) Mitigate Once community configurable, ensure permissions are set for editing with Growth team. Qualitative complaints Inrease necessary permissions to edit Example Messages.

如何追蹤進展

我們創建了T322083作為 Phabricator Epic 來追蹤這項工作。我們邀請您在那裡或在我們的討論頁面上與我們合作。 我們邀請您在那裡或在我們的討論頁面上與我們合作。

隨著進展，我們將在此頁面上定期更新。如果您有興趣參加我們主持的設計回饋會議，請在我們的討論頁面上告知我們，我們將與您聯繫。

我們有以下推出策略：

2023–2024 時段 諮詢 發佈給回滾權限的用戶
2023年10月 印尼语维基百科
2023年11月 印尼语维基百科 印尼语维基百科
2024年1月 西班牙语维基百科, 法语维基百科
2024年2月 西班牙语维基百科, 法语维基百科
2024年3月 中文维基百科, 英语维基百科, 伊博语维基百科 西班牙语维基百科, 法语维基百科
2024年4月 英语维基百科, 伊博语维基百科, Global Sysops and Rollbackers 英语维基百科, 伊博语维基百科
2024年5月 適用於所有維基專案


技術文檔

如果您有興趣了解該功能的實作方式，請造訪巡邏者任務開發說明以了解更多詳細資訊。

更新

2024年9月

  • After conversations with Igbo Wikipedia admins, we changed the availability of Edit Patrol for users on Igbo Wikipedia, and it’s now available to users with 500 edits and 30 days of tenure. T371442

2024年8月

  • Inspired by this feature, we also added an entry point to the talk page from the Watchlist Diff page. T370697

2024年7月 - Results after 30 days

We have results to share 30 days after the release of Edit Patrol to all Wikipedias within the Android App. Overall, we met or almost met 3/5 of our Key Indicators, and 2/2 of our guardrails.

Validation

  • KR 1.1: 65% of Target mature audiences that use the tool say they find it helpful for maintaining the quality of wikis and would recommend it to other patrollers
    • Almost met: In an in-app feedback about satisfaction with the feature, 63.6% of users who gave feedback selected Satisfied, 22.7% selected Neutral, 13.6% selected Unsatisfied
    • Qualitatively: an Indonesian Wikipedia editor mentioned they found accessing the talk page templates through the feature helpful, and that it would make them more efficient. They mentioned this feature is the only option for them to check Recent Changes on Indonesian Wikipedia. Another Indonesian Wikipedia editor found the tool helpful for patrolling without needing to carry a laptop. 2 other editors mentioned they are excited to download the app to try the Edit Patrol feature, one mentioned it might make them more active in patrolling.
  • KR 1.2: 10% of target mature audiences interacted with another user by sending thanks or a talk page message.
    • Not met: 3.2% of all users sent Thanks, no users sent talk page messages through the feature. We heard from patrollers about the importance of communication along with undo and rollback actions especially for newcomers. However we did not see users sending Talk Page messages along with edits, even though ‘Talk’ was an option in the toolbar. Iterative improvements to motivate users to send talk page messages should be considered for future work.
  • KR 1.3: 10% of target mature audiences engage with filter for preferences
    • Met: 23.8% of users engaged with Filters
  • KR 1.4.1: 30% of users engage with the tool more than once in a 30 day window
    • Met: 38.1% of users returned on more than 1 day
  • KR 1.4.2: 65% of Target mature audiences (potential sysop/rollback Android editors) engage with the tool once in a thirty day window
    • Not met: 30.6% of all potential users engaged with the tool once. This could be due to a few reasons: many users with extended rights already have established workflows on Desktop or Mobile Web, or users with extended rights who have the the Android App are not aware of the feature.

Guardrails

  • Guardrail 1: Experienced users without rollback rights, users that have and have not used alternative patrolling tools equally understand the workflow
    • Met: We conducted interviews with 6 Wikimedians who had a variety of experience patrolling with V1 of the feature. Some were admins, and others were experienced editors. 2 interviewees had not used alternative patrolling tools.
      • 6/6 of participants thought that the location of the tool is intuitive.
      • 6/6 could easily understand the 'List of edits' page displayed
      • 6/6 of the participants thought that the information provided through the feature looked fine.
      • 2/6 of the participants didn't understand the title 'ORES score' (they knew good vs bad faith edits but didn't relate that to the ORES score), and we updated the way the scores were presented in response.
  • Guardrail 2: We do not receive reports of tool being used to negatively target underrepresented content or contributors based on in-app reporting mechanisms
    • Met: We have not received reports through in app reporting.

Curiosities

  • Curiosity 1: How does use of our tool compare to other patrolling tools when looking at MediaWiki Tags (SWViewer, Huggle, and Twinkle)
    • One of our goals in building this tool was that it could work across language wikipedias.
    • In terms of Edits: We saw that 93.1% of Android Patroller edits were made on wikis other than English, comparable to SWViewer where 88.4% of edits were made on language wikipedias other than English. This is markedly different from Huggle and Twinkle, where the majority of edits are made on English Wikipedia
Rollback/Undo Edits by Tool on English vs Other Wikis
Tool Total Rollback/Undo Edits % English Wikipedia Edits % Other Wiki Edits
Huggle 9249 88.6% 11.4%
Twinkle 17133 89.9% 10.1%
SWViewer 3758 11.6% 88.4%
Android App Patrollers 331 6.9% 93.1%
    • In terms of unique Editors, 60% of unique editors on the Android Patrolling tool were editing on a language other than English, comparable to SWViewer where 71% of editors are editing on a language other than English. Huggle and Twinkle’s unique editors/bots were primarily editing English Wikipedia, with only 10% of Huggle’s unique editors editing a language other than English, and 14% of Huggle unique editors.
Unique Rollback/undo Editors by Tool on English vs Other Wikis
Tool Total Uniques % English Wikipedia Editors/Bots % Other Wikipedia Editors/Bots
Huggle 75 89.33% 10.67%
Twinkle 829 85.77% 14.23%
SWViewer 64 28.13% 71.88%
Android App Patrollers (All non bot editors) 23 39.13% 60.87%
  • Curiosity 2: Do we see an increase in Undo/Rollback/Thank events
    • We saw an average 7.9% increase in rollback/undo counts compared to previous monthly events. We did not see an increase or change in Thank events.
  • Curiosity 3: How popular is this task with our target audience relative to other Suggested Edits task?
    • Edit patrol had 331 edits in a 30 day time period, making up 2% of all suggested edits. Adding image captions has a similar usage rate, at 3.1% of all suggested edits, and 517 edits in a 30 day time period. Edit patrol has a key difference in availability: it is only available to a much smaller audience: editors with rollback rights (other suggested edits are available to users with 50+ edits).
  • Curiosity 4: What actions are most popular in the feature?
    • All editors who entered the feature opened an edit from the list of edits, and swiped through edits. 25.4% of all editors completed undo or rollback actions.
Action % of All Users Completing Action
Swiping through edits 100.0%
Clicking on an Edit 100.0%
Completing an Undo 23.8%
Completing a Rollback 12.7%
  • Curiosity 5: How are users interacting with Saved Messages and Example Messages?
    • We have not seen engagement with Saved Messages so far.
  • Curiosity 6: How are users interacting with template search and filing out template data?
    • We have not seen engagement with Templates so far.

Lessons Learned

  • 30% of our eligible audience engaged with the tool in a 30-day window. When deciding how to release the feature, we listened to community requests to only make it available to users with rollback rights. This resulted in a smaller eligible audience, and we did not have a baseline for frequency of use in a given period. In the future, we should continue to explore how the feature could be made available to more users, especially on small to medium-sized Wikipedias. If community configuration capabilities are added to this tool in the future, it could allow for expanded access: communities could choose to allow editors with a certain edit threshold to have access to this tool.
  • We heard from patrollers about the importance of communication along with undo and rollback actions, and we heard requests to add support for Templates. However, we did not see users sending talk page messages along with edits, or using templates within the feature. The feature could have benefitted from an in-app feedback mechanism triggered after a user completed a rollback or undo function, but did not send a message.

2024年6月

  • We connected with Moderator Tools on the release of the RevertRisk model to RecentChanges, and agreed that we'll wait to confirm model stability and effectiveness with Automoderator on production wikis before assessing the work needed to make the RevertRisk model available via RecentChanges. In addition, we are still monitoring the timing of needing to switch to RevertRisk model as a result of anticipated degradation of the GoodFaith and Damage scores from ORES legacy.

2024年5月

  • Edit Patrol is now available on production for all Wikis! T350513
  • Community ambassador, Bona, shared the feature at the ESEAP 2024 conference, and we heard the following feedback:
    • One Indonesian Wikipedia editor mentioned they found the talk page templates helpful, and it makes them more efficient. They mentioned this feature is the only option for them to check Recent Changes on Indonesian Wikipedia.
    • Another Indonesian editor mentioned it was confusing at first to change their primary language to view the tool (indicating that we could improve the entry point). They found the tool helpful for patrolling without needing to carry a laptop.
    • 2 other editors mentioned they are excited to download the app to try the Edit Patrol feature, one mentioned it might make them more active in patrolling.
  • We have preliminary analysis to share after Edit Patrol’s release (acknowledging this was a phased release, we will share numbers 30-days after its release to all wikipedias) T363353
    • Key Indicator 1: 65% of Target mature audiences that use the tool say they find it helpful for maintaining the quality of wikis and would recommend it to other patrollers
      • Actual: 57.1% of users who gave feedback selected Satisfied, 42.9% selected Neutral
    • Key Indicator 2: 10% of target mature audiences interacted with another user by sending thanks or a talk page message.
      • 0% of users sent thanks or talk page messages. We had a discrepancy in our data instrumentation that caused us to over-report the number of messages that were sent through the tool. This was updated to the corrected percent on 10 July 2024.
    • Key Indicator 3: 10% of target mature audiences engage with filter for preferences
      • We saw 1.6% of users engage with Filters
    • Key Indicator 4: 65% of Target mature audiences engage with the tool at least once in a thirty day window
      • We saw 87.5% of those who opened the feature completed successful engagements with the tool.
  • We learned we may be able to offer blocking as an action, as requested by some users
  • We’ve documented multiple ways that community configuration could benefit this tool in the future.
  • Fixed some small issues in Edit Patrol:
    • Make “Next” button active for Saved / Example Messages in Talk flow, even if user has not made change to saved message T362994
    • Navigating back from editing a saved message now returns you to the tab you started on T362996

2024年4月

The team released “V2” of Edit Patrol to target wikis, which includes Saved messages functionality and support for Templates to production, T356774 & T355141.

  • Edit patrol is now available on production for Igbo and Chinese Wikipedia, it will be available in production for all Wikis by mid-May.T350512
  • We received feedback that we should change “warn” to “talk” to encourage more positive behavior, and we finished updating this throughout the feature: T360449 & T361648
  • Outreach:
    • We met with admins from the Igbo community to share the feature and receive feedback on how it lands with a smaller wiki.
    • We shared release information and consultation hours information with English Wikipedia, and on discussion pages of patrolling audiences: Stewards, Global Rollbackers, Global Sysops, Recent Changes Patrol, Small wiki monitoring team, and Coutnervandalism unit. Our consultation hour was held on Friday, April 26.
    • We coordinated with WMFR to share a short async presentation and demo in the French Admins meeting on April 13.
  • Learnings:
    • We learned from one English Wikipedia admin that they would value quick access to Blocking users through this tool, and would expect to find it under the user overflow menu. They would also like to see a prompt to quickly add the appropriate talk page message to accompany the block. T363422
    • A global rollbacker shared that they would like to have access to Advanced Reporting and Vetting (ARV), which is supported through Twinkle.
    • We heard another request for the Example Messages provided to be community configurable, highlighting the importance of this work once Community Config supports the apps T358265
    • We heard feedback that reaffirms our choice to make this tool only available to rollbackers at the start, but suggested a threshold to be considered in the future could be 500+ edits and 30 days of tenure. We see another opportunity for Community Config here, supporting wikis in changing permission levels for this feature.T358265

2024年4月, Special Mid Month Update

  • Edit patrol has been released to all wikis in the Beta version of the app! To view the feature, download or update the Wikipedia Beta app. Open the Edits tab, and look for Edit Patrol under Suggested Edits. The feature is available to users with rollback rights, and will display if you have rollback rights on the language that is set as your Primary in the App.
Edit patrol demonstration on test.wiki

2024年3月

  • We released the Edit Patrol suggested edit to French and Spanish Wikipedias. T350511
  • Development continued for Saved Messages for Edit Patrol (Example messages available in the App) and access to templates.
  • While completing development on Saved Messages, we learned that it wasn’t feasible to allow users to edit, delete, and rearrange the prewritten "Example Messages" from within the app in the same way that users can edit their own custom made messages. We updated the designs for Saved Messages to add visual separation between “Your Messages” and “Example Messages” T359209
  • We learned we will be able to use the Growth team’s community config to make Example messages available for modification in the app.
  • We solicited feedback about how to handle the links to policies within the example messages: we heard from one global admin (a staff member), who recommended against linking to English Policies as the fall-back. We heard from a member of Igbo community that they may choose to keep the links to English policies, and eventually update them. We decided to modify the wording of the English example messages, adding "this wikipedia" in a few places so that the sentences make sense without links. Translation instructions on translatewiki will say, “Please include the relevant language version of the link(s). If no link is found, please do not include a link. Editors may add a link(s) to another language wiki's policy if desired.” We will continue to get more input as we scale to more languages and iterate on how we are treating saved messages for small wikis until community config is available. The example message texts are on a Media.wiki page with links to translations.
  • We received feedback that we should change “warn” to “talk” to encourage more positive behavior, and began updating this throughout the feature. T360449
  • In our meeting with Spanish Wikipedians, they reaffirmed the choice of Edit Patrol only being available to rollbackers.
  • We are sharing the feature to Igbo Wikipedia April 3rd and will have office hours with English Wikipedia April 26nd.

2024年2月

  • We hosted two synchronous community consultations & recorded a third where we shared the Edit Patrol workflow, and showed designs for Saved messages and templates:
  • We've started development on Saved Messages T356774 (example messages available in the App) and access to templates T355141, which was well received by French Wikipedia. Draft saved messages are posted here, and we welcome feedback on the discussion page.
  • Another community member raised interest in the example warning messages being configurable via the community config.(T358265#9573393), and we are coordinating with the Growth team on this.
  • French Wikipedians reaffirmed the choice of Edit Patrol only being available to rollbackers.

2024年1月

  • Indonesian Wikipedia requested consideration for using Edit Patrol in the upcoming election to fight disinformation and vandalism. Our team had the feature reviewed by our legal team, and volunteers were cleared to use the tool for patrolling during their upcoming election.
  • This month we learned that some communities appreciate being able to have speedy deletion as an option in patrolling tools, which we will consider for future iterations of this feature.
  • Additionally, our team met with the Growth, Moderator Tools and Machine Learning teams to discuss adding the revert risk model to recent changes filtering. We may be able to switch over from using Good Faith and Damaging ORES scores to the Revert Risk model as we scale to Spanish, French and Chinese Wikipedias in the coming months. This may open the door for an experimental training task for experienced editors without rollback rights.
  • We have established demo sessions for our next set of pilot wikis:
    • French Moderators - scheduled for 21 February 2024 from 16-17 UTC
    • Spanish Moderators - scheduled for 28 February 2024 from 16-17 UTC
    • Chinese Moderators - recorded presentation to be shared asynchronous
  • Our designer worked on the flow and UI for the saved warning messages and templates, which will be released in the coming months.
  • Choose Talk
    Choose Talk
  • Select message from list of saved messages
    Select message from list of saved messages
  • Select from list of example messages
    Select from list of example messages
  • Create new message
    Create new message
  • Review message and make changes
    Review message and make changes
  • Save as new message or update saved message
    Save as new message or update saved message
  • Review preview and publish (Web view)
    Review preview and publish (Web view)
  • Edit list of messages by swiping left or right
    Edit list of messages by swiping left or right
  • Reorder or delete multiple messages
    Reorder or delete multiple messages
  • Saved messages are always accessible from the overflow menu
    Saved messages are always accessible from the overflow menu
  • Template Flow: T355141: The team is working to add support for templates, so patrollers can utilize existing templates in their messages
  • Templates will be accessible from the Wikitext editing toolbar
    Templates will be accessible from the Wikitext editing toolbar
  • In Saved Messages (Edit Patrol), create a new message
    In Saved Messages (Edit Patrol), create a new message
  • Compose message, and open Template icon
    Compose message, and open Template icon
  • Search for templates by name, recently used are displayed
    Search for templates by name, recently used are displayed
  • Fill out template form and insert
    Fill out template form and insert
  • Message with template inserted. Then follow same steps to, save, preview, publish
    Message with template inserted. Then follow same steps to, save, preview, publish

2023年12月

Patrolling Pain Points on French Wikipedia

We met with a few language communities to get feedback about Edit patrol. The Indonesian Wikipedia community approved the release of the feature for their community and shared which templates are used for warnings, which we will incorporate in a future release. For the month of December we are enabling users to save warning messages on their device (T343841). In January we will begin outreach to Spanish and Chinese Wikipedia to scale to more communities. We’ve already begun outreach to French Wikipedia via the French Wikimedia ED, he shared some pain points identified by French patrollers as it relates to RC Live and SWViewer and other tools as it relates specifically to the French Wikipedia community that we are taking into consideration for Edit Patrol. We are hoping to establish office hours sometime in February with French Wikipedia to discuss Edit patrol.

2023年11月

Release to Indonesian Wikipedia

Edit Patrol 已發佈到印尼語和維基百科測試版。為了在「建議編輯」中查看該功能，您必須具有回滾或管理員權限。 In order to see the feature in Suggested Edits you must have rollback or sysops rights.

透過第一個版本，回滾權限的用戶能夠：

  • 加入任務並解釋何時使用「感謝」、「觀察」、「警告」、「撤消」或「回滾」，以及 ORES 分數的解釋。 (T343242)
  • 訓練模式 1
    訓練模式 1
  • 訓練模式 2
    訓練模式 2
  • 訓練模式 3
    訓練模式 3
  • 巡邏編輯 1
    巡邏編輯 1
  • 巡邏編輯 2
    巡邏編輯 2
  • 撰寫、儲存並發佈第一條警告訊息。 (T344842)
  • 撰寫新的警告訊息
    撰寫新的警告訊息
  • 編輯新訊息
    編輯新訊息
  • 回擊
    回擊
  • 空白主題
    空白主題
  • 空白訊息
    空白訊息
  • 儲存變更
    儲存變更
  • 訊息已發佈
    訊息已發佈
  • 嘗試不帶訊息標題發佈
    嘗試不帶訊息標題發佈
  • 新增訊息標題
    新增訊息標題
  • 訊息已儲存並發佈
    訊息已儲存並發佈
  • 選擇、編輯、儲存和發佈現有警告訊息 (T344842)
  • 新增訊息
    新增訊息
  • 選擇訊息
    選擇訊息
  • 已選擇的訊息
    已選擇的訊息
  • 編輯訊息
    編輯訊息
  • 預覽訊息
    預覽訊息
  • 發佈、保存
    發佈、保存
  • 儲存新訊息 空訊息標題
    儲存新訊息 空訊息標題
  • 預覽訊息
    預覽訊息
  • 儲存變更訊息
    儲存變更訊息
  • 訊息已儲存並發佈
    訊息已儲存並發佈
  • 查看有關其他編輯的信息，包括他們作為編輯的任期和編輯次數(T343835)
  • 編輯選單列表
    編輯選單列表
  • 使用者資訊模態
    使用者資訊模態
  • 最近更改來源的篩選器包括維基專案的語言、註冊狀態、經驗程度、品質分數預測、使用者意圖預測、自動貢獻和編輯的重要性。過濾器頁面同時允許按最新版本排序，也可以透過編輯進行搜尋。
篩選無結果
  • 報告過濾器問題的能力(T343834)
應用程式列選單 - 功能對話框問題

我們歡迎有關該功能的回饋，因為我們準備好聯繫其他維基專案來擴展該功能。

2023 年 9 月：推進巡查者任務 V1——向印尼語維基百科社群推出新功能

我們繼續開發巡查者任務的 V1，並向印尼語維基百科宣布了該功能。我們的工程師示範了巡查者任務 V1 的過濾器：

  • 沒有結果
    沒有結果
  • 重置過濾器
    重置過濾器
  • 預設過濾器
    預設過濾器

2023 年 8 月：專案更新與技術考量

  • We shared updates about this project at Wikimania. The recording can be found on Youtube starting at 1:24:30. We received a question about having a central place for Warning messages that can be used across apps. We are planning to work with the Growth team to explore the possibility of centralized warning messages.
  • We became aware of the deprecation of ORES and migration to Liftwing which will host the revertrisk model. Due to our team using the MediaWiki API to show the recent edits feed, we will continue to show the Goodfaith and Damaging Models at least in V1. Using the Revert Risk model would require two API calls, which could slow down the feature, this also doesn’t address filtering. If you have feedback about this technical decision, feel free to comment on our discussion page.
  • We created designs for Onboarding to the feature T343242.
  • 解釋該功能的用途
    解釋該功能的用途
  • 主要行動清單
    主要行動清單
  • 數據採集
    數據採集
  • 解釋「品質」分數
    解釋「品質」分數
  • 解釋「意圖」分數
    解釋「意圖」分數
  • 指示可以在哪裡提交有關該功能的回饋
    指示可以在哪裡提交有關該功能的回饋

2023 年 7 月：設計研究與訪談結果

可用性測試

我們進行了一項有審核的遠端可用性測試，涉及六名經驗豐富的貢獻者，他們使用安卓系統(Android)設備並自願花時間監控西班牙語、法語、英語和中文維基專案上的活動。 我們從這些維基專案中選擇了參與者，因為他們擁有大量具有管理員/回滾權限的編輯，這使我們能夠有效地收集可用性回饋。

巡查員對「編輯巡邏」工具的早期設計和可用性提供了寶貴的見解。

在測驗期間，編輯人員的任務是使用該工具的有限原型完成簡短的作業。他們同時被要求即時敘述他們完成這些任務時的經歷。

  • 在應用程式中找到該工具
    在應用程式中找到該工具
  • 從最近編輯清單中選擇一個編輯
    從最近編輯清單中選擇一個編輯
  • 查看頁面上的差異和附加信息
    查看頁面上的差異和附加信息
  • 決定是否應恢復編輯
    決定是否應恢復編輯
  • 向編輯發送警告訊息
    向編輯發送警告訊息
  • 將頁面新增到他們的關注列表中
    將頁面新增到他們的關注列表中

For additional details about the usability test, please refer to the following link.

結果

參與者的回饋和寶貴建議有助於改進初始設計。 我們實施了以下改進：

  • 參與者表示希望在最近編輯頁面上為每次編輯顯示標籤，並能夠辨別編輯者是否對單一頁面進行了多次編輯。
  • 之前的編輯列表
    之前的編輯列表
  • 新的編輯列表
    新的編輯列表
  • 下拉式選單可查看同一編輯者在同一頁面上所做的編輯
    下拉式選單可查看同一編輯者在同一頁面上所做的編輯
  • 我們的目標是在顯示最近編輯的頁面上合併篩選器。為了確定「編輯巡邏」工具初始版本的過濾器，我們諮詢了巡查員。他們建議包括以下過濾器：語言、用戶註冊和體驗、自動貢獻、貢獻品質預測、用戶意圖預測、最新修訂和重要性。隨後，我們設計了一個包含這些過濾器的頁面，如下所示。
  • 過濾器
    過濾器
  • 差異視圖頁面已簡化
  • 之前的差異視圖頁面
    之前的差異視圖頁面
  • 之前帶有完整底部工作表的差異視圖頁面
    之前帶有完整底部工作表的差異視圖頁面
  • 新的差異視圖頁面
    新的差異視圖頁面
  • 較小的設計增強已應用於為巡查員創建、保存、發佈和編輯警告訊息的過程。現將修改後的設計展示如下，以供大家參考。
  • 編寫新的警告訊息
    編寫新的警告訊息
  • 選擇已儲存的警告訊息
    選擇已儲存的警告訊息
  • 參與者提供了有關巡邏的進一步回饋，我們的目標是透過入門、工具提示或提醒在工具中傳達這些回饋。這些要點包括：以同理心與其他貢獻者溝通的重要性，以及強調巡視編輯的品質優先於數量。

「編輯巡邏」工具目前正處於開發階段，您可以透過Phabricator T343224追蹤其進度。

2023 年 2 月：初始設計概念

該團隊透過結合現有工具的見解和我們收集的有關其局限性的回饋，開發了初步的設計概念。 我們與管理員工具團隊和研究團隊分享了這些概念，以徵求他們的意見和回饋。

  • Concept for filtering contribution date, ORES Scores or Language
    Concept for filtering contribution date, ORES Scores or Language
  • Design concept for expanding the bottom sheet
    Design concept for expanding the bottom sheet
  • Design concepts for the overflow menu
    Design concepts for the overflow menu
  • Design concept for using templates when leaving a warning
    Design concept for using templates when leaving a warning

我們將利用收到的回饋來改進設計概念，並為應用程式使用者的審核和非同步回饋建立協議。 目前，我們正在啟動直接外展活動，以安排主持的回饋會議，並確保這些會議的翻譯機制到位。 一旦該協議在 MediaWiki 上可用，我們將發出更廣泛的通訊，開始在我們的討論頁面上收集非同步回饋。

提供的設計概念旨在提供範例，說明我們如何解決其他工具面臨的問題。 但是，請注意，我們正處於此過程的早期階段，設計將根據我們在未來幾週內收到的回饋進行演變和擴展。

2023 年 1 月：比較審查與現有使用者研究

團隊進行了對比審查，分析了現有的巡邏工具。 在審查過程中，我們評估了這些工具之間的異同，並確定了哪些工具在行動裝置上有效。

我們已審查的工具完整清單包括：

  • Huggle
  • Twinkle
  • TwinkleMobile
  • STiki
  • SWViewer
  • WikiLoop Double Check
  • CheckWiki
  • ReWarn
  • CheckWiki

透過我們的評估，我們發現大多數工具都針對桌面使用進行了最佳化，只有三個例外。此外，上述解決方案中只有兩個在各種語言的維基專案上表現良好。

這些工具中常見的元素是：

  • 代表主要操作的圖示（例如恢復、快速刪除、歡迎用戶等）
  • 存取模板
  • 過濾器
  • 貢獻清單
  • 差異
  • 有關編輯的信息

除了對現有工具進行比較審查之外，我們同時收集了巡查員關於這些工具的反覆請求。常見的請求包括：

  • 按感興趣的主題和特定時段過濾貢獻
  • 一種排除已巡查的貢獻的簡單方法
  • 不需要特殊權限，例如存取工具的回溯權限
  • 「跳過」和「恢復」之間的選項可實現更細緻的操作
  • 促進巡查員之間合作的工具

透過考慮這些要求，我們的目標是開發一個全面的巡邏解決方案，滿足不同語言和使用者體驗水平的巡查員的需求和偏好。

2022 年 12 月：概念驗證原型

該團隊開發了一個概念驗證原型，以探索使用現有 API 的功能和可能性。 這個原型使我們能夠測試和實驗不同的功能並評估我們想法的可行性。 這種早期探索有助於我們了解這些工具的潛力，並在進一步開發之前完善我們的方法。

  • Anti-Vandalism Patrolling task proof of concept
    Anti-Vandalism Patrolling task proof of concept
  • Anti-vandalism patrolling proof of concept
    Anti-vandalism patrolling proof of concept
  • Screen recording of prototype

During our development process, we successfully exposed the ORES score, which provides users with an indication of the likelihood that something may be vandalism. This feature allows users to get insights into the quality of edits and helps them make informed decisions during the patrolling process. We would ideally send feedback to the research team's API for improvements, which will be valuable in improving the accuracy and effectiveness of the ORES score.

2022 年 11 月：定義初始受眾

該團隊進行了研究(T322065)，以評估擁有管理員和回滾權限的維基百科應用程式使用者的數量。 調查結果顯示，372 名安卓系統(Android)應用程式用戶和 176 名 iOS 用戶擁有這些權利。 根據這些數據，我們決定優先在安卓系統(Android) 應用程式中推出該功能，以便 iOS 開發團隊能夠專注於建立「關注列表」功能。

此外，我們同時試著了解不同語言中擁有管理員和回溯權限的使用者分佈。這些資訊在確定我們在初始研究階段直接推廣的初始目標語言社群方面發揮了至關重要的作用。透過關注這些特定的語言社群，我們的目標是從具有審核和巡邏經驗的用戶那裡獲得寶貴的見解和回饋，這將有助於開發該功能以供更廣泛的使用：

  • 英语维基百科
  • 法语维基百科
  • 中文维基百科
  • 西班牙语维基百科

雖然我們專注於直接接觸特定語言的維基社群和作業系統用戶，但我們想強調，我們歡迎並高度鼓勵任何具有巡邏經驗的應用程式用戶提供回饋和想法。我們同時重視網路使用者的意見，但我們的首要任務是收集應用程式使用者的回饋。

創建跨平台的統一體驗至關重要，為了實現這一目標，我們與管理員工具團隊密切溝通，他們將為網頁用戶建立相關的體驗。透過學習他們的發現並密切合作，我們的目標是確保應用程式和網路平台的連續性和一致性。您的回饋和想法將對所有使用者的巡邏功能的開發和改進發揮至關重要的作用。

Retrieved from "https://www.mediawiki.org/w/index.php?title=Wikimedia_Apps/Team/Android/Anti_Vandalism/zh&oldid=6855499"