<?xml version="1.0"?>
<feed xmlns="http://www.w3.org/2005/Atom" xml:lang="en">
	<id>https://consumerrights.wiki/api.php?action=feedcontributions&amp;feedformat=atom&amp;user=78.0.191.204</id>
	<title>Consumer Rights Wiki - User contributions [en]</title>
	<link rel="self" type="application/atom+xml" href="https://consumerrights.wiki/api.php?action=feedcontributions&amp;feedformat=atom&amp;user=78.0.191.204"/>
	<link rel="alternate" type="text/html" href="https://consumerrights.wiki/w/Special:Contributions/78.0.191.204"/>
	<updated>2026-05-17T04:26:30Z</updated>
	<subtitle>User contributions</subtitle>
	<generator>MediaWiki 1.44.0</generator>
	<entry>
		<id>https://consumerrights.wiki/index.php?title=Talk:ReCAPTCHA&amp;diff=53240</id>
		<title>Talk:ReCAPTCHA</title>
		<link rel="alternate" type="text/html" href="https://consumerrights.wiki/index.php?title=Talk:ReCAPTCHA&amp;diff=53240"/>
		<updated>2026-05-10T08:58:06Z</updated>

		<summary type="html">&lt;p&gt;78.0.191.204: /* reCAPTCHA Mobile Verification &amp;quot;AI-resistant challenge&amp;quot; */ new section&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;== reCAPTCHA Mobile Verification &amp;quot;AI-resistant challenge&amp;quot; ==&lt;br /&gt;
&lt;br /&gt;
Here is a huge bombshell being shared around in libre spaces:&lt;br /&gt;
&lt;br /&gt;
https://reclaimthenet.org/google-broke-recaptcha-for-de-googled-android-users&lt;br /&gt;
&lt;br /&gt;
In summary, reCAPTCHA now serves a new form of CAPTCHA for IPs/devices flagged as bots (mobile, desktop, etc.), presenting itself as a QR code. The problem is, anyone who isn&#039;t using an Android/iOS phone with sufficiently updated Google Play Services, being de-Googled Android phones, Linux phones, feature phones, and having a complete lack thereof will get locked out.&lt;br /&gt;
&lt;br /&gt;
In fairness, the regular CAPTCHA still shows up, however, anyone who is unlucky to have their IP/device flagged and has to perform an action gated behind reCAPTCHA (login/register/anything else) could find themselves having to use this new flow.&lt;br /&gt;
&lt;br /&gt;
I think that previously, Google showed an infinite CAPTCHA or refused to even serve a CAPTCHA upon bot detection, so this should merely be a new way to regain clean status, right? This still sets a dangerous precedent, and only time will tell if this becomes the only way to solve the CAPTCHA and whether other CAPTCHA providers will incorporate something like this.&lt;br /&gt;
&lt;br /&gt;
This is part of a larger &amp;quot;Google Cloud Fraud Defense&amp;quot; program designed to &amp;quot;verify the legitimacy of bots, humans, and AI agents&amp;quot;:&lt;br /&gt;
&lt;br /&gt;
https://cloud.google.com/blog/products/identity-security/introducing-google-cloud-fraud-defense-the-next-evolution-of-recaptcha/&lt;br /&gt;
&lt;br /&gt;
Reading into it, it isn&#039;t clear whether this measure is exclusively used to verify users&#039; use of AI agents (it doesn&#039;t appear that way), but regardless, this is now a feature of reCAPTCHA.&lt;/div&gt;</summary>
		<author><name>78.0.191.204</name></author>
	</entry>
</feed>