Your CAPTCHA Sucks: A Manifesto
I need to say something and I need to say it now. I am a software developer. I build things for the internet. And multiple times every single day, the internet asks me to identify fire hydrants in a grid of photos like I'm taking a vision test administered by a parking meter. I am done. I am so done. This is my manifesto and I will not be silenced.
The Fire Hydrant Industrial Complex
Do you know how many fire hydrants I have clicked in my lifetime? I don't. Nobody does. Google doesn't publish those numbers because if people saw the aggregate total of human hours spent clicking fire hydrants, there would be riots. Actual riots. We have collectively spent millions of hours identifying objects in photographs so that Google's self-driving cars can navigate intersections, and our compensation for this labor is the privilege of accessing websites we were already trying to use. This is not a security measure. This is a hostage situation with better branding.
The Accessibility Nightmare Nobody Mentions
reCAPTCHA image challenges are functionally unusable for people with visual impairments. The audio alternative is a garbled mess of distorted numbers that sounds like a numbers station broadcasting from inside a washing machine. If you're color blind, good luck distinguishing traffic lights from street lamps in a compressed JPEG. Google's solution to web accessibility was to create the least accessible verification system imaginable and then make it mandatory for half the internet. Nobody talks about this enough. It's genuinely exclusionary and it makes me furious every time I think about it.
The "Invisible" CAPTCHA That Isn't
reCAPTCHA v3 claimed to solve everything by going invisible. No more puzzles! Just a score! Except now you have a Google script running on every page of your site, tracking mouse movements, scroll patterns, and browsing behavior to generate a "human likelihood score." You traded a bad user experience for comprehensive surveillance. And if the score is ambiguous? You still have to fall back to the image grid. So now you have surveillance AND fire hydrants. Progress.
hCaptcha: Same Problems, Different Logo
Before someone comments "just use hCaptcha," please know that I have also clicked many, many motorcycles for hCaptcha. The user experience is identical. The business model is identical (you label data, they sell it). The only difference is which company profits from your unpaid labor. Switching from reCAPTCHA to hCaptcha is like switching from one brand of mosquito to another brand of mosquito. You're still getting bitten.
What I Actually Want
I want a verification system that: does not track my users, does not make them perform free labor, does not exclude people with disabilities, and actually filters the threats that matter. Traditional CAPTCHAs fail on all four counts. They stop bots (poorly) while letting state-sponsored human attackers walk right through.
EVANDALIZE is the unhinged alternative I didn't know I needed. Instead of clicking fire hydrants, users draw on dictator portraits. It's genuinely fun. It doesn't train anyone's AI. It doesn't track anyone. And it creates a jurisdictional barrier that actually blocks the most dangerous threat actors on earth. Is it weird? Yes. Is it a better security model than "click all the buses"? Also yes. Unambiguously yes.
The Call to Action
Stop using reCAPTCHA. Stop using hCaptcha. Stop making your users identify crosswalks and bicycles and parking meters. Read the EVANDALIZE API docs. Get a free key from the dashboard. The integration takes ten minutes. Your users will thank you. I will thank you. The fire hydrants will finally rest.