Usually feels like
An evening
You put the machine down and come back to it the same day.
A single picture is a seconds wait. A loop you cannot get out of is an evening, because the way out of it is almost always time rather than effort.
The wait, in plain words
The gate hands you an image, you type what you see, and it puts you back at the gate. Once is a misread. A run of them is a different problem wearing the same screen.
The instinct is to concentrate harder, and it is the wrong instinct, because most of the reasons a gate refuses you have nothing to do with your eyes. Effort is the input you have, so effort is what you apply, and effort is the one thing this screen does not respond to.
This is the band where the correct move is to shut the tab and come back after doing something else. It is also the band where hardly anybody does that, because leaving feels like giving up and reloading feels like progress.
Underneath, while nothing moves
Four separate failures share this one screen, and the screen refuses to distinguish between them.
- You read it wrongly. Fixed by looking again. These images are drawn to be awkward for software, which makes them awkward for tired people as a side effect.
- The image never fully arrived. Over this network a picture can paint part way and stop, and part of a picture is not solvable. It is the same failure as a page that half arrived, in a smaller frame.
- The session expired. The gate issued a challenge with a lifetime attached to it. If you looked away, made tea, or spent a long time squinting, your answer can be correct and stale at the same time.
- You are being throttled. Repeated failures from one direction get slowed deliberately. The gate stops being a test and becomes a delay, and it will not tell you that it has changed job.
None of the four announces itself. You get the same refusal in every case, partly because a gate that explained its reasoning would be explaining it to the wrong audience as well as to you.
That is why elapsed time is the fix rather than effort. Three of the four resolve on their own. A fresh request brings a complete image, a fresh session starts with a full lifetime, and a limiter forgets about you. Only the first cause is about you, and it is the one you have already tried at length.
Loading the gate again straight away is the worst available move. It asks for a new image over a path that was already struggling to deliver the last one, it starts another session clock while you are still tired, and it adds one more entry to whatever counter is watching your direction. A cooldown after failed tries is what this becomes once that counter tips over.
Behaving, and not behaving
A gate being strict and a gate that has closed on you look identical for the first few rounds. What separates them is what changes between attempts, not how the refusal is worded.
A gate being strict
Every attempt brings a new image, the image arrives whole, and the refusal comes back at a reasonable speed. You are being tested and failing, which is irritating and completely normal.
A short break and a fresh look usually ends it. Nothing is escalating and nothing is being counted against you.
A gate that has closed
Images arrive broken, or do not arrive, or the same picture comes back unchanged. Refusals return instantly, faster than any real check could run, or arrive after a delay that keeps growing.
Here more attempts make things worse rather than better. The way out is to stop, and the length of the stop is not something the screen will ever tell you.
The belief that ruins this evening is that the counter resets when you leave the page. It does not. It resets when whatever holds it decides it has, on a schedule that has nothing to do with your patience or your reasons for being in a hurry.
If a real break has not got you through, the remaining honest options are to come back later on a different path or to accept that the evening is spent. The gate screen holding you covers the shorter version of this, where the wait is the gate working rather than the gate refusing.
Safe to do meanwhile
The whole list is variations on leaving, because leaving is the mechanism.
- Close the tab properlyNot a reload. The session you are fighting only ends when you stop holding it open.
- Give it longer than feels necessaryA limiter forgets you on its own schedule, and coming back early restarts the count you were waiting out.
- Read what the picture is forIt costs almost nothing and it explains why these images are drawn the way they are.
- Return on a fresh circuit laterA different path is not a trick. It is simply a different path, and it is worth one attempt.
What makes it longer
Almost everything here is something people do precisely because it feels like effort.
- Hammering the reload, which asks for images faster than the path can deliver them and feeds whatever is counting.
- Answering slowly, which is good for reading and fatal for a challenge with a short lifetime on it.
- A congested or slow path, which delivers partial images reliably and correct ones rarely.
- Several tabs open on the same gate, each holding a session and each adding to the same count.
- Coming back too soon after a break, which restarts the clock instead of finishing it.
- Being tired, which is the only cause on this list that gets worse the longer you sit there.
What this card is not. This card is not a technique for solving a captcha and it cannot tell you why a particular gate refused a particular answer.