Summary
hCaptcha is configured in 99.9% passive mode. A challenge is presented when hCaptcha suspects a bot is involved. In these cases, we want to record the diff of the existing content to proposed new editor content, so we can analyze if the content was likely spam
Technical notes
- Rely on confirmEditMerged hook to detect when challenge is presented after edit change, and compute diff change, and send a backend event to a schema
- Add a separate schema to the schemas-event-secondary repo ( with a field proposed_content_diff which would be a unified diff string, T408613)
Acceptance criteria
- The proposed changes to a page from an editor are logged in an event logging stream for further analysis when a challenge is presented