Change Details

The Product Safety and Integrity team is testing a bot detection service (hCaptcha) as a possible replacement for the current CAPTCHA system. In a deployment planned for Q2 (2025 - 2026), the team will release hCaptcha in 100% passive mode [i] (to start) in the source/wikitext editor [ii] and move to a 99.9% passive mode if the latter does not surface any issues. This task involves the work of: # **Editing + Product Analytics**: ## Document the metrics we need to be gathered as part of this trial so that we can evaluate its impact on the core editing funnel ## Review instrumentation plan !!(@EMill-WMF to link)!! being added as part of this trial and ensure it accords with established patterns in EditAttemptStep and VisualEditorFeatureUse. //E.g. T409701.// # **Product Safety and Integrity** ## Confirm key editing metrics (see below) are implemented in a way that will enable Editing to evaluate === Open questions - [ ] 1. At what point in the editing funnel will requests be sent off to hCaptcha? //Knowing this will enable the Editing Team to determine the point from which to look at the metrics listed below.// === Editing key metrics WARNING: this section will not be considered final and ready for review by Product Safety and Integrity until @MNeisler has singed off on its completeness and accuracy. |Learning objective|Metric(s)|Notes |---|---|--- |**Edit completion**: What proportion of people go on to publish an edit after reaching the point in the editing funnel when a request is sent off to hCaptcha?| | |**Time to save**: How much time does hCaptcha introduce into the publishing process?| | |**Edit abandonment:** What proportion of people abandon edits after reaching the point in the editing funnel when a request is sent off to hCaptcha?| | |**No-JS users:** What % of edits are blocked from publishing b/c someone is attempting to edit without JS enabled?| | |**Edit quality:** How does the rate at which edits are reverted or cause an AbuseFilter to become activated vary between edits included as part of this trial and those that are not?| | |[nice to have] **Editor retention:** How does editor retention vary among people whose edits are sent off to hCaptcha and those that are not?| | --- i. Where "100% passive mode" means all edit included in the trial: -- Will be submitted to hCaptcha client for evaluation -- Will NOT be presented with a puzzle/challenge ii. A trial of hCaptcha within visualeditor-based editing interfaces will occur at a later time.

The Product Safety and Integrity team is testing a bot detection service (hCaptcha) as a possible replacement for the current CAPTCHA system. In a deployment planned for Q2 (2025 - 2026), the team will release hCaptcha in 99.9% passive mode on several wikis, and in 100% passive mode [i] on enwiki/frwiki in the source/wikitext editor [ii] and move to a 99.9% passive mode after one week of data collection This task involves the work of: # **Editing + Product Analytics**: ## Document the metrics we need to be gathered as part of this trial so that we can evaluate its impact on the core editing funnel ## Review instrumentation plan !!(@EMill-WMF to link)!! being added as part of this trial and ensure it accords with established patterns in EditAttemptStep and VisualEditorFeatureUse. //E.g. T409701.// # **Product Safety and Integrity** ## Confirm key editing metrics (see below) are implemented in a way that will enable Editing to evaluate === Open questions - [ ] 1. At what point in the editing funnel will requests be sent off to hCaptcha? //Knowing this will enable the Editing Team to determine the point from which to look at the metrics listed below.// === Editing key metrics WARNING: this section will not be considered final and ready for review by Product Safety and Integrity until @MNeisler has singed off on its completeness and accuracy. |Learning objective|Metric(s)|Notes |---|---|--- |**Edit completion**: What proportion of people go on to publish an edit after reaching the point in the editing funnel when a request is sent off to hCaptcha?| | |**Time to save**: How much time does hCaptcha introduce into the publishing process?| | |**Edit abandonment:** What proportion of people abandon edits after reaching the point in the editing funnel when a request is sent off to hCaptcha?| | |**No-JS users:** What % of edits are blocked from publishing b/c someone is attempting to edit without JS enabled?| | |**Edit quality:** How does the rate at which edits are reverted or cause an AbuseFilter to become activated vary between edits included as part of this trial and those that are not?| | |[nice to have] **Editor retention:** How does editor retention vary among people whose edits are sent off to hCaptcha and those that are not?| | --- i. Where "100% passive mode" means all edit included in the trial: -- Will be submitted to hCaptcha client for evaluation -- Will NOT be presented with a puzzle/challenge ii. A trial of hCaptcha within visualeditor-based editing interfaces will occur at a later time.

The Product Safety and Integrity team is testing a bot detection service (hCaptcha) as a possible replacement for the current CAPTCHA system. In a deployment planned for Q2 (2025 - 2026), the team will release hCaptcha in 100% passive mode [i] (to start) in the source/wikitext editor [ii] and move to a 99.9% passive mode if the latter does not surface any issues.99.9% passive mode on several wikis, and in 100% passive mode [i] on enwiki/frwiki in the source/wikitext editor [ii] and move to a 99.9% passive mode after one week of data collection This task involves the work of: # **Editing + Product Analytics**: ## Document the metrics we need to be gathered as part of this trial so that we can evaluate its impact on the core editing funnel ## Review instrumentation plan !!(@EMill-WMF to link)!! being added as part of this trial and ensure it accords with established patterns in EditAttemptStep and VisualEditorFeatureUse. //E.g. T409701.// # **Product Safety and Integrity** ## Confirm key editing metrics (see below) are implemented in a way that will enable Editing to evaluate === Open questions - [ ] 1. At what point in the editing funnel will requests be sent off to hCaptcha? //Knowing this will enable the Editing Team to determine the point from which to look at the metrics listed below.// === Editing key metrics WARNING: this section will not be considered final and ready for review by Product Safety and Integrity until @MNeisler has singed off on its completeness and accuracy. |Learning objective|Metric(s)|Notes |---|---|--- |**Edit completion**: What proportion of people go on to publish an edit after reaching the point in the editing funnel when a request is sent off to hCaptcha?| | |**Time to save**: How much time does hCaptcha introduce into the publishing process?| | |**Edit abandonment:** What proportion of people abandon edits after reaching the point in the editing funnel when a request is sent off to hCaptcha?| | |**No-JS users:** What % of edits are blocked from publishing b/c someone is attempting to edit without JS enabled?| | |**Edit quality:** How does the rate at which edits are reverted or cause an AbuseFilter to become activated vary between edits included as part of this trial and those that are not?| | |[nice to have] **Editor retention:** How does editor retention vary among people whose edits are sent off to hCaptcha and those that are not?| | --- i. Where "100% passive mode" means all edit included in the trial: -- Will be submitted to hCaptcha client for evaluation -- Will NOT be presented with a puzzle/challenge ii. A trial of hCaptcha within visualeditor-based editing interfaces will occur at a later time.