Concern 183 · Working draft · editorial review in progress
CAPTCHA breakage
CAPTCHA breakage occurs when automated systems can pass a challenge intended to distinguish people from bots.
Understanding the concern
CAPTCHAs often ask users to recognize images or complete another task assumed to be difficult for software. As machine perception improves, that assumption can weaken. A successful challenge may then provide less evidence of human participation than the service expects.
A CAPTCHA is usually only one signal in a wider system. Research against a particular version does not show that every bot defense is broken. Stronger defenses must also consider accessibility, privacy, and the burden on legitimate users rather than simply making puzzles harder.
An example
A gatekeeper asks a question once difficult for machines, but newer machines have learned that skill too.
Illustrative unless identified as a documented case.
Words in plain English
- CAPTCHA
- A challenge used by a website to try to distinguish human users from automated software.
Evidence and its limits
The paper evaluates reCAPTCHAv2 under its experimental conditions, not all CAPTCHA products or the entire abuse-prevention stack.
Plesner, Vontobel and Wattenhofer · 2024 · Research study
Breaking reCAPTCHAv2 ↗ (opens in a new tab)Evaluates a particular image-challenge system and conditions, not every CAPTCHA or abuse defense.
Broader frameworks and background
These resources provide context. They do not establish every claim in this concern.
A question to discuss
What evidence besides puzzle-solving helps identify abuse without excluding legitimate users?
Keep track of different views, what needs checking, and any next step in your own discussion notes.
Open discussion notes →Principles for the conversation
Before you finish · reflect together
Virtues and principles to consider
Virtues are qualities we practice in how we treat people and make choices. They are not scores for judging someone. Use these ideas to explore what a thoughtful response could look like.
Stewardship
Stewardship means caring for resources and systems that others depend on, including people who will use them later. It looks beyond the benefit of a quick launch.
Plan for maintenance, energy use, data protection, and eventual shutdown. Ask who will look after the tool when the original team moves on and how future users can avoid inheriting hidden costs.
Ask together: What are we responsible for caring for over time?
Prudence
Prudence means using careful judgment before and during action. It balances worthwhile opportunities with the need to avoid harm that could have been anticipated.
Start with a limited trial, set stopping points, and prefer choices that can be undone when uncertainty is high. Review what happens rather than assuming the original plan remains sound.
Ask together: What is a careful next step, and when should we stop or change course?
Accountability
Accountability means being answerable for decisions and taking responsibility for repair. It requires more than saying that the software made the choice.
Name the person or team responsible, keep useful records, and give them authority to correct problems. Make the route to a complaint clear to the people affected.
Ask together: Who will answer for the outcome and help put things right?
Editorial ratings
These are editorial judgments from the register, not measured probabilities or predictions about your situation.
About the register and scoring →More ways to explore
Search for more writing
For more specific or recent material, open a search below or ask for a web summary. AI-generated summaries can contain mistakes; open the original articles to check them.